A.3.2 Signalling flows for PN-registration

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

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

A.3.2.1 PN-registration in the IM CN subsystem using third party registration

Figure A.3.2.1-1 details the signalling flows for a successful PN-registration in the IM CN subsystem using third party registration. In this scenario the PN UE also performs the PN controller function.

Figure A.3.2.1-1: Successful PN-registration signalling: in the IM CN subsystem using third party registration

1. REGISTER request (PN UE to IM CN subsystem entities)

The PN UE initiates a REGISTER request after successful authentication.

Table A.3.2.1-1: REGISTER request (PN UE to IM CN subsystem entities)

Via: SIP/2.0/UDP icscf1_p.home1.net;branch=z9hG4bK351g45.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: 68

P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11: 3GPP-UTRAN; np

Path:<VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@pcscf1.visited1.net:1337;lr;ob>

Require: path

P-Visited-Network-ID: "Visited Network Number 1"

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

From: <sip:PN_user1_public1@home1.net>;tag=4fa3

To: <sip:PN_user1_public1@home1.net>

Contact: <sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp>;reg-id=1;

+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>";

+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";

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

+g.3gpp.cs-audio;

+g.3gpp.cs-video;

expires=600000

Call-ID: apb03a0s09dkjdfglkj49111

Authorization: Digest username="user1_private@home1.net", realm="registrar.home1.net", nonce=base64(RAND + AUTN + server specific data), algorithm=AKAv1-MD5, uri="sip:registrar.home1.net", response="6629fae49393a05397450978507c4ef1", integrity-protected="yes"

CSeq: 2 REGISTER

Supported: gruu, outbound

Content-Length: 0

NOTE: the above REGISTER request contents are shown as received at the S-CSCF not as sent by the PN UE.

2. Cx: S-CSCF registration notification procedure

There is no PNM specific content to this, for detailed message flows see 3GPP TS 29.228 [11] in subclause 6.1.2.

3. SIP 200 (OK) response (IM CN subsystem entities to PN UE)

4. REGISTER request (S-CSCF to PNM AS)

After the PN UE successfully registered in the IM CN subsystem, the S-CSCF sends a third party REGISTER request containing in the body the incoming REGISTER request from the PN UE and the 200 (OK) response to the incoming REGISTER request to the PNM AS based on the initial filter criteria it received which contains an Include Register Request XML element and an Include Register Response XML element.

Table A.3.2.1-4: REGISTER request (S-CSCF to PNM AS)

Via: SIP/2.0/UDP pnmas.home1.net;branch=z9hG499ffhy

Max-Forwards: 70

From: <sip:scscf1.home1.net>; tag=538ya

To: <sip: PN_user1_public1@home1.net >

Call-ID: 1asdaddlrfjflslj40a222

Contact: <sip:scscf1.home1.net>; expires=600000

CSeq: 87 REGISTER

Content-Type: multipart/mixed;boundary="boundary1"

Content-Length: (…)

–boundary1

Content-Type: message/sip

Via: SIP/2.0/UDP icscf1_p.home1.net;branch=z9hG4bK351g45.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: 68

P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11: 3GPP-UTRAN; np

Path:<VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@pcscf1.visited1.net:1337;lr;ob>

Require: path

P-Visited-Network-ID: "Visited Network Number 1"

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

From: <sip:PN_user1_public1@home1.net>;tag=4fa3

To: <sip:PN_user1_public1@home1.net>

Contact: <sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp>;reg-id=1;

+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>";

+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";

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

+g.3gpp.cs-audio;

+g.3gpp.cs-video;

expires=600000

Call-ID: apb03a0s09dkjdfglkj49111

CSeq: 2 REGISTER

Supported: gruu, outbound

Content-Length: 0

–boundary1

Content-Type: message/sip

SIP/2.0 200 OK

Via: SIP/2.0/UDP icscf1_p.home1.net;branch=z9hG4bK351g45.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

Path: <sip:term@pcscf1.visited1.net;lr>

Service-Route: <sip:orig@scscf1.home1.net;lr>

From: <sip:PN_user1_public1@home1.net>;tag=4fa3

To: <sip:PN_user1_public1@home1.net>

Call-ID: apb03a0s09dkjdfglkj49111

Contact: <sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp>;

pub-gruu="sip:PN_user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6";

temp-gruu="sip:tgruu.7hs==jd7vnzga5w7fajsc7-ajd6fabz0f8g5@example.com;gr";

reg-id=1;

+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>";

+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";

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

+g.3gpp.cs-audio;

+g.3gpp.cs-video;

expires=600000

CSeq: 2 REGISTER

Supported: path, outbound

