A.6 PUA subscribing to his own watcher list and receiving notification of new watcher subscriptions

24.1413GPPPresence service using the IP Multimedia (IM) Core Network (CN) subsystemRelease 17Stage 3TS

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

A.6.1 Introduction

This subclause covers the signalling flows that show how a PUA can subscribe to his own watcher list.

A.6.2 PUA subscribing to watcher list and receiving a notification of an already pending watcher subscription followed by a notification of a subscription from a new watcher not already in the watcher list

Figure A.6.2-1: PUA subscribing to watcher list and receiving a notification
of an already pending watcher subscription followed by a notification of a subscription
from a new watcher not already in the watcher list

Figure A.6.2-1 shows a PUA subscribing to the watcher list and receiving a notification of an already pending watcher subscription followed by a notification of a subscription from a new watcher not already in the watcher list. In this example the default watcherinfo subscription filtering policy is applied meaning that a partial state of a watcher-info document is transported in the notifications. The details of the signalling flows as follows:

1. SUBSCRIBE request (UE to P-CSCF) – see example in table A.6.2-1

The presentity wishes to watch his own watcher information, therefore he subscribes for the watcher information template-package of presence. The UE generates a SUBSCRIBE request containing the presence.winfo event, together with an indication of the length of time this periodic subscription should last.

Table A.6.2-1: SUBSCRIBE request (UE to P-CSCF)

SUBSCRIBE sip:user1_public1@home1.net SIP/2.0

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

Max-Forwards: 70

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

Route: <sip:pcscf1.visited1.net:7531;lr;comp=sigcomp>, <sip:orig@scscf1.home1.net;lr>

P-Preferred-Identity: <sip:user1_public1@home1.net>

Privacy: none

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

To: <sip:user1_public1@home1.net>

Call-ID: b89rjhnedlrfjflslj40a222

CSeq: 123 SUBSCRIBE

Require: sec-agree

Proxy-Require: sec-agree

Security-Verify: ipsec-3gpp; q=0.1; alg=hmac-sha-1-96; spi-c=98765432; spi=87654321; port-c=8642; port-s=7531

Event: presence.winfo

Expires: 7200

Accept: application/watcherinfo+xml

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

Content-Length: 0

Request URI: Public user identity whose events the subscriber subscribes to. In this case the Public User Identity of the presentity in SIP URI format.

Event: This field is populated with the value "presence.winfo" to specify the use of the watcher information template-package of presence.

Accept: This field is populated with the value ‘application/watcherinfo+xml’ indicating that the UE supports this body type for notification.

To: Same as the Request-URI.

2. SUBSCRIBE request (P-CSCF to S-CSCF) – see example in table A.6.2-2

The P-CSCF looks up the serving network information for the public user identity that was stored during the registration procedure. The SUBSCRIBE request is forwarded to the S-CSCF. A Route header is inserted into SUBSCRIBE request.

Table A.6.2-2: SUBSCRIBE request (P-CSCF to S-CSCF)

SUBSCRIBE sip:user1_public1@home1.net SIP/2.0

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK120f34.1 ,SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKehuefdam

P-Access-Network-Info:

Max-Forwards: 69

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

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

Privacy:

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

Record-Route: <sip:pcscf1.visited1.net;lr>

From:

To:

Call-ID:

CSeq:

Event:

Expires:

Accept:

Contact:

Content-Length:

3. Evaluation of initial filter criteria

The S-CSCF validates the service profile of this subscriber and evaluates the initial filter criteria. For sip:user1_public1@home1.net the S-CSCF has originating initial Filter Criteria with Service Point Trigger of Method = SUBSCRIBE AND Event = "presence.winfo" that informs the S-CSCF to route the SUBSCRIBE request to the AS sip:ps.home1.net.

4. SUBSCRIBE request (S-CSCF to PS) – see example in table A.6.2-4

The S-CSCF forwards the SUBSCRIBE request to the PS.

Table A.6.2-4: SUBSCRIBE request (S-CSCF to PS)

SUBSCRIBE sip:user1_public1@home1.net SIP/2.0

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK344a65.1, SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK120f34.1, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKehuefdam

P-Access-Network-Info:

Max-Forwards: 68

P-Asserted-Identity: <sip:user1_public1@home1.net>, <tel:+1-212-555-1111>

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

P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66]; ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4ee]; ecf=[5555::6aa:7bb:8cc:9dd]

Privacy:

Route: <sip:ps.home1.net;lr>, <sip:scscf1.home1.net;lr>

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

