A.1 LMU Messages

12.713GPPLocation Services (LCS)Location services managementTS

Messages in this clause have been provided for information only. When there is a discrepancy between this clause and the ASN.1 code, the ASN.1 code takes precedence.

A.1.1 Message Details

The formats of all messages in Subclauses 7.1.2.2 through 7.1.2.8 are each described by a table format illustration. No formal text description has been provided, because of the self-explanatory nature of the illustrations. ASN.1 coding does not require bit-level definitions. The following clauses show bit-level coding for informational purposes only.

A.1.1.1 Message Categories

This clause defines the transport format and coding of the two Network Management message categories sent over the LMU-SMLC 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 the following clauses, M and O denote whether information elements are mandatory or optional. V indicates that the length is different for each message.

A.1.1.1.1 Formatted O&M Messages

LCS O&M is transported using the container messages specified in 04.71 [9]. ASN.1 coding does not require bit-level definition of the DTAP messages. However, clauses of 12.21 [5] have been included here to show how bit-level coding is performed on the Abis interface.

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 coded here as 00000000. The number can be incremented without limit by 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 with attribute value length indicator described in Subclause A.1.1.1.3.

NOTE 4: Coding for O&M Data field is found in Subclause A.1.1.1.3 and the following clauses.

A.1.1.1.2 Manufacturer-Defined O&M messages

LCS O&M is transported using the container messages specified in 04.71 [9]. ASN.1 coding does not require bit-level definition of the DTAP messages. However, clauses of 12.21 [5] have been included here to show how bit-level coding is performed on the Abis interface.

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 A.1.1.1.1

Sequence Number

M

1

Note 2 of Subclause A.1.1.1.1

Length Indicator

M

1

Binary, 1)

Man. ID Length Indicator

M

1

Binary, 2)

Man. ID

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 A.1.1.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 A.1.2.4.

Remarks: Since the Data Field of messages of this category is not subject to a GSM standardisation, it should be noted that a compliance to messages of this category does not guarantee an interoperability between different manufacturers.

A.1.1.1.3 Structure of Formatted O&M Messages

This clause 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 LMU. This allows changing 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 LMU 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 A.1.2.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 require 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 startup or the last restart. Optional attributes provide new information if they have not been defined in an earlier message.

The message type and managed entity identification are given in the message header as is illustrated below:

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

The Managed Entity Class information element shall be filled in with the correct information in accordance with the present document.

The Managed Entity Instance information element shall contain three fields:

1) The LMU Number identifies one LMU in a multi cell site.

2) The First Tier number identifies which Uplink Timing Estimator, Downlink Timing Estimator, or Network Transceiver is concerned in the message.

3) The third element is provided for future use.

For further information see Subclause A.1.2.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 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 number of octets in the remaining part of the information element. Note that this Length code differs from the "Length Indicator" described in Subclause A.1.1.1.

A.1.1.2 SW Download Management Messages

A.1.1.2.1 Load Data Initiate (No CMIP [13] equivalent)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

SW Description

A.1.2.4.41

M

TV

>=2

Window Size

A.1.2.4.49

M

TV

2

Number of Segments

A.1.2.4.26

M

TV

1

A.1.1.2.2 Load Data Segment (No CMIP equivalent)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Sequence Number

M 1)

V

1

File Data

A.1.2.4.13

M 2)

TLV

>=2

NOTE 1: The Sequence Number is incremented for each data segment and rolls over from 255 to 0.

NOTE 2: File Data is individual segments of the actual file to be transferred.

A.1.1.2.3 Load Data Abort (No CMIP equivalent)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

NOTE: The LLP invoke ID will be used to associate segmented messages. One logical message will have one invoke ID regardless of how many segments it is spread over.

A.1.1.2.4 Load Data End (No CMIP equivalent)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

NOTE: The LMU must maintain a counter and send an ACK when all the data has been received.

