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
Acknowledgment is made of applicant’s claim for foreign priority under 35 U.S.C. 119 (a)-(d).
---------- ---------- ----------
Information Disclosure Statement
The information disclosure statements (IDS) submitted on 26th September 2024 and 12th June 2025 are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
========== ========== ==========
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.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 1 – 4, 6 – 9, 11, 13, 14, 16, 18 and 19 are rejected under 35 U.S.C. 103 as being unpatentable over Tiwari et al (US 2025/0063336 A1) in view of Liang et al (US 2024/0314886 A1).
Claim 1 (similarly Claim 6). Tiwari shows a first network entity performing a session management function and a packet data network gateway-control function (SMF+PGW-C) in a wireless communication system (figs. 1 – 4 and 14: SMF+PGW-C / PGW-C+SMF), the first network entity comprising: a transceiver (fig. 14: transceiver); and at least one processor (fig. 14: controller) configured to: transmit, to a second network entity performing a session management-policy control function (SM-PCF), a request message for updating a user equipment (UE) policy of a UE (fig. 2 step 4 and [0313]: upon reception of the create session request message the PGW-C+SMF 71 sends an existing message defined between SMF (e.g. PGW-C+SMF 71) and PCF 73 or a new message e.g. Npcf_get_UEpolicy Request message containing at least one of Policy type, S1 mode supported, N1 mode supported, the UE policy list, the UE policy classmark, the UE OS ID IE and the UE status), and receive, from the second network entity, a response message for updating the UE policy of the UE, the response message including information about a changed UE policy of the UE (fig. 2 step 7 and [0340]: upon reception of the UE policy in the response message from the UDM 75 or UDR, the PCF 73 sends an existing message defined between PCF 73 to SMF or in a new message e.g. Npcf_get_UEpolicy response message to the PGW-C+SMF 71 wherein the existing message or the new message may include the UE policy), wherein the request message includes information used for association establishment of the UE policy between the second network entity ([0341]: upon reception of the UE policy in the response message from the PCF 73, the PGW-C+SMF 71 sends a Create session response message containing the UE policy to the S-GW 81 wherein the UE policy may be stored in the PCO and the UE policy may be stored in the PCO of the Create session response message).Tiwari does not very expressly describe the request message also includes a third network entity performing a UE-policy control function (UE-PCF).Liang teaches a request message that includes a third network entity performing a UE-PCF (fig. 3, [0086], [0090] and [0095]: the UE registers to the network and retrieves the allowed NSSAI wherein during the registration procedure, the AMF establishes AM Policy Association with the (V-)PCF by sending Npcf_AMPolicyControl_Create to the (V-)PCF… the PCF selected by the AMF for the AM Policy Association is referred to as AM-PCF and/or UE-PCF… the SMF provides the request for notification of SM Policy Association establishment and termination to a DNN, S-NSSAI together with AM-PCF binding information to the SM-PCF if received from the AMF… the AM-PCF subscribes to notifications of event “start/stop of application traffic” by sending Npcf_PolicyAuthorization_Subscribe (UE address, EventId, EventFilter set to “list of Application Identifiers”) to the SM-PCF).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the UE-PCF information as taught by Liang in the request message of Tiwari to dynamically push personalized routing, mobility and network-slicing policies directly to individual devices and optimizing traffic and battery life.
Claim 2 (similarly claim 7). Tiwari, modified by Liang, shows the first network entity of claim 1, wherein the at least one processor is further configured to: receive, from a fourth network entity performing a unified data management and home subscriber server (UDM+HSS) (figs. 1 – 4 and [0294]: HSS+UDM / UDM… HSS+UDM 75 has functions of HSS in EPC and functions of UDM in 5GC), a first message including at least one of an indicator indicating that the UE policy has been changed ([0395]: when the PCF 73 determines e.g. when the PCF 73 receives the updated UE policy from the UDM 75 or the PCF 73 determines by itself e.g. based on the current network condition or operator policy, to update the UE policy and the UE 3 is registered to the EPS, the PCF 73 sends an existing message or a new message containing an indicator indicating that the UE policy update is pending to the PGW-C+SMF 71).
Claim 3 (similarly claim 8). Tiwari, modified by Liang, shows the first network entity of claim 2, wherein the first message further includes at least one of an identifier indicating the UE ([0300]: the UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) may be set in the PCO parameter in the attach request message) or an identifier indicating the third network entity (n/a).
Claim 4 (similarly claim 9). Tiwari, modified by Liang, shows the first network entity of claim 1, wherein the information used for association establishment of the UE policy includes at least one of an identifier of the UE ([0300]: the UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) may be set in the PCO parameter in the attach request message), an indicator indicating that the UE policy is transferable through a first network to the UE ([0378]: upon reception of the message from the PCF 73, the UDR or the UDM 75 transfers the UE policy to the PCF 73 in an existing message between UDM 75/UDR and PCF 73 or a new message e.g. an Nudm_get_UEpolicy Response message), and an identifier indicating the third network entity (n/a), and wherein the UE moves from a second network to the first network (n/a).
---------- ---------- ----------
Claim 11 (similarly Claim 14). Tiwari shows a second network entity performing a session management-policy control function (SM-PCF) in a wireless communication system (figs. 1 – 4 and 16: PCF), the second network entity comprising: a transceiver (fig. 16: transceiver); and at least one processor (fig. 16: controller) configured to: receive, from a first network entity performing a session management function and a packet data network gateway-control (SMF+PGW-C), a request message for updating a user equipment (UE) policy of a UE (fig. 2 step 4 and [0313]: upon reception of the create session request message the PGW-C+SMF 71 sends an existing message defined between SMF (e.g. PGW-C+SMF 71) and PCF 73 or a new message e.g. Npcf_get_UEpolicy Request message containing at least one of Policy type, S1 mode supported, N1 mode supported, the UE policy list, the UE policy classmark, the UE OS ID IE and the UE status), and transmit, to the first network entity, a response message for updating the UE policy of the UE, the response message including information about a changed UE policy of the UE (fig. 2 step 7 and [0340]: upon reception of the UE policy in the response message from the UDM 75 or UDR, the PCF 73 sends an existing message defined between PCF 73 to SMF or in a new message e.g. Npcf_get_UEpolicy response message to the PGW-C+SMF 71 wherein the existing message or the new message may include the UE policy).Tiwari does not expressly describe the step of: performing association establishment for the UE policy with a third network entity performing a UE-policy control function (UE-PCF) using information included in the request message.Liang teaches feature of performing association establishment for a UE policy with a third network entity performing a UE-policy control function (UE-PCF) using information included in a request message (fig. 3, [0086], [0090] and [0095]: the UE registers to the network and retrieves the allowed NSSAI wherein during the registration procedure, the AMF establishes AM Policy Association with the (V-)PCF by sending Npcf_AMPolicyControl_Create to the (V-)PCF… the PCF selected by the AMF for the AM Policy Association is referred to as AM-PCF and/or UE-PCF… the SMF provides the request for notification of SM Policy Association establishment and termination to a DNN, S-NSSAI together with AM-PCF binding information to the SM-PCF if received from the AMF… the AM-PCF subscribes to notifications of event “start/stop of application traffic” by sending Npcf_PolicyAuthorization_Subscribe (UE address, EventId, EventFilter set to “list of Application Identifiers”) to the SM-PCF).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the UE-PCF information as taught by Liang in the request message of Tiwari to dynamically push personalized routing, mobility and network-slicing policies directly to individual devices and optimizing traffic and battery life.
Claim 13 (similarly claim 18). Tiwari, modified by Liang, shows the second network entity of claim 11, wherein the information used for association establishment for the UE policy includes at least one of an identifier of the UE ([0300]: the UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) may be set in the PCO parameter in the attach request message), an indicator indicating that the UE policy is transferable through a first network to the UE ([0378]: upon reception of the message from the PCF 73, the UDR or the UDM 75 transfers the UE policy to the PCF 73 in an existing message between UDM 75/UDR and PCF 73 or a new message e.g. an Nudm_get_UEpolicy Response message), and an identifier indicating the third network entity (n/a), and wherein the UE moves from a second network to the first network (n/a).
Claim 16 (similarly claim 19). Tiwari, modified by Liang, shows the second network entity of claim 13, wherein the indicator indicating that the UE policy is transferable through the first network to the UE is transmitted from a fourth network entity performing a user data repository (UDR) ([0378]: upon reception of the message from the PCF 73, the UDR or the UDM 75 transfers the UE policy to the PCF 73 in an existing message between UDM 75/UDR and PCF 73 or a new message e.g. an Nudm_get_UEpolicy Response message).
---------- ---------- ----------
Claims 5, 10, 17 and 20 are rejected under 35 U.S.C. 103 as being unpatentable over Tiwari et al in view of Liang et al, applied to claims 1 and 11, and in further view of Youn et al (US 2020/0145953 A1).
Claim 5 (similarly claim 10). Tiwari, modified by Liang, shows the first network entity of claim 1; Tiwari, modified by Liang, does not expressly describe wherein the at least one processor is further configured to: transmit, to the UE, a second message including a UE policy container including the information about the changed UE policy, and wherein the response message includes the UE policy container including the information about the changed UE policy.Youn teaches features of: transmitting, to a UE, a second message including a UE policy container including information about changed UE policy ([0497]: the AMF may determine a need for a UE configuration change for various causes (e.g. a UE mobility change, an NW policy, a UE subscription information change) wherein if the UE is in CM-IDLE, the AMF triggers a network trigger service request and the AMF may transmit, to the UE, a UE configuration update command including UE parameters (temporary user ID, a TAI list, an NSSAI, mobility restriction, an MICO inactive mode, a policy message container)), and wherein a response message includes the UE policy container including the information about the changed UE policy ([0498] – [0499]: the UE transmits a registration update message to the AMF when it receives the disable MICO mode… after the UE receives the UE configuration update command, the update of a specific parameter may trigger a registration update procedure by the UE).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the UE policy container features as taught by Youn in the first network entity of Tiwari, modified by Liang, to ensure safe, end-to-end delivery of policies without allowing intermediate nodes to decode them.
Claim 17 (similarly claim 20). Tiwari, modified by Liang, shows the second network entity of claim 11; Tiwari, modified by Liang, does not expressly describe wherein the information about the changed UE policy is included in a UE policy container.Youn teaches information about changed UE policy being included in a UE policy container ([0497]: the AMF may determine a need for a UE configuration change for various causes (e.g. a UE mobility change, an NW policy, a UE subscription information change) wherein if the UE is in CM-IDLE, the AMF triggers a network trigger service request and the AMF may transmit, to the UE, a UE configuration update command including UE parameters (temporary user ID, a TAI list, an NSSAI, mobility restriction, an MICO inactive mode, a policy message container)).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the UE policy container feature as taught by Youn in the first network entity of Tiwari, modified by Liang, to ensure safe, end-to-end delivery of policies without allowing intermediate nodes to decode them.
========== ========== ==========
Conclusion
The prior art made of record is considered pertinent to applicant’s disclosure.
1. KIM et al, US 2022/0150811 A1: a first network entity managing a packet data network (PDN) session in a wireless communication system supporting interworking between a first network and a second network, the first network entity comprising a transceiver; and a processor configured to: receive, via the transceiver from a second network entity managing subscription information, subscription update information of a user equipment (UE) for which a PDN connection associated with a network slice is established in the second network, the network slice being subscribed in the first network, determine whether to release the PDN connection in case that the subscription update information includes information notifying that network slice related information of the UE is changed, and perform an operation for a release of the PDN connection associated with the network slice in case that the release of the PDN connection is determined.
2. Zhou et al, US 2022/0150683 A1: a system for selecting a session management network element, comprising a first session management network element configured to provide service for a terminal device; and a mobility management network element configured to: determine a first data network access identifier (DNAI) corresponding to a first session of the terminal device; and select, for the first session of the terminal device, the first session management network element, wherein the first session management network element is configured to support all DNAIs in the first DNAI.
3. Cheng et al, US 2020/0404107 A1: techniques for user equipment (UE) policy management in interworking evolved packet systems (EPS) and fifth generation (5G) wireless communications systems wherein a UE may transmit, to a mobility management entity (MME), a request for a UE policy from a policy control function (PCF) and receive the UE policy from the MME.
4. Dao et al, US 2018/0199398 A1: a network architecture and methods of managing packet data unit (PDU) sessions in a network which includes PDU session establishment procedures, PDU session modification procedures, PDU session state transfer procedures, PDU session release procedures, and user equipment (UE) handover procedures.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Xavier Szewai Wong whose telephone number is 571.270.1780. The examiner can normally be reached on 11:30 am - 8:30 pm Mon to Fri.
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, Jeffrey Rutkowski can be reached on 571.270.1215. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/XAVIER S WONG/Primary Examiner, Art Unit 2415 8th July 2026