From:

To:

Call-ID:

CSeq:

Event:

Expires:

Accept:

Contact:

Content-Length:

P-Charging-Vector: The S-CSCF inserts the originating Inter Operator Identifier (IOI) parameter received and populates the identifier of its own network to the originating Inter Operator Identifier (IOI) parameter of this header.

P-Charging-Function-Addresses: The S-CSCF stores the P-Charging-Function-Addresses header field and passes this header to the PS.

5. Authorization

The PS performs the necessary authorization checks on the originator. In this example, the originator is the owner of the watcher information, so he/she is authorized to see the full watcher information.

In other examples (when the originator is not the owner of the watcher information) subscribers are only allowed to monitor the state of their own subscription, which means that they will receive notifications only containing the state of their own subscription. This requires that a terminating initial Filter Criteria with Service Point Trigger of Method = SUBSCRIBE AND Event = "presence.winfo" has been defined for the user sip:user1_public1@home1.net.

6. 200 (OK) response (PS to S-CSCF) – see example in table A.6.2-6

The PS sends the response to the S-CSCF.

Table A.6.2-6: 200 (OK) response (PS to S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK344a65.1, SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK120f34.1, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKehuefdam

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

P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66]; ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4ee]; ecf=[5555::6aa:7bb:8cc:9dd]

Record-Route:

From:

To: <sip:user1_public1@home1.net>;tag=151170

Call-ID:

CSeq:

Expires:

Contact: <sip:ps.home1.net>

Content-Length: 0

P-Charging-Vector: The PS stores the originating Inter Operator Identifier (IOI) parameter and populates the identifier of its own network to the terminating Inter Operator Identifier (IOI) parameter of this header.

P-Charging-Function-Addresses: The PS stores the P-Charging-Function-Addresses header field and passes this header to the S-CSCF.

7. 200 (OK) response (S-CSCF to P-CSCF) – see example in table A.6.2-7

The S-CSCF forwards the response to the P-CSCF.

Table A.6.2-7: 200 (OK) response (S-CSCF to P-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK120f34.1, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKehuefdam

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

Record-Route:

From:

To:

Call-ID:

CSeq:

Expires:

Contact:

Content-Length:

P-Charging-Vector: The S-CSCF stores the terminating Inter Operator Identifier (IOI) parameter.

8. 200 (OK) response (P-CSCF to UE) – see example in table A.6.2-8

The P-CSCF forwards the response to the PUA in the UE.

Table A.6.2-8: 200 (OK) response (P-CSCF to UE)

SIP/2.0 200 OK

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

Record-Route: <sip:orig@scscf1.home1.net;lr>, <sip:pcscf1.home1.net:7531;lr;comp=sigcomp>

From:

To:

Call-ID:

CSeq:

Expires:

Contact:

Content-Length:

9. NOTIFY request (PS to S-CSCF) – see example in table A.6.2-9

After the PS generated a 200 (OK) response to the SUBSCRIBE request from the UE, it generates a NOTIFY request containing the current state of the watcher information. The watcher information contains one pending subscription.

Table A.6.2-9 NOTIFY request (PS to S-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

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

Max-Forwards: 70

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

P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66]; ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4ee]; ecf=[5555::6aa:7bb:8cc:9dd]

Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.visited1.net;lr>

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

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

Call-ID: b89rjhnedlrfjflslj40a222

CSeq: 89 NOTIFY

Subscription-State: active;expires=7200

Event: presence.winfo

Contact: <sip:ps.home1.net>

Content-Type: application/watcherinfo+xml

Content-Length: (…)

<?xml version="1.0"?>

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

version="0" state="full">

<watcher-list resource="sip:user1_public1@home1.net" package="presence">

<watcher id="77ajsyy76" event="subscribe"

status="pending">sip:user2_public1@home2.net</watcher>

</watcher-list>

</watcherinfo>

P-Charging-Vector: The PS populates the icid parameter with a globally unique value and populates the identifier of its own network to the originating Inter Operator Identifier (IOI) parameter of this header.

P-Charging-Function-Addresses: The PS populates the P-Charging-Function-Addresses header field to be passed to the S-CSCF.

10. NOTIFY request (S-CSCF to P-CSCF) – see example in table A.6.2-10

The S-CSCF forwards the NOTIFY request to the P-CSCF.

