1、 ETSI TS 122 174 V14.0.0 (2017-03) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Push Service; Service aspects; Stage 1 (3GPP TS 22.174 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 122 174 V14.0.0 (2017-03)13GP
2、P TS 22.174 version 14.0.0 Release 14Reference RTS/TSGS-0122174ve00 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-Prfecture
3、 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 modi
4、fied 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 Secretariat. U
5、sers 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 se
6、nd 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 permissio
7、n 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 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ET
8、SI 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
9、V14.0.0 (2017-03)23GPP TS 22.174 version 14.0.0 Release 14Intellectual 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, a
10、nd 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 th
11、e 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. For
12、eword 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 corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be f
13、ound 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 th
14、e expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 122 174 V14.0.0 (2017-03)33GPP TS 22.174 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3
15、Introduction 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 Provisioning . 8g35.3 Subscription 8g35.4 Addressing and Routing . 9g35.5 Delivery 9g35.6 Service Managem
16、ent 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): Change history . 13g3History 15g3ETSI ETSI TS 122 174 V14.0.0 (2017-03)43GPP TS 22.174 version 14.0.0 Re
17、lease 14Foreword This Technical Specification (TS) has been produced by ETSI 3rd 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 d
18、ocument, 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 c
19、ontrol. 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
20、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 bl
21、ock 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
22、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
23、 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
24、 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
25、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 bec
26、omes available that satisfies the users 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, corpora
27、te 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 funct
28、ion 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 cons
29、idered appropriate for inclusion here. Push will be available for use in appropriate applications of all high level services. ETSI ETSI TS 122 174 V14.0.0 (2017-03)53GPP TS 22.174 version 14.0.0 Release 141 Scope This Technical Specification defines the Stage 1 description of the Push Service and is
30、 the set of requirements that shall be supported for the provision of push, seen primarily from the subscribers, 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
31、 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 fea
32、ture. 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 do
33、cuments 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
34、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 thre
35、ats 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
36、 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
37、 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 t
38、o the Push recipient. ETSI ETSI TS 122 174 V14.0.0 (2017-03)63GPP TS 22.174 version 14.0.0 Release 14Push 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.
39、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 co
40、ntrolled 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 cou
41、ld 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.
42、Push Subscription Profile: a set of parameters indicating the Push recipients 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 fol
43、lowed 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. Push Recipient PLMN User, Device, Or Mach
44、ine 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 interaction from the Push Recipient. ETSI ETSI TS 122 174 V14.0.0 (2017-03)73GPP TS 22.174 version
45、 14.0.0 Release 14The 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 R
46、ecipients 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 data to the Push function, identifying the Rec
47、ipients 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 parameters, to the Push Recipient and for providing feedback to the Push Initiator regarding delivery o
48、f 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, selection of appropriate bearers, out-of-coverage or roaming issues, and other wireless network anoma
49、lies. 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 recipients push user profile subject to privacy considerations. The push server shall not change the push data (cont
