7 Message functional definitions and content

04.113GPPPoint-to-Point (PP) Short Message Service (SMS) support on mobile radio interfaceRelease 1996TS

7.1 General

The notation used is as used in GSM 04.08/clause 9, and each definition includes:

a) A brief description of the message direction and use.

b) A table listing the information elements in the order of their appearance in the message. For each information element the table indicates:

1) A reference to the (sub)clause/Technical Specification describing the information element.

2) The presence requirement indication (M, C, or O) for the IE as defined in GSM 04.07.

3) The format of the information element (T, V, TV, LV, TLV) as defined in GSM 04.07.

4) The length of the information element (or permissible range of lengths), in octets, in the messages.

7.2 Messages for short message or notification transfer on CM

This subclause describes the functional definition and content of the messages sent between two SMC entities.

There are three messages defined: CP‑DATA, CP‑ACK and CP‑ERROR.

7.2.1 CP‑DATA

The CP‑DATA message is sent between an MSC and an MS, in both directions. The message contains the user data to be relayed between the CM‑users, and associated parameters. See table 7.1/ GSM 04.11.

Table 7.1/GSM 04.11: CP‑DATA message content

Information element

Reference

Presence

Format

Length

Protocol discriminator

GSM 04.07

M

V

1/2 octet

Transaction identifier

GSM 04.07

M

V

1/2 octet

Message type

Subclause 8.1.3

M

V

1 octet

CP‑User data

Subclause 8.1.4.1

M

LV

 249 octets

7.2.2 CP‑ACK

The CP‑ACK message is sent between an MSC and an MS, in both directions, and is used to acknowledge the reception of a CP‑DATA message.

See table 7.2/GSM 04.11.

Table 7.2/GSM 04.11: CP‑ACK message content

Information element

Reference

Presence

Format

Length

Protocol discriminator

GSM 04.07

M

V

1/2 octet

Transaction identifier

GSM 04.07

M

V

1/2 octet

Message type

Subclause 8.1.3

M

V

1 octet

7.2.3 CP‑ERROR

The CP‑ERROR message is sent between an MSC and an MS, in both directions, and used to convey error information. See table 7.3/GSM 04.11.

Table 7.3/GSM 04.11: CP‑ERROR message content

Information element

Reference

Presence

Format

Length

Protocol discriminator

GSM 04.07

M

V

1/2 octet

Transaction identifier

GSM 04.07

M

V

1/2 octet

Message type

Subclause 8.1.3

M

V

1 octet

CP‑Cause

Subclause 8.1.4.2

M

V

1 octet

7.3 Messages for short message and notification transfer on SM‑RL

This subclause describes the functional definition and content of the messages sent between two SMR entities.

There are 4 messages defined: RP‑DATA, RP‑SMMA, RP‑ACK and RP‑ERROR.

7.3.1 RP‑DATA

A phase 2 entity shall not reject a RP‑DATA message where both address elements have a length greater than 0.

7.3.1.1 RP‑DATA (Network to Mobile Station)

This message is sent in MSC ‑> MS direction. The message is used to relay the TPDUs. The information elements are in line with GSM 03.40. See table 7.4/GSM 04.11.

Table 7.4/GSM 04.11: RP‑DATA message content

Information element

Reference

Presence

Format

Length

RP‑Message Type

Subclause 8.2.2

M

V

3 bits

RP‑Message Reference

Subclause 8.2.3

M

V

1 octet

RP‑Originator Address

Subclause 8.2.5.1

M

LV

1‑12 octets

RP‑Destination Address

Subclause 8.2.5.2

M

LV

1 octet

RP‑User Data

Subclause 8.2.5.3

M

LV

 233 octets

7.3.1.2 RP‑DATA (Mobile Station to Network)

This message is sent in MS ‑> MSC direction. The message is used to relay the TPDUs. The information elements are in line with GSM 03.40. See table 7.5/GSM 04.11.

Table 7.5/GSM 04.11: RP‑DATA message content

Information element

Reference

Presence

Format

Length

RP‑Message Type

Subclause 8.2.2

M

V

3 bits

RP‑Message Reference

Subclause 8.2.3

M

V

1 octet

RP‑Originator Address

Subclause 8.2.5.1

M

LV

1 octet

RP‑Destination Address

Subclause 8.2.5.2

M

LV

1‑12 octets

RP‑User Data

Subclause 8.2.5.3

M

LV

 233 octets

7.3.2 RP‑SMMA

This message is sent by the mobile station to relay a notification to the network that the mobile has memory available to receive one or more short messages. The information elements are in line with GSM 03.40. See table 7.6/GSM 04.11.

Table 7.6/GSM 04.11: RP‑SMMA message content

Information element

Reference

Presence

Format

Length

RP‑Message Type

Subclause 8.2.2

M

V

3 bits

RP‑Message Reference

Subclause 8.2.3

M

V

1 octet

7.3.3 RP‑ACK

This message is sent between the MSC and the mobile station in both directions and used to relay the acknowledgement of a RP‑DATA or RP‑SMMA message reception. The information elements are in line with GSM 03.40. See table 7.7/GSM 04.11.

Table 7.7/GSM 04.11: RP‑ACK message content

IEI

Information element

Reference

Presence

Format

Length

RP‑Message Type

Subclause 8.2.2

M

V

3 bits

RP‑Message Reference

Subclause 8.2.3

M

V

1 octet

41

RP-User Data

Subclause 8.2.5.3

O

TLV

 234 octets

7.3.4 RP‑ERROR

This message is sent between the MSC and the mobile station in both directions and used to relay an error cause from an erroneous short message or notification transfer attempt. The information elements are in line with GSM 03.40. See table 7.8/GSM 04.11.

The contents of the cause field are given in subclause 8.2.5.4.

Table 7.8/GSM 04.11: RP‑ERROR message content

IEI

Information element

Reference

Presence

Format

Length

RP‑Message Type

Subclause 8.2.2

M

V

3 bits

RP‑Message Reference

Subclause 8.2.3

M

V

1 octet

RP‑Cause

Subclause 8.2.5.4

M

LV

2‑3 octets

41

RP‑User Data

Subclause 8.2.5.3

O

TLV

 234 octets