1、 ETSI TR 1Universal Mobile TelPu(3GPP TR 23.9TECHNICAL REPORT 123 976 V13.0.0 (2016elecommunications System (LTE; Push architecture .976 version 13.0.0 Release 1316-01) (UMTS); 13) ETSI ETSI TR 123 976 V13.0.0 (2016-01)13GPP TR 23.976 version 13.0.0 Release 13Reference RTR/TSGS-0223976vd00 Keywords
2、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 de Grasse (06) N 7803/88 Important notice The present document can be downloaded
3、 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
4、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. Users of the present document should be aware that the document may be subject to
5、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 your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSup
6、portStaff.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 authori
7、zation 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 logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE a
8、re 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 TR 123 976 V13.0.0 (2016-01)23GPP TR 23.976 version 13.0.0 Release 13Intellectual Property Rights IPRs
9、 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 can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or pot
10、entially 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.
11、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. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Proje
12、ct (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 corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can
13、 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 f
14、or the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 123 976 V13.0.0 (2016-01)33GPP TR 23.976 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword
15、. 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Architecture requirements 9g34.1 Delivery network independent support for Push service 9g34.2 Selection of delivery network . 9g34.3 Delivery network support of acknowledged and
16、unacknowledged Push Data delivery . 9g35 Push architecture overview 9g35.1 PS domain delivery networks supporting push 10g35.1.1 PS domain network elements and interfaces supporting Push 10g35.1.2 NRPCA with static IP address assignment . 11g35.1.3 Push using SMS in the PS domain 11g35.1.3.1 Push no
17、tification with user connect scenario 12g35.1.3.2 Push broadcast scenario 12g35.1.3.3 Addressing 13g35.1.3.4 Delivery reliability 13g35.1.4 Push using Long-Lived PDP Context . 14g35.1.4.1 Internet Control Message Protocol 14g35.1.4.2 PDP Context State Notification message 14g35.1.4.3 Radius Accounti
18、ng START/STOP messages 15g35.1.4.4 COPS DRQ operation . 15g35.1.4.5 Keep alive messages . 15g35.1.4.6 PDP context re-establishment . 15g35.1.4.7 Presence information . 15g35.1.4.8 Comparison . 15g35.1.5 NRPCA with dynamic IP address assignment 16g35.1.5.1 NRPCA with one GGSN per Push service APN . 1
19、6g35.1.5.1.1 Deactivate PDP Context and update Address Resolver . 18g35.1.5.1.2 Address Resolver and User-ID 19g35.1.5.2 NRPCA using a Presence server . 19g35.1.5.3 Comparison of NRPCA approaches 20g35.2 CS domain delivery networks supporting Push 21g35.2.1 CS domain network elements and interfaces
20、supporting Push . 21g35.2.2 Push using SMS in the CS domain . 22g35.3 IMS delivery networks supporting Push 22g35.3.1 IMS network elements and interfaces supporting Push 22g35.3.2 Push based on SIP . 22g35.4 MBMS delivery networks supporting Push 23g35.5 WLAN delivery networks supporting Push 23g36
21、Analysis and conclusion . 23g36.1 Comparison summary of Push requirements to Push mechanisms 23g36.2 Conclusion 28g3Annex A: PDP Context State Notification message procedures 30g3Annex B: NRPCA with no restrictions on APN and GPRS configuration . 32g3ETSI ETSI TR 123 976 V13.0.0 (2016-01)43GPP TR 23
22、.976 version 13.0.0 Release 13Annex C: Change history 36g3History 37g3ETSI ETSI TR 123 976 V13.0.0 (2016-01)53GPP TR 23.976 version 13.0.0 Release 13Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to c
23、ontinuing 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
24、 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 editori
25、al only changes have been incorporated in the document. ETSI ETSI TR 123 976 V13.0.0 (2016-01)63GPP TR 23.976 version 13.0.0 Release 131 Scope The purpose of this technical report is to analyse the service requirements for push services as defined in TS 22.174 “Push service; Stage 1“. It continues t
26、he work of TR 23.875 (3GPP internal report). This technical report describes methods for supporting push services by 3GPP delivery networks. The mechanisms described apply to existing delivery networks for the 3GPP Packet Switched (PS) domain, Circuit Switched (CS) domain, IP Multimedia Core Network
27、 Subsystem (IMS), Multimedia Broadcast / Multicast Service (MBMS), and Wireless Local Area Network (WLAN). Any necessary changes identified during this work will be introduced by means of change requests to the appropriate specifications. The definition of Push Functionality that applies to push App
28、lication Servers is outside the scope of this work. The definition of Push Functionality that is best implemented in push Application Servers such as a Push Proxy and Push Initiator will be undertaken by other standards bodies and industry forums. 2 References The following documents contain provisi
29、ons 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 re
30、ference, 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: “ Vocabulary for 3GPP Specifications “. 2 3G
31、PP TS 22.060: “General Packet Radio Service (GPRS); Service description; Stage 1“. 3 3GPP TS 22.174: “Push service; Stage 1“. 4 3GPP TR 23.039: “Interface Protocols for the Connection of Short Message Service Centres (SMSCs) to Short Message Entities (SMEs)“. 5 3GPP TS 23.040: “ Technical realizatio
32、n of the Short Message Service (SMS)“. 6 3GPP TS 23.060: “ General Packet Radio Service (GPRS); Service description; Stage 2“. 7 3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2“. 8 3GPP TS 23.002: “Network architecture“. 9 3GPP TS 29.007: “General requirements on interworking between the Pub
33、lic Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)“. 10 3GPP TR 23.910: “Circuit switched data bearer services“. 11 3GPP TS 29.061: “Interworking between the Public Land Mobile Network (PLMN) supporting packet based services
34、and Packet Data Networks (PDN)“. 12 3GPP TS 24.229: “Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 13 IETF RFC 3428: “Session Initiation Protocol (SIP) Extension for Instant Messaging“. 14 IETF RFC
35、 3265: “Session Initiation Protocol (SIP) - Specific Event Notification“. ETSI ETSI TR 123 976 V13.0.0 (2016-01)73GPP TR 23.976 version 13.0.0 Release 1315 3GPP TS 23.207: “End-to-end Quality of Service (QoS) concept and architecture“. 16 3GPP TR 23.917: “Dynamic policy control enhancements for End
36、to end Quality of Service (QoS)“. 17 IETF RFC 2748: “Common Open Policy Service protocol (COPS)“. 18 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“. 19 IETF RFC 792: “Internet Control Message Protocol“. 20 IETF RFC 1035: “Domain names Implementation and speci
37、fication“. 21 IETF RFC 2486: “The Network Access Identifier“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 22.174 3 and the following apply. delivery network: transfers Push Data from Push Function to UE in a
38、 connectionless or connection oriented manner. A delivery network may be a GPRS bearer service. Application Server: a server that provides push services through a delivery network, e.g. via an IP connection user IP address: an IP address provided by the delivery network that can be used by an Applic
39、ation Server to provide push services to a user. The address may be permanently assigned (static) or temporarily assigned (dynamic). user-ID: an identity or name that can be used to deliver push content to a user in a delivery network. The format of user-ID is dependent on the protocol for the push
40、services. user availability: the ability of an delivery network to transfer data to a subscribed user. long-lived PDP Context: a PDP Context that remains active/open for an indefinite period of time. Also referred to as “always-on PDP context“. always-on PDP Context: this is a PDP Context that remai
41、ns active/open for an indefinite period of time. Also referred to as “long-lived PDP context“. PDP Context: Push Data: data sent by the push initiator to the Push Recipient. Push Function: the entity in the PLMN that receives the Push Data from the Push Initiator. The Push Function is responsible fo
42、r delivering the Push Data to the Push Recipient. 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 D
43、ata 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. Push service: a service capability offered by the PLMN that transfers Pus
44、h 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: any software or device associated with a Push Recipient that interprets
45、 Push Data to the user. This may include textual browsers, voice browsers, search engines, machine or device interface software, etc. ETSI ETSI TR 123 976 V13.0.0 (2016-01)83GPP TR 23.976 version 13.0.0 Release 133.2 Abbreviations For the purposes of the present document, the following abbreviations
46、 apply: APN Access Point Name AR Address ResolverAS Application Server CS Circuit SwitchedCSCF Call Server Control Function COPS Common Open Policy Service DHCP Dynamic Host Configuration Protocol DNS Domain Name Service DRQ Delete Request EDGE Enhanced Data rates for GSM Evolution GERAN GSM / EDGE
47、RAN GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GSM Global System for Mobile communication HLR Home Location Register HPLMN Home PLMN ICMP Internet Control Message Protocol IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identifier IP Internet Protocol ISC IMS S
48、ervice Control ISDN Integrated Services Digital Network IWF InterWorking Function LAN Local Area Network NM Notification Message MSC Mobile Switching Centre MSISDN Mobile Station ISDN number NRPCA Network Requested PDP Context Activation OMA Open Mobile Alliance P-CSCF Proxy CSCF PDF Policy Decision
49、 Function PDN Packet Data Network PDP Packet Data Protocol PDU Protocol Data Unit PF Push Function PI Push Initiator PLMN Public Land Mobile Network PS Packet Switched PS Presence ServerPSTN Public Switched Telephone Network RAN Radio Access Network S-CSCF Serving CSCF SGSN Serving GPRS Support Node SIP Session Initiation Protocol SMS Short Message Service SMSC Short Message Service Centre TBD To Be Decided TI Transaction Identifier UE User Equipment URI Uniform Resource Identifier UTRAN Universal Terrestrial RAN VPLMN Visited PLM
