ETSI TS 122 141 V15.0.0 (2019-07)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Presence service; Stage 1 (3GPP TS 22.141 version 15.0.0 Release 15)

RTS/TSGS-0122141vf00

General Information

• Status: Published
• Publication Date: 22-Jul-2019
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 23-Jul-2019

Standards Content (Sample)

ETSI TS 122 141 V15.0.0 (2019-07)






TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Presence service;
Stage 1
(3GPP TS 22.141 version 15.0.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 1 ETSI TS 122 141 V15.0.0 (2019-07)



Reference
RTS/TSGS-0122141vf00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2019.
All rights reserved.

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
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 2 ETSI TS 122 141 V15.0.0 (2019-07)
Intellectual Property Rights
Essential patents
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
server (https://ipr.etsi.org/).
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
server) which are, or may be, or may become, essential to the present document.
Trademarks
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.
Legal Notice
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
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
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
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 3 ETSI TS 122 141 V15.0.0 (2019-07)
Contents
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

ETSI

---------------------- Page: 4 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 4 ETSI TS 122 141 V15.0.0 (2019-07)
Foreword
rd
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
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
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
behaviour in internet recommendations.
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
those currently present in the internet world.
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:
- New communications services
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
individual media in a multimedia session etc.
- Information services
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
services etc.
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 5 ETSI TS 122 141 V15.0.0 (2019-07)
- Enhanced existing services
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,
enable terminal capabilities support etc.
The following figure 1 represents a logical overview of how services could exploit the presence service to create
advanced services.
VisitVisiteed ned nettwworkorkss
Home Environment
Home Environment
PrPreseseennccee--enhaenhanncceded
PS domain
Voice services
Voice services
IntInteernernett
Data services
Data services
Pr e sence
Supplementary services
Supplementary services
Multimedia services
Multimedia services
IMS
CS domain
OtOtheherr net netwwoorrkkss

Figure 1: Logical presence service support of services
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.
ETSI
AAbbsstrtraact entict entititieses

---------------------- Page: 6 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 6 ETSI TS 122 141 V15.0.0 (2019-07)
1 Scope
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’
points of view.
This TS includes information applicable to the home environment, device and network manufacturers which are
sufficient to provide complete support of the presence service.
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
specification.
2 References
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] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; Vocabulary for 3GPP Specifications".
[2] Void
[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.
[5] RFC 3863 " Presence Information Data Format (PIDF)";
C:\DOCUME~1\Michele\LOCALS~1\Documents and Settings\Michele\Local
Settings\Temp\ZipTemp\ http:\www.ietf.org\internet-drafts\draft-ietf-impp-cpim-
05.txtC:\DOCUME~1\Michele\LOCALS~1\Documents and Settings\Michele\Local
Settings\Temp\ZipTemp\ http:\www.ietf.org\internet-drafts\draft-ietf-impp-cpim-
05.txtC:\DOCUME~1\Michele\LOCALS~1\Documents and Settings\Michele\Local
Settings\Temp\ZipTemp\ http:\www.ietf.org\internet-drafts\draft-ietf-impp-cpim-05.txt
http://www.ietf.org/rfc.html.
2.1 Acknowledgement
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.
Copyright (C) The Internet Society (2000). All Rights Reserved.
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
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 7 ETSI TS 122 141 V15.0.0 (2019-07)
copyrights defined in the Internet Standards process must be followed, or as required to translate it into
languages other than English.
3 Definitions, symbols and abbreviations
3.1 Definitions
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.
poller: a fetcher that requests presence information on a regular basis.
presence information: is a set of attributes characterising current properties of presentities such as status, an optional
communication address and other optional attributes etc
presence service: the capability to support management of presence information between watchers and presentities, in
order to enable applications and services to make use of presence information
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 associated with it.
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
monitors.
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
of changes in the presence information of one or more presentities
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
refers to this relationship.
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 shall have one, and only one, principal associated with it.
watcher information: information about watchers that have received or may receive presence information about a
particular presentity within a particular recent span of time.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 8 ETSI TS 122 141 V15.0.0 (2019-07)
3.2 Abbreviations
For the purposes of this document the following abbreviations apply:
IETF Internet Engineering Task Force
LAN Local Area Network
VHE Virtual Home Environment
4 Presence models
4a A brief introduction to the Presence Service
This clause attempts to give a simplistic high level informative overview of what presence is from a user’s perspective,
and how it is used to published to, and accessed by, other users.
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
information consists of user status and location information.


My name is Mark and I am supported by the
presence service. I have a presentity which
represents me, and I am the principal of my
presentity. As the principal, I supply
information to my presentity.

Available
User Status
Access
Discreet
Rules

Not available
My presentity consists
Invisib le
of information
(describing my ability

City Location
and willingness to
communicate) and
Country
access rules
(describing how my
Mark’s Presentity
presence information
may be accessed).

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
Mark is principal of his presentity (see Figure 1).
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,
Paul and Jude become watchers of Mark (see Figure 2).

ETSI

---------------------- Page: 9 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 9 ETSI TS 122 141 V15.0.0 (2019-07)

Oh dear, here
Hello Mark, the
comes trouble!
car needs
fixing!
Paggy
Hello Mark, how
about a drink?
Mark
Available
User Status
Paul
Access
Discreet
Rules

Not available
Hello Mark, have you seeen
Invisib le
Paul?

City Location
Countr y
Jude

Mark’s Presentity
Hello Mark,
we’ve got a
great job
for you!
Watcher group


Figure 2: Watchers of Mark
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
that Mark is not available, when in fact he is available), see Figure 3.


…I think the car
Hello, weather is
alarm is playing up…
great here!
Paggy
…see you in the
bar at 7:30
Mark

Available

User Status
Paul
Access
Discreet
Rules
Not ava ilable

Invisible
City
Location

Country
Jude
Mark’s Presentity
…shame, Mark can’t
tell me where Paul is
…looks like
Mark is not
Watcher group
around!

Figure 3: Application of Mark’s access rules on watchers
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 22.141 version 15.0.0 Release 15 10 ETSI TS 122 141 V15.0.0 (2019-07)
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
information.
By supporting a presence service in the network, the operator has the capability to offer an exciting range of advanced
presence-based services and applications.
4.1 Informative models
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
provided by the presence service.
4.2 Roles in the presence service
PRESENCE SERVICE
PRESENTITY WATCHER
FETCHER SUBSCRIBED-
WATCHER
Fetcher requests the current
value of some Presentity’s
presence information from the
Presence Service
Subscribed-watcher is a Watcher that
requests notification of (future) changes
in some Presentity’s presence
information from the Presence Service
POLLER
A Poller is a Fetcher that
requests the current value of
some Presentity’s presence
information from the Presence
Service on a regular basis.

Figure 2: Presence service model
The presence service may be considered to support two main roles, as depicted in figure 2"Presence service model".
For the purposes of this TS, the following roles are id
...