ImageVerifierCode 换一换
格式:PDF , 页数:38 ,大小:274.72KB ,
资源ID:736707      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-736707.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(ETSI TR 123 976-2018 Universal Mobile Telecommunications System (UMTS) LTE Push architecture (V15 0 0 3GPP TR 23 976 version 15 0 0 Release 15).pdf)为本站会员(fuellot230)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

ETSI TR 123 976-2018 Universal Mobile Telecommunications System (UMTS) LTE Push architecture (V15 0 0 3GPP TR 23 976 version 15 0 0 Release 15).pdf

1、 ETSI TR 123 976 V15.0.0 (2018-06) Universal Mobile Telecommunications System (UMTS); LTE; Push architecture (3GPP TR 23.976 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 123 976 V15.0.0 (2018-06)13GPP TR 23.976 version 15.0.0 Release 15Reference RTR/TSGS-0223976vf00 Keywords LTE,UMTS ETS

2、I 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 from: http:

3、/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 di

4、fference 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 revision or

5、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/CommiteeSuppo

6、rtStaff.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 authoriza

7、tion of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the bene

8、fit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 123 976 V15.0.0 (2018-06)23GPP TR 23.976 version 15.0.0 Release 15Intellectual Property Ri

9、ghts 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 Rig

10、hts (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, h

11、as 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 tra

12、denames 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 cons

13、titute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP ident

14、ities, 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 found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present documen

15、t “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 citat

16、ion. ETSI ETSI TR 123 976 V15.0.0 (2018-06)33GPP TR 23.976 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Arc

17、hitecture requirements 9g34.1 Delivery network independent support for Push service 9g34.2 Selection of delivery network . 9g34.3 Delivery network support of acknowledged and unacknowledged Push Data delivery . 9g35 Push architecture overview 9g35.1 PS domain delivery networks supporting push 10g35.

18、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 notification with user connect scenario 12g35.1.3.2 Push broadcast scenario 12g35.1.3.3 Addressing 13g35.1.3.4 Delivery reliabi

19、lity 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 Accounting START/STOP messages 14g35.1.4.4 COPS DRQ operation . 15g35.1.4.5 Keep alive messages . 15g35.1.4.6 PDP context re-establis

20、hment . 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 . 16g35.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 NRPC

21、A using a Presence server . 19g35.1.5.3 Comparison of NRPCA approaches 20g35.2 CS domain delivery networks supporting Push 20g35.2.1 CS domain network elements and interfaces supporting Push . 21g35.2.2 Push using SMS in the CS domain . 21g35.3 IMS delivery networks supporting Push 21g35.3.1 IMS net

22、work elements and interfaces supporting Push 21g35.3.2 Push based on SIP . 22g35.4 MBMS delivery networks supporting Push 22g35.5 WLAN delivery networks supporting Push 22g36 Analysis and conclusion . 22g36.1 Comparison summary of Push requirements to Push mechanisms 22g36.2 Conclusion 28g3Annex A:

23、PDP Context State Notification message procedures 30g3Annex B: NRPCA with no restrictions on APN and GPRS configuration . 32g3ETSI ETSI TR 123 976 V15.0.0 (2018-06)43GPP TR 23.976 version 15.0.0 Release 15Annex C: Change history 36g3History 37g3ETSI ETSI TR 123 976 V15.0.0 (2018-06)53GPP TR 23.976 v

24、ersion 15.0.0 Release 15Foreword This Technical Report has been produced by the 3rdGeneration 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

25、 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

26、 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. ETSI ETSI TR 123 976 V15.0.0 (2018-06)63GPP TR 23.976 version 15.0.0

27、Release 151 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 the work of TR 23.875 (3GPP internal report). This technical report describes methods for supporting push services by 3GPP del

28、ivery networks. The mechanisms described apply to existing delivery networks for the 3GPP Packet Switched (PS) domain, Circuit Switched (CS) domain, IP Multimedia Core Network Subsystem (IMS), Multimedia Broadcast / Multicast Service (MBMS), and Wireless Local Area Network (WLAN). Any necessary chan

29、ges 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 Application Servers is outside the scope of this work. The definition of Push Functionality that is best implemented in push App

30、lication 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 provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (i

31、dentified 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

32、 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 3GPP TS 22.060: “General Packet Radio Service (GPRS); Service description; Stage 1“. 3 3GPP TS 22.174: “Push service; Stage 1“.

33、 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 realization of the Short Message Service (SMS)“. 6 3GPP TS 23.060: “ General Packet Radio Service (GPRS); Service description; Stage 2“

34、. 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 Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)

35、“. 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 and Packet Data Networks (PDN)“. 12 3GPP TS 24.229: “Internet Protocol (IP) multimedia call control protocol based on Session

36、 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 3265: “Session Initiation Protocol (SIP) - Specific Event Notification“. 15 3GPP TS 23.207: “End-to-end Quality of Service (

37、QoS) concept and architecture“. ETSI ETSI TR 123 976 V15.0.0 (2018-06)73GPP TR 23.976 version 15.0.0 Release 1516 3GPP TR 23.917: “Dynamic policy control enhancements for End to end Quality of Service (QoS)“. 17 IETF RFC 2748: “Common Open Policy Service protocol (COPS)“. 18 ITU-T Recommendation E.1

38、64: “The international public telecommunication numbering plan“. 19 IETF RFC 792: “Internet Control Message Protocol“. 20 IETF RFC 1035: “Domain names Implementation and specification“. 21 IETF RFC 2486: “The Network Access Identifier“. 22 3GPP TS 29.060: “General Packet Radio Service (GPRS); GPRS T

39、unnelling Protocol (GTP) across the Gn and Gp interface“. 23 3GPP TS 23.141: “Presence Service; Architecture and functional description“. 24 3GPP TS 43.010: “GSM Public Land Mobile Network (PLMN) connection types“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the pres

40、ent 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 connectionless or connection oriented manner. A delivery network may be a GPRS bearer service. Application Server: a server that provides push ser

41、vices 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 Application Server to provide push services to a user. The address may be permanently assigned (static) or temporarily assigned (dynamic). user-ID: an id

42、entity 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 services. user availability: the ability of an delivery network to transfer data to a subscribed user. long-lived PDP Context: a PDP Context that r

43、emains 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 remains 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 initia

44、tor 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 for delivering the Push Data to the Push Recipient. Push Initiator: the entity that originates Push Data and submits it to the Push Function for deli

45、very 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 applica

46、tion level address, and the device, machine or person which uses the Push Data. Push service: a service capability offered by the PLMN that transfers 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

47、 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 Push Data to the user. This may include textual browsers, voice browsers, search engines, machine or device interface software, etc. ETSI ETSI TR

48、123 976 V15.0.0 (2018-06)83GPP TR 23.976 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the following abbreviations apply: APN Access Point Name AR Address ResolverAS Application Server CS Circuit SwitchedCSCF Call Server Control Function COPS Common Open Policy

49、 Service DHCP Dynamic Host Configuration Protocol DNS Domain Name Service DRQ Delete Request EDGE Enhanced Data rates for GSM Evolution GERAN GSM / EDGE 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 Service Control ISDN Integrated Services Digital Network IWF InterWorking Funct

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1