OrganizedProgrammers/ETSISpecContent · Datasets at Hugging Face

hash stringlengths 32 32	doc_id stringlengths 7 13	section stringlengths 3 121	content stringlengths 0 3.58M
e59ea8dcad939b2b08179091ad5f515d	100 623	6.4.2 Disconnect Multi-drop Link	This message shall be used to disconnect a multi-drop configuration in the BTS. BSC BTS Disconnect Multi-drop Link --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified multi-drop link connection has been disconnected. Message specific Nack causes (see subclause 9.4.36): 20. ETSI 21 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	6.5 Air Interface Management Procedures
e59ea8dcad939b2b08179091ad5f515d	100 623	6.5.1 Set BTS Attributes	This message shall be sent to provide an object instance on BTS with all the necessary attributes relating to that BTS object. This message does also include common information for all logical channels of one type, e.g., CCCH parameters. BSC BTS Set BTS Attributes --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: All specified BTS attributes have been set. Message specific Nack causes (see subclause 9.4.36): 23.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.5.2 Set Radio Carrier Attributes	This message shall be used to set a Radio Carrier's RF-related attributes such as the frequencies and the power. BSC BTS Set Radio Carrier Attributes --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: All specified Radio Carrier attributes have been set. Message specific Nack causes (see subclause 9.4.36): 1B, 23.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.5.3 Set Channel Attributes	This message shall be sent for each Channel instance to give the channel combination as defined in GSM 05.02 for that time slot. It shall be possible to send one message, if all 8 radio time slots need the same attribute value. This shall be done by not addressing one specific Channel instance in the Instance field in the header, but using a broadcast address. The message may include starting time. BSC BTS Set Channel Attributes --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: All specified channel attributes have been set. Message specific Nack causes (see subclause 9.4.36): 23.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.6 Test Management Procedures
e59ea8dcad939b2b08179091ad5f515d	100 623	6.6.1 Perform Test	This message shall be used to tell the BTS to perform a test, if necessary to set a physical configuration for the BSC to carry out a test on the BTS, or to perform a test using a particular configuration. Any measurements may be performed as specific tests. Duration for the test can be given, after which the test report may be autonomously sent if so requested. Three tests are defined. 1) A radio loop test via the antenna shall be used to test all equipment needed to provide service of one traffic channel. The loop starts and ends in the transceiver baseband parts and loops one traffic channel back in the air interface i.e., using actual antenna equipment. The baseband parts of the transceiver calculate the bit error rate to describe the quality of service that channel provides. ETSI 22 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) 2) A radio loop test via the transceiver shall be used to test most of the equipment needed to provide service of one traffic channel. The loop starts and ends in the transceiver baseband parts and loops one traffic channel back inside the transceiver before the antenna combining equipment. The baseband parts of the transceiver calculate the bit error rate to describe the quality of service that channel provides. This test can be used in conjunction with the previous test to discriminate the location of a possible hardware failure. 3) A functional object self test shall be used to activate an internal self test procedure of a functional object on the BTS made to test equipment that provides the services of the functional object. By its nature this test and its results are proprietary. BSC BTS Perform Test --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Test configuration has been set (if necessary) and the specified test has been started. Message specific Nack causes (see subclause 9.4.36): 1C, 1D, 1E.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.6.2 Test Report	This message shall be sent by the BTS giving the result of a test ordered by the BSC and is sent autonomously as soon as the result is available. A Test Report shall also be sent after a specific request from the BSC by a Send Test Report message. The Test Report indicates what was tested, the test type, and the result. No Ack or Nack is returned to the BTS. BSC BTS Test Report <--------------------------------------------
e59ea8dcad939b2b08179091ad5f515d	100 623	6.6.3 Send Test Report	This message shall be sent from the BSC to ask for the result/report of a test which was not to be sent autonomously now to be started being reported. If the test result was already made to be autonomously reported, this message can also be used to have the present result of the test be reported immediately. The message must include identification of the test. BSC BTS Send Test Report --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified test report will be sent. Message specific Nack causes (see subclause 9.4.36): 1C, 1F.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.6.4 Stop Test	This message shall be used by the BSC to stop a continuously recurring test at the BTS, to reset a physical test configuration to the normal configuration, or to stop the test and to restore to the normal physical configuration. The message must include identification of the test being performed. BSC BTS Stop Test --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified test has been stopped and test configuration reset to normal (if necessary). Message specific Nack causes (see subclause 9.4.36): 20, 21, 22. ETSI 23 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7 State Management and Event Report Procedures
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7.1 State Changed Event Report	An unsolicited report shall be sent from the BTS to the BSC whenever a change of the operational state or of the optional manufacturer dependent state of a managed object defined in this GTS occurs. The message shall be also sent when any site input changes its state. A failure, causing change of operational state, shall generate two event reports: State Changed Event Report and Failure Event Report. No Ack or Nack is returned to the BTS. BSC BTS State Changed Event Report <--------------------------------------------
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7.2 Failure Event Report	An unsolicited report shall be sent from the BTS to the BSC whenever failure events occur in the BTS. Such failure events are: - fault in a resource resulting from passing a threshold but not constituting a failure; - failure of a resource. Pertaining to a failure, there shall be a report for its start and another for its cease. A failure causing change of operational state shall generate two event reports: State Changed Event Report and Failure Event Report. No Ack or Nack is returned to the BTS. BSC BTS Failure Event Report <--------------------------------------------
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7.3 Stop Sending Event Reports	This inhibition of sending of event reports shall be used by the BSC to prevent a flood of event reports which are of no benefit to the BSC. One example of this occurs at a BTS restart following a power failure. The operational capability of the BTS hardware is unlikely to be different from what it was before the failure, and a flood of reports, each stating that a piece of hardware is operating, will delay the software download. Another example concerns the case of a frequently occurring transient fault. BSC BTS Stop Sending Events Reports --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Sending of specified Event Report has been stopped. Message specific Nack causes (see subclause 9.4.36): None. ETSI 24 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7.4 Restart Sending Event Reports	When the BTS is back in normal operation or if it is of interest to check whether the BTS still generates a flood of Event Reports, a Restart Sending Event Reports shall be sent. BSC BTS Restart Sending Events Reports --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Sending of specified Event Report has been restarted. Message specific Nack causes (see subclause 9.4.36): None.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7.5 Change Administrative State	The Change Administrative State message shall be used by the BSC to change the administrative state (as specified by specification GSM 12.20) of a managed object. BSC BTS Change Administrative State --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified change of administrative state has been performed. Message specific Nack causes (see subclause 9.4.36): None.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7.6 Change Administrative State Request	This request message shall be sent by the BTS when there is a need to change the administrative state of a managed object at the BTS site. This message can only be initiated as a result of a local MMI command. BSC BTS Change Administrative State Request <-------------------------------------------- ACK/NACK --------------------------------------------> Meaning of Ack message: The request is granted and a change administrative state message will be sent. Message specific Nack causes (see subclause 9.4.36): 28, 29.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.7.7 Report Outstanding Alarms	This message shall be used by the BSC to ask BTS to report all outstanding alarms related to the object instance indicated in the message. The BTS shall report alarms by sending a series of Failure Event Report messages for all outstanding alarms. Only those alarms previously reported and still outstanding shall be re-reported through this procedure. Any new alarms not yet reported but about to be reported shall be excluded and they shall be reported through a separate Failure Event Report procedure spontaneously initiated by the BTS itself. If there is no outstanding alarm, the BTS shall reply with a NACK with that cause indicated. BSC BTS Report Outstanding Alarms --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Sending of Failure Event Report will start. Message specific Nack causes (see subclause 9.4.36): 28, 29, 2A. ETSI 25 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	6.8 Equipment Management Procedures
e59ea8dcad939b2b08179091ad5f515d	100 623	6.8.1 Change-over	This message shall be sent to change over between active and standby units of equipment. The action may be performed on any addressable BTS entity, manufacturer dependent HW units included. Which type of HW unit to address and how to identify certain units of this type of HW are manufacturer dependent. BSC BTS Changeover --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified change-over operation has been performed. Message specific Nack causes (see subclause 9.4.36): 19, 1A, 1E, 23.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.8.2 Opstart	This message shall be sent by the BSC to tell the BTS to attempt to operatethe identified object putting it to an initial normal operational state (i.e., "enabled", see subclause 5.3.2). This message does not affect the object's administrative state if there exists a value explicitly assigned by the BSC. If there is yet no administrative state value explicitly set by the BSC (e.g., at an initialization time), the object shall be presumed to be administratively locked by default. No BTS function is required to be responsible for testing the operability of the identified resource as a consequence of this message. Prior to this message being issued, all necessary physical and logical preparations (such as repair of equipment, software downloading, parameter setting, etc., as needed) are expected to have been completed. If the object is in fact not ready to be in an enabled state, the object will be in a fault condition as a consequence of this message, and the condition shall be handled by the object's normal fault handling function as the condition is detected. BSC BTS Opstart --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The BTS has reset the operational state of the specified object to "enabled" state. Message specific Nack causes (see subclause 9.4.36): 19, 1A, 23.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.8.3 Reinitialize	This message shall be sent by the BSC to tell the BTS to have specified hardware resource of the indicated object start a re-initialization procedure as sketched in figure 2. The specifics of a re-initialization procedure, which typically takes place at the time of a cold start of the resource, is manufacturer-dependent. For a software reinitialization, Activate SW message shall be used. BSC BTS. Reinitialize --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The BTS has received the message and is about to start a reinitialization of the specified resource. Message specific Nack causes (see subclause 9.4.36): 19, 1A, 23. ETSI 26 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	6.8.4 Set Site Outputs	This message shall be sent by the BSC to tell the BTS to set specified site outputs to the specified state. BSC BTS Set Site Outputs --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The outputs have been set. Message specific Nack causes (see subclause 9.4.36): None.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.9 Measurement Management Procedures
e59ea8dcad939b2b08179091ad5f515d	100 623	6.9.1 Measurement Result Request	This message shall be used by the BSC to request the result of a certain measurement which is running in the BTS to be sent to the BSC. After having responded with the current result, the BTS initializes the measurement result buffer (e.g. setting to zero) and continues the measurement. BSC BTS Measurement Result Request --------------------------------------------> Response/NACK <-------------------------------------------- Message specific Nack causes (see subclause 9.4.36): 2A, 2B.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.9.2 Measurement Result Response	This message shall be used by the BTS to successfully respond to the BSC on an associated Measurement Result Request completing a Measurement Result Request elementary procedure. By this message, the presently registered measurement result requested shall be reported. If it is not possible for any reason, a NACK message must be used instead of this.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.9.3 Stop Measurement	This message shall be used by the BSC to stop a continuously running measurement at the BTS. The message must include identification of the measurement to be stopped. BSC BTS Stop Measurement --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified measurement has been stopped Message specific Nack causes (see subclause 9.4.36): 2A ETSI 27 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	6.9.4 Start Measurement	This message shall be used by the BSC to start a measurement continuously at the BTS. The message must include identification of the measurement to be started. BSC BTS Start Measurement --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified measurement has been started Message specific Nack causes (see subclause 9.4.36): 2A
e59ea8dcad939b2b08179091ad5f515d	100 623	6.10 Miscellaneous Procedures
e59ea8dcad939b2b08179091ad5f515d	100 623	6.10.1 Get Attributes	This message shall be used by the BSC to tell the BTS to send attributes which have previously been set by the BTS. It may be used as a check on accuracy and be incorporated into normal procedures, or may be used by the BSC to recover information which it has lost. BSC BTS Get Attributes --------------------------------------------> Response/NACK <-------------------------------------------- Message specific Nack causes (see subclause 9.4.36): None.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.10.2 Set Alarm Threshold	This message shall be used by the BSC to tell the BTS some threshold parameters related to fault thresholds. BSC BTS Set Alarm Threshold --------------------------------------------> ACK/NACK <-------------------------------------------- Message specific Nack causes (see subclause 9.4.36): None.
e59ea8dcad939b2b08179091ad5f515d	100 623	6.10.3 Get Attributes Response	This message shall be used by the BTS to successfully respond to the BSC on an associated Get Attribute elementary procedure. By this message, the presently set values of all requested attributes shall be reported. Otherwise, a NACK message shall be used instead of this.
e59ea8dcad939b2b08179091ad5f515d	100 623	7 Structured Procedures	Applicable structured A-bis procedures are described in GSM 12.22.
e59ea8dcad939b2b08179091ad5f515d	100 623	8 Message Details	The formats of all messages in subclauses 8.3 through 8.11 are described each by a table format illustration with no formal text description provided because of the self-explanatory nature of the illustration. ETSI 28 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.1 Message Categories	This subclause defines the transport format and coding of the four Network. Management message categories sent over the Abis interface. The various message categories may be sent in either direction. In each message, the message discriminator identifies the category and is transmitted first. In a message the octets must be sent in the order shown in the description of the messages. In an octet, bit 1 must be transmitted first. In the following subclauses, M and O denote whether information elements are mandatory or optional.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.1.1 Formatted O&M Messages	The message format and coding of these messages are as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 1 0 0 0 0 0 0 0 Placement Indicator M 1 1) Sequence Number M 1 2) Length Indicator M 1 Binary, 3) O&M Data Field M V 4) NOTE 1: The meanings and codings of the Placement Indicator are: - only: This message is contained within one segment 1 0 0 0 0 0 0 0; - first: The first segment of a multi-segment message 0 1 0 0 0 0 0 0; - middle: A middle segment of a multi-segment message 0 0 1 0 0 0 0 0; - last: The last segment of a multi-segment message 0 0 0 1 0 0 0 0. NOTE 2: This is the sequence number of the segment in the message, modulo 256, starting with 00000000. Thus a single segment message is here coded 00000000. The number can be incremented unlimitedly being wrapped around the modulo to transport very long multi-segment messages. NOTE 3: The Length Indicator gives the length of the O&M data field in the message segment being transported which is less than or equal to 255 octets. This length indicator should not be confused with the actual length of the message at the logical level that may go over multiple segments. This length indicator should not be confused also with attribute value length indicator described in subclause 8.2. NOTE 4: Coding for O&M Data field is found in subclause 8.2 and the following subclauses.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.1.2 MMI Transfer	The message format and coding of these messages are as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 0 1 0 0 0 0 0 0 Placement Indicator M 1 note 1 of subclause 8.1.1 Sequence Number M 1 note 2 of subclause 8.1.1 Length Indicator M 1 Binary, 1) MMI Data Field M V Proprietary NOTE: The Length Indicator gives the length of the MMI data field in the message segment being transported which is less than or equal to 255 octets. See also note 3 of subclause 8.1.1. The protocol for MMI is not covered in this GTS. ETSI 29 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.1.3 TRAU O&M Messages	These messages are required for option (ii) of subclause 4.10.1 of specification GSM 08.60. The message format is as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 0 0 1 0 0 0 0 0 Channel Number M 1 1) Repetition Indicator M 1 2) TRAU O&M Message O 33 3) NOTE 1: The channel number element shall be coded as defined for the octet of the channel number information element of specification GSM 08.58. NOTE 2: The meanings and codings of the Repetition Indicator are: - terminate sending of O&M TRAU frames: 0 0 0 0 0 0 0 1; - repeat sending of O&M TRAU frames every 20 ms until a terminate order is received 0 0 0 0 0 0 1 0; - send O&M TRAU frame once: 0 0 0 0 0 1 0 0. NOTE 3: The TRAU O&M message is not sent when the Repetition Indicator is set to 00000001, but sending of the TRAU O&M message is mandatory otherwise. All 264 bits of the TRAU O&M frame information field are sent unchanged in the 33 octets.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.1.4 Manufacturer-Defined O&M messages	The message format and coding of these messages is as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 0 0 0 1 0 0 0 0 Placement Indicator M 1 note 1 of subclause 8.1.1 Sequence Number M 1 note 2 of subclause 8.1.1 Length Indicator M 1 Binary, 1) ManId Length Indicator M 1 Binary, 2) Manuf. Identifier M V 3) Man-Def O&M Data Field M V Proprietary NOTE 1: The Length Indicator gives the length of the Manufacturer-defined O&M data field in the message segment being transported which is less than or equal to 255 octets. See also note 3 of subclause 8.1.1 NOTE 2: The Length Indicator gives the length of the Manufacturer Identifier field which must be less than or equal to 255 octets. NOTE 3: The Manufacturer Identifier is an octet string of maximally 255 octets. This value, to be appropriately determined by an arrangement between the operator and the manufacturer, may or may not be related to the value of the attribute Manufacturer Id (Attribute Id: 1E) listed in subclause 9.4. Remarks: Since the Data Field of messages of this category is not subject to a GSM standardization, it should be noted that a compliance to messages of this category does not guarrantee an interoperability between different manufacturers.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.2 Structure of Formatted O&M Messages	This subclause provides details of all the formatted O&M messages. In every case when particular header octets provide no usable information at the receiver, they shall be coded all 1's. ETSI 30 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) All fields in the messages are marked with M for Mandatory or O for Optional. This indicates whether the field is mandatory or optional to be contained in a message, and not whether it is mandatory or optional to be used or set for every BTS. This allows to change a single attribute without having to repeat all the attributes not to be changed. The header fields of formatted O&M messages (see below) are always mandatory. The attributes defined for a certain message supported by the BTS implementation are mandatory to be used if not stated otherwise in an explanatory note. The first octet of the formatted O&M messages shall identify the message types. Some messages are replied by an ACK or a NACK response. The replies shall be distinguished by different codings of the message type (the first octet of formatted O&M messages). See subclause 9.1. ACK messages shall return all the attributes in the original message. NACK messages shall add a Nack cause field (two octets) at the end of the message. None of the messages concerned requires all of the capacity available in a Layer 2 segment, so the NACK message will not need a second Layer 2 frame. An ACK to a number of Load Data Segments shall consist of only the header with the 'Load Data Segment Ack' message type. All attributes shall overwrite those defined in an earlier message since start-up or the last restart. Optional attributes provide new information if they have not been defined in an earlier message. The message type and managed object identification are given in the message header as is illustrated below: INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 The Object Class information element shall be filled in with the correct information in accordance with this GTS. The Object Instance information element shall contain three fields: 1) the BTS Number identifies one BTS in a multi cell site; 2) the Baseband Transceiver number or the Radio Carrier number identifies which Baseband Transceiver or Radio Carrier is concerned in the message; 3) the third element identifies a radio timeslot (0-7) of the Baseband Transceiver identified by 2). For further information see subclause 9.3. The FORMAT field describes the structure of each information element using T(Tag), L(Length) and V(Value) coding. T is the attribute identifier. V is the actual information presented. L must be indicated if the the information element is of variable length and its prediction is not possible in the context . L shall binary-represent in a two octet space the the number of octets in the remaining part of information element. Note that this Length code differs from the "Length Indicator" described in subclause 8.1.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3 SW Download Management Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3.1 Load Data Initiate	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 SW Description 9.4.62 M TV >=2 Window Size 9.4.59 M TV 2 ETSI 31 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3.2 Load Data Segment	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 File Data 9.4.17 M (note) TLV >=2 NOTE: File Data is segments of the actual file to be transferred.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3.3 Load Data Abort	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3.4 Load Data End	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 SW Description 9.4.62 M (note) TV >=2 NOTE: The same SW Description as in the corresponding Load Data Initiate message.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3.5 SW Activate Request	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 HW Configuration 9.4.62 M TLV >=2 SW Configuration 9.4.61 M TLV >=2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3.6 Activate SW	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 SW Description 9.4.62 O (note) TV >=2 NOTE: SW Descriptions may be repeated for multiple software activation. No SW Description entry implies all software for the object instance.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.3.7 SW Activated Report	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 ETSI 32 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.4 A-bis Interface Management Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.4.1 Establish TEI	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 TEI 9.4.54 M TV 2 Abis Channel 9.4.1 M TV 4
e59ea8dcad939b2b08179091ad5f515d	100 623	8.4.2 Connect Terrestrial Signalling	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4
e59ea8dcad939b2b08179091ad5f515d	100 623	8.4.3 Disconnect Terrestrial Signalling	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4
e59ea8dcad939b2b08179091ad5f515d	100 623	8.4.4 Connect Terrestrial Traffic	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4 Radio Sub Channel 9.4.46 O TV 2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.4.5 Disconnect Terrestrial Traffic	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4 Radio Sub Channel 9.4.46 O TV 2 ETSI 33 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.5 Transmission Management Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.5.1 Connect Multi-drop link	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Multi-drop BSC Link 9.4.34 M (note 1) TV 3 Multi-drop next BTS Link 9.4.35 M (note 2) TV 3 NOTE 1: This attribute specifies the incoming (in BSC direction) 64 kbps timeslot to be set up to another BTS in a multi-drop configuration. NOTE 2: This attribute specifies the outgoing (to the next BTS direction) 64 kbps timeslot to be set up through the BTS in a multi-drop configuration.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.5.2 Disconnect Multi-drop link	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Multi-drop BSC Link 9.4.34 M (note 1) TV 3 Multi-drop next BTS Link 9.4.35 M (note 2) TV 3 NOTE 1: This attribute specifies the incoming (in BSC direction) 64 kbps timeslot to be taken down from another BTS in a multi-drop configuration. NOTE 2: This attribute specifies the outgoing (to the next BTS direction) 64 kbps timeslot to be taken down through the BTS in a multi-drop configuration.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.6 Air Interface Management Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.6.1 Set BTS Attributes	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Interference Level Boundaries 9.4.25 O (note 1) TV 7 Intave Parameter 9.4.24 O TV 2 Connection Failure Criterion 9.4.14 O TLV >=4 T200 9.4.53 O (note 2) TV 8 Max Timing Advance 9.4.31 O (note 3) TV 2 Overload Period 9.4.39 O (note 5) TLV >=2 CCCH Load Threshold 9.4.12 O (notes 4 and 5) TV 2 CCCH Load Indication Period 9.4.11 O (note 5) TV 2 RACH Busy Threshold 9.4.44 O (note 5) TV 2 RACH Load Averaging Slots 9.4.45 O (note 5) TV 3 BTS Air Timer 9.4.10 O TV 2 NY1 9.4.37 O TV 2 BCCH ARFCN 9.4.8 O TV 3 BSIC 9.4.9 O TV 2 Starting Time 9.4.52 O (note 6) TV 3 ETSI 34 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) NOTE 1: Interference Level Boundaries Boundary 0 (see GSM 05.08) Boundary x1 ¦ ¦ Boundary x5 NOTE 2: For FACCH and SACCH. NOTE 3: Optional in BTS design and administration use. NOTE 4: Presentation of the load threshold in 1% steps. NOTE 5: These attributes are special CCCH Parameters NOTE 6: For synchronisation of when the specific action defined in the message shall be performed. Needed only to change BCCH ARFCN or BSIC while in operation.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.6.2 Set Radio Carrier Attributes	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 RF Max Power Reduction 9.4.47 O TV 2 ARFCN list 9.4.5 O (note) TLV >=2 NOTE: The structure of value will vary depending on the mode of frequency hopping supported.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.6.3 Set Channel Attributes	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Channel Combination 9.4.13 O TV 2 HSN 9.4.21 O (note 1) TV 2 MAIO 9.4.27 O (note 1) TV 2 ARFCN list 9.4.5 O (note 2) TLV >=2 Starting Time 9.4.52 O (note 3) TV 3 TSC 9.4.60 O (note 4) TV 2 NOTE 1: Used only in a hopping channel. NOTE 2: If frequency hopping is not in use, the only frequency of the Radio Carrier is set with the message Radio Carrier Attributes. NOTE 3: For synchronisation of when the specific action defined in the message shall be performed. NOTE 4: A NULL value signifies that the BCC shall be used as the TSC value for the channel. ETSI 35 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.7 Test Management Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.7.1 Perform Test	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2 Autonomously Report 9.4.6 M TV 2 Test Duration 9.4.55 O TV 3 Physical Configuration 9.4.40 O (note) TLV >=2 NOTE: Use of Physical Configuration depends on the need on extra information in setting up specific test configurations.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.7.2 Test Report	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2 Test Report Info 9.4.57 M (note) TLV >=2 NOTE: The test report information may give a numerical result or an indication of the range into which the test report falls.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.7.3 Send Test Report	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.7.4 Stop Test	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2 ETSI 36 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8 State Management and Event Report Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8.1 State Changed Event Report	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Operational State 9.4.38 O TV 2 Availability Status 9.4.7 O TLV >=2 Man.dep. State 9.4.28 O TV 2 Site Inputs 9.4.48 O TLV >=2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8.2 Failure Event Report	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Event Type 9.4.16 M TV 2 Perceived Severity 9.4.63 M TV 2 Probable Cause 9.4.43 M TV 4 Specific Problems 9.4.51 O (note 1) TV 2 HW Description 9.4.23 O (notes 1 and 2) TV >=2 SW Description 9.4.62 O (notes 1 and 2) TV >=2 Additional Text 9.4.3 O (note 1) TLV >=2 Additional Info 9.4.2 O (note 1) TLV >=2 Outstanding Alarm Sequence 9.4.65 O (note 3) TV 2 NOTE 1: Depending on the nature of the specific failure and the BTS implementation, only the needed and supported attributes shall be sent. NOTE 2: This field shall be included to identify the specific associated equipment or software in case the addressed functional object alone is not sufficient to localize the failure. NOTE 3: This field shall be included if and only if this report is a response to a Report Outstanding Alarms message.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8.3 Stop Sending Event Reports	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Operational State 9.4.38 O (note 1) TV 2 Availability Status 9.4.7 O (note 1) TLV >=2 Manufacturer Dependant State 9.4.28 O (note 1) TV 2 Probable Cause 9.4.43 O (note 1) TV 4 Specific Problems 9.4.51 O (note 1) TV 2 NOTE 1: Stop sending event reports concerning events with any of the parameter values in this attribute list. Depending on the type of event report that shall be stopped, one or some of the attributes shall be sent. The effect of multiple optional attributes in one message is that only those events that satisfy all the attributes simultaneously shall stop. The effect of repeated uses of this message with each different optional attribute is accumulative, thus, is different from the effect of putting all the optional attributes listed together at once in one message. If there occurs any inconsistency or confusion between the conditions for stopping and starting (see subclause 8.8.4), the event shall be reported instead of being stopped. ETSI 37 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) NOTE 2: This message with no optional attributes means that all event reports shall be stopped from now.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8.4 Restart Sending Event Reports	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Operational State 9.4.38 O (note 1) TV 2 Availability Status 9.4.7 O (note 1) TLV >=2 Manufacturer Dependent State 9.4.28 O (note 1) TV 2 Probable Cause 9.4.43 O (note 1) TV 4 Specific Problems 9.4.51 O (note 1) TV 2 NOTE 1: Restart sending event reports concerning events with any of the parameter values in this attribute list. Depending on the type of event report that needs to be restarted, one or some of the attributes shall be sent. The effect of multiple optional attributes is just same as multiple messages repeated with each attribute one by one and events that satisfy any one of the attribute set shall be reported. Note the difference from the condition stated in note 1 of subclause 8.8.3. NOTE 2: This message with no optional attributes means that all event reports shall be started from now.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8.5 Change Administrative State	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Administrative State 9.4.4 M (note) TV 2 NOTE: Required new administrative state for the specified managed object.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8.6 Change Administrative State Request	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Administrative State 9.4.4 M (note) TV 2 NOTE: The requested administrative state for the specified managed object.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.8.7 Report Outstanding Alarms	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 ETSI 38 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.9 Equipment Management Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.9.1 Changeover	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Source 9.4.50 M (note 1) TLV >=2 Destination 9.4.15 M (note 2) TLV >=2 NOTE 1: Source is the manufacturer dependent identity of piece of equipment that shall be taken out of active servicing (changed-over from) and replaced by the Destination. NOTE 2: Destination is the manufacturer dependent identity of piece of equipment that shall be put into active servicing (changed-over to) in place of the Source.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.9.2 Opstart	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3
e59ea8dcad939b2b08179091ad5f515d	100 623	8.9.3 Reinitialize	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 HW Description 9.4.23 O (note) TV >=2 NOTE: HW Descriptions may be repreated for multiple resources. If no HW Description is provided, all resource for the objectis is implied. For a software reinitialization, Activate SW message shall be used.
e59ea8dcad939b2b08179091ad5f515d	100 623	8.9.4 Set Site Outputs	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Site Outputs 9.4.49 M TLV >=2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.9.5 Change HW Configuration	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Site Outputs 9.4.49 M TLV >=2 ETSI 39 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.10 Measurement Management Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.10.1 Measurement Result Request	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.10.2 Measurement Result Response	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2 Measurement Result 9.4.32 M TLV >= 2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.10.3 Start Measurement	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.10.4 Stop Measurement	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.11 Miscellaneous Messages
e59ea8dcad939b2b08179091ad5f515d	100 623	8.11.1 Get Attributes	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 List of Required Attributes 9.4.26 M (note) TLV >=2 NOTE: Any of the attributes defined in subclause 9.4, including those not marked with an X in the GET column, can be requested by Get Attributes message. ETSI 40 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	8.11.2 Set Alarm Threshold	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Probable Cause 9.4.43 M TV 4 Power Output Thresholds 9.4.42 O TV 4 VSWR Thresholds 9.4.58 O TV 3 Manufacturer Dependent Thresholds 9.4.29 O TLV >=2
e59ea8dcad939b2b08179091ad5f515d	100 623	8.11.3 Get Attribute Response	INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Get Attribute Response Info 9.4.64 M TLV >=4
e59ea8dcad939b2b08179091ad5f515d	100 623	9 Coding	This clause defines the coding of each field in the messages defined in earlier clauses. The following conventions are required: - the least significant bit shall be transmitted first, followed by bits 2, 3, 4, etc; - in an element where octets are identified by an octer number, Octet 1 shall be transmitted first, then octet 2, etc; - when a field extends over more than one octet, the order of bit values shall progressively decrease as the octet number increases. The least significant bit of the field shall be represented by the lowest numbered bit of the highest numbered octet of the field; - for unpredictable variable length elements, a length indication coding method defined in subclause 8.2 shall be used. Always the length information shall indicate the number of element units (which is octets) following the length indicator excluding the space for the length findicator itself; - all defined values are indicated in this GTS. Other values are reserved.
e59ea8dcad939b2b08179091ad5f515d	100 623	9.1 Message Type	The Message Type is coded with 1 octet as illustrated below. Message Type 1 The following message types are used (all other values reserved). Message Type hexadecimal code SW Download Management Messages: Load Data Initiate 01 Load Data Initiate Ack 02 Load Data Initiate Nack 03 Load Data Segment 04 ETSI 41 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Load Data Segment Ack 05 Load Data Abort 06 Load Data End 07 Load Data End Ack 08 Load Data End Nack 09 SW Activate Request 0A SW Activate Request Ack 0B SW Activate Request Nack 0C Activate SW 0D Activate SW Ack 0E Activate SW Nack 0F SW Activated Report 10 A-bis Interface Management Messages: Establish TEI 21 Establish TEI Ack 22 Establish TEI Nack 23 Connect Terrestrial Signalling 24 Connect Terrestrial Signalling Ack 25 Connect Terrestrial Signalling Nack 26 Disconnect Terrestrial Signalling 27 Disconnect Terrestrial Signalling Ack 28 Disconnect Terrestrial Signalling Nack 29 Connect Terrestrial Traffic 2A Connect Terrestrial Traffic Ack 2B Connect Terrestrial Traffic Nack 2C Disconnect Terrestrial Traffic 2D Disconnect Terrestrial Traffic Ack 2E Disconnect Terrestrial Traffic Nack 2F Transmission Management Messages: Connect Multi-Drop Link 31 Connect Multi-Drop Link Ack 32 Connect Multi-Drop Link Nack 33 Disconnect Multi-Drop Link 34 Disconnect Multi-Drop Link Ack 35 ETSI 42 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Disconnect Multi-Drop Link Nack 36 Air Interface Management Messages: Set BTS Attributes 41 Set BTS Attributes Ack 42 Set BTS Attributes Nack 43 Set Radio Carrier Attributes 44 Set Radio Carrier Attributes Ack 45 Set Radio Carrier Attributes Nack 46 Set Channel Attributes 47 Set Channel Attributes Ack 48 Set Channel Attributes Nack 49 Test Management Messages: Perform Test 51 Perform Test Ack 52 Perform Test Nack 53 Test Report 54 Send Test Report 55 Send Test Report Ack 56 Send Test Report Nack 57 Stop Test 58 Stop Test Ack 59 Stop Test Nack 5A State Management and Event Report Messages: State Changed Event Report 61 Failure Event Report 62 Stop Sending Event Reports 63 Stop Sending Event Reports Ack 64 Stop Sending Event Reports Nack 65 Restart Sending Event Reports 66 Restart Sending Event Reports Ack 67 Restart Sending Event Reports Nack 68 Change Administrative State 69 Change Administrative State Ack 6A Change Administrative State Nack 6B ETSI 43 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Change Administrative State Request 6C Change Administrative State Request Ack 6D Change Administrative State Request Nack 6E Report Outstanding Alarms 93 Report Outstanding Alarms Ack 94 Report Outstanding Alarms Nack 95 Equipment Management Messages: Changeover 71 Changeover Ack 72 Changeover Nack 73 Opstart 74 Opstart Ack 75 Opstart Nack 76 Reinitialize 87 Reinitialize Ack 88 Reinitialize Nack 89 Set Site Outputs 77 Set Site Outputs Ack 78 Set Site Outputs Nack 79 Change HW Configuration 90 Change HW Configuration Ack 91 Change HW Configuration Nack 92 Measurement Management Messages: Measurement Result Request 8A Measurement Result Response 8B Stop Measurement 8C Start Measurement 8D Other Messages: Get Attributes 81 Get Attributes Response 82 Get Attributes Nack 83 Set Alarm Threshold 84 Set Alarm Threshold Ack 85 Set Alarm Threshold Nack 86 ETSI 44 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	9.2 Object Class	An Object Class shall be coded with 1 octet. The values of the object class code are as defined below. Object Class 1 Object Class hexadecimal code Site Manager 00 BTS 01 Radio Carrier 02 Baseband Transceiver 04 Channel 03 <reserved for future use> <05-FE> NULL FF
e59ea8dcad939b2b08179091ad5f515d	100 623	9.3 Object Instance	The Object Instance shall be coded with 3 octets, addressing the specific object of the given object class as illustrated below. BTS number 1 Baseband Transceiver or Radio Carrier number 2 Radio Timeslot number 3 All 3 octets are mandatory in the header of every message. The BTS number distinguishes BTSs which are unique for each cells at a site under the Site Manager. The Baseband Transceiver or Radio Carrier number distinguishes either Baseband Transceivers or Radio Carriers under the BTS. The Radio Timeslot number distinguishes channels under the Baseband Transceiver. When the object class is Site Manager, all three octets shall be NULLs, because there is only one Site Manager, which doesn't need an identifier. When the object class is BTS, octet 1 shall be a binary presentation of the identifier of the addressed BTS. Octets 2 and 3 shall be coded NULLs. If the BTS number is NULL, it shall be understood as referring to all BTSs under the Site Manager. When the object class is Baseband Transceiver or Radio Carrier, octet 2 shall be a binary presentation of the identifier of the addressed Baseband Transceiver or Radio Carrier object, and octet 1 is the identiferrof the BTS above it. Octet 3 is coded NULL. If the Baseband Transceiver or Radio Carrier number is NULL, it shall be understood as referring to all instances of the class under the BTS. When the object class is Channel, octet 3 shall be a binary presentation of the identifier of the addressed radio timeslot, octet 2 shall be the identifier of the Baseband Transceiver, and octet 1 shall be the identifer of the BTS above the addressed Channel. If the radio timeslot number is NULL, it shall be understood as referring to all Channels under the Baseband Transceiver. To avoid unnecessary complexity of BTS implementation, it shall not be allowed to assign a NULL value to any object above the addressed object class. For example, if the addressed object class is the Baseband Transceiver, it is not allowed to assign a NULL value to both BTS and Baseband Transceiver instances (without this constraint, this could be understood as referring to all the Baseband Transceivers of all the BTSs). ETSI 45 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) The value for NULL shall be <FF> in all the cases mentioned above in this subclause.
e59ea8dcad939b2b08179091ad5f515d	100 623	9.4 Attributes and Parameters	The Attribute Identifier is coded with 1 octet. The number of parameters within an attribute is at least one. The length of the parameters within an attribute will vary. The attributes used and the coding of their Attribute Identifier fields are listed below. The values are in hexadecimal. The attributes marked with an X in “Get” column are only getable by the BSC, and BSC is not permitted to alter their values. Attribute Name Attribute Id. Get Abis Channel 01 X Additional Info 02 Additional Text 03 Administrative State 04 X ARFCN List 05 X Autonomously Report 06 Availability Status 07 X BCCH ARFCN 08 X BSIC 09 X BTS Air Timer 0A X CCCH Load Indication Period 0B X CCCH Load Threshold 0C X Channel Combination 0D X Connection Failure Criterion 0E X Destination 0F Event Type 11 File Data 47 File Id 12 X File Version 13 X GSM Time 14 X Get Attribute Response Info 44 HSN 15 X HW Configuration 16 X HW Conf Change Info 45 HW Description 17 X Intave Parameter 18 X Interference Level Boundaries 19 X List of Required Attributes 1A ETSI 46 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) MAIO 1B X Manufacturer Dependent State 1C X Manufacturer Dependent Thresholds 1D X Manufacturer Id 1E X Max Timing Advance 1F X Multi-drop BSC Link 20 Multi-drop next BTS Link 21 Nack Causes 22 Ny1 23 X Operational State 24 X Outstanding Alarm Sequence 46 Overload Period 25 X Physical Config 26 Power Class 27 X Power Output Thresholds 28 X Probable Cause 29 RACH Busy Threshold 2A X RACH Load Averaging Slots 2B X Radio Sub Channel 2C RF Max Power Reduction 2D X Site Inputs 2E X Site Outputs 2F X Source 30 Specific Problems 31 Starting Time 32 T200 33 X TEI 34 X Test Duration 35 Test No 36 Test Report Info 37 VSWR Thresholds 38 X Window Size 39 TSC 40 X SW Configuration 41 X ETSI 47 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) SW Description 42 X Perceived Severity 43 Measurement Result 48 Measurement Type 49 All other values are reserved for future use. The data structures of the attributes and parameters are described in the remaining part of this subclause in tablular forms with no formal text description of the individual subclauses provided because of their self-explanatory nature. Henceforth "Attribute Identifier" in this subclause means the identifier for an attribute or a parameter.
e59ea8dcad939b2b08179091ad5f515d	100 623	9.4.1 Abis Channel	Attribute Identifier 1 BTS Port Number 2 Timeslot Number 3 Subslot Number 4 BTS Port Number <0-FF> Timeslot Number Time slot in 2 Mbps link <0-1F> Subslot Number a (bits 1,2) 00 b (bits 3,4) 01 c (bits 5,6) 02 d (bits 7,8) 03 64 kbps signalling FF
e59ea8dcad939b2b08179091ad5f515d	100 623	9.4.2 Additional Info	Attribute Identifier 1 Length 2-3 Additional Info <man.dep.> 4 (cont.) (cont.) N Additional Info is a manufacturer dependent field.
e59ea8dcad939b2b08179091ad5f515d	100 623	9.4.3 Additional Text	Attribute Identifier 1 Length 2-3 Additional Text <man.dep.> 4 (cont.) (cont.) N Additional Text is a manufacturer dependent field and shall be used to include fault localization information. ETSI 48 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)
e59ea8dcad939b2b08179091ad5f515d	100 623	9.4.4 Administrative State	Attribute Identifier 1 Administrative State 2 Administrative State shall be coded as follows: Locked 01 Unlocked 02 Shutting Down 03 NULL (Adm. state not supported) FF
e59ea8dcad939b2b08179091ad5f515d	100 623	9.4.5 ARFCN List	Attribute Identifier 1 Length 2-3 ARFCN1 (MSB) 4 ARFCN1 (LSB) 5 ARFCNn (MSB) N-1 ARFCNn (LSB) N ARFCN (see GSM 05.05) <0-3FF>
e59ea8dcad939b2b08179091ad5f515d	100 623	9.4.6 Autonomously Report	Attribute Identifier 1 Autonomously Report 2 The toggle switch for autonomous report shall be coded as follows: Autonomously Report 01; Not Autonomously Report 00.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.4.2 Disconnect Multi-drop Link

