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 .
Response to Amendment
This Office Action is in response to applicant’s amendment submitted on February 25, 2026.
Claims, 150-163 are now currently pending in the present application.
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.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 150, 152-157 and 159-163, are rejected under U.S.C. 102(a)(1) as being anticipated by MARY (WO 2020/249201 A1,hereinafter MARY).
Consider Claim 150, discloses a method of operation of a Network Exposure Function, NEF, the method comprising:
receiving a request from an Application Function, AF, wherein the request comprises information indicating a plurality of UEs, wherein the plurality of UEs comprises at least one UE that has not established a Protocol Data Unit, PDU, session yet; and (page 23 line 19-25, the network functions such as SMF or PCF or a node such a gNB can send Redundant POU session trigger message to the AF either directly or through a Network Exposure Function NEF 11 accordingly in a step 502, 602. This message contains information on s-NSSAI, DNN, DNAI, UE ID (SUPI/GPSI), Redundancy Indicator (RSN2). The SMF/PCF can then send this message through NEF, the NEF transfers this information into AS Service ID and sends the AF Service ID along with the GPSI to the Application Function AF 12. Page 11 line 3-7, the network function, the SMF 5, is configured to obtain from a User Equipment, UE 1, a Protocol Data Unit, PDU, session request for establishment of a redundant PDU session in step 103. The SMF 5 is configured to determine in step 104 said redundant PDU session to be established based on at least one condition, wherein said at least one condition comprises one or many of).
transmitting, to the AF, an NEF response indicating whether the request is granted or not. (Page 24 line 20-25, the AF on receiving such a redundant POU session trigger request message, sends the Trigger Delivery Request message with the received information from SMF/PCF to the NEF (if involved). The NEF checks that the AF is authorized to send trigger requests and that the AF has not exceeded its quota or rate of trigger submission over Nnef. If this check fails, the NEF sends an Nnef_Trigger_Delivery response with a cause value indicating the reason for the failure condition and the flow stops at this step).
Consider Claim 152, MARY discloses the method of claim 150, wherein the information indicating the plurality of UEs comprises a list of UE IDs of the plurality of UEs, a UE group ID of the plurality of UEs, or a UE indication that identifies whether the request applies to any UE of the plurality of UEs. (Page 18 line 20-24, the network function is configured to obtain a list of redundancy policies for at least one UE, and to configure the redundant PDU session for a UE based on the redundancy policy associated with the UE in the list of redundancy policies. Also, the network function can store the obtained list).
Consider Claim 153, MARY discloses the method of claim 152, further comprising:
transmitting data update request to a Unified Data Repository, UDR, for storage, wherein the data update request comprises information associated with the list of UE IDs, the UE group ID, or the UE indication; and (page 19 line 12-14, The PCF maintains the latest list of UE Redundant UP policy delivered to the UE and updates the latest list in the UDR by invoking Nudr_DM_Update (SUPI, Redundant UP Policy Data, Policy Set Entry) service operation).
receiving, from the UDR, a UDR response indicating that the data update request is stored in the UDR. (Page 20 line 16-19, in a step 404, the SMF 5 verifies the "Network UP Redundancy ID" against the Redundant UP policy if available or using Nudm_SDM_Get operations receives the Redundant UP policy from UDM/UDR and subscribes to receive UE Redundant UP policy using Nudm_SDM_Subscribe).
Consider Claim 154, MARY discloses the method of claim 153, wherein:
the request further comprises one or more conditions to be satisfied by the plurality of UEs and the data update request further comprises information associated with the one or more conditions. (Page 12 line1-7, if the SMF derived CN assisted RAN parameters tuning are stored for the activated PDU Session(s), the AMF may derive updated CN assisted RAN parameters tuning and provide them the (R)AN. The (R)AN can store the RSN1, RSN2, Redundancy Status received from the AMF to identify the subsequent Redundant PDU session request for same AMF selection. Then, in a step 113, (R)AN forwards the NAS message (PDU Session ID, RSN1, RSN2, Redundancy Status, N1 SM container (PDU Session Establishment Accept)) provided in step 12 to the UE).
Consider Claim 155, MARY discloses the method of claim 154, wherein the one or more conditions define one or more geographic zones, one or more time windows, or both one or more geographic zones and one or more time window. (Page 7 line 21-27, these network conditions in 5GS can be analyzed/identified based on monitoring, real time or predictions. The indication for the redundancy requirement related to the request PDU session can be notified to the UE by the network during the PDU session establishment procedure. The UE can then send a request for redundant user plane through redundant PDU session initiation request message based on the indication sent by the network and can also include the network sent authorization information for initiating the redundant user plane).
Consider Claim 156, MARY discloses the method of claim 153, wherein the data update request further comprises QoS data or sponsor data. (Page 17 line 28-30, the step 301 can be initiated when the PCF 6 receives QoS Monitoring Results or NF(s) QoS/load conditions to update the UE redundant UP policy and PDU Session selection related policy information in the UE configuration).
Consider Claim 157, MARY discloses a network node that implements a Network Exposure Function, NEF, the network node comprising:
a network interface; and
processing circuitry associated with the network interface, the processing circuitry configured to cause the network node to: (Page 23 line 19-25, the network functions such as SMF or PCF or a node such a gNB can send Redundant PDU session trigger message to the AF either directly or through a Network Exposure Function NEF 11 accordingly in a step 502, 602. This message contains information on s-NSSAI, DNN, DNAI, UE ID (SUPI/GPSI), Redundancy Indicator (RSN2). The SMF/PCF can then send this message through NEF, the NEF transfers this information into AS Service ID and sends the AF Service ID along with the GPSI to the Application Function AF 12).
receive a request from an Application Function, AF, wherein the request comprises information indicating a plurality of UEs, wherein the plurality of UEs comprises at least one UE that has not established a Protocol Data Unit, PDU, session yet; and (page 23 line 19-25, the network functions such as SMF or PCF or a node such a gNB can send Redundant POU session trigger message to the AF either directly or through a Network Exposure Function NEF 11 accordingly in a step 502, 602. This message contains information on s-NSSAI, DNN, DNAI, UE ID (SUPI/GPSI), Redundancy Indicator (RSN2). The SMF/PCF can then send this message through NEF, the NEF transfers this information into AS Service ID and sends the AF Service ID along with the GPSI to the Application Function AF 12. Page 11 line 3-7, the network function, the SMF 5, is configured to obtain from a User Equipment, UE 1, a Protocol Data Unit, PDU, session request for establishment of a redundant PDU session in step 103. The SMF 5 is configured to determine in step 104 said redundant PDU session to be established based on at least one condition, wherein said at least one condition comprises one or many of).
transmit, to the AF, an NEF response indicating whether the request is granted or not. (Page 24 line 20-25, the AF on receiving such a redundant POU session trigger request message, sends the Trigger Delivery Request message with the received information from SMF/PCF to the NEF (if involved). The NEF checks that the AF is authorized to send trigger requests and that the AF has not exceeded its quota or rate of trigger submission over Nnef. If this check fails, the NEF sends an Nnef_Trigger_Delivery response with a cause value indicating the reason for the failure condition and the flow stops at this step).
Consider Claim 159, MARY discloses the network node of claim 157, wherein the information indicating the plurality of UEs comprises a list of UE IDs of the plurality of UEs, a UE group ID of the plurality of UEs, or a UE indication that identifies whether the request applies to any UE of the plurality of UEs. (Page 18 line 20-24, the network function is configured to obtain a list of redundancy policies for at least one UE, and to configure the redundant PDU session for a UE based on the redundancy policy associated with the UE in the list of redundancy policies. Also, the network function can store the obtained list).
Consider Claim 160, MARY discloses the network node of claim 159, wherein the processing circuitry is further configured to cause the network node to:
transmit data update request to a Unified Data Repository, UDR, for storage, wherein the data update request comprises information associated with the list of UE IDs, the UE group ID, or the UE indication; and (page 19 line 12-14, The PCF maintains the latest list of UE Redundant UP policy delivered to the UE and updates the latest list in the UDR by invoking Nudr_DM_Update (SUPI, Redundant UP Policy Data, Policy Set Entry) service operation).
receive, from the UDR, a UDR response indicating that the data update request is stored in the UDR. (Page 20 line 16-19, in a step 404, the SMF 5 verifies the "Network UP Redundancy ID" against the Redundant UP policy if available or using Nudm_SDM_Get operations receives the Redundant UP policy from UDM/UDR and subscribes to receive UE Redundant UP policy using Nudm_SDM_Subscribe).
Consider Claim 161, MARY discloses the network node of claim 160, wherein:
the request further comprises one or more conditions to be satisfied by the plurality of UEs; and the data update request further comprises information associated with the one or more conditions. (Page 12 line1-7, if the SMF derived CN assisted RAN parameters tuning are stored for the activated PDU Session(s), the AMF may derive updated CN assisted RAN parameters tuning and provide them the (R)AN. The (R)AN can store the RSN1, RSN2, Redundancy Status received from the AMF to identify the subsequent Redundant PDU session request for same AMF selection. Then, in a step 113, (R)AN forwards the NAS message (PDU Session ID, RSN1, RSN2, Redundancy Status, N1 SM container (PDU Session Establishment Accept)) provided in step 12 to the UE).
Consider Claim 162, MARY discloses the network node of claim 161, wherein the one or more conditions define one or more geographic zones, one or more time windows, or both one or more geographic zones and one or more time windows. (Page 7 line 21-27, these network conditions in 5GS can be analyzed/identified based on monitoring, real time or predictions. The indication for the redundancy requirement related to the request PDU session can be notified to the UE by the network during the PDU session establishment procedure. The UE can then send a request for redundant user plane through redundant PDU session initiation request message based on the indication sent by the network and can also include the network sent authorization information for initiating the redundant user plane).
Consider Claim 163, MARY discloses the network node of claim 160, wherein the data update request further comprises QoS data or sponsor data. (Page 17 line 28-30, the step 301 can be initiated when the PCF 6 receives QoS Monitoring Results or NF(s)
QoS/load conditions to update the UE redundant UP policy and PDU Session selection related policy information in the UE configuration).
Response to Arguments
Applicant’s arguments with respect to claims 150, 152-157 and 159-163 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
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 MICHELE CAMILLE DOUGLAS whose telephone number is (571)270-0458. The examiner can normally be reached Monday - Friday 6:30 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.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jeanette Parker can be reached at 571-270-3647. 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.
/MICHELE C DOUGLAS/Examiner, Art Unit 2646
/JEANETTE J PARKER/Supervisory Patent Examiner, Art Unit 2646
Prosecution Insights