throbber
REMARKS
`
`This Amendment is fully responsive to the final Office Action dated August 14, 2019,
`
`issued in connection with the above-identified application. A request for continued examination
`
`(RCE) is included. Claims 1-14 are pending in the present application. With this Amendment,
`
`claims 1, 7, 13, and 14 have been amended. The amendments made to the claims are fully
`
`supported by the Applicant’s disclosure (e.g., paragraphs [0119]-[0125] of the US publication of
`
`the present application). Therefore, no new matter has been introduced by the amendments made
`
`to the claims. Favorable reconsideration is respectfully requested.
`
`In the Office Action, claims 13 and 14 are objected to because the phrase “to operates as”
`
`is grammatically incorrect and should be changed to “to operate as.”
`
`The Applicant has amended claims 13 and 14, as suggested by the Examiner (e.g., “to
`
`operate as”). Based on the amendments made to the claims, withdrawal of the objection to the
`
`claims is respectfully requested.
`
`In the Office Action, claims 1-4, 7-10, 13, and 14 are rejected under 35 U.S.C. 103 as
`
`being unpatentable over Kwon et al. (US 2017/0171070, hereafter “K1”) in view of (“WT-
`
`Based Media Transport Scheme in Digital Broadcasting Systems,” hereafter “ARIB”).
`
`The Applicant has amended independent claims 1, 7, 13, and 14. For example,
`
`independent claim 1 (as amended) recites the following features:
`
`“A transmission method comprising:
`
`generating a frame for transfer in which one or more first internet protocol (1P) packets
`
`and one or more second IP packets are stored, the one or more first IP packets storing content,
`
`and each of the one or more second IP packets including first reference clock information which
`
`indicates a time for playing back the content, and
`
`transmitting the generated frame through broadcasting including attaching, to each of the
`
`one or more first IP packets and each of the one or more second IP packets, a context identifier
`
`indicating a preset fixed value in accordance with a type of an IP data flow,
`
`wherein second reference clock information is stored in control information in a physical
`
`layer and the control information is transmitted, and
`
`in the generating, header compression is performed on the one or more first IP packets
`
`and the header compression is not performed on the one or more second IP packets.” (Emphasis
`
`added).
`
`

`

`The features emphasized above in independent claim 1 are similarly recited in
`
`independent claims 7, l3, and 14. That is, independent claim 7 and 14 are directed respectively
`
`to a reception method and a reception apparatus that receive the first reference clock information
`
`and second reference clock information emphasized above in independent claim 1. Additionally,
`
`independent claim 13 is directed to a transmission apparatus reciting the same features noted
`
`above in independent claim 1.
`
`The features recited in independent claims 1, 7, l3, and 14 are believed to be
`
`distinguished from the cited prior art at least with regard to respectively reciting the transmitting
`
`and receiving of the one or more first IP packets storing content, wherein each of the one or more
`
`second IP packets includes first reference clock information which indicates a time for playing
`
`back the content, and respectively reciting the transmitting and receiving of second reference
`
`clock information stored in control information in a physical layer.
`
`More specifically, as recited in independent claims 1, 7, l3, and 14, the first reference
`
`clock information is transmitted and received in an IP layer and the second reference clock
`
`information is transmitted and received in a physical layer different from the 1P layer.
`
`In the Office Action, although the Examiner relies on the combination of K1 and ARIB
`
`for disclosing or suggesting all the features recited in independent claims 1, 7, l3, and 14, the
`
`Examiner appears to rely specifically on Kl for disclosing or suggesting the use of reference
`
`clock information. In particular, the Examiner relies on paragraphs [0302] and [0308] of K1.
`
`K1 in paragraph [0302] discloses that a “Clock Relation Information (CRI)” message
`
`including an CR1 table, which contains clock related information for the mapping between the
`
`NTP timestamp and the MPEG-2 STC. As described in K1, the CRI message may not be
`
`delivered through the MIVITP session.
`
`K1 in paragraph [0308] discloses the use of a physical layer pipe identifier descriptor that
`
`can be used as one of descriptors of an MP table and provides information about the PLP
`
`carrying an asset. As described in Kl. if an asset is delivered by a PLP different from the current
`
`PLP delivering the MP table, the physical layer pipe identifier descriptor can be used as an asset
`
`descriptor in the associated MP table to identify the PLP carrying the asset. The physical layer
`
`pipe identifier descriptor may also include BSID information, which can be an ID of a broadcast
`
`stream that delivers an MMTP packet for an asset described by the descriptor.
`
`

`

`K1 also clearly refers to the use of the ATSC3.0 broadcast standard (e.g., paragraph
`
`[0299]).
`
`Based on a review of K1, nothing in the reference discloses or suggests first reference
`
`clock information transmitted and received in an IP layer and second reference clock information
`
`transmitted and received in a physical layer different from the 1P layer, as recited in independent
`
`claims 1, 7, 13, and 14.
`
`As noted above, although the Examiner relies on the combination of K1 and ARIB for
`
`disclosing or suggesting all the features recited in independent claims 1, 7, 13, and 14, the
`
`Examiner appears to rely specifically on K1 for disclosing or suggesting the use of reference
`
`clock information.
`
`Thus, based on the deficiencies noted above in K1, no combination of K1 and ARIB
`
`would result in, or otherwise render obvious, all the features now recited in independent claims
`
`1, 7, 13, and 14. Additionally, no combination of K1 and ARIB would result in, or otherwise
`
`render obvious, all the features of claims 2-4 and 8-10 at least by their virtue of their respective
`
`dependencies from independent claims 1 and 7.
`
`In the Office Action, claims 5, 6, 11, and 12 are rejected under 35 U.S.C. 103 as being
`
`unpatentable over K1 in view of ARIB, as applied to claims 1 and 7 above, in further view of
`
`Vare et al. (US 2007/0268874, hereafter “Vare”).
`
`Claims 5 and 6 depend from independent claim 1, and claims 11 and 12 depend from
`
`independent claim 7.
`
`As noted above, K1 and ARIB fail to disclose or suggest all the features recited in
`
`independent claims 1 and 11 (as amended). Additionally, Vare fails to overcome the deficiencies
`
`noted above in the combination of K1 and ARIB. Accordingly, no combination of K1 and ARIB
`
`would result in, or otherwise render obvious, all the features of claims 5, 6, 11 and 12 at least by
`
`virtue of their respective dependencies from independent claims 1 and 11.
`
`In light of the above, the Applicant submits that all the pending claims are patentable
`
`over the prior art of record. The Applicant respectfully requests that the Examiner withdraw the
`
`rejections presented in the outstanding Office Action and pass the present application to issue.
`
`

`

`The Examiner is invited to contact the undersigned attorney by telephone in order to resolve any
`
`issues remaining in the application.
`
`Respectfully submitted,
`
`/Mark D. Pratt/
`
`
`2019.11.1411259216 -05'OO'
`
`Mark D. Pratt
`
`Registration No. 45,794
`Attorney for Applicant
`
`WENDEROTH, LIND & PONACK, L.L.P.
`1025 Connecticut Avenue, N.W., Suite 500
`Washington, DC. 20036
`Telephone (202) 721-8200
`Facsimile (202) 721-8250
`November 14, 2019
`
`The Director is hereby authorized to charge any fees which may be required, or credit any overpayment
`to Deposit Account No. 23-09 75.
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket