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/437,483
`
`02/21/2017
`
`NORITAKA IGUCHI
`
`2017-0448T
`
`6904
`
`52349
`
`759°
`
`06/11/20”
`
`WENDEROTH, LIND & PONACK L.L.P.
`1025 Connecticut Avenue, NW
`Suite 500
`
`Washington DC 20036
`
`WANG” HANNAH S
`
`ART UNIT
`2454
`
`PAPER NUMBER
`
`NOTIFICATION DATE
`
`DELIVERY MODE
`
`06/ 1 1/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 @ wenderothcom
`
`PTOL-90A (Rev. 04/07)
`
`

`

`0,7709 A0170” Summary
`
`Application No.
`15/437,483
`Examiner
`HANNAH s WANG
`
`Applicant(s)
`IGUCHI et al.
`Art Unit
`2454
`
`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 05/14/2019.
`[:1 A declaration(s)/affidavit(s) under 37 CFR 1.130(b) was/were filed on
`
`2a). This action is FINAL.
`
`2b) C] 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—12 is/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 02/21/2017 is/are: a). accepted or b)[:] 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) C] Notice of References Cited (PTO-892)
`
`Information Disclosure Statement(s) (PTO/SB/08a and/or PTO/SB/08b)
`2)
`Paper No(s)/Mail DateW.
`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 20190603
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 2
`
`DETAILED ACTION
`
`Response to Amendment
`
`This communication is in response to the Amendment filed on 05/14/2019.
`
`Claims 1-12 are pending.
`
`Claims 1,5 and 9-10 have been amended.
`
`Claims 11-12 have been added.
`
`Rel'ection of Claims 1, 5 and 9-10 under 35 us. C. 103
`
`Applicant’s Arguments:
`
`Applicant argues that the prior art of record does not teach “each of the IP data flows always
`
`respectively stores only the corresponding service from among the plurality of services”, because one IP
`
`data flow always corresponds to one service and one IP data flow does not correspond to plural services.
`
`Examiner’s Response:
`
`Applicant's arguments have been fully considered but they are not persuasive.
`
`DASDSA discloses “one-to-one” correspondence between broadcasting service and MMT
`
`package in an IP data flow. In addition, DASDSA further discloses multiple MMT packages m
`
`contained in an IP data flow, which seems to imply that a single MMT package or multiple MMT packages
`
`may be contained in an IP data flow and thus “one-to-one” correspondence between broadcasting
`
`service and IP data flow (broadcasting service-MMT package-IP data flow). However, DASDSA does
`
`not explicitly disclose that a single MMT package or multiple MMT packages may be contained in an IP
`
`data flow and thus does not explicitly teach the “one-to-one” correspondence between broadcasting
`
`service and IP data flow.
`
`In analogous teaching, AOKI explicitly discloses MMT packages (Pg.356, last Para., When a
`
`MMT package is received) in IP data flows for services (Pg.359, Para.2-3, the IP data flow to be received.
`
`The service ID corresponding to the specified IP data flow is identified using AMT... The IP packet
`
`received as described above contains the MMT packets) and multiple packages may be contained in one
`
`IP data flow (Pg.359, Para.4, In broadcasting, multiple packages may be multiplexed in one IP data flow),
`
`which indicates a single package may be contained in one IP data flow.
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 3
`
`Thus, given the teaching of AOKI, it would have been obvious to one of ordinary skill in the art
`
`before the effective filling date of the claimed invention to combine the teaching of a single MMT
`
`package contained in a single IP data flow (one-to—one correspondence between MMT and IP data
`
`flow) of AOKI into a single broadcasting service contained in a single MMT package (one-to-one
`
`correspondence between broadcasting service and MMT package) of DASDSA so that a single
`
`service would be contained in a single IP data flow (one-to-one correspondence between IP data
`
`flow and service). One of ordinary skill in the art would have been motivated to do so because this is
`
`combining prior art elements according to known methods to yield predictable results, specifically,
`
`incorporating a known method of MMT package in IP data flow of broadcasting (a single MMT package
`
`contained in a single IP data flow) as taught by AOKI into another known method of MMT package in IP
`
`data flow of broadcasting (a single service contained in a single MMT package) as taught by DASDSA to
`
`yield predictable and reasonably successful results, especially when AOKI and DASDSA are in the same
`
`filed of endeavor of MMT broadcasting for services in data flows (KSR MPEP 2143).
`
`Therefore DBSDSA in view of AOKI teaches one-to—one correspondence between IP data
`
`flow and broadcasting service and in other words single IP data flow corresponds to a single
`
`broadcasting service.
`
`Claim Rejections - 35 USC § 1 12
`
`The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
`
`(a) IN GENERAL—The specification shall contain a written description of the
`invention, and of the manner and process of making and using it, in such full, clear, concise,
`and exact terms as to enable any person skilled in the art to which it pertains, or with which it
`is most nearly connected, to make and use the same, and shall set forth the best mode
`contemplated by the inventor orjoint inventor of carrying out the invention.
`
`The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
`
`The specification shall contain a written description of the invention, and of the
`manner and process of making and using it, in such full, clear, concise, and exact terms as to
`enable any person skilled in the art to which it pertains, or with which it is most nearly
`connected, to make and use the same, and shall set forth the best mode contemplated by the
`inventor of carrying out his invention.
`
`The following is a quotation of 35 U.S.C. 112(b):
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 4
`
`(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.
`
`Claims 1, 5 and 9-10 are rejected under 35 U. 8. C. 112jaj or 35 U. 8.C. 112 jpre-AIAj, first
`
`paragraph, as failing to comply with the written description reguirement. The claim(s) contains subject
`
`matter which was not described in the specification in such a way as to reasonably convey to one skilled
`
`in the relevant art that the inventor or ajoint inventor, or for pre-AIA the inventor(s), at the time the
`
`application was filed, had possession of the claimed invention. Claims 1, 5 and 9-10 recite “each of the IP
`
`data flows always respectively stores o_n|\j the corresponding service from among the plurality of
`
`services”. However, the specification lacks the corresponding written description for this. Because for
`
`example, an IP flow could not only contain service information but also indicators, flags, etc. The
`
`specification does not provide support forthe term “only”.
`
`Claims 11 -12 are rejected under 35 US. C. 112jaj or 35 U.8.C. 112 jpre-AIAj, first paragraph, as
`
`failing to comply with the written description requirement. The claim(s) contains subject matter which was
`
`not described in the specification in such a way as to reasonably convey to one skilled in the relevant art
`
`that the inventor or a joint inventor, or for pre-AIA the inventor(s), at the time the application was filed, had
`
`possession of the claimed invention. Claims 11-12 recite “information indicating whether is one service is
`
`stored in the stream”, but however the specification does not provide the corresponding written
`
`description for such indicator which indicates whether there is one service in the stream.
`
`Claims 1, 5 and 9-10 are rejected under 35 U. 8. C. 112jbj or 35 U. BC. 112 jpre-AIAj, 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. Claims 1, 5
`
`and 9-10 recite “each ofthe lP data flows always respectively stores only the corresponding service from
`
`among the plurality of services”. However, it is unclear whetherthis limitation means that a singular data
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 5
`
`flow stores a singular corresponding service or that a data flow does not include anything else rather than
`
`a service. For examining purposes, it is interpreted to be the former.
`
`Claims 1, 5 and 9-10 are rejected under 35 U. 8. C. 112(bj or 35 U. BC. 112 (pre-AIAjz 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. The term
`
`"always" in claims 1, 5 and 9-10 is a relative term which renders the claim indefinite. The term "always" is
`
`not defined by the claim, the specification does not provide a standard for ascertaining the requisite
`
`degree, and one of ordinary skill in the art would not be reasonably apprised of the scope of the invention.
`
`For examining purposes, the relative term “always” gives no patentable weight.
`
`Claims 11 -12 are rejected under 35 U. 8.C. 112(bj or 35 U. 8. C. 112 (pre-AIAj, 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. Claims 11-12 recite
`
`“information indicating whether there is one service is stored in the stream”. It is unclear whether such
`
`limitation means indicating whether there is at least one service in the stream (0 service versus 0+
`
`service), or indicating whether there is a singular service instead of plural services in the stream (1
`
`service versus 1+ services). For examining purposes, it is interpreted to be any of the above.
`
`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 for a claimed invention may not be obtained, notwithstanding that the claimed
`invention is not identically disclosed as set forth in section 102, if the differences between
`the claimed invention and the prior art are such that the claimed invention as a whole
`would have been obvious before the effective filing date of the claimed invention to a
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 6
`
`person having ordinary skill in the art to which the claimed invention pertains.
`Patentability shall not be negated by the manner in which the invention was made.
`
`Claims 1- 12 are reiected under 35 U. 8. C. 103 as being ungatentable over Digital Broadcasting
`
`Systems Development Subcommittee Association of Radio Industries and Business (Interim report on
`
`
`ultra-hi h-definition television broadcastin s stems multi leXin method
`hereinafter DBSDSA in view
`
`of AOKI (A study on Implementation of MM T in Next Generation Broadcasting Systems).
`
`Per claims 1 and 9, DBSDSA teaches “A transmission method comprising: generating a stream
`
`including a plurality of Internet Protocol (IP) data flows (Pg.10, Para.1, In broadcasting, these multiple
`
`IP data flows are multiplexed on one TLV stream. A TLV stream is a series of TLV packets
`
`identified by the TLV stream ID, and contains TLV transmission control signals (TLV-Sis) such as
`
`TLV-NIT (Network Information Table) and AMT (Address Map Table) as TLV packets) corresponding
`
`with a plurality of services in broadcast, each of the IP data flows always respectively stores
`
`the
`
`corresponding service from among the plurality of services; (Pg.54, Para.1; Pg.9, Para.4; Pg.9, last Para.,
`
`Then correspondence between the IP data flow and service ID is made using AMT; While the
`
`content unit is defined as the package in MMT, this package and the service are used with one-to-
`
`one correspondence; As shown in Fig. 3 .1.4, multiple MMT packages can be multiplexed on the
`
`same IP data flow) and transmitting the generated stream in a determined channel” (Pg.9, Fig.3.1.4,
`
`“TLV stream” “Physical channel”; Pg.10, Fig.3.1.5, “TLV stream (Transmission unit in
`
`broadcasting)” “Physical channel”; Pg.7, Last Para.-Pg.8, First Para.; Pg.53, Last Para.-Pg.54, First
`
`Para., TL V-SI is the transmission control signal for multiplexing of IP packets, and it provides the
`
`channel selection information and information on correspondence between IP address and
`
`service; Channel selection by the user is executed by specifying the IP data flow or the service ID.
`
`Then correspondence between the IP data flow and service ID is made using AMT. Next, TL V-NIT
`
`is used to identify the physical channel for the corresponding service ID to execute the channel
`
`selection process).
`
`Moreover, DASDSA discloses “one-to-one” correspondence between broadcasting service and
`
`MMT package in an IP data flow. In addition, DASDSA further discloses multiple MMT packages m
`
`contained in an IP data flow, which seems to imply that a single MMT package or multiple MMT packages
`
`may be contained in an IP data flow and thus “one-to-one” correspondence between broadcasting service
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 7
`
`and IP data flow (broadcasting service-MMT package-IP data flow). However, DASDSA does not
`
`explicitly disclose that a single MMT package or multiple MMT packagesm contained in an IP data
`
`flow and thus does not explicitly teach the “one-to-one” correspondence between broadcasting service
`
`and IP data flow and in other words each lP data flow stores “only” the corresponding service.
`
`In analogous teaching, AOKI explicitly discloses MMT packages (Pg.356, last Para., When a
`
`MMT package is received) in IP data flows for services (Pg.359, Para.2—3, the IP data flow to be
`
`received. The service ID corresponding to the specified IP data flow is identified using AMT... The
`
`IP packet received as described above contains the MMT packets) and multiple packages may be
`
`contained in one IP data flow (Pg.359, Para.4, In broadcasting, multiple packages may be
`
`multiplexed in one IP data flow), which indicates a single package may be contained in one IP data
`
`flow.
`
`Thus, given the teaching of AOKI, it would have been obvious to one of ordinary skill in the art
`
`before the effective filling date of the claimed invention to combine the teaching of a single MMT
`
`package contained in a single IP data flow (one-to—one correspondence between MMT and IP data
`
`flow) of AOKI into a single broadcasting service contained in a single MMT package (one-to-one
`
`correspondence between broadcasting service and MMT package) of DASDSA so that a single
`
`service would be contained in a single IP data flow (one-to-one correspondence between IP data
`
`flow and service). One of ordinary skill in the art would have been motivated to do so because this is
`
`combining prior art elements according to known methods to yield predictable results, specifically,
`
`incorporating a known method of MMT package in IP data flow of broadcasting (a single MMT package
`
`contained in a single IP data flow) as taught by AOKI into another known method of MMT package in IP
`
`data flow of broadcasting (a single service contained in a single MMT package) as taught by DASDSA to
`
`yield predictable and reasonably successful results, especially when AOKI and DASDSA are in the same
`
`filed of endeavor of MMT broadcasting for services in data flows (KSR MPEP 2143).
`
`Per claims 5 and 10, DBSDSA teaches “A reception method comprising: receiving a stream
`
`including a plurality of IP (Internet Protocol) data flows (Pg.10, Para.1, In broadcasting, these multiple
`
`IP data flows are multiplexed on one TLV stream. A TLV stream is a series of TLV packets
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 8
`
`identified by the TLV stream ID, and contains TLV transmission control signals (TLV-Sis) such as
`
`TLV-NIT (Network Information Table) and AMT (Address Map Table) as TLV packets) corresponding
`
`with a plurality of services in broadcast in a determined channel, each of the IP data flows always
`
`respectively stores
`
`the corresponding service from among the plurality of services; (Pg.54, Para.1;
`
`Pg.9, Para.4; Pg.9, last Para., Then correspondence between the IP data flow and service ID is
`
`made using AMT; While the content unit is defined as the package in MMT, this package and the
`
`service are used with one-to-one correspondence; As shown in Fig. 3 .1.4, multiple MMT packages
`
`can be multiplexed on the same IP data flow) and reproducing one of the plurality of services from the
`
`received stream” (Pg.9, Fig.3.1.4, “TLV stream” “Physical channel”; Pg.10, Fig.3.1.5, “TLV stream
`
`(Transmission unit in broadcasting)” “Physical channel”; Pg.7, Last Para.-Pg.8, First Para.; Pg.53,
`
`Last Para.-Pg.54, First Para., TL V-SI is the transmission control signal for multiplexing of IP
`
`packets, and it provides the channel selection information and information on correspondence
`
`between IP address and service; Channel selection by the user is executed by specifying the IP
`
`data flow or the service ID. Then correspondence between the IP data flow and service ID is made
`
`using AMT. Next, TL V-NIT is used to identify the physical channel for the corresponding service
`
`ID to execute the channel selection process).
`
`Moreover, DASDSA discloses “one-to-one” correspondence between broadcasting service and
`
`MMT package in an IP data flow. In addition, DASDSA further discloses multiple MMT packages m
`
`contained in an IP data flow, which seems to imply that a single MMT package or multiple MMT packages
`
`may be contained in an IP data flow and thus “one-to-one” correspondence between broadcasting service
`
`and IP data flow (broadcasting service-MMT package-IP data flow). However, DASDSA does not
`
`explicitly disclose that a single MMT package or multiple MMT packagesm contained in an IP data
`
`flow and thus does not explicitly teach the “one-to-one” correspondence between broadcasting service
`
`and IP data flow and in other words each IP data flow stores “only” the corresponding service.
`
`In analogous teaching, AOKI explicitly discloses MMT packages (Pg.356, last Para., When a
`
`MMT package is received) in IP data flows for services (Pg.359, Para.2—3, the IP data flow to be
`
`received. The service ID corresponding to the specified IP data flow is identified using AMT... The
`
`IP packet received as described above contains the MMT packets) and multiple packages may be
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 9
`
`contained in one IP data flow (Pg.359, Para.4, In broadcasting, multiple packages may be
`
`multiplexed in one IP data flow), which indicates a single package may be contained in one IP data
`
`flow.
`
`Thus, given the teaching of AOKI, it would have been obvious to one of ordinary skill in the art
`
`before the effective filling date of the claimed invention to combine the teaching of a single MMT
`
`package contained in a single IP data flow (one-to-one correspondence between MMT and IP data
`
`flow) of AOKI into a single broadcasting service contained in a single MMT package (one-to-one
`
`correspondence between broadcasting service and MMT package) of DASDSA so that a single
`
`service would be contained in a single IP data flow (one-to-one correspondence between IP data
`
`flow and service). One of ordinary skill in the art would have been motivated to do so because this is
`
`combining prior art elements according to known methods to yield predictable results, specifically,
`
`incorporating a known method of MMT package in IP data flow of broadcasting (a single MMT package
`
`contained in a single IP data flow) as taught by AOKI into another known method of MMT package in IP
`
`data flow of broadcasting (a single service contained in a single MMT package) as taught by DASDSA to
`
`yield predictable and reasonably successful results, especially when AOKI and DASDSA are in the same
`
`filed of endeavor of MMT broadcasting for services in data flows (KSR MPEP 2143).
`
`Per claim 2, DBSDSA furtherteaches “wherein the generated stream includes an IP data flow
`
`different from the plurality of IP data flows, the IP dataflow storing program control information that
`
`indicates correspondence between each of the plurality of services and specification information that
`
`specifies the plurality of IP data flows that stores the plurality of services” (Pg.10, Para.1; Pg.54, Para.1,
`
`In broadcasting, these multiple IP data flows are multiplexed on one TLV stream. A TLV stream is
`
`a series of TLV packets identified by the TLV stream ID, and contains TLV transmission control
`
`signals (TLV-Sis) such as TLV-NIT (Network Information Table) and AMT (Address Map Table) as
`
`TLV packets; Then correspondence between the IP data flow and service ID is made using AMT).
`
`Per claim 6, DBSDSA furtherteaches “wherein the received stream includes an IP data flow
`
`different from the plurality of IP data flows, the IP data flow storing program control information that
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 10
`
`indicates correspondence between each of the plurality of services and specification information that
`
`specifies the plurality of IP data flows that respectively stores the corresponding services of the plurality of
`
`services, (Pg.10, Para.1; Pg.54, Para.1, In broadcasting, these multiple IP data flows are multiplexed
`
`on one TLV stream. A TLV stream is a series of TLV packets identified by the TLV stream ID, and
`
`contains TLV transmission control signals (TLV-Sis) such as TLV-NIT (Network Information Table)
`
`and AMT (Address Map Table) as TLV packets; Then correspondence between the IP data flow
`
`and service ID is made using AMT) and the reception method comprising: specifying the IP data flow
`
`corresponding to the service to be reproduced from the plurality of IP data flows based on the program
`
`control information; and reproducing the service stored in the specified lP data flow” (Pg.53, Fig. A2-1;
`
`Pg.54, Para.1-5, Then correspondence between the IP data flow and service ID is made using AMT.
`
`Next, TLV-NIT is used to identify the physical channel for the corresponding service ID to execute
`
`the channel selection process. As a consequence, the desired IP data flow is output from the front
`
`end section of the broadcasting receiver. The IP packet received as described above contains the
`
`MMTP packets. From here, the MMTP packet with value 0x0000 in the packet_id field of the MMTP
`
`packet header is selected to obtain the PA message and then the MP table from inside the
`
`message...The IP data flow and packet_id to transmit the asset which comprises the contents
`
`(MFU) are identified from general_location_info described on the MP table. At the same time, the
`
`layout number and the MPU presentation time are also identified from the MPU timestamp
`
`descriptor and MPU presentation region specification descriptor. Then the MMTP packet with the
`
`packet_id identified as the asset is selected to obtain the necessary MFU. By presenting the MFU
`
`obtained as shown above at the position of the specified layout number and region number at the
`
`specified presentation time, video signals, and audio signals are presented).
`
`Per claims 3 and 7, DBSDSA further teaches “wherein each of the plurality of services is stored in
`
`an MMT (MPEG Media Transport) packet in the corresponding lP data flow” (Pg.9, Para.4; Pg.9, last
`
`Para., While the content unit is defined as the package in MMT, this package and the service are
`
`used with one-to-one correspondence; As shown in Fig. 3 .1.4, multiple MMT packages can be
`
`multiplexed on the same IP data flow).
`
`

`

