DETAILED ACTION
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 .
Priority
Receipt is acknowledged of papers submitted under 35 U.S.C 119(a)-(d), which papers have been placed of record in the file.
Information Disclosure Statement
The references listed in the Information Disclosure Statement filed on September 18, 2025 and June 09, 2026 has been considered by the examiner (see attached PTO-1449 form).
Claim Rejections - 35 USC § 102
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 (i.e., changing from AIA to pre-AIA ) 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 the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-5 and 11-15 are rejected under 35 U.S.C. 102(a1) as being anticipated by Park et al. (U.S. Pub. No. 2021/0014541).
Regarding claim 1, Park et al. discloses a method of processing media data, comprising:
generating media data (see abstract; a method of transmitting a broadcast signal according to embodiments including generating service data, see fig. 1 (1000-1030) shows input formatting, BICM, frame building, and OFDM generation, which together constitute media data generation);
generating a service list related to the media data (see figs. 8-15, 19-20, 29-30. Figs. 8-15 discloses generating ServiceDiscoveryListTable (SDLT)); and
transmitting the media data and the service list based on a network (see fig. 1, shows Tx Signal Output transmitted via antennas, fig. 10 shows transmitting SDLT from broadband server: “Respond with service display list…”, figs. 19, 29).
Regarding claim 11, Park et al. discloses an apparatus for processing media data, comprising:
a server storing media data (see abstract; fig. 1 (1000-1030), fig. 29 shows broadband server hosting media content: https://bbl.com/KBSsports33-7.mpd);
a server storing a service list related to the media data (see figs. 8-15, stores ServiceDiscoveryListTable (SDLT), see fig. 10, fig. 19 shows SDLT stored and served by a broadband server “<Service@serviceId=0x2107/>…”, see fig. 29 shows USBD and MPD stored on the server); and
a processor configured to transmit the media data and the service list based on a network (see fig. 1 shows Tx Signal Output transmitting media data, see fig. 10, 19, 29).
Regarding claim 12, claim 12 is rejected for the same reason set forth in the rejection of claim 1.
Regarding claim 14, claim 14 is rejected for the same reason set forth in the rejection of claim 1.
Regarding claims 2, 13 and 15, Park et al. discloses everything claimed as applied above (see claims 1, 12 and 14). Park et al. discloses receiving a query for discovery of the service list from a client (see fig. 7 (700 – SDLT Request to Broadband Server), fig. 9, fig. 18 (steps 18001-18003));
transmitting an entry point for the service list in response to the query (see fig. 18 “<SdltlnetUrl @urllType=1> http://aaa.bbb.com/ <SdltnetUrl>” – this is the entry point for retrieving the service list. See fig. 10 and 19);
receiving a request for the service list (see fig. 18 (step 3 “https://aaa.bbb.com/0x2107/ALL”) the client requests the service list using the entry-point URL. See fig. 19 (step 5)); and
transmitting the service list in response to the request (see fig. 10 (step 3 “Respond with service display list including all of terrestrial, cable, satellite, and Internet services), see fig. 19 (the server transmits SDLT containing <Service@serviceId=0x2107/> and <SdltInetUrl>)),
wherein the service list is related to an internet-based broadcasting service (see fig. 10 (step 3 – display list including all of terrestrial, cable, satellite, and Internet services), see fig. 19, 29).
Regarding claim 3, Park et al. discloses everything claimed as applied above (see claim 2). Park et al. discloses wherein a service for 5G multicast streaming (5GMS) is selected based on the service list (see fig. 3 (shows DVB-I integrating 5G delivery paths), see fig. 10 shows the receiver selecting among Internet-based services from the SDLT. 5GMS is an Internet-based broadcast/multicast service, so it falls within the same category).
Regarding claim 4, Park et al. discloses everything claimed as applied above (see claim 3). Park et al. discloses wherein the service list comprises a service instance, the service instance comprising DASH delivery parameter information (see figs. 20, 26, 29),
wherein the DASH delivery parameter information comprises information related to a unicast-based DASH service (see figs. 26, 29).
Regarding claim 5, Park et al. discloses everything claimed as applied above (see claim 4). Park et al. discloses wherein the service for the 5GMS is requested based on the service instance (see fig. 29 shows a User Service Description (USD) (the DVB-I service instance) containing: “@MediaPresentationDescription = http://bbl.com/KBSsports33-7.mpd, see fig. 19 (steps 4 and 5), see fig. 3).
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 (i.e., changing from AIA to pre-AIA ) 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 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 6-10 are rejected under 35 U.S.C. 103 as being unpatentable over Park et al. as applied to claim 5 above, and further in view of Blatek et al. (U.S. Pub. No. 2024/0137596).
Regarding claim 6, Park et al. discloses everything claimed as applied above (see claim 5). Park et al. discloses wherein the DASH delivery parameter information comprises 5GMS host name information (see fig. 29 MPD excerpt: “<BaseURL>http://bb1.com/33-7/sports/</BaseURL>”. The host name is bb1.com. and see fig. 18) and session-identifier-based service access (see fig. 29, fig. 19 (step 5), see fig. 18 (step 3), fig. 3).
However, Park et al. is silent as to provisioning session ID information for service access supporting the 5GMS.
Blatek et al. discloses provisioning session ID information for service access supporting the 5GMS (see paragraph 0023; describes personalization using UUIDs, profile IDs, and group IDs, fig. 3a, 3c).
It would have been obvious to a skilled artisan before the effective filing date of the claimed invention to modify the system of Park et al. with the teachings of Blatek et al., the motivation being to access personalized services.
Regarding claim 7, Park et al. and Blatek et al. discloses everything claimed as applied above (see claim 6). Park et al. discloses wherein the DASH delivery type information comprises delivery type information for the 5GMS (see fig. 29 MPD excerpts ”<BaseURL>http://bb1.com/33-7/sports/</BaseURL>”. This is DASH delivery type information, fig. 3),
wherein the delivery type information for the 5GMS comprises the 5GMS host name information and provisioning session ID information (see fig. 29 MPD excerpt: http://bb1.com/... Host name is bb1.com), figs. 18, 19, 29).
Blatek et al. discloses wherein the provisioning session ID information references a provisioning session ID related to 3GPP (see paragraph 0023, figs. 3a, 3c).
Regarding claim 8, Park et al. discloses everything claimed as applied above (see claim 5). Park et al. discloses wherein the DASH delivery parameter information comprises a 5GMS delivery parameter (see fig. 29 MPD excerpts ”<BaseURL>http://bb1.com/33-7/sports/</BaseURL>”, fig. 3), the 5GMS delivery parameter being defined as a URI value (see fig. 29 MPD excerpt: http://bb1.com/33-7/sports/” – a URI value; fig. 18), and
wherein the URI value comprises a 5GMS host name (see fig. 29, 18).
However, Park et al. is silent as to wherein the provisioning session ID information references a provisioning session ID related to 3GPP.
Blatek et al. discloses wherein the provisioning session ID information references a provisioning session ID related to 3GPP (see paragraph 0023, figs. 3a, 3c).
It would have been obvious to a skilled artisan before the effective filing date of the claimed invention to modify the system of Park et al. with the teachings of Blatek et al., the motivation being to access personalized services.
Regarding claim 9, Park et al. discloses everything claimed as applied above (see claim 5). Park et al. discloses wherein the DASH delivery parameter information comprises a 5GMS delivery parameter in a sequence form (see fig. 29 USBD excerpt shows a sequence of DASH parameter: “<UnicastAppService> <BasePattern>http://bb1.com/33-7/sports/</BasePttern> </UnicastAppService>”, see fig. 26, fig. 3),
the 5GMS delivery parameter comprises 5GMS host name information (see fig. 29 MPD excerpt: Host name = bb1.com, fig. 29 USBD excerpts: Host name = bbl.com, fig. 18 Host name = aaa.bbb.com).
However, Park et al. is silent as to provisioning session ID information, the provisioning session ID information referencing a provisioning session ID related to 3GPP.
Blatek et al. discloses provisioning session ID information, the provisioning session ID information referencing a provisioning session ID related to 3GPP (see paragraph 0023, fig. 3a, 3c shows UUID#1, UUID#2, UUID#N used to generate personalized linear channels).
It would have been obvious to a skilled artisan before the effective filing date of the claimed invention to modify the system of Park et al. with the teachings of Blatek et al., the motivation being to access personalized services.
Regarding claim 10, Park et al. discloses everything claimed as applied above (see claim 5). Park et al. discloses wherein a sequence of the DASH delivery parameter information contains a 5GMS delivery parameter (see fig. 29 USBD excerpt shows a sequence of DASH parameters: “<UnicastAppService> <BasePattern>http://bb1.com/33-7/sports/</BasePttern> </UnicastAppService>. This is a sequence form (element, sub-element, string). Fig. 26 defines UserServiceDescription containing multiple sequential fields (serviced, globalServiceId, MediaPresentationDescription, DeliveryMethod, etc.),
wherein the DASH delivery parameter information comprises 5GMS host name information (see fig. 29 MPD excerpt: Host name = bb1.com, fig. 29 USBD excerpts: Host name = bbl.com, fig. 18 Host name = aaa.bbb.com).
However, Park et al. is silent as to provisioning session ID information, the provisioning session ID information referencing a provisioning session ID related to 3GPP.
Blatek et al. discloses provisioning session ID information, the provisioning session ID information referencing a provisioning session ID related to 3GPP (see paragraph 0023, fig. 3a, 3c shows UUID#1, UUID#2, UUID#N used to generate personalized linear channels).
It would have been obvious to a skilled artisan before the effective filing date of the claimed invention to modify the system of Park et al. with the teachings of Blatek et al., the motivation being to access personalized services.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NNENNA NGOZI EKPO whose telephone number is (571)270-1663. The examiner can normally be reached M-W 10:00am - 6:30pm, TH-F 8:00am - 4:30pm.
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, Brian Pendleton can be reached at 571-272-7527. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
NNENNA EKPO
Primary Examiner
Art Unit 2425
/NNENNA N EKPO/Primary Examiner, Art Unit 2425 June 23, 2026.
Prosecution Insights