ETSI GSM 12 21-1993 European Digital Cellular Telecommunication System (Phase 2) Network Management Procedures and Messages on the A-Bis Interface《欧洲数字蜂窝通信系统(第2阶段) 在A-Bis接口上的网络管理程序.pdf

《ETSI GSM 12 21-1993 European Digital Cellular Telecommunication System (Phase 2) Network Management Procedures and Messages on the A-Bis Interface《欧洲数字蜂窝通信系统(第2阶段) 在A-Bis接口上的网络管理程序.pdf》由会员分享，可在线阅读，更多相关《ETSI GSM 12 21-1993 European Digital Cellular Telecommunication System (Phase 2) Network Management Procedures and Messages on the A-Bis Interface《欧洲数字蜂窝通信系统(第2阶段) 在A-Bis接口上的网络管理程序.pdf（57页珍藏版）》请在麦多课文档分享上搜索。

1、= 3404583 0099137 T77 = Released: 15 October 4993 GSM 12.21 Version: 4.2.0 Date: 27 September, 1993 Work Item No: Key words: European digital cellular telecommunication system (phase 2); Network Management Procedures and Messages on the A-bis Interface ETSI European Telecommunications Standards Inst

2、itute ETSI Secretariat: 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

3、 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 embodied. m 3404583 0099338 903 m ETSI / TC SMG

4、Source : ETSI/SMG6 Date : 1 October 1993 Title : SPECIFICATION GSM 12.21 NETWORK MANAGEMENT PROCEDURES AND MESSAGES ON THE A-BIS INTERFACE version 4.2.0 Contents : 4 7 GENERAL 2 FUNCTIONAL SPLIT BETWEEN BSC AND BTS 3 INFORMATION MODEL 3.1 Managed Objects 3.2 Addressing of Objects 3.3 State Managemen

5、t of Objects ELEMENTARY PROCEDURES 4.1 Definition of the Procedures 4.2 SW Download Management Procedures 4.3 A-bis Interface Management Procedures 4.4 Transmission Management Procedures 4.5 Air Interface Management Procedures 4.6 Test Management Procedures 4.7 State Management and Event Report 4.8

6、Equipment Management Procedures 4.9 Other Messages Procedures -4 4 6 6 9 9 10 12 13 14 15 17 19 20 STRUCTURED PROCEDURES 21 5.1 Reconfiguration when BCCH is lost 21 5.2 Reconfiguration when SDCCH is lost 22 MESSAGE 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 DETAILS 23 Message Categories 23 Structure o

7、f Formatted Oet At tribut es Zquipment Management Proc. Zstablish TE1 Set Site Outputs State Management and Event Report Procedures ;W Download Management Proc. rest Management Proc. Set Attribut es 3quipment Management Proc. ;et BTS Attributes State Management and Event Report Procedures SW Downloa

8、d Management Proc. rest Management Proc. Set TRX Attributes Connect Terrestrial Signalling Disconnect Terrestrial Sign. Yet Attribut es Equipment Management Proc. State Management and Event Report Procedures SW Download Management Proc. Test Management Proc. Set Channel Attributes Connect Terrestria

9、l Traffic Disconnect Terrestrial Traffic Get Attributes Equipment Management Proc. State Management and Event Report Procedures Test Management Proc. If more than one layer 2 link is defined to handle this information model, the actual implementation may affect on which layer 2 link attributes conce

10、rning frequency hopping and front-end switch are sent. Equipment used to implement frequency hopping can be common to several transceivers or located inside a transceiver. Front-end switch is handled by Site Manager, therefore all Abis Channel attributes must be sent to it. Those attributes that nee

11、d a link identifier in BSC data structures are marked with an asterisk (*). m 3404583 0099343 270 m GSM 12.21 - 4.2.0 - page 6 3.2. Addressing of Objects It is a requirement that the BSC is capable of operating with BTSs from different manufacturers and so it is necessary that the differences betwee

12、n BTSs, as seen by the BSC, are minimised as much as possible. This is achieved by addressing NM messages by the Managed Object Class and Managed Object Instance. There must be in the BSC an object model with a complete layer 2 link description for each object instance in the BTS (Transceiver 1, Tra

13、nsceiver 2, Transceiver 3,). When a message has to be sent to an object instance this mapping is used to find the correct link. The first connection is established from the BTS site by using a (semi-) permanently programmed default TEI. Subsequent to the establishment of the default connection to th