A.1.1.2.5 SW Activate Request (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

HW Configuration

A.1.2.4.16

M

TLV

>=2

SW Configuration

A.1.2.4.40

M

TLV

>=2

A.1.1.2.6 Activate SW (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

SW Description

A.1.2.4.41

O 1)

TV

>=2

NOTE 1: SW Descriptions may be repeated for multiple software activation. No SW Description entry implies all software for the managed entity instance.

A.1.1.2.7 SW Activated Report (Compare M-Event-Report)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Result

A.1.2.4.33

M

V

1

A.1.1.3 Test Management Messages

A.1.1.3.1 Perform Test (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Test Number

A.1.2.4.43

M

TV

2

Autonomously Report

A.1.2.4.6

M

TV

1

Test Duration

A.1.2.4.42

O

TV

3

Physical Configuration

A.1.2.4.30

O 1)

TLV

>=2

NOTE 1: Use of Physical Configuration depends on the need for extra information in setting up specific test configurations.

A.1.1.3.2 Test Report (Compare M-Event-Report)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Test Number

A.1.2.4.43

M

TV

2

Test Report Info

A.1.2.4.44

M 1)

TLV

>=2

NOTE 1: The test report information may give a numerical result or an indication of the range (e.g. pass/fail) into which the test report falls.

A.1.1.3.3 Send Test Report (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Test Number

A.1.2.4.43

M

TV

2

A.1.1.3.4 Stop Test (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Test Number

A.1.2.4.43

M

TV

2

A.1.1.4 State Management Messages

A.1.1.4.1 State Changed Event Report (Compare M-Event-Report)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Operational State

A.1.2.4.27

O

TV

2

Availability Status

A.1.2.4.7

O

TLV

>=2

Manufacturer Dependent State

A.1.2.4.21

O 1)

TLV

>=3

NOTE 1: Use of Manufacturer Dependent State depends on the need for extra information on the state change.

A.1.1.4.2 Change Administrative State (Compare M-Set)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Administrative State

A.1.2.4.3

M 1)

TV

2

NOTE 1: Required new administrative state for the specified managed entity.

A.1.1.4.3 Change Administrative State Request (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Administrative State

A.1.2.4.3

M 1)

TV

2

NOTE 1: The requested administrative state for the specified managed entity.

A.1.1.5 Event Report Messages

A.1.1.5.1 Failure Event Report (Compare M-Event-Report)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Event Type

A.1.2.4.12

M

TV

2

Perceived Severity

A.1.2.4.29

M

TV

2

Probable Cause

A.1.2.4.31

M

TV

4

Event Time

A.1.2.4.11

O

TV

2

Specific Problems

A.1.2.4.39

O 1)

TV

2

HW Description

A.1.2.4.17

O 1) 2)

TV

>=2

SW Description

A.1.2.4.41

O 1) 2)

TV

>=2

Additional Text

A.1.2.4.2

O 1)

TLV

>=2

Additional Info

A.1.2.4.1

O 1)

TLV

>=2

Outstanding Alarm Sequence

A.1.2.4.28

O 3)

TV

1

NOTE 1: Depending on the nature of the specific failure and the LMU 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 managed entity alone is not sufficient to localise the failure.

NOTE 3: This field shall be included if and only if this report is a response to a Report Outstanding Alarms message.

A.1.1.5.2 Stop Sending Event Reports (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

EventType

A.1.2.4.12

O 1)

TV

2

Perceived Severity

A.1.2.4.29

O 1)

TV

2

Probable Cause

A.1.2.4.31

O 1)

TV

4

Specific Problems

A.1.2.4.39

O 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 A.1.1.5.3), the event shall be reported instead of being stopped.

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

A.1.1.5.3 Restart Sending Event Reports (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

EventType

A.1.2.4.12

O 1)

TV

2

Availability Status

A.1.2.4.7

O 1)

TLV

>=2

Perceived Severity

A.1.2.4.29

O 1)

TV

2

Probable Cause

A.1.2.4.31

O 1)

TV

4

Specific Problems

A.1.2.4.39

O 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 the 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 A.1.1.5.2.

NOTE 2: This message with no optional attributes means that all event reports of this event type shall be started from now.

