A.3.4 Signalling flows for PN UE redirection

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

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

A.3.4.1 PN UE redirection in the IM CN subsystem

Figure A.3.4.1-1 details the signalling flows for PN UE redirection in the IM CN subsystem.

Figure A.3.4.1-1: Successful PN UE redirection: in the 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 request (I-CSCF#2 to S-CSCF#2) –see example in table A.3.4.1-1

I-CSCF#2 forwards the INVITE request to S-CSCF#2 after invocation of the User Location Query procedure.

Table A.3.4.1-1: INVITE (I-CSCF#2 to S-CSCF#2)

INVITE sip:PN_user2_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.home1.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.home1.net;lr>

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

Privacy: none

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

To: <sip: PN_user2_public1@home2.net>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 127 INVITE

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. SIP 100 (Trying) response

3. Evaluation of initial filter criteria

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

4. INVITE#1 request (S-CSCF#2 to PNM AS)- see example in table A.3.4.1-4

Based on the evaluation of initial filter criteria, the S-CSCF#2 forwards the INVITE request with the Request-URI of the UE-1 to the PNM AS.

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

INVITE sip:PN_user2_public1@home2.net SIP/2.0

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK240f34.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.home1.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.home2.net;lr>,<sip:icscf1.home1.net;lr>,<sip:scscf1.home1.net;lr>,<sip:pcscf1.home.net;lr>

P-Asserted-Identity:

Privacy: none

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

To: <sip: PN_user2_public1@home2.net>

Call-ID:

Cseq:

Supported: precondition, 100rel, gruu

Accept-Contact:

P-Asserted-Service:

Contact:

Allow:

Accept:

Content-Type:

Content-length: (…)

5. SIP 100 (Trying) response (PNM AS to S-CSCF#2)

6. PN UE redirection control

The PNM AS executes the PN UE redirection logic based on the PN-user’s PN configurations and decides to redirect the initial request to the default UE of the PN, e.g. to the UE-3.

7. INVITE#2 request (PNM AS to S-CSCF#2) – see example in table A.3.4.1-7

As a result of the PN UE redirection logic execution, the PNM AS sends the redirected INVITE request with the Request-URI of the UE-2 public user identity to the S-CSCF#2.

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

INVITE sip:PN_user3_public1@home2.net SIP/2.0

Via: SIP/2.0/UDP pnmas.home2.net; brach= z9hG4bK712z34.1,

SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.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.home1.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:pnmas.home2.net>, <sip:scscf2.home2.net;lr>, <sip:icscf1.home1.net;lr>, <sip:scscf1.home1.net;lr>,<sip:pcscf1.home1.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

Supported: precondition,100rel,gruu,199,histinfo

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

<sip:PN_user3_public1@home2.net>;index=1.1

Accept-Contact:

P-Asserted-Service:

Contact:

Allow:

Accept:

Content-Type:

Content-length: (…)

8. SIP 100 (Trying) response (S-CSCF#2 to PNM AS)

9. INVITE#2 request (S-CSCF#2 to S-CSCF#3) – see example in table A.3.4.1–9

The S-CSCF#2 forwards the redirected INVITE request to the S-CSCF#3. The S-CSCF#2 and S-CSCF#3 can be the same entity.

Table A.3.4.1-9: INVITE#2 (S-CSCF#2 to S-CSCF#3)

INVITE sip:PN_user3_public1@home2.net SIP/2.0

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

SIP/2.0/UDP Pnmas.home2.net;brach= z9hG4bK712z34.1,

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

SIP/2.0/UDP icscf1.home1.net;branch=z9hG4bK871y12.1,

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

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

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

Max-Forwards: 62

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

Record-Route: <sip:scscf3.home2.net;lr>, <sip:pnmas.home2.net>, <sip:scscf2.home2.net;lr>, <sip:icscf1.home1.net;lr>, <sip:scscf1.home1.net;lr>, <sip:pcscf1.home1.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

History-Info:

Accept-Contact:

P-Asserted-Service:

Supported:

Contact:

Allow:

Accept:

Content-Type:

Content-length: (…)

10. SIP 100 (Trying) response (S-CSCF#3 to S-CSCF#2)

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

11. INVITE#2 request (S-CSCF#3 to PNM AS) – see example in table A.3.4.1-11

Based on the evaluation of initial filter criteria, the S-CSCF#3 forwards the INVITE request with the Request-URI of the UE-3 to the PNM AS.

Table A.3.4.1-11: INVITE#2 (S-CSCF#3 to PNM AS)

INVITE sip:PN_user3_public1@home2.net SIP/2.0

Via: SIP/2.0/UDP scscf3.home2.net;branch=z9hG4bK735z12.1,

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

SIP/2.0/UDP Pnmas.home2.net;brach= z9hG4bK712z34.1,

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

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

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

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

Max-Forwards: 61

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

Record-Route: <sip:scscf3.home2.net;lr>,<sip:scscf2.home2.net;lr>, <sip:pnmas.home2.net>, <sip:scscf1.home2.net;lr>, <sip:icscf2.home2.net;lr>, <sip:scscf1.home1.net;lr>, <sip:pcscf1.home1.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

Supported:

History-Info:

Accept-Contact:

P-Asserted-Service:

Contact:

Allow:

Accept:

Content-Type:

Content-length: (…)

12. SIP 100 (Trying) response (PNM AS to S-CSCF#3)

13. PN UE redirection control

The PNM AS executes the PN UE redirection control logic based on the PN-user’s PN configurations and decides to forward the request to S-CSCF#3 as the UE-3 is the default UE of the PN.

14. INVITE#2 request (PNM AS to S-CSCF#3) – see example in table A.3.4.1-14

Table A.3.4.1-14: INVITE#2 (PNM AS to S-CSCF#3)

INVITE sip: PN_user3_public1@home2.net SIP/2.0

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

SIP/2.0/UDP scscf3.home2.net;branch=z9hG4bK735z12.1,

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

SIP/2.0/UDP Pnmas.home2.net;brach= z9hG4bK712z34.1,

SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.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.home1.net;branch=z9hG4bK240f34.1,

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

Max-Forwards: 60

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

Record-Route: <sip:pnmas.home2.net;lr>,<sip:scscf3.home2.net;lr>,<sip:scscf2.home2.net;lr>, <sip:pnmas.home2.net>, <sip:scscf2.home2.net;lr>, <sip:icscf2.home2.net;lr>, <sip:scscf1.home1.net;lr>, <sip:pcscf1@home1.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

Supported:

History-Info:

Accept-Contact:

P-Asserted-Service:

Contact:

Allow:

Accept:

Content-Type:

Content-length: (…)

15. SIP 100 (Trying) response (S-CSCF#3 to PNM AS)

16. INVITE#2 request (S-CSCF#3 to P-CSCF-#3) — see example in table A.3.4.1-16

The S-CSCF#3 continues the redirected INVITE request based on the standard call setup procedures.

Table A.3.4.1-16: INVITE#2 (S-CSCF#3 to P-CSCF#3)

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

Via: SIP/2.0/UDP scscf3.home2.net;branch=z9hG4bK735z12.1,

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

SIP/2.0/UDP scscf3.home2.net;branch=z9hG4bK735z12.1,

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

SIP/2.0/UDP Pnmas.home2.net;brach= z9hG4bK712z34.1,

SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.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.home1.net;branch=z9hG4bK240f34.1,

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

Max-Forwards: 59

Route: <sip: pcscf#3@home2.net;lr>

Record-Route: <sip:scscf3.home2.net;lr>, <sip:pnmas.home2.net;lr>,<sip:scscf3.home2.net;lr>,<sip:scscf2.home2.net;lr>, <sip:pnmas.home2.net>, <sip:scscf2.home2.net;lr>, <sip:icscf2.home2.net;lr>, <sip:scscf1.home1.net;lr>, <sip:pcscf1.home1.net;lr>

P-Asserted-Identity:

Privacy:

From:

To:

Cseq:

Call-ID:

Supported:

History-Info:

Accept-Contact:

P-Asserted-Service:

Contact:

Allow:

Accept:

P-Called-Party-ID: <sip:PN_user3_public1@home2.net>

Content-Type:

Content-length: (…)

17. Steps 17 to 30 are identical to generic session setup procedure specified in 3GPP TS 24.228 [10].

A.3.4.2 PN UE redirection in the CS domain

Figure A.3.4.2-1 provides the signaling flow for PN UE redirection in the CS domain. The GMSC will receive the ISUP containing calling party number and called party number. The gsmSCF will invoke the service logic in order to route the call to the Default-UE.

Figure A.3.4.2-1: Signalling flow for PN UE redirection in the CS domain

1. ISUP IAM

An IAM message arrives at the GMSC#1. Specifically for this signalling flow, the IAM includes:

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

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

2. MAP Send Routing Information (SRI) (GMSC#1 to HSS)

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

3. Retrieval of PNM subscriber information

The HSS provides information including the T-CSI information element that contains information configured for the PNM subscriber, identifying the subscriber as having terminating CAMEL services. The T-CSI IE also includes the gsmSCF address.

4. MAP Send Routing Information Acknowledgement (SRI ACK) (HSS to GMSC#1)

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

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. The gsmSCF invokes PNM Redirection service logic to route the call.

7. CAMEL CONNECT (gsmSCF to GMSC#1)

The CAMEL service function causes the gsmSCF to respond to the CAMEL IDP message with a CAMEL CONNECT message containing:

– The MSISDN of the Default UE: 12245678912

8. IAM message arrived at GMSC#2 of Default UE.

The IAM includes:

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

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

9. ISUP IAM

The call is routed to the Default UE.

10-12. ISUP ACM

In response an ACM is generated .There is no PNM specific content to this response.

13-15. ISUP ANM

The ANM is generated after the terminating UE answers the call. There is no PNM specific content to this response.