7 LCS O&M Protocol

12.713GPPLocation Services (LCS)Location services managementTS

There are two operation codes set aside for LLP O&M messages (OMManagerReq and OMAgentReq). OMManagerReq is invoked by the network, as explained in GSM 04.71 [9], to request a specific O&M activity from the LMU and receive reports from the LMU. OMAgentReq is invoked by the LMU, as explained in GSM 04.71 [9], to report an O&M event to the network or for the LMU to request service from the network.

7.1 LMU LCS O&M Messages and Procedures

7.1.1 Management Information Model

7.1.1.1 Managed Entities

This model describes how entities are managed across the LMU-SMLC interface, but it does not specify how information is transferred inside the site. That is, the manner of communication between a managed entity and managed entities under it is not specified in the present document.

Managed Entities are shown in Figure 2 and listed below. Functional descriptions of each managed entity are found in Table 1.

LMU provides the overall management of the timing measurement capability.

Uplink Timing Estimator is needed for TOA only. It conditions the received uplink signal in preparation for the estimation algorithm and then estimates the time of arrival of the received uplink signal.

Downlink Timing Estimator conditions the received downlink signal in preparation for the estimation algorithm and then estimates the time of arrival of the received downlink signal. The downlink timing estimation algorithm and the uplink timing estimation algorithm are different due to the difference in frame structure. The downlink timing estimation algorithm may only be required to perform coarse timing estimates in the case of TOA.

Network Interfacer supports the network interface required for commands and reports between the GSM network and the LMU. The physical interface may be a GSM Radio Interface, a wire or a bus (in the case of an LMU integrated into a BTS). Peer communications are between the SMLC and the LMU.

Figure 2: Managed Entity Model Seen Across the LMU-SMLC Interface

Table 1: Managed Entities, Attributes and Procedures Seen Across the LMU-SMLC Interface

Managed Entities

Attributes

Procedures

LMU

Administrative State

Operational State

Availability Status

Manufacturer ID

HW Configuration

SW Configuration

LMU Position (optional)

Type1

Self-Position Capability1

Set Own Position Upon Startup2

Method1

Software Download Capability1

Time

Autonomous Swap3

Calibration Required1

TimingType1

SW Download Management (7.1.2.2)

Diagnostic Test (7.1.2.3)

State Management (7.1.2.4)

Event Report (7.1.2.5)

Equipment Management (7.1.2.6)

General Management (A.1.1.7)

Report Management (0)

Uplink Timing Estimator (TOA only)

Administrative State

Operational State

Availability Status

Diversity (optional)

Attenuator Enable (optional)

SW Download Management (7.1.2.2)

Diagnostic Test (7.1.2.3)

State Management (7.1.2.4)

Event Report (7.1.2.5)

Equipment Management (7.1.2.6)

General Management (A.1.1.7)

Downlink Timing Estimator

Administrative State

Operational State

Availability Status

Diversity (optional)

Attenuator Enable (optional)

SW Download Management (7.1.2.2)

Diagnostic Test (7.1.2.3)

State Management (7.1.2.4)

Event Report (7.1.2.5)

Equipment Management (7.1.2.6)

General Management (A.1.1.7)

Network

Interfacer

Administrative State

Operational State

Availability Status

Attenuator Enable(optional)

SW Download Management (7.1.2.2)

Diagnostic Test (7.1.2.3)

State Management (7.1.2.4)

Event Report (7.1.2.5)

Equipment Management (7.1.2.6)

General Management (A.1.1.7)

NOTE 1: Mandatory on the manager, optional on the LMU.

NOTE 2: Conditional on the manager when Method = A-GPS, optional on the LMU.

NOTE 3: Conditional on the manager when Software Download Capability = Software Download Capability, optional on the LMU.

NOTE 4: Attribute support is mandatory unless noted otherwise.

7.1.1.2 Addressing of Managed Entities

It is a GSM requirement that the SMLC is capable of operating with LMUs from different manufacturers. So, it is necessary that the differences between LMUs, as seen by the SMLC, are minimised as much as possible. This is achieved by addressing NM messages by the Managed Entity Class and Managed Entity Instance. Correct addressing of the LMU must be provided in Layer 2. All O&M messages are contained in DTAP messages and addressing the DTAP messages properly is out of the scope of this specification.

Managed entity instances also have a Layer 3 address. The instance number is used to address the managed entity instance. Regardless of whether the Layer 2 address uniquely identifies the managed entity instance or not, the Layer 3 address must also be provided so that it can be used by the management agent to determine which managed entity instance is being addressed.

At the time of initialisation, the SMLC and the LMU need to be able to communicate with each other. Interpretation of the IMSI provides the initial linking information.

Specific equipment configuration information is manufacturer-dependent. However, for interoperability, instance numbering must be known by both manager and agent. This, as well as supported functions, is considered as Shared Management Knowledge.

7.1.1.3 State Management of Managed Entities

State management in the present document is generally in line with CCITT X.731 [14]. How state values are applied is explained below.

CCITT X.731 states that "the management state of a managed entity represents the instantaneous condition of availability and operability of the associated resources from the point of view of management."

In the present document there are two different factors (CCITT X.731 defines usage state in addition to these two) that are considered to affect the management state of a managed entity. They are:

– Administration: permission to use or prohibition against using the resource, imposed through the management services;

– Operability: whether or not the resource is physically installed and working.