A.1.1.5.4 Report Outstanding Alarms (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

A.1.1.6 Equipment Management Messages

A.1.1.6.1 Change-over (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Source

A.1.2.4.38

M 1)

TLV

>=2

Destination

A.1.2.4.9

M 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.

A.1.1.6.2 Opstart (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

A.1.1.6.3 Reinitialise (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

HW Description

A.1.2.4.17

O 1)

TV

>=2

NOTE 1: HW Descriptions may be repeated for multiple resources. If no HW Description is provided, all resources for the managed entity is implied. For a software reinitialisation, Activate SW message shall be used.

A.1.1.7 General Management Messages

A.1.1.7.1 Set Attributes (Compare M-Set)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Length

M

V

1

Attributes ID

A.1.2.4

M

TLV

1

Value

A.1.2.4

M

TLV

>=2

Attributes ID

A.1.2.4

M

TLV

1

Value

A.1.2.4

M

TLV

>=2

(cont.)

(cont.)

A.1.1.7.2 Get Attributes (Compare M-Get)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

List Attributes

A.1.2.4

M

TLV

>=2

A.1.1.7.3 Set Alarm Threshold (No CMIP equivalent)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Probable Cause

A.1.2.4.31

M

TV

4

Manufacturer-Dependent Thresholds

A.1.2.4.22

O

TLV

>=2

A.1.1.8 Report Messages

A.1.1.8.1 GPS Parameter Report (Compare M-Event-Report)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

Pseudo-range

A.1.2.4.32

M

TLV

>=2

Time of Fix

A.1.2.4.46

M

TV

4

Satellite Info

A.1.2.4.34

M

TLV

>=2

A.1.1.8.2 GPS Parameter Request (Compare M-Action)

INFORMATION ELEMENT

REFERENCE

PRESENCE

FORMAT

LENGTH

Message Type

A.1.2.1

M

V

1

Managed Entity Class

A.1.2.2

M

V

1

Managed Entity Instance

A.1.2.3

M

V

3

A.1.2 Coding

This clause defines the bit-level 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 octet 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 A.1.1.1.3 shall be used. The length information shall always indicate the number of element units (which is octets) following the length indicator excluding the space for the length indicator itself.

– All defined values are indicated in the present document. Other values are reserved.

A.1.2.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).

NOTE: Codes do not match the ASN.1 code

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

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

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 Messages:

State Changed Event Report 61

Change Administrative State 69

Change Administrative State ACK 6A

Change Administrative State NACK 6B

Change Administrative State Request 6C

Change Administrative State Request ACK 6D

Change Administrative State Request NACK 6E

Event Report Messages:

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

Report Outstanding Alarms 93

Report Outstanding Alarms ACK 94

Report Outstanding Alarms NACK 95

Equipment Management Messages:

Change-over 71

Change-over ACK 72

Change-over NACK 73

Opstart 74

Opstart ACK 75

Opstart NACK 76

Reinitialise 87

Reinitialise ACK 88

Reinitialise NACK 89

General Messages:

Set Attributes 77

Set Attributes ACK 78

Set Attributes NACK 79

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

Report Messages:

GPS Parameter Report 87

GPS Parameter Report ACK 88

GPS Parameter Report NACK 89

GPS Parameter Request 90

A.1.2.2 Managed Entity Class

An Managed Entity Class shall be coded with 1 octet. The values of the managed entity class code are as defined below:

Managed Entity Class

Managed Entity Class Hexadecimal Code

LMU 01

Uplink Timing Estimator 02

Downlink Timing Estimator 03

Network Transceiver 04

<reserved for future use> <05-FE>

NULL FF

A.1.2.3 Managed Entity Instance

The Managed Entity Instance shall be coded with 3 octets, addressing the specific managed entity of the given managed entity class as illustrated below:

LMU number

1-2

Second Tier number

3

All 3 octets are mandatory in the header of every message.

The LMU number distinguishes multiple LMUs at the same cell site.

The Second Tier number distinguishes functional managed entities at the second level under the LMU.

A Third Tier number may be used in the future to distinguish functional managed entities at the third level.

When the managed entity class is LMU, octets 1-2 shall be a binary presentation of the identifier of the addressed LMU. Octets 3 shall be coded NULL. If the LMU number is NULL, it shall be understood as referring to all LMUs at the site.

When the managed entity class is a function on the second tier, octet 3 shall be a binary presentation of the identifier of the addressed second-tier managed entity, and octet 1 is the identifier of the LMU above it. If the Second Tier number is NULL, it shall be understood as referring to all instances of the class under the LMU.

To avoid unnecessary complexity of LMU implementation, it shall not be allowed to assign a NULL value to any managed entity above the addressed managed entity. For example, if the addressed managed entity is Uplink Timing Estimator, it is not allowed to assign a NULL value to both LMU and Uplink Timing Estimator instances. (Without this constraint, this could be understood as referring to all the Uplink Timing Estimators of all the LMUs).

The value for NULL shall be <FF> in all the cases mentioned above in this Subclause.

A.1.2.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.

Attribute Name Attribute ID

Administrative State 01

Attenuator Enable 02

Autonomous Swap 03

Availability Status 04

Calibration Required 05

Diversity 06

HW Configuration 07

Manufacturer ID 08

Method 09

LMU Position 0A

Operational State 0B

Self Position Capability 0C

Set Own Position Upon Startup 0D

Software Download Capability 0E

Software Configuration 0F

Time 10

Timing Type 11

Type 12

All other values are reserved for future use.

The data structures of the attributes and parameters are described in the remaining part of this clause in tabular forms with no formal text description of the individual clauses provided because of their self-explanatory nature.

Henceforth "Attribute Identifier" in this clause means the identifier for an attribute or a parameter.

A.1.2.4.1 Additional Info

Attribute Identifier

1

Length

2-3

Additional Info <man.dep.>

4

(cont.)

(cont.)

N

Additional Info is a manufacturer-dependent field.

A.1.2.4.2 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 localisation information.

A.1.2.4.3 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

A.1.2.4.4 Attenuator Enable

Attribute Identifier

1

Attenuator Enable

2

The toggle switch for Attenuator Enable shall be coded as follows:

Attenuator Disable 00

Attenuator Enable 01

A.1.2.4.5 Autonomous Swap

Attribute Identifier

1

Autonomous Swap

2

The toggle switch for Autonomous Swap shall be coded as follows:

Swap on command 00

Autonomously swap 01

This attribute enables three options for download software swapping:

 Swap on command:

 The OSS directly controls swap by disabling autonomous swap and commanding a swap.

 Autonomously swap:

 The LMU performs download status check and then swaps when there are no measurements pending.

 The OSS indirectly controls swap by using restart, discontinuing further measurement assignments, or continuing measurements.

A.1.2.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

NOTE: Autonomous reports may occur multiple times during the period specified by duration to support recurring tests reporting at the completion of each test cycle.

A.1.2.4.7 Availability Status

Attribute Identifier

1

Length

2-3

Availability Status

4

(cont.)

(cont.)

N

Availability Status may contain one or more octets. Each octet shall have a single status value, which shall be coded as follows:

In test 01

Failed 02

Power off 03

Off line 04

<not used> 05

Dependency 06

Degraded 07

Not installed 08

A.1.2.4.8 Calibration Required

Attribute Identifier

1

Calibration Required

2

Calibration Required shall be coded as follows:

Calibration not required 00

Calibration required 01

A.1.2.4.9 Destination

Attribute Identifier

1

Length

2-3

Destination

4

(cont.)

(cont.)

N

Destination identifies a unit of equipment that shall be the destination to be "changed to" on a Change-over operation. How to identify a type of equipment and how to identify a specific unit of this type is manufacturer-dependent.

A.1.2.4.10 Diversity

Attribute Identifier

1

Diversity

2

Diversity shall be coded as follows:

No Diversity 00

Diversity 01

A.1.2.4.11 Event Time

Attribute Identifier

1

Event Time

2-3

Event Time is taken from the Time attribute.

A.1.2.4.12 Event Type

Attribute Identifier

1

Event Type

2

Event Type shall be coded as follows:

communication failure 01

quality of service failure 02

processing failure 03

equipment failure 04

environment failure 05

<reserved for future use> <06-0F>

<man.dep.> <10-FF>

A.1.2.4.13 File Data

Attribute Identifier

1

Length

2

File Data <man.dep.>

3

(cont.)

(cont.)

N

File Data is manufacturer-dependent, but must be consistent with the associated GSM 12.20 attribute.

A.1.2.4.14 File Id

Attribute Identifier

1

Length

2

File Id <man.dep.>

3

(cont.)

(cont.)

N

File Id is manufacturer-dependent, but must be consistent with the associated GSM 12.20 attribute.

A.1.2.4.15 File Version

Attribute Identifier

1

Length

2

File Version <man.dep.>

3

(cont.)

(cont.)

N

File Version is manufacturer-dependent, but must be consistent with the associated GSM 12.20 attribute.

A.1.2.4.16 HW Configuration

Attribute Identifier

1

Length

2

HW Description 1

3

HW Description n

N

HW Configuration shall consist of a list of HW Descriptions related to a managed entity.

A.1.2.4.17 HW Description

Attribute Identifier

1

Equipment Id Length

2

Equipment Id

(cont.)

Equipment Type Length

Equipment Type

(cont.)

Equipment Version Length

Equipment Version

(cont.)

Location Length

Location

(cont.)

Man. Dep. Info Length

Man. Dep. Info

(cont.)

N

All fields are manufacturer-dependent variable length character strings. They must be consistent with associated GSM 12.20 attributes.

Equipment Id distinguishes a piece of equipment from others of same type.

Equipment Type codes the type of piece of equipment (e.g., Baseband Transceiver Unit).

Equipment Version codes the version of the piece of equipment.

Location codes the place where the piece of equipment is found (e.g., row -rack – shelf – slot).

Man. Dep. Info codes additional manufacturer-dependent information.

A.1.2.4.18 Latitude

Attribute Identifier

1

Degrees

2

Minutes

3

Fractional Minutes

4-5

Direction

6

Latitude follows the format of DDMM.mmmm and use the following ranges:

Degrees 0 to 90

Minutes 0 to 59

Fractional Minutes 0 to 9999

Direction North – 00, South – 01

A.1.2.4.19 LMU Position

Attribute Identifier

1

Latitude

2-7

Longitude

8-13

Altitude

14-15

Altitude shall be coded as 1.5 micro-meters from mean sea level.

A.1.2.4.20 Longitude

Attribute Identifier

1

Degrees

2

Minutes

3

Fractional Minutes

4-5

Direction

6

Latitude follows the format of DDMM.mmmm and use the following ranges:

Degrees 0 to 1800

Minutes 0 to 59

Fractional Minutes 0 to 9999

Direction East – 00, West – 01

A.1.2.4.21 Manufacturer-Dependent State

Attribute Identifier

1

Manufacturer-Dependent State

2

The content of Manufacturer-Dependent State is manufacturer-dependent.

A.1.2.4.22 Manufacturer-Dependent Thresholds

Attribute Identifier

1

Length

2

Manufacturer-Dependent ID

3

Manufacturer-Dependent Thresholds

4

(cont.)

(cont.)

N

The content of Manufacturer-Dependent Thresholds is manufacturer-dependent.

A.1.2.4.23 Manufacturer Id

Attribute Identifier

1

Length

2

Manufacturer Id

3

(cont.)

(cont.)

N

The content of Manufacturer Id is manufacturer-dependent.

A.1.2.4.24 Method

Attribute Identifier

1

Method

2

Method is coded as a bit string with the bits indicated below:

TOA Bit 1

E-OTD Bit 2

A-GPS Bit 3

A zero indicates that the capability is not supported. A one indicates that the capability is supported.

A.1.2.4.25 NACK Causes

Attribute Identifier

1

NACK Cause

2

NACK Causes shall be coded as follows:

General NACK Causes:

Incorrect message structure 01

Invalid message type value 02

<reserved> <03-04>

Invalid managed entity class value 05

Managed entity class not supported 06

LMU number unknown 07

Baseband transceiver number. unknown 08

Managed entity instance unknown 09

<reserved> <0A-0B>

Invalid attribute identifier value 0C

Attribute identifier not supported 0D

Parameter value outside permitted range 0E

Inconsistency in attribute list 0F 1)

