PNE Networks enable functions for the management and direct accessibility of the physically separated components of a UE, i.e. TEs and MEs..
PNE Network functions comprise the management and communication of these PNEs within a PN as well as the extension of the PN UE Redirecting application and the PN access control function to include the redirection to UE and PAN components.
Service requirements cover the management of UE(s), as well as UE components and TE(s), ME(s) or MT(s) and belonging to the same PAN(s) (see Figure 2).
A UE including a USIM, can comprise physically separated TEs and can also have connections with other MTs or MEs (e.g., a PDA, music player, laptop, camera, headset, etc.). The devices are connected through short-range wired or wireless connections (when they are in close proximity) and form a small network, called a PAN (Personal Area Network). The owner of the PNE that holds the USIM controls the PAN.
PNEs of a PAN without / not requiring a USIM, may have the need to access services provided by the PLMN or to communicate with another entity through the PLMN. In this case PNEs must be authenticated and authorized by using the USIM associated with the PLMN (i.e., a single USIM authority shall be shared by all the PNEs of the PAN that access services provided by the PLMN).
For managing a PAN means are required to identify a particular PNE within a PAN. The PNE identifiers enable connections between selected PNEs and directing of terminating services to a particular PNE.
Thus PNM identifiers are divided into subscriber identities and PNE identities. 3GPP private subscriber identifiers are the unique IMSI and the unique IMS Private User Identies stored in USIM and ISIM. The subscriber identities are used, for example, for registration, authorization, administration, and accounting purposes in the network. The PNE Identifiers are used to identify devices within a PN and may be used, for example, for blacklist and Device Management purposes. When the PNE is a ME, the IMEI should be reused as PNE identifier unless for security reasons or other reasons this is not feasible. In contrast to MEs the PNE identifiers of TEs are PNM-specific and have little network security relevance as TE have no own radio access means.
Annex A.3 shows two use cases where users access a PLMN from their PANs.
The PN shall support the combination and separation of PANs.
The Personal Network may comprise more than one UE or PAN. Each entity belonging to a Personal Network is generally termed as a PNE. The PNE may be a single device or a group of devices. The Personal Network from a user's perspective is his own network. Any of his PNEs may connect to each other, whereby the user may restrict public access via means provided by PNM. Personal Network Elements may not have public user IDs (E.g. MSISDN or URI), and therefore "other" users are not able to directly address data to these TEs.
The PNE Redirecting application is based on the PN UE Redirecting Service. In contrast to the PN UE Redirecting Service the PNE Redirecting application shall not only allow to activate/deactivate UEs but is able to direct data to particular TEs of the UEs or to connected MEs. Thus a PNE is not limited to UEs and it is possible to handle particular components within a UE or PAN as PNE.
Annex A.1 shows a use case describing aspects of PNE-PNE connection.