Require: outbound

Date: Wed, 11 July 2001 08:49:37 GMT

P-Associated-URI: <sip:PN_user1_public2@home1.net>, <sip:PN_user1_public3@home1.net>, <sip:+1-212-555-1111@home1.net;user=phone>

Content-Length: 0

–boundary1–

5. SIP 200 (OK) response (PNM AS to S-CSCF)

6. Sh-Pull (AS to HSS)

For detailed message flows see 3GPP TS 29.328 [9] in subclause 6.1.1.

7. Sh-Pull Response (HSS to PNM AS)

After successful registration, the PNM AS enrols the registered public user identity in the database.

A.3.2.2 PN-registration in the IM CN subsystem with subscription to reg event package

Figure A.3.2.2-1 details the signalling flows for a successful PN-registration in the IM CN subsystem with subscription to reg event package. In this scenario the PN UE also performs the PN controller function.

Figure A.3.2.2-1: Successful PN-registration signalling: in the IM CN subsystem with subscription to reg event package

1. REGISTER request (PN UE to IM CN subsystem entities)

The PN UE initiates a REGISTER request after successful authentication.

Table A.3.2.2-1: REGISTER request (PN UE to IM CN subsystem entities)

Via: SIP/2.0/UDP icscf1_p.home1.net;branch=z9hG4bK351g45.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: 68

P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11: 3GPP-UTRAN; np

Path:<VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@pcscf1.visited1.net:1337;lr;ob>

Require: path

P-Visited-Network-ID: "Visited Network Number 1"

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

From: <sip:PN_user1_public1@home1.net>;tag=4fa3

To: <sip:PN_user1_public1@home1.net>

Contact: <sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp>;reg-id=1;

+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>";

+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";

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

+g.3gpp.cs-audio;

+g.3gpp.cs-video;

expires=600000

Call-ID: apb03a0s09dkjdfglkj49111

CSeq: 2 REGISTER

Supported: gruu, outbound

Content-Length: 0

NOTE: The above REGISTER request contents are shown as received at the S-CSCF not as sent by the PN UE.

2. Cx: S-CSCF registration notification procedure

There is no PNM specific content to this, for detailed message flows see 3GPP TS 29.228 [11] in subclause 6.1.2.

3. SIP 200 (OK) response (IM CN subsystem entities to PN UE)

4. REGISTER request (S-CSCF to PNM AS)

After the PN UE successfully registered in the IM CN subsystem, the S-CSCF sends a third party REGISTER request containing in the body a <service-info> element containing the private user identity of the PN UE to the PNM AS based on the initial filter criteria it received which contains the <service-info> element containing the private user identity of the PN UE.

Table A.3.2.2-4: REGISTER request (S-CSCF to PNM AS)

Via: SIP/2.0/UDP pnmas.home1.net;branch=z9hG499ffhy

Max-Forwards: 70

From: <sip:scscf1.home1.net>; tag=538ya

To: <sip: PN_user1_public1@home1.net>

Call-ID: 1asdaddlrfjflslj40a222

Contact: <sip:scscf1.home1.net>; expires=600000

CSeq: 87 REGISTER

Content-Type: application/3gpp-ims+xml

Content-Length: (…)

<3gpp-ims version="1">

<service-info>sip:PN_user1_private@home1.net</service-info>

</3gpp-ims>

5. SIP 200 (OK) response (PNM AS to S-CSCF)

6. SUBSCRIBE request (PNM AS to S-CSCF) – see example in table A.3.2.2-6

The PNM AS sends a SUBSCRIBE request to the S-CSCF for the reg event package for the public user identity.

Table A.3.2.2-6: SUBSCRIBE request (PNM AS to S-CSCF)

SUBSCRIBE sip: PN_user1_public1@home1.net SIP/2.0

Via: SIP/2.0/UDP pnmas.home1.net;branch=z9hG4bK240f34.1

Max-Forwards: 70

Route: <sip:scscf@home1.net;lr>

Privacy: none

From: <sip: pnamas.home1.net>; tag=31415

To: <sip: PN_user1_public1@home1.net>

Call-ID: b89rjhnedlrfjflslj40a222

CSeq: 61 SUBSCRIBE

Event: reg

Expires: 600000

Accept: application/reginfo+xml

Contact: <sip:pnmas.home1.net>

Content-Length: 0

7. SIP 200 (OK) response (S-CSCF to PNM AS)

8. NOTIFY request (S-CSCF to PNM AS) – see example in table A.3.2.2-8

The S-CSCF sends a first NOTIFY request towards the PNM AS in order to inform the PNM AS about the registration status of the monitored user and the UE capabilities.