Specified implementation not supported 10

Message cannot be performed 11 2)

<reserved> <12-18>

Specific NACK Causes:

Resource not implemented 19

Resource not available 1A

Frequency not available 1B

Test not supported 1C

Capacity restrictions 1D

Physical configuration cannot be performed 1E

Test not initiated 1F

Physical configuration cannot be restored 20

No such test 21

Test cannot be stopped 22

Message inconsistent with physical config. 23 3)

Unable to receive file 24

Complete file not received 25

File not available at destination 26

File cannot be activated 27

Request not granted 28

Wait 29

Not all segment messages received successfully 2A

Window Size Too Large 2B

Duplicate Sequence Number 2C

Missing Sequence Number 2D

<reserved> <2E-7F>

<man.dep.> <80-FE>

NULL FF

NOTE 1: This NACK cause shall apply to conflicting or incomplete data in the attribute list which prevents the LMU from performing the message.

NOTE 2: This NACK cause shall apply when the message is valid and is supported by the LMU, but cannot be performed correctly for reasons not covered by other general or special NACK causes.

NOTE 3: This NACK cause shall apply to the case where the data in attribute list is valid, but is beyond the capabilities of the particular LMU implementation.

A.1.2.4.26 Number of Segments

Attribute Identifier

1

Number of Segments

