1、 ETSI TS 128 390 V14.0.0 (2017-04) 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 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS
2、 128 390 V14.0.0 (2017-04)13GPP TS 28.390 version 14.0.0 Release 14Reference RTS/TSGS-0528390ve00 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. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLU
8、GTESTSTM, UMTSTMand the ETSI 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 Associat
9、ion. ETSI ETSI TS 128 390 V14.0.0 (2017-04)23GPP TS 28.390 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
10、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 the ETSI Web server (https:/ipr.
11、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 become, essential to
12、 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 be interpreted as
13、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“, “need not“, “will“
14、, “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 128 390 V14.0.0 (2017-04)33GPP TS
15、 28.390 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 NGCOR Fault Management Solution Profile. 6g34.1 Requir
16、ement statements . 6g34.2 System context . 9g34.3 SP . 9g3Annex A (informative): Change history . 11g3History 12g3ETSI ETSI TS 128 390 V14.0.0 (2017-04)43GPP TS 28.390 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). Th
17、e 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 document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as
18、 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 control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
19、 etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 128 390 V14.0.0 (2017-04)53GPP TS 28.390 version 14.0.0 Release 141 Scope The objective of this specification is to define a set of Solution Profiles (SPs) for Interface IRPs. Each
20、 SP identifies the necessary and sufficient subset of the 3GPP IRP defined solutions (solutions) required 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 characte
21、rised by a set of Requirement statements. In other words, the solutions identified in a specific SP would 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 o
22、f solutions under a common (SP) name so that: - Operators and vendors need not decide arbitrarily which 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 Req
23、uirements. This version of the TS contains a number of SPs defined in clause 4 and onwards, one clause 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 (identifi
24、ed 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 refere
25、nce implicitly refers to the latest version of that document in the same Release as the present document. 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 3G
26、PP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)”. 4 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS)”. 5 3G
27、PP TS 32.352: “Telecommunication management; Communication Surveillance (CS) Integration Reference Point (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: “Telecommu
28、nication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Information Service (IS)”. 8 3GPP TS 21.905: “Vocabulary for 3GPP Specifications”. ETSI ETSI TS 128 390 V14.0.0 (2017-04)63GPP TS 28.390 version 14.0.0 Release 143 Definitions, symbols and abbreviations 3.1 Defin
29、itions 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 the definition of the same term, if any, in TR 21.905 8. 3.2 Abbreviations For the purposes of the present document, the
30、 abbreviations given in TR 21.905 8, TS 32.150 1 and the following apply. An abbreviation defined in 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 Pro
31、file 4 NGCOR Fault Management Solution Profile 4.1 Requirement statements These requirement statements, 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 ETSI
32、 ETSI TS 128 390 V14.0.0 (2017-04)103GPP TS 28.390 version 14.0.0 Release 14- A: The related operation supports the related requirement. REQ-FM (1) requires the use of ITU-T X.733 defined structured information. Current IRP solution supports the use of all X.733 defined Probable Causes. Current IRP
33、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) requires a query type of service for both alarms and events. Current IRP supports a query type service for alarms (e.g
34、. 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 carried in a file and not in the response of the query request). - C: The related operation supports the related requirem
35、ent. 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 related to the design principle of the protocol and implementation. They are not related to any particular operation(s) o
36、r notification(s); nevertheless these IRPs in general support those requirements. Their requirement column headings are marked with a * (e.g. “REQ-FM(9)”). Table 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
37、X notifyNewAlarm A X X notifyAckStateChanged X X notifyChangedAlarm X notifyClearedAlarm X X X notifyAlarmListRebuilt 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
38、X NL IRP 6 subscribeLog X unsubscribeLog X exportLogRecords B X ETSI ETSI TS 128 390 V14.0.0 (2017-04)113GPP TS 28.390 version 14.0.0 Release 14Annex 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
39、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 Remove 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 ETSI ETSI TS 128 390 V14.0.0 (2017-04)123GPP TS 28.390 version 14.0.0 Release 14History Document history V14.0.0 April 2017 Publication