Table A.3.2.2-8: NOTIFY request (S-CSCF to PNM AS)

NOTIFY sip: pnmas.home1.net SIP/2.0

Via: SIP/2.0/UDP scscf@home1.net;branch=z9hG4bK332b23.1

Max-Forwards: 70

From: <sip:scscf@home1.net>;tag=151170

To: <sip: pnmas.home1.net>;tag=31415

Call-ID: dre36d2v32gnlgiiomm72445

CSeq: 42 NOTIFY

Subscription-State: active;expires=600000

Event: reg

Content-Type: application/reginfo+xml

Contact: <sip:scscf@home1.net>

Content-Length: (…)

<?xml version="1.0"?>

<reginfo xmlns="urn:ietf:params:xml:ns:reginfo"

xmlns:gr="urn:ietf:params:xml:ns:gruuinfo"

version="1" state="full">

<unknown-param name=”+sip.instance”><urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>” </unknown-param>

<unknown-param name=”+g.3gpp.icsi_ref”><urn:urn-7:3gpp-service.ims.icsi.mmtel>” </unknown-param>

<unknown-param name=”+g.3gpp.iari_ref”><urn:urn-7:3gpp-application.ims.iari.pnm-controller&gt"</unknown-param>

<unknown-param name=”+g.3gpp.cs-audio”> </unknown-param>

<unknown-param name=”+g.3gpp.cs-video”> </unknown-param>

</allOneLine>

<gr:pub-gruu uri="sip:PN_user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"/>

</allOneLine>

<gr:temp-gruu uri="sip:8ffkas08af7fasklzi9@home1.net;gr" first-cseq="40"/>

</contact>

</registration>

<unknown-param name=”+sip.instance”><urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>” </unknown-param>

<unknown-param name=”+g.3gpp.iari_ref”><urn:urn-7:3gpp-service.ims.icsi.mmtel>” </unknown-param>

<unknown-param name=”+g.3gpp.cs-audio”> </unknown-param>

<unknown-param name=”+g.3gpp.cs-video”> </unknown-param>

</allOneLine>

<gr:pub-gruu uri="sip:PN_user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"/>

</allOneLine>

<gr:temp-gruu uri="sip:2k3e8farf7flfka9zi9@home1.net;gr" first-cseq="40"/>

</contact>

</registration>

</reginfo>

9. SIP 200 (OK) response (PNM AS to S-CSCF)

10. Sh-Pull (AS to HSS)

For detailed message flows see 3GPP TS 29.328 [9] in subclause 6.1.1.

11. Sh-Pull Response (HSS to PNM AS)

After successful registration, the PNM AS enrols the registered public user identity in the database.

A.3.2.3 PN-registration procedure for PNE other than a PN UE

Figure A.3.2.3-1 details the signalling flows for a successful PN-registration in the IM CN subsystem for two PNEs other than a PN UE.

Figure A.3.2.3-1: Successful PN-registration signalling for PNE other than a PN UE

1. Register request

PNE1 sends a Register request towards UE via the PAN internal interface. The Register request may contain the PNE identifier.

2. SIP REGISTER request (PN UE to IM CN subsystem entities)- see example in table A.3.2.3-2.

The PN UE initiates a SIP REGISTER request on behalf the PNE1. The PNE1 identifier is conveyed in the g.3gpp.pne-id media feature tag of the Contact header field to indicate this is registration for the PNE. The value of "reg-id" is set to 2.

NOTE: In this case, a successful authentication has been done before sending the SIP REGISTER request.

Table A.3.2.3-2: SIP REGISTER request (PN UE to IM CN subsystem entities)

Via: SIP/2.0/UDP icscf1_p.home1.net;branch=z9hG4bK351g45.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: 68

P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11: 3GPP-UTRAN; np

Path:<VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@pcscf1.visited1.net:1337;lr;ob>

Require: path,outbound

P-Visited-Network-ID: "Visited Network Number 1"

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

From: <sip:PN_user1_public1@home1.net>;tag=4fa3

To: <sip:PN_user1_public1@home1.net>

Contact: <sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp>;reg-id=2;

+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>";

+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";

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

+g.3gpp.cs-audio;

+g.3gpp.pne-id="<urn:uuid:f81d4fae-7dec-11d0-a765-001w4dfdafer>"expires=600000

Call-ID: apb03a0s09dkjdfglkj49111

CSeq: 2 REGISTER

Supported: gruu, outbound

Content-Length: 0

3. SIP 200 (OK) response (IM CN subsystem entities to PN UE)

4. Successful response (UE to PNE1)