2-3

Number of Segments is the binary representation of the number of segments contained in the overall file to be sent. This parameter is necessary for determining when to send the final ACK.

A.1.2.4.27 Operational State

Attribute Identifier

1

Operational State

2

Operational States are in accordance with GSM 12.20 and shall be coded as follows:

Disabled 01

Enabled 02

<reserved for future use> <03-FE>

NULL(Operat. state not supported) FF

A.1.2.4.28 Outstanding Alarm Sequence

Attribute Identifier

1

Pending Reports

2

The integer coded Pending Reports field indicates the number of pending Failure Event Report messages to follow the current message as a response to the associated Report Outstanding Alarms message. The value being 0 signals that it is the last message for the outstanding alarms.

A.1.2.4.29 Perceived Severity

Attribute Identifier

1

Severity Value

2

Severity Value shall be coded as follows:

failure ceased 01

critical failure 02

major failure 03

minor failure 04

warning level failure 05

indeterminate failure 06

<reserved> <07-3F>

<man, dep.> <40-FF>

A.1.2.4.30 Physical Configuration

Attribute Identifier

1

Length

2

Required Test Config <man.dep.>

3

(cont.)

(cont.)

N

Required Test Config is manufacturer-dependent.

A.1.2.4.31 Probable Cause

Attribute Identifier

