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

加入VIP,免费下载
 

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

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

下载须知

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

版权提示 | 免责声明

本文(ETSI TS 125 442-2017 Universal Mobile Telecommunications System (UMTS) UTRAN implementation-specific O&M transport (V14 0 0 3GPP TS 25 442 version 14 0 0 Release 14)《通用移动通信系统(UMTS).pdf)为本站会员(boatfragile160)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

ETSI TS 125 442-2017 Universal Mobile Telecommunications System (UMTS) UTRAN implementation-specific O&M transport (V14 0 0 3GPP TS 25 442 version 14 0 0 Release 14)《通用移动通信系统(UMTS).pdf

1、 ETSI TS 125 442 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); UTRAN implementation-specific O 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 s

2、erver (https:/ipr.etsi.org/). Pursuant to the 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 be

3、come, essential to the present document. Foreword 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

4、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 document “shall“, “shall not“, “should“, “should not“, “may“,

5、“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 ETSI TS 125 442 V14.0.0

6、 (2017-04)33GPP TS 25.442 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Implementation Specific O 2 presented to TSG

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

8、. ETSI ETSI TS 125 442 V14.0.0 (2017-04)53GPP TS 25.442 version 14.0.0 Release 141 Scope The present document specifies the transport of implementation specific O&M signalling between Node B and the Management Platform in case that the transport is routed via the RNC. 2 References The following docu

9、ments 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. -

10、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 Void 2 Void 3 ITU-T Recommendation I.36

11、3.5 (1996-08): “B-ISDN ATM Adaptation Layer Type 5 Specification“. 4 IETF RFC 2225 (1998-04): “Classical IP and ARP over ATM“. 5 IETF RFC 2684 (1999-09): “Multiprotocol Encapsulation over ATM Adaptation Layer 5“. 6 IETF RFC 791 (1981-09): “Internet Protocol“. 7 Void 8 3GPP TS 25.426: “UTRAN Iur and

12、Iub Interface Data Transport&Transport Signalling for DCH“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Logical O&M: Logical O&M is the signalling associated with the control of logical resources owned by the RN

13、C but physically implemented in Node B. Implementation Specific O&M: Implementation Specific O&M functions depend on the implementation of the Node B, both for its hardware and software components. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AAL5 AT

14、M Adaptation Layer type 5 ATM Asynchronous Transfer Mode ARP Address Resolution Protocol RFC Request For CommentIP Internet Protocol O&M Operation and Maintenance ETSI ETSI TS 125 442 V14.0.0 (2017-04)63GPP TS 25.442 version 14.0.0 Release 14RNC Radio Network Controller TNL Transport Network Layer4

15、Implementation Specific O&M Transport 4.1 Requirements While this specification only addresses the transport of Node B Implementation Specific O&M signalling, many of the following requirements are derived from generic requirements for O&M of UMTS network elements: uni25CF Common O&M infrastructure

16、for all network elements. uni25CF Independence from various data link protocols. Support of various higher layer protocols and applications. Secure transmission. No Impact of O&M transport on traffic transport and signalling. Re-use of existing transport facilities, i.e. co-existence of Iub and Impl

17、ementation Specific O&M on the same bearer. 4.2 Routing It is the responsibility of the RNC to route Implementation Specific O&M signalling traffic. The traffic exchanged over this signalling link is completely transparent to the RNC. Both RNC and Node B have to support the routing of Implementation

18、 specific O&M via the RNC. Management Platform(s)Node BRNCManagementModelImplementationSpecificO&MIubLogical O&MNode BManagementModelNode BImplementationSpecificO&MLogical O&MRNC O&MNode BLogicalO&MNode BManagementModelRNCIubImplementationSpecific O&MtransportImplementationSpecific O&MTransportPhysi

19、calbearerPhysicalbearerFigure 1: Implementation Specific O&M Transport via RNC ETSI ETSI TS 125 442 V14.0.0 (2017-04)73GPP TS 25.442 version 14.0.0 Release 144.3 Transport Bearer An appropriate transport bearer for Implementation Specific O&M should consider the requirements listed in subclause 4.1.

20、 IP (IETF RFC 791 6) should be the transport mechanism in order to allow a data link independent support of a variety of O&M applications and protocols for the Implementation Specific O&M of the Node B. IP datagrams containing O&M signalling have to be carried over the same bearer as Iub. There are

21、two options for the implementation specific O&M signalling bearer in Iub. 1) ATM Transport option 2) IP Transport option 4.3.1 ATM Transport Option The following figure shows the protocol stack for Implementation Specific O&M transport between Node B and RNC in case of ATM transport option in Iub: F

22、igure 2: Protocol Stack for Implementation Specific O&M Transport (ATM transport option) AAL5 shall be used according to ITU-T Recommendation I.363.5 3. AAL5 virtual circuits are used to transport the IP packets containing Implementation Specific O&M signalling data between Node B and RNC. Multiple

23、VCs can be used over the interface. An association shall be made between a VC and the IP addresses that are related to this VC in the peer node side. This association can be made using O&M or using ATM Inverse ARP according to Classical IP over ATM. Classical IP over ATM protocols are used to carry

24、the IP packets over the ATM transport network. Classical IP over ATM is specified in IETF RFC 2225 4. Multiprotocol Encapsulation over AAL5 is specified in IETF RFC 2684 5. 4.3.2 IP Transport Option The following figure shows the protocol stack for Implementation Specific O&M transport between Node

25、B and RNC in case of IP transport option in Iub: IPAAL5ATMPHYData LinkLayerPHYIPAAL5ATMPHYImplementationSpecific O&MRNC Node BETSI ETSI TS 125 442 V14.0.0 (2017-04)83GPP TS 25.442 version 14.0.0 Release 14Figure 3: Protocol Stack for Implementation Specific O&M Transport (IP TNL) Implementation spec

26、ific O&M signalling is conveyed by IP between the Node B and the RNC. IP-in-IP tunneling may be applied when the Iub Transport Network Layer is used. IP based Transport Network Layer of Iub is further defined in TS 25.426 8. PHYImplementation Specific O&MNode BDatalink layer IPIPPHY PHY Datalink lay

27、er Datalink layer IPIPRNC (if tunnelled)ETSI ETSI TS 125 442 V14.0.0 (2017-04)93GPP TS 25.442 version 14.0.0 Release 14Annex A (informative): Change history Date / TSG TSG Doc. CR Rev Subject/Comment New 12/2008 - - - Creation of Rel-8 version based on v7.0.0 8.0.0 12/2009 - - - Creation of Rel-9 ve

28、rsion based on v8.0.0 9.0.0 SP-49 SP-100629 Clarification on the use of References (TS 21.801 CR#0030) 9.0.1 03/2011 Creation of Rel-10 version based on v9.0.1 10.0.0 52 RP-110685 0005 Removal of unused references 10.1.0 09/2012 Update to Rel-11 version (MCC) 11.0.0 09/2014 Update to Rel-12 version

29、(MCC) 12.0.0 12/2015 Update to Rel-13 version (MCC) 13.0.0 Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2017-03 SA#75 Promotion to Release 14 without technical change 14.0.0 ETSI ETSI TS 125 442 V14.0.0 (2017-04)103GPP TS 25.442 version 14.0.0 Release 14History Document history V14.0.0 April 2017 Publication

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