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 .
Information Disclosure Statement
The information disclosure statement submitted on 04/26/2024, have been considered by the examiner and made of record in the application file.
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 1-20 are rejected under U.S.C. 102(a)(1) as being anticipated by 3GPP (3GPP TS 23.502 V18.0.0 (2022-12), hereinafter 3GPP).
Consider Claim 1, 3GPP discloses a method performed by an access and mobility management function (AMF) entity in a wireless communication system, the method comprising:
receiving, from a user equipment (UE), a registration request for fifth generation system (5GS), wherein the registration request includes information on a UE policy container and an indicator that the UE is moving from an evolved packet system (EPS); (Section 4.11.1.2.2.3 page 247, the UE performs the EPS to 5GS Mobility Registration Procedure from step 2 in clause 4.11.1.3.3. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available. If the UE holds a native 5G-GUTI it also includes the native 5G-GUTI as an additional GUTI in the Registration Request).
transmitting, to a first policy control function (PCF) entity for the UE, a first request message for first access and management (AM) policy association based on the registration request, wherein the first request message includes the indicator; and (Section 4.2.4.3 page 85, if the UE is registered in both 3GPP and non-3GPP accesses and reachable on both access and served by the same AMF, the AMF transfers transparently the UE Policy container to the UE via one of the accesses based on the AMF local policy).
receiving, from the first PCF entity, a message including an identifier (ID) of a second PCF entity for the EPS based on the first request message. (Section 4.2.4.3 page 84, the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503 [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message).
Consider Claim 2, 3GPP discloses the method of claim 1, further comprising: transmitting, to the second PCF entity, a second request message for second AM policy association, wherein the second request message includes the information on the UE policy container; (section 4.16.3.2 page 417, the (V-)PCF removes the policy context for the UE and replies to the AMF with an Acknowledgement including success or failure. In the non-roaming case, the PCF may unsubscribe to analytics from NWDAF).
receiving, from the second PCF entity, information on a second AM policy for the UE as a response to the second request message; and Section 4.2.3.3 page 71, the PCF needs to send a message to the UE, using the Npcf_AMPolicyControl_Create Response service operation, or the Npcf_AMPolicyControl_UpdateNotify service operation and the UE is in CM-IDLE state).
applying the information on the second AM policy to a management of a registration and a mobility for the UE. (Section 4.15.6.9.2 page 391, The PCF takes a policy decision and then an AM Policy Association Modification procedure initiated by the PCF for the UE may be performed as described in clause 4.16.2.2. If the AF has subscribed to access and mobility management related events i.e. request for service area coverage outcome in step 2, then the PCF reports the event (i.e. outcome of the request for service area coverage) to the AF as described in clause 4.16.2.2).
Consider Claim 3, 3GPP discloses the method of claim 1, wherein the message further includes an indicator for a PCF relocation request,
wherein the UE policy container includes at least one of information on a UE policy stored in the UE or information indicating that the UE is capable of receiving a UE policy via the EPS, and (Section 4.2.4.3 page 85, If the UE is in CM-CONNECTED over 3GPP access or non-3GPP access, the AMF transfers transparently the UE Policy container (UE policy information) received from the PCF to the UE. The UE Policy container includes the list of Policy Sections as described in TS 23.503 [20]).
wherein the first request message further includes a subscription permanent identifier for the UE. (Section 4.2.2.2.2 page 38, if old AMF was a consumer of UE related NWDAF services, the old AMF includes information about active analytics subscriptions, i.e. the Subscription Correlation ID, NWDAF identifier (i.e. Instance ID or Set ID), Analytics ID(s) and associated Analytics specific data in the Namf_Communication_UEContextTransfer response).
Consider Claim 4, 3GPP discloses the method of claim 1, further comprising:
receiving, from the first PCF entity, information on a first AM policy as a response to the first request message; (Section 4.2.3.3 page 71, the PCF needs to send a message to the UE, using the Npcf_AMPolicyControl_Create Response service operation, or the Npcf_AMPolicyControl_UpdateNotify service operation and the UE is in CM-IDLE state).
transmitting, to the first PCF entity, a third request message for first UE policy association; and (Section 4.2.4.3 page 84, for the network triggered UE policy update case (e.g. the change of UE location, the change of Subscribed S-NSSAIs as described in clause 6.1.2.2.2 of TS 23.503 [20]), the PCF checks the latest list of PSIs to decide which UE policies have to be sent to the UE).
receiving, from the first PCF entity, the message including the ID of the second PCF entity for the EPS and an indicator for a PCF relocation request as a response to the third request message, (Section 4.2.4.3 page 84, the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503 [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message).
wherein the third request message includes the information on the UE policy container. (Section 4.2.4.3 page 84, PCF invokes Namf_Communication_N1N2 MessageTransfer service operation provided by the AMF. The message includes SUPI, UE Policy Container).
Consider Claim 5, 3GPP discloses the method of claim 4, further comprising:
transmitting, to the first PCF entity, a message for releasing the first AM policy association; and (section 4.16.3.2 page 417, the (V-)PCF removes the policy context for the UE and replies to the AMF with an Acknowledgement including success or failure. In the non-roaming case, the PCF may unsubscribe to analytics from NWDAF).
deleting the information on the first AM policy. (Section 4.2.2.2.2 page 43, If new AMF received in the UE context transfer in step 5 the information about the AM Policy Association and the UE Policy Association and decides, based on local policies, not to use the PCF(s) identified by the PCF ID(s) for the AM Policy Association and the UE Policy Association, then it will inform the old AMF that the AM Policy Association and the UE Policy Association in the UE context is not used any longer and then the PCF selection is performed in step 15).
Consider Claim 6, 3GPP discloses an access and mobility management function (AMF) entity in a wireless communication system, the AMF entity comprising:
a transceiver; and (section 4.3.4.2 page 151, if the message received from the SMF in step 3 does not include N2 SM Resource Release request, the AMF transmits the NAS message (PDU Session ID, N1 SM container) to the UE).
a controller coupled with the transceiver and configured to: (section 4.2.2.2.3 page 52, after receiving the Registration Request message transmitted at step 7(A)a or step 7(B)b, the target AMF continues with the Registration procedure from step 4 until 22 of figure 4.2.2.2.2-1 (with the target AMF corresponding to the new AMF), which includes the UE context retrieved from old AMF).
receive, from a user equipment (UE), a registration request for fifth generation system (5GS), wherein the registration request includes information on a UE policy container and an indicator that the UE is moving from an evolved packet system (EPS), (section 4.11.1.2.2.3 page 247, the UE performs the EPS to 5GS Mobility Registration Procedure from step 2 in clause 4.11.1.3.3. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available. If the UE holds a native 5G-GUTI it also includes the native 5G-GUTI as an additional GUTI in the Registration Request).
transmit, to a first policy control function (PCF) entity for the UE, a first request message for first access and management (AM) policy association based on the registration request, wherein the first request message includes the indicator, and (Section 4.2.4.3 page 85, if the UE is registered in both 3GPP and non-3GPP accesses and reachable on both access and served by the same AMF, the AMF transfers transparently the UE Policy container to the UE via one of the accesses based on the AMF local policy).
receive, from the first PCF entity, a message including an identifier (ID) of a second PCF entity for the EPS based on the first request message. (Section 4.2.4.3 page 84, the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503 [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message).
Consider Claim 7, 3GPP discloses the AMF entity of claim 6, wherein the controller is further configured to:
transmit, to the second PCF entity, a second request message for second AM policy association, wherein the second request message includes the information on the UE policy container, (section 4.16.3.2 page 417, the (V-)PCF removes the policy context for the UE and replies to the AMF with an Acknowledgement including success or failure. In the non-roaming case, the PCF may unsubscribe to analytics from NWDAF).
receive, from the second PCF entity, information on a second AM policy for the UE as a response to the second request message, and Section 4.2.3.3 page 71, the PCF needs to send a message to the UE, using the Npcf_AMPolicyControl_Create Response service operation, or the Npcf_AMPolicyControl_UpdateNotify service operation and the UE is in CM-IDLE state).
apply the information on the second AM policy to a management of a registration and a mobility for the UE. (Section 4.15.6.9.2 page 391, The PCF takes a policy decision and then an AM Policy Association Modification procedure initiated by the PCF for the UE may be performed as described in clause 4.16.2.2. If the AF has subscribed to access and mobility management related events i.e. request for service area coverage outcome in step 2, then the PCF reports the event (i.e. outcome of the request for service area coverage) to the AF as described in clause 4.16.2.2).
Consider Claim 8, 3GPP discloses the AMF entity of claim 6, wherein the message further includes an indicator for a PCF relocation request,
wherein the UE policy container includes at least one of information on a UE policy stored in the UE or information indicating that the UE is capable of receiving a UE policy via the EPS, and (Section 4.2.4.3 page 85, If the UE is in CM-CONNECTED over 3GPP access or non-3GPP access, the AMF transfers transparently the UE Policy container (UE policy information) received from the PCF to the UE. The UE Policy container includes the list of Policy Sections as described in TS 23.503 [20]).
wherein the first request message further includes a subscription permanent identifier for the UE. (Section 4.2.2.2.2 page 38, if old AMF was a consumer of UE related NWDAF services, the old AMF includes information about active analytics subscriptions, i.e. the Subscription Correlation ID, NWDAF identifier (i.e. Instance ID or Set ID), Analytics ID(s) and associated Analytics specific data in the Namf_Communication_UEContextTransfer response).
Consider Claim 9, 3GPP discloses the AMF entity of claim 6, wherein the controller is further configured to:
receive, from the first PCF entity, information on a first AM policy as a response to the first request message, (Section 4.2.3.3 page 71, the PCF needs to send a message to the UE, using the Npcf_AMPolicyControl_Create Response service operation, or the Npcf_AMPolicyControl_UpdateNotify service operation and the UE is in CM-IDLE state).
transmit, to the first PCF entity, a third request message for first UE policy association, and (Section 4.2.4.3 page 84, for the network triggered UE policy update case (e.g. the change of UE location, the change of Subscribed S-NSSAIs as described in clause 6.1.2.2.2 of TS 23.503 [20]), the PCF checks the latest list of PSIs to decide which UE policies have to be sent to the UE).
receive, from the first PCF entity, the message including the ID of the second PCF entity for the EPS and an indicator for a PCF relocation request as a response to the third request message, and (Section 4.2.4.3 page 84, the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503 [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message).
wherein the third request message includes the information on the UE policy container. (Section 4.2.4.3 page 84, PCF invokes Namf_Communication_N1N2 MessageTransfer service operation provided by the AMF. The message includes SUPI, UE Policy Container).
Consider Claim 10, 3GPP discloses the AMF entity of claim 9, wherein the controller is further configured to: transmit, to the first PCF entity, a message for releasing the first AM policy association, and (section 4.16.3.2 page 417, the (V-)PCF removes the policy context for the UE and replies to the AMF with an Acknowledgement including success or failure. In the non-roaming case, the PCF may unsubscribe to analytics from NWDAF).
delete the information on the first AM policy. (Section 4.2.2.3.2 page 56, if there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated AM Policy Association Termination procedure as defined in clause 4.16.3.2 delete the association with the PCF).
Consider Claim 11, 3GPP discloses a method performed by a first policy control function (PCF) entity in a wireless communication system, the method comprising:
receiving, from an access and mobility management function (AMF) entity, a first request message for first access management (AM) policy association based on a registration request including information on a UE policy container and an indicator that a user equipment (UE) is moving from an evolved packet system (EPS); and (Section 4.2.4.3 page 85, if the UE is registered in both 3GPP and non-3GPP accesses and reachable on both access and served by the same AMF, the AMF transfers transparently the UE Policy container to the UE via one of the accesses based on the AMF local policy).
transmitting, to the AMF entity, a message including an identifier (ID) of a second PCF entity for the EPS based on the first request message, wherein the first request message includes the indicator. (Section 4.2.4.3 page 84, the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503 [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message).
Consider Claim 12, 3GPP discloses the method of claim 11, further comprising:
transmitting, to a binding support function (BSF) entity, a message for requesting the ID of the second PCF entity for the EPS; and (section 4.15.9.2 page 395, the PCF registers to BSF as described in TS 23.503 [20]. TSCTSF invokes a Npcf_PolicyAuthorization_Create request message to the PCF and stores the DNN, S-NSSAI and IP address as received from PCF and SUPI as received from BSF and associates them with the AF-session).
receiving, from the BSF entity, information on the ID of the second PCF entity, wherein the message for requesting the ID of the second PCF entity includes a subscription permanent identifier (SUPI) for the UE, (section 4.15.9.4 page 409, The BSF provides to the TSCTSF the identity of the PCF for the UE for the requested SUPI via an Nbsf_Management_Notify operation. If matching entries already existed in the BSF when step 6 is performed, this shall be immediately reported to the TSCTSF).
wherein the information on the ID of the second PCF entity includes at least one of an end point address or a uniform resource identifier (URI). (Section 4.9.1.3.2 page 211, Allowed NSSAI for each Access Type if available, Tracing Requirements, LTE M Indication, the list of PDU Session IDs along with the corresponding SMF information and the corresponding S-NSSAI(s), PCF ID(s), DNN, UE Radio Capability ID and UE Radio Capability Information, N2 Notify URI)).
Consider Claim 13, 3GPP discloses the method of claim 11, wherein the message further includes an indicator for a PCF relocation request,
wherein the UE policy container includes at least one of information on a UE policy stored in the UE or information indicating that the UE is capable of receiving a UE policy via the EPS, and (section 4.11.1.2.2.3 page 247, The UE performs the EPS to 5GS Mobility Registration Procedure from step 2 in clause 4.11.1.3.3. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available).
wherein the first request message further includes a subscription permanent identifier (SUPI) for the UE. (Section 4.2.2.2.2 page 36, if the UE's 5G-GUTI was included in the Registration Request and the serving AMF has changed since last Registration procedure, new AMF and old AMF are in the same AMF Set and UDSF is deployed, the new AMF retrieves the stored UE's SUPI and UE context directly from the UDSF using Nudsf_UnstructuredDataManagement_Query service operation or they can share stored UE context via implementation specific means if UDSF is not deployed).
Consider Claim 14, 3GPP discloses the method of claim 11, further comprising: transmitting, to the AMF entity, information on a first AM policy as a response to
the first request message; (Section 4.2.2.2.2 page 43, If new AMF received in the UE context transfer in step 5 the information about the AM Policy Association and the UE Policy Association and decides, based on local policies, not to use the PCF(s) identified by the PCF ID(s) for the AM Policy Association and the UE Policy Association, then it will inform the old AMF that the AM Policy Association and the UE Policy Association in the UE context is not used any longer and then the PCF selection is performed in step 15).
receiving, from the AMF entity, a third request message for first UE policy association; and (section 4.2.2.2.2 page 38, If old AMF holds information about AM Policy Association and the information about UE Policy Association (i.e. the Policy Control Request Trigger for updating UE Policy as defined in TS 23.503 [20]), the old AMF includes the information about the AM Policy Association, the UE Policy Association and PCF ID).
transmitting, to the AMF entity, the message including the ID of the second PCF entity for the EPS and an indicator for a PCF relocation request as a response to the third request message, wherein the third request message includes the information on the UE policy container. (Section 4.11.1.1 page 234, the AMF indicates the UE support for EPS User Plane Integrity Protection to SMF. Then, for PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF may perform the EPS bearer ID allocation procedure as described in clause 4.11.1.4).
Consider Claim 15, 3GPP discloses the method of claim 14, further comprising:
receiving, from the AMF entity, a message for releasing the first AM policy association; and (Section 4.2.2.2.2 page 43, If new AMF received in the UE context transfer in step 5 the information about the AM Policy Association and the UE Policy Association and decides, based on local policies, not to use the PCF(s) identified by the PCF ID(s) for the AM Policy Association and the UE Policy Association, then it will inform the old AMF that the AM Policy Association and the UE Policy Association in the UE context is not used any longer and then the PCF selection is performed in step 15).
deleting the information on the first AM policy based on the message for releasing the first AM policy association. . (Section 4.2.2.3.2 page 56, if there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated AM Policy Association Termination procedure as defined in clause 4.16.3.2 delete the association with the PCF).
Consider Claim 16, 3GPP discloses a first policy control function (PCF) entity in a wireless communication system, the first PCF entity comprising:
a transceiver; and (section 4.3.4.2 page 151, if the message received from the SMF in step 3 does not include N2 SM Resource Release request, the AMF transmits the NAS message (PDU Session ID, N1 SM container) to the UE).
a controller coupled with the transceiver and configured to: (section 4.2.2.2.3 page 52, after receiving the Registration Request message transmitted at step 7(A)a or step 7(B)b, the target AMF continues with the Registration procedure from step 4 until 22 of figure 4.2.2.2.2-1 (with the target AMF corresponding to the new AMF), which includes the UE context retrieved from old AMF).
receive, from an access and mobility management function (AMF) entity, a first request message for first access management (AM) policy association based on a registration request including an indicator that a user equipment (UE) is from an evolved packet system (EPS) and information on a UE policy container, and (Section 4.2.4.3 page 85, if the UE is registered in both 3GPP and non-3GPP accesses and reachable on both access and served by the same AMF, the AMF transfers transparently the UE Policy container to the UE via one of the accesses based on the AMF local policy).
transmit, to the AMF entity, a message including an identification (ID) of a second PCF entity for the EPS based on the first request message, wherein the first request message includes the indicator that the UE is from the EPS. . (Section 4.2.4.3 page 84, the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503 [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message).
Consider Claim 17, 3GPP discloses the first PCF entity of claim 16, wherein the controller is further configured to:
transmit, to a binding support function (BSF) entity, a message for requesting the ID of the second PCF entity for the EPS, and (section 4.15.9.2 page 395, the PCF registers to BSF as described in TS 23.503 [20]. TSCTSF invokes a Npcf_PolicyAuthorization_Create request message to the PCF and stores the DNN, S-NSSAI and IP address as received from PCF and SUPI as received from BSF and associates them with the AF-session).
receive, from the BSF entity, information on the ID of the second PCF entity,
wherein the message for requesting the ID of the second PCF entity includes a subscription permanent identifier (SUPI) for the UE, and (section 4.15.9.4 page 409, The BSF provides to the TSCTSF the identity of the PCF for the UE for the requested SUPI via an Nbsf_Management_Notify operation. If matching entries already existed in the BSF when step 6 is performed, this shall be immediately reported to the TSCTSF).
wherein the information on the ID of the second PCF entity includes at least one of an end point address or a uniform resource identifier (URI). (Section 4.9.1.3.2 page 211, Allowed NSSAI for each Access Type if available, Tracing Requirements, LTE M Indication, the list of PDU Session IDs along with the corresponding SMF information and the corresponding S-NSSAI(s), PCF ID(s), DNN, UE Radio Capability ID and UE Radio Capability Information, N2 Notify URI)).
Consider Claim 18, 3GPP discloses the first PCF entity of claim 16, wherein the message further includes an indicator for a PCF relocation request,
wherein the UE policy container includes at least one of information on a UE policy stored in the UE or information indicating that the UE is capable of receiving a UE policy via the EPS, and (section 4.11.1.2.2.3 page 247, The UE performs the EPS to 5GS Mobility Registration Procedure from step 2 in clause 4.11.1.3.3. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available).
wherein the first request message further includes a subscription permanent identifier (SUPI) for the UE. (Section 4.2.2.2.2 page 36, if the UE's 5G-GUTI was included in the Registration Request and the serving AMF has changed since last Registration procedure, new AMF and old AMF are in the same AMF Set and UDSF is deployed, the new AMF retrieves the stored UE's SUPI and UE context directly from the UDSF using Nudsf_UnstructuredDataManagement_Query service operation or they can share stored UE context via implementation specific means if UDSF is not deployed).
Consider Claim 19, 3GPP discloses the first PCF entity of claim 16, wherein the controller is further configured to:
transmit, to the AMF entity, information on a first AM policy as a response to the first request message, (Section 4.2.2.2.2 page 43, If new AMF received in the UE context transfer in step 5 the information about the AM Policy Association and the UE Policy Association and decides, based on local policies, not to use the PCF(s) identified by the PCF ID(s) for the AM Policy Association and the UE Policy Association, then it will inform the old AMF that the AM Policy Association and the UE Policy Association in the UE context is not used any longer and then the PCF selection is performed in step 15).
receive, from the AMF entity, a third request message for first UE policy association, and (section 4.2.2.2.2 page 38, If old AMF holds information about AM Policy Association and the information about UE Policy Association (i.e. the Policy Control Request Trigger for updating UE Policy as defined in TS 23.503 [20]), the old AMF includes the information about the AM Policy Association, the UE Policy Association and PCF ID).
transmit, to the AMF entity, the message including the ID of the second PCF entity for the EPS and an indicator for a PCF relocation request as a response to the third request message, and wherein the third request message includes the information on the UE policy container. (Section 4.11.1.1 page 234, the AMF indicates the UE support for EPS User Plane Integrity Protection to SMF. Then, for PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF may perform the EPS bearer ID allocation procedure as described in clause 4.11.1.4).
Consider Claim 20, 3GPP discloses the first PCF entity of claim 19, wherein the controller is further configured to:
receive, from the AMF entity, a message for releasing the first AM policy association; and (Section 4.2.2.2.2 page 43, If new AMF received in the UE context transfer in step 5 the information about the AM Policy Association and the UE Policy Association and decides, based on local policies, not to use the PCF(s) identified by the PCF ID(s) for the AM Policy Association and the UE Policy Association, then it will inform the old AMF that the AM Policy Association and the UE Policy Association in the UE context is not used any longer and then the PCF selection is performed in step 15).
delete the information on the first AM policy based on the message for releasing the first AM policy association. . (Section 4.2.2.3.2 page 56, if there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated AM Policy Association Termination procedure as defined in clause 4.16.3.2 delete the association with the PCF).
Conclusion
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, Matthew Anderson can be reached at 571-272-4177. 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
/MATTHEW D. ANDERSON/Supervisory Patent Examiner, Art Unit 2646