ETSI TS 122 174 V17.0.0 (2022-04)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Push Service; Service aspects; Stage 1 (3GPP TS 22.174 version 17.0.0 Release 17)

RTS/TSGS-0122174vh00

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 08-Apr-2022

Standards Content (Sample)

ETSI TS 122 174 V17.0.0 (2022-04)






TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Push Service;
Service aspects;
Stage 1
(3GPP TS 22.174 version 17.0.0 Release 17)

---------------------- Page: 1 ----------------------
3GPP TS 22.174 version 17.0.0 Release 17 1 ETSI TS 122 174 V17.0.0 (2022-04)

Reference
RTS/TSGS-0122174vh00
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 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
warranty is made of merchantability or fitness
and/or governmental rule and/or regulation and further, no representation or
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2022.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3GPP TS 22.174 version 17.0.0 Release 17 2 ETSI TS 122 174 V17.0.0 (2022-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
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.
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.174 version 17.0.0 Release 17 3 ETSI TS 122 174 V17.0.0 (2022-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 5
3.1 Definitions . 5
3.2 Abbreviations . 6
4 Overview of the Push Service . 6
5 Requirements . 7
5.1 General . 8
5.2 Provisioning . 8
5.3 Subscription . 8
5.4 Addressing and Routing . 9
5.5 Delivery . 9
5.6 Service Management . 10
6 Security. 10
7 Privacy . 10
8 Access rules . 11
9 Charging . 11
10 Push Subscription Profile Information . 12
11 Roaming . 12
12 Barring of the Push Service . 12
Annex A (informative): Change history . 13
History . 15

ETSI

---------------------- Page: 4 ----------------------
3GPP TS 22.174 version 17.0.0 Release 17 4 ETSI TS 122 174 V17.0.0 (2022-04)
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
The Push Service introduces a means to transmit push data from a push initiator to a push recipient (e.g. a UE) without
a previous user action. The push concept, as provided by the SMS teleservice, has been very successful in the GSM
second generation, both for text messaging (for user viewing) and for other unstandardized data to the SIM (as a
building block used for OTA and other purposes). This TS introduces the Push Service as a generalization of existing
network capabilities plus the development of new capabilities. The Push Service should therefore be understood as a
building block (network capability), which can be used for new services, both public and private, in 3GPP.
In the normal client/server model, a client requests a service or information from a server, which then responds in
transmitting information to the client. This is known as the "pull" technology, the user pulls information from the
content provider. The World Wide Web is a typical example of pull technology, where a user enters a URL (the
request) that is sent to a server and the server answers by sending a Web page (the response) to the user.
In contrast to this there is also the "push" technology where there is no explicit request from the user before the content
provider (push initiator) initiates an information transfer to a user. Another way of saying this is that whereas "pull"
transaction of information are always initiated from the user, "push" transactions are content provider initiated.
The welcome message received after registration with a visited network whilst roaming is an example of information
transfer that has been initiated without a request from the user. Typically, a user signs up with the push initiator and
defines their interest, volume of information acceptable and other factors in the push subscription profile. As
information becomes available that satisfies the user’s push subscription profile, the push initiator delivers it to the user
using the Push Service.
The Push service may be used to implement high level services such as IP multimedia services, MMS, etc., and new
services including public safety, government, corporate IT, transfer of push data to machines and devices, in addition to
infotainment type services.
Another common use for push services is the delivery of notification from e.g. MMS to the user while the user has the
option of "pulling" the actual push data from the push initiator.
The PLMN Push function provides the push data to the user agent in the UE. The user agent interprets and presents the
push data to a person, device or machine using the UE.
NOTE: The requirements of services such as streaming, conversational services and broadcast are independent
from push. Therefore they are not considered appropriate for inclusion here. Push will be available for use
in appropriate applications of all high level services.
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 22.174 version 17.0.0 Release 17 5 ETSI TS 122 174 V17.0.0 (2022-04)
1 Scope
This Technical Specification defines the Stage 1 description of the Push Service and is the set of requirements that shall
be supported for the provision of push, seen primarily from the subscriber’s, service providers’ and delivery network
points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers. It
is of use to manufacturers and organisations which have devices or machines benefiting by availability of push service.
This TS contains the core requirements for the Push Service, for operator and external Push Initiators, which are sufficient
to provide a complete service capability and service capability feature.
This TS defines the requirements for the Push Service to enable delivery of push data, including such functionality as:
• Transfer of push data from a Push Initiator to a Push Recipient
• Latency and Priority classes,
• Definition of handling of undeliverable push data.
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 TS 21.133: "3G security; Security threats and requirements".
[2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[3] 3GPP TS 22.240: "Service requirements for 3GPP Generic User Profile (GUP); Stage 1".
3 Definitions and abbreviations
Definitions and abbreviations used in the present document are listed in TR 21.905 [2]. For the purposes of this
document the following definitions and abbreviations apply:
3.1 Definitions
Push Data: data sent by the push initiator to the push recipient, of a format known to the receiver (push recipient), and
not otherwise defined by the push service.
PLMN: the 3GPP network that receives the push data from the push initiator and ensures the delivery of push data to
the push recipient. The delivery of the push data may involve other networks.
Push function: the function in the PLMN that receives the Push Data from the Push initiator. The push function is
responsible for delivering the push data to the Push recipient.
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 22.174 version 17.0.0 Release 17 6 ETSI TS 122 174 V17.0.0 (2022-04)
Push initiator: the entity that originates push data and submits it to the push function for delivery to a Push recipient. A
Push initiator may be e.g. an application providing value added services.
Push recipient: the entity that receives the push data from the Push function and processes or uses it. This may include
the UE with which the PLMN communicates with, the user agent with the application level address, and the device,
machine or person which uses the push data. A Push recipient is controlled by an individual user .
Push service: a service capability offered by the PLMN. The Push Service is initiated by a Push Initiator in order to
transfer push data (e.g. data, multimedia content) from the Push Initiator to the Push Recipient without a previous user
action. The Push Service could be used as a basic capability or as component of a value added service.
Push User agent: is any software or device associated with a Push recipient that interprets Push Data to the user. This
may include textual browsers, voice browsers, search engines, machine or device interface software, etc.
Push Subscription Profile: a set of parameters indicating the Push recipient’s settings and preferences for the Push
Service.
3.2 Abbreviations
For the purposes of this document the following abbreviations apply:
URL – Uniform Resource Locator.
4 Overview of the Push Service
The overview of push is followed by a summary of the relationships among the entities involved (operators, users, push
recipients and push initiators).
NOTE: these are functional descriptions: multiple functions may, depending on business arrangements, be performed
by a single entity.

User,

Device,
PLMN
Or
Push
Machine
function
Push
Push
Initiator
Recipient
Push Service

Figure 1: Push Service Overview
The Push Service is a service whereby the Push Initiator sends push data through a Push Server to a Push Recipient,
without interaction from the Push Recipient.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 22.174 version 17.0.0 Release 17 7 ETSI TS 122 174 V17.0.0 (2022-04)
The typical mode of operation is as follows:
• A Push Recipient (e.g. user, receiving device like a meter) explicitly or implicitly subscribes to a set of value
added services offered by various Push Initiators and allow these Push Initiators to send it push data that meet
the Push Recipient’s configured criteria. (This configured criteria is part of the Push user profile.)
• A Push Initiator identifies information matching the criteria set by the Push Initiator and package it up into the
push data
• The Push Initiator delivers the push
...