A.2 Introduction

24.2593GPPPersonal Network Management (PNM)Release 17Stage 3TS

A.2.1 General

The signalling flows provided in this annex follow the methodology developed in 3GPP TS 24.228 [10]. The following additional considerations apply:

a) 3GPP TS 24.228 [10] shows separate signalling flows with no configuration hiding between networks, and with configuration hiding between networks. There is no personal network management specific functionality associated with this hiding, and therefore such separate signalling flows are not shown in the present document;

b) 3GPP TS 24.228 [10] does not show the functionality between the S-CSCF and the AS. As personal network management depends on the functionality provided by various AS, the signalling flows between S-CSCF and AS are shown in the present document;

c) 3GPP TS 24.228 [10] breaks down the functionality of the various CSCFs. Such intervening activity in the CSCFs is in general not relevant to showing the functionality within personal network management, and therefore the CSCFs are often collapsed into a single entity labelled "Intermediate IM CN subsystem entities";

d) where entities are combined as in c) above, and the signalling flow is directed to such a combined entity, the contents of the signalling flow represent the contents of the sending entity except when otherwise stated;

e) where entities are combined as in c) above and the signalling flow originates at such a combined entity, the contents of the signalling flow represent the contents of the receiving entity except when otherwise stated;

f) within the CS domain, both ISUP and BICC can be used. The signalling flows represent only the ISUP signalling flows, and the BICC signalling flows (which can be assumed to be similar with no additional PNM specific content) are not shown; and

g) additional functionality from 3GPP releases 6, 7 and 8 over and above that shown in 3GPP TS 24.228 [10] is incorporated in these.

A.2.2 Key required to interpret signalling flows

The key to interpret signalling flows specified in 3GPP TS 24.228 [10] subclauses 4.1 and 4.2 applies with the additions specified below:

– Consistent with the conventions used in 3GPP TS 24.228 [10] home1.net is used for the home network of the originating user and home2.net is used for the home network of the terminating user. In registration and configuration flows the PN UE and PNM network elements are considered to be in home1.net, however in scenarios such as PN redirection and PNM access control where the PNM elements are in the terminating network the PN UE and PNM network elements are considered to be in home2.net. Therefore in some flows identities shown as home2.net are equivalent to the identities shown as home1.net in other flows and as described further below.

For signaling flows for PN-registration (see subclause A.3.2) and PN-configuration (see subclause A.3.3) the following applies:

– pnmas.home1.net:1234 represents the Internet host and port number of the PNM AS, which can be obtained by a PN UE from the address (URI) of the resource http://pnmas.home1.net:1234/service.

– PN_user1_public1@home1.net, PN_user1_public2@home1.net, etc. represent the public user identities configured for a PN-user for the PN UE#1. PN_user2_public1@home1.net, PN_user2_public2@home1.net, etc. represent the public user identities configured for a PN-user for the PN UE#2, etc. PN_user_public@home1.net represents the shared public user identity.

– PN_user1_private@home1.net represents the private user identity configured for a PN-user for PN UE#1. PN_user2_private@home1.net represents the private user identity configured for a PN-user for PN UE#2, etc.

– PN_user1_friend_public1@home1.net, PN_user1_friend_public2@home1.net etc represent the public user identities of a PN access control list configured for PN UE#1. PN_user2_friend_public1@home1.net, PN_user2_friend_public2@home1.net etc represent the public user identities of a PN access control list configured for PN UE#2, etc.

– PN_user1_public1_old and PN_user1_public1_new represent the old and the new PN UE names related to the public user identity PN_user1_public1@home1.net, PN_user2_public1_old and PN_user2_public1_new represent the old and the new PN UE names related to the public user identity PN_user2_public1@home1.net.

For signaling flows for PN UE redirection (see subclause A.3.4), PN access control (see subclause A.3.5) and inter-domain networking (see subclause A.3.6) the following applies:

– PN_user1_public@home2.net, PN_user2_public@home2.net, etc. represent the public user identities for the PN UEs;

– user1_public1@home1.net represents a user outside of the personal network originating a session to a user within the personal network.

In order to differentiate between messages for HTTP, SIP, Diameter and media flows over CS and PS connections, the notation in figure A.2.2-1 is used.

Figure A.2.2-1: Signalling flow notation