Content for TS 23.141 Word version: 18.0.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Presence Architecture
4.1 Overview
4.2 Reference Architecture Model
4.3 Reference points
4.4 Support of OSA Presence Service Capability Server in the Presence Architecture
...
...
1 Scope p. 6
The present document describes the stage 2 description (architectural solution and functionalities) for the Presence Service, which includes the elements necessary to realise the stage 1 requirements in TS 22.141.
The present document includes information applicable to network operators, service providers and manufacturers.
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]
RFC 3863: "Presence Information Data Format", August 2004.
[4]
RFC 3856: "A Presence Event Package for the Session Initiation Protocol (SIP)", August 2004.
[5]
TS 33.203: "3G security; Access security for IP-based services".
[6]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[7]
TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[8]
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[9]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[10]
TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".
[11] Void.
[12] Void.
[13]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN)".
[14]
TS 23.271: "Location Services (LCS); Functional description; Stage 2".
[15]
TS 23.198: "Open Service Access (OSA); Stage 2".
[16]
RFC 2778: "A Model for Presence and Instant Messaging".
[17]
RFC 2779: "Instant Messaging / Presence Protocol Requirements".
[18]
TS 23.002: "Network architecture".
[19] Void.
[20]
LIF TS 101: "Mobile Location Protocol Specification"(Location Interoperability Forum 2001) [Available at http://www.openmobilealliance.org].
[21]
TR 23.981: "Interworking aspects and migration scenarios for IPv4 based IMS implementations".
[22]
3GPP2 X.S0027-004: "Network Presence".
[23]
3GPP2 X.S0004: "Introduction to MAP".
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
For the purposes of the present document, the terms and definitions defined in TR 21.905 and TS 22.141 and the following apply:
Presence List Server:
functional entity that stores grouped lists of watched presentities and enables a Watcher Application to subscribe to the presence of multiple presentities using a single transaction.
Presence Network Agent:
network located element that collects and sends network related presence information on behalf of the presentity to a presence server.
Presentity Presence Proxy:
functional entity that provides presentity related functionality such as determining the presence server associated with a presentity.
Presence Server:
network entity responsible for managing presence information on behalf of a presence entity.
Presence User Agent:
a terminal or network located element that collects and sends user related presence information to a presence server on behalf of a Principal.
Watcher Presence Proxy:
a functional entity that provides watcher related function such as authentication of watchers.
3.2 Abbreviations p. 7
For the purposes of the present document, the abbreviations in TR 21.905 and TS 22.141 and the following apply:
AAA
Authentication, Authorisation and Accounting
CAMEL
Customised Applications for Mobile network Enhanced Logic
CAP
CAMEL Application Part
CGI
Cell Global Identity
CS
Circuit Switched
CSCF
Call Session Control Function
GGSN
Gateway GPRS Support Node
GMLC
Gateway Mobile Location Centre
GPRS
General Packet Radio Service
HLR
Home Location Register
HSS
Home Subscriber Server
HTTP
Hyper Text Transport Protocol
I-CSCF
Interrogating CSCF
IETF
Internet Engineering Task Force
IMS
IP Multimedia Subsystem
ISDN
Integrated Service Digital Network
LIF
Location Interoperability Forum
MAP
Mobile Application Part
MSC
Mobile Switching Centre
MSISDN
Mobile Subscriber ISDN Number
P-CSCF
Proxy CSCF
PDG
Packet Data Gateway
PLMN
Public Land Mobile Network
PS
Packet Switched
PUA
Presence User Agent
RFC
Request For Comments
SAI
Service Area Identity
S-CSCF
Serving CSCF
SGSN
Serving GPRS Support Node
SIP
Session Initiation Protocol
SMS
Short Message Service
UE
User Equipment
URL
Uniform Resource Locator
WAP
Wireless Access Protocol
WLAN
Wireless Local Area Network
WML
Wireless Markup Language
WV
Wireless Village
4 Presence Architecture p. 8
4.1 Overview p. 8
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.
4.2 Reference Architecture Model p. 8
The generic reference architectural model for providing presence service is depicted in Figure 4.2-1 below. The details of the elements in the figure (e.g. agents, proxies) are provided in clause 5.
The mapping of the Presence Service functional elements and reference points to the functional elements and reference points in the 3GPP Network Architecture TS 23.002 (and additionally IMS) is defined in clauses 4.3 and clause 5.
4.3 Reference points p. 9
4.3.1 Reference point Presence User Agent - Presence Server (Peu) p. 9
This reference point shall allow the Presence User Agent to manage subscription authorization policies.
IPv6 shall be supported for all functionalities required from a Presence User Agent that supports the Peu reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Peu. However, early IMS implementations and deployments may use IPv4;if IPv4 is used, the guidelines and recommendations in TR 23.981 should be followed.
This reference point uses capabilities defined for the Ut reference point as defined in TS 23.002.
4.3.2 Reference point Presence Network Agent - Presence Server (Pen) p. 9
This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations to the size of the presence information.
Pen shall provide mechanisms for the Network Agent to manage subscription authorisation policies.
Pen shall provide mechanisms for the Network Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server.
Pen shall provide mechanisms for activating or deactivating the reporting of Presence Information for a given presentity from the network entities within the PLMN.
The Pen interface is an intra-operator interface. In order to provide the all the functionalities required on this reference point, a combination of multiple protocols may be used. In general the protocols used at the Pen reference point are not standardised. However, for 3GPP2 systems this reference point is defined in X.S0027-004 [x]. At least, this interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3].
4.3.3 Reference point Presence External Agent - Presence Server (Pex) p. 10
This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations on the size of the presence information.
Pex shall provide mechanisms for the Presence External Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server.
In order to provide all the functionalities required on this reference point, a combination of multiple protocols may be used. Presence information obtained from an external network by the Presence External Agent is transferred across the Pex reference point to the Presence Server. This interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3].
4.3.4 Reference point Watcher applications - Presentity Presence Proxy (Pw) p. 10
This reference point shall allow a Watcher application to request and obtain presence information. This interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3].
The transport shall not impose any limitations to the size of the presence information.
In order to provide all the functionalities required on this interface, a combination of multiple protocols may be used.
This reference point shall support both presence monitoring and fetching modes. In the fetching mode, it shall be possible for the watcher to once request all or only a subset of a presentity's presence information (e.g. one or more tuples). The subset of the presence information is defined by the filter that is carried in the presence information subscription.
In the monitoring mode, it shall be possible for the watcher to request monitoring of all or a subset of a presentity's presence information (i.e. one or more tuples) . Watcher shall be able to explicitly indicate the capability to process partial updates. The subset of the presence information is defined by the filter that is carried in the presence information subscription. It shall be possible for the watcher to request the presence server to filter out information when the watcher is equal to the publishing Presence User Agent.
It shall be possible for the notifications containing the presentity's presence information to contain only information as defined by filters. It shall be possible for the notifications containing the presentity's presence information to contain only the modified tuples, i.e. only those tuples which have changed since the last notification.
This reference point may allow a Watcher application to use presence lists in presence information subscriptions, and the Watcher Presence Proxy to interface to a server that provides the functionality of Presence List Server.
IPv6 shall be supported for all functionalities required from a Watcher application that supports the Pw reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Pw. However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 should be followed.
4.3.5 Reference point HSS/HLR - Presence Network Agent (Ph) p. 10
This reference point shall allow the Presence Network Agent to query HSS/HLR about the state and status of a subscriber (associated with a presentity) from the serving network (for 3GPP this is the CS domain or GPRS) and IMS perspective.
This reference point permits the Presence Network Agent to activate and deactivate the reporting of mobility management events from the serving network (for 3GPP this is the CS domain or GPRS) and/or the IMS-specific reports from the S-CSCF.
This reference point uses capabilities defined for the Sh reference point as defined in TS 23.002 as well as the MAP interface.
4.3.6 Reference point S-CSCF - Presence Network Agent (Pi) p. 11
The S-CSCF may provide IMS-specific presence information (e.g. about IMS registration state). This reference point shall use mechanisms defined for the ISC reference point as defined in TS 23.002.
4.3.7 Reference point Presentity Presence Proxy - HSS (Px) p. 11
The Px interface is an intra-operator interface. This interface shall assist locating the Presence Server of the presentity. This interface is implemented using the mechanisms defined for the Cx and Dx reference points as defined in TS 23.002.
4.3.8 Reference point Presence Network Agent - GMLC (Pl) p. 11
This reference point shall be used by the Presence Network Agent to retrieve location information related to a subscriber (associated with the presentity). This reference point is the interface to GMLC and it is an instance of the Le reference point (defined in TS 23.271 and TS 23.002). In the case of Presence the LCS client (defined in TS 23.271) is the Presence Network Agent and so the protocol implementing Pl needs to be defined. Though normally a stage 3 responsibility in this case the protocol to be used is defined here since it is a reference to an existing protocol. Thus, Pl shall conform to OMA's LIF-MLP specification [20].
For 3GPP2 systems, the interface for this reference point is to the 3GPP2 Position Server and is not supported in the current release of the specification.
4.3.9 Reference point Presence Network Agent - SGSN (Pg) p. 11
This reference point shall allow the SGSN to report mobility management related events (such as attach/not reachable for paging/detach/routing area update) to the Presence Network Agent.
This reference point may allow the SGSN to report Mobility States (such as Detached, Idle and Connected) and Session States (such as PDP context active and inactive).
This reference point is implemented using the existing mechanisms of CAMEL phase 4, 3GPP Release 5.
For 3GPP2 systems, this reference point is not supported.
4.3.10 Reference point Presence Network Agent -MSC Server/VLR (Pc) p. 11
This reference point shall allow the MSC Server/VLR to report the mobility management related events to the Network Agent (such as attach/detach/location area update) and may allow the MSC Server/VLR to report call related events (such as call setup with the bearer information and call release).
This reference point may allow the MSC Server/ VLR to report Mobility States (such as Detached, Idle and Connected) and Call States (such as Busy with Bearer information and Idle).
This reference point is implemented using the existing mechanisms of CAMEL phase 4, 3GPP Release 5.
For 3GPP2 systems, the interface to this reference point is defined in 3GPP2 X.S0004 [23].
4.3.11 Reference point Presence Network Agent - GGSN (Pk) p. 11
This reference point shall allow the GGSN to report presence relevant events to the Presence Network Agent (such as PDP context activation/de-activation). This reference point is implemented using the mechanisms of the RADIUS interface for reporting of access requests on Gi reference point as defined in TS 29.061.
For 3GPP2 systems, this reference point is not supported.
4.3.12 Reference point Presence Network Agent - 3GPP AAA Server (Pr) p. 12
This reference point shall allow the 3GPP AAA Server to report IP-connectivity related events to the Presence Network Agent (such as WLAN UE attaching/detaching and tunnel establishment/removal). The Pr reference point shall be as much as possible based on mechanisms of existing interfaces.
For 3GPP2 systems, the interface for this reference point is to the AAA server and is defined in X.S0027-004 [22].
4.3.13 Reference point Presence Network Agent - PDG (Pp) p. 12
This reference point shall allow the PDG to report presence relevant events to the Presence Network Agent (such as tunnel establishment/removal, allocation of the remote IP address for the WLAN UE). This reference point is based on reusing of the Wi reference point.
For 3GPP2 systems, this reference point is not supported.
4.3.14 Reference point Presence User Agent - Presentity Presence Proxy (Pep) p. 12
This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations on the size of the presence information. This interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3].
Pep shall provide mechanisms for the Presence User Agent to obtain information on watcher subscriptions to the presentity's presence information.
Pep shall provide mechanisms for the Presence User Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server. It shall also be possible for the Presence User Agent to supply the complete presence document over Pep.
Pep shall support SIP-based communications for publishing presence information.
IPv6 shall be supported for all functionalities required from a Presence User Agent that supports the Pep reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Pep. However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 should be followed.
4.3.15 Reference point Presentity Presence Proxy - Presence Server (Pwp) p. 12
The Pwp interface is an intra-operator interface. This reference point shall allow all the functionalities provided by the Pw and Pep reference points.
4.3.16 Reference point Watcher Applications - Presence List Server (Pet) p. 12
This reference point shall allow a Watcher application to manage presence list information in the Presence List Server.
This reference point uses capabilities defined for the Ut reference point as defined in TS 23.228.
4.4 Support of OSA Presence Service Capability Server in the Presence Architecture p. 12
An OSA API may be provided to allow external application to access presence service features, details of which are found in TS 23.198.
The OSA Presence SCS may act like a presentity or a watcher. The application may then register as a presentity and/or watcher, to supply presence information, to request presence information, to be notified of subsequent changes, to request watcher information, and to manage subscription authorisation policies.