14、e site, further initial connections to other objects are established using TEIs provided by procedures in section 4.3.1. Possible additional TEIs to an object already having an initial TE1 are assigned with a GSM 12.21 message found in section 4.3.1. through an already assigned signalling link. Obje

15、ct instances also have a layer 3 address. The instance number is used to address the object instance. In the case when the layer 2 address does not uniquely identify the object instance, the layer 3 address is used by management agent to determine which object instance is being addressed. In this ca

16、se the agent must have this instance number (semi-) permanently programmed. This combination of layer 2 and layer 3 addressing accommodates BTS sites with either single or multiple physical links. Specific equipment configuration information is manufacturer dependent. However, for interoperability,

17、link configuration, default TE1 assignment and instance numbering must be known by both manager and agent. This as well as supported functions are considered as Shared Management Knowledge. 3.3. State Management of Objects State management in GSM 12.21 is generally in line with CCITT X.731. How stat

18、e values are applied is explained below. According to CCITT X.731: “The management state of a managed object represents the instantaneous condition of availability and operability of the associated resource from the point of view of management. I In GSM 12.21 there are two different factors (CCITT X

19、.731 defines usage state in addition to these two) that are considered to affect the management state of a managed object. They are: - Administration: permission to use or prohibition against using the resource, imposed through the management services - Operability: whether or not the resource is ph

20、ysically installed and working GSM 12.21 defines the following three state management attributes to represent the management state of a managed object: - Administrative state - Operational state - Availability status (this elaborates the operational state) 3404583 0077344 307 GSM 12.21 - 4.2.0 - pag

21、e 7 3.3.1. Administrative state The usage of resources is controlled by BSC (actually call control is located in MSC) and therefore administrative states of the GSM 12.21 managed objects can only be controlled by the BSC. Setting the administrative state of a Channel to locked means that it has to b

22、e discontinue all transmission and reception of information on Air interface and all telecom information on A-bis interface. Setting the administrative state of a Transceiver to locked means it has to discontinue all RF emission on Air interface for the frequencies it is responsible and the Channels

23、 which are affected should indicate they are Disabled or Degraded. Setting the administrative state of a BTS to locked means it has to discontinue all RF emission on all Channels of all Transceivers, i.e., Channels and Transceivers are in Disabled, Dependency state. The administrative state at the B

24、TS site is also used to provide information e.g., for a local MMI user at a BTS site. The locked state of a GSM 12.21 managed object means that BCC has disconnected all the calls that go through the resource that is represented by the managed object. No new traffic is connected through this resource

25、 any more. The shutting down state means that no new traffic is connected through this resource any more. The on-going calls remain. The unlocked state means that new traffic is allowed through the resource represented by the managed object. 3.3.2. Operational state and availability status CCITT X.7

26、31 gives the following definitions or the values of the operational state attribute: - Disabled: The resource is totally inoperable and unable to provide service to the user (s) . - Enabled: The resource is partially or fully operable and available for use. In GSM 12.21 the value Disabled represents

27、 the following conditions that the resources could have: - Hardware or software is not installed - Power is turned off - Failure - Radio parameters has not been set by GSM 12.21 elementary procedures (the resource is off line) The availability status elaborates the operational state attribute. In GS

28、M 12.21 the following values are used (availability status is a set values) : In test: The resource is undergoing a test procedure. Failed: The resource has an internal fault that prevents it from operating. The operational state is Disabled. Power off: The resource requires power to be applied and

29、is not powered on. The operational state is Disabled. Off line: Attributes of an object have to be set by elementary procedures of GSM 12.21. Operational state is Disabled. Dependency: The resource cannot operate because some other resource on which it depends is unavailable. The operational state i

30、s Disabled. - 3404583 0099345 O43 GSM 12.21 - 4.2.0 - page 8 Degradad: The service available from the resource is degraded in some respect, such as in speed or operating capacity. The operational state is Enabled. Not installed: Not installed means that the hardware or the software associated with t

31、he managed object has not been installed at the site. Operational state is Disabled. Figure 2. Operational state and availability status behaviour of GSM 12.21 objects (Site Manager, BTS, Transceiver) during initialization. Initial value for Administrative state is locked. 1- 1 CW Activate Request I

32、 v II Disabled, II II Not Installed IChanged State I Event Report I V fl i1 11 Disabled, II Off Line II II BTC related object (Site Manager, BTS, Transceiver) requests downloading and activation of the running software version. Software downloading and activation takes place when object is in this s

