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

加入VIP,免费下载
 

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

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

下载须知

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

版权提示 | 免责声明

本文(ETSI TS 128 390-2018 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fixed Mobile Convergence (FMC) Interface Integration Reference Point (IRP) S.pdf)为本站会员(towelfact221)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

ETSI TS 128 390-2018 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fixed Mobile Convergence (FMC) Interface Integration Reference Point (IRP) S.pdf

1、 ETSI TS 128 390 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fixed Mobile Convergence (FMC); Interface Integration Reference Point (IRP) Solution Profiles (SPs) (3GPP TS 28.390 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS

2、 128 390 V15.0.0 (2018-07)13GPP TS 28.390 version 15.0.0 Release 15Reference RTS/TSGS-0528390vf00 Keywords 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 en

3、registre la Sous-Prfecture 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

4、document shall not 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

5、within ETSI Secretariat. 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the p

6、resent document, please send 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 autho

7、rized by written permission 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trade

8、marks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit 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 G

9、SM Association. ETSI ETSI TS 128 390 V15.0.0 (2018-07)23GPP TS 28.390 version 15.0.0 Release 15Intellectual Property Rights 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,

10、is publicly available for ETSI members and non-members, and 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 t

11、he ETSI Web server (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

12、be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames 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 righ

13、t to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Gener

14、ation 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 corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP

15、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 “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Draftin

16、g 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 128 390 V15.0.0 (2018-07)33GPP TS 28.390 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs t

17、erminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 NGCOR Fault Management Solution Profile. 6g34.1 Requirement statements . 6g34.2 System context . 9g34.3 SP . 9g3Annex A (informative): Change history . 11g

18、3History 12g3ETSI ETSI TS 128 390 V15.0.0 (2018-07)43GPP TS 28.390 version 15.0.0 Release 15Foreword 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 may change follo

19、wing 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; 2 presented to

20、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 incorporated in the docu

21、ment. ETSI ETSI TS 128 390 V15.0.0 (2018-07)53GPP TS 28.390 version 15.0.0 Release 151 Scope The objective of this specification is to define a set of Solution Profiles (SPs) for Interface IRPs. Each SP identifies the necessary and sufficient subset of the 3GPP IRP defined solutions (solutions) requ

22、ired for the network management of a specific operating environment or domain, including that defined for the converged management environments. A specific operating environment or domain is characterised by a set of Requirement statements. In other words, the solutions identified in a specific SP w

23、ould satisfy the Requirements listed in that same SP. An SP, in its simplest form, is nothing else than a list of solutions (e.g. 3GPP IRP defined operations). The purpose is to place a combination of solutions under a common (SP) name so that: - Operators and vendors need not decide arbitrarily whi

24、ch solutions are to be used to satisfy the Requirements; - There is one document where readers can have a clear view of solutions, specified in various IRP specifications, required to satisfy the Requirements. This version of the TS contains a number of SPs defined in clause 4 and onwards, one claus

25、e for each SP. 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 number, etc.) or non-specific. - For a specific re

26、ference, 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 document in the same Release as the present docum

27、ent. 1 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 2 NGMN Alliance NGCOR: “Next Generation Converged Operations Requirements” v1.3. 3 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference

28、Point (IRP): Information Service (IS)”. 4 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS)”. 5 3GPP TS 32.352: “Telecommunication management; Communication Surveillance (CS) Integration Reference Po

29、int (IRP); Information Service (IS)”. 6 3GPP TS 32.332: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Information Service (IS)”. 7 3GPP TS 32.122: “Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Information S

30、ervice (IS)”. 8 3GPP TS 21.905: “Vocabulary for 3GPP Specifications”. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 8 and TS 32.150 1 apply. A term defined in the present document takes precedence over

31、the definition of the same term, if any, in TR 21.905 8. ETSI ETSI TS 128 390 V15.0.0 (2018-07)63GPP TS 28.390 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 8, TS 32.150 1 and the following apply. An abbreviation defined in

32、the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 8. FM Fault Management NGCOR Next Generation Converged Operations Requirements SP Solution Profile 4 NGCOR Fault Management Solution Profile 4.1 Requirement statements These requirement statement

33、s, pertaining to fault management, are extracted from 2. The REQ-GEN (122) statements are from section 2 of 2. The REQ-FM (18) statements are from section 5 of 2. REQ-GEN (122) REQ-GEN (1) “Plug - A: The related operation supports the related requirement. REQ-FM (1) requires the use of ITU-T X.733 d

34、efined structured information. Current IRP solution supports the use of all X.733 defined Probable Causes. Current IRP solution supports a subset of X.733 defined Event Type. Enhancement of current IRP may need to be considered. - B: the related operation supports the related requirement. REQ-FM (5)

35、 requires a query type of service for both alarms and events. Current IRP supports a query type service for alarms (e.g. result of a query is carried by the response of the query request). The current IRP supports an export facility with filtering capability for events (e.g. result of an query is ca

36、rried in a file and not in the response of the query request). - C: The related operation supports the related requirement. REQ-FM (12) requires support of Toggle and Transient Rule of activateAAMRule () only. - *: Some requirements are stated in a general form (e.g. “REQ-GEN (2) Useful”) and are re

37、lated to the design principle of the protocol and implementation. They are not related to any particular operation(s) or notification(s); nevertheless these IRPs in general support those requirements. Their requirement column headings are marked with a * (e.g. “REQ-FM(9)”). ETSI ETSI TS 128 390 V15.

38、0.0 (2018-07)103GPP TS 28.390 version 15.0.0 Release 15Table 4.3-1: NGCOR FM SP REQ-FM () REQ-GEN () 1 2 3 4 5 6 7 8 9* 10 11 12 13 1-18* 19 20-22* Alarm IRP 3 acknowledgeAlarms X getAlarmList A X X X notifyNewAlarm A X X notifyAckStateChanged X X notifyChangedAlarm X notifyClearedAlarm X X X notify

39、AlarmListRebuilt X X AAM IRP 7 activateAAMRule C deactivateAAMRule X getAAMRules X Notification IRP 4 subscribe X X unsubscribe X X CS IRP 5 setHeartbeatPeriod X X triggerHeartbeat X notifyHeartbeat X NL IRP 6 subscribeLog X unsubscribeLog X exportLogRecords B X ETSI ETSI TS 128 390 V15.0.0 (2018-07

40、)113GPP TS 28.390 version 15.0.0 Release 15Annex A (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2013-06 SA#60 SP-130280 Presented to SA Plenary for approval 1.1.1 2.0.0 2013-06 Upgrade of approved version 2.0.0 12.0.0 2014-12 SA#66 SP-140798 001 1 R

41、emove feature support statement 12.0.0 12.1.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.1.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 ETSI ETSI TS 128 390 V15.0.0 (2018-07)123GPP TS 28.390 version 15.0.0 Release 15History Document history V15.0.0 July 2018 Publication

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