The UE sends the successful response to the register request towards the PNE1 via the PAN internal interface.

5. SIP REGISTER request (S-CSCF to PNM AS)- see example in table A.3.2.3-5

After the PN UE successfully registered in the IM CN subsystem, the S-CSCF sends a third party REGISTER request to the PNM AS based on the initial filter criteria.

Table A.3.2.3-5: SIP REGISTER request (S-CSCF to PNM AS)

Via: SIP/2.0/UDP pnmas.home1.net;branch=z9hG499ffhy

Max-Forwards: 70

From: <sip:scscf1.home1.net>; tag=538ya

To: <sip: PN_user1_public1@home1.net >

Call-ID: 1asdaddlrfjflslj40a222

Contact: <sip:scscf1.home1.net>; expires=600000

CSeq: 87 REGISTER

6. SIP 200 (OK) response (PNM AS to S-CSCF)

7. SUBSCRIBE request (PNM AS to S-CSCF) – see example in table A.3.2.3-7

The PNM AS sends a SUBSCRIBE request to the S-CSCF for the reg event package.

Table A.3.2.3-7: SUBSCRIBE request (PNM AS to S-CSCF)

SUBSCRIBE sip: PN_user1_public1@home1.net SIP/2.0

Via: SIP/2.0/UDP pnmas.home1.net;branch=z9hG4bK240f34.1

Max-Forwards: 70

Route: <sip:scscf@home1.net;lr>

Privacy: none

From: <sip: pnamas.home1.net>; tag=31415

To: <sip: PN_user1_public1@home1.net>

Call-ID: b89rjhnedlrfjflslj40a222

CSeq: 61 SUBSCRIBE

Event: reg

Expires: 600000

Accept: application/reginfo+xml

Contact: <sip:pnmas.home1.net>

Content-Length: 0

8. SIP 200 (OK) response (S-CSCF to PNM AS)

9. NOTIFY request (S-CSCF to PNM AS) – see example in table A.3.2.3-9

The S-CSCF sends a first NOTIFY request towards the PNM AS in order to inform the PNM AS about the registration status of the monitored user and the PNE capabilities.

Table A.3.2.3-9: NOTIFY request (S-CSCF to PNM AS)

NOTIFY sip: pnmas.home1.net SIP/2.0

Via: SIP/2.0/UDP scscf@home1.net;branch=z9hG4bK332b23.1

Max-Forwards: 70

From: <sip:scscf@home1.net>;tag=151170

To: <sip: pnmas.home1.net>;tag=31415

Call-ID: dre36d2v32gnlgiiomm72445

CSeq: 42 NOTIFY

Subscription-State: active;expires=600000

Event: reg

Content-Type: application/reginfo+xml

Contact: <sip:scscf@home1.net>

Content-Length: (…)

<?xml version="1.0"?>

<reginfo xmlns="urn:ietf:params:xml:ns:reginfo"

xmlns:gr="urn:ietf:params:xml:ns:gruuinfo"

version="1" state="full">

<unknown-param name=”+sip.instance”><urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>” </unknown-param>

<unknown-param name=”+g.3gpp.icsi_ref”><urn:urn-7:3gpp-service.ims.icsi.mmtel>” </unknown-param>

<unknown-param name=”+g.3gpp.iari_ref”><urn:urn-7:3gpp-application.ims.iari.pnm-controller&gt"</unknown-param>

<unknown-param name=”+g.3gpp.cs-audio”> </unknown-param>

</unknown-param>

<unknown-param name=”+g.3gpp.pne-id”><urn:uuid: f81d4fae-7dec-11d0-a765-001w4dfdafer;” </unknown-param>

</allOneLine>

<gr:pub-gruu uri="sip:PN_user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"/>

</allOneLine>

<gr:temp-gruu uri="sip:8ffkas08af7fasklzi9@home1.net;gr" first-cseq="40"/>

</contact>

</registration>

<unknown-param name=”+sip.instance”><urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>” </unknown-param>

<unknown-param name=”+g.3gpp.iari_ref”><urn:urn-7:3gpp-service.ims.icsi.mmtel>” </unknown-param>

<unknown-param name=”+g.3gpp.cs-audio”> </unknown-param>

<unknown-param name=”+g.3gpp.cs-video”> </unknown-param>

</allOneLine>

<gr:pub-gruu uri="sip:PN_user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"/>

</allOneLine>

<gr:temp-gruu uri="sip:2k3e8farf7flfka9zi9@home1.net;gr" first-cseq="40"/>

</contact>

</registration>

</reginfo>

10. SIP 200 (OK) response (PNM AS to S-CSCF)