The present document defines the following three state management attributes to represent the management state of a managed entity:

– Administrative state;

– Operational state;

– Availability status (this provides additional information for understanding the operational state values).

7.1.1.3.1 Administrative State

Administrative states of the managed entity can be controlled only by the SMLC.

The locked state of a managed entity means that the SMLC has terminated all requests to the resource that is represented by the managed entity. No new requests are initiated to this resource.

The shutting down state means that no new requests are initiated to this resource. The on‑going requests are completed.

The unlocked state means that new requests are allowed to the resource represented by the managed entity.

7.1.1.3.2 Operational State

CCITT X.731 gives the following definitions for the values of the operational state attribute:

disabled: the resource is totally inoperable and unable to provide service to the user(s);

enabled: the resource is partially or fully operable and available for use.

In the present document the value disabled represents the following conditions that the resources could have:

– hardware or software is not installed;

– power is turned off;

– failure has occurred;

– radio parameters have not yet been set by elementary procedures (7.1.2), therefore, the resource is off-line.

7.1.1.3.3 Availability Status

The availability status elaborates the operational state attribute. State change is only reported when the operational state changes, not when availability status changes. Availability status is only sent as information along with the state change indication. In the present document the following values are used (availability status is a set value):

In test: The resource is undergoing a test procedure. The operational state may be disabled or enabled, depending on the level of intrusion of the test.

Failed: The resource has an internal fault that prevents it from operating. The operational state is disabled.

Power off: The resource requires power to be applied and is not powered on. The operational state is disabled.

Off line: The resource requires some manual and/or automatic operation(s) to be performed to make it available for use. The operational state is disabled.

Dependency: The resource cannot operate because some other resource on which it depends is unavailable. The operational state is disabled.

Degraded: The service available from the resource is degraded in some respect, such as in speed or operating capacity. The operational state is enabled.

Not installed: The hardware or the software associated with the managed entity has not been installed at the site. Operational state is disabled.

Figure 3 illustrates the operational state and availability status behaviour of managed entities. The initial value of the administrative state is locked.

Figure 3: Managed Entities’ Operational State and Availability Status Behaviour During Initialisation

7.1.2 Elementary Procedures

The operational procedures applicable to the LMU consist of bringing LMU equipment and software into (or taking them out of) service, initiation of tests at the LMU, collection of test results made at the LMU, reporting and clearing of any LMU faults, and reporting of any LMU external alarms. Bringing into service of equipment at the LMU will consist of manual operations, including powering on, and performing local testing where relevant at the LMU, followed by an indication to the SMLC of the LMU equipment availability. It is then an SMLC function to ensure that relevant data on the existence of the equipment is resident at the LMU, and to activate (bring into service) the new equipment.

7.1.2.1 Definition of the Procedures

All the procedures covered in the present document are based on formatted O&M messages. Most formatted O&M messages initiated by the SMLC (or by an LMU) will receive a response or acknowledgement at Layer 3. A pair of such messages, or single message if a response is not required, is referred to as an elementary procedure. All messages shall be sent using LLP messages.

For all elementary procedures described in Subclauses 7.1.2.2 through 7.1.2.8, the protocol scenarios are illustrated with no further explicit reference made from their corresponding clauses because of their self-explanatory nature.

Descriptions of the messages and the direction of transmission are given in the following clauses.

No elementary procedure shall be initiated to a managed entity instance which has not yet replied to a previously initiated elementary procedure with a response (a defined response, an ACK or a NACK) within a Layer 3 time-out. The Layer 3 timeout for ACK, NACK and responses shall have a default value of 10 seconds.

An ACK message is returned to inform the application which initialised the message that the command is performed or will be performed.

The whole message must be rejected if there is something not understood/supported in the original message.

A NACK may not be relevant for some elementary procedures.

The most relevant NACK causes, not covered by the general causes (which are used for understanding of header fields), are given for each elementary procedure with reference to the coding of the NACK causes in Subclause A.1.2.4.25.

The general NACK causes are relevant for any NACK message and are also found in A.1.2.4.25.

7.1.2.2 SW Download Management Procedures

(See ITU Recommendation M.3400 [10] Configuration Management/Installation/Loading SW into NEs).

Software Download Management Procedures facilitate file transfer for downloading software to the LMU. The procedures for software download in the SMLC are as follows. In order to reduce the burden of the management functions on the SMLC, it is recommended that the software storage and the initiation and management control of the procedures reside in the OSS. However, this does not preclude an SMLC from performing these functions.

7.1.2.2.1 Load Data Initiate

This message shall be sent from the SMLC to the LMU to initiate the loading of a file. It indicates the number of segments for which a Layer 3 acknowledgement is required (window size). When receiving data the LMU shall send an ACK after this number of segments, except for the last batch.

SMLC LMU

Load Data Initiate

ACK/NACK

Meaning of ACK message: Ready to receive the specified file.

Message specific NACK causes (see Subclause A.1.2.4.24): 35, 36, 43.

7.1.2.2.2 Load Data Segment

These multi-segment messages shall be used to carry the files for the transfer initiated by the Load Data Initiate message. No other file transfer shall be allowed until the current transfer is finished.

SMLC LMU

Load Data Segment ─╖

Load Data Segment ╟─ Window Size

│ ║

│ ─╜

ACK/NACK

Load Data Segment

etc.

etc.

