ETSI GSM 12 01-1994 European Digital Cellular Telecommunications System (Phase 2) Common Aspects of GSM DCS 1800 Network Management《欧洲数字蜂窝通信系统(第2阶段) GSM DCS 1800网络管理的公共方面 GSM 12 01.pdf

《ETSI GSM 12 01-1994 European Digital Cellular Telecommunications System (Phase 2) Common Aspects of GSM DCS 1800 Network Management《欧洲数字蜂窝通信系统(第2阶段) GSM DCS 1800网络管理的公共方面 GSM 12 01.pdf》由会员分享，可在线阅读，更多相关《ETSI GSM 12 01-1994 European Digital Cellular Telecommunications System (Phase 2) Common Aspects of GSM DCS 1800 Network Management《欧洲数字蜂窝通信系统(第2阶段) GSM DCS 1800网络管理的公共方面 GSM 12 01.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、= 3404583 OLL7237 727 Released: IO May, 1994 GSM 12.01 Version: 4.2.0 Date: I5 April, 1994 Source: ETSI TC-SMG Reference: GSM 12.01 UDC: 621.396.21 Key words: European digital cellular telecommunications system, Global System for Mobile communications (GSM) European digital cellular telecommunicatio

2、ns system (Phase 2); Common Aspects of GSM/DCS 1800 Network management (GSM 12.01) ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: + 33 92 94 42

3、 O0 - Fax: + 33 93 65 47 16 European Telecommunications Standards Institute 1 994. All rights reserved. No part may be reproduced except as authorised by written permission. The copyright and the foregoing restriction on reproduction extend to all media in which the information may be embodied. ETSI

4、 / TC GSM Source: ETSI/GSM/SMG6 Date: May 1994 Title: SPECIFICATION GSM 12.0 1 COMMON ASPECTS OF GSMDCS 1800 NETWORK MANAGEMENT Version 4.2.0 Contents: 1 GENEFWL 2 GSM NETWORK MANAGEMENT 3 GSM NETWORK MANAGEMENT INTERFACES 4 GSM NETWORK MANAGEMENT PROTOCOLS AND SERVICES AT THE 43 INTERFACE 5. IMPLEM

5、ENTATION REQUIREMENTS FOR THE Qx NM INTERFACE 6. INTER-TMN OPERATION ANNEX 1 GSM PROTOCOL CONFORMANCE STATEMENTS ANNEX2 EXAMPLE FOR IMPLEMENTATION OF AN ADDRESSING SCHEME ANNEX 3 BIBLIOGRAPHY Original language: English Number of pages: 43 . - . I_ = 3404583 0337239 5TT W GSM 12.01 - version 4.2.0 .

6、page 2 . DETAILED LIST OF CONTENTS 1 . General . 4 1.1. Scope 4 1.2. . Abbreviations . 4 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, GSM Network Management 8 General TMN Stnictual Aspects 8 . Hierarchical Interworking Between Function Blocks Implementation of Interf

7、aces According to M.301 O . 10 Phase 2 Implementation Requirements for the Qx Interface Reference Points vs Interfaces . 8 9 Implementation Requirements 12 GSM Phase 2 Implementation Requirements for the 43 Interface . 12 14 GSM Phase 2 Implementation Requirements for Interworking Between 43 and Qx

8、Interfaces . 15 3 . GSM Network Management Interfaces 16 3.1. General 16 3.2. NM Interfaces Within a GSM 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.

9、6. 4.3.1.7. 4.3.2. 4.3.3. 4.3.4. 4.3.5. 4.4. 4.4.1. GSM 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 Elemen

10、t . 20 Description of how CMISE, ACSE, ROSE and OS1 Presentation Layer Interact 21 Protocol Capabilities . 23 Naming and Addressing Capability . 23 General Aspects 23 SCCPAddressing . 23 X.25 Addressing . 23 ISDN Addressing . 23 Transport Addressing 23 Addressing on the Application Layer . 23 Implem

11、entation Example 24 Connection-oriented Communication Capability 24 Connectionless Communication Capability . 24 File Transfer Capability 24 Remote Operation Handling . 24 Implementation Requirements 25 General 25 4.4.2. 4.4.2.1. 4.4.2.2. 4.4.2.3. 4.4.2.4. 4.4.3. 4.4.4. 4.4.5. 4.4.6. 4.5. 4.5.1. 4.5

12、.2. 4.5.3. 4.5.4. 4.5.5. 4.5.6. 5 . 5.1. 5.2. 5.3. 5.4. 6 . 6.1. 6.2. ANNEX 1 ANNEX 2 ANNEX 3 _ _ m 34043 0337240 231, m GSM 12.01 . version 4.2.0 . page 3 Layer 1 to 3 25 Requirements Specific to CCITT Signalling System No.7 . 25 Requirements Specific to the A Interface 25 Requirements Specific to

