A.3.5 Signalling flows for PN access control

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

A.3.5.1 PN access control procedure in IM CN subsystem

Figure A.3.5.1-1 details the signalling flows for PN access control in the IM CN subsystem.

In the following flow UE#2a is the PN controller UE and UE#2b is the PN controllee UE.

Figure A.3.5.1-1: Signalling flow for PN access control procedure in IM CN subsystem

The steps prior to step 1 are according to the standard procedures specified in 3GPP TS 24.228 [10].

1. INVITE#1 (I-CSCF#2 to S-CSCF#2)

I-CSCF-2 forwards the INVITE message to S-CSCF#2 after invocation of a location Query.

Table A.3.5.1-1: SIP INVITE request (I-CSCF#2 to S-CSCF#2)

INVITE sip:PN_user2b_public1@home2.net SIP/2.0

Via:SIP/2.0/UDP icscf2.home2.net;branch=z9hG4bK871y12.1,

SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1,

SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.1,

SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7

Max-Forwards: 65

Route: <sip:scscf2.home2.net;lr>

Record-Route:<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited.net;lr>

P-Asserted-Identity: "John Doe" <sip:user1_public1@home1.net>

Privacy: none

From: <sip:user1_public1@home1.net>;tag=157893

To: <sip:PN_user2b_public1@home2.net>

Cseq: 127 INVITE

Call-ID:131243vdse

Supported: precondition,100rel,gruu,199

Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"

P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel

Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"

Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE

Accept: application/sdp, application/3gpp-ims+xml

Content-Type: application/sdp

Content-length: (…)

v=0

o=- 2987933615 2987933615 IN IP6 5555::aaa:bbb:ccc:ddd

s=-

c=IN IP6 5555::aaa:bbb:ccc:ddd

t=0 0

m=audio 3456 RTP/AVP 97 96

a=tcap:1 RTP/AVPF

a=pcfg:1 t=1

b=AS:25.4

a=curr:qos local none

a=curr:qos remote none

a=des:qos mandatory local sendrecv

a=des:qos none remote sendrecv

a=inactive

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; maxframes=2

a=rtpmap:96 telephone-event

2. 100 Trying

S-CSCF#2 responds to the INVITE#1 request with a 100 Trying provisional response.

Table A.3.5.1-2: SIP 100 Trying

SIP/2.0 100 Trying

Via:SIP/2.0/UDP icscf2.home2.net;branch=z9hG4bK871y12.1,

SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1,

SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.1,

SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7

From:

To:

Call-ID:

CSeq:

Content-Length: 0

3. Evaluation of Initial Filter Criteria

S-CSCF#2 validates the service profile of this subscriber and evaluates the initial filter criteria.

4. INVITE#1(S-CSCF#2 to PNM AS)

S-CSCF#2 forwards the INVITE#1 request to the PNM AS based upon the initial filter criteria (IFCs).

Table A.3.5.1-4: SIP INVITE request (S-CSCF#2 to PNM AS)

INVITE sip:PN_user2b_public1@home2.net SIP/2.0

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP icscf2.home2.net;branch=z9hG4bK871y12.1,

SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1,

SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.1,

SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7

Max-Forwards: 64

Route: <sip:pnmas.home2.net;lr>

Record-Route: <sip:scscf2.home1.net;lr>,<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

Supported:

Accept-Contact:

P-Asserted-Service:

Contact:

Allow:

Accept:

Content-Type:

Content-length: (…)

5. 100 Trying

The PNM AS responds to the INVITE#1 request with a 100 Trying provisional response.

Table A.3.5.1-5: SIP 100 Trying

SIP/2.0 100 Trying

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP icscf2.home2.net;branch=z9hG4bK871y12.1,

SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1,

SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.1,

SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7

From:

To:

Call-ID:

CSeq:

Content-Length: 0

6. PN access control

The PNM AS invokes the Private network service logic. As user1_public1@home1.net is not on the <PNAccessControlList> of PN_user2b_public1@home2.net the PN access controller needs to be contacted.

7. INVITE#2 (PNM AS to S-CSCF#2)

The PNM AS generates a new INVITE request message called INVITE#2 and sends it to S-CSCF#1 in order to interact with the PN controller UE.

Table A.3.5.1-7: SIP INVITE request (PNM AS to S-CSCF#2)

INVITE sip:PN_user2a_public1@home2.net;target=PN_user2b_public1@home2.net SIP/2.0

Via: SIP/2.0/UDP pnmas.home2.net;branch=z9hG4bwt871y12.1

Max-Forwards: 70

Route: <sip:scscf2.home2.net;lr>

P-Asserted-Identity: "John Doe" <sip:user1_public1@home1.net>

Privacy:

From: <sip:pnmas.home1.net>;tag=r3rw33

To: <sip:PN_user2a_public1@home2.net>

Cseq:

Call-ID:

Supported: precondition, 100rel, 199, histinfo

Contact: <sip:pnmas.home2.net>

History-Info: <sip:PN_user2b_public1@home2.net>;index=1,

<sip:PN_user2a_public1@home2.net;target=PN_user2b_public1@home2.net>;index=1.1

Accept-Contact:*;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.pnm-controller"

P-Asserted-Service:

Allow:

Accept:

Content-Type:

Content-length: (…)

Request-URI: contains the URI of the PN controller UE (PN_user2a_public1@home2.net) obtained from the <PNController> element along with the target uri-parameter which contains the URI from the original Request-URI (PN_user2b_public1@home2.net).

P-Asserted-Identity: the identity of the originator ("John Doe" <sip:user1_public1@home1.net>).

From: contains the SIP URI of the PNM AS (sip: pnmas.home1.net).

To: contains the URI of the PN controller UE ( PN_user2a_public1@home2.net).

Supported: contains the following option tags: precondition, 100rel, 199, histinfo.

Contact: a SIP URI that contains the IP address or FQDN of the PNM AS.

History-Info: contains the URIs from the original Request-URI (PN_user2b_public1@home2.net) and the URI of the PN controller UE (PN_ user2a_public1@home2.net).

Accept-Contact: contains the g.3gpp.iari-ref media feature tag with the IARI value "urn%3Aurn-7%3A3gpp-application.ims.iari.pnm-controller".

8. 100 Trying

S-CSCF#2 responds to the INVITE#2 request with a 100 Trying provisional response.

Table A.3.5.1-8: SIP 100 Trying

SIP/2.0 100 Trying

Via: SIP/2.0/UDP pnmas.home2.net;branch=v7hG4bwt171y12.1

To:

Call-ID:

CSeq:

Content-Length: 0

9. INVITE#2 (S-CSCF#2 to P-CSCF#2a)

S-CSCF#2 forwards the INVITE#2 request to P_CSCF#2a.

Table A.3.5.1-9: SIP INVITE request (S-CSCF#2 to P-CSCF#2a)

INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP pnmas.home2.net;branch=z9hG4bwt871y12.1

Max-Forwards: 69

Route: <sip:pcscf2a.visited2.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

Supported:

Contact:

History-Info:

Accept-Contact:

P-Asserted-Service:

Allow:

Accept:

P-Called-Party-ID: <sip:PN_user2a_public1@home2.net;target=PN_user2b_public1@home2.net>

Content-Type:

Content-length: (…)

10. 100 Trying

P-CSCF#2a responds to the INVITE#2 request with a 100 Trying provisional response.

Table A.3.5.1-10: SIP 100 Trying

SIP/2.0 100 Trying

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP pnmas.home2.net;branch=z9hG4bwt871y12.1

To:

Call-ID:

CSeq:

Content-Length: 0

11. INVITE #2 (P-CSCF#2a to UE-2a)

P-CSCF#2a sends the INVITE#2 to UE-2a (controller UE)

Table A.3.5.1-11: SIP INVITE request (P-CSCF#2a to UE-2a)

INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP pcscf2a.visited2.net;branch=z9hG4bK240f34.1,

SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP pnmas.home1.net;branch=k9hG4bwt871y12.1

Max-Forwards: 68

Record-Route: <sip:pcscf2a.visited2.net;lr>,

<sip:scscf2.home2.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

Require:

Supported:

Contact:

History-Info:

Accept-Contact:

P-Asserted-Service:

Allow:

Accept:

P-Called-Party-ID:

Content-Type:

Content-length: (…)

12. 100 Trying

UE-2a responds to the INVITE#2 request with a 100 Trying provisional response.

Table A.3.5.1-12: SIP 100 Trying

SIP/2.0 100 Trying

Via:SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP pnmas.home2.net;branch=v7hG4bwt171y12.1

To:

Call-ID:

CSeq:

Content-Length: 0

13. PNM Privacy Decision

Based upon the IARI value the PN controller UE invokes the PN controller application. The PN controller application provides the originators identity from the P-Asserted-Identity header, the PN controllee UE identity from the target URI-parameter in the Request-URI to the user and provides the option to the user to either:

1. Forward the session to the controllee UE

2. Reject the session

3. Accept the session

In the example the user determines to forward the sesssion to the controllee UE.

14. 302 Moved Temporarily

The PN controller UE sends a SIP 302 Moved Temporarily response to pcscf2a.visited2.net.

Table A.3.5.1-14: SIP 302 Moved Temporarily

SIP/2.0 302 Moved Temporarily

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK240f34.1,

SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP pnmas.home2.net;branch=k9hG4bwt871y12.1

From:

To:

Call-ID:

CSeq:

History-Info: <sip:PN_user2b_public1@home2.net>;index=1,

<sip:PN_user2a_public1@home2.net;target=PN_user2b_public1@home2.net>;index=1.1

Contact: <sip:PN_user2b_public1@home2.net>

Content-Length:0

Contact: a URI that contains the address of the PN controllee UE (PN_user2b_public1@home2.net).

History-info: contains the URIs from the History-Info header in the original INVITE (PN_ user2b_public1@home2.net and PN_user2a_public1@home2.net).

15. 302 Moved Temporarily

P-CSCF#2a forwards the 302 Moved Temporarily response to S-CSCF#2.

Table A.3.5.1-15: SIP 302 Moved Temporarily

SIP/2.0 302 Moved Temporarily

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP pnmas.home2.net;branch=k9hG4bwt871y12.1

From:

To:

Call-ID:

CSeq:

History-Info:

Contact:<sip:PN_user2b_public1@home2.net>

Content-Length:0

16. 302 Moved Temporarily

S-CSCF#2 forwards the 302 Moved Temporarily response to the PNM AS.

Table A.3.5.1-16: SIP 302 Moved Temporarily

SIP/2.0 302 Moved Temporarily

Via: SIP/2.0/UDP pnmas.home2.net;branch=k9hG4bwt871y12.1

From:

To:

Call-ID:

CSeq:

History-Info:

Contact: <sip:PN_user2b_public1@home2.net>

Content-Length:0

17. PN UE redirection

Upon receiving the 302 Moved Temporarily response from the controller UE, the PNM AS determines the session is to be redirected to the controllee UE.

18. INVITE#3 (PNM AS to S-CSCF#2)

The PNM AS forwards the Originating INVITE message to S-CSCF#2.

Table A.3.5.1-18: SIP INVITE request (PNM AS to S-CSCF#2)

INVITE sip:PN_user2b_public1@home2.net SIP/2.0

Via:SIP/2.0/UDP pnmas.home2.net;branch=z9hG4bwt871y12.1

SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1,

SIP/2.0/UDP icscf2.home2.net;branch=z9hG4bK871y12.1,

SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1,

SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.1,

SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7

Max-Forwards: 63

Route: <sip:scscf2.home2.net;lr>

Record-Route: <sip:scscf2.home1.net;lr>,<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited.net;lr>

P-Asserted-Identity: "John Doe" <sip:user1_public1@home1.net>

Privacy:

From: <sip:user1_public1@home1.net>;tag=157893

To: <sip:PN_user2_public1@home2.net>

Cseq:

Call-ID:

Supported: precondition, 100rel, 199, histinfo

Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"

History-Info: <sip:PN_user2b_public1@home2.net>;index=1,

<sip:PN_user2a_public1@home2.net;target=PN_user2b_public1@home2.net>;index=1.1,

<sip:PN_user2b_public1@home2.net?Reason=SIP;cause=302>;index=1.2

Accept-Contact: *;g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"

P-Asserted-Service:

Allow:

Content-Type:

Content-length: (…)

P-Asserted-Identity: the identity of the originator ("John Doe" <sip: user1_public1@home1.net>).

From: contains the SIP URI of the PNM AS (sip: pnmas.home1.net).

To: contains the URI of the PN controller UE (PN_user2a_public1@home2.net).

Supported: contains the following option tags: precondition, 100rel, 199, histinfo.

Contact: the contents of the Contact header in the original INVITE (<sip: user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>).

History-info: contains the URIs from the History-Info header in the 302 Moved Temporarily response (PN_user2b_public1@home2.net and PN_user2a_public1@home2.net) with the addition of the URI of the PN controllee UE (PN_user2b_public1@home2.net) from the Contact header in the 302 Moved Temporarily response along with the reason code 302.

Accept-Contact: contains the g.3gpp.icsi-ref media feature tag with the ICSI value from the Accept-Contact header in the original INVITE ("urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel").

19-34. These flows follow the standard session establishment procedures specified in 3GPP TS 24.228 [10].

A.3.5.2 PN access control procedure in CS domain.

Figure A.3.5.2-1 provides the signalling flows for the PN access control procedure in the CS domain. PN access control services deal with a user having access control over its personal network.

Figure A.3.5.2-1 Signalling flow for PN access control in the CS domain

1. ISUP IAM

A Call Request containing an IAM message arrives at the GMSC.

Specifically for this signalling flow, the IAM includes:

– Calling Party number =12134587692

– Called Party Number parameter = [(Numbering plan identifier = ISDN/telephony numbering plan), (type of number = international number), (Number digits = 15346789043)]

2. MAP Send Routing Information (SRI)

On receipt of the incoming call request, the GMSC queries the HSS for routing information.

3. Retrieval of PNM subscriber information

The HSS identifies the subscriber as a PNM subscriber and provides the configured terminated CAMEL subscription information (T-CSI) towards the GMSC in the SRI-ACK.

4. MAP Send Routing Information Acknowledgement (SRI ACK)

The HSS returns the T-CSI information element which includes the gsmSCF address to the GMSC in response to the query for routing information (SRI).

5. CAMEL IDP (GMSC to gsmSCF)

The GMSC#1 triggers a CAMEL activity which results in sending a CAMEL IDP message to the GSM Service Control Function (gsmSCF). The CAMEL IDP message contains at least:

– the calling party number;

– the called party number;

– the type of call; and

– information from the T-CSI IE received by the GMSC#1 in the SRI ACK from the HSS. This includes the CAMEL service key.

6. PN access control

The gsmSCF performs the PN access control. Since the calling party is not configured in the PN access control list, the gsmSCF needs to ask the controller UE to grant the access to the calling party.

7-8. MAP-UNSTRUCTURED-SS-REQUEST (gsmSCF to HSS)

As part of this process the gsmSCF starts the timer to supervise the call establishment and sends a MAP-UNSTRUCTURED-SS-REQUEST message to the HSS. The message contains the following information.

USSD String:- Calling Number 12134587692 and called Number 15346789043.

9. MAP-UNSTRUCTURED-SS-REQUEST (HSS to MSC/VLR)

The HSS relays the USSD request message to the MSC/VLR. It contains the following information.

USSD String:- Calling Number 12134587692 and called Number 15346789043.

10. REGISTER (MSC/VLR to controller UE)

This message is used between MSC/VLR and the UE to get the access granted for the incoming call. It contains the following information.

Facility (Invoke=UNSTRUCTURED-SS-REQUEST(USSD-Data-Coding-Scheme, USSD String))

11-13. When the timer expires, the gsmSCF generates a play announcement message containing Tone ID and Duration parameters as specified in 3GPP TS 29.078 [13].

14. FACILITY (controller UE to MSC/VLR)

The controller UE will send the FACILITY message back to the MSC/VLR. It contains the following information.

Facility (ReturnResult=UNSTRUCTURED-SS-REQUEST (USSD-Data-Coding-Scheme, USSD String)) which inform that the call is accepted.

15-16. MAP-UNSTRUCTURED-SS-REQUEST-Ack (MSC/VLR to HSS)

After receiving the FACILITY message from the controller UE, the MSC/VLR sends an USSD message towards the gsmSCF via the HSS. It contains the following information.

Facility (ReturnResult=UNSTRUCTURED-SS-REQUEST(USSD-Data-Coding-Scheme, USSD String))

17. As the user responds, the gsmSCF stops playing the announcement by sending a DisconnectForwardConnection message to the GMSC.

NOTE: If the user responds before the timer started in step 7 expires, steps 12, 13 & 17 are skipped.

18. Call Continue/Release Call (HSS to GMSC)

Based on the response of the controller UE the gsmSCF sends a CAMEL CONTINUE or CAMEL RELEASE message to the GMSC.

19-20. MAP Send Routing Information (SRI)

On receipt of the call continue message, the GMSC queries again the HSS for the routing information for the called party but this time with the parameter Suppress T-CSI.

21. MAP SRI Ack

The HSS executes the roaming number enquiry procedure and sends this information back to the GMSC within the SRI-Ack containing MSRN=15346787943.

22. Call setup

The GMSC starts the normal call setup towards the visited MSC of the called party to establish the call.