8 Message Details

12.213GPPNetwork Management (NM) procedures and messages on the A-bis interfaceRelease 1998TS

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.

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.

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.

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 the present document.

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.

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.

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.

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 the present document.

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.

8.3 SW Download Management Messages

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

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.

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

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.

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

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.

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

8.4 A‑bis Interface Management Messages

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

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

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

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

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

8.5 Transmission Management Messages

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.

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.

8.6 Air Interface Management Messages

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

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.

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.

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.

8.7 Test Management Messages

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.

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.

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

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

8.8 State Management and Event Report Messages

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

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.

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.

NOTE 2: This message with no optional attributes means that all event reports shall be stopped from now.

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.

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.

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.

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

8.9 Equipment Management Messages

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.

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

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.

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

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

8.10 Measurement Management Messages

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

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

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

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

8.11 Miscellaneous Messages

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.

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

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