throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`UNITED STATES DEPARTMENT OF COMMERCE
`United States Patent and Trademark Office
`Address: COMMISSIONER FOR PATENTS
`P.O. Box 1450
`Alexandria, Virginia 2231371450
`www.uspto.gov
`
`15/618,803
`
`06/09/2017
`
`Noritaka IGUCHI
`
`2017-0916A
`
`4299
`
`52349
`
`759°
`
`03/06/20”
`
`WENDEROTH, LIND & PONACK L.L.P.
`1030 15th Street, N.W.
`Suite 400 East
`
`Washington, DC 20005-1503
`
`KAVLESKI‘ RYANC
`
`ART UNIT
`2412
`
`PAPER NUMBER
`
`NOTIFICATION DATE
`
`DELIVERY MODE
`
`03/06/2019
`
`ELECTRONIC
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`The time period for reply, if any, is set in the attached communication.
`
`Notice of the Office communication was sent electronically on above—indicated "Notification Date" to the
`
`following e—mail address(es):
`eoa @ wenderoth. com
`kmiller @ wenderotheom
`
`PTOL-90A (Rev. 04/07)
`
`

`

`0/7709 A0170” Summary
`
`Application No.
`15/618,803
`Examiner
`RYAN c KAVLESKI
`
`Applicant(s)
`IGUCHI etal.
`Art Unit
`2412
`
`AIA (FITF) Status
`Yes
`
`- The MAILING DA TE of this communication appears on the cover sheet wit/7 the correspondence address -
`Period for Reply
`
`A SHORTENED STATUTORY PERIOD FOR REPLY IS SET TO EXPIRE g MONTHS FROM THE MAILING
`DATE OF THIS COMMUNICATION.
`Extensions of time may be available under the provisions of 37 CFR 1.136(a). In no event, however, may a reply be timely filed after SIX (6) MONTHS from the mailing
`date of this communication.
`|f NO period for reply is specified above, the maximum statutory period will apply and will expire SIX (6) MONTHS from the mailing date of this communication.
`-
`- Failure to reply within the set or extended period for reply will, by statute, cause the application to become ABANDONED (35 U.S.C. § 133).
`Any reply received by the Office later than three months after the mailing date of this communication, even if timely filed, may reduce any earned patent term
`adjustment. See 37 CFR 1.704(b).
`
`Status
`
`1). Responsive to communication(s) filed on 6/9/2017.
`[:1 A declaration(s)/affidavit(s) under 37 CFR 1.130(b) was/were filed on
`
`2a)D This action is FINAL.
`
`2b)
`
`This action is non-final.
`
`3)[:] An election was made by the applicant in response to a restriction requirement set forth during the interview on
`; the restriction requirement and election have been incorporated into this action.
`
`4)[:] Since this application is in condition for allowance except for formal matters, prosecution as to the merits is
`closed in accordance with the practice under Expat/7e Quay/e, 1935 CD. 11, 453 O.G. 213.
`
`Disposition of Claims*
`5)
`Claim(s)
`
`1—14is/are pending in the application.
`
`5a) Of the above claim(s)
`
`is/are withdrawn from consideration.
`
`E] Claim(s)
`
`is/are allowed.
`
`Claim(s) fl is/are rejected.
`
`[:1 Claim(s) _ is/are objected to.
`
`) ) ) )
`
`6 7
`
`8
`
`
`
`are subject to restriction and/or election requirement
`[j Claim(s)
`9
`* If any claims have been determined aflowabie. you may be eligible to benefit from the Patent Prosecution Highway program at a
`
`participating intellectual property office for the corresponding application. For more information, please see
`
`http://www.uspto.gov/patents/init events/pph/index.jsp or send an inquiry to PPeredback@uspto.gov.
`
`Application Papers
`10)[:] The specification is objected to by the Examiner.
`
`11). The drawing(s) filed on 6/9/2017 is/are: a). accepted or b)D objected to by the Examiner.
`
`Applicant may not request that any objection to the drawing(s) be held in abeyance. See 37 CFR 1.85(a).
`Replacement drawing sheet(s) including the correction is required if the drawing(s) is objected to. See 37 CFR 1.121 (d).
`
`Priority under 35 U.S.C. § 119
`12). Acknowledgment is made of a claim for foreign priority under 35 U.S.C. § 119(a)-(d) or (f).
`Certified copies:
`
`a). All
`
`b)D Some**
`
`C)D None of the:
`
`1.. Certified copies of the priority documents have been received.
`
`2.[:] Certified copies of the priority documents have been received in Application No.
`
`3:] Copies of the certified copies of the priority documents have been received in this National Stage
`application from the International Bureau (PCT Rule 17.2(a)).
`
`** See the attached detailed Office action for a list of the certified copies not received.
`
`Attachment(s)
`
`1)
`
`Notice of References Cited (PTO-892)
`
`Information Disclosure Statement(s) (PTO/SB/08a and/or PTO/SB/08b)
`2)
`Paper No(s)/Mail Date M.
`U.S. Patent and Trademark Office
`
`3) C] Interview Summary (PTO-413)
`Paper No(s)/Mail Date
`4) CI Other-
`
`PTOL-326 (Rev. 11-13)
`
`Office Action Summary
`
`Part of Paper No./Mai| Date 20190225
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 2
`
`DETAILED ACTION
`
`In response to communication filed on 6/9/2017.
`
`Claims 1-14 are pending.
`
`Claims 1-14 are rejected.
`
`Notice of Pre-AIA or AIA Status
`
`The present application, filed on or after March 16, 2013, is being examined under the first
`
`inventor to file provisions of the AIA.
`
`Information Disclosure Statement
`
`The information disclosure statement (IDS) submitted on 6/9/2017 is in compliance with the
`
`provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the
`
`examiner.
`
`Claim Interpretation
`
`The following is a quotation of 35 U.S.C. 112(f):
`
`(f) Element in Claim for a Combination. — An element in a claim for a combination may be expressed as
`a means or step for performing a specified function without the recital of structure, material, or acts
`in support thereof, and such claim shall be construed to cover the corresponding structure, material,
`or acts described in the specification and equivalents thereof.
`
`The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
`
`An element in a claim for a combination may be expressed as a means or step for performing a
`specified function without the recital of structure, material, or acts in support thereof, and such claim
`shall be construed to cover the corresponding structure, material, or acts described in the
`specification and equivalents thereof.
`
`The claims in this application are given their broadest reasonable interpretation using the plain
`
`meaning of the claim language in light of the specification as it would be understood by one of ordinary
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 3
`
`skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as
`
`a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35
`
`U.S.C. 112, sixth paragraph, is invoked.
`
`As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong
`
`test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
`
`(A)
`
`the claim limitation uses the term ”means” or ”step” or a term used as a substitute for ”means”
`
`that is a generic placeholder (also called a nonce term or a non-structural term having no
`
`specific structural meaning) for performing the claimed function;
`
`(B)
`
`the term ”means” or ”step” or the generic placeholder is modified by functional language,
`
`typically, but not always linked by the transition word ”for” (e.g., ”means for”) or another linking
`
`word or phrase, such as ”configured to” or ”so that”; and
`
`(C)
`
`the term ”means” or ”step” or the generic placeholder is not modified by sufficient structure,
`
`material, or acts for performing the claimed function.
`
`Use of the word ”means” (or ”step”) in a claim with functional language creates a rebuttable
`
`presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35
`
`U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C.
`
`112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient
`
`structure, material, or acts to entirely perform the recited function.
`
`Absence of the word ”means” (or ”step”) in a claim creates a rebuttable presumption that the
`
`claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth
`
`paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-
`
`AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without
`
`reciting sufficient structure, material or acts to entirely perform the recited function.
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 4
`
`This application includes one or more claim limitations that do not use the word ”means,” but
`
`are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph,
`
`because the claim limitation(s) uses a generic placeholder that is coupled with functional language
`
`without reciting sufficient structure to perform the recited function and the generic placeholder is not
`
`preceded by a structural modifier. Such claim limitation(s) is/are: ”a generator” in claim 13 and ”a
`
`determiner” and ”playback unit” in claim 14.
`
`Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA
`
`35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure
`
`described in the specification as performing the claimed function, and equivalents thereof.
`
`|f applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or
`
`pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may:
`
`(1) amend the claim limitation(s) to avoid it/them
`
`being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting
`
`sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim
`
`limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being
`
`interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
`
`Claim Rejections - 35 USC § 112
`
`The following is a quotation of 35 U.S.C. 112(b):
`
`(B) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out
`
`and distinctly claiming the subject matter which the inventor or a joint inventor regards as the
`invention.
`
`The following is a quotation of 35 U.S.C. 112 (pre-AIA), second paragraph:
`
`The specification shall conclude with one or more claims particularly pointing out and distinctly claiming
`
`the subject matter which the applicant regards as his invention.
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 5
`
`Claim 14 is rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA), second paragraph, as
`
`being indefinite for failing to particularly point out and distinctly claim the subject matter which the
`
`inventor or a joint inventor, or for pre-AIA the applicant regards as the invention.
`
`Claim limitation ”a playback unit” invokes 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth
`
`paragraph. However, the written description fails to disclose the corresponding structure, material, or
`
`acts for performing the entire claimed function and to clearly link the structure, material, or acts to the
`
`function. Although Figure 56 and the Specifications provide support for the playback unit [refer
`
`Specifications; page 79], there is no sufficient structure detailed that would allow for one of ordinary
`
`skill in the art to understand the scope of what comprises of the playback unit. Therefore, the claim is
`
`indefinite and is rejected under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph.
`
`Applicant may:
`
`(a)
`
`Amend the claim so that the claim limitation will no longer be interpreted as a limitation under
`
`35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph;
`
`(b)
`
`Amend the written description of the specification such that it expressly recites what structure,
`
`material, or acts perform the entire claimed function, without introducing any new matter (35
`
`U.S.C. 132(a)); or
`
`(c)
`
`Amend the written description of the specification such that it clearly links the structure,
`
`material, or acts disclosed therein to the function recited in the claim, without introducing any
`
`new matter (35 U.S.C. 132(a)).
`
`If applicant is of the opinion that the written description of the specification already implicitly or
`
`inherently discloses the corresponding structure, material, or acts and clearly links them to the function
`
`so that one of ordinary skill in the art would recognize what structure, material, or acts perform the
`
`claimed function, applicant should clarify the record by either:
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 6
`
`(a)
`
`Amending the written description of the specification such that it expressly recites the
`
`corresponding structure, material, or acts for performing the claimed function and clearly links
`
`or associates the structure, material, or acts to the claimed function, without introducing any
`
`new matter (35 U.S.C. 132(a)); or
`
`(b)
`
`Stating on the record what the corresponding structure, material, or acts, which are implicitly or
`
`inherently set forth in the written description of the specification, perform the claimed function.
`
`For more information, see 37 CFR 1.75(d) and MPEP §§ 608.01(o) and 2181.
`
`Claim Rejections - 35 USC § 103
`
`In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102
`
`and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory
`
`basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and
`
`the rationale supporting the rejection, would be the same under either status.
`
`The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections
`
`set forth in this Office action:
`
`A patent may not be obtained though the invention is not identically disclosed or described as set forth in
`section 102 of this title, if the differences between the subject matter sought to be patented and the prior art
`are such that the subject matter as a whole would have been obvious at the time the invention was made to a
`person having ordinary skill in the art to which said subject matter pertains. Patentability shall not be
`negatived by the manner in which the invention was made.
`
`The factual inquiries set forth in Graham v. John Deere C0,, 383 U.S. 1, 148 USPQ 459 (1966),
`
`that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are
`
`summarized as follows:
`
`PENN!“
`
`Determining the scope and contents of the prior art.
`
`Ascertaining the differences between the prior art and the claims at issue.
`
`Resolving the level of ordinary skill in the pertinent art.
`
`Considering objective evidence present in the application indicating obviousness or
`nonobviousness.
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 7
`
`This application currently names joint inventors. In considering patentability of the claims the
`
`examiner presumes that the subject matter of the various claims was commonly owned as of the
`
`effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised
`
`of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that
`
`was not commonly owned as of the effective filing date of the later invention in order for the examiner
`
`to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art
`
`against the later invention.
`
`Claims 1-4,7-10,13 and 14 are rejected under 35 U.S.C. 103 as being unpatentable over Kwon
`
`et al. (US Pub. 2017/0171070)(K1 hereafter) in view of "MMT-Based Media Transport Scheme in
`
`Digital Broadcasting Systems." (ARIB hereafter).
`
`Regarding claims 1 and 13, K1 teaches a transmission apparatus [refer Fig. 18; Transmitter] comprising:
`
`a generator (i.e. link layer)[refer Fig. 18; Transmitter Link Layer] which generates (i.e. structures)
`
`a frame (i.e. media processing unit (MPU))[paragraph 0123] for transfer in which one or more first
`
`internet protocol (IP) packets and one or more second IP packets are stored (the transmitter uses an IP
`
`packet and/or MPEG packets used in digital broadcast as an input signal and performs
`
`encapsulation)[paragraph 0503], the one or more first IP packets storing content (services and content
`
`are delivered using MMTP, which is a MPEG media transport protocol [paragraph 0118] operating on a
`
`IP multicast on a physical layer [paragraph 0121]), and each of the one or more second IP packets
`
`including reference clock information which indicates a time for playing back the content (clock relation
`
`information messages containing a clock related to an NTP timestamp can be delivered with MMTP
`
`messages in a session [paragraph 0302], broadcast streams deliver MMTP packets [paragraph 0308]);
`
`and
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 8
`
`a transmitter (i.e. physical |ayer)[refer Fig. 18; Transmitter Physical Layer] which transmits the
`
`generated frame through broadcasting (i.e. digital broadcast)[paragraph 0503], the generator performs
`
`header compression on the one or more first IP packets (IP header compression can be performed in the
`
`link |ayer)[paragraph 0507].
`
`However K1 does not disclose that the generator does not perform the header compression on
`
`the one or more second IP packets.
`
`ARIB discloses that for an IP packet used for carrying MMTP payloads [refer page 2; ”The codes
`
`of the video and audio signals of a broadcast program shall be in MFU/MPU format, stored into an MMT
`
`protocol (MMTP) payload for MMTP packetization and transferred in an IP packet.”], the IP packet can
`
`be compressed and transferred in an TLV packet format [refer page 3; ”An IP packet or header-
`
`compressed IP packet is transferred in an TLV packet (ARIB STD-B32)”], and IP packets transferring an
`
`NTP format are transferred in a TLV format, however IP header compression are not performed [refer
`
`page 4; ”Moreover, when an IP packet including NTP format is transferred in a TLV format, IP header
`
`compression shall not be performed.”].
`
`It would have been obvious to one of ordinary skill in the art before the effective filing date of
`
`the claimed invention to modify the teachings of K1 for providing header compression on packets [refer
`
`K1; paragraph 0507] and transmitting clock relation information messages containing a clock related to
`
`an NTP timestamp delivered with MMTP messages in a session [refer K1; paragraph 0302] to explicitly
`
`perform header compression on one set of MMTP messages while not performing header compression
`
`on messages comprising NTP information as taught by ARIB. One would be motivated to do so to
`
`provide the use of a known standard, such as that disclosed by ARIB, for providing broadcast
`
`communications to a known system for handling such communications to yield predictable results.
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 9
`
`Regarding claims 2 and 8, K1 teaches the header compression includes: (i) attaching, to a part of the one
`
`or more first IP packets, a full header which includes specification information for specifying an IP data
`
`flow to which the one or more first IP packets belong (IP packets have a fixed header format that has
`
`information which is needed in a communication environment (i.e. specifying IP data flow))[paragraph
`
`0315]; and
`
`(ii) attaching, to a first IP packet other than the part of the one or more first IP packets, a
`
`compressed header which does not include the specification information (for redundant information,
`
`the link layer protocol provides mechanisms to reduce broadcast overhead by providing sync byte
`
`removal, null packet deletion and/or common header removal)[paragraph 0315].
`
`Regarding claims 3 and 9, K1 teaches the reference clock information complies with a network time
`
`protocol (NTP) [paragraph 0302].
`
`Regarding claims 4 and 10, K1 teaches the content is stored in an MPEG media transport (MMT) packet
`
`in each of the one or more first IP packets (services and content are delivered using MMTP, which is a
`
`MPEG media transport protocol [paragraph 0118] operating on a IP multicast on a physical layer
`
`[paragraph 0121]).
`
`Regarding claims 7 and 14, K1 teaches a reception apparatus [refer Fig. 18; Receiver] comprising: a
`
`receiver [refer Fig. 18; Receiver Physical Layer] which receives, through broadcasting [paragraph 0503], a
`
`frame for transfer (i.e. media processing unit (MPU))[paragraph 0123] in which one or more internet
`
`protocol (IP) packets are stored [paragraph 0504], the one or more IP packets storing content (services
`
`and content are delivered using MMTP, which is a MPEG media transport protocol [paragraph 0118]
`
`operating on a IP multicast on a physical layer [paragraph 0121]) and including: one or more first IP
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 10
`
`packets whose headers have been compressed (the receiver receives and restores data and signaling
`
`received from the transmitter [paragraph 0504], IP header compression can be performed in the link
`
`layer by the transmitter [paragraph 0507]); and
`
`one or more second IP packets, each of the one or more second IP packets including reference
`
`clock information which indicates a time for playing back the content (the receiver receives and restores
`
`data and signaling received from the transmitter [paragraph 0504], clock relation information messages
`
`containing a clock related to an NTP timestamp can be delivered with MMTP messages in a session
`
`[paragraph 0302], broadcast streams deliver MMTP packets [paragraph 0308]);
`
`a determiner (i.e. link layer)[refer Fig. 18; Receiver Link Layer] which determines whether each
`
`of the one or more IP packets that are received is the first IP packet or the second IP packet [paragraph
`
`0504]; and
`
`a playback unit (i.e. television)[paragraph 0115] which plays back the content stored in the one
`
`or more first IP packets (the receiver receives data and signaling to be processed [paragraph 0530], the
`
`digital broadcasting is presented to a user [paragraph 0486]), using the reference clock information
`
`stored in the each of the one or more second IP packets, based on a result of the determination
`
`[paragraph 0302].
`
`However K1 does not disclose receiving one or more second IP packets whose headers have not
`
`been compressed and determining whether each of the one or more IP packets that are received is the
`
`first IP packet or the second IP packet based on whether or not a header of the IP packet has been
`
`compressed.
`
`ARIB discloses that for an IP packet used for carrying MMTP payloads [refer page 2; ”The codes
`
`of the video and audio signals of a broadcast program shall be in MFU/MPU format, stored into an MMT
`
`protocol (MMTP) payload for MMTP packetization and transferred in an IP packet.”], the IP packet can
`
`be compressed and transferred in an TLV packet format [refer page 3; ”An IP packet or header-
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 11
`
`compressed IP packet is transferred in an TLV packet (ARIB STD-332)”], and IP packets transferring an
`
`NTP format are transferred in a TLV format, however IP header compression are not performed [refer
`
`page 4; ”Moreover, when an IP packet including NTP format is transferred in a TLV format, IP header
`
`compression shall not be performed.”].
`
`It would have been obvious to one of ordinary skill in the art before the effective filing date of
`
`the claimed invention to modify the teachings of K1 for providing header compression on packets [refer
`
`K1; paragraph 0507] and the transmission of clock relation information messages containing a clock
`
`related to an NTP timestamp delivered with MMTP messages in a session [refer K1; paragraph 0302] to
`
`explicitly allow for header compression on one set of MMTP messages while not performing header
`
`compression on messages comprising NTP information as taught by ARIB. By doing so, compressed data
`
`would be seen as one type, while uncompressed data would be of another. One would be motivated to
`
`do so to provide the use of a known standard, such as that disclosed by ARIB, for providing broadcast
`
`communications to a known system for handling such communications to yield predictable results.
`
`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, as applied above, in further view of Vare et al. (US Pub.
`
`2007/0268874)(V1 hereafter).
`
`Regarding claims 5 and 11, K1 teaches the frame includes one or more second transfer units (i.e. media
`
`processing units (MPUs))[paragraph 0118], each of the one or more second transfer units includes one
`
`or more first transfer units, and each of the one or more first transfer units includes one of: the one or
`
`more first IP packets and the one or more second IP packet [paragraph 0123].
`
`However K1 does not disclose that the one or more second transfer units each having a fixed
`
`length.
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 12
`
`V1 discloses that digital video broadcast (DVB) streams deliver compressed audio and video and
`
`data to a user via transport streams in which the stream is packetized with fixed length packets to carry
`
`different elements of a particular program, video and audio [paragraph 0044].
`
`It would have been obvious to one of ordinary skill in the art before the effective filing date of
`
`the claimed invention to modify the teachings of K1 for providing digital broadcasting to packetize the
`
`transport streams into fixed length packets as taught by V1. One would be motivated to do so to
`
`provide the use of a known technique within digital broadcasting to yield predictable results.
`
`Regarding claims 6 and 12, K1 in view of ARIB teaches each of the one or more first transfer units is a
`
`type length value (TLV) packet [refer ARIB; page 3; ”An IP packet or header-compressed IP packet is
`
`transferred in an TLV packet (ARIB STD-332)”].
`
`However K1 in view of ARIB do not expressly disclose each of the one or more second transfer
`
`units is a slot defined under a transmission system for advanced wide band satellite digital broadcasting,
`
`and the frame is a transfer slot defined under the transmission system for advanced wide band satellite
`
`digital broadcasting.
`
`V1 discloses that digital broadcast standards for broadband broadcast systems can utilize
`
`Integrated Services Digital Broadcasting-Terrestrial, Advanced Television Systems Committee, and other
`
`standards and techniques [paragraph 0037], such that that digital video broadcast (DVB) streams deliver
`
`compressed audio and video and data to a user via transport streams in which the stream is packetized
`
`with fixed length packets to carry different elements of a particular program, video and audio
`
`[paragraph 0044].
`
`It would have been obvious to one of ordinary skill in the art before the effective filing date of
`
`the claimed invention to modify the teachings of K1 for providing digital broadcasting to packetize the
`
`transport streams into fixed length packets using a digital broadcast standard known in the field as
`
`

`

`Application/Control Number: 15/618,803
`Art Unit: 2412
`
`Page 13
`
`taught by V1. One would be motivated to do so to provide the use of a known technique within digital
`
`broadcasting to yield predictable results.
`
`Conclusion
`
`Any inquiry concerning this communication or earlier communications from the examiner
`
`should be directed to RYAN C KAVLESKI whose telephone number is (571)270-3619. The examiner can
`
`normally be reached on M-F 6:30am-3pm.
`
`Examiner interviews are available via telephone, in-person, and video conferencing using a
`
`USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use
`
`the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
`
`If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor,
`
`Charles C Jiang can be reached on 571-270-7191. The fax phone number for the organization where this
`
`application or proceeding is assigned is 571-273-8300.
`
`Information regarding the status of an application may be obtained from the Patent Application
`
`Information Retrieval (PAIR) system. Status information for published applications may be obtained
`
`from either Private PAIR or Public PAIR. Status information for unpublished applications is available
`
`through Private PAIR only. For more information about the PAIR system, see http://pair-
`
`direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic
`
`Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer
`
`Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR
`
`CANADA) or 571-272-1000.
`
`Ryan Kavleski
`
`/R. K./
`
`Examiner, Art Unit 2412
`
`

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