This message shall be used to disconnect a multi-drop configuration in the BTS. BSC BTS Disconnect Multi-drop Link --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified multi-drop link connection has been disconnected. Message specific Nack causes (see subclause 9.4.36): 20. ETSI 21 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

6.5 Air Interface Management Procedures

e59ea8dcad939b2b08179091ad5f515d

100 623

6.5.1 Set BTS Attributes

This message shall be sent to provide an object instance on BTS with all the necessary attributes relating to that BTS object. This message does also include common information for all logical channels of one type, e.g., CCCH parameters. BSC BTS Set BTS Attributes --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: All specified BTS attributes have been set. Message specific Nack causes (see subclause 9.4.36): 23.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.5.2 Set Radio Carrier Attributes

This message shall be used to set a Radio Carrier's RF-related attributes such as the frequencies and the power. BSC BTS Set Radio Carrier Attributes --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: All specified Radio Carrier attributes have been set. Message specific Nack causes (see subclause 9.4.36): 1B, 23.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.5.3 Set Channel Attributes

This message shall be sent for each Channel instance to give the channel combination as defined in GSM 05.02 for that time slot. It shall be possible to send one message, if all 8 radio time slots need the same attribute value. This shall be done by not addressing one specific Channel instance in the Instance field in the header, but using a broadcast address. The message may include starting time. BSC BTS Set Channel Attributes --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: All specified channel attributes have been set. Message specific Nack causes (see subclause 9.4.36): 23.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.6 Test Management Procedures