33、tate. Operational state=disabled Availability status= Not installed The last file belonging to the running software version has been downloaded and activated. Operational state=Disabled Availability status=Off line Object doesnt have correct attribute values yet. They will be received when the unloc

34、k procedure is executed. Operational state=Disabled Availability status=Off line All needed attributes of the managed object I are set. Changed State I Availability status=() V Event Report Operational state=Enabled W 3LtOLt583 00Lqb T8T GSM 12.21 - 4.2.0 - page 9 4. ELEMENTARY PROCEDURES The operat

35、ional procedures applicable to the BTS consist of the bringing into (or taking out of) service of BTS equipment and software, and the initiation and collection of any test results made at the BTS, the reporting and clearing of any BTS faults, and the reporting of any BTS external alarms. The bringin

36、g into service of equipment at the BTS will include manual operations, including switch on, and local testing where relevant at the BTS, followed by an indication of the availability of the equipment to the BTS via some man-machine interface (MMI terminal, telephone). It is then a BSC function to en

37、sure that relevant data on the existence of the equipment is resident at the BTS, and to activate (bring into service) the new equipment. Manual procedures may also be employed for software loading, at least initially. As far as software is concerned, all operational software used at the BTS is held

38、 also at the BSC, and can be downloaded from the BSC. At the BTS there may be either single instances of the software, or there may also be back-up versions. 4.1. Definition of the Procedures All the procedures covered in this Specification are based on formatted O&M messages. Most formatted O&M mes

39、sages initiated by the BTS or the BSC will receive a response or acknowledgement at Layer 3. A pair of such messages, or single message if a response is not required, is referred to as an elementary procedure. All messages are sent using I frames at Layer 2. A number of procedures, referred to as st

40、ructured procedures (see GCM 12.22), are based on a multiplicity of elementary procedures. Some structured procedures may also involve MMI messages, but these are not defined in this specification. Descriptions of the messages and the direction of transmission are given in the following sections. No

41、 elementary procedure is initiated to an object instance which has not yet replied to a previously initiated elementary procedure with a response, an ACK or a NACK within a layer 3 time-out. The layer 3 timeout for ACK, NACK and responses shall have a default value of 10 seconds. An ACK message is r

42、eturned to inform the application initializing the message that the command is performed or will be performed. The whole message is rejected if there is something not understood/supported in the original message. A NACK is not relevant for all elementary procedures. The most relevant Nack causes, no

43、t covered by the general causes (which are used for understanding of header fields), are given for each elementary procedure with reference to the coding of the Nack causes in sec. 7.4.34. The general Nack causes are relevant for any Nack message and are also found in section 7.4.34. m 3404583 OOL47

44、 9Lb m GSM 12.21 - 4.2.0 - page 10 4.2. SW Download Management Procedures 4.2.1. Load Data Initiate This message is sent from the BSC to the BTS to initiate the loading of a file. It indicates the number of segments for which Layer 3 acknowledgements are required (window size). When receiving data t

45、he BTS sends an ACK after this number of segments, except for the last batch. BSC BTS Load Data Initiate ACK/NACK II Load Data Segment Load Data Segment Window Size I I ACK - Load Data Segment etc etc The ACK is for the number of segments specified in the Load Data Initiate message, except that when

46、 all the expected blocks have been received the ACK is sent regardless of the window size. If a time-out on the Layer 3 acknowledgement expires, the BSC sends a Load Data Abort message and the file transfer is aborted. Meaning of Ack message : A window of Load data segment messages or a complete fil

47、e has been received. 4.2.3. Load Data Abort This message is used by either end if the file transfer can no longer be supported. This message will also be used by the BTS if the received amount of data exceeds the expected amount. ESC BTS Load Data Abort = 3404583 0099348 852 GSM 12.21 - 4.2.0 - page

48、 11 4.2.4. Load Data End This message is sent by the BSC to the BTS. The BTS sends an ACK when the file has been received in the BTS. BSC BTS Load Data End ACK/NACK . Meaning of Ack message : File download is successfully terminated Message specific Nack causes (ref.sec. 7.4.34.) : 25. 4.2.5. SW Act

49、ivate Request This message is sent by the BTS when the resource presented by the object instance (Site Manager, Transceiver) has started up. The initialization of mentioned object instance is started with software activation, which may include software download continuing with attribute setting. BSC BTS SW Activate Request ACK/NACK c Meaning of Ack message : The request is granted and software activation will be commenced. Message specific Nack causes (ref.sec. 7.4.34.) : None. 4.2.6. Activate SW This message from the BSC to the BTS activates the loaded software, indica