9 Message Functional Definitions and Contents

09.313GPPBase Station System Application Part LCS Extension (BSSAP-LE)Location Services (LCS)Release 1999TS

For each message there is, in this clause, a table listing the signalling elements in their order of appearance in the transmitted message.

9.1 BSSMAP-LE PERFORM LOCATION REQUEST message

This message is sent to request a location estimate for a target MS and contains sufficient information to enable location according to the required QoS using any positioning method supported by the PLMN and, where necessary, MS. The message is also used to request LCS assistance data transfer to an MS or request a deciphering keys for LCS broadcast assistance data The message can be sent from the BSC to the SMLC and from the MSC to the SMLC.

Table 9.1: BSSMAP-LE PERFORM LOCATION REQUEST message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

Location Type

Location Type

M

TLV

3-4

Cell Identifier

Cell Identifier

M

TLV

3-10

Classmark Information Type 3

Classmark Information Type 3

O

TLV

2-n

LCS Client Type

LCS Client Type

C

TLV

3

Chosen Channel

Chosen Channel

O

TLV

2-n

LCS Priority

LCS Priority

O

TLV

3

LCS QoS

LCS QoS

O

TLV

6

GPS Assistance Data

GPS Assistance Data

O

TLV

3-n

BSSLAP APDU

APDU

O

TLV

2-n

9.1.1 Location Type

This parameter defines the type of locatin information being requested.

9.1.2 Cell Identifier

This parameter gives the current cell location of the target MS. The format shall either be the cell global identification or the LAC plus CI form.

9.1.3 Classmark Information Type 3

This parameter indicates the positioning methods supported by the MS as obtained from the MS Classmark 3 received earlier from the target MS.

9.1.4 LCS Client Type

This parameter defines the type of the originating LCS Client. It shall be included if the Location Type indicates a request for a location estimate and may be included in other cases to assist an SMLC to appropriately prioritize a location request

9.1.5 Chosen Channel

This parameter defines the type of radio channel currently assigned to the target MS.

9.1.6 LCS Priority

This parameter defines the priority of the location request.

9.1.6a LCS QoS

This parameter provides the required Quality of Service for the LCS Request. Quality of Service may include horizontal accuracy, vertical accuracy and allowed response time.

9.1.7 GPS Assistance Data

This parameter identifies the specific GPS assistance data that may be requested.

9.1.8 BSSLAP APDU

This parameter provides additional measurements (e.g. timing advance) for the target MS from the BSC. The measurements are contained inside a BSSLAP APDU.

9.2 BSSMAP-LE PERFORM LOCATION RESPONSE message

This message is sent in response to a BSSMAP-LE Perform Location Request to return a successful location estimate for a target MS or to indicate some failure in obtaining this. The message is also sent in response to a BSSMAP-LE Perform Location Request to return deciphering keys or an indication that LCS assistance data has been successfully delivered to an MS. The message can be sent from the SMLC to the BSC and from the SMLC to the MSC.

Table 9.2: BSSMAP-LE PERFORM LOCATION RESPONSE message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

Location Estimate

Geographic Location

C

TLV

2-22

Positioning Data

Positioning Data

O

TLV

2-n

Deciphering Keys

Deciphering Keys

O

TLV

17

LCS Cause

LCS Cause

O

TLV

3

9.2.1 Location Estimate

This parameter provides a location estimate for the target MS in the case of a successful location attempt.

9.2.2 Positioning Data

This parameter provides additional information for the positioning attempt from the SMLC.

9.2.3 Deciphering Keys

This parameter provides two deciphering keys that can be used to decode LCS broadcast assitance data by the MS. The SMLC shall provide the current deciphering key for the MS’s present location. The SMLC shall also provide the next deciphering key applicable after the current deciphering key.

9.2.4 LCS Cause

The LCS Cause is included if and only if a requested location estimate was not successfully obtained (e.g. location estimate not available), requested deciphering keys were not successfully returned or requested LCS assistance data was not successfully transferred to the MS. The parameter provides the reason for the failure. If the LCS Cause is included, the Location Estimate and Deciphering Key shall not be included.

9.3 BSSMAP-LE PERFORM LOCATION ABORT message

This message is sent by the instigator of a location request to abort the positioning attempt or the request for assistance data or deciphering keys. This message can be sent from the MSC to the SMLC and from the BSC to the SMLC.

Table 9.3: BSSMAP-LE PERFORM LOCATION ABORT message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

LCS Cause

LCS Cause

M

TLV

3

9.3.1 LCS Cause

The LCS Cause provides the reason for the aborting the location attempt.

9.4 BSSMAP-LE LMU CONNECTION REQUEST message

This message is sent to request the establishment of a signaling connection between an LMU and an SMLC. The message can be sent from an SMLC to an MSC and from an MSC to an SMLC.

Table 9.4: BSSMAP-LE LMU CONNECTION REQUEST message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

IMSI

IMSI

M

TLV

3-10

Sender Address

Signaling Point Code

O

TLV

2-n

Security

Security

O

TLV

2-n

Call Number

ISDN Address

O

TLV

3-n

9.4.1 IMSI

This parameter identifies the LMU using its E.212 IMSI.

9.4.2 Sender Address

This parameter provides the SS7 signaling point code for the sender of the message. The parameter is mandatory for message transfer between an MSC and SMLC on the Ls interface.

9.4.3 Security

This parameter indicates if authentication or ciphering are required for the LMU. This parameter may be included for message transfer from an SMLC. If the parameter is absent, authentication and ciphering shall be assumed not to be required.

9.4.4 Call Number