Table A.6.2-10: NOTIFY request (S-CSCF to P-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

Max-Forwards: 69

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

P-Charging-Function-Addresses:

Route: <sip:pcscf1.visited1.net;lr>

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

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Contact:

Content-Type:

Content-Length:

(…)

P-Charging-Vector: The S-CSCF stores the originating Inter Operator Identifier (IOI) parameter received.

P-Charging-Function-Addresses: The S-CSCF stores the P-Charging-Function-Addresses header field and passes this header to the P-CSCF.

11. NOTIFY request (P-CSCF to UE) – see example in table A.6.2-11

The P-CSCF forwards the NOTIFY request to the PUA in the UE.

Table A.6.2-11: NOTIFY request (P-CSCF to UE)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK351g45.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

Record-Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.home1.net:7531;lr;comp=sigcomp>

Max-Forwards: 68

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Contact:

Content-Type:

Content-Length:

(…)

12. 200 (OK) response (UE to P-CSCF) – see example in table A.6.2-12

The PUA on the UE determines that this is a full state watcher-info document and replaces any current watcher-info with the new document. The UE acknowledges the NOTIFY request with a 200 (OK) response to the P-CSCF.

Table A.6.2-12: 200 (OK) response (UE to P-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

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

From:

To:

Call-ID:

CSeq:

Content-Length: 0

13. 200 (OK) response (P-CSCF to S-CSCF) – see example in table A.6.2-13

The P-CSCF forwards the 200 (OK) response to the S-CSCF.

Table A.6.2-13: 200 (OK) response (P-CSCF to S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

P-Access-Network-Info:

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

From:

To:

Call-ID:

CSeq:

Content-Length:

14. 200 (OK) response (S-CSCF to PS) – see example in table A.6.2-14

The P-CSCF forwards the response to the PS in the home network of the UE.

Table A.6.2-14: 200 (OK) response (S-CSCF to PS)

SIP/2.0 200 OK

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

P-Access-Network-Info:

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

From:

To:

Call-ID:

CSeq:

Content-Length:

P-Charging-Vector: The S-CSCF inserts the terminating Inter Operator Identifier (IOI) parameter received and populates the identifier of its own network to the terminating Inter Operator Identifier (IOI) parameter of this header.

15. Authorization of watcher

The presentity determines to allow the watcher to access the presence information. The PUA modifies the subscription authorization policy by authorizing presence information for sip:user2_public1@home1.net.

16. NOTIFY request (PS to S-CSCF) – see example in table A.6.2-16

The authorization event means changes in the watcher information, which triggers a new NOTIFY request. The watcher information included in the NOTIFY request contains only information on the watcher whose state has changed, which in this example is the accepted subscription of sip:user2_public1@home1.net.

Table A.6.2-16: NOTIFY request (PS to S-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

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

Max-Forwards: 70

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

P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66]; ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4ee]; ecf=[5555::6aa:7bb:8cc:9dd]

Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.visited1.net;lr>

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

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

Call-ID: b89rjhnedlrfjflslj40a222

CSeq: 90 NOTIFY

Subscription-State: active;expires=4900

Event: presence.winfo

Contact: <sip:ps.home1.net>

Content-Type: application/watcherinfo+xml

Content-Length: (…)

<?xml version="1.0"?>

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

version="0" state="partial">

<watcher-list resource="sip:user1_public1@home1.net" package="presence">

<watcher id="77ajsyy76" event="subscribe"

status="active">sip:user2_public1@home2.net</watcher>

</watcher-list>

</watcherinfo>

P-Charging-Function-Addresses: The PS populates the P-Charging-Function-Addresses header field to be passed to the S-CSCF.

17. NOTIFY request (S-CSCF to P-CSCF) – see example in table A.6.2-17

The S-CSCF forwards the NOTIFY request to the P-CSCF.

Table A.6.2-17: NOTIFY request (S-CSCF to P-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

Max-Forwards: 69

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

P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66]; ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4ee]; ecf=[5555::6aa:7bb:8cc:9dd]

Route: <sip:pcscf1.visited1.net;lr>

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

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Contact:

Content-Type:

Content-Length:

(…)

P-Charging-Vector: The S-CSCF passes this header received.

P-Charging-Function-Addresses: The S-CSCF stores the P-Charging-Function-Addresses header field and passes this header to the P-CSCF.

18. NOTIFY request (P-CSCF to UE) – see example in table A.6.2-18

The P-CSCF forwards the NOTIFY request to the PUA in the UE.

Table A.6.2-18: NOTIFY request (P-CSCF to UE)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK351g45.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

Record-Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.home1.net:7531;lr;comp=sigcomp>

Max-Forwards: 68

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Contact:

Content-Type:

Content-Length:

(…)

19. 200 (OK) response (UE to P-CSCF) – see example in table A.6.2-19

The PUA determines that this is a full state watcher-info document and replaces any current watcher-info with the new document. The UE acknowledges the NOTIFY request with a 200 (OK) response to the P-CSCF.

Table A.6.2-19: 200 (OK) response (UE to P-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

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

From:

To:

Call-ID:

CSeq:

Content-Length: 0

20. 200 (OK) response (P-CSCF to S-CSCF) – see example in table A.6.2-20

The P-CSCF forwards the 200 (OK) response to the S-CSCF.

Table A.6.2-20: 200 (OK) response (P-CSCF to S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

P-Access-Network-Info:

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

From:

To:

Call-ID:

CSeq:

Content-Length:

21. 200 (OK) response (S-CSCF to PS) – see example in table A.6.2-21

The P-CSCF forwards the response to the PS in the home network of the UE.

Table A.6.2-21: 200 (OK) response (S-CSCF to PS)

SIP/2.0 200 OK

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

P-Access-Network-Info:

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

From:

To:

Call-ID:

CSeq:

Content-Length:

P-Charging-Vector: The PS inserts the originating Inter Operator Identifier (IOI) parameter received and.populates the identifier of its own network to the terminating Inter Operator Identifier (IOI) parameter of this header.

22. Pending new watcher subscription

The PS receives a SUBSCRIBE request from a new watcher and performs the necessary authorization checks on the originator and determines that this is a new watcher that is not yet in the watcher list.

23. NOTIFY request (PS to S-CSCF) – see example in table A.6.2-23

The PS generates a NOTIFY request containing watcher information of the new watcher pending subscription. Thus, the watcher information contains the partial state.

Table A.6.2-23 NOTIFY request (PS to S-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

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

Max-Forwards: 70

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

P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66]; ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4ee]; ecf=[5555::6aa:7bb:8cc:9dd]

Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.visited1.net;lr>

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

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

Call-ID: b89rjhnedlrfjflslj40a222

CSeq: 90 NOTIFY

Subscription-State: active;expires=5000

Event: presence.winfo

Content-Type: application/watcherinfo+xml

Contact: <sip:ps.home1.net;lr>

Content-Length: (…)

<?xml version="1.0"?>

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

version="0" state="partial">

<watcher-list resource="sip:user1_public1@home1.net" package="presence">

<watcher id="34bytzx54" event="subscribe"

status="pending">sip:user3_public1@home3.net</watcher>

</watcher-list>

</watcherinfo>

P-Charging-Function-Addresses: The PS populates the P-Charging-Function-Addresses header field to be passed to the S-CSCF.

24. NOTIFY request (S-CSCF to P-CSCF) – see example in table A.6.2-24

The S-CSCF forwards the NOTIFY request to the P-CSCF.

Table A.6.2-24: NOTIFY request (S-CSCF to P-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

Max-Forwards: 69

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

P-Charging-Function-Addresses:

Route: <sip:pcscf1.visited1.net;lr>

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

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Content-Type:

Contact:

Content-Length:

(…)

P-Charging-Vector: The S-CSCF stores the originating Inter Operator Identifier (IOI) parameter received.

P-Charging-Function-Addresses: The S-CSCF stores the P-Charging-Function-Addresses header field and passes this header to the P-CSCF.

25. NOTIFY request (P-CSCF to UE) – see example in table A.6.2-25

The P-CSCF forwards the NOTIFY request to the PUA in the UE.

Table A.6.2-25: NOTIFY request (P-CSCF to UE)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK351g45.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

Max-Forwards: 68

Record-Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.home1.net:7531;lr;comp=sigcomp>

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Content-Type:

Contact:

Content-Length:

(…)

26. 200 (OK) response (UE to P-CSCF) – see example in table A.6.2-26

The PUA determines that this is a partial state notification of watcher-info and adds the new pending subscription to its existing watcher-info document. The UE acknowledges the NOTIFY request with a 200 (OK) response to the P-CSCF.

Table A.6.2-26: 200 (OK) response (UE to P-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

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

From:

To:

Call-ID:

CSeq:

Content-Length: 0

27. 200 (OK) response (P-CSCF to S-CSCF) – see example in table A.6.2-27

The P-CSCF forwards the 200 (OK) response to the S-CSCF.

Table A.6.2-27: 200 (OK) response (P-CSCF to S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

P-Access-Network-Info:

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

From:

To:

Call-ID:

CSeq:

Content-Length:

28. 200 (OK) response (S-CSCF to PS) – see example in table A.6.2-28

The P-CSCF forwards the response to the PS in the home network of the UE.

Table A.6.2-28: 200 (OK) response (S-CSCF to PS)

SIP/2.0 200 OK

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

P-Access-Network-Info:

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

From:

To:

Call-ID:

CSeq:

Content-Length:

P-Charging-Vector: The S-CSCF insertes the originating Inter Operator Identifier (IOI) parameter received and populates the identifier of its own network to the terminating Inter Operator Identifier (IOI) parameter of this header.

29. Authorization of watcher

The presentity determines to allow the watcher to access the presence information. The PUA modifies the authorization policy by authorizing presence information for sip:user3_public1@home3.net.

30. NOTIFY request (PS to S-CSCF) – see example in table A.6.2-30

The authorization event means changes in the watcher information, which triggers a new NOTIFY request. The watcher information included in the NOTIFY request contains the accepted subscription of sip:user3_public1@home3.net.

Table A.6.2-30 NOTIFY request (PS to S-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

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

Max-Forwards: 70

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

P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66]; ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4ee]; ecf=[5555::6aa:7bb:8cc:9dd]

Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.visited1.net;lr>

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

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

Call-ID: b89rjhnedlrfjflslj40a222

CSeq: 90 NOTIFY

Subscription-State: active;expires=4900

Event: presence.winfo

Content-Type: application/watcherinfo+xml

Contact: <sip:ps.home1.net;lr>

Content-Length: (…)

<?xml version="1.0"?>

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

version="0" state="partial">

<watcher-list resource="sip:user1_public1@home1.net" package="presence">

<watcher id="34bytzx54" event="subscribe"

status="active">sip:user3_public1@home3.net</watcher>

</watcher-list>

</watcherinfo>

P-Charging-Function-Addresses: The PS populates the P-Charging-Function-Addresses header field to be passed to the S-CSCF.

31. NOTIFY request (S-CSCF to P-CSCF) – see example in table A.6.2-31

The S-CSCF forwards the NOTIFY request to the P-CSCF.

Table A.6.2-31: NOTIFY request (S-CSCF to P-CSCF)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

Max-Forwards: 69

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

P-Charging-Function-Addresses:

Route: <sip:pcscf1.visited1.net;lr>

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

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Content-Type:

Contact:

Content-Length:

(…)

P-Charging-Vector: The S-CSCF stores the originating Inter Operator Identifier (IOI) parameter received.

P-Charging-Function-Addresses: The S-CSCF stores the P-Charging-Function-Addresses header field and passes this header to the P-CSCF.

32. NOTIFY request (P-CSCF to UE) – see example in table A.6.2-32

The P-CSCF forwards the NOTIFY request to the PUA in the UE.

Table A.6.2-32: NOTIFY request (P-CSCF to UE)

NOTIFY sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK351g45.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

Max-Forwards: 68

Record-Route: <sip:scscf1.home1.net;lr>, <sip:pcscf1.home1.net:7531;lr;comp=sigcomp>

From:

To:

Call-ID:

CSeq:

Subscription-State:

Event:

Content-Type:

Contact:

Content-Length:

(…)

33. 200 (OK) response (UE to P-CSCF) – see example in table A.6.2-33

The PUA determines that this is a partial state notification of watcher-info and updates the active subscription to its existing watcher-info document. The UE acknowledges the NOTIFY request with a 200 (OK) response to the P-CSCF.

Table A.6.2-33: 200 (OK) response (UE to P-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=240f34.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.1, SIP/2.0/UDP ps.home2.net;branch=z9hG4bK348923.1

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

From:

To:

Call-ID:

CSeq:

Content-Length: 0

34. 200 (OK) response (P-CSCF to S-CSCF) – see example in table A.6.2-34

The P-CSCF forwards the 200 (OK) response to the S-CSCF.

Table A.6.2-34: 200 (OK) response (P-CSCF to S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP ps.home1.net;branch=z9hG4bK240f34.1

P-Access-Network-Info:

From:

To:

Call-ID:

CSeq:

Content-Length:

35. 200 (OK) response (S-CSCF to PS) – see example in table A.6.2-35

The P-CSCF forwards the response to the PS in the home network of the UE.

Table A.6.2-35: 200 (OK) response (S-CSCF to PS)

SIP/2.0 200 OK

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

P-Access-Network-Info:

From:

To:

Call-ID:

CSeq:

Content-Length: