9 LMU LCS Protocol operation specifications

04.713GPPLocation Services (LCS)Mobile radio interface Layer 3 specificationRelease 1998TS

9.1 General

This clause specifies the abstract syntax for the LMU LCS Protocol using the Abstract Syntax Notation One (ASN.1), defined in CCITT Recommendation X.680 (1997).

The encoding rules which are applicable to the defined abstract syntax are the Packet Encoding Rules for Abstract Syntax Notation One, defined in ITU-T Recommendation X.691. For each Location Service parameter which has to be transferred by a Location Service message, there is a PDU field (an ASN.1 NamedType) whose ASN.1 identifier has the same name as the corresponding parameter, except for the differences required by the ASN.1 notation (blanks between words are removed, the first letter of the first word is lower-case and the first letter of the following words are capitalized (e.g. "bearer service" is mapped to "bearerService"). In addition some words may be abbreviated as follows:

lmu: location measurement unit;

lcs: location services;

The ASN.1 data type which follows the keywords ARGUMENT "PARAMETER" or "RESULT" (for OPERATION and ERROR) is always optional from a syntactic point of view. However, except specific mention, it has to be considered as mandatory from a semantic point of view. When in an invoke component, a mandatory element is missing in any component or inner data structure, a reject component is returned with the problem code "Mistyped Parameter". When an optional element is missing in an invoke component or in an inner data structure while it is required by the context, an error component is returned; the associated type of error is "DataMissing".

In case an element is defined as mandatory in the protocol description (3GPP TS 04.71 including imports from 3GPP TS 09.02), but is not present according to the service description (stage 1 to stage 3), the ASN.1 protocol description takes precedence over the diagrams in the 3GPP TS 04.8x and 04.9x-series of technical specifications.

When possible operations and errors are imported from 3GPP TS 09.02 thereby making the MSC transparent to most of the messages sent to or from the LMU.

Timer values for operations which require timers are shown as ASN.1 comments.

Ellipsis Notation shall be used in the same way as described in 3GPP TS 09.02 and shall be supported on the radio interface by the LMU and the network for all operations defined in this specification including those imported from 3GPP TS 09.02.

9.2 Operation types

Table 7.1 summarizes the operations defined for LMU LCS Protocol in this specification, and shows which of these operations are Radio Interface Timing (RIT) related, Time Of Arrival (TOA) location method related, and general LMU procedures related. In this ASN.1 module, ASN.1/88 defined in CCITT X.680 recommendations (ASN.1 1997) is used.

Table 7.1: Relevance of location service operations

Operation name

Direction

Response allowed

RIT

TOA

General LMU

StartRIT

SMLC -> LMU

ReturnResult (empty) .

X

ReportRIT

LMU -> SMLC

No

X

StopRIT

SMLC -> LMU

ReturnResult (empty).

X

IndicateRITError

LMU -> SMLC

No

X

PerformTOA

SMLC -> LMU

ReturnResult

X

StatusQuery

SMLC -> LMU

ReturnResult

X

StatusUpdate

LMU -> SMLC

ReturnResult

(empty)

X

ResetRequest

SMLC -> LMU

ReturnResult (empty).

X

OMMngrRequest

SMLC -> LMU

ReturnResult

X

OMAgntRequest

LMU -> SMLC

ReturnResult

X

This specification defines the following operations (transparent to MSC):

– StartRIT

– ReportRIT

– StopRIT

– IndicateRITError

– PerformTOA

– StatusQuery

– StatusUpdate

– ResetRequest

– OMMngrRequest

– OMAgntRequest

— LLP-Operations module defines the operations transparent to MSC

LLP-Operations

— { LLP-Operations object identifier }

DEFINITIONS ::=

BEGIN

IMPORTS

OPERATION

FROM TCAPMessages {

ccitt recommendation q 773 modules (2) messages (1) version2 (2)}

SystemFailure,

DataMissing,

UnexpectedDataValue,

FacilityNotSupported,

UnknownSubscriber,

FROM MAP-Errors {

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

gsm-Network (1) modules (3) map-Errors (10) version4 (4)}

UnDefinedError

FROM LLP-Errors

— {}

StartRITReq,

StartRITRsp,

ReportRITArg,

StopRITReq,

StopRITRsp,

ErrorRITArg,

PerformTOAReq,

TOAResultRsp,

StatusReq,

StatusRsp,

ResetReq,

ResetRsp,

StatusUpdateReq,

StatusUpdateRsp

FROM LLP-DataTypes {

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

gsm-Network (1) modules (3) map-LCS-DataTypes (n) version4 (4)}

OMMngrReq,

OMMngrRsp,

OMAgntReq,

OMAgntRsp,

NACKCauses

FROM LLP-OM-Protocol –{ LLP-OM-Protocol Object identifier }–

;

— OPERATION definitions based on macro notation

StartRIT::= OPERATION — identifier StartRIT-Measurement

ARGUMENT

startRITReq StartRITReq

RESULT

startRITRsp StartRITRsp

ERROR {

SystemFailure,

DataMissing,

UnexpectedDataValue,

ResourcesNotAvailable,

UnDefinedError

}

ReportRIT::= OPERATION — identifier ReportRIT-Measurement

ARGUMENT

reportRITArg ReportRITArgR

StopRIT::= OPERATION — identifier StopRIT-Measurement

ARGUMENT

stopRITReq StopRITReq

RESULT

StopRITRsp StopRITRsp

IndicateRITError ::= OPERATION

ARGUMENT

errorRITArg ErrorRITArg

PerformTOA::= OPERATION — identifier PerformTOA-Measurment

ARGUMENT

performTOAReq PerformTOAReq

RESULT

toaResultRsp TOAResultRsp

ERROR {

SystemFailure,

DataMissing,

UnexpectedDataValue,

ResourcesNotAvailable,

UnDefinedError

}

StatusQuery::= OPERATION

ARGUMENT

statusReq StatusReq

RESULT

statusRsp StatusRsp

ERROR {

}

ResetRequest::= OPERATION

ARGUMENT

resetReq ResetReq

RESULT

resetRsp ResetRsp

ERROR {

SystemFailure,

UnDefinedError

}

OMMngrRequest ::= OPERATION — defined in LLP-OM, 12.71

ARGURMENT

oMMngrReq OMMngrReq

RESULT

oMMngrRsp OMMngrRsp

ERROR

{

NACKCauses

}

OMAgntRequest ::= OPERATION — defined in LLP-OM, 12.71

ARGURMENT

oMAgntReq OMAgntReq

RESULT

oMAgntRsp OMAgntRsp

ERROR

{

NACKCauses

}

StatusUpdate ::= OPERATION — identifier Status Update

ARGUMENT

statusUpdateReq StatusUpdateReq

RESULT

statusUpdateRsp StatusUpdateRsp

ERROR {

SystemFailure,

DataMissing,

UnexpectedDataValue,

ResourceNotAvailable,

UnDefinedError

}

END

9.2.1 Operation types description

For each operation type this subclause provides a brief prose description.

9.2.1.1 StartRIT (network –> LMU)

This operation type is invoked by the network to request RIT measurement information from an LMU.

9.2.1.2 ReportRIT (LMU –>network)

This operation type is invoked by an LMU to report to the network RIT measurement information. This operation is used to report periodical measurements.

9.2.1.3 StopRIT (network –> LMU)

This operation type is invoked by the network to request an LMU to stop on-going RIT measurements and reporting.

9.2.1.4 IndicateRITError (LMU –> network)

This operation type is invoked by an LMU to indicate error situations.

9.2.1.5 PerformTOA (network –> LMU)

This operation type is invoked by the network to request an LMU to perform TOA location mesurements. The measurement results are returned using the return result component of the operation.

9.2.1.6 StatusQuery (network –> LMU)

This operation type is invoked by the network to request status an LMU The status is returned using the return result component of the operation.

9.2.1.7 StatusUpdate (LMU –> network)

This operation type is invoked by an LMU to report status of LMU, e.g. after reset or periodically.

9.2.1.8 ResetRequest (network –> LMU)

This operation type is invoked by the network to reset an LMU.

9.2.1.9 OMMngrRequest (network –> LMU)

This operation type is invoked by the network to request a specific O&M activity to LMU as defined in 3GPP TS 12.71.

9.2.1.10 OMAgntRequest (LMU -> network)

This operation type is invoked by the LMU to report an O&M event to Network or asking for reporting O&M information from Network as defined in 3GPP TS 12.71.

10.3 Error types

10.3.1 Error types ASN.1 specification

The following ASN.1 module provides an ASN.1 specification of errors. Errors from MAP are imported in the LCS-Protocol module in subclause 9.2. In this ASN.1 module, ASN.1/88 defined in CCITT X.680 recommendations (ASN.1 1997) is used.

LLP-Errors

— { LLP-Errors object identifier }

DEFINITIONS ::=

BEGIN

IMPORTS

ERROR FROM

TCAPMessages FROM {

ccitt recommendation q 773 modules (2) messages (1) version2 (2) }

;

— The MAP errors

— error types definition

UnDefinedError ::=ERROR

END

10.3.2 Error types description

For each error type this subclause provides a brief prose description.

10.3.2.4 SystemFailure

This error is returned by the LMU or the network, when it cannot perform an operation because of a failure.

10.3.2.5 DataMissing

This error is returned by the network or the LMU when an optional parameter is missing in an invoke component or an inner data structure, while it is required by the context of the request.

10.3.2.6 UnexpectedDataValue

This error is returned by the network or the LMU when it receives a parameter with an unexpected value, without type violation.

10.3.2.7 ResourcesNotAvailable

This error is returned by the network or the LMU if temporarily there are no resources.

10.3.2.9 UnDefinedError

This error is returned by the LMU or the network when any other error type is not applicable.

10.4 Operations and errors implementation

For the actual implementation of location services, operations and errors have to be defined by value. The following ASN.1 module, imports operation types from the ASN.1 module described in subclause 9.2 and operation and error types from MAP. It defines operations by allocating operations and errors a local value. For the involved operations and errors the same local values as in MAP are allocated. In this ASN.1 module, ASN.1/88 defined in CCITT X.680 recommendations (ASN.1 1997) is used.

LLP-Protocol

— { LLP-Protocol object identifier }

DEFINITIONS ::=

BEGIN

IMPORTS

SystemFailure,

DataMissing,

UnexpectedDataValue,

FacilityNotSupported,

UnknownSubscriber,

FROM MAP-Errors {

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

gsm-Network (1) modules (3) map-Errors (10) version4 (4)}

UnDefinedError

FROM LLP-Errors

— { LLP-Errors object identifier }

StartRIT,

ReportRIT,

StopRIT,

IndicateRITError,

PerformTOA,

StatusQuery,

ResetRequest,

OMRequest,

OMReport,

StatusUpdate

FROM -LLP-Operations

— { LLP-Operations object identifier }

— allocate local values for errors

systemFailure SystemFailure ::= localValue 10

dataMissing DataMissing ::= localValue 11

unexpectedDataValue UnexpectedDataValue ::= localValue 12

facilityNotSupported FacilityNotSupported ::= localValue 13

unknownSubscriber UnknownSubscriber ::= localValue 14

unDefinedError UnDefinedError ::= localValue 50

startRIT StartRIT ::= localValue 10

reportRIT ReportRIT ::= localValue 11

stopRIT StopRIT ::= localValue 12

indicateRITError IndicateRITError ::= localValue 13

performTOA PerformTOA ::= localValue 20

statusQuery statusQuery ::= localValue 30

resetRequest ResetRequest ::= localValue 31

omMngrRequest OMMngrRequest ::= LocalValue 32

omAgntRequest OMAgntRequest ::= LocalValue 33

StatusUpdate StatusUpdate ::= LocalValue 34

END