ETSI TS 132 392-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Delta synchronization .pdf

1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommDelta synchronizationInfor(3GPP TS 32.3TECHNICAL SPECIFICATION132 392 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; ion Integration Reference Poinormation Service (IS) .392 version 13.0.0 Rele

2、ase 1316-02) hase 2+); (UMTS); oint (IRP); 13) ETSI ETSI TS 132 392 V13.0.0 (2016-02)13GPP TS 32.392 version 13.0.0 Release 13Reference RTS/TSGS-0532392vd00 Keywords GSM,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

3、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:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The

4、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 difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable

5、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 change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi

6、.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/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical,

7、 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 authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Stand

8、ards 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 are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are

9、 Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 392 V13.0.0 (2016-02)23GPP TS 32.392 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these es

10、sential 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 potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest upda

11、tes 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. 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 serv

12、er) which are, or may be, or may become, 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 identiti

13、es 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 document “shall“, “shall no

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

15、ation. ETSI ETSI TS 132 392 V13.0.0 (2016-02)33GPP TS 32.392 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations .

16、 7g34 System overview 8g34.1 System context . 8g35 Information Object Classes 8g35.1 Information entities imported and local labels . 8g35.2 Class Diagram 9g35.2.1 Attributes and relationships 9g35.2.2 Inheritance 9g35.3 Information Object Class (IOC) definitions . 10g35.3.1 DeltaSynchronizationIRP

17、. 10g35.3.1.1 Definition 10g35.4 Information relationship definitions . 10g35.5 Information attribute definition 10g36 Interface definition . 11g36.1 Class diagram . 11g36.2 Generic rules 11g36.3 deltaSynchGenericParts Interface (M) . 12g36.3.1 Operation manageDeltaSynchronization (M) . 12g36.3.1.1

18、Definition 12g36.3.1.2 Input parameters 12g36.3.1.3 Output parameters . 12g36.3.1.4 Pre-condition . 12g36.3.1.5 Post-condition . 12g36.3.1.6 Exceptions . 13g36.3.2 Operation getAvailableDeltaSynchPoints (O) 14g36.3.2.1 Definition 14g36.3.2.2 Input parameters 14g36.3.2.3 Output parameters . 14g36.3.2

19、.4 Pre-condition . 15g36.3.2.5 Post-condition . 15g36.3.2.6 Exceptions . 15g36.3.3 Notification notifyNewDeltaSynchPoint (O) 16g36.3.3.1 Definition 16g36.3.3.2 Input Parameters . 16g36.3.3.3 Triggering Event . 17g36.3.3.3.1 From-state 17g36.3.3.3.2 To-state 17g36.3.4 Notification notifyStatusOfDelta

20、SynchChanged (O) 18g36.3.4.1 Definition 18g36.3.4.2 Input Parameters . 18g36.3.4.3 Triggering Event . 18g36.3.4.3.1 From-state 18g3ETSI ETSI TS 132 392 V13.0.0 (2016-02)43GPP TS 32.392 version 13.0.0 Release 136.3.4.3.2 To-state 18g36.4 deltaSynchOfCMData Interface (O) . 19g36.4.1 Operation triggerD

21、eltaSynchOfCMData (M) . 19g36.4.1.1 Definition 19g36.4.1.2 Input parameters 20g36.4.1.3 Output parameters . 21g36.4.1.4 Pre-condition . 22g36.4.1.5 Post-condition . 22g36.4.1.6 Exceptions . 22g36.5 deltaSynchOfAlarmData Interface (O) . 23g36.5.1 Operation triggerDeltaSynchOfAlarms (M) . 23g36.5.1.1

22、Definition 23g36.5.1.2 Input parameters 24g36.5.1.3 Output parameters . 25g36.5.1.4 Pre-condition . 26g36.5.1.5 Post-condition . 26g36.5.1.6 Exceptions . 26g37 Operation Modes 27g37.1 Delta Synchronization Mode DSM1 27g37.2 Delta Synchronization Mode DSM2 27g37.3 Delta Synchronization Mode DSM3 27g3

23、Annex A (informative): Modes of operation for delta synchronization . 28g3A.1 Operation Mode DSM1 28g3A.2 Operation Mode DSM2 28g3A.3 Operation Mode DSM3 28g3Annex B (informative): Change history . 29g3History 30g3ETSI ETSI TS 132 392 V13.0.0 (2016-02)53GPP TS 32.392 version 13.0.0 Release 13Forewor

24、d 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 following formal TSG approval. Should the TSG modify the contents of the present document, it will be re

25、-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 control. y the second d

26、igit 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. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnersh

27、ip Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.391: “Delta Synchronization Integration Reference Point (IRP); Requirements“. 32.392: “Delta Synchronization Integration Reference Point (IRP); Information Service (IS)“. 32.3

28、96: “Delta Synchronization Integration Reference Point (IRP); Solution Set (SS) definitions“. The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101