An ACK shall be sent from the LMU to the SMLC every time when Window Size number of segments specified in the Load Data Initiate message are downloaded. Each segment will be numbered sequentially. A reception of an ACK must not reset the value of the sequence number of the subsequent message segments. When all the expected blocks have been received, an ACK must be sent regardless of the window size. If the timer for a time-out for the Layer 3 acknowledgement expires, the SMLC shall send a Load Data Abort message and the file transfer shall be aborted.

A NACK provides the capability for resending messages that are in error since the last ACK. All messages from the previous ACK shall be resent. Without the NACK, transmission would be delayed while waiting for ACK timeout, or the entire file would need to be resent after receiving a NACK to Load Data End.

Meaning of ACK message: A window of Load Data Segment messages or a complete file has been received successfully. Message specific NACK causes (see Subclause A.1.2.4.24): 42, 44, 45.

7.1.2.2.3 Load Data Abort

This message shall be used by either end if the file transfer can no longer be supported. This message shall also be used by the LMU if the received amount of data exceeds the expected amount.

SMLC LMU

Load Data Abort

7.1.2.2.4 Load Data End

This message shall be sent by the SMLC to the LMU. The LMU sends an ACK when the file has been received in the LMU.

SMLC LMU

Load Data End

ACK/NACK

Meaning of ACK message: File download is successfully terminated.

Message specific NACK causes (see Subclause A.1.2.4.24): 37.

7.1.2.2.5 SW Activate Request

This message shall be sent by the LMU when the resource represented by the managed entity instance has started up. The initialisation of mentioned managed entity instance shall be started with software activation, which may include software download continuing with attribute setting.

SMLC LMU

SW Activate Request

ACK/NACK

Meaning of ACK message: The request is granted and software activation will be commenced.

Message specific NACK causes (see Subclause A.1.2.4.24): 40.

7.1.2.2.6 Activate SW

This message from the SMLC to the LMU shall be used to activate or re-initialise the loaded software, indicating which file (or files) is to be activated. The acknowledgement of the Activate SW indicates that the software can be activated. If the software cannot be activated, a NACK must be sent. The activation may include LMU internal software distribution.

SMLC LMU

Activate SW

ACK/NACK

Meaning of ACK message: File will be activated.

Message specific NACK causes (see Subclause A.1.2.4.24): 35, 38, 39.

7.1.2.2.7 SW Activated Report

This message from the LMU to the SMLC shall be sent from the addressed managed entity on the LMU at a successful completion of the software distribution to and activation on all indicated destinations in the LMU.

SMLC LMU

SW Activated Report

7.1.2.3 Diagnostic Test Procedures

Diagnostic Test Procedures allow the OSS to run tests that are available in the LMU. These are not intended to provide an exhaustive in-field test capability.

7.1.2.3.1 Perform Test

(See ITU Recommendation M.3400 [10] Fault Management/Fault Localisation/Running of Diagnostic and Configuration Management/Provisioning/NE Configuration/Start Transmission Test).

This message shall be used to tell the LMU to perform a test, if necessary to set a physical configuration for the SMLC to carry out a test on the LMU, 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. It is not assumed that the LMU will provide scheduling for recurring tests. Therefore, the recurring mechanism must be built into the test definition.

One test is defined:

A functional managed entity self-test shall be used to activate an internal self test procedure of a functional managed entity on the LMU made to test equipment that provides the services of the functional managed entity. By its nature this test and its results are proprietary.

SMLC LMU

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 A.1.2.4.24): 28, 29, 30.

7.1.2.3.2 Test Report

(See ITU Recommendation M.3400 [10] Fault Management/Fault Localisation/NE Fault Localisation/Diagnostic Report).

This message shall be sent by the LMU giving the result of a test ordered by the SMLC and is sent autonomously as soon as the result is available. A Test Report shall also be sent after a specific request from the SMLC 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 LMU by the SMLC.

SMLC LMU

Test Report

7.1.2.3.3 Send Test Report

(See ITU Recommendation M.3400 [10] Fault Management/Fault Localisation/NE Fault Localisation/Request Diagnostic Data).

This message shall be sent from the SMLC to ask for the result/report of a test which was not to be sent autonomously, but is now to start 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.

SMLC LMU

Send Test Report

ACK/NACK

Meaning of ACK message: The specified test report will be sent.

Message specific NACK causes (see Subclause A.1.2.4.24): 28, 31.

7.1.2.3.4 Stop Test

(See ITU Recommendation M.3400 [10] Fault Management/Fault Localisation/NE Fault Localisation/Stop Diagnosis in Progress).

This message shall be used by the SMLC to stop a continuously recurring test at the LMU, 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.

SMLC LMU

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 A.1.2.4.24): 32, 33, 34.

7.1.2.4 State Management Procedures

The State Management Procedures provide the capability to control state values.

7.1.2.4.1 State Changed Event Report

(See ITU Recommendation M.3400 [10] Configuration Management/Status and Control/Notification of state changes by NEs).

An unsolicited report shall be sent from the LMU to the SMLC whenever a change of the operational state of a managed entity defined in the present document occurs.

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

SMLC LMU

State Changed Event Report

7.1.2.4.2 Change Administrative State

(See ITU Recommendation M.3400 [10] Configuration Management/Provisioning/NE Configuration/Set Service State).

The Change Administrative State message shall be used by the SMLC to change the administrative state (as specified by specification GSM 12.20) of a managed entity.

SMLC LMU

Change Administrative State

ACK/NACK

Meaning of ACK message: The specified change of administrative state has been performed.

Message specific NACK causes (see Subclause A.1.2.4.24): None.

7.1.2.4.3 Change Administrative State Request

This request message shall be sent by the LMU when there is a need to change the administrative state of a managed entity at the LMU site. This message can only be initiated as a result of a local MMI command. This message is needed since there may be a need to change the administrative state from the LMU, yet only the agent can change the administrative state. To resolve this, the LMU requests the agent to change the administrative state.

SMLC LMU

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 A.1.2.4.24): 40, 41.

7.1.2.5 Event Report Procedures

Event Report Procedures provide event reporting and control.

7.1.2.5.1 Failure Event Report

(See ITU Recommendation M.3400 [10] Fault Management/Alarm Surveillance/Alarm Reporting/Report Alarm, Fault Management/Alarm Surveillance/Failure Event Detection and Reporting, Configuration Management/Status and Control/NE Status and Control/Control Event Report, and Fault Management/Fault Correction/NE Fault Correction/Automatic Restoration Report).

An unsolicited report shall be sent from the LMU to the SMLC whenever failure events occur in the LMU.

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

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

SMLC LMU

Failure Event Report

7.1.2.5.2 Stop Sending Event Reports

(See ITU Recommendation M.3400 [10] Fault Management/Alarm Surveillance/Alarm Reporting/Inhibit Alarm Reporting).

This inhibition of sending of event reports shall be used by the SMLC to prevent a flood of event reports which are of no benefit to the SMLC. One example of this occurs at an LMU restart following a power failure. The operational capability of the LMU 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.

SMLC LMU

Stop Sending Events Reports

ACK/NACK

Meaning of ACK message: Sending of specified Event Report has been stopped.

Message specific NACK causes (see Subclause A.1.2.4.24): None.

7.1.2.5.3 Restart Sending Event Reports

(See ITU Recommendation M.3400 [10] Fault Management/Alarm Surveillance/Alarm Reporting/Allow Alarm Reporting).

When the LMU is back in normal operation or if it is of interest to check whether the LMU still generates a flood of Event Reports, a Restart Sending Event Reports shall be sent.

SMLC LMU

Restart Sending Events Reports

ACK/NACK

Meaning of ACK message: Sending of specified Event Report has been restarted.

Message specific NACK causes (see Subclause A.1.2.4.24): None.

7.1.2.5.4 Report Outstanding Alarms

(See ITU Recommendation M.3400 [10] Fault Management/Alarm Surveillance/Alarm Reporting/Request Alarm History).

This message shall be used by the SMLC to ask the LMU to report all outstanding alarms related to the managed entity instance indicated in the message. The LMU 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 LMU itself. If there is no outstanding alarm, the LMU shall reply with a NACK with that cause indicated.

SMLC LMU

Report Outstanding Alarms

ACK/NACK

Meaning of ACK message: Sending of Failure Event Report will start.

Message specific NACK causes (see Subclause A.1.2.4.24): 40, 41, 42.

7.1.2.6 Equipment Management Procedures

Equipment Management Procedures provide the capability to control equipment during maintenance.

7.1.2.6.1 Change-over

(See ITU Recommendation M.3400 [10] Configuration Management/Status and Control/Status and Control of NEs).

This message shall be sent to change over between active and standby units of equipment. The action may be performed on any addressable functional managed entity and manufacturer-dependent HW units. Which type of HW unit to address and how to identify certain units of this type of HW are manufacturer-dependent.

SMLC LMU

Change-over

ACK/NACK

Meaning of ACK message: The specified change-over operation has been performed.

Message specific NACK causes (see Subclause A.1.2.4.24): 25, 26, 30, 35.

7.1.2.6.2 Opstart

(See ITU Recommendation M.3400 [10] Configuration Management/Status and Control/NE Status and Control).

This message shall be sent by the SMLC to tell the LMU to attempt to operate the identified managed entity putting it to an initial normal operational state (i.e., enabled, see Subclause 7.1.1.3.2). This message does not affect the managed entity’s administrative state if there exists a value explicitly assigned by the SMLC. If there is yet no administrative state value explicitly set by the SMLC (e.g., at an initialisation time), the managed entity shall be presumed to be administratively locked by default. No LMU 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 managed entity is in fact not ready to be in an enabled state, the managed entity will be in a fault condition as a consequence of this message, and the condition shall be handled by the managed entity’s normal fault handling function as the condition is detected.

SMLC LMU

Opstart

ACK/NACK

Meaning of ACK message: The LMU has reset the operational state of the specified

managed entity to "enabled" state.

Message specific NACK causes (see Subclause A.1.2.4.24): 25, 26, 35.

NOTE: The manager cannot change the operational state, so this procedure allows a change of the operational state.

7.1.2.6.3 Reinitialise

(See ITU Recommendation M.3400 [10] Configuration Management/Provisioning/NE Configuration/Restart Request and Report).

This message shall be sent by the SMLC to tell the LMU to have specified hardware resource of the indicated managed entity start a re-initialisation procedure as sketched in Figure 3. The specifics of a re-initialisation procedure, which typically takes place at the time of a cold start of the resource, is manufacturer-dependent. For a software reinitialisation, Activate SW message shall be used.

SMLC LMU

Reinitialise

ACK/NACK

Meaning of ACK message: The LMU has received the message and is about to start a reinitialisation of the specified resource.

