ETSI TS 122 141 V16.0.0 (2020-08)

ETSI TS 122 141 V16.0.0 (2020-08)
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Presence service;
Stage 1
(3GPP TS 22.141 version 16.0.0 Release 16)
---------------------- Page: 1 ----------------------
3GPP TS 22.141 version 16.0.0 Release 16 1 ETSI TS 122 141 V16.0.0 (2020-08)
Reference
RTS/TSGS-0122141vg00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or

print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any

existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI

deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.

Users of the present document should be aware that the document may be subject to revision or change of status.

Information on the current status of this and other ETSI documents is available at

If you find errors in the present document, please send your comment to one of the following services:

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying

The content of the PDF version shall not be modified without the written authorization of ETSI.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and

oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and

IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information

pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found

in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in

respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee

can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.

ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no

right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does

not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).

The present document may refer to technical specifications or reports using their 3GPP identities. These shall be

The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and

"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

Intellectual Property Rights ................................................................................................................................ 2

Legal Notice ....................................................................................................................................................... 2

Modal verbs terminology .................................................................................................................................... 2

Foreword ............................................................................................................................................................. 4

Introduction ........................................................................................................................................................ 4

1 Scope ........................................................................................................................................................ 6

2 References ................................................................................................................................................ 6

2.1 Acknowledgement .............................................................................................................................................. 6

3 Definitions, symbols and abbreviations ................................................................................................... 7

3.1 Definitions .......................................................................................................................................................... 7

3.2 Abbreviations ..................................................................................................................................................... 7

4 Presence models ....................................................................................................................................... 8

4a A brief introduction to the Presence Service ...................................................................................................... 8

4.1 Informative models........................................................................................................................................... 10

4.2 Roles in the presence service ............................................................................................................................ 10

4.3 Presence information ........................................................................................................................................ 12

5 High level requirements ......................................................................................................................... 13

5.1 Home Environment requirements ..................................................................................................................... 13

5.3 General requirements ....................................................................................................................................... 13

5.4 Management requirements ............................................................................................................................... 15

5.5 Notification and acknowledgement requirements ............................................................................................ 17

6 Privacy .................................................................................................................................................... 17

6.1 General privacy requirements ........................................................................................................................... 17

6.2 Access rules ...................................................................................................................................................... 17

7 Security................................................................................................................................................... 18

8 Charging ................................................................................................................................................. 18

9 Administration ........................................................................................................................................ 18

9.1 Provision .......................................................................................................................................................... 18

9.2 Withdrawal ....................................................................................................................................................... 19

9.3 Registration ...................................................................................................................................................... 19

9.4 Erasure .............................................................................................................................................................. 19

9.5 Activation ......................................................................................................................................................... 19

9.6 Deactivation ..................................................................................................................................................... 19

9.7 Invocation ......................................................................................................................................................... 20

Annex A (informative): Example presence service use cases.............................................................. 21

Annex B (informative): Change history ............................................................................................... 24

History .............................................................................................................................................................. 26

This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal

TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,

z the third digit is incremented when editorial only changes have been incorporated in the document.

This specification defines the requirements for the support of the presence service. The presence service results in

presence information of a user and information on a user's devices, services and services components being managed by

the network. Together, user, these devices, services and services components are termed presentity (presence entity).

This TS makes extensive use of internet terminology to ensure alignment with the presence service description and

The presence service provides access to presence information to be made available to other users or services.

Exploitation of this service, see figure 1, will enable the creation of enhanced rich multimedia services along the lines of

Presence is an attribute related to, but quite different from mobility information, and is a service that can be exploited to

create additional services. The types of services that could be supported by the presence service may include:

The presence service will enable new multimedia services to exploit this key enabler to support other advanced

multimedia services and communications. These new services may infer the context, availability and

willingness of a user to accept or participate in particular types of communications by accessing the presence

information for the user's devices and services. Examples of such new multimedia services that could potentially

exploit the presence service include "chat", instant messaging, multimedia messaging, e-mail, , handling of

The presence service may also be exploited to enable the creation of services in which abstract entities are

providing the services to the mobile community. The presence service may be used to support such abstract

services as cinema ticket information, the score at a football match, motorway traffic status, advanced push

Existing services may also be significantly enhanced by exploiting the presence information. For example a user

may dynamically arrange for his wireless services to be supported through his corporate PABX whilst he is on-

site, require media to be converted and directed to specific devices (e.g. user cannot accept a voice call whilst in

a meeting, but is prepared to receive the voice call converted to text in the form of an SMS/MMS/e-mail

message). The presence service may also be used to enable the creation of advanced versions of CS/PS services,

The following figure 1 represents a logical overview of how services could exploit the presence service to create

A presence-enabled service as observed by the user is a service in which the user can control the dissemination of his

presence information to other users and services, and also be able to explicitly identify specifically which other users

and services to which he provides presence status. Combined with the capability of other users' control of their own

presence status, virtually infinite combinations of users and services interacting at different levels can be created.

The exploitation of the presence service is already available in the internet world, although unfortunately with different

non interoperable mechanisms. This specification identifies the requirements for support of an enhanced version of the

presence service through the support of attributes (e.g. services, media components of a multimedia service, location

information) in an interoperable manner within both wireless and fixed networks, and with external networks.

This TS defines the stage one description for the presence service. Stage one is the set of requirements which shall be

supported to enable the exploitation of the presence service, seen primarily from the users' and home environments’

This TS includes information applicable to the home environment, device and network manufacturers which are

Additional functionalities not documented in this TS are considered outside the scope of this TS. Such additional

functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional

functionality shall not compromise conformance to the requirements of the presence service defined in this

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

• References are either specific (identified by date of publication, edition number, version number, etc.) or

• 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

[1] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services

[3] RFC 2778: "A Model for Presence and Instant Messaging"; http://www.ietf.org/rfc.html.

[4] RFC 2779 "Instant Messaging / Presence Protocol Requirement"; http://www.ietf.org/rfc.html.

Settings\Temp\ZipTemp\ http:\www.ietf.org\internet-drafts\draft-ietf-impp-cpim-05.txt

This document contains extracts of documents, the copyright of which is vested in the Internet Society. The terms of the

Internet Society copyright are fulfilled by the reproduction of the copyright and paragraph below. This copyright only

applies to text in this document that has been directly reproduced from the appropriate RFC.

This document and translations of it may be copied and furnished to others, and derivative works that comment

on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in

whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are

included on all such copies and derivative works. However, this document itself may not be modified in any

way, such as by removing the copyright notice or references to the Internet Society or other Internet

organizations, except as needed for the purpose of developing Internet standards in which case the procedures for

copyrights defined in the Internet Standards process must be followed, or as required to translate it into

Access rules: constraints on how the presence service makes presence information available to watchers. For each

presentity’s presence information, the applicable access rules are managed by the principal that controls the presentity.

availability: a property of a presentity denoting its ability and willingness to communicate based on factors such as the

identity or properties of the watcher and the preferences and/or policies that are associated with the presentity

fetcher: a form of watcher that has asked the presence service for the presence information of one or more presentities,

but is not requesting a notification from the presence service of (future) changes in a presentity's presence information.

identifier: a means of indicating a point of contact, intended for public use such as on a business card. Telephone

numbers, email addresses, and typical home page URLs are all examples of identifier in other systems.

presence information: is a set of attributes characterising current properties of presentities such as status, an optional

presence service: the capability to support management of presence information between watchers and presentities, in

presentity (presence entity): any uniquely identifiable entity that is capable of providing presence information to

presence service. Examples of presentities are devices, services etc. Any presentity shall have one, and only one,

principal: human, organisation, program, or collection of humans, organisations and/or programs that chooses to

appear to the presence services as a single actor, distinct from all other principals. A principal is associated with one or

more presentities and/or watchers. A principal is said to "own" a certain presentity or watcher if such an association

exists. Within the context of this specification a subscriber may be a principal to one or more presentities and/or

watchers. Examples: A subscriber may be a principal to the terminals (the presentities) he owns. A program, providing

a stock exchange information service to customers, may be the principal to the market quotations (the presentities) it

Note: The case where a presentity is not a subscriber requires to be further considered

subscribed-watcher: a subscribed-watcher is a type of watcher, which requests notification from the presence service

of changes in a presentity's presence information, resulting in a watcher-subscription, as they occur in the future.

watcher-subscription: the information kept by the presence service about a subscribed-watcher's request to be notified

Note: This definition represents an entity's request to obtain presence information, and is not related to the term

"subscription" in [1]. Within this specification the term watcher-subscription (and its derivatives) purely

watcher: any uniquely identifiable entity that requests presence information about a presentity, or watcher information

about a watcher, from the presence service. Special types of watcher are fetcher, poller, and subscribed-watcher. Any

watcher information: information about watchers that have received or may receive presence information about a

This clause attempts to give a simplistic high level informative overview of what presence is from a user’s perspective,

Mark’s ability and willingness to be reached for communication is defined by a set of information known as presence

information. Mark’s presence information may be related to his mobile network connection status, however it

represents much more than just whether he has network coverage or not. Mark also defines a set of access rules to

control access to his presence information. For the presence service, Mark is represented by a presentity (presence

entity) associated with Mark's presence information and set of access rules.. In this example, Mark’s presence

Figure 1: Principal and his representation in the presence information as a presentity

As well as representing a user such as Mark, a presentity may even be created to represent an abstract service or

application (e.g. to provide road traffic information, sports results, news headlines etc.). The entity represented by the

Presentity (in this case Mark) controls the supply of information for the presentity and is known as the principal; thus

Paggy, Paul and Jude (e.g. Mark’s callers or instant messaging buddies) who want to determine Mark’s ability (and

willingness) to communicate may do so by checking the status information in Mark’s presentity. By doing so, Paggy,

To protect his privacy and confidentiality, Mark has full control over whether Paggy, Paul and Jude, or any other group

of watchers, can access his presence information. Mark may give different watchers different levels of access so that,

for example Paggy can see all of Mark’s of presence information, Paul may only see part of it, and Jude can see none of

it. Hence, Mark can control (per watcher) which parts of his presence information may be seen, and he may decide that

specific watchers have restricted access, and that some do not have any access at all. Indeed, Mark may also define his

presence information and set up his access rules so that some watchers are given different information (e.g. Jude is told

Mark’s presentity consists of dynamic and static information supplied directly by himself and/or by the network. Some

of the dynamic information may be derived from a number of sources (e.g. equipment login/attachment, roaming status,

keyboard activity monitoring, equipment type, location information etc.). An example of the static information could

be a fixed telephone number. The network may also add further information to the presentity (e.g. the evening/night

times when his mobile is usually switched offderived from his usage patterns) to provide customised presence

By supporting a presence service in the network, the operator has the capability to offer an exciting range of advanced

The below models of the presence service and presence information are not definitive, and no implementation model or

architecture is implied or required by them, and are solely provided to describe the functions and roles that shall be

The presence service may be considered to support two main roles, as depicted in figure 2"Presence service model".