1、111 3404583 0120756 750 9 Released: July 1994 GSM 12.22 Version: 4.0.1 Date: I July, 1994 Work Item No: Key words: European digital cellular telecommunications system (phase 2); Interworking of management procedures and messages at the BSC ETSI European Telecommunications Standards Institute ETSI Se
2、cretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address: Route des Lucioles - Sophia Antipoiis - Valbonne - FRANCE Tel.: +33 92 94 42 O0 - Fax: +33 93 65 47 16 This is an unpublished work the copyright in which vests in the European Telecommunications Standards Institute. All
3、rights reserved. The information contained herein is the property 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 embodi
4、ed. 1 2 3 . - 3404583 0320757 697 W Page 3 GSM 12.22 version 4.0.1 CONTENTS GENERAL . 7 1.1 SCOPE . 7 1.4 ABBREVIATIONS . 8 1.2 STRUCTURE OF THIS SPECIFICATION . 7 1.3 INTERWORKING TASKS . 7 1.5 NORMATIVE REFERENCES . 8 COMMON INTERWORKING ASPECTS . 10 2.1 2.2 2.3 2.4 2.5 GENERAL CONSIDERATIONS 10 2
5、.1.1 Mapping behiveen GSM 12.20 Specified and GSM 12.21 Specified Object Classes 10 2.1.2 Addressing Objects at the BTS Site and Handling Different BTS Configurations . 10 CMIP OPERATIONS 11 2.2.1 Creation of BTS Related Object Instances 11 2.2.2 Setting Attributes of BTS Related Objects . 11 2.2.3
6、Getting Attributes of BTS Related Objects 12 2.2.4 Deletion of BTS Related Objects . 12 2.2.5 Actions on BTS Related Objects . 12 2.2.6 Event Reports sent by BTS Related Objects . 13 2.2.7 CMIS Parameters . 13 ERROR HANDLING . 14 2.4.1 initial States 15 2.4.2 Setting Administrative State 15 2.4.2.1
7、Setting Administrative State to Unlocked 16 2.4.2.2 Setting Administrative State to Locked . 16 2.4.2.3 Setting Administrative State to Shutting Down 16 Getting State Attributes . 16 Notifications about State Changes 16 STATE MANAGEMENT OF BTS RELATED OBJECTS 15 2.4.3 2.4.4 ALARM REPORTING . 18 3.1.
8、2 SPECIFIC INTERWORKING ASPECTS 20 3.1 BASEBANDTRANSCEIVER OBJECT CLASS 21 3.1.1 Information Mapping between GSM 12.20 basebandTransceiver and 3.1.1.1 Mapping of Attributes . 21 3.1.1.2 Mapping of GSM 12.21 Event Reports to GSM 12.20 Notifications . 22 3.1.1.3 Mapping of GSM 12.20 Actions to GSM 12.
9、21 procedures . 22 The Specific Interworking Procedures of the basebandrransceiver Object Class . 22 3.1.2.1 Initialisation Procedure for the basebandTransceiver Object Class . 22 GSM 12.21 Baseband Transceiver . 21 3.1.2.2 M-DELETE . 24 3.1.2.3 M-SET . 24 3.1.2.4 M-GET . 25 3.1.2.5 M-ACTION, forced
10、HO . 25 Information Mapping between GSM 12.20 bts Object and GSM 12.21 BTS Obiect . 26 3.2 BTS OBJECT CLASS . 26 3.2.1 3.2.1.1 Attribute Mapping . 26 3.2.1.2 Mapping of GSM 12.21 Event Reports to GSM 12.20 Notifications . 27 Previous page is blank Page 4 GSM 12.22 version 4.0.1 3404583 0120755 814 3
11、.2.1.3 Mapping of GSM 12.20 Actions to GSM 12.21 The Specific Intenivorking Procedures of the bts Object Class 28 3.2.2.1 Initialisation Procedure for the bts Object Class . 28 procedures . 28 3.2.2 3.2.2.2 M-DELETE . 30 3.2.2.3 M-SET . 30 3.2.2.4 M-GET . 31 3.2.2.5 M.ACTION. forcedHO 31 3.2.2.6 M.A
12、CTION. channelConfigurationModification . 32 3.3 BTS SITEMANAGER OBJECT CLASS 34 3.3.1 Information Mapping between GSM 12.20 btsSiteManager and GSM 12.21 Site Manager 34 3.3.1.1 Mapping of Attributes . 34 3.3.1.2 Mapping of GSM 12.21 Event Reports to GSM 12.20 Notifications . 34 The Specific Interwo
13、rking Procedures of the btsSiteManager Object Class 35 3.3.2.1 Initialisation Procedure for the btsSiteManager Object Class . 35 3.3.2.2 M-DELETE . 36 3.3.2.3 M-SET . 36 3.3.2.4 M-GET . 36 3.3.2 3.4 CHANNEL OBJECT CLASS . 37 3.4.1 Information Mapping between GSM 12.20 channel and GSM 12.21 Channel 3
14、7 3.4.2 Mapping of Attributes 37 3.4.2.1 Notifications . 37 The Specific Interworking Procedures of the channel Object Class . 38 Initialisation Procedure for the channel Object Class 38 Mapping of GSM 12.21 Event Reports to GSM 12.20 3.4.3 3.4.3.1 3.4.3.2 M-DELETE . 40 3.4.3.3 M-SET . 40 3.4.3.4 M-
15、GET . 41 3.5 FREQUENCYHOPPINGSYSTEM OBJECT CLASS . 42 3.5.1 Information Mapping between GSM 12.20 frequencyHoppingSystem Attributes and GSM 12.21 Channel . 42 3.5.1.1 Mapping of Attributes . 42 Class 42 3.5.2.1 Object Class 42 3.5.2.2 M-DELETE . 42 3.5.2.3 M-SET . 42 3.5.2.4 M-GET . 43 LAPDLINK OBJE
16、CT CLASS . 44 3.6.1 3.5.2 The Interworking Procedures of the frequencyHoppingSystem Object Initialisation Procedure for the frequencyHoppingSystem 3.6 Information Mapping between GSM 12.20 lapdlink and GSM 12.21 3.6.1.1 3.6.2.1 Objects 44 Interworking Procedures for the lapdlink Object Class . 45 Ma
17、pping of Attributes . 44 Initialisation Procedure for the IapdLink Object Class . 45 3.6.2 3.6.2.2 M-DELETE . 45 3.6.2.3 . M-SET . 45 3.6.2.4 M-GET . 46 3.7 RADIOCARRIER OBJECT CLASS . 47 3.7.1 Information Mapping between GSM 12.20 radiocarrier and GSM 12.21 Radio Carrier 47 3.7.1.1 Mapping of Attri
18、butes . 47 3.7.2 3.8.3 3404583 0320758 523 Page 5 GSM 12.22 version 4.0.1 3.7.1.2 Mapping of GSM 12.21 Event Reports to GSM 12.20 Notifications . 47 The Initialisation Procedure for the radiocarrier Object Class . 48 3.7.2.2 M-DELETE . 49 3.7.2.3 M-SET . 50 3.7.2.4 M-GET . 50 3.8 SOFTWARE OBJECTS 51
19、 3.8.1 Introduction . 51 3.8.2 REPLACEABLE SOFIWARE UNIT OBJECT CLASS . 53 3.8.2.1 Information Mapping between GSM 12.20 replaceabieSotwareUnit and GSM 12.21 objects . 53 3.8.2.2 Interworking procedures . 53 The Interworking Procedures of the radiocarrier Object Class 48 3.7.2.1 3.8.2.1.1 Mapping of
20、 Attributes 53 3.8.2.2.1 M-CREATE . 53 3.8.2.2.2 M-DELETE54 3.8.2.2.3 M-SET . 54 3.8.2.2.4 M-GET . 54 EXECUTABLE SOFMIARE UNIT OBJECT CLASS . 54 3.8.3.1 Information Mapping between GSM 12.20 executableSotwareUnit and GSM 12.21 objects 54 3.8.3.2 Interworking procedures . 54 3.8.3.2.1 M-CREATE . 54 3
21、.8.3.2.2 M-D E LETE 54 3.8.3.2.3 M-SET . 54 3.8.3.2.4 M-GET . 54 3.8.4 OPERATING SOFtWARE UNIT OBJECT CLASS 55 3.8.4.1 Information Mapping between GSM 12.20 3.8.4.2 Interworking procedures . 55 OperatingSoftwareUnit and GSM 12.21 objects 55 3.8.4.2.1 M-CREATE . 55 3.8.4.2.2 M-DELETE . 55 3.8.4.2.3 M
22、-SET . 55 3.8.4.2.4 M-GET . 57 4 RELATED A-BIS STRUCTURED PROCEDURES . 58 4.1 4.2 4.3 LAPD Link Connection 58 LAPD Link Disconnection . 58 Software Downloading and Activation . 59 4.3.1 Software Downloading 59 4.3.2 Software Activation . 59 ANNEX 1 . SOME INTERWORKING ISSUES 61 STRUCTURED PROCEDURES
23、 ON Q3 INTERFACE 61 LIST OF ATTRIBUTES 62 Number of pages: 64 . W 3404583 0320757 4bT Page 7 GSM 12.22 version 4.0.1 1 GENERAL 1.1 SCOPE To ensure management of different manufacturers BTSs from the OMC through the BSC in a standardised way, this BSC interworking specification is needed to relate th
24、e OMC-BSC interface (23) as specified in GSM 12.20 and the BSC-BTS interface (A-bis Qx) as specified in GSM 12.21. In GSM 12.01 it is required that the BSC performs the Mediation Function between the OMC and the BTS. This specification defines the requirements for this Mediation Function. 1.2 STRUCT
25、URE OF THIS SPECIFICATION This specification is structured as follows 1. General 2. Common interworking aspects 3. Specific interworking aspects 4. Related A-bis structured procedures Annex 1. Some interworking issues Section 1 contains the general overview of this specification. Section 2 describes
26、 the aspects common to all the managed object classes that cause interworking between the Q3 and Qx interfaces. Objects and their naming and addressing on the OMC-BSC and A- bis Ox interfaces are briefly described. General requirements for Q3/Qx interworking for CMIP operations including error handl
27、ing are given. Q3/Qx interworking of general functions, .e., state management and alarm reporting, are also specified. Section 3 specifies the aspects, specific to each object class, that cause interworking. This section contains the requirements on mapping between the GSM 12.20 specified and GSM 12
28、.21 specified objects, their attributes, and object specific interworking procedures for different CMIP operations. Section 4 defines the A-bis structured procedures used in section 3. Annex 1 describes the structured procedures at a high level which are used in managing the BTS from the OMC. 1.3 IN
29、TER WORKING TASKS Figure l/GSM 12.22 illustrates differences between Q3 and A-bis Qx interfaces and the object models in the BSC and the BTS. Previous page is blank 3404583 0120760 181 Page 8 GSM 12.22 version 4.0.1 OMC gj-rnodel BSC #podel BTS I I l I 1 M: Manager A: Agent Figure l/GSM 12.22. Mappi
30、ng of information models. In the A-bis interface, layers 1 and 2 are common with telecommunication signalling specified in GSM 08.5X. Network management messages and procedures on the A-bis interface are based on the layer 3 transport mechanism specified in GSM 12.21 and are consistent with the tele
31、communications signalling on layers 3 as specified in GSM 08.58. The protocol profiles for the Q3 interface are specified in GSM 12.01. For network management purposes, the BSC is responsible for the following interworking tasks: - bi-directional protocol conversion so as to provide mapping between
32、Q3 and A-bis Qx interfaces which consists of mapping of GSM 12.20 objects onto GSM 12.21 objects, mapping of CMIS services onto GSM 12.21 procedures and association of GSM 12.20 attributes to GSM 12.21 attributes; management of interworking functions activated by the OMC and terminated within the BT
33、S and vice versa; handling of interworking errors, .e., reporting errors in case of failure in interworking procedures. - - Note The functions activated by the OMC and terminated within the BSC or functions activated by the BTS and terminated within the BSC are not specified here. This applies also
34、to the vice versa situations. 1.4 ABBREVIATIONS Definitions and abbreviations used in this ETS are listed in GSM 01.04. 1.5 NORMATIVE REFERENCES CCIlT Recommendation X.71 O: Common Management Information Service Definition for CCIlT Applications CCIT Recommendation X.711: Common Management Informati
35、on Protocol Definition for CCITT Applications CCIlT Recommendation X.721: Definition of Management Information - _- -_ . w 3404583 0320763 018 m Page 9 GSM 12.22 version 4.0.1 CCITT Recommendation X.731: State Management Function for CCIlT Applications CCITT Recommendation X.733: Alarm Management Fu
36、nction for CCiTT Applications CCITT Recommendation X.734: Event Reporting Management Function for CCIlT Applications CCITT Recommendation X.735: Log Control Function for CCIlT Applications GSM 04.08, Mobile Radio Interface Layer 3 Specification GSM 08.56, BSC-BTS Layer 2 Specification GSM 08.58, BSC
37、-BTS Layer 3 Specification GSM 12.00, Objectives and Structure of Network Management GSM 12.01, Common Aspects of GSM Network Management GSM 12.20, BSS Management information GSM 12.21, Network Management Procedures and Messages on the A-bis Interface I , Page 10 GSM 12.22 version 4.0.1 GSM 12.20 BT
38、S related object classes btsSiteManager bts basebandTransceiver radiocarrier = 3404583 0320762 T54 GSM 12.21 object classes Site Manager BTS Baseband Transceiver Radio Carrier 1 2 COMMON INTERWORKING ASPECTS 2.1 GENERAL CONSIDERATIONS 2.1.1 Mapping between GSM 12.20 Specified and GSM 12.21 Specified
39、 Object Classes Q3 and A-bis Qx interfaces use different object models. The specification of the interworking procedures between these interfaces requires mapping the object classes and instances between the Q3 interface and the A-bis Qx interface and vice versa. The following table contains BTS rel
40、ated object classes specified in GSM 12.20 and the corresponding object classes specified in GSM 12.21. Table l/GSM 12.22. BTS related object classes in GSM 12.20 and GSM 12.21. I frequencyHoppingSystem 1 lkhannel I I channel I Channel I I IapdLink I 2) I Note 1: GSM 12.21 doesnt specify the frequen
41、cy hopping system as an object class. The corresponding information is included in the attributes of the channel class. Note 2: The information about the signalling links of the BTS side (PCM port numbers and timeslots in the BIS) is included in the attributes of Site Manager, BTS and Baseband Trans
42、ceiver classes. In GSM 12.20 the corresponding object classes have references to LAPD links which are either O&M links (in Site Manager, bts or basebandTransceiver) or telecom signalling links (only to basebandTransceiver). 2.1.2 Addressing Objects at the BTS Site and Handling Different BTS Configur
43、ations The BCF (Base Control Function) mentioned in GSM 08.52 and GSM 08.56 is the agent at the BTS end of the A-bis Qx interface. There could be one or more of these agents at the site and the GSM 12.21 objects and attributes that each agent can manage depend on the implementation. Each agent is co
44、nnected to the manager at the BSC via a LAPD link which is identified by a physical link address (.e. PCM circuit and (sub)timeslot), TE1 (Terminal Endpoint Identifier) and SAPI (Service Access Point Identifier). In order to address the various BTS objects over the A-bis Qx interface it is required
45、that the BSC contain associations between BTS related objects defined in GSM 12.20 and the agents (.e. O&M links) that manage the corresponding GSM 12.21 objects at the BTS site. The procedures that relate to the A-bis interface management are optional in GSM 12.21 and therefore not all the BTSs hav
46、e to support them. However, it is required that these are implemented in the BSC so that it can support all the BTS implementations that are made according to GSM 12.21. In this case the BSC must have the information per ,each BTS whether the A-bis interface management option is supported or not. m
47、NOWH OI,ZOL wo m Page 11 GSM 12.22 version 4.0.1 2.2 CMIP OPERATIONS 2.2.1 Creation of BTS Related Object Instances The M-CREATE service is used by the OMC to request a peer CMISE-service-user (.e., the agent) at the BSC to create an object instance, complete with its identification. The Correspondi
48、ng physical resource may or may not exist at the BTS site. Normally the initialisation of the physical resource via A-bis Qx interface will be started immediately ater the creation if the corresponding physical resource at the BTS site has been installed. Initialisation might include several steps,
49、such as, setting up O&M (and telecommunications) signalling links, downloading and activation of the software, setting various O&M attributes by GSM 12.21 messages and setting the system information to be broadcasted from the BTS by GSM 08.58 procedures. Some of these steps are not relevant for some object classes. Object creation to the BSC should be possible before any resources are installed at the BTS site. If the resource for the object to be created has not been installed at the BTS site, the agent at the BTS site wont respond or it will respond with a NAC
