A.3.6 Signalling flows for interdomain networking

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

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

A.3.6.1 IM CN subsystem to CS domain

Figure A.3.6-1 details the signaling flows for inter-domain networking from IM CN to CS domain.

Figure A.3.6-1: interdomain networking: (IM CN-CS)

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

The UE initiates the INVITE request with the request-URI of the UE-1 to the IM CN subsystem entities.

There is no PNM specific content to this request.

Table A.3.6-1-1: INVITE request (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.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_user2_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-00a0c91e6bf6g.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

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

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 request (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.6-1-4: INVITE request (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=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:

Content-Type:

Content-length: (…)

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

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

There is no PNM specific content to this response.

6. PNM session redirection service control

The PNM AS executes the PNM redirection service control logic in order to route the call to the default UE located in the CS domain.

In this example the MSISDN of the called party is +1237654799942

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

A.3.6.2 CS domain to IM CN subsystem

Figure A.3.6-2 shows the signaling flows for inter-domain networking from CS domain to IM CN subsystem.

Figure A.3.6-2: Inter-domain networking: (CS-IM CN)

1. ISUP IAM (coming from the originating PLMN through the CS domain)

In this example, a call request (ISUP IAM) makes an entry from the PLMN of the originating user (calling party) into the home PLMN of the terminating user (called party). The first entry point of the PLMN of the terminating user is the Gateway MSC (GMSC). The call request is a form of an ISUP IAM (Initial Address Message) and contains the called party number (MSISDN).

In this example the MSISDN of the called party is +12134567897

2. MAP Send Routing Information (SRI) (GMSC 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)

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 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 in the SRI ACK from the HSS. This includes the CAMEL service key.

6. Reroute to IMS determination

The gsmSCF invokes PNM redirection service logic to determine whether the call needs to be rerouted to the default UE located in the IM CN subsystem for UE redirection.

7. CAMEL CONNECT (gsmSCF to GMSC)

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

MSISDN of default UE: 12134567897

8. IAM#2(GMSC to MGCF)

The GMSC generates the IAM#2 containing the MSISDN of the default UE at which the call is to be redirected and signals it to the MGCF.

MSISDN of default UE: 12134567897

9. SIP INVITE (MGCF to S-CSCF)

The MGCF interworks the IAM into the appropriate SIP message and initiates the SIP INVITE request towards the S-CSCF via the intermediate IM CN subsystem entities.

(MGCF towards the S-CSCF through the intermediate IM CN subsystem entities) – see example in table A.3.Y1

Table A.3.6-2-9: SIP INVITE request (MGCF to S-CSCF)

INVITE tel:+12134567897 SIP/2.0

Via: SIP/2.0/UDP mgcf.home1.net;branch=z9hG4bK779s24.0

Max-Forwards: 69

Route: <sip:icscf1.home1.net;lr>

P-Asserted-Identity: <tel:+1-212-555-1111>

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"; orig-ioi=home1.net

Privacy: none

From: <tel:+1-212-555-1111>;tag=171828

To: <tel:+ 12134567897>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 127 INVITE

Supported: precondition, 100rel

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:mgcf1.home1.net>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"

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