8 SEAL Off-network Location Management protocol message formats

24.5453GPPLocation managementProtocol specificationRelease 17Service Enabler Architecture Layer (SEAL)TS

8.1 Functional definitions and contents

8.1.1 General

The following clauses describe the SEAL Off-network Location Management message functional definition and contents. The standard format of a MONP message and the encoding rules for each type of information element as documented in Annex I of 3GPP TS 24.379 [15] is used to describe Off-network location management message and information elements.

8.1.2 Off-network location management message

8.1.2.1 Message definition

This message is used between SEAL location management clients (of UE-1 and UE-2) to send request, response or acknowledgement. The Message Type IE identifies the request, response, or acknowledgement. For contents of the message see Table 8.1.2.1-1.

Message type: Off-network location management message

Direction: UE to other UE

Table 8.1.2.1-1: Off-network location reporting trigger configuration message content

IEI

Information Element

Type/Reference

Presence

Format

Length

Message Type

Message Type

8.2.2

M

V

1

Originating VAL user ID

VAL user ID
8.2.3

M

LV-E

3-x

Terminating VAL user ID

VAL User ID
8.2.3

M

LV-E

3-x

Message ID

Message ID
8.2.6

M

V

16

X

Reply-to message ID

Reply-to message ID

8.2.7

O

TV

17

Z

Location Management Data

Message Data

8.2.4

O

TLV-E

4-x

A

Cause

Cause

8.2.5

O

TLV-E

3-x

8.2 General message format and information elements coding

8.2.1 General

8.2.2 Message type

The purpose of the Message type information element is to identify the type of the message.

The value part of the Message type information element is coded as shown in Table 8.2.2-1.

The Message type information element is a type 3 information element with a length of 1 octet.

Table 8.2.2-1: Message types

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

1

LOCATION REPORTING TRIGGER CONFIGURATION REQUEST

0

0

0

0

0

0

1

0

LOCATION REPORTING TRIGGER CONFIGURATION RESPONSE

0

0

0

0

0

0

1

1

LOCATION MANAGEMENT ACK

0

0

0

0

0

1

0

0

LOCATION REPORT

0

0

0

0

0

1

0

1

LOCATION REPORTING TRIGGER CANCEL REQUEST

0

0

0

0

0

1

1

0

LOCATION REPORTING TRIGGER CANCEL RESPONSE

0

0

0

0

0

1

1

1

LOCATION REQUEST (ON-DEMAND)

0

0

0

0

1

0

0

0

LOCATION RESPONSE (ON-DEMAND)

All other values are reserved.

8.2.3 VAL user ID

The VAL user ID information element is used to indicate a VAL user ID.

The VAL user ID information element is coded as shown in Figure 8.2.3-1 and Table 8.2.3-1.

The VAL user ID information element is a type 6 information element.

8

7

6

5

4

3

2

1

Length of VAL user ID contents

octet 1

octet 2

octet 3

VAL user ID contents

octet n

Figure 8.2.3-1: VAL user ID information element

Table 8.2.3-1: VAL user ID information element

VAL user ID is contained in octet 3 to octet n; Max value of 65535 octets.

8.2.4 Message Data

The Message data information element is used to send message specific data based on Message Type IE;

The Message data information element is coded as shown in Figure 8.2.4-1 and Table 8.2.4-1.

The Message data information element is a type 6 information element.

8

7

6

5

4

3

2

1

Message data IEI

octet 1

Length of Message data contents

octet 2

octet 3

octet 4

Message data contents

octet n

Figure 8.2.4-1: Message data information element

Table 8.2.4-1: Message data information element

Message data is contained in octet 4 to octet n; Max value of 65535 octets.

The Message data information element contains the seal-location-info+xml defined in clause 7.4.

8.2.5 Cause

The Cause information element is used to provide short cause of the failure;

The Cause information element is coded as shown in Figure 8.2.5-1 and Table 8.2.5-1.

The Cause information element is a type 6 information element.

8

7

6

5

4

3

2

1

Message data IEI

octet 1

Length of Message data contents

octet 2

octet 3

Message data contents

octet 127

Figure 8.2.5-1: Cause information element

Table 8.2.5-1: Cause information element

Message data is contained in octet 3 to octet n; Max value of 127 octets.

8.2.6 Message ID

The Message ID information element uniquely identifies a message.

The Message ID information element is coded as shown in Figure 8.2.6-1 and Table 8.2.6-1.

The Message ID information element is a type 3 information element with a length of 16 octets.

8

7

6

5

4

3

2

1

Message ID value

octet 1

octet 16

Figure 8.2.6-1: Message ID value

Table 8.2.6-1: Message ID value

Message ID value (octet 1 to 16)

The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier as specified in IETF RFC 4122 [r4122].

8.2.7 Reply-to message ID

The Reply-to message ID information element is used to associate a message within a conversation that is a reply to an existing message in a conversation.

The Reply-to message ID information element is coded as shown in Figure 8.2.7-1 and Table 8.2.7-1.

The Reply-to message ID information element is a type 3 information element with a length of 17 octets.

8

7

6

5

4

3

2

1

Reply-to message ID IEI

octet 1

Reply-to message ID value

octet 2

octet 17

Figure 8.2.y-1: Reply-to message ID value

Table 8.2.y-1: Reply-to message ID value

Reply-to message ID value (octet 2 to 17)

The Reply-to message ID contains a number uniquely identifying a message. The value is a universally unique identifier as specified in IETF RFC 4122 [r4122].

Annex A (normative):
Timers