Content for TS 24.141 Word version: 18.0.0

1 Scope p. 6

The present document provides the protocol details for the presence service within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in TS 24.229.

Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by TS 24.229.

Requirements for manipulation of presence data are defined by use of a protocol at the Ut reference point based on XML Configuration Access Protocol (XCAP) (RFC 4825).

The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing presence functionality.

2 References p. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 22.141: "Presence Service; Stage 1".

[3]

TS 23.002: "Network architecture".

[4]

TS 23.141: "Presence service; Architecture and functional description; Stage 2".

[5]

TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".

[6]

TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".

[7]

TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua); Protocol details".

[8]

TS 24.228: Release 5: "Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

[9]

TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

[10]

TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".

[11]

TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)".

[12]

RFC 2664 (1999): "FYI on Questions and Answers - Answers to Commonly asked New Internet User Questions".

[13] Void.

[14]

RFC 2387 (August 1998): "The MIME Multipart/Related Content-type".

[15] Void.

[15A] Void.

[16]

RFC 2778 (2000): "A Model for Presence and Instant Messaging".

[17]

RFC 3261 (June 2002): "SIP: Session Initiation Protocol".

[18]

RFC 3263 (June 2002): "Session Initiation Protocol (SIP): Locating SIP Servers".

[19]

RFC 6665 (July 2012): "SIP-Specific Event Notification".

[20]

RFC 3310 (2002): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)".

[21]

RFC 3863 (August 2004): "Presence Information Data Format (PIDF)".

[22]

RFC 4662 (August 2006): "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists".

[23]

RFC 3903 (October 2004): "Session Initiation Protocol (SIP) for Event State Publication".

[24]

RFC 5263 (September 2008): "Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information".

[25]

RFC 5196 (September 2008): "Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)".

[26]

RFC 4480 (July 2006): "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)".

[27]

RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".

[28]

RFC 3857 (August 2004): "A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)".

[29]

RFC 3858 (August 2004): "An Extensible Markup Language (XML) Based Format for Watcher Information".

[30]

RFC 4661 (September 2006): "An Extensible Markup Language (XML) Based Format for Event Notification Filtering".

[31]

RFC 4660 (September 2006): "Functional Description of Event Notification Filtering".

[32]

RFC 4482 (July 2006): "CIPID: Contact Information for the Presence Information Data Format".

[33]

RFC 4825 (May 2007): "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".

[34]

RFC 4827 (May 2007): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents".

[35]

RFC 5025 (December 2007): "Presence Authorization Rules".

[35A]

RFC 4745 (February 2007): "Common Policy: A Document Format for Expressing Privacy Preferences".

[36]

RFC 4826 (May 2007): "An Extensible Markup Language (XML) Formats for Representing Resource Lists".

[37]

RFC 4119 (December 2005): "A Presence-based GEOPRIV Location Object Format".

[38]

RFC 5262 (September 2008): "Presence Information Data Format (PIDF) Extension for Partial Presence".

[39]

RFC 5874 (May 2010): "An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources".

[40]

RFC 4483 (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages".

[41] Void.

[42] Void.

[43]

RFC 5875 (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".

[44]

RFC 4479 (July 2006): "A Data Model for Presence".

[45]

RFC 5264 (September 2008): "Publication of Partial Presence Information".

[46]

3GPP2 X.S0027-004: "Network Presence".

[47] Void

[48]

3GPP2 S.S0109: "Generic bootstrapping architecture"

[49]

3GPP2 S.S0114: "Security mechanisms using GBA"

[50] Void

[51]

TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".

[52]

RFC 7231 (June 2014): "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".

[53]

RFC 7616 (September 2015): "HTTP Digest Access Authentication".

3 Definitions and abbreviations p. 8

3.1 Definitions p. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply:

subscription authorization policy:

a policy that determines which watchers are allowed to subscribe to diffa presentity's presence information

The subscription authorization policy also determines to which presentity's presence information the watcher has access.

For the purposes of the present document, the following terms and definitions given in TS 23.141 apply:

Presence list server

Presence Network Agent (PNA)

Presence Server (PS)

Presence User Agent (PUA)

For the purposes of the present document, the following terms and definitions from RFC 2778 apply:

Presence tuple

Presentity

For the purposes of the present document, the following terms and definitions from RFC 3903 apply:

Event Publication Agent (EPA)

Event State Compositor (ESC)

For the purposes of the present document, the following terms and definitions from RFC 4825 apply:

XCAP client

XCAP server

For the purposes of the present document, the following terms and definitions from RFC 4662 apply:

Resource List Server (RLS)

For the purposes of the present document, the following terms and definitions given in RFC 1594.

Fully-Qualified Domain Name (FQDN)

For the purposes of the present document, the following terms and definitions given in RFC 3261 apply:

Final response

Header

Header field

Method

Request

Response

(SIP) transaction

Status-code (see Section 7.2 of RFC 3261)

Tag (see Section 19.3 of RFC 3261)

For the purposes of the present document, the following terms and definitions given in subclause 4.1.1.1 of TS 23.002 and subclause 4a.7 of TS 23.002, apply:

Call Session Control Function (CSCF)

Home Subscriber Server (HSS)

For the purposes of the present document, the following terms and definitions given in subclause 3.1 of TS 23.218 apply:

Filter criteria

Initial filter criteria

Subsequent request

For the purposes of the present document, the following terms and definitions given in subclause 4.3.3.1 of TS 23.228 and subclause 4.6 of TS 23.228 apply:

Interrogating-CSCF (I-CSCF)

Proxy-CSCF (P-CSCF)

Serving-CSCF (S-CSCF)

For the purposes of the present document, the following terms and definitions given in TR 21.905 apply:

User Equipment (UE)

For the purposes of the present document, the following terms and definitions from TS 33.222 apply:

Authentication Proxy

3.2 Abbreviations p. 9

For the purposes of the present document, the following abbreviations apply:

Application Server

AUID

Application Unique ID

Core Network

CPIM

Common Profile for Instant Messaging

CSCF

Call Session Control Function

EPA

Event Publication Agent

ESC

Event State Compositor

HSS

Home Subscriber Server

HTTP

HyperText Transfer Protocol

I-CSCF

Interrogating - CSCF

IP Multimedia

IOI

Inter Operator Identifier

Internet Protocol

MIME

Multipurpose Internet Mail Extensions

P-CSCF

Proxy - CSCF

PIDF

Presence Information Data Format

PNA

Presence Network Agent

Presence Server

PSI

Public Service Identity

PUA

Presence User Agent

RLMI

Resource List Meta-Information

RLS

Resource List Server

RPID

Rich Presence Information Data

S-CSCF

Serving - CSCF

SIP

Session Initiation Protocol

TLS

Transport Layer Security

User Equipment

URI

Universal Resource Identifier

XCAP

XML Configuration Access Protocol

XML

Extensible Markup Language

4 Presence service overview p. 10

The presence service provides the ability for the home network to manage presence information of a user's device, service or service media even whilst roaming. A user's presence information may be obtained through input from the user, information supplied by network entities or information supplied by elements external to the home network. Consumers of presence information, watchers, may be internal or external to the home network. The architecture for the 3GPP presence service is specified in TS 23.141.

SIP and XCAP provide means to manipulate the presence status of a user. For details on the differences between those means refer to RFC 3903 and RFC 4827. For details on the relationship of XCAP server to other roles see subclause 6.2.2.