e59ea8dcad939b2b08179091ad5f515d

100 623

6.6.1 Perform Test

This message shall be used to tell the BTS to perform a test, if necessary to set a physical configuration for the BSC to carry out a test on the BTS, or to perform a test using a particular configuration. Any measurements may be performed as specific tests. Duration for the test can be given, after which the test report may be autonomously sent if so requested. Three tests are defined. 1) A radio loop test via the antenna shall be used to test all equipment needed to provide service of one traffic channel. The loop starts and ends in the transceiver baseband parts and loops one traffic channel back in the air interface i.e., using actual antenna equipment. The baseband parts of the transceiver calculate the bit error rate to describe the quality of service that channel provides. ETSI 22 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) 2) A radio loop test via the transceiver shall be used to test most of the equipment needed to provide service of one traffic channel. The loop starts and ends in the transceiver baseband parts and loops one traffic channel back inside the transceiver before the antenna combining equipment. The baseband parts of the transceiver calculate the bit error rate to describe the quality of service that channel provides. This test can be used in conjunction with the previous test to discriminate the location of a possible hardware failure. 3) A functional object self test shall be used to activate an internal self test procedure of a functional object on the BTS made to test equipment that provides the services of the functional object. By its nature this test and its results are proprietary. BSC BTS Perform Test --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Test configuration has been set (if necessary) and the specified test has been started. Message specific Nack causes (see subclause 9.4.36): 1C, 1D, 1E.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.6.2 Test Report