Message specific NACK causes (see Subclause A.1.2.4.24): 25, 26, 35.

7.1.2.7 General Management Procedures

General Management Procedures are protocol-unique procedures that provide the capability to control attribute values.

7.1.2.7.1 Set Attributes

(See ITU Recommendation M.3400 [10] Configuration Management/Provisioning/NE Configuration/Set Service State and Set Parameters).

This message shall be sent to provide a managed entity instance in LMU with all the necessary attributes relating to that LMU managed entity. This message also includes common information for all logical channels of one type, e.g., CCCH parameters.

SMLC LMU

Set Attributes

ACK/NACK

Meaning of ACK message: All specified LMU attributes have been set.

Message specific NACK causes (see Subclause A.1.2.4.24): 35.

7.1.2.7.2 Get Attributes

(See ITU Recommendation M.3400 [10] Configuration Management/Provisioning/NE Configuration/Request Configuration and Configuration Report, Configuration Management/Status and Control/NE Status and Control/Request Status and Status Report, and Configuration Management/Status and Control/Access to State Information in NEs).

This message shall be used by the SMLC to tell the LMU to send attributes which have previously been set by the LMU. It may be used as a check on accuracy and be incorporated into normal procedures, or may be used by the SMLC to recover information which it has lost.

SMLC LMU

Get Attributes

Response/NACK

Message specific NACK causes (see Subclause A.1.2.4.24): None.

7.1.2.7.3 Set Alarm Threshold

(See ITU Recommendation M.3400 [10] Configuration Management/Provisioning/NE Configuration/Set Service Thresholds).

This message shall be used by the SMLC to tell the LMU some threshold parameters related to fault thresholds.

SMLC LMU

Set Alarm Threshold

ACK/NACK

Message specific NACK causes (see Subclause A.1.2.4.24): None.

7.1.2.8 Report Management Procedures

(See ITU Recommendation M.3400 [10] Configuration Management/Status and Control/Status and Control of NEs).

Report Management Procedures provide access to GPS information.

7.1.2.8.1 GPS Parameter Request

This message shall be used by the SMLC to request current GPS position from the LMU.

SMLC LMU

GPS Parameter Request

GPS Parameter Report/NACK

Message specific NACK causes (see Subclause A.1.2.4.24): None.

7.1.2.8.2 GPS Parameter Report

This message shall be used by the LMU as a solicited or unsolicited report to convey GPS position measurements which may be corrected by the SMLC.

SMLC LMU

GPS Parameter Report

ACK/NACK

Message specific NACK causes (see Subclause A.1.2.4.24): None.

7.1.3 Message Coding

This clause defines the OMMngrReq and OMAgentReq messages specified in 04.71 [9]. These messages contain the SMLC-LMU messages defined by ASN.1 and coded by PER (X.691 [12]). In this ASN.1 module, ASN.1/94 defined in ITU-T X.680 [11] recommendations (ASN.1 1994) is used.

LLP-OM-Protocol

–{ LLP-OM-Protocol Object Identifier }

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

IMPORTS

ExtensionContainer

FROM MAP-ExtensionDataTypes {

ccitt identified-organization (4) etsi (0) mobileDomain (0)

gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version4 (4)}

;

— OMMngrReq are message requests from the SMLC to the LMU

OMMngrReq ::= CHOICE

{

— SW Download Message

loadDataInitiate LoadDataInitiate,

loadDataSegment LoadDataSegment,

loadDataEnd LoadDataEnd,

loadDataAbort LoadDataAbort, — Does not have ACK/NACK

activateSW ActivateSW,

— Diagnostic Test Procedures

performTest PerformTest,

sendTestRep SendTestRep,

stopTest StopTest,

— State Management Procedures

chngAdminState ChngAdminState,

— Event Report Procedures

stopSendingEvntRep StopSendingEvntRep,

restartSendingEvntRep RestartSendingEvntRep,

repOuststandingAlarms RepOuststandingAlarms,

— Equipment Management Procedures

chngOver ChngOver,

opstart Opstart,

reinitialize Reinitialize,

— General Management Procedures

setAttributes SetAttributes,

getAttributes GetAttributes,

setAlarmThreshold SetAlarmThreshold,

— Report Management Procedures

gpsParameterReq GPSParameterReq,

— Manufacture Dependent Procedures

mngrManufDepReq MngrManufDepReq,

}

— OMAgntReq are message requests from the LMU to the SMLC

OMAgntReq ::= CHOICE

{

— SW Download Message

loadDataAbort LoadDataAbort, — Does not have ACK/NACK

swActivateReq SWActivateReq,

swActivatedRep SWActivatedRep, — Does not have ACK/NACK

— Diagnostic Test Procedures

testRep TestRep, — Does not have ACK/NACK

— State Management Procedures

stateChngEvntRep StateChngEvntRep, — Does not have ACK/NACK

chngAdminStateReq ChngAdminStateReq,

— Event Report Procedures

failureEvntRep FailureEvntRep, — Does not have ACK/NACK

— Report Management Procedures

gpsParameterRep GPSParameterRep,

— Manufacture Dependent Procedures

agntManufDepReq AgntManufDepReq,

}

— OMMngrRsp are responses from the LMU to the SMLC message requests

OMMngrRsp ::= CHOICE

