22.2593GPPService requirements for Personal Network Management (PNM)Stage 1TS
4.1 General description
Personal UE Network features enable the management of multiple UEs belonging to a single PN-User. In particular, customer needs who own more than one terminal and subscription are addressed, e.g. ordinary handset for telephony, car phone, PDA for emails when on the move, data card with laptop for work when in semi-stationary mode. Although those devices are mainly held for a particular usage, many are able to support more than one sort of services, e.g. telephony is supported by all but the data card. Personal UE Networks are not aware of the presence of other PNEs belonging to a user.
Functionality enabled by Personal UE Networks comprises PN UE redirection and PN Access Control.
Registration, configuration and interrogation procedures for PNM are supported via IMS capable PN UEs, via a web client or by administrative procedures.
4.2 PN UE Redirecting application
Customers may not carry always their full set of "gadgets", but still want to be reachable. Currently management of all the terminals for the PN-User by setting forwarding options, switch on and off terminals, providing partners with multiple addresses is not very customer friendly.
Fig 1: UEs managed by PN e.g. UE Redirecting application
4.2.1 Requirements for PN UE redirecting application
– PNM shall be provided to a subscription upon customers request via administrative procedures.
– PNM shall be withdrawn upon customer request or for administrative reasons via administrative procedures.
– The PN-Users shall be able to register and deregister UEs to their PN.
– Successful registration shall add the UE as new Personal Network Element to the Personal Network. The information on the UE and the public user identities belonging to the UE shall be written to the service profile in the network. A deregistration procedure shall be performed to remove a registered UE from the Personal Network.
– Each UE shall only be registered in one PN and the network shall reject the registration request of a UE that is already registered in another PN.
– The PN-Users shall be able to "activate" a certain UE of their PN as the default UE for terminating services addressed to any of the UEs belonging to the PN. Activation shall be possible
– On a global level for all services supported by the UE capabilities and subscription
– On a per service basis for selected services supported by the UE capabilities and subscription
– On a per service component basis for the different media of a supported service (in line with )
– The PN-Users shall be able to configure priorities of a UEs list with priority for terminating a specific service.
– Note: the priority may be based on parameters such as time, device capability and PN-User choice.
– The PN-User shall be able to interrogate the PNM network database for the current PN-User settings of their own PN.
– The registration and configuration procedures shall include a validation and update of identities and capabilities associated with the UE. For this reason, registration and activation of a UE shall only be done for UEs that are currently attached/registered to the network. The UE shall either send an registration/activation request to the network or the network shall "invite" the UE based on a request received from another UE belonging to the PN. Registration and activation may be also provided via administrative procedures.
– The UE or the network shall deny activation as default UE for terminating a particular service or service component, in case the UE does not provide the capability or the subscription to terminate the service.
– Deactivation and deregistration should not always require the involvement of the UE affected by the setting. However the network shall only process deactivation and deregistration requests from UEs belonging to the same PN.
– A UE performing activations shall have the capability to perform the deactivations for these settings.
– For terminating services without an activated UE, the services shall not be redirected but shall be terminated by the addressed target UE. Information shall be offered to the PN-User when the only active device for terminating a service is deactivated.
– In case more than one device is activated for a terminating service, e.g. IMS devices with the same Public User Identity, the service should be directed to all devices that are currently reachable for the network (PS attached or IMS registered). It shall be possible to make the PN-User aware on charging implications caused by activation of more than one UE for directing of the same service.
– If activations are configured for one or more media types of a service then the overall service directing setting shall be overwritten for directing these service components.
– Directing media of a service to different devices should be up to the choice and responsibility of the PN-User. For instance, in case of synchronized media the redirection to different devices may result in a loss of synchronization.
– A new activation overrides the previous activation status when successful.
– Deregistration of active UEs shall comprise the global deactivation of the UEs.
– It shall be possible to allow two sets of activation settings. One set is always present and contains the default configuration. On a temporary basis, a second set of activation settings is configured. The temporary activations shall provide a means for saving and restoring current activation settings. While temporary activations are switched on, these settings shall override the non-temporary configuration.
– The network shall assume that the non-temporary settings are still valid after fallback from temporary to non-temporary activation settings. For this reason, it shall be possible for the UE to access and change temporary as well as non-temporary settings.
– If capabilities or subscriptions of an active UE change and activated services are no longer supported by the UE, e.g. TEs providing these capabilities are removed, then the UE shall deactivate the affected services and offer appropriate information to the user and the PN service.
– It shall be possible for a UE to offer capability lists to the PNM service, where the capability list contains the capabilities that the UE is capable of terminating or is interested in receiving updates regarding them.
– It shall be possible for UEs of the PN to update PN configuration after an attachment/registration of the UE to the network.
– PNM settings may comprise current UE capabilities and redirection settings of a PN. The PNM service shall update the PNM settings to the UEs, selectively based on their respective capability lists, when other UE capabilities of the PN change.
– Means shall be provided to enable redirection to a particular UE for dealing with situations where UEs share the same Public User Identity.
– Terminating services shall only be redirected if the redirection does not cause systematic misbehaviour of user devices or the network (e.g. SMS is one service where redirection shall not be applied if any over-the-air management of the target UE would be prevented.)
– The PNM service shall interwork with CS-Domain call forwarding  and IMS session redirecting  in a way that no collisions of contradicting redirections occur in the network and the redirection of data remains transparent for the user. The considered interworking scenarios shall include the redirection of IP Multimedia sessions caused by any of the listed events or conditions .
– The UE Redirecting application shall be applicable to terminating services in the CS-domain, PS-domain, and IMS subsystem.
– Originating services shall not be affected by the default settings.
– The services that are made available for redirection shall be consistent with existing service identifiers, e.g. IMS communication service identifier , or service grouping, e.g. basic service groups .
– Redirection of terminating services and service media shall be done for only public user identities and addresses belonging to a UE of the PN.
– The PN-User shall be able to exclude specific public user identities and addresses of the PN from data redirection.
Note: In the above requirements, registration means the registration of UE and of its public identities to the PN. The registration procedures of the UE to the PLMN remain unaffected.
4.2.2 Usability requirements forPN UE redirection application
The following PNM procedures shall be at least available via one of the UEs belonging to the actual PN of the PN-User and shall be realized in a user friendly and secure manner:
– Registration of a UE
– Deregistration of a UE
– Activation of a UE for a specific service or service component
– Global activation of a UE for all services, as far as supported
– Setting up of capability lists as requested by a user
– Interrogation of PNM database
4.2.3 Security for PN UE redirection application
– Registration of UEs to a PN shall require the consent of the subscriber by appropriate means, e.g. an ”invite" function, preventing intended/unintended access by unauthorized UEs.
4.2.4 Charging for PN UE redirection application
– All charges for terminating services shall be levied to the "active" UEs, even when originally addressed to another UE belonging to the PN.
– It shall be possible to raise registration/deregistration and activation/deactivation fees.
4.2.5 Interaction with supplementary services
– For terminating services invocation of Supplementary Services applicable to the active UE shall take precedence over invocation of Supplementary Service applicable to the called UE.
– There is no impact on the registration, erasure, activation, deactivation of Supplementary Services.
4.3 PN access control
– Private networks may consist of UEs which are only privately accessed, that is each UE may be accessed only by other UEs of the PN. The PN-User may additionally modify the access levels of each UE of the PN to be public or private.
– In order to allow external UEs or Guest UEs to access these UEs, the PNM provides access control procedures. The PNM shall provide registration and authentication mechanisms for guest device access.
Note 1: Authentication refers to verifying the registration status of a certain guest UE by the PNM.
Note 2: It is assumed that guest UE access to a UE in a PN is routed via the PLMN Network. In particular control of access to a UE via local interfaces is outside the scope of this specification.
4.3.1 Requirements for PN access control
– The PN-User may register up to <n> UEs to be private to the PN, whereby public access to these devices may be restricted.
– The PN-User is able to register up to <m> UE public identities not owned by him as registered callers that are allowed to initiate sessions with the private UEs of the PN, and these UEs containing these registered public identities are referred to as Guest UEs.
– The PN-User may nominate a UE as the default UE for access control. This UE shall have the access rights to register/deregister private UEs and guest UEs.
– The registration of Guest UE may be performed by the default UE for access control and enabled dynamically (querying during session initiation procedures using public identity of caller) or statically (using PN specific database) by PNM procedures.
– In case the user has another UE in the PN as the default UE for redirection, then the querying shall be directed to the default UE for redirection.
4.3.2 Usability requirements for PN access control
– Registration of a Guest UE
– Deregistration of a Guest UE
– PN access level settings for a particular UE of the PN to be public / private
– PN Access control settings are stored at PNM database, for a particular Guest UE e.g unlimited access of PN by close friends, limited access by acquaintances.
Note: In the above requirements, public identity may be substituted in place of UE. Example, either a public identity or a UE may be registered into a PN.
4.3.3 Security for PN access control
– PN access control settings refer to the PN-User providing different access control settings of his PN for different Guest UEs / Public Identity.
4.3.4 Charging for PN access control
Note: Currently no additional charging issues have been identified, but this topic may be studied further.