29、 1 and 3GPP TS 32.102 2. IRPManagers (typically Network Management Systems) and IRPAgents (typically EMs or NEs) synchronize their data concerning alarms or configuration data. In certain scenarios this synchronization is lost or not done. This IRP provides functionality to significantly reduces the

30、 amount of data which needs to be transferred in order to re-establish synchronization. ETSI ETSI TS 132 392 V13.0.0 (2016-02)63GPP TS 32.392 version 13.0.0 Release 131 Scope The purpose of Delta Synchronization IRP is to define an interface through which an IRPManager can request only those data wh

31、ich changed (i.e. changed, were created or deleted) from a synchronization point onwards. The present document is the Information Service of Delta Synchronization IRP. It defines, for the purpose of Delta Synchronization, the information observable and controlled by management systems client and it

32、also specifies the semantics of the interactions used to carry this information. 2 References The following documents contain provisions that, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition num

33、ber, 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 reference implicitly refers to the latest versio

34、n of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); No

35、tification Integration Reference Point (IRP): Information Service (IS)“. 4 3GPP TS 32.391: “Telecommunication management; Delta Synchronization Integration Reference Point (IRP): Requirements“. 5 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions

36、“. 6 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 7 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (I

37、S)“. 8 3GPP TS 32.602: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)“. 9 3GPP TS 32.662: “Telecommunication management; Configuration Management (CM); Kernel CM; Information Service (IS)“. 10 3GPP TS 32.342: “Teleco

38、mmunication management; File Transfer (FT); Integration Reference Point (IRP): Information Service (IS)“. 11 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. ETSI ETSI TS 132 392 V13.0.0 (2016-02)73GPP TS 3

39、2.392 version 13.0.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2 and 3GPP TS 32.391 4 apply. synchPoint Creation Policy: The IRPAgent may create synchronizationPoint in diffe

40、rent policies. These policies are called synchPoint creation policies. There are two synchPoint Creation policies: AgentScheduledPolicy: A new synchronizationPoint is created by the IRPAgent on the IRPAgents internal decision, that decision is not related to any IRPManagers operations. In this mode,

41、 after successful delta synchronization, the IRPAgent does not create a new synchronizationPoint. ManagerRequestPolicy: The new synchronizationPoint is requested by the IRPManager. The exact time for this synchronizationPoint is determined by the IRPAgent. The IRPAgent that supports either AgentSche

42、duledPolicy or ManagerRequestPolicy to create a new synchronizationPoint can claim compliance to this specification. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager IOC Information Object Class IRP Integrat

43、ion Reference Point IS Information Service (see 3GPP TS 32.101 1) Itf-N Interface N NE Network Element ETSI ETSI TS 132 392 V13.0.0 (2016-02)83GPP TS 32.392 version 13.0.0 Release 134 System overview 4.1 System context The general definition of the System Context for the present IRP is found in 3GPP

44、 TS 32.150 5, clause 4.7. In addition, the set of related IRP(s) relevant to the present IRP is shown in figures 4.1-1 and 4.1-2. NEs Itf-N EM IRPAgent IRPManager NM Notification IRP Figure 4.1.1: System Context A Itf-N NE IRPAgent IRPManager NM Notification IRP Figure 4.1.2 : System Context B 5 Inf

45、ormation Object Classes 5.1 Information entities imported and local labels Label reference Local label 3GPP TS 32.622 6, information object class, Top Top 3GPP TS 32.622 6, information object class, IRPAgent IRPAgent 3GPP TS 32.622 6, information object class, GenericIRP GenericIRP 3GPP TS 32.312 7,

46、 information object class, ManagedGenericIRP ManagedGenericIRP 3GPP TS 32.302 3, information object class, NotificationIRP NotificationIRP Delta Synchronization IRP Delta Synchronization IRP ETSI ETSI TS 132 392 V13.0.0 (2016-02)93GPP TS 32.392 version 13.0.0 Release 135.2 Class Diagram 5.2.1 Attrib

47、utes and relationships This clause introduces the set of Information Object Classes (IOCs) that encapsulate information within the IRPAgent. The intent is to identify the information required for the delta synchronization IRP Agent implementation of its operations and notification emission. This cla

48、use provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these support object classes. ManagedGenericIRP (from TS 32.312) DeltaSynchronizationIRP Figure 5.2.1: Information Object Class (IOC) UML Diagram 5.2.2 Inherit

49、ance ManagedGenericIRP (from TS 32.312) DeltaSynchronizationIRP GenericIRP (from TS 32.622) Top (from TS 32.622) Figure 5.2.2: Information Object Class (IOC) Inheritance UML Diagram ETSI ETSI TS 132 392 V13.0.0 (2016-02)103GPP TS 32.392 version 13.0.0 Release 135.3 Information Object Class (IOC) definitions 5.3.1 DeltaSynchronizationIRP 5.3.1.1 Definition DeltaSynchronizationIRP is the representation of the delta synchronization capabilities specified by the present document. This IOC inherits from ManagedGenericIRP IOC s