`Application/Control Number: 15/437,483
`Art Unit: 2454
`
`Page 11
`
`Per claims 4 and 8, DBSDSA further teaches “wherein each of the IP data flows is stored in a
`
`TLV (Type Length Value) packet” (Pg.10, Para.1, In broadcasting, these multiple IP data flows are
`
`multiplexed on one TLV stream. A TLV stream is a series of TLV packets identified by the TLV
`
`stream ID, and contains TLV transmission control signals (TLV-Sis) such as TLV-NIT (Network
`
`Information Table) and AMT (Address Map Table) as TLV packets)
`
`Per claims 11-12, DASDSA furtherteaches “information indicating whetherthere is one service is
`
`stored in the stream” (Pg.10, Para.1; Pg.54, Para.1, In broadcasting, these multiple IP data flows are
`
`multiplexed on one TLV stream. A TLV stream is a series of TLV packets identified by the TLV
`
`stream ID, and contains TLV transmission control signals (TLV-Sis) such as TLV-NIT (Network
`
`Information Table) and AMT (Address Map Table) as TLV packets; Then correspondence between
`
`the IP data flow and service ID is made using AMT). [A TLV stream contains lP data flows and AMT
`
`indicates which lP data flow contains which service. Therefore AMT indicates that there is one service
`
`stored/included in the stream.]
`
`Conclusion
`
`Applicant's amendment necessitated the new ground(s) of rejection presented in this Office
`
`action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of
`
`the extension of time policy as set forth in 37 CFR 1.136(a).
`
`A shortened statutory period for reply to this final action is set to expire THREE MONTHS from
`
`the mailing date of this action.
`
`In the event a first reply is filed within TWO MONTHS of the mailing date
`
`of this final action and the advisory action is not mailed until after the end of the THREE-MONTH
`
`shortened statutory period, then the shortened statutory period will expire on the date the advisory action
`
`is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of
`
`the advisory action.
`
`In no event, however, will the statutory period for reply expire later than SIX
`
`MONTHS from the date of this final action.
`
`