{

activateSWRsp ActivateSWRsp,

loadDataInitiateRsp LoadDataInitiateRsp,

loadDataSegmentRsp LoadDataSegmentRsp,

loadDataEndRsp LoadDataEndRsp,

performTestRsp PerformTestRsp,

sendTestRepRsp SendTestRepRsp,

stopTestRsp StopTestRsp,

chngAdminStateRsp ChngAdminStateRsp,

stopSendingEvntRepRsp StopSendingEvntRepRsp,

restartSendingEvntRepRsp RestartSendingEvntRepRsp,

repOuststandingAlarmsRsp RepOuststandingAlarmsRsp,

chngOverRsp ChngOverRsp,

opstartRsp OpstartRsp,

reinitializeRsp ReinitializeRsp,

setAttributesRsp SetAttributesRsp,

getAttributesRsp GetAttributesRsp,

setAlarmThresholdRsp SetAlarmThresholdRsp,

mngrManufDepRsp MngrManufDepRsp,

gpsParameterReqRsp GPSParameterReqRsp,

}

— OMAgntRsp are responses from the SMLC to the LMU message requests

OMAgntRsp ::= CHOICE

{

swActivateReqRsp SWActivateReqRsp,

chngAdminStateReqRsp ChngAdminStateReqRsp,

gpsParameterRepRsp GPSParameterRepRsp,

agntManufDepRsp AgntManufDepRsp,

}

–OMMngrReq Messages

ActivateSW ::= SEQUENCE

{

header Header,

swDescription SWDescription OPTIONAL

}

ChngAdminState ::= SEQUENCE

{

header Header,

administrativeState AdministrativeState

}

ChngOver ::= SEQUENCE

{

header Header,

source Source,

destination Destination

}

GetAttributes ::= SEQUENCE

{

header Header,

list SEQUENCE OF AttributeIdentifier

}

GPSParameterReq ::= SEQUENCE

{

header Header

}

LoadDataAbort ::= SEQUENCE

{

header Header

}

LoadDataEnd ::= SEQUENCE

{

header Header

}

LoadDataInitiate ::= SEQUENCE

{

header Header,

swDescription SWDescription,

windowSize WindowSize,

numberOfSegments NumberOfSegments

}

LoadDataSegment ::= SEQUENCE

{

header Header,

sequenceNumber INTEGER (0..255),

fileData FileData

}

MngrManufDepReq ::= SEQUENCE

{

header Header,

}

Opstart ::= SEQUENCE

{

header Header

}

PerformTest ::= SEQUENCE

{

header Header,

testNumber TestNumber,

autonomouslyRep AutonomouslyRep,

testDuration TestDuration OPTIONAL,

physicalConfiguration PhysicalConfiguration OPTIONAL

}

Reinitialize ::= SEQUENCE

{

header Header,

hwDescription SEQUENCE OF HWDescription OPTIONAL

}

RepOuststandingAlarms ::= SEQUENCE

{

header Header

}

RestartSendingEvntRep ::= SEQUENCE

{

header Header,

eventType EventType,

perceivedSeverity PerceivedSeverity OPTIONAL,

probableCause ProbableCause OPTIONAL,

specificProblems SpecificProblems OPTIONAL

}

SendTestRep ::= SEQUENCE

{

header Header,

testNumber TestNumber

}

SetAlarmThreshold ::= SEQUENCE

{

header Header,

probableCause ProbableCause,

manufacturerDependentThresholds ManufacturerDependentThresholds OPTIONAL

}

SetAttributes ::= SEQUENCE

{

header Header,

list SEQUENCE OF SEQUENCE

{

id AttributeIdentifier,

value AttributeData

}

}

StopSendingEvntRep ::= SEQUENCE

{

header Header,

eventType EventType,

perceivedSeverity PerceivedSeverity OPTIONAL,

probableCause ProbableCause OPTIONAL,

specificProblems SpecificProblems OPTIONAL

}

StopTest ::= SEQUENCE

{

header Header,

testNumber TestNumber

}

–OMAgntReq Messages

AgntManufDepReq ::= SEQUENCE

{

header Header,

}

ChngAdminStateReq ::= SEQUENCE

{

header Header,

administrativeState AdministrativeState

}

FailureEvntRep ::= SEQUENCE

{

header Header,

eventType EventType,

perceivedSeverity PerceivedSeverity,

probableCause ProbableCause,

eventTime EventTime OPTIONAL,

specificProblems SpecificProblems OPTIONAL,

hwDescription HWDescription OPTIONAL,

swDescription SWDescription OPTIONAL,

additionalText AdditionalText OPTIONAL,

additionalInfo AdditionalInfo OPTIONAL,

outstandingAlarmSequence OutstandingAlarmSequence OPTIONAL

}

GPSParameterRep ::= SEQUENCE

{

header Header,

pseudoRange PseudoRange,

timeOfFix TimeOfFix,

satelliteInfo SatelliteInfo

}

StateChngEvntRep ::= SEQUENCE

{

header Header,

operationalState OperationalState OPTIONAL,

availabilityStatus AvailabilityStatus OPTIONAL,

manufacturerDependentState ManufacturerDependentState OPTIONAL

}

SWActivatedRep ::= SEQUENCE

{

header Header,

result Result

}

SWActivateReq ::= SEQUENCE

{

header Header,

hwConfiguration HWConfiguration,

swConfiguration SWConfiguration

}

TestRep ::= SEQUENCE

{

header Header,

testNumber TestNumber,

testRepInfo TestRepInfo

}