13、X.25 25 Requirements Specific to ISDN . 26 Transport Layer 26 Session Layer . 27 Presentation Layer 27 Application Layer . 28 The Use of QOS Parameters in OS1 Layer Services and Protocols . 30 General 30 30 31 31 31 General 32 Layer 1 32 Layer2 . 32 Layer3 . 32 Inter-TMN Operation 34 General 34 34 .

14、 36 . 37 . 39 Quality of Session Service . Quality of Transport Service . 31 Quality of Network Service Quaiity of Data Link Service . Quality of Physical Service Implementation Requirements for the Qx NM Interface 32 Interface to Other Management Systems . -= - - - m 3404583 0117241 158 m GSM 12.01

15、 - version 4.2.0 - page 4 - 1. General - 1.1. ScoDe This specification provides the survey of the GSM network management interfaces in accordance with the requirements in the GSM standards and with the architec- tural concept and methodology defined in GSM 12.00. Note: The requirements for GSM cover

16、s the requirements for a DCS 1800 network as well. 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 stack appropriate for a GSM TMN. This standard describes the relevant protocol p

17、rofiles for 43 and Qx interfaces. - 1.2. Abbreviations A AARE MQ ACPM ACSE AE AET AFI APDU API Q ASE ASN. 1 AT f=Q Agent A-ASSOCIATE-RESPONSE A-ASSOCIATE-REQUEST Association Control Protocol Machine Association Control Service Element Application Entity Application Entity Qualifier Application Entit

18、y Title Authority and Format Identifier Application Protocol Data Unit Application Programming Interface Application Process Qualifier Application Service Element (CCITT) Abstract Syntax Notation One Application Title BA Basic Access BSC GSM Base Station Controler BSS GSM Base Station System BSSOMAP

19、 BTS GSM Base Transceiver Station BSS Operation and Maintenance Application Part CCITT CMIP Common Management Information Protocol CMIP-DU CMIS Common Management Information Service CMISE CONS Connection-mode Network Service CUG Closed User Group International Telegraph and Telephone Consultative Co

20、m- mitee Common Management Information Protocol Data Unit Common Management Information Service Element DAF Destination Address Field DCE DCF DCS 1800 DEAF DIS DISP DSP DTE ETSI FTAM GT GSM ICF ID1 IS ISDN IS0 ISP LAPB LAPD M w MAPDU MCF MF MMI MO MSC MTP Mux NE NEF NM NMC NSAP O The following servi

21、ce is defined: 1) M-EVENT-REPORT (confirirmed/unconfirirmed). b) A management operation service - used to convey management information applicable to operations directed at a managed object; The following services are defined: 1) M-GET (confirmed), 2) M-SET (confumednon confirmed), 3) M-ACTION (conf

22、irmednon confirmed), 4) M-CREATE (confirmed), 5) M-DELETE (confirmed). 6) M-CANCEL-GET (confirmed) CMISE does not provide separate services for the establishment and release of application associations. The CMISE-service-user relies on the services of ACSE for the control of application associations

23、. During the association establishment phase, various ASEs may exchange initialisation information to establish an association using ACSE. The applica- tion context specifies the rules required for coordinating the information belonging to different ASEs, embedded in ACSE user information service pa

24、rameters. 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 termina- tion of an association. These may be invoked by either of the CMISE-ser- vice-users. How CMISE-servi

25、ce-users, CMISE, ACSE, ROSE and Presentation Layer interact is explained in section 4.2.4. 4.2.3. SDecific Management Amlication Service Element Specific Management Application Services Elements are CMISE users and provide a means to exchange Management Application Protocol Data Units (MAPDUs) betwe

26、en SMAPs. m 3404583 OLL7258 451 m GSM 12.01 - version 4.2.0 - page 21 4.2.4. DescriDtion of how CMISE. ACSE. ROSE and OS1 Presenta- tion Laver Interact In an OS1 environment, communication between application processes takes the form of communication between two application entities (AEs). CMiSE is

27、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 association (establishment, release, abort) between two AEs. ACSE services A-ASSOCIATE, A-RELEASE and A-AB

28、ORT 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 associations. The Presentation Service provides the transfer mechanism and ACSE primitives in turn, map onto t

29、he 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 service of ROSE to carry out an operation and map onto RO-RESULT to return the result. If the opera

30、tion 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 field of the P-DATA Presentation service. = 3404583 OLL7259 398 GSM 12.01 - version 4.2.0 - page 22

31、 -k c C J z: 8 I- a N c! I= X M L t GSM 12.01 - version 4.2.0 - page 23 - 4.3. Protocol Cauabilities 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 SW). See also Figure 8 / GSM 12.0

