1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelS(3GPP TS 22.1TECHNICAL SPECIFICATION122 174 V13.0.0 (2016communications system (Phaelecommunications System (LTE; Push Service; Service aspects; Stage 1 .174 version 13.0.0 Release 1316-02) hase 2+); (UMTS); 13) ETSI ETSI TS 122 174 V13.0.0 (2016
2、-02)13GPP TS 22.174 version 13.0.0 Release 13Reference RTS/TSGS-0122174vd00 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 enregistre la Sous-P
3、rfecture 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
4、 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 only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secret
5、ariat. 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send
6、 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
7、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. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI
8、 logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 122 174 V1
9、3.0.0 (2016-02)23GPP TS 22.174 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document 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
10、 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
11、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. Forew
12、ord 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, UMTS identities or GSM identities. These should be interpreted as being references to the corr
13、esponding ETSI deliverables. The cross reference between GSM, UMTS, 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 “can
14、not“ 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 ETSI TS 122 174 V13.0.0 (2016-02)33GPP TS 22.174 version 13.0.0 Relea
15、se 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Overview of the Push Service 6g35 Requirements 7g35.1 General . 8g35.2 Prov
16、isioning . 8g35.3 Subscription 8g35.4 Addressing and Routing . 9g35.5 Delivery 9g35.6 Service Management 10g36 Security. 10g37 Privacy 10g38 Access rules 11g39 Charging . 11g310 Push Subscription Profile Information . 12g311 Roaming . 12g312 Barring of the Push Service 12g3Annex A (informative): Cha
17、nge history . 13g3History 15g3ETSI ETSI TS 122 174 V13.0.0 (2016-02)43GPP TS 22.174 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and
18、 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
19、; 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 incorpo
20、rated 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 te
21、xt 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
22、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
23、“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
24、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 a
25、re 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
26、 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 I
27、P 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 use
28、r 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 streamin
29、g, 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 ETSI TS 122 174 V13.0.0 (2016-02)53GPP TS 22.174 version 13.0.0 Release 13
30、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 applic
31、able 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 Ini
32、tiators, 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 P
33、riority 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
34、 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 do
35、cument 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 Defin
36、itions 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),
37、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 P
38、ush Data from the Push initiator. The push function is responsible for delivering the push data to the Push recipient. ETSI ETSI TS 122 174 V13.0.0 (2016-02)63GPP TS 22.174 version 13.0.0 Release 13Push initiator: the entity that originates push data and submits it to the push function for delivery
39、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
40、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) f
41、rom 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 incl
42、ude 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 abbreviatio
43、ns 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
44、 business arrangements, be performed by a single entity. Push Recipient PLMN User, Device, Or Machine Push Initiator Push function 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
45、interaction from the Push Recipient. ETSI ETSI TS 122 174 V13.0.0 (2016-02)73GPP TS 22.174 version 13.0.0 Release 13The 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
46、 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 int
47、o the push data The Push Initiator delivers the push data to the Push function, identifying the Recipient“s address, and optionally priority, delivery time parameters, etc. The Push function takes the responsibility of delivering the push data, optionally following the priority and delivery time par
48、ameters, to the Push Recipient and for providing feedback to the Push Initiator regarding delivery of the push data if requested by the Push Initiator. Key characteristics of the Push Service include: The Push Initiator may, but is not required to deal with the specifics of the wireless transport, s
49、election of appropriate bearers, out-of-coverage or roaming issues, and other wireless network anomalies. These are all managed by the Push Service and hence can be optimised at the network level rather than being handled by all applications. Using an available bearer the push service offers as many capabilities that are available to delivery of the push data following the requested push services requested by the push initiator. The push initiator shall be provided with a means to query the push server for a specific recipient“s push user pro