This message shall be sent by the BTS giving the result of a test ordered by the BSC and is sent autonomously as soon as the result is available. A Test Report shall also be sent after a specific request from the BSC by a Send Test Report message. The Test Report indicates what was tested, the test type, and the result. No Ack or Nack is returned to the BTS. BSC BTS Test Report <--------------------------------------------

e59ea8dcad939b2b08179091ad5f515d

100 623

6.6.3 Send Test Report

This message shall be sent from the BSC to ask for the result/report of a test which was not to be sent autonomously now to be started being reported. If the test result was already made to be autonomously reported, this message can also be used to have the present result of the test be reported immediately. The message must include identification of the test. BSC BTS Send Test Report --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified test report will be sent. Message specific Nack causes (see subclause 9.4.36): 1C, 1F.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.6.4 Stop Test

This message shall be used by the BSC to stop a continuously recurring test at the BTS, to reset a physical test configuration to the normal configuration, or to stop the test and to restore to the normal physical configuration. The message must include identification of the test being performed. BSC BTS Stop Test --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified test has been stopped and test configuration reset to normal (if necessary). Message specific Nack causes (see subclause 9.4.36): 20, 21, 22. ETSI 23 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7 State Management and Event Report Procedures

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7.1 State Changed Event Report

An unsolicited report shall be sent from the BTS to the BSC whenever a change of the operational state or of the optional manufacturer dependent state of a managed object defined in this GTS occurs. The message shall be also sent when any site input changes its state. A failure, causing change of operational state, shall generate two event reports: State Changed Event Report and Failure Event Report. No Ack or Nack is returned to the BTS. BSC BTS State Changed Event Report <--------------------------------------------

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7.2 Failure Event Report