1

Probable Cause Type

2

Probable Cause Value

3

Probable Cause Value (cont.)

4

Probable Cause Type shall be coded as follows:

ISO/CCITT values (X.721) 01

GSM specific values 02

Manufacturer specific values 03

<reserved for future use> <04-FF>

For Probable Cause Value coding, the last numeric value of the managed entity identifier value specified in ASN.1 syntax coding shall be used if Probable Cause Type is either 01 or 02. (This will be eliminated when ASN.1 coding is performed).

A.1.2.4.32 Pseudo-range

Attribute Identifier

1

Kilometres

2-4

Fractional Kilometres

5-7

Pseudo-range is coded as KKKKK.kkkkk.

A.1.2.4.33 Result

Attribute Identifier

1

Result

2

Result is coded as follows:

Failure 0

Success 1

A.1.2.4.34 Satellite Info

Attribute Identifier

1

Length

2

Satellite ID

3

(cont.)

(cont.)

N

Satellite ID is one octet.

A.1.2.4.35 Self-Position Capability

Attribute Identifier

1

Self-Position Capability

2

Self-Position Capability shall be coded as follows:

Incapable of Self-Position 00

Capable of Self-Position 01

A.1.2.4.36 Set Own Position Upon Startup

Attribute Identifier

1

Set Own Position Upon Startup