— OMMngrRsp Messages

ActivateSWRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

ChngOverRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

ChngAdminStateRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

GetAttributesRsp ::= SEQUENCE OF SEQUENCE

{

attributeIdentifier AttributeIdentifier,

information AttributeData

}

GPSParameterReqRsp ::= CHOICE

{

gpsParameterRep GPSParameterRep, — or a NACK is sent

empty Empty

}

LoadDataEndRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

LoadDataInitiateRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

LoadDataSegmentRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

MngrManufDepRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

OpstartRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

PerformTestRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

ReinitializeRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

RepOuststandingAlarmsRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

RestartSendingEvntRepRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

SendTestRepRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

SetAlarmThresholdRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

SetAttributesRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

StopSendingEvntRepRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

StopTestRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

— OMAgntRsp Messages

AgntManufDepRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

ChngAdminStateReqRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

GPSParameterRepRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

SWActivateReqRsp ::= SEQUENCE

{

extensionContainer ExtensionContainer OPTIONAL,

}

— Other Type Definition

AdditionalInfo ::= OCTET STRING (SIZE (1..244))

AdditionalText ::= OCTET STRING (SIZE (1..244))

AdministrativeState ::= INTEGER

{

locked (1),

unlocked (2),

shuttingDown (3),

null (64)

} (1..64)

AttributeIdentifier ::= INTEGER

{

administrativeState (1),

attenuatorEnable (2),

autonomousSwap (3),

availabilityStatus (4),

calibrationRequired (5),

diversity (6),

hwConfiguration (7),

manufacturerID (8),

method (9),

lmuPosition (10),

operationalState (11),

selfPositionCapability (12),

setOwnPositionUponStartup (13),

softwareDownloadCapability (14),

swConfiguration (15),

time (16),

timingType (17),

type (18)

} (1..255)

AttributeData ::= CHOICE

{

administrativeState AdministrativeState,

attenuatorEnable AttenuatorEnable,

autonomouslySwap AutonomouslySwap,

availabilityStatus AvailabilityStatus,

calibrationRequired CalibrationRequired,

diversity Diversity,

hwConfiguration HWConfiguration,

lmuPosition LMUPosition,

manufacturerID ManufacturerID,

method Method,

operationalState OperationalState,

selfPositionCapabilty SelfPositionCapabilty,

setOwnPositionUponStartup SetOwnPositionUponStartup,

softwareDownloadCapability SoftwareDownloadCapability,

swConfiguration SWConfiguration,

time Time,

timingType TimingType,

type Type,

}

AttenuatorEnable ::= BOOLEAN

— Enable (TRUE)

— Disable (FALSE)

AutonomouslyRep ::= BOOLEAN

— Autonomously Report (TRUE)

— No Autonomous Report (FALSE)

AutonomouslySwap ::= BOOLEAN

— Autonomous Swap (TRUE)

— No Autonomous Swap (FALSE)

Availability ::= INTEGER

{

inTest (1),

failed (2),

powerOff (3),

offLine (4),

unused (5),

dependancy (6),

degraded (7),

notInstalled (8)

} (1..128)

AvailabilityStatus ::= SEQUENCE SIZE (1..28) OF Availability

CalibrationRequired ::= BOOLEAN

— Calibration Required (TRUE)

— Calibration Not Required ( FALSE)

Destination ::= OCTET STRING (SIZE (1..244))

Diversity ::= BOOLEAN

— Diversity (TRUE)

— No Diversity (FALSE)

Empty ::= SEQUENCE

{

emptyField NULL,

extensionContainer ExtensionContainer OPTIONAL

}

EventTime ::= INTEGER (0..604799)

EventType ::= INTEGER

{

communicationFailure (1),

qualityOfServiceFailure (2),

processingFailure (3),

equipmentFailure (4),

environmentFailure (5)

— reserved (6..15)

— manufacturerDependent (16..255)

} (1..255)

FileData ::= OCTET STRING (SIZE (1..244))

FileID ::= OCTET STRING (SIZE (1..244))

FileVersion ::= OCTET STRING (SIZE (1..244))

Header ::= SEQUENCE

{

managedEntityType ManagedEntityType,

managedEntityInstance ManageEntityInstance

}

HWConfiguration ::= SEQUENCE SIZE (1..64) OF HWDescription

HWDescription ::= SEQUENCE

{

equipmentID OCTET STRING (SIZE (1..244)),

equipmentType OCTET STRING (SIZE (1..244)),

equipmentVersion OCTET STRING (SIZE (1..244)),

location OCTET STRING (SIZE (1..244)),

manufacturerInfo OCTET STRING (SIZE (1..244)),

}

Latitude ::= SEQUENCE

{

— ddMM.mmmm

degrees INTEGER (0..90),

minutes INTEGER (0..59),

fractionalMinuntes INTEGER (0..9999),

direction BOOLEAN

— North (FALSE )

— South (TRUE)

}

LMUPosition ::= SEQUENCE

{

latitude Latitude,

longitude Longitude,

altitude INTEGER (0..16383)

}

Longitude ::= SEQUENCE

{

— ddMM.mmmm

degrees INTEGER (0..180),

minutes INTEGER (0..59),

fractionalMinuntes INTEGER (0..9999),

direction BOOLEAN

— East (FALSE)

— West (TRUE)

}

ManagedEntityType ::= INTEGER