An unsolicited report shall be sent from the BTS to the BSC whenever failure events occur in the BTS. Such failure events are: - fault in a resource resulting from passing a threshold but not constituting a failure; - failure of a resource. Pertaining to a failure, there shall be a report for its start and another for its cease. A failure causing change of operational state shall generate two event reports: State Changed Event Report and Failure Event Report. No Ack or Nack is returned to the BTS. BSC BTS Failure Event Report <--------------------------------------------

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7.3 Stop Sending Event Reports

This inhibition of sending of event reports shall be used by the BSC to prevent a flood of event reports which are of no benefit to the BSC. One example of this occurs at a BTS restart following a power failure. The operational capability of the BTS hardware is unlikely to be different from what it was before the failure, and a flood of reports, each stating that a piece of hardware is operating, will delay the software download. Another example concerns the case of a frequently occurring transient fault. BSC BTS Stop Sending Events Reports --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Sending of specified Event Report has been stopped. Message specific Nack causes (see subclause 9.4.36): None. ETSI 24 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7.4 Restart Sending Event Reports

When the BTS is back in normal operation or if it is of interest to check whether the BTS still generates a flood of Event Reports, a Restart Sending Event Reports shall be sent. BSC BTS Restart Sending Events Reports --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Sending of specified Event Report has been restarted. Message specific Nack causes (see subclause 9.4.36): None.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7.5 Change Administrative State

The Change Administrative State message shall be used by the BSC to change the administrative state (as specified by specification GSM 12.20) of a managed object. BSC BTS Change Administrative State --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified change of administrative state has been performed. Message specific Nack causes (see subclause 9.4.36): None.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7.6 Change Administrative State Request

This request message shall be sent by the BTS when there is a need to change the administrative state of a managed object at the BTS site. This message can only be initiated as a result of a local MMI command. BSC BTS Change Administrative State Request <-------------------------------------------- ACK/NACK --------------------------------------------> Meaning of Ack message: The request is granted and a change administrative state message will be sent. Message specific Nack causes (see subclause 9.4.36): 28, 29.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.7.7 Report Outstanding Alarms

This message shall be used by the BSC to ask BTS to report all outstanding alarms related to the object instance indicated in the message. The BTS shall report alarms by sending a series of Failure Event Report messages for all outstanding alarms. Only those alarms previously reported and still outstanding shall be re-reported through this procedure. Any new alarms not yet reported but about to be reported shall be excluded and they shall be reported through a separate Failure Event Report procedure spontaneously initiated by the BTS itself. If there is no outstanding alarm, the BTS shall reply with a NACK with that cause indicated. BSC BTS Report Outstanding Alarms --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: Sending of Failure Event Report will start. Message specific Nack causes (see subclause 9.4.36): 28, 29, 2A. ETSI 25 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

6.8 Equipment Management Procedures

e59ea8dcad939b2b08179091ad5f515d

100 623

6.8.1 Change-over

This message shall be sent to change over between active and standby units of equipment. The action may be performed on any addressable BTS entity, manufacturer dependent HW units included. Which type of HW unit to address and how to identify certain units of this type of HW are manufacturer dependent. BSC BTS Changeover --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified change-over operation has been performed. Message specific Nack causes (see subclause 9.4.36): 19, 1A, 1E, 23.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.8.2 Opstart

This message shall be sent by the BSC to tell the BTS to attempt to operatethe identified object putting it to an initial normal operational state (i.e., "enabled", see subclause 5.3.2). This message does not affect the object's administrative state if there exists a value explicitly assigned by the BSC. If there is yet no administrative state value explicitly set by the BSC (e.g., at an initialization time), the object shall be presumed to be administratively locked by default. No BTS function is required to be responsible for testing the operability of the identified resource as a consequence of this message. Prior to this message being issued, all necessary physical and logical preparations (such as repair of equipment, software downloading, parameter setting, etc., as needed) are expected to have been completed. If the object is in fact not ready to be in an enabled state, the object will be in a fault condition as a consequence of this message, and the condition shall be handled by the object's normal fault handling function as the condition is detected. BSC BTS Opstart --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The BTS has reset the operational state of the specified object to "enabled" state. Message specific Nack causes (see subclause 9.4.36): 19, 1A, 23.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.8.3 Reinitialize

This message shall be sent by the BSC to tell the BTS to have specified hardware resource of the indicated object start a re-initialization procedure as sketched in figure 2. The specifics of a re-initialization procedure, which typically takes place at the time of a cold start of the resource, is manufacturer-dependent. For a software reinitialization, Activate SW message shall be used. BSC BTS. Reinitialize --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The BTS has received the message and is about to start a reinitialization of the specified resource. Message specific Nack causes (see subclause 9.4.36): 19, 1A, 23. ETSI 26 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

6.8.4 Set Site Outputs

This message shall be sent by the BSC to tell the BTS to set specified site outputs to the specified state. BSC BTS Set Site Outputs --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The outputs have been set. Message specific Nack causes (see subclause 9.4.36): None.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.9 Measurement Management Procedures

e59ea8dcad939b2b08179091ad5f515d

100 623

6.9.1 Measurement Result Request

This message shall be used by the BSC to request the result of a certain measurement which is running in the BTS to be sent to the BSC. After having responded with the current result, the BTS initializes the measurement result buffer (e.g. setting to zero) and continues the measurement. BSC BTS Measurement Result Request --------------------------------------------> Response/NACK <-------------------------------------------- Message specific Nack causes (see subclause 9.4.36): 2A, 2B.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.9.2 Measurement Result Response

This message shall be used by the BTS to successfully respond to the BSC on an associated Measurement Result Request completing a Measurement Result Request elementary procedure. By this message, the presently registered measurement result requested shall be reported. If it is not possible for any reason, a NACK message must be used instead of this.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.9.3 Stop Measurement