32、1. - 4.3.1. Naming: and Addressing Capabilitv 4.3.1 .l. General AsDects 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

33、 No.7 is or X.25 38). 4.3.1.2. SCCP Addressing, The user of the Signalling Connection Control Part SCCP 29 (network users) shall use the Global Title (GT) according to CCITT 4.713 1313 for transfer of management messages in the Signalling System No. 7 network. 4.3.1.3. X.25 Addressing The users of X

34、.25 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 sub-addressing in X.25, if needed, should be done as described in CCITT X.25, Appendix IV. 4.3.1.4. ISDN Addressing The user of ISDN shall use a numb

35、ering plan according to CCITT E. 164 181 for the transfer of management messages. 4.3.1.5. Transort Addressinp, The users of the Transport Layer (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

36、transport-address to refer unambiguously to a specific Transport Service Access Point (TSAP). 4.3.1.6. Addressing on the Aupiication Laver The addressing capabilities of the application layer are required to comply with the naming and addressing definitions of CCITT X.217X.227 54, SI. The applicatio

37、n-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 Protocol Data Units (APDUs) as specified in CCITT X.227 SI. GSM 12.01 - version 4.2.0 - page 24 The presentation add

38、ress (PSAP Identifier) to be issued by the requesting Association Control Protocol Machine (ACPM) in P-CONNECT request pri- mitive may be derived from the application-entity-title received in A-ASSO- CIATE request primitive, or it may be passed in the called presentation address parameter of the A-A

39、SSOCIATE request primitive, i.e. mapping of application-entity title on PSAP Identifier may be done by the ACPM or its service-user as a local issue. 4.3.1.7. Implementation Example An example for implementation of an addressing scheme is provided in ANNEX 2. This example is for guidance only. 4.3.2

40、. Connection-oriented Communication Catlabilitv This capability establishes a connection, either physical or logical, for the purpose of transporting management information between two application entities. This is required to support Common Management Information Ser- vices (CMIS) 16, File Transfer

41、, Access and Management (FTAM) 7, 8, 91, oI. - 4.3.3. Connectionless Communication catlabib This capability allows the transfer of management information between two application entities without the establishment of a connection. This capability is not currently proposed in the context of this docum

42、ent. However it might be used when OMAP, 33, is fully specified and is con- sidered for use as part of GSM network management. - 4.3.4. File Transfer Catlabilitv This capability provides the means for communications between network management applications requiring file transfers. This is required,

43、for example, for software downloading or transfer of statistics. This capability can be provided by the File Transfer Access and Management Application Service Element (FTAM ASE), defined in IS0 IS 8571 7, 8, 9, lo, and the Association Control Service Element (ACSE), defined in CCITT X.217 .and X.22

44、7 54,f55. The waf adequate lower layers is assumed, especially the use of a presentation service in accordance with CCITT X.216 52. - 4.3.5. Remote Oueration Handling, This capability allows a user to request that a particular operation be per- formed in another node which has to report the outcome.

45、 This capability is an application layer capability and can be provided by CMIS defined in IS0 IS 9595-2 16 and IS 9596-2 17. GSM 12.01 - version 4.2.0 - page 25 - 4.4. Imdementation Requirements 4.4.1. General The recommended protocol stack to support a 43 interface is defined in CCITT Q. 811 and Q

46、. 812 2, 3. It confis to the layer structure specified by the OS1 reference model. The service and protocol defuiitions selected for the first implementation phase of the 43 interface in the GSM TMN are specified in the following subsections. See also Figure 8/GSM 12.01 (Protocol array for GSM NM su

47、pport). 4.4.2. Laver 1 to 3 Layer 1 to 3 of any network used on the 43 interface shall as a minimum provide the mandatory Network Services defined in CCITT X.211 to X.213 MI, 451, 46l. Below three examples are detailed, Le. CCITT Signalling System No. 7, X.25, and ISDN. 4.4.2.1. Reauirements Suecifi

48、c to CCITT Simailing Svstem No.7 The CCITT Signailing System No.7 Message Transfer Part (MTP) shall generally comply to CCITT 4.701 - 4.709 20, 21, 22, 23, 24, 25, 1261, 271,281. The CcIn signalling system No.7 signalling Connection Control Part (SCCP) shall generally comply to CCITT 4.711 - 4.714 1

49、91, 30, 31, 32. For the 43 interface, SCCP Class 2 is required and Class 3 is optional. 4.4.2.2. Reauirements Suecific to the A Interface For the A interface layer 1, 2 and 3 are specified in GSM 08.04, 08.06 and 08.08 respectively. SCCP Class 2 is required on the A interface and Class 3 is optional. 4.4.2.3. Requirements Suecific to X.25 The service definition for the physical layer shall be in accordance with CCITT x.211 44. The physical interface shall be in accordance with: CCITT X