2

Set Own Position Upon Startup shall be coded as follows:

Do Not Set Own Position 00

Set Own Position 01

NOTE: If the LMU contains a GPS receiver, the LMU may provide its own position. GPS timing may be improved if a more accurate position is provided to the GPS receiver than that which it can derive by itself. This more accurate position can be provided by a survey or by applying differential corrections to the initial measured position.

Since GPS may be available in the LMU for deriving LMU position, there must be flexibility for determining how LMU position is set. There must be the capability to request derivation of a new LMU position and send this new LMU position to the SMLC. There must be the possibility during the LMU position derivation process to update or leave unchanged the LMU position stored in the LMU. (The reason for this is that the LMU may not be able to derive its position directly, but may require differential correction by the SMLC.) The SMLC must have the capability to directly set the LMU position stored in the LMU. The SMLC must also be able to read the current LMU position stored in the LMU.

These capabilities are supported by this attribute.

A.1.2.4.37 Software Download Capability

Attribute Identifier

1

Software Download Capability

2

Software Download Capability shall be coded as follows:

No Software Download Capability 00

Software Download Capability 01

A.1.2.4.38 Source

Attribute Identifier

1

Length

2

Source

3

(cont.)

(cont.)

N

Source identifies a unit of equipment that shall be "changed from" on a Change-over operation. How to identify a type of equipment and how to identify a specific unit of this type is manufacturer-dependent.

A.1.2.4.39 Specific Problems

Attribute Identifier

1

Specific Problems

2

Specific Problems shall be coded as follows:

<reserved for future use> <00-0F>

<man.dep.> <10-FF>

A.1.2.4.40 SW Configuration

Attribute Identifier

1

Length

2

SW Description 1

SW Description n

N

SW Configuration shall contain a list of SW Descriptions related to the managed entity.

A.1.2.4.41 SW Description

Attribute Identifier

1

File Id

2

File Version

N

A.1.2.4.42 Test Duration

Attribute Identifier

1

Test Duration

2-4

Test Duration shall be a binary presentation of seconds in range <01-FFFF> indicating the time the test should last.

A.1.2.4.43 Test Number

Attribute Identifier

1

Test Number

2

Test Number shall be coded as follows:

LMU functional managed entity self test 00

<reserved> <01-3F>

<man.dep.> <40-FE>

<all tests associated with the managed entity> <FF>

A.1.2.4.44 Test Report Info

Attribute Identifier

1

Length

2-3

Test Result Info

4

(cont.)

(cont.)

N

If the test was LMU functional managed entity self test, octet 4 shall indicate pass or fail for the test of the functional managed entity on the LMU by value 1 or 0 where 0 is the code for fail.

In the defined test cases Test Result Info may also contain manufacturer-dependent information in subsequent octets. In other tests, Test Result Info is manufacturer-dependent.

A.1.2.4.45 Time

Attribute Identifier

1

Time

2-4

Time is elapsed time in seconds modulo 86400.

A.1.2.4.46 Time of Fix

Attribute Identifier

1

Time of Fix

2-4

Time of Fix shall be coded as GPS time in seconds modulo 604800.

A.1.2.4.47 Timing Source

Attribute Identifier

1

Timing Source

2

Timing Source shall be coded as:

GPS 00

GSM 01

GLONASS 02

Internal Clock 03

Network 04

A.1.2.4.48 Type

Attribute Identifier

1

Type

2

Type shall be coded as follows:

Type A 01

Type B 02

A.1.2.4.49 Window Size

Attribute Identifier

1

Window Size

2-3

Window Size shall be a binary presentation of the number of Layer 3 Load Data Segment messages to be sent before a Layer 3 acknowledgement needs to be issued. Value 0 is not used.