4 PNM overview

23.2593GPPPersonal Network Management (PNM)Procedures and information flowsRelease 17Stage 2TS

4.1 General

Personal Network Management (PNM) is a home network-based application and provides the home network-based management of Personal Network (PN) consisting of multiple devices belonging to a single PN-user, as described in 3GPP TS 22.259 [1]. These home network-based management functions cover the configuration of the PN-user’s PN such as PN-registration, PN-deregistration, PN-configuration, PN-deconfiguration and PN-query procedures, and the operation of the PN-user’s PN. Functionality enabled by the PNM comprises the PN UE redirection and the PN access control applications as described in 3GPP TS 22.259 [1]. In order to provide the PN UE redirection and the PN access control applications, the PNM is realized as an AS in the IM CN subsystem as described in 3GPP TS 23.002 [2] and as a CAMEL service in the CS domain as described in 3GPP TS 23.078 [4].

4.2 PN access control concepts

The PN access control is one of the PNM applications specified in 3GPP TS 22.259 [1] that enables PN-users to exercise access control to restrict accesses to certain UE(s) of their PNs. The PN 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 this regard the PN behaves similar to a CUG as specified in 3GPP TS 22.085 [13] and 3GPP TS 23.085 [14], with Outgoing Access and whether Incoming Access is allowed for the PN UE is dependent on the PN access control list for that PN UE.

In order to perform such PN access control the PN-users need to configure a PN access control list for each UE of the PN. The configuration can be done either in a static or a dynamic way. Besides other additional information, the PN access control list of a UE within a PN contains all identities (e.g., a SIP URI) which are permitted to be used to initiate sessions to that UE. In this document, the UE of a PN that is used by the PN-user to exercise access control is referred to controller UE, whereas the UE of the PN, over which an access control is enabled, is referred to controllee UE. The controller UE of a PN-user’s PN is assigned by provisioning and the controller UE can configure any UE of the PN as controllee UE. The PN access control list of the controllee UE is only configurable by the controller UE.

Figure 4.2-1: Relationship of various service profiles in PN access control

An example of the service profiles configuration for PN access control is shown in the above figure 4.2-1. The arrows indicate the direction of control. Some of the aspects involved are:

– A PN-user’s PN consists of two UEs, i.e., UE 1a and UE 1b, where UE 1b is the controllee UE and UE 1a is the controller UE.

– The service profile of UE 1b is referred to as the controllee UE Service Profile.

– The service profile of UE 1a is referred to as the controller UE Service Profile.

– The assignment of controller UE service profile is done during provisioning.

– Access control of UE 1b by UE 1a is performed with the help of a SIP Application Server (AS), referred to as PNM AS.

– From UE 1a, the PN-user configures a PN access control list that contains details of PN access control regarding UE 1b’s service profile. This configuration is done over the Ut interface. For example: this PN access control list can contain a list of UE identities that are allowed to initiate sessions with UE 1b.

– The PNM AS executes the actual PN access control procedures.

– The PNM AS performs PN access control by utilizing the PN access control list.

– If inadequate information present in the access control list to enable PN access control, the PNM AS can query the controller UE about the information with how to precede the received initial request.