This message shall be used by the BSC to stop a continuously running measurement at the BTS. The message must include identification of the measurement to be stopped. BSC BTS Stop Measurement --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified measurement has been stopped Message specific Nack causes (see subclause 9.4.36): 2A ETSI 27 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

6.9.4 Start Measurement

This message shall be used by the BSC to start a measurement continuously at the BTS. The message must include identification of the measurement to be started. BSC BTS Start Measurement --------------------------------------------> ACK/NACK <-------------------------------------------- Meaning of Ack message: The specified measurement has been started Message specific Nack causes (see subclause 9.4.36): 2A

e59ea8dcad939b2b08179091ad5f515d

100 623

6.10 Miscellaneous Procedures

e59ea8dcad939b2b08179091ad5f515d

100 623

6.10.1 Get Attributes

This message shall be used by the BSC to tell the BTS to send attributes which have previously been set by the BTS. It may be used as a check on accuracy and be incorporated into normal procedures, or may be used by the BSC to recover information which it has lost. BSC BTS Get Attributes --------------------------------------------> Response/NACK <-------------------------------------------- Message specific Nack causes (see subclause 9.4.36): None.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.10.2 Set Alarm Threshold

This message shall be used by the BSC to tell the BTS some threshold parameters related to fault thresholds. BSC BTS Set Alarm Threshold --------------------------------------------> ACK/NACK <-------------------------------------------- Message specific Nack causes (see subclause 9.4.36): None.

e59ea8dcad939b2b08179091ad5f515d

100 623

6.10.3 Get Attributes Response

This message shall be used by the BTS to successfully respond to the BSC on an associated Get Attribute elementary procedure. By this message, the presently set values of all requested attributes shall be reported. Otherwise, a NACK message shall be used instead of this.

e59ea8dcad939b2b08179091ad5f515d

100 623

7 Structured Procedures

Applicable structured A-bis procedures are described in GSM 12.22.

e59ea8dcad939b2b08179091ad5f515d

100 623

8 Message Details

The formats of all messages in subclauses 8.3 through 8.11 are described each by a table format illustration with no formal text description provided because of the self-explanatory nature of the illustration. ETSI 28 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.1 Message Categories

This subclause defines the transport format and coding of the four Network. Management message categories sent over the Abis interface. The various message categories may be sent in either direction. In each message, the message discriminator identifies the category and is transmitted first. In a message the octets must be sent in the order shown in the description of the messages. In an octet, bit 1 must be transmitted first. In the following subclauses, M and O denote whether information elements are mandatory or optional.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.1.1 Formatted O&M Messages

The message format and coding of these messages are as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 1 0 0 0 0 0 0 0 Placement Indicator M 1 1) Sequence Number M 1 2) Length Indicator M 1 Binary, 3) O&M Data Field M V 4) NOTE 1: The meanings and codings of the Placement Indicator are: - only: This message is contained within one segment 1 0 0 0 0 0 0 0; - first: The first segment of a multi-segment message 0 1 0 0 0 0 0 0; - middle: A middle segment of a multi-segment message 0 0 1 0 0 0 0 0; - last: The last segment of a multi-segment message 0 0 0 1 0 0 0 0. NOTE 2: This is the sequence number of the segment in the message, modulo 256, starting with 00000000. Thus a single segment message is here coded 00000000. The number can be incremented unlimitedly being wrapped around the modulo to transport very long multi-segment messages. NOTE 3: The Length Indicator gives the length of the O&M data field in the message segment being transported which is less than or equal to 255 octets. This length indicator should not be confused with the actual length of the message at the logical level that may go over multiple segments. This length indicator should not be confused also with attribute value length indicator described in subclause 8.2. NOTE 4: Coding for O&M Data field is found in subclause 8.2 and the following subclauses.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.1.2 MMI Transfer

The message format and coding of these messages are as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 0 1 0 0 0 0 0 0 Placement Indicator M 1 note 1 of subclause 8.1.1 Sequence Number M 1 note 2 of subclause 8.1.1 Length Indicator M 1 Binary, 1) MMI Data Field M V Proprietary NOTE: The Length Indicator gives the length of the MMI data field in the message segment being transported which is less than or equal to 255 octets. See also note 3 of subclause 8.1.1. The protocol for MMI is not covered in this GTS. ETSI 29 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.1.3 TRAU O&M Messages

These messages are required for option (ii) of subclause 4.10.1 of specification GSM 08.60. The message format is as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 0 0 1 0 0 0 0 0 Channel Number M 1 1) Repetition Indicator M 1 2) TRAU O&M Message O 33 3) NOTE 1: The channel number element shall be coded as defined for the octet of the channel number information element of specification GSM 08.58. NOTE 2: The meanings and codings of the Repetition Indicator are: - terminate sending of O&M TRAU frames: 0 0 0 0 0 0 0 1; - repeat sending of O&M TRAU frames every 20 ms until a terminate order is received 0 0 0 0 0 0 1 0; - send O&M TRAU frame once: 0 0 0 0 0 1 0 0. NOTE 3: The TRAU O&M message is not sent when the Repetition Indicator is set to 00000001, but sending of the TRAU O&M message is mandatory otherwise. All 264 bits of the TRAU O&M frame information field are sent unchanged in the 33 octets.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.1.4 Manufacturer-Defined O&M messages

The message format and coding of these messages is as below. INFORMATION ELEMENT M/O LENGTH CODING 8 1 Message Discriminator M 1 0 0 0 1 0 0 0 0 Placement Indicator M 1 note 1 of subclause 8.1.1 Sequence Number M 1 note 2 of subclause 8.1.1 Length Indicator M 1 Binary, 1) ManId Length Indicator M 1 Binary, 2) Manuf. Identifier M V 3) Man-Def O&M Data Field M V Proprietary NOTE 1: The Length Indicator gives the length of the Manufacturer-defined O&M data field in the message segment being transported which is less than or equal to 255 octets. See also note 3 of subclause 8.1.1 NOTE 2: The Length Indicator gives the length of the Manufacturer Identifier field which must be less than or equal to 255 octets. NOTE 3: The Manufacturer Identifier is an octet string of maximally 255 octets. This value, to be appropriately determined by an arrangement between the operator and the manufacturer, may or may not be related to the value of the attribute Manufacturer Id (Attribute Id: 1E) listed in subclause 9.4. Remarks: Since the Data Field of messages of this category is not subject to a GSM standardization, it should be noted that a compliance to messages of this category does not guarrantee an interoperability between different manufacturers.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.2 Structure of Formatted O&M Messages

This subclause provides details of all the formatted O&M messages. In every case when particular header octets provide no usable information at the receiver, they shall be coded all 1's. ETSI 30 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) All fields in the messages are marked with M for Mandatory or O for Optional. This indicates whether the field is mandatory or optional to be contained in a message, and not whether it is mandatory or optional to be used or set for every BTS. This allows to change a single attribute without having to repeat all the attributes not to be changed. The header fields of formatted O&M messages (see below) are always mandatory. The attributes defined for a certain message supported by the BTS implementation are mandatory to be used if not stated otherwise in an explanatory note. The first octet of the formatted O&M messages shall identify the message types. Some messages are replied by an ACK or a NACK response. The replies shall be distinguished by different codings of the message type (the first octet of formatted O&M messages). See subclause 9.1. ACK messages shall return all the attributes in the original message. NACK messages shall add a Nack cause field (two octets) at the end of the message. None of the messages concerned requires all of the capacity available in a Layer 2 segment, so the NACK message will not need a second Layer 2 frame. An ACK to a number of Load Data Segments shall consist of only the header with the 'Load Data Segment Ack' message type. All attributes shall overwrite those defined in an earlier message since start-up or the last restart. Optional attributes provide new information if they have not been defined in an earlier message. The message type and managed object identification are given in the message header as is illustrated below: INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 The Object Class information element shall be filled in with the correct information in accordance with this GTS. The Object Instance information element shall contain three fields: 1) the BTS Number identifies one BTS in a multi cell site; 2) the Baseband Transceiver number or the Radio Carrier number identifies which Baseband Transceiver or Radio Carrier is concerned in the message; 3) the third element identifies a radio timeslot (0-7) of the Baseband Transceiver identified by 2). For further information see subclause 9.3. The FORMAT field describes the structure of each information element using T(Tag), L(Length) and V(Value) coding. T is the attribute identifier. V is the actual information presented. L must be indicated if the the information element is of variable length and its prediction is not possible in the context . L shall binary-represent in a two octet space the the number of octets in the remaining part of information element. Note that this Length code differs from the "Length Indicator" described in subclause 8.1.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3 SW Download Management Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3.1 Load Data Initiate

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 SW Description 9.4.62 M TV >=2 Window Size 9.4.59 M TV 2 ETSI 31 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3.2 Load Data Segment

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 File Data 9.4.17 M (note) TLV >=2 NOTE: File Data is segments of the actual file to be transferred.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3.3 Load Data Abort

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3.4 Load Data End

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 SW Description 9.4.62 M (note) TV >=2 NOTE: The same SW Description as in the corresponding Load Data Initiate message.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3.5 SW Activate Request

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 HW Configuration 9.4.62 M TLV >=2 SW Configuration 9.4.61 M TLV >=2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3.6 Activate SW

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 SW Description 9.4.62 O (note) TV >=2 NOTE: SW Descriptions may be repeated for multiple software activation. No SW Description entry implies all software for the object instance.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.3.7 SW Activated Report

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 ETSI 32 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.4 A-bis Interface Management Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.4.1 Establish TEI

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 TEI 9.4.54 M TV 2 Abis Channel 9.4.1 M TV 4

e59ea8dcad939b2b08179091ad5f515d

100 623

8.4.2 Connect Terrestrial Signalling

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4

e59ea8dcad939b2b08179091ad5f515d

100 623

8.4.3 Disconnect Terrestrial Signalling

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4

e59ea8dcad939b2b08179091ad5f515d

100 623