11. Enrol the PNE1

After successful registration, the PNE1 is registered into the PAN, i.e. save the bindings between UE and PNE identifiers in the database.

12. Register request

PNE2 sends a Register request towards UE via the PAN internal interface. The Register request may contain the PNE2 identifier.

13. SIP REGISTER request (PN UE to IM CN subsystem entities)- see example in table A.3.2.3-13.

The PN UE initiates a SIP REGISTER request on behalf the PNE2. The PNE2 identifier is conveyed in the g.3gpp.pne-id media feature tag of the Contact header field to indicate this is registration for the PNE2. The value of "reg-id" is set to 3 to not override the previous registration for PNE2.

Table A.3.2.3-13: SIP REGISTER request (PN UE to IM CN subsystem entities)

Via: SIP/2.0/UDP icscf1_p.home1.net;branch=z9hG4bK351g45.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: 68

P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11: 3GPP-UTRAN; np

Path:<VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@pcscf1.visited1.net:1337;lr;ob>

Require: path,outbound

P-Visited-Network-ID: "Visited Network Number 1"

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

From: <sip:PN_user1_public1@home1.net>;tag=4fa3

To: <sip:PN_user1_public1@home1.net>

Contact: <sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp>;reg-id=3;

+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>";

+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";

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

+g.3gpp.cs-video;

+g.3gpp.pne-id="<urn:uuid:f81d4fae-7dec-11d0-b789-99ef34fledvd5>"

expires=600000

Call-ID: apb03a0s09dkjdfglkj49111

CSeq: 3 REGISTER

Supported: gruu, outbound

Content-Length: 0

14. SIP 200 (OK) response (IM CN subsystem entities to PN UE)

15. Successful response (UE to PNE2)

The UE sends the successful response to the register request towards the PNE via the PAN internal interface.

16. NOTIFY request (S-CSCF to PNM AS) – see example in table A.3.2.3-16

The S-CSCF sends a first NOTIFY request towards the PNM AS in order to inform the PNM AS about the PNE2 identifier and PNE2 capabilites.

Table A.3.2.3-16: NOTIFY request (S-CSCF to PNM AS)

NOTIFY sip: pnmas.home1.net SIP/2.0

Via: SIP/2.0/UDP scscf@home1.net;branch=z9hG4bK332b23.1

Max-Forwards: 70

From: <sip:scscf@home1.net>;tag=151170

To: <sip: pnmas.home1.net>;tag=31415

Call-ID: dre36d2v32gnlgiiomm72445

CSeq: 43 NOTIFY

Subscription-State: active;expires=600000

Event: reg

Content-Type: application/reginfo+xml

Contact: <sip:scscf@home1.net>

Content-Length: (…)

<?xml version="1.0"?>

<reginfo xmlns="urn:ietf:params:xml:ns:reginfo"

xmlns:gr="urn:ietf:params:xml:ns:gruuinfo"

version="1" state="full">

<unknown-param name=”+sip.instance”><urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>” </unknown-param>

<unknown-param name=”+g.3gpp.icsi_ref”><urn:urn-7:3gpp-service.ims.icsi.mmtel>” </unknown-param>

<unknown-param name=”+g.3gpp.iari_ref”><urn:urn-7:3gpp-application.ims.iari.pnm-controller&gt"</unknown-param>

<unknown-param name=”+g.3gpp.cs-video”> </unknown-param>

</unknown-param>

<unknown-param name=”+g.3gpp.pne-id”><urn:uuid:f81d4fae-7dec-11d0-b789-99ef34fledvd5;” </unknown-param>

</allOneLine>

<gr:pub-gruu uri="sip:PN_user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"/>

</allOneLine>

<gr:temp-gruu uri="sip:8ffkas08af7fasklzi9@home1.net;gr" first-cseq="40"/>

</contact>

</registration>

<unknown-param name=”+sip.instance”><urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>” </unknown-param>

<unknown-param name=”+g.3gpp.iari_ref”><urn:urn-7:3gpp-service.ims.icsi.mmtel>” </unknown-param>

<unknown-param name=”+g.3gpp.cs-audio”> </unknown-param>

<unknown-param name=”+g.3gpp.cs-video”> </unknown-param>

</allOneLine>

<gr:pub-gruu uri="sip:PN_user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"/>

</allOneLine>

<gr:temp-gruu uri="sip:2k3e8farf7flfka9zi9@home1.net;gr" first-cseq="40"/>

</contact>

</registration>

</reginfo>

17. SIP 200 (OK) response (PNM AS to S-CSCF)

18. Enrol the PNE2

After successful registration, the PNE2 is registered into the PAN.