A.2 Introduction

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

A.2.1 General

The signalling flows provided in this annex follow the methodology developed in 3GPP TS 24.228 [8]. The following additional considerations apply:

a) 3GPP TS 24.228 [8] shows separate signalling flows with no configuration hiding between networks, and with configuration hiding between networks. There is no presence specific functionality associated with this hiding, and therefore such separate signalling flows are not show in the present document; and

b) 3GPP TS 24.228 [8] does not show the functionality between the S-CSCF and the AS. As the presence service depends on the functionality provided by various AS, the signalling flows between S-CSCF and AS are shown in the present document.

A.2.2 Key required to interpret signalling flows

The key to interpret signalling flows specified in 3GPP TS 24.228 [8] subclauses 4.1 and 4.2 applies with the additions specified below.

– rls.home1.net: an RLS in the home network of the watcher;

– rls.home2.net: an RLS in the home network of the service provider, but not the home network of the watcher;

– ps.home1.net: a PS in the home network of the publisher;

– ps.home2.net: a PS in the home network of the service provider, but not in that of the watcher;

– user1_list1@home1.net: a resource list being subscribed to on a RLS in the home network;

– user2_list1@home2.net: a resource list being subscribed to on a RLS in the home network of the service provider, but not the home network of the subscriber;

– user1_public1@home1.net: presentity being watched, own watcher list;

– user3_public1@home3.net: presentity being watched.

As in 3GPP TS 24.228 [8], in order to differentiate between SIP methods and other protocol messages, the message name is preceded with the associated protocol for all non-SIP messages. Where the XCAP is used to map an HTTP URI to an XML document, the protocol name "XCAP" is used for both the HTTP request and HTTP response.

Each signalling flow table contains descriptions for headers where the content of the header is new to that signalling flow, as is already performed in 3GPP TS 24.228 [8].

However, 3GPP TS 24.228 [8] includes extensive descriptions for the contents of various headers following each of the tables representing the contents of the signalling flows. Where the operation of the header is identical to that shown in 3GPP TS 24.228 [8], then such text is not reproduced in the present document.

Additional text may also be found on the contents of headers within 3GPP TS 24.228 [8] in addition to the material shown in the present document.