8.4.4 Connect Terrestrial Traffic

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4 Radio Sub Channel 9.4.46 O TV 2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.4.5 Disconnect Terrestrial Traffic

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Abis Channel 9.4.1 M TV 4 Radio Sub Channel 9.4.46 O TV 2 ETSI 33 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.5 Transmission Management Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.5.1 Connect Multi-drop link

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Multi-drop BSC Link 9.4.34 M (note 1) TV 3 Multi-drop next BTS Link 9.4.35 M (note 2) TV 3 NOTE 1: This attribute specifies the incoming (in BSC direction) 64 kbps timeslot to be set up to another BTS in a multi-drop configuration. NOTE 2: This attribute specifies the outgoing (to the next BTS direction) 64 kbps timeslot to be set up through the BTS in a multi-drop configuration.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.5.2 Disconnect Multi-drop link

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Multi-drop BSC Link 9.4.34 M (note 1) TV 3 Multi-drop next BTS Link 9.4.35 M (note 2) TV 3 NOTE 1: This attribute specifies the incoming (in BSC direction) 64 kbps timeslot to be taken down from another BTS in a multi-drop configuration. NOTE 2: This attribute specifies the outgoing (to the next BTS direction) 64 kbps timeslot to be taken down through the BTS in a multi-drop configuration.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.6 Air Interface Management Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.6.1 Set BTS Attributes

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Interference Level Boundaries 9.4.25 O (note 1) TV 7 Intave Parameter 9.4.24 O TV 2 Connection Failure Criterion 9.4.14 O TLV >=4 T200 9.4.53 O (note 2) TV 8 Max Timing Advance 9.4.31 O (note 3) TV 2 Overload Period 9.4.39 O (note 5) TLV >=2 CCCH Load Threshold 9.4.12 O (notes 4 and 5) TV 2 CCCH Load Indication Period 9.4.11 O (note 5) TV 2 RACH Busy Threshold 9.4.44 O (note 5) TV 2 RACH Load Averaging Slots 9.4.45 O (note 5) TV 3 BTS Air Timer 9.4.10 O TV 2 NY1 9.4.37 O TV 2 BCCH ARFCN 9.4.8 O TV 3 BSIC 9.4.9 O TV 2 Starting Time 9.4.52 O (note 6) TV 3 ETSI 34 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) NOTE 1: Interference Level Boundaries Boundary 0 (see GSM 05.08) Boundary x1 ¦ ¦ Boundary x5 NOTE 2: For FACCH and SACCH. NOTE 3: Optional in BTS design and administration use. NOTE 4: Presentation of the load threshold in 1% steps. NOTE 5: These attributes are special CCCH Parameters NOTE 6: For synchronisation of when the specific action defined in the message shall be performed. Needed only to change BCCH ARFCN or BSIC while in operation.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.6.2 Set Radio Carrier Attributes

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 RF Max Power Reduction 9.4.47 O TV 2 ARFCN list 9.4.5 O (note) TLV >=2 NOTE: The structure of value will vary depending on the mode of frequency hopping supported.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.6.3 Set Channel Attributes

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Channel Combination 9.4.13 O TV 2 HSN 9.4.21 O (note 1) TV 2 MAIO 9.4.27 O (note 1) TV 2 ARFCN list 9.4.5 O (note 2) TLV >=2 Starting Time 9.4.52 O (note 3) TV 3 TSC 9.4.60 O (note 4) TV 2 NOTE 1: Used only in a hopping channel. NOTE 2: If frequency hopping is not in use, the only frequency of the Radio Carrier is set with the message Radio Carrier Attributes. NOTE 3: For synchronisation of when the specific action defined in the message shall be performed. NOTE 4: A NULL value signifies that the BCC shall be used as the TSC value for the channel. ETSI 35 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.7 Test Management Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.7.1 Perform Test

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2 Autonomously Report 9.4.6 M TV 2 Test Duration 9.4.55 O TV 3 Physical Configuration 9.4.40 O (note) TLV >=2 NOTE: Use of Physical Configuration depends on the need on extra information in setting up specific test configurations.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.7.2 Test Report

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2 Test Report Info 9.4.57 M (note) TLV >=2 NOTE: The test report information may give a numerical result or an indication of the range into which the test report falls.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.7.3 Send Test Report

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.7.4 Stop Test

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Test No 9.4.56 M TV 2 ETSI 36 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8 State Management and Event Report Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8.1 State Changed Event Report

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Operational State 9.4.38 O TV 2 Availability Status 9.4.7 O TLV >=2 Man.dep. State 9.4.28 O TV 2 Site Inputs 9.4.48 O TLV >=2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8.2 Failure Event Report

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Event Type 9.4.16 M TV 2 Perceived Severity 9.4.63 M TV 2 Probable Cause 9.4.43 M TV 4 Specific Problems 9.4.51 O (note 1) TV 2 HW Description 9.4.23 O (notes 1 and 2) TV >=2 SW Description 9.4.62 O (notes 1 and 2) TV >=2 Additional Text 9.4.3 O (note 1) TLV >=2 Additional Info 9.4.2 O (note 1) TLV >=2 Outstanding Alarm Sequence 9.4.65 O (note 3) TV 2 NOTE 1: Depending on the nature of the specific failure and the BTS implementation, only the needed and supported attributes shall be sent. NOTE 2: This field shall be included to identify the specific associated equipment or software in case the addressed functional object alone is not sufficient to localize the failure. NOTE 3: This field shall be included if and only if this report is a response to a Report Outstanding Alarms message.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8.3 Stop Sending Event Reports

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Operational State 9.4.38 O (note 1) TV 2 Availability Status 9.4.7 O (note 1) TLV >=2 Manufacturer Dependant State 9.4.28 O (note 1) TV 2 Probable Cause 9.4.43 O (note 1) TV 4 Specific Problems 9.4.51 O (note 1) TV 2 NOTE 1: Stop sending event reports concerning events with any of the parameter values in this attribute list. Depending on the type of event report that shall be stopped, one or some of the attributes shall be sent. The effect of multiple optional attributes in one message is that only those events that satisfy all the attributes simultaneously shall stop. The effect of repeated uses of this message with each different optional attribute is accumulative, thus, is different from the effect of putting all the optional attributes listed together at once in one message. If there occurs any inconsistency or confusion between the conditions for stopping and starting (see subclause 8.8.4), the event shall be reported instead of being stopped. ETSI 37 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) NOTE 2: This message with no optional attributes means that all event reports shall be stopped from now.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8.4 Restart Sending Event Reports

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Operational State 9.4.38 O (note 1) TV 2 Availability Status 9.4.7 O (note 1) TLV >=2 Manufacturer Dependent State 9.4.28 O (note 1) TV 2 Probable Cause 9.4.43 O (note 1) TV 4 Specific Problems 9.4.51 O (note 1) TV 2 NOTE 1: Restart sending event reports concerning events with any of the parameter values in this attribute list. Depending on the type of event report that needs to be restarted, one or some of the attributes shall be sent. The effect of multiple optional attributes is just same as multiple messages repeated with each attribute one by one and events that satisfy any one of the attribute set shall be reported. Note the difference from the condition stated in note 1 of subclause 8.8.3. NOTE 2: This message with no optional attributes means that all event reports shall be started from now.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8.5 Change Administrative State

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Administrative State 9.4.4 M (note) TV 2 NOTE: Required new administrative state for the specified managed object.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8.6 Change Administrative State Request

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Administrative State 9.4.4 M (note) TV 2 NOTE: The requested administrative state for the specified managed object.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.8.7 Report Outstanding Alarms

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 ETSI 38 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.9 Equipment Management Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.9.1 Changeover

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Source 9.4.50 M (note 1) TLV >=2 Destination 9.4.15 M (note 2) TLV >=2 NOTE 1: Source is the manufacturer dependent identity of piece of equipment that shall be taken out of active servicing (changed-over from) and replaced by the Destination. NOTE 2: Destination is the manufacturer dependent identity of piece of equipment that shall be put into active servicing (changed-over to) in place of the Source.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.9.2 Opstart

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3

e59ea8dcad939b2b08179091ad5f515d

100 623

8.9.3 Reinitialize

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 HW Description 9.4.23 O (note) TV >=2 NOTE: HW Descriptions may be repreated for multiple resources. If no HW Description is provided, all resource for the objectis is implied. For a software reinitialization, Activate SW message shall be used.

e59ea8dcad939b2b08179091ad5f515d

100 623

8.9.4 Set Site Outputs

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Site Outputs 9.4.49 M TLV >=2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.9.5 Change HW Configuration

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Site Outputs 9.4.49 M TLV >=2 ETSI 39 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.10 Measurement Management Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.10.1 Measurement Result Request

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.10.2 Measurement Result Response

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2 Measurement Result 9.4.32 M TLV >= 2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.10.3 Start Measurement

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.10.4 Stop Measurement

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Measurement Identifier 9.4.33 M TV 2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.11 Miscellaneous Messages

e59ea8dcad939b2b08179091ad5f515d

100 623

8.11.1 Get Attributes

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 List of Required Attributes 9.4.26 M (note) TLV >=2 NOTE: Any of the attributes defined in subclause 9.4, including those not marked with an X in the GET column, can be requested by Get Attributes message. ETSI 40 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

8.11.2 Set Alarm Threshold

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Probable Cause 9.4.43 M TV 4 Power Output Thresholds 9.4.42 O TV 4 VSWR Thresholds 9.4.58 O TV 3 Manufacturer Dependent Thresholds 9.4.29 O TLV >=2

e59ea8dcad939b2b08179091ad5f515d

100 623

8.11.3 Get Attribute Response

INFORMATION ELEMENT REFERENCE PRESENCE FORMAT LENGTH Message Type 9.1 M V 1 Object Class 9.2 M V 1 Object Instance 9.3 M V 3 Get Attribute Response Info 9.4.64 M TLV >=4

e59ea8dcad939b2b08179091ad5f515d

100 623

9 Coding

This clause defines the coding of each field in the messages defined in earlier clauses. The following conventions are required: - the least significant bit shall be transmitted first, followed by bits 2, 3, 4, etc; - in an element where octets are identified by an octer number, Octet 1 shall be transmitted first, then octet 2, etc; - when a field extends over more than one octet, the order of bit values shall progressively decrease as the octet number increases. The least significant bit of the field shall be represented by the lowest numbered bit of the highest numbered octet of the field; - for unpredictable variable length elements, a length indication coding method defined in subclause 8.2 shall be used. Always the length information shall indicate the number of element units (which is octets) following the length indicator excluding the space for the length findicator itself; - all defined values are indicated in this GTS. Other values are reserved.

e59ea8dcad939b2b08179091ad5f515d

100 623

9.1 Message Type

