5 Procedures and information flows for PN configuration
23.2593GPPPersonal Network Management (PNM)Procedures and information flowsRelease 17Stage 2TS
5.1 PN-registration
5.1.1 General
The PN-registration is a procedure where the PN-user requests authorization to use PNM applications. As a result of a successful registration, the UE capabilities can be conveyed to the PNM AS.
5.1.2 PN-registration procedure in the IM CN subsystem
Figure 5.1.2-1: Successful PN-registration procedure in the IM CN subsystem
1. The Register information flow sent by a UE arrives at the S-CSCF/Registrar. The Register information flow contains the private user identity and the public user identity of the UE.
2. The S-CSCF sends a Cx-Put/Cx-Pull containing the private user identity and public user identity to the HSS and the HSS returns the information flow (eg. the initial filter criteria) to the S-CSCF.
3. Based on the initial filter criteria, the S‑CSCF sends a Register information flow to the PNM AS. If the PNM AS specific data, for instance the PN UE name or the private user identity, which is associated with the initial filter criteria, is received from the HSS in Step 2, it is delivered to the PNM AS in the Register information flow.
4. The PNM AS sends a Subscribe information flow to obtain the public user identity received in the Register information flow in Step 3.
5. The S-CSCF sends a Notify information flow to the PNM AS containing the public user identities and the UE capabilities. If the S-CSCF assigned a GRUU for the UE during the registration, then the GRUU of the UE is delivered in the Notify information flow.
NOTE: At the same time as Steps 4) and 5) the AS can also contact the HSS using Sh to obtain the information. Where identical information is received from both sources, it is implementation specific how this is combined.
6. Optionally, the PNM AS authorizes the PN-registration by querying the HSS. It is done by sending the private user identity to the HSS. The HSS checks the public user identity/identities tied to the private user identity and sends the public user identity/identities and the private user identity back to the PNM AS.
7. The PNM AS then verifies the PN-registration by comparing the public user identity/identities and the PN UE name or with the other received from S-CSCF in the Step 3. As a result of a successful verification, the PNM AS enrols the public user identity and the PN UE name or as registered in the data base.
5.1.3 PN-registration procedure in the CS domain
Figure 5.1.3-1: Successful PN-registration in the CS domain
1. The VLR receives a location update request from a UE.
2. The VLR sends the MAP_UPDATE_LOCATION message to the HSS to request the subscription information of the UE.
3. The HSS sends the MAP_INSERT_SUBSCRIBER_DATA message back to update the VLR with the PNM subscriber data.
4. The VLR changes the status of the UE to ‘attached’and sends the MAP_NOTE_MM_EVENT message to the gsmSCF (CAMEL service for PNM) to report the mobile event.
NOTE: To support the mobility management event, the CAMEL Phase 3 or later is required.
5. The gsmSCF setups the UE registration status in the PN to ‘registered’.
6. The gsmSCF will send the UE status to the PNM AS.
NOTE: The interface between the gsmSCF and the PNM AS is unspecified.
5.1.4 PN-registration procedure for PNE other than a PN UE
Figure 5.1.4-1: UE initiates the registration on behalf of the PNE
1. The PNE sends a register request to the UE including its capabilities via the PAN internal communication means.
2. Optionally, based on the user decision, the PNE is allowed to be added to the PAN.
3. The UE sends a SIP register request on behalf of the PNE to the S-CSCF. The Register information flow contains the private user identity and the public user identity of the UE, the PNE identifier, and the PNE capabilities.
4. The S-CSCF sends the register response back to the UE.
5. UE forwards the register response to the PNE via the PAN internal communication means.
6. Based on the initial filter criteria, the S‑CSCF sends a third party Register information flow to the PNM AS.
7. The PNM AS sends a Subscribe information flow to obtain the public user identities, PNE identifier and the PNE capabilities.
8. The S-CSCF sends a Notify information flow to the PNM AS containing the public user identities, PNE identifier and PNE capabilities.
9. The PNM AS enrols the PNE identifier into the PAN.
5.2 PN-deregistration
5.2.1 General
Information shall be offered to the user by sending the status if the de-registered UE is the only default UE of the PN.
Figure 5.2.2-1 provides the procedure in the IM CN subsystem to inform the PN-user about De-registration of the only default UE in the PN.
Figure 5.2.3-1 provides the procedure in the CS domain to inform the PN-user about De-registration of the only default UE in the PN.
Figure 5.2.4-1 provides the procedure to inform the UE about De-registration of the PNE.
5.2.2 PN-deregistration procedure in the IM CN subsystem
Figure 5.2.2-1: Successful PN-deregistration procedure in the IM CN subsystem
1. To de-register, the UE sends a new Register information flow with an expiration value of zero seconds. The Register information flow contains the private user identity and the public user identity of the UE.
2. Based on the initial filter criteria, the S‑CSCF sends Register information flow with an expiration value of zero seconds to the PNM AS.
3. Optionally, the PNM AS authorizes the PN-registration by querying the HSS. It is done by sending the private user identity to the HSS. The HSS checks the public user identity/identities tied to the private user identity and sends it back to the PNM AS.
4. The PNM AS then verifies the PN-registration by comparing the public user identity/identities with the other received from S-CSCF in the Step 2. As a result of a successful verification, the PNM AS enrols the public user identity as de-registered in the data base and removes the stored configuration setting related to this specific public user identity.
5. The PNM AS sends an Unsubscribe information flow to unsubscribe to the service subscription notification of the public user identity.
6. The S-CSCF sends a Cx-Put/Cx-Pull containing the private user identity, public user identity and clear/keep S-CSCF name to the HSS base on operator choice and the HSS returns response to the S-CSCF.
7. If the UE ties to this specific public user identity registered as the only default UE, then the PNM AS sends the status to these UEs of the PN to inform this change.
5.2.3 PN-deregistration procedure in the CS domain
The PN-deregistration in the CS domain relies on the notification procedure of mobility management event and is accomplished by a notification with the event type of IMSI detach.
Figure 5.2.3-1: Procedure to inform the PN-user about the PN-deregistration of the default UE
1. After IMSI detach procedure, the VLR sends the MAP_NOTE_MM_EVENT message to the gsmSCF (CAMEL service for PNM) to report the mobile event.
2. The gsmSCF sets up the PN UE registration status in the PN to ‘Deregistered’.
3. The gsmSCF checks whether the PN UE was the only default UE in the PN or not. If it was the only default UE in the PN, the gsmSCF generates the USSD Notify message to the HSS.
4-5. The HSS forwards this message to the PN UE via MSC/VLR according to 3GPP TS 23.090 [12].
5.2.4 PN-deregistration procedure for PNE other than a PN UE
Figure 5.2.4-1: PN-deregistration procedure for PNE other than a PN UE
1. The PNE sends a de-register request to the UE via the PAN internal communication means.
2. The UE sends a register request on behalf of the PNE to the S-CSCF with an expiration value of zero seconds.
3. The S-CSCF sends the register response back to the UE.
4. The UE sends the de-register response to the PNE via the PAN internal communication means.
5. Based on the initial filter criteria, the S‑CSCF sends a De-Register information flow to the PNM AS.
6. The PNM AS then verifies the PN-deregistration by comparing the PNE identifier with the other received from S-CSCF. As a result of a successful verification, the PNM AS enrols the PNE identifier as de-registered in the data base and removes the stored configuration setting related to this specific PNE identifier.
7. The PNM AS sends a Notify information flow to the S-CSCF containing the register status of PNE.
5.3 PN-configuration
5.3.1 General
The PN-configuration procedures enable the PN-user to configure UEs as the default UE for terminating requests addressed to any UE belonging to the same PN and to configure the PN access control list. The PN-configuration can be done in three levels in IM CN subsystem and two levels in CS domain. They are a global level for all services supported by the UE capabilities and subscriptions, a per service basis for selected services supported by the UE capabilities and subscriptions, and a per service component basis for the different media of a supported service for the UE.
The following subclause describes the PN-configuration procedures in the IM CN subsystem. The signalling flow in figure 5.3.2-1 describes the information flow exchange between UE and NAF/PNM AS when the UE performs the PN-configuration.
5.3.2 PN-configuration procedure in the IM CN subsystem
Figure 5.3.2-1: Successful PN-configuration procedure in the IM CN subsystem
The signalling flow in figure 5.3.2-1 describes the signal flow between UE and NAF/PNM AS when the UE wants to configure the PN. The procedure shall only take place after a successful bootstrapping procedure (as described in 3GPP TS 33.220 [11]) in which case the bootstrapped security association has been established before Step 1.
1. UE sends a PN-configuration request to the NAF/PNM AS informing the PNM AS about its desirable settings for the PN UE redirection applications and/or the PN access control list. The PN-configuration request contains the public user identity/identities of the UE, and the PN UE names of the UEs to be configured. The relevant parameters for executing the PN UE redirection application (e.g configuration level and the priority value) may be included. The controller UE and controllee UE, and the PN access control list including either the public user identities (if reachable in the IM CN subsystem) and/or the directory number (if reachable in the CS domain) may be included.
Editor’s note: Whether routing information is needed is FFS.
2. Upon receiving this Configuration request message, the NAF/PNM AS authenticates the PN-configuration request according to the 3GPP TS 33.222 [9]. After a successful authentication, the NAF inserts the private user identity of the UE and forwards the requestto the PNM AS. The PNM AS authorizes the Configuration request message by comparing the public user identity and the PN UE name with those ones that are registered in the PN by means of the PN-registration procedure.
3. The NAF/PNM AS sends a Service Subscription Query request to the HSS in order to obtain the service subscription tied to the public user identity received in the PN-configuration request.
4. The HSS sends a Service Subscription Query response back to the NAF/PNM AS with the service subscription tied to the public user identity.
5. Upon receiving the Service Subscription Query response, the NAF/PNM AS verifies the UE capability and the service subscription of the public user identity.
6. The NAF/PNM AS sends the Service Subscription Subscribe request to the HSS.
7. The HSS sends the Service Subscription Subscribe Response to the NAF/PNM AS.
8. The NAF/PNM AS stores the configuration settings.
9. The NAF/PNM AS sends the PN-configuration response to the UE.
5.3.3 PN-configuration procedure for PNE other than a PN UE in the IM CN subsystem
Figure 5.3.3-1: PN-configuration procedure for PNE in the IM CN subsystem
The signalling flow in figure 5.3.3-1 describes the signalling flow between PNE and NAF/PNM AS through the UE when the PNE wants to configure the PN.
1. PNE sends a PN-configuration request to the UE contains the public user identity/identities of the UE, and the PN identifier of the PNE to be configured. The relevant parameters for executing the PN redirection application (e.g configuration level and the priority value) may be included. The PN access control list including either the public user identities (if reachable in the IM CN subsystem) and/or the directory number (if reachable in the CS domain) may be included.
NOTE: The interface between PNE and UE is out of scope.
2. UE forwards the PN-configuration request to the NAF/PNM AS informing the PNM AS about the desirable settings of PNE.
3. Upon receiving this Configuration request message, the NAF/PNM AS authenticates the PN-configuration request according to the 3GPP TS 33.222 [9]. After a successful authentication, the NAF inserts the private user identity of the UE and forwards the request to the PNM AS. The PNM AS authorizes the Configuration request message by comparing the public user identity and the PN UE name with those ones that are registered in the PN by means of the PN-registration procedure.
4. The NAF/PNM AS sends a Service Subscription Query request to the HSS in order to obtain the service subscription tied to the public user identity received in the PN-configuration request.
5. The HSS sends a Service Subscription Query response back to the NAF/PNM AS with the service subscription tied to the public user identity.
6. Upon receiving the Service Subscription Query response, the NAF/PNM AS verifies the PNE service subscription of the public user identity.
7. The NAF/PNM AS sends the Service Subscription Subscribe request to the HSS.
8. The HSS sends the Service Subscription Subscribe Response to the NAF/PNM AS.
9. The NAF/PNM AS stores the configuration settings.
10. The NAF/PNM AS sends the PN-configuration response to the UE.
11. UE forwards the PN-configuration response to the PNE.
5.4 PN-deconfiguration
5.4.1 General
The PN-deconfiguration procedure enables the PN-user to deconfigure the default UE of a PN. Corresponding to the configuration procedure described in subclause 5.3, the PN-deconfiguration can be done in three levels in IM CN subsystem and two levels in CS domain.
The following subclauses describe the PN-deconfiguration procedure in the IM CN subsystem.
5.4.2 PN-deconfiguration procedure in the IM CN subsystem
Figure 5.4.2-1: Successful PN-deconfiguration procedure in the IM CN Subsystem
The signalling flow in figure 5.4.2-1 describes the signal flow between UE and NAF/PNM AS when the UE wants to deconfigure the PN. The messaging shall only take place after a successful bootstrapping procedure (as described in 3GPP TS 33.220 [11]) in which case the bootstrapped security association has been established before Step 1.
1. In order to remove its configuration settings for the PN UE redirection applications from the PN, a UE sends a Deconfiguration request message to the PNM AS containing the public user identity/identities of the UEs to be deconfigured. Additionally, other relevant parameters for executing the PN UE redirection application such as the configuration level and the priority value can be included.
2. Upon receiving the PN-deconfiguration request, the NAF/PNM AS authenticates the PN-deconfiguration Request according to the 3GPP TS 33.222 [9]. After a successful authentication, the NAF inserts the private user identity of the UE and forwards it to the PNM AS. The PNM AS authorizes the PN-deconfiguration request by comparing the public user identity with those ones that are registered in the PN by means of the PN-registration procedure.
3. The PNM AS sends the Unsubscribe request to the HSS.
4. The HSS sends the Unsubscribe response to the PNM AS.
5. The PNM AS removes the stored configuration setting.
6. The PNM AS sends the PN-deconfiguration response to the UE.
7. If the UE ties to this specific public user identity registered as the only default UE, then the NAF/PNM AS sends the Status message request to these UEs of the PN to inform this change.
5.5 PN-query
5.5.1 General
Figure 5.5.2-1 shows a successful PN-query procedure that is used by the PN-users to enquiry their PN settings information which is stored in the PNM AS after performing the PN-registration and PN-configuration procedures.
5.5.2 PN query procedure
The PN setting information belonging to a PN-user can be categorized into:
– information about the registered public user identities,
– settings for PN UE redirection, such as the default UEs, service level settings and redirection priority.
– settings for the PN access control, such as a PN access control list.
Figure 5.5.2-1: Successful PN query procedure in the IM CN subsystem
The signalling flow in figure 5.5.2-1 describes the signal flow between UE and NAF/PNM AS when the UE wants to query the PN settings. The procedure shall only take place after a successful bootstrapping procedure (as described in 3GPP TS 33.220 [11]) in which case the bootstrapped security association has been established before Step 1.
1. UE sends a PNquery request to the NAF/PNM AS in order to obtain the PN setting information classified above for the PNM applications by including the public user identity/identities of the UEs.
2. Upon receiving the PN-query request, the NAF/PNM AS authenticates the PN-query request according to the 3GPP TS 33.222 [9]. After a successful authentication, the NAF/PNM AS inserts the private user identity associated with the public user identity/identities of the UE and forwards the message to the NAF/PNM AS. The NAF/PNM AS authorizes the PN-query request by comparing the public user identity with those ones that are registered in the PN by means of the PN-registration procedure.
3. The NAF/PNM AS sends the PNquery response message to the UE containing the PN settings information for the PNM applications as asked by the UE.