This parameter may be included in an LMU connection request sent by an MSC to enable the SMLC to subsequently establish a TCH to the LMU.

9.5 BSSMAP-LE LMU CONNECTION ACCEPT message

This message is sent in response to a BSSMAP-LE LMU Connection Request message to accept the establishment of a signaling connection between an LMU and an SMLC. The message can be sent from an SMLC to an MSC and from an MSC to an SMLC.

Table 9.5: BSSMAP-LE LMU CONNECTION ACCEPT message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

Security

Security

O

TLV

3

Call Number

ISDN Address

O

TLV

3-n

9.5.1 Security

This parameter indicates if authentication or ciphering are required for the LMU. This parameter may be included for message transfer from an SMLC. If the parameter is absent, authentication and ciphering shall be assumed not to be required.

9.5.2 Call Number

This parameter may be included in an LMU connection accept sent by an MSC to enable the SMLC to subsequently establish a TCH to the LMU.

9.6 BSSMAP-LE LMU CONNECTION REJECT message

This message is sent in response to a BSSMAP-LE LMU Connection Request message to reject the establishment of a signaling connection between an LMU and an SMLC. The message can be sent from an SMLC to an MSC and from an MSC to an SMLC.

Table 9.6: BSSMAP-LE LMU CONNECTION REJECT message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

Reject Cause

LMU Cause

M

TLV

3

9.6.1 Reject Cause

This parameter provides the reason for the rejection of an LMU connection.

9.7 BSSMAP-LE LMU CONNECTION RELEASE message

This message is sent to release a signaling connection between an LMU and an SMLC. The message can be sent from an SMLC to an MSC and from an MSC to an SMLC.

Table 9.7: BSSMAP-LE LMU CONNECTION RELEASE message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

Release Cause

LMU Cause

M

TLV

3

9.7.1 Release Cause

This parameter provides the reason for the release of an LMU connection.

9.8 BSSMAP-LE CONNECTION ORIENTED INFORMATION message

This message is sent in association with an existing signaling connection between an SMLC and another enity to transfer information between the SMLC and other entity belonging to a higher level protocol. The message can be sent from an SMLC to an MSC, from an MSC to an SMLC, from a BSC to an SMLC and from an SMLC to a BSC.

Table 9.8: BSSMAP-LE CONNECTION ORIENTED INFORMATION message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

BSSLAP APDU

APDU

M

TLV

3-n

Segmentation

Segmentation

C

TLV

3

9.8.1 BSSLAP APDU

This parameter contains a BSSLAP message.

9.8.2 Segmentation

This parameter contains segmentation information for a segmented APDU. The parameter shall not include message information. The parameter shall be included if and only if the BSSLAP APDU is segmented.

9.9 BSSMAP-LE CONNECTIONLESS INFORMATION message

This message conveys signaling information associated with a higher protocol level between an SMLC and another entity when there is no existing signaling connection association. The message can be sent from an SMLC to an MSC, from an MSC to an SMLC, from a BSC to an SMLC, from an SMLC to a BSC and from an SMLC to another SMLC.

Table 9.9: BSSMAP-LE CONNECTIONLESS INFORMATION message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

Source Identity

Network Element Identity

M

TLV

3-n

Destination Identity

Network Element Identity

M

TLV

3-n

APDU

APDU

O

TLV

3-n

Segmentation

Segmentation

C

TLV

5

Return Error Request

Return Error Request

O

TLV

2

Return Error Cause

Return Error Cause

O

TLV

3

9.9.1 Source Identity

This parameter identifies the original source of the message. The original source can either be an SMLC or a Type B LMU. The source is identified by association with either a location area or a cell site.

9.9.2 Destination Identity

This parameter identifies the final destination of the message. The final destination can either be an SMLC or a Type B LMU. The destination is identified by association with either a location area or a cell site.

9.9.3 APDU

This parameter contains an embedded APDU. For information transfer between an SMLC and Type B LMU this shall be an LLP APDU. For information transfer between two peer SMLCs, this shall be an SMLCPP APDU.

9.9.4 Segmentation

This parameter contains segmentation and message information for a segmented APDU. The parameter shall be included if and only if a segmented APDU is present.

9.9.5 Return Error Request

This parameter may be included to request an error response if BSSMAP-LE message cannot be delivered successfully to its final destination. This parameter shall not be included if the Return Error cause is present.

9.9.6 Return Error Cause

This parameter indicates an error response for a BSSMAP-LE connectionless information message that could not be delivered to its final destination. The APDU should be present and the same as the APDU in the original undelivered message. The source and destination identies shall be included and the same as the destination and source identities, respectively, in the original undelivered message.

9.10 BSSMAP-LE RESET message

This message is sent to indicate a failure in the sending entity with loss of memory of LMU connections and location service transactions that were established or were being established. The message may be sent from an SMLC to an MSC or BSC and from an MSC or BSC to an SMLC.

This message is sent as a connectionless SCCP message.

Table 9.10: BSSMAP-LE RESET message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1

Cause

Cause

M

TLV

3-4

9.11 BSSMAP-LE RESET ACKNOWLEDGE message

This message is sent in response to a Reset message to indicate that references and resources associated with LMU connections and location service transactions towards the entity sending the Reset have been released. The message may be sent from an SMLC to an MSC or BSC and from an MSC or BSC to an SMLC.

This message is sent as a connectionless SCCP message.

Table 9.11: BSSMAP-LE RESET ACKNOWLEDGE message content

Information element

Type / Reference

Presence

Format

Length in octets

Message type

Message Type

M

V

1