The Message Type is coded with 1 octet as illustrated below. Message Type 1 The following message types are used (all other values reserved). Message Type hexadecimal code SW Download Management Messages: Load Data Initiate 01 Load Data Initiate Ack 02 Load Data Initiate Nack 03 Load Data Segment 04 ETSI 41 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Load Data Segment Ack 05 Load Data Abort 06 Load Data End 07 Load Data End Ack 08 Load Data End Nack 09 SW Activate Request 0A SW Activate Request Ack 0B SW Activate Request Nack 0C Activate SW 0D Activate SW Ack 0E Activate SW Nack 0F SW Activated Report 10 A-bis Interface Management Messages: Establish TEI 21 Establish TEI Ack 22 Establish TEI Nack 23 Connect Terrestrial Signalling 24 Connect Terrestrial Signalling Ack 25 Connect Terrestrial Signalling Nack 26 Disconnect Terrestrial Signalling 27 Disconnect Terrestrial Signalling Ack 28 Disconnect Terrestrial Signalling Nack 29 Connect Terrestrial Traffic 2A Connect Terrestrial Traffic Ack 2B Connect Terrestrial Traffic Nack 2C Disconnect Terrestrial Traffic 2D Disconnect Terrestrial Traffic Ack 2E Disconnect Terrestrial Traffic Nack 2F Transmission Management Messages: Connect Multi-Drop Link 31 Connect Multi-Drop Link Ack 32 Connect Multi-Drop Link Nack 33 Disconnect Multi-Drop Link 34 Disconnect Multi-Drop Link Ack 35 ETSI 42 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Disconnect Multi-Drop Link Nack 36 Air Interface Management Messages: Set BTS Attributes 41 Set BTS Attributes Ack 42 Set BTS Attributes Nack 43 Set Radio Carrier Attributes 44 Set Radio Carrier Attributes Ack 45 Set Radio Carrier Attributes Nack 46 Set Channel Attributes 47 Set Channel Attributes Ack 48 Set Channel Attributes Nack 49 Test Management Messages: Perform Test 51 Perform Test Ack 52 Perform Test Nack 53 Test Report 54 Send Test Report 55 Send Test Report Ack 56 Send Test Report Nack 57 Stop Test 58 Stop Test Ack 59 Stop Test Nack 5A State Management and Event Report Messages: State Changed Event Report 61 Failure Event Report 62 Stop Sending Event Reports 63 Stop Sending Event Reports Ack 64 Stop Sending Event Reports Nack 65 Restart Sending Event Reports 66 Restart Sending Event Reports Ack 67 Restart Sending Event Reports Nack 68 Change Administrative State 69 Change Administrative State Ack 6A Change Administrative State Nack 6B ETSI 43 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) Change Administrative State Request 6C Change Administrative State Request Ack 6D Change Administrative State Request Nack 6E Report Outstanding Alarms 93 Report Outstanding Alarms Ack 94 Report Outstanding Alarms Nack 95 Equipment Management Messages: Changeover 71 Changeover Ack 72 Changeover Nack 73 Opstart 74 Opstart Ack 75 Opstart Nack 76 Reinitialize 87 Reinitialize Ack 88 Reinitialize Nack 89 Set Site Outputs 77 Set Site Outputs Ack 78 Set Site Outputs Nack 79 Change HW Configuration 90 Change HW Configuration Ack 91 Change HW Configuration Nack 92 Measurement Management Messages: Measurement Result Request 8A Measurement Result Response 8B Stop Measurement 8C Start Measurement 8D Other Messages: Get Attributes 81 Get Attributes Response 82 Get Attributes Nack 83 Set Alarm Threshold 84 Set Alarm Threshold Ack 85 Set Alarm Threshold Nack 86 ETSI 44 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

9.2 Object Class

An Object Class shall be coded with 1 octet. The values of the object class code are as defined below. Object Class 1 Object Class hexadecimal code Site Manager 00 BTS 01 Radio Carrier 02 Baseband Transceiver 04 Channel 03 <reserved for future use> <05-FE> NULL FF

e59ea8dcad939b2b08179091ad5f515d

100 623

9.3 Object Instance

The Object Instance shall be coded with 3 octets, addressing the specific object of the given object class as illustrated below. BTS number 1 Baseband Transceiver or Radio Carrier number 2 Radio Timeslot number 3 All 3 octets are mandatory in the header of every message. The BTS number distinguishes BTSs which are unique for each cells at a site under the Site Manager. The Baseband Transceiver or Radio Carrier number distinguishes either Baseband Transceivers or Radio Carriers under the BTS. The Radio Timeslot number distinguishes channels under the Baseband Transceiver. When the object class is Site Manager, all three octets shall be NULLs, because there is only one Site Manager, which doesn't need an identifier. When the object class is BTS, octet 1 shall be a binary presentation of the identifier of the addressed BTS. Octets 2 and 3 shall be coded NULLs. If the BTS number is NULL, it shall be understood as referring to all BTSs under the Site Manager. When the object class is Baseband Transceiver or Radio Carrier, octet 2 shall be a binary presentation of the identifier of the addressed Baseband Transceiver or Radio Carrier object, and octet 1 is the identiferrof the BTS above it. Octet 3 is coded NULL. If the Baseband Transceiver or Radio Carrier number is NULL, it shall be understood as referring to all instances of the class under the BTS. When the object class is Channel, octet 3 shall be a binary presentation of the identifier of the addressed radio timeslot, octet 2 shall be the identifier of the Baseband Transceiver, and octet 1 shall be the identifer of the BTS above the addressed Channel. If the radio timeslot number is NULL, it shall be understood as referring to all Channels under the Baseband Transceiver. To avoid unnecessary complexity of BTS implementation, it shall not be allowed to assign a NULL value to any object above the addressed object class. For example, if the addressed object class is the Baseband Transceiver, it is not allowed to assign a NULL value to both BTS and Baseband Transceiver instances (without this constraint, this could be understood as referring to all the Baseband Transceivers of all the BTSs). ETSI 45 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) The value for NULL shall be <FF> in all the cases mentioned above in this subclause.

e59ea8dcad939b2b08179091ad5f515d

100 623

9.4 Attributes and Parameters

The Attribute Identifier is coded with 1 octet. The number of parameters within an attribute is at least one. The length of the parameters within an attribute will vary. The attributes used and the coding of their Attribute Identifier fields are listed below. The values are in hexadecimal. The attributes marked with an X in “Get” column are only getable by the BSC, and BSC is not permitted to alter their values. Attribute Name Attribute Id. Get Abis Channel 01 X Additional Info 02 Additional Text 03 Administrative State 04 X ARFCN List 05 X Autonomously Report 06 Availability Status 07 X BCCH ARFCN 08 X BSIC 09 X BTS Air Timer 0A X CCCH Load Indication Period 0B X CCCH Load Threshold 0C X Channel Combination 0D X Connection Failure Criterion 0E X Destination 0F Event Type 11 File Data 47 File Id 12 X File Version 13 X GSM Time 14 X Get Attribute Response Info 44 HSN 15 X HW Configuration 16 X HW Conf Change Info 45 HW Description 17 X Intave Parameter 18 X Interference Level Boundaries 19 X List of Required Attributes 1A ETSI 46 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) MAIO 1B X Manufacturer Dependent State 1C X Manufacturer Dependent Thresholds 1D X Manufacturer Id 1E X Max Timing Advance 1F X Multi-drop BSC Link 20 Multi-drop next BTS Link 21 Nack Causes 22 Ny1 23 X Operational State 24 X Outstanding Alarm Sequence 46 Overload Period 25 X Physical Config 26 Power Class 27 X Power Output Thresholds 28 X Probable Cause 29 RACH Busy Threshold 2A X RACH Load Averaging Slots 2B X Radio Sub Channel 2C RF Max Power Reduction 2D X Site Inputs 2E X Site Outputs 2F X Source 30 Specific Problems 31 Starting Time 32 T200 33 X TEI 34 X Test Duration 35 Test No 36 Test Report Info 37 VSWR Thresholds 38 X Window Size 39 TSC 40 X SW Configuration 41 X ETSI 47 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996) SW Description 42 X Perceived Severity 43 Measurement Result 48 Measurement Type 49 All other values are reserved for future use. The data structures of the attributes and parameters are described in the remaining part of this subclause in tablular forms with no formal text description of the individual subclauses provided because of their self-explanatory nature. Henceforth "Attribute Identifier" in this subclause means the identifier for an attribute or a parameter.

e59ea8dcad939b2b08179091ad5f515d

100 623

9.4.1 Abis Channel

Attribute Identifier 1 BTS Port Number 2 Timeslot Number 3 Subslot Number 4 BTS Port Number <0-FF> Timeslot Number Time slot in 2 Mbps link <0-1F> Subslot Number a (bits 1,2) 00 b (bits 3,4) 01 c (bits 5,6) 02 d (bits 7,8) 03 64 kbps signalling FF

e59ea8dcad939b2b08179091ad5f515d

100 623

9.4.2 Additional Info

Attribute Identifier 1 Length 2-3 Additional Info <man.dep.> 4 (cont.) (cont.) N Additional Info is a manufacturer dependent field.

e59ea8dcad939b2b08179091ad5f515d

100 623

9.4.3 Additional Text

Attribute Identifier 1 Length 2-3 Additional Text <man.dep.> 4 (cont.) (cont.) N Additional Text is a manufacturer dependent field and shall be used to include fault localization information. ETSI 48 ETSI TS 100 623 V5.0.0 (2000-05) (GSM 12.21 version 5.0.0 Release 1996)

e59ea8dcad939b2b08179091ad5f515d

100 623

9.4.4 Administrative State

Attribute Identifier 1 Administrative State 2 Administrative State shall be coded as follows: Locked 01 Unlocked 02 Shutting Down 03 NULL (Adm. state not supported) FF

e59ea8dcad939b2b08179091ad5f515d

100 623

9.4.5 ARFCN List

Attribute Identifier 1 Length 2-3 ARFCN1 (MSB) 4 ARFCN1 (LSB) 5 ARFCNn (MSB) N-1 ARFCNn (LSB) N ARFCN (see GSM 05.05) <0-3FF>

e59ea8dcad939b2b08179091ad5f515d

100 623

9.4.6 Autonomously Report

Attribute Identifier 1 Autonomously Report 2 The toggle switch for autonomous report shall be coded as follows: Autonomously Report 01; Not Autonomously Report 00.