DETAILED ACTION
This communication is in response to Application No. 18/561,224 filed on 11/15/2023. The amendment presented on 7/29/2026, which amends claims 73, 81, and 84, is hereby acknowledged. Claims 64-84 have been examined.
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 .
Claim Rejections - 35 USC § 112
The amendment presented on 7/29/2026 amending claims 73 and 84 obviates the outstanding 35 USC 112 rejections, and they are hereby withdrawn.
Claim Rejections - 35 USC § 103
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 64-65, 72-74, and 83-84 are rejected under 35 U.S.C. 103 as being unpatentable over Xu et al. (hereinafter Xu)(US 2020/0304958) in view of Hou et al. (hereinafter Hou)(US 2018/0146362).
Regarding claims 64 and 72, Xu teaches as follows:
An edge orchestrator (interpreted as the broadcast multicast service center (hereinafter BM-SC) apparatus 30 may be a service center, such as BM-SC 114 in figures 2-4, see, ¶ [0093] and figure 6c) configured to operate in an edge computing system, the edge orchestrator comprising:
a processor (apparatus 30 includes a processor 42 for processing information and executing instructions or operations. Processor 42 may be any type of general or specific purpose processor, see, ¶ [0094] and figure 6c);
a memory storing instructions that, when executed by the processor, cause the edge orchestrator to (apparatus 30 may further include or be coupled to a memory 44, which may be coupled to processor 42, for storing information and instructions that may be executed by processor 42… The instructions stored in memory 44 may include program instructions or computer program code that, when executed by processor 42, enable the apparatus 30 to perform tasks as described herein, see, ¶ [0095] and figure 6c):
receive, from an application server (interpreted as the intelligent transport system station (ITS-S/RSU) 120 in figure 4)(an application server (e.g., ITS-S/RSU 120) may initiate an activate MBMS bearer procedure including the use of a local MBMS distribution path, see, ¶ [0060]) that hosts a central application (the application server may send the downlink data to the LME 105, which is then sent to the eNB 101 as MBMS data, see, ¶ [0062]), a first request for performing an Multimedia Broadcast/Multicast Service (MBMS) service management procedure for the central application (at 5, the ITS-S/RSU 120 may initiate an activation MBMS bearer request procedure that includes sending an activate MBMS bearer request message (equivalent to applicant’s first request) to the BM-SC 114, see, ¶ [0068] and figure 4);
process the first request; and transmit, to the application server, a first response indicating whether the MBMS service management procedure was successfully performed, wherein the first response is at least partially based on a result of the processing (the BM-SC 114 may reply, at 6, with an activate MBMS bearer response message, see, ¶ [0068] and figure 4)(the activate MBMS bearer request message is inherently processed and succeeded before the activate MBMS bearer response message was sent back).
Xu does not explicitly teach the edge computing system.
Hou teaches as follows:
With development of distributed cloud computing technologies, a mobile network edge is capable of providing a cloud computing service. In this context, a low-latency feature of an edge multimedia service (equivalent to applicant’s edge computing system) is to bring users brand new Internet use experience (see, ¶ [0024]); and
in an MBMS service data transmission system in this example, an edge BM-SC and an MBMS GW are deployed on a network edge (equivalent to applicant’s edge computing system), and a central BM-SC is deployed on a core network (see, ¶ [0027] and figure 2).
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the claimed invention to modify Xu with Hou to include the edge multimedia service as taught by Hou in order to efficiently provide low-latency feature of the edge multimedia service.
Regarding claims 65 and 74, Xu teaches as follows:
Before receiving the first request:
transmitting, to each of one or more edge nodes that host an MBMS support service, a second request (interpreted as the local distribution request message) for provisioning a configuration at the corresponding edge node for localized MBMS (at 3, the ITS-S/RSU 120 may initiate a local distribution request procedure that includes sending a local distribution request message to the Local MBMS Entity (LME) 105, see, ¶ [0066] and figure 4); and
receiving, from each of the one or more edge nodes, a second response (interpreted as the local distribution response message) indicating whether the configuration is successfully provisioned at the corresponding edge node (at 4, the LME 105 may reply with a local distribution response message that includes a list of the IP address(es)/port(s) in the LME 105 for receiving data, and the associated information of local MBMS distribution, such as IP Source Address, and IP Multicast Address in the LME 105 for IP multicast distribution, see, ¶ [0067] and figure 4).
Regarding claims 73 and 84, Xu in view of Hou teaches similar limitations as presented above in the rejection for claims 64 and 72.
Regarding claim 83, Xu teaches as follows:
Forwarding a message from a user equipment (UE) via the edge application to the BM-SC for multicasting or broadcasting (the source UE 102 may use the L-GW 104 to send the data to ITS-S/RSU 120 via the local breakout path, see, ¶[0063] and figure 2).
Claims 66-71 and 75-80 are rejected under 35 U.S.C. 103 as being unpatentable over Xu et al. (hereinafter Xu)(US 2020/0304958) in view of Hou et al. (hereinafter Hou)(US 2018/0146362), and further in view of Zhu (US 2021/0029775).
Regarding claims 66 and 75, Xu in view of Hou teaches all limitations as presented above except for the xMB interface.
Zhu teaches as follows:
The BM-SC provides a service and a capability supported by the BM-SC for the SCEF by using an xMB interface. The BM-SC 240 supports provision and delivery of an MBMS user service, and is configured to serve as an entry point for a content provider MBMS to perform transmission, to authorize and initiate an MBMS bearer service, and arrange and transmit MBMS data (see, ¶ [0121]).
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the claimed invention to modify Xu in view of Hou with Zhu to include the well-known xMB interface as taught by Zhu in order to efficiently provide a MBMS bearer service and transmit MBMS data.
Regarding claims 67 and 80, Xu teaches as follows:
Wherein the first request is a request for creating an MBMS user service (the MBMS feature is divided into the MBMS bearer service and the MBMS user service… The MBMS user service is the MBMS service layer and may provide a streaming and a download delivery method, see, ¶ [0044]) and comprises an identifier of the central application (interpreted as the IP source address)(at 4, the LME 105 may reply with a local distribution response message that includes a list of the IP address(es)/port(s) in the LME 105 for receiving data, and the associated information of local MBMS distribution, such as IP Source Address, and IP Multicast Address in the LME 105 for IP multicast distribution, see, [0067]); and
the first response comprises an identifier of a resource assigned to the MBMS user service (at 7, the BM-SC 114 may initiate a MBMS session start procedure that includes sending a MBMS session start request message, which includes the information of local MBMS distribution, see, ¶ [0069]).
Regarding claim 68, Xu teaches as follows:
Next, at 7, the BM-SC 114 may initiate a MBMS session start procedure (equivalent to applicant’s third request creating the MBMS user service) that includes sending a MBMS session start request message, which includes the information of local MBMS distribution, to the MME/MBMS-GW 111... The MBMS-GW 111 may use the received local MBMS distribution information in the MBMS session start request message, and send it to the MME, which at 8 is forwarded to eNB/MCE 101. At 9, the eNB may join the IP Multicast group, which is one of the groups in the LME. The BM-SC 114 may initiate a MBMS service announcement at 10. In an embodiment, at 11, the ITS-S/RSU 120 may send the data to the LME 105 based on the LME's IP address/port received in step 4. Once the LME 105 receive the data in the specific IP address/port, the LME 105 may then forward the data to the associated IP multicast distribution path (see, ¶ [0069]-[0070] and figure 4).
Xu in view of Hou teaches all limitations as presented above except for the xMB interface.
Zhu teaches as follows:
The BM-SC provides a service and a capability supported by the BM-SC for the SCEF by using an xMB interface. The BM-SC 240 supports provision and delivery of an MBMS user service, and is configured to serve as an entry point for a content provider MBMS to perform transmission, to authorize and initiate an MBMS bearer service, and arrange and transmit MBMS data (see, ¶ [0121]).
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the claimed invention to modify Xu in view of Hou with Zhu to include the well-known xMB interface as taught by Zhu in order to efficiently provide a MBMS bearer service and transmit MBMS data.
Regarding claim 69, Xu in view of Hou and Zhu teaches similar limitations as presented above and Xu further teaches the service name as follows:
The ITS-S/RSU 120 may be preconfigured with LME information, such as fully qualified domain name (FQDN)(equivalent to applicant’s service name) or an IP address for each location (see, ¶ [0066]).
Therefore, the fully qualified domain name (FQDN) is inherently exchanged during the communications.
Regarding claims 70, 77, and 79, Xu teaches as follows:
Selecting at least one of the one or more edge nodes (interpreted as LME 105 in figure 4) that host the MBMS support service, based at least partially on the respective serving areas of the one or more edge nodes (the activate MBMS bearer request message may comprise at least one of information on local MBMS distribution received from a local MBMS entity (LME), or a destination area, or a destination area and an indication that preferred delivery is via local distribution, see, ¶ [0018]);
transmitting, to each of the selected edge nodes, a fourth request for notifying information for the MBMS user service; and receiving, from each of the selected edge nodes, a fourth response acknowledging the fourth request (at 3, the ITS-S/RSU 120 may initiate a local distribution request procedure that includes sending a local distribution request message to the LME 105. In an embodiment, the local distribution request message may include the TMGI(s) as an identifier. According to an embodiment, at 4, the LME 105 may reply with a local distribution response message that includes a list of the IP address(es)/port(s) in the LME 105 for receiving data, and the associated information of local MBMS distribution, such as IP Source Address, and IP Multicast Address in the LME 105 for IP multicast distribution, see, ¶ [0066]-[0067] and figure 4).
Regarding claim 71, Xu in view of Hou and Zhu teaches similar limitations as presented in the rejections for claims 67 and 69-70.
Therefore, it is rejected for similar reason as presented above.
Regarding claims 76 and 78, Xu in view of Hou and Zhu teaches all limitations as presented above and Xu further teaches the MBMS session start procedure as follows:
At 5, the BM-SC 114 may initiate a MBMS session start procedure by sending a MBMS session start request message to MBMS-GW 111. The MBMS session start request message may include the information of local MBMS distribution. Upon the reception of the information of local MBMS distribution, the MBMS-GW 111 may skip the normal processing for IP multicast distribution, e.g., allocate an IP multicast address. The MBMS-GW 111 may use the received local MBMS distribution information in the MBMS session start request message, and send it to the MME, which in turn is forwarded at 6 to the eNB/MCE 101 (see, ¶[0074] and figure 5).
Therefore, they are rejected for similar reason as presented above.
Claims 81-82 are rejected under 35 U.S.C. 103 as being unpatentable over Xu et al. (hereinafter Xu)(US 2020/0304958) in view of Hou et al. (hereinafter Hou)(US 2018/0146362) and Zhu (US 2021/0029775), and further in view of Lee et al. (hereinafter Lee)(US 2005/0255836).
Regarding claim 81, Xu in view of Hou and Zhu teaches all limitations as presented above except for subscribing MBMS user service change notification.
Lee teaches as follows:
If the notification indicator includes the MBMS service ID to which the UE has subscribed to and indicates the modification of the MCCH information for the service, the UE identifies it as the notification indicator indicating the MBMS service to which the UE has subscribed (see, ¶[0073]).
Therefore, it would have been obvious for one of ordinary skill in the art before the effective filing date of the claimed invention to modify Xu in view of Hou and Zhu with Lee to include the notification indicator as taught by Lee in order to efficiently indicate the modification of the MBMS service for the UE subscribed for the MBMS service.
Regarding claim 82, Xu teaches similar limitations as presented above in the rejection for claim 67.
Therefore, it is rejected for similar reason as presented above.
Response to Arguments
Applicant's arguments filed 10/2/2020 have been fully considered but they are not persuasive.
Summary of Applicant’s Arguments
In the remarks the applicant argues as follows:
1) Xu discloses that an application server in communication with a BM-SC entity transmits an activate MBMS bearer request message containing the information of the LME and the BM-SC responds with an activate MBMS bearer response message. Though Xu discloses application server sending a bearer request message to BM-SC, Xu does not disclose any edge computing system or the BM-SC (edge orchestrator) being part of the edge computing system.
2) Xu does not disclose any xMB interface used to process the MBMS bearer
request message.
Response to Arguments:
In response to applicant's argument 1), Xu does not explicitly teach the edge computing system. Hou teaches the edge computing system as follows:
With development of distributed cloud computing technologies, a mobile network edge is capable of providing a cloud computing service. In this context, a low-latency feature of an edge multimedia service (equivalent to applicant’s edge computing system) is to bring users brand new Internet use experience (see, ¶ [0024]); and
in an MBMS service data transmission system in this example, an edge BM-SC and an MBMS GW are deployed on a network edge (equivalent to applicant’s edge computing system), and a central BM-SC is deployed on a core network (see, ¶ [0027] and figure 2).
In response to applicant's argument 2), Xu in view of Hou does not teach the well-known xMB interface.
Zhu teaches as follows:
The BM-SC provides a service and a capability supported by the BM-SC for the SCEF by using an xMB interface. The BM-SC 240 supports provision and delivery of an MBMS user service, and is configured to serve as an entry point for a content provider MBMS to perform transmission, to authorize and initiate an MBMS bearer service, and arrange and transmit MBMS data (see, ¶ [0121]).
Therefore, Xu in view of Hou and Zhu teaches the argued limitation.
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 nonprovisional extension fee (37 CFR 1.17(a)) 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 mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Jeong S Park whose telephone number is (571)270-1597. The examiner can normally be reached Monday through Friday 8:00-4:30 ET.
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, Rebecca E Song can be reached at 571-270-3667. 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.
/JEONG S PARK/Primary Examiner, Art Unit 2417
October 2, 2026
Prosecution Insights