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 .
This is in response to the amendment filed 06/23/2025. Claims 1-20 are pending and presented for examination.
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 1-20 are rejected under 35 U.S.C. 103 as being unpatentable over Li et al. US-20230345310-A1 (hereinafter “Li”), in view of Saily et al US-20210378053-A1 (hereinafter “Saily”).
As to claim 1:
Li1 discloses:
A method for wireless communication, comprising: receiving, by a base station, a message from a communication node in a core network, wherein the message includes an identifier identifying a multicast or broadcast service that is authorized for a mobile device to receive data; “AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li “after determining that the UE is authorized to use multicast/broadcast service. AMF 203 sends MBS session establishment message or update request message to the selected MB-SMF 208 depending on whether the MBS session exists” [0156, 0160] Li
receiving, by the base station, a request from the communication node to establish a multicast or broadcast session for the multicast or broadcast service, wherein the request includes an identifier identifying the multicast or broadcast service and a quality of service profile of the multicast or broadcast session; “after determining that the UE is authorized to use multicast/broadcast service. AMF 203 sends MBS session establishment message or update request message to the selected MB-SMF 208 depending on whether the MBS session exists, the request may include the information such as UE ID, session ID, QoS flow ID and corresponding QoS information (e.g., 5G QoS Indicator (5QI), QoS requirements such as maximum data rate per QoS flow or per MBS session, maximum latency, or error rate ” [0156, 0160] “AMF 203 also sends a N2 message to RAN node 202 including a NAS message (switch response) that may be forwarded to UE 201 by the RAN node 202. The N2 message includes UE ID, unicast session ID and corresponding session context information, QoS profile, UPF address/ID, MBS session ID with TMGI or multicast IP address, time instant that switch starts” [0244] Li
transmitting, by the base station, a message to the mobile device that is authorized to receive the data for the multicast or broadcast service, the message indicating a resource configuration for the multicast or broadcast session, wherein the resource configuration is determined in part based on the quality of service profile associated with the multicast or broadcast session; and
“the RAN node 202 is able the configure radio resource within access network for data transfer to UE 201 to meet the QoS requirement” [0172] Li
“RAN node 202 sends an RRC message to UE 201 including the NAS message carrying the delivery mode switch response from AMF 203” [0175] Li
transmitting, by the base station, the data for the multicast or broadcast service using a resource configured according to the resource configuration. “RAN node 202 may send the multicast data to one or more UEs within its cell using the radio resource.” [0175] Li
Li does not appear to explicitly disclose “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state”.
However, Saily discloses “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state” (See Saily ¶ 0056 and ¶67 ; discloses deciding how to configure a mobile device to receive multicast data or service according to the mobile device state; the mobile device will receive multicast data via multicast (point to multipoint) if the mobile is in inactive or idle mode; Also, the mobile can receive multicast data via unicast (point to point) if the mobile is in active mode). It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, having the teachings of Li and Saily before him or her, to modify the invention of Kim to decide how to deliver multicast data to a mobile based on determining whether the mobile in idle state or active state. The suggestion for doing so would have been to solve challenges that may exist in providing multicast data transmission to mobile low activity UEs, e.g., as the UEs change location (move between cells) and/or change state (¶ 0052).
As to claim 2:
The combination of Li and Saily discloses:
The method of claim 1, wherein the resource configuration s further based on the quality of service profile associated with the multicast or broadcast session.
(see Li ¶s 0156, 0160) after determining that the UE is authorized to use multicast/broadcast service. AMF 203 sends MBS session establishment message or update request message to the selected MB-SMF 208 depending on whether the MBS session exists, the request may include the information such as UE ID, session ID, QoS flow ID and corresponding QoS information (e.g., 5G QoS Indicator (5QI), QoS requirements such as maximum data rate per QoS flow or per MBS session, maximum latency, or error rate ”; (Also see Saily ¶ 0041 and 110).
As to claim 3:
Li1 discloses:
The method of claim 1, when the mobile device is in an the idle state, a context of the mobile device is released by the base station, wherein the context includes the identifier identifying the multicast or broadcast service that is authorized for the mobile device to receive data; (See Li ¶ 170 and Saily ¶ 0041 and 0050)
As to claim 4:
Li discloses:
The method of claim 1, wherein the resource configuration is determined further based on a number of mobile devices that are interested in accessing the multicast or broadcast service.
“In an example, the core network function finds that the number of UEs receiving the same data content via respective unicast session exceeds a threshold number and decides to start the multicast data transfer for more efficient network resource usage.” [0134] Li
“the content provider finds that the number of users receiving data on the multicast session decreases, and it becomes less efficient to continue multicast from resource management aspect” [0216] Li
As to claim 5:
LI discloses:
The method of claim 1, wherein the identifier identifying the multicast or broadcast service is a Temporary Mobile Group Identity (TMGI).
“AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li
“The information may include … TMGI to identify the multicast group.” [0170] Li
As to claim 6:
Li discloses:
A method for wireless communication, comprising:
transmitting, by a mobile device, a request to access a multicast or broadcast service, wherein the request is configured to cause the mobile device to be authorized to receive data for the multicast or broadcast service;
“AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li
“The information may include … TMGI to identify the multicast group.” [0170] Li
receiving, at the mobile device, a message indicating a resource configuration for a multicast or broadcast session of the multicast or broadcast service, wherein the resource configuration is determined; and
“AMF 203 also sends a N2 message to RAN node 202 including a NAS message (switch response) that may be forwarded to UE 201 by the RAN node 202. The N2 message includes UE ID, unicast session ID and corresponding session context information, QoS profile, UPF address/ID, MBS session ID with TMGI or multicast IP address, time instant that switch starts” [0244] Li
receiving, at the mobile device, the data for the multicast or broadcast service using a resource configured according to the resource configuration.
“RAN node 202 may send the multicast data to one or more UEs within its cell using the radio resource.” [0175] Li
Li1 does not appear to explicitly disclose “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state”.
However, Saily discloses “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state” (See Saily ¶ 0056 and ¶67 ; discloses deciding how to configure a mobile device to receive multicast data or service according to the mobile device state; the mobile device will receive multicast data via multicast (point to multipoint) if the mobile is in inactive or idle mode; Also, the mobile can receive multicast data via unicast (point to point) if the mobile is in active mode). It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, having the teachings of Li and Saily before him or her, to modify the invention of Kim to decide how to deliver multicast data to a mobile based on determining whether the mobile in idle state or active state. The suggestion for doing so would have been to solve challenges that may exist in providing multicast data transmission to mobile low activity UEs, e.g., as the UEs change location (move between cells) and/or change state (¶ 0052).
As to claim 7:
The combination of Li and Saily discloses:
The method of claim 1, wherein the resource configuration s further based on the quality of service profile associated with the multicast or broadcast session.
(see Li ¶s 0156, 0160) after determining that the UE is authorized to use multicast/broadcast service. AMF 203 sends MBS session establishment message or update request message to the selected MB-SMF 208 depending on whether the MBS session exists, the request may include the information such as UE ID, session ID, QoS flow ID and corresponding QoS information (e.g., 5G QoS Indicator (5QI), QoS requirements such as maximum data rate per QoS flow or per MBS session, maximum latency, or error rate ”; (Also see Saily ¶ 0041 and 110).
As to claim 8:
The combination of Li and Saily discloses:
The method of claim 1, when the mobile device is in an the idle state, a context of the mobile device is released by radio access network (RAN), wherein the context includes identifier identifying the multicast or broadcast service that is authorized for the mobile device to receive data; (See Li ¶ 170 and Saily ¶ 0041 and 0050)
As to claim 9:
Li1 discloses:
The method of claim 6, wherein the resource configuration is further determined based on a number of mobile devices that are interested in accessing the multicast or broadcast service.
“In an example, the core network function finds that the number of UEs receiving the same data content via respective unicast session exceeds a threshold number and decides to start the multicast data transfer for more efficient network resource usage.” [0134] Li1
As to claim 10:
Li discloses:
The method of claim 6, wherein the multicast or broadcast service is associated with a Temporary Mobile Group Identity (TMGI) that identifies the multicast or broadcast service.
“AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li
“The information may include … TMGI to identify the multicast group.” [0170] Li
As to claim 11:
Li discloses:
An apparatus for wireless communication comprising a processor and a memory storing instructions, execution of which by the processor causes the apparatus to:
See FIG. 1B Li
receive a message from a communication node in a core network, wherein the message includes an identifier identifying a multicast or broadcast service that is authorized for a mobile device to receive data;
“AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li
“The information may include … TMGI to identify the multicast group.” [0170] Li
receive a request from the communication node to establish a multicast or broadcast session for the multicast or broadcast service, wherein the request includes an identifier identifying the multicast or broadcast service and a quality of service profile of the multicast or broadcast session;
“AMF 203 also sends a N2 message to RAN node 202 including a NAS message (switch response) that may be forwarded to UE 201 by the RAN node 202. The N2 message includes UE ID, unicast session ID and corresponding session context information, QoS profile, UPF address/ID, MBS session ID with TMGI or multicast IP address, time instant that switch starts” [0244] Li
transmit a message to the mobile device that is authorized to receive the data for the multicast or broadcast service, the message indicating a resource configuration for the multicast or broadcast session, wherein the resource configuration is determined; and
“the RAN node 202 is able the configure radio resource within access network for data transfer to UE 201 to meet the QoS requirement” [0172] Li
“RAN node 202 sends an RRC message to UE 201 including the NAS message carrying the delivery mode switch response from AMF 203” [0175] Li
transmit the data for the multicast or broadcast service using a resource configured according to the resource configuration.
“RAN node 202 may send the multicast data to one or more UEs within its cell using the radio resource.” [0175] Li
Li1 does not appear to explicitly disclose “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state”.
However, Saily discloses “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state” (See Saily ¶ 0056 and ¶67 ; discloses deciding how to configure a mobile device to receive multicast data or service according to the mobile device state; the mobile device will receive multicast data via multicast (point to multipoint) if the mobile is in inactive or idle mode; Also, the mobile can receive multicast data via unicast (point to point) if the mobile is in active mode). It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, having the teachings of Li and Saily before him or her, to modify the invention of Kim to decide how to deliver multicast data to a mobile based on determining whether the mobile in idle state or active state. The suggestion for doing so would have been to solve challenges that may exist in providing multicast data transmission to mobile low activity UEs, e.g., as the UEs change location (move between cells) and/or change state (¶ 0052).
As to claim 12:
The combination of Li and Saily discloses:
The method of claim 11, is further based on a quality of service profile associated with the multicast or broadcast session, wherein a context includes the identifier identifying the multicast or broadcast service that is authorized for the apparatus to receive data.
(see Li ¶s 0156, 0160) after determining that the UE is authorized to use multicast/broadcast service. AMF 203 sends MBS session establishment message or update request message to the selected MB-SMF 208 depending on whether the MBS session exists, the request may include the information such as UE ID, session ID, QoS flow ID and corresponding QoS information (e.g., 5G QoS Indicator (5QI), QoS requirements such as maximum data rate per QoS flow or per MBS session, maximum latency, or error rate ”; (Also see Saily ¶ 0041 and 110).
As to claim 13:
The combination of Li and Saily discloses:
The method of claim 1, when the mobile device is in an the idle state, a context of the mobile device is released by radio access network (RAN); (See Li ¶ 170 and Saily ¶ 0041 and 0050)
As to claim 14:
Li discloses:
The apparatus of claim 11, wherein the resource configuration is determined further based on a number of mobile devices that are interested in accessing the multicast or broadcast service.
“In an example, the core network function finds that the number of UEs receiving the same data content via respective unicast session exceeds a threshold number and decides to start the multicast data transfer for more efficient network resource usage.” [0134] Li
As to claim 15:
Li discloses:
The apparatus of claim 11, wherein the identifier identifying the multicast or broadcast service is a Temporary Mobile Group Identity (TMGI).
“AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li
“The information may include … TMGI to identify the multicast group.” [0170] Li
As to claim 16:
Li discloses:
An apparatus for wireless communication comprising a processor and a memory storing instructions, execution of which by the processor causes the apparatus to:
See FIG. 1B Li
transmit a request to access a multicast or broadcast service, wherein the request is configured to cause the apparatus to be authorized to receive data for the multicast or broadcast service;
“AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li
“The information may include … TMGI to identify the multicast group.” [0170] Li
receive a message indicating a resource configuration for a multicast or broadcast session of the multicast or broadcast service, wherein the resource configuration is determined; and
“the RAN node 202 is able the configure radio resource within access network for data transfer to UE 201 to meet the QoS requirement” [0172] Li
“RAN node 202 sends an RRC message to UE 201 including the NAS message carrying the delivery mode switch response from AMF 203” [0175] Li
receive the data for the multicast or broadcast service using a resource configured according to the resource configuration.
“RAN node 202 may send the multicast data to one or more UEs within its cell using the radio resource.” [0175] Li
Li1 does not appear to explicitly disclose “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state”.
However, Saily discloses “wherein the resource configuration is determined according to whether the mobile device is in a connected state or in an idle state such that a point-to-point resource configuration is used when the mobile device is in a connected state and a point-to-multipoint configuration is used when the mobile device is in an idle state” (See Saily ¶ 0056 and ¶67 ; discloses deciding how to configure a mobile device to receive multicast data or service according to the mobile device state; the mobile device will receive multicast data via multicast (point to multipoint) if the mobile is in inactive or idle mode; Also, the mobile can receive multicast data via unicast (point to point) if the mobile is in active mode). It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, having the teachings of Li and Saily before him or her, to modify the invention of Kim to decide how to deliver multicast data to a mobile based on determining whether the mobile in idle state or active state. The suggestion for doing so would have been to solve challenges that may exist in providing multicast data transmission to mobile low activity UEs, e.g., as the UEs change location (move between cells) and/or change state (¶ 0052).
As to claim 17:
The combination of Li and Saily discloses:
The method of claim 1, wherein the resource configuration is further based on a quality of service profile associated with the multicast or broadcast session; (see Li ¶s 0156, 0160) after determining that the UE is authorized to use multicast/broadcast service. AMF 203 sends MBS session establishment message or update request message to the selected MB-SMF 208 depending on whether the MBS session exists, the request may include the information such as UE ID, session ID, QoS flow ID and corresponding QoS information (e.g., 5G QoS Indicator (5QI), QoS requirements such as maximum data rate per QoS flow or per MBS session, maximum latency, or error rate ”; (Also see Saily ¶ 0041 and 110).
As to claim 18:
Li1 discloses:
when the apparatus is in an the idle states a context of the apparatus is released by radio access network (RAN), wherein the context includes an identifier identifying the multicast or broadcast service that is authorized for the apparatus to receive data; (See Li ¶ 170 and Saily ¶ 0041 and 0050)
As to claim 19:
Li discloses:
The apparatus of claim 16, wherein the resource configuration is further determined based on a number of mobile devices that are interested in accessing the multicast or broadcast service.
“In an example, the core network function finds that the number of UEs receiving the same data content via respective unicast session exceeds a threshold number and decides to start the multicast data transfer for more efficient network resource usage.” [0134] Li
As to claim 20:
Li discloses:
The apparatus of claim 16, wherein the multicast or broadcast service is associated with a Temporary Mobile Group Identity (TMGI) that identifies the multicast or broadcast service.
“AMF 203 sends a N2 message to RAN node 202 … may include the following information to help RAN node 202 prepare for the switch.” [0165] Li
“The information may include … TMGI to identify the multicast group.” [0170] Li
Response to Arguments
Applicant’s arguments with respect to the claims have been considered but are moot because the arguments do not apply to any of the references being used in the current rejection.
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 KHALED M KASSIM whose telephone number is (571)270-3770. The examiner can normally be reached 9:00 am - 5:00 PM.
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.
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.
/KHALED M KASSIM/supervisory patent examiner, Art Unit 2475
Prosecution Insights