{

lmu (1),

uplinkTimingEstimator (2),

downlinkTimingEstimator (3),

networkTransceiver (4),

null (255)

} (1..255)

ManageEntityInstance ::= SEQUENCE

{

lmuNumber INTEGER (0..65535),

firstTierNumber INTEGER (0..255),

}

ManufacturerDependentState ::= INTEGER (1..64)

ManufacturerDependentThresholds ::= SEQUENCE SIZE (0..255) OF SEQUENCE

{

id INTEGER (0..255),

threshold Number

}

ManufacturerID ::= OCTET STRING (SIZE (1..244))

Method ::= BIT STRING

{

toa (0),

eotd (1),

agps (2)

} (SIZE(1..32))

NACKCauses ::= INTEGER

{

— General Nack

incorrectMsgStruct (1),

invalidMsgTypeValue (2),

— reserved (3-4)

invalidManagedEntityClassValue (5),

managedEntityClassNotSupported (6),

lmuNumUnknown (7),

basebandTransceiverNumUnknown (8),

managedEntityInstanceUnknown (9),

— reserved (10-11)

invalidAttributeIdentifierValue (12),

attributeIdentifierNotSupported (13),

parameterValueOutsidePermittedRange (14),

inconsistencyInAttributeList (15),

specifiedImplementationNotSupported (16),

messageCannotBePerformed (17),

— reserved (18..24)

— Specific NACK

resourceNotImplemented (25),

resourceNotAvailable (26),

frequencyNotAvailable (27),

testNotSupported (28),

capacityRestrictions (29),

physicalConfigurationCannotBePerformed (30),

testNotInitiated (31),

physicalConfigurationCannotBeRestored (32),

noSuchTest (33),

testCannotBeStopped (34),

messageInconsisitentWithPhysicalConfig (35),

unableToReceiveFile (36),

completeFileNotReceived (37),

fileNotAvailableAtDestination (38),

fileCannotBeActivated (39),

requestNotGranted (40),

wait (41),

notAllSegmentMessageReceivedSuccessfully (42),

windowSizeTooLarge (43),

duplicateSequenceNumber (44),

missingSequenceNumber (45),

— reserved (46..126)

— manufacturerDependent (127..254)

null (255)

} (1..255)

Number CHOICE

{

intNum INTEGER (0..255),

realNum REAL

}

NumberOfSegments ::= INTEGER (0..65535)

OperationalState ::= INTEGER

{

disabled (1),

enabled (2),

null (255)

} (1..255)

OutstandingAlarmSequence ::= INTEGER (0..255)

PerceivedSeverity ::= INTEGER

{

failureCeased (1),

criticalFailure (2),

majorFailure (3),

minorFailure (4),

warningLevelFailure (5),

indeterminateFailure (6)

— reserved (7..63)

— manufacturerDependent (63..255)

} (1..255)

PhysicalConfiguration ::= INTEGER (0..255)

ProbableCause ::= SEQUENCE

{

probableCauseType ProbableCauseType,

probableCauseValue INTEGER (1..1024)

}

ProbableCauseType ::= INTEGER

{

x721 (1),

gsmSpecific (2),

manufacturerSpecific (3)

} (1..32)

PseudoRange ::= SEQUENCE

{

— KKKKK.kkkkk

kiloMeters INTEGER (0..99999),

factionalKM INTEGER (0.99999)

}

Result ::= BOOLEAN

— Success (TRUE)

— Failure (FLASE)

SatelliteInfo ::= SEQUENCE SIZE (1..16) OF SEQUENCE

{

id INTEGER (1..32)

}

SelfPositionCapabilty ::= BOOLEAN

— Capable Of Self Position (TRUE)

— Incapable Of Self Position (FLASE)

SetOwnPositionUponStartup ::= BOOLEAN

— Set Own Position Upon Startup (TRUE)

— Do Not Set Own Position Upon Startup (FLASE)

SoftwareDownloadCapability ::= BOOLEAN

— Software Download Capability (TRUE)

— No Software Download Capability (FLASE)

Source ::= OCTET STRING (SIZE (1..244))

SpecificProblems ::= INTEGER (0..255)

— reserved (0..15)

— manufacturerDependent (16..255)

SWConfiguration ::= SEQUENCE SIZE (1..64) OF SWDescription

SWDescription ::= SEQUENCE

{

fileId FileID,

fileVersion FileVersion

}

TestDuration ::= INTEGER (0..16777215)

TestNumber ::= INTEGER

{

lmuFunctionalObjectSelfTest (1),

allTestsAssociatedWithTheObject (255)

— reserved (2..63)

— manufacturerDependent (64..254)

} (1..255)

TestRepInfo ::= Number

Time ::= INTEGER (0..604800)

TimeOfFix ::= INTEGER (0..604800)

— In GPS seconds

TimingSource ::= BIT STRING

{

gps (0),

gsm (1),

glonass (2),

internalClock (3),

network (4)

} (SIZE(0..63))

TimingType ::= SEQUENCE

{

timingSource TimingSource,

calibrationRequired CalibrationRequired

}

Type ::= INTEGER

{

typeALMU (1),

typeBLMU (2)

} (1..32)

WindowSize ::= INTEGER (1..65535)

END

7.2 SMLC LCS O&M Messages and Procedures

For future study.

7.3 GMLC LCS O&M Messages and Procedures

For future study.

Annex A (informative):
Messages and Procedures Descriptions