1、= 3404583 0078682 638 Released: 15 October 1993 GSM 12.01 Version: 4. I .O Date: 27 September, 1993 Work Item No: Key words: European digital cellular telecommunication system (phase 2); Common Aspects of PLMN network Management ETSI European Telecommunications Standards Institute ETSI Secretariat:
2、Route des Lucioles, F-O6921 Sophia Antipolis Cedex . France TP. + 33 92 94 42 O0 TF. + 33 93 65 47 16 Tx. 47 O0 40 F This is an unpublished work the copyright in which vests in the European Telecommunications Standards institute. All rights reserved. The information contained herein is the property
3、of ETSI and no part may be reproduced or used except as authorised by contract or other written permission. The copyright and the foregoing restriction on reproduction and use extend to all media in which the information may be embodied. 3404583 0078683 574 ETSI / TC GSM Source : ETSTGSWSMG6 Date :
4、October 1993 Title: SPECIFICATION GSM 12.0 1 COMMON ASPECTS OF PLMN NETWORK MANAGEMENT Version 4.1 .O Contents: 1 GENERAL 2 PLMNNETWORK MANAGEMENT 3 PLMN NETWORK MANAGEMENT INTERFACES 4 PLMN NETWORK MANAGEMENT PROTOCOLS AND SERVICES AT THE 43 INTERFACE 5. IMPLEMENTATION REQUIREMENTS FOR THE QX NM IN
5、TERFACE 6. INTER-TMN OPERATION ANNEX 1 GSM PROTOCOL CONFORMANCE STATEMENTS ANNEX 2 EXAMPLE FOR IMPLEMENTATION OF AN ADDRES- SING SCHEME ANNEX 3 BIBLIOGRAPHY Original language: English Number of pages: 42 rn 3404583 0098684 400 m GSM 12.01 . version 4.1.0 . page 2 DETAILED LIST OF CONTENTS 1 . Genera
6、l . 4 1.1. Scope 4 Abbreviations . 4 1.2. 1.3. GSM References 6 2 . 2.1. 2.1.1. 2.1.2. 2.1.3. 2.2. 2.2.1. 2.2.2. 2.2.3. PLMN Network Management . 8 General Ti“ Structual Aspects 8 Reference Points vs Interfaces . 8 9 Implementation Requirements 12 12 14 GSM Phase 2 Implementation Requirements for In
7、terworking Between Q3 and Qx Interfaces . 15 Hierarchical Interworking Between Function Blocks Implementation of Interfaces According to M.30 1 O . 10 GSM Phase 2 Implementation Requirements for the Q3 Interface Phase 2 Implementation Requirements for the Qx Interface . 3 . PLMN Network Management I
8、nterfaces . 16 3.1. General 16 3.2. NM Interfaces Within a PLMN Network . 16 3.2.1. 43 Interface 16 3.2.2 Qx Interface 17 3.3. The Man Machine Interface 17 4 . 4.1. 4.2. 4.2.1. 4.2.2. 4.2.3. 4.2.4. 4.3. 4.3.1. 4.3.1.1. 4.3.1.2. 4.3.1.3. 4.3.1.4. 4.3.1.5. 4.3.1.6. 4.3.2. 4.3.3. 4.3.4. 4.3.5. 4.4. 4.4
9、.1. 4.4.2. 4.4.2.1. 4.4.2.2. 4.4.2.3. PLI“ Network Management Protocols and Services at the 43 Interface 18 General 18 Communication Model For Management Information Transfer . 18 General 18 Common Management Application Services Element 18 Specific Management Application Service Element . 21 Descri
10、ption of how CMTSE, ACSE, ROSE and OS1 Presentation Layer Interact 21 Protocol Capabilities . 23 Naming and Addressing Capability . 23 General Aspects 23 SCCP Addressing . 23 X.25 Addressing . 23 Addressing on the Application Layer 23 Implementation Example 24 Connection-oriented Communication Capab
11、ility 24 Connectionless Communication Capability . 24 Transport Addressing 23 File Transfer Capability 24 Remote Operation Handling . 25 Implementation Requirements 25 General 25 Layer 1 to 3 25 Requirements Specific to CCITT Signalling System No.7 . 25 Requirements S-pecific to the A Interface 25 R
12、equirements Specific to X.25 26 4.4.3. 4.4.4. 4.4.5. 4.4.6. 4.5. 4.5.1. 4.5.2. 4.5.3. 4.5.4. 4.5.5. 4.5.6. 3Y04583 0098685 347 GSM 12.01 . version 4.1.0 . page 3 Transport Layer 27 Session Layer . 27 Presentation Layer 28 Application Layer . 28 The Use of QOS Parameters in OS1 Layer Services and Pro
13、tocols . 31 General 31 Quality of Session Service . 31 Quality of Transport Service . 32 Quality of Network Service 32 32 Quality of Physical Service 32 Quality of Data Link Service . 5 . Implementation Requirements for the Qx NM Interface 33 5.3. Layer2 . 33 5.1. General 33 5.2. Layer 1 33 5.4. Lay
14、er 3 . 33 6 . Inter-TMN Operation 35 6.1. General 35 6.2. Interface to Other Management Systems . 35 ANNEX 1 . 36 ANNEX 2 . 37 ANNEX 3 . 39 3404583 0098b8b 283 GSM 12.01 - version 4.1.0 - page 4 General 1.1. ScoDe - This specification provides the survey of the PLMN network management inter- faces i
15、n accordance with the requirements in the GSM standards and with the ar- chitectural concept and methodology defined in GSM 12.00. The various possibilities for transfer of NM messages between the NM entities and NEs are outlined in this standard, and the requirements are set up for an OS1 protocol
16、stack appropriate for a PLMN TMN. As the current implementation of phase 2 is limited to the management of the BSS, this standard describes the relevant protocol profiles for 43 and Qx interfaces. -. . - 1.2. A AARE ACPM ACSE AE AEQ AET AFI APDU API ASE ASN. 1 AT BSC BSS BSSOMAP BTS CCITT CMIP CMIS
17、CMISE MQ APQ CMIP-DU Abbreviations Agent A-ASSOCIATE-RESPONSE A-ASSOCIATE-REQUEST Association Control Protocol Machine Association Control Service Element Application Entity Application Entity Qualifier Application Entity Title Authority and Format Identifier Application Protocol Data Unit Applicati
18、on Programming Interface Application Process Qualifier Application Service Element (CCITT) Abstract Syntax Notation One Application Title GSM Base Station Controler GSM Base Station System BSS Operation and Maintenance Application Part GSM Base Transceiver Station International Telegraph and Telepho
19、ne Consultative Com- mi tee Common Management Information Protocol Common Management Information Protocol Data Unit Common Management Information Service Common Management information Service Element DAF DCE DCF DEAF DIS DISP DSP DTE ETSI FTAM GT GSM ICF ID1 IS IS0 ISP LAPB LAPD M MAF MAPDU MCF MF M
20、MI MO MSC MTP NE NEF NM NMC NSAP O - Q3 I OSF I - Q3 f- Ox - Qx Example Functional Groupings I OSF 93 MF i , I , - Qx I ; NEF W 340q583 0098693 Li13 GSM 12.01 - version 4.1 .O - page 11 Figure 3 shows a decomposition of a general OSF into more specific OSFs which represent different functional areas
21、. Each OSF contains the manage- ment functionality necessary for the specific functional area, i.e. OSF1 is responsible for managing performance measurements, OSF2 manages the logical configuration, etc. The managed network element has been designed, in this example, to include certain function bloc
22、ks of the conceptual TMN. “OMC“ device con- tains OSFs and a MF. The external interface of the NE device is, therefore, the sum of the inter- faces (Qx + Q3 + 43) relevant to the various components, and these may or may not be implemented together . OSF4, which is shown contained within the NE devic
23、e, may or may not interface to a higher level manage- ment device or function. QAF3 has been implemented in the NE device to convert an existing non-standard interface to a standardized interface. “OMC“ DEVICE NE DEVICE ox A 63 - I i-, ( QAF3 I ,f u Om i-, OSF4 i b Om I NEF 1 I Fig. 3. Example Funct
24、ional Relationship I m 3404583 0098b4 35T m GSM 12.01 - version 4.1.0 - page 12 - 2.2. Imdementation Requirements The implementation requirements are derived out of GSM 12.00, Section 3. In this context this document shall specify a suitable subset of a Q3 and Qx profile defined as The implemented s
25、ubset of the layer services profiles - The implemented subset of the layer protocols profiles The application service and protocols profiles The conformance requirements of the specified services The conformance requirements of the specified profile - - - 2.2.1. GSM Phase 2 Implementation Requiremen
26、ts for the 03 inter- - face - The degree of implementation freedom allowed for by the present CCITT M.3010 TMN model i, as has been described in the previous paragraphs, is simply too large to come to any significant level of multi-vendor interop- erability . For example, in figure 2 the OS in colum
27、n (a) could interface to the NE in column (b) as they both claim to support the same Q3 interface, provided that these are supported by the same object model using a common message set. However, if the reference point contained within the OS in column (a) is not discernible then it could not interfa
28、ce to the lower layer OS in column (b) without redevelopment for that purpose. It is therefore essential to uniquely define the grouping of the different func- tional areas supporting the different layers within the logically layered archi- tecture, in order to provide for interoperability in multi-
29、vendor environments. The following introduces the requirements for a standardized GSM Phase 2 Q3 interface, i.e. OMC - BSS interface. The phase 2 target reference model for the BSS is defined as single OSF and BSS NEF , interfacing with each other via a single accessible q3 reference point / 43 inte
30、rface, as depicted in figure 4 below: 3404583 0078695 296 GSM 12.01 - version 4.1.0 - page 13 I Fig. 4. BSS Reference Model for Phase 2 The BSS can be implemented either as: 1) a single BSS NEF, which directly interacts with the OSF through the 43 interface or: 2) a) the BSC NEF and the BSC MF, whic
31、h directly interacts with the OSF through the Q3 interface and b) the BTS NEF, which interacts with the BSC MF through the Qx (Abis) interface, which is depicted in figure 5 below: 3404583 0098bb 122 = GSM 12.01 - version 4.1.0 - page 14 i 03 GSMIZO O3 GSM 1226 i l Fig. 5. Allowed BSS Context Models
32、 for Phase 2 The BSS object model and message set are defined in GSM 12.20, while the O The following service is defined: i ) M-EVENT-REPORT (confirmedunconfirmed). b) A management operation service - used to convey management information applicable to operations directed at a managed object; The fo
33、llowing services are defined: i) M-GET (confirmed), 2) M-SET (confirmedhon confirmed), 3) M-ACTION (confirmednon confirmed), 4) M-CREATE (confirmed), 5) M-DELETE (confirmed). 6) M-CANCEL-GET (confirmed) CMSE does not provide separate services for the establishment and release of application associat
34、ions. The CMISE-service-user relies on the services of ACSE for the control of application associations. During the association estabiishment phase, various ASEs may exchange initialisation information to establish an association using ACSE. The applica- tion context specifies the rules required for
35、 Co-ordinating the information belonging to different ASEs, embedded in ACSE user information service parameters. The application context, presentation and session requirements are conveyed using parameters of the A-ASSOCIATE service. The A-RELEASE and A-ABORT services of ACSE are used for the termi
36、na- tion of an association. These may be invoked by either of the CMISE-ser- vice-users. How CMISE-service-users, CMISE, ACSE, ROSE and Presentation Layer interact is explained in section 4.2.4. m 34083 oowm 172 m GSM 12.01 - version 4.1.0 - page 21 4.2.3. Soecific Management Application Service Ele
37、ment Specific Management Application Services Elements are CMISE users and provide a means to exchange Management Application Protocol Data Units (MAPDUs) between SMAPs. 4.2.4. Description of how CMISE, ACSE. ROSE and OS1 Presenta- tion Laver Interact In an OS1 environment, communication between app
38、lication processes takes the form of communication between two application entities (AEs). CMISE is used to transfer systems management information between peer AEs. CMISE needs the services of ROSE and the Presentation Layer to do this. See Figure 7 / GSM 12.01. ACSE controls the application associ
39、ation (establishment, release, abort) between two AEs. ACSE services A-ASSOCIATE, A-RELEASE and A-ABORT are used to set up and tear down an association. The ACSE ser- vices are invoked by the CMISE-service-users, i.e. CMiSE does not provide separate services for the control of application associatio
40、ns. The Presentation Service provides the transfer mechanism and ACSE primitives in turn, map onto the P-CONNECT, P-RELEASE and P-U-ABORT Presentation services. ROSE controls the communication between peer AEs over an association set up and controlled by ACSE. CMISE primitives map onto the RO INVOKE
41、 service of ROSE to carry out an operation and map onto RO RSULT to return the result. If the operation was unsuccessful or some other problem was detected, the reply would be carried by either RO-ERROR, RO-REJEC- T-U or RO-REJECT-P services of ROSE. ROSE primitives, in turn, map onto the user data
42、field of the P-DATA Presentation service. 3404583 0098704 O29 GSM 12-01 - version 4.1.0 - page 22 I It Service GSM Management Application Service Element CMISE (IS0 9596 CCITT X.710) (and possibly user SM ASES) ROSE 1 CCITT X.229 IS0 9072 ACSE FTAM IS0 8571 I I I Presentation Protocol CCITT X.226 IS
43、0 8823 I Class 2 (includ. O) Class 2 (optional Class 3) SCCP CCITT Q.711 - 4.714 MTP-3 CCITT Q.701 - 4.707 MTP-2 CCITT 4.701 - 4.707 I I MTP-I CCITT 4.701 - 4.707 I Class O or 2 CCTTT X.25 IS0 8208 1 CCITT LAPB X.25 IS0 7776 I j X.21K.21bis CCITTG703/ Figure 8 / GSM 12-01: PROTOCOL ARRAY FOR GSM NM
44、SUPPORT m 3404583 0098705 Tb5 GSM 12.01 - version 4.1.0 - page 23 - 4.3. Pro toco I Capabilities The following capabilities are required from the protocol stack implemented in each GSM Network Node, to support the GSM System Management Ap- plication Process (GSM SMAP). See also Figure 8 / GSM 12.0 I
45、. 4.3.1. Naming and Addressing Capability 4.3.1.1. General Aspects The addressing capability allows a user to address applications unambiguous- ly in all nodes in the GSM TMN. The addressing schemes for layer 4 to 7 are valid, independent from the net- work service to be used (Signalling System No.7
46、 19 or X.25 4381). 4.3.1.2. SCCP AddressinK The user of the Signalling Connection Control Part SCCP (291 (network users) shall use the Global Title (GT) according to CCITT 4.713 31 for transfer of management messages in the Signalling System No. 7 network. 4.3.1.3. X.25 Addressinq The users of X.25
47、network layer (network users) should use a numbering plan according to CCITT X.121 39 for transfer of management messages in the X.25 network. The CCITT X.25, Appendix IV. sub-addressing in X.25, if needed, should be done as described in 4.3.1.4. Transport Addressinq The users of the Transport Layer
48、 (TS users) shall use a system of addressing which is mapped onto the addressing scheme of the supporting Network Ser- vice. A TS user shall use a specific transport-address to refer unambiguous- ly to a specific Transport Service Access Point (TSAP). 4.3.1.5. Addressing on the Audication Laver The
49、addressing capabilities of the application layer are required to comply with the naming and addressing definitions of CCITT X.217m.227 54, WI. The application-entity-title, composed of application-process- title and ap- plication-entity qualifier, may be included in the A-ASSOCIATE-REQUEST (AARQ) and A-ASSOCIATE-RESPONSE (AARE) Application Pro toco1 3404583 0098706 9Tl = GSM 12.01 - version 4.1.0 - page 24 Data Units (APDUs) as specified in CCITT X.227 SI. The presentation address (PSAP Identifier) to be issued by the requesting Association Control Protoco
