10.4 Message Type
24.0083GPPCore network protocolsMobile radio interface Layer 3 specificationRelease 18Stage 3TS
The message type IE and its use are defined in 3GPP TS 24.007 [20]. Tables 10.3/3GPP TS 24.008, 10.4/3GPP TS 24.008, and 10.4a/3GPP TS 24.008 define the value part of the message type IE used in the Mobility Management protocol, the Call Control protocol, and Session management protocol.
Table 10.2/3GPP TS 24.008: Message types for Mobility Management
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
x |
x |
0 |
0 |
– |
– |
– |
– |
Registration messages: |
|
|
0 |
0 |
0 |
1 |
– IMSI DETACH INDICATION |
|||||
|
0 |
0 |
1 |
0 |
– LOCATION UPDATING ACCEPT |
|||||
|
0 |
1 |
0 |
0 |
– LOCATION UPDATING REJECT |
|||||
|
1 |
0 |
0 |
0 |
– LOCATION UPDATING REQUEST |
|||||
|
x |
x |
0 |
1 |
– |
– |
– |
– |
Security messages: |
|
|
0 |
0 |
0 |
1 |
– AUTHENTICATION REJECT |
|||||
|
0 |
0 |
1 |
0 |
– AUTHENTICATION REQUEST |
|||||
|
0 |
1 |
0 |
0 |
– AUTHENTICATION RESPONSE |
|||||
|
1 |
1 |
0 |
0 |
– AUTHENTICATION FAILURE………….. |
|||||
|
1 |
0 |
0 |
0 |
– IDENTITY REQUEST |
|||||
|
1 |
0 |
0 |
1 |
– IDENTITY RESPONSE |
|||||
|
1 |
0 |
1 |
0 |
– TMSI REALLOCATION COMMAND |
|||||
|
1 |
0 |
1 |
1 |
– TMSI REALLOCATION COMPLETE |
|||||
|
x |
x |
1 |
0 |
– |
– |
– |
– |
Connection management messages: |
|
|
0 |
0 |
0 |
1 |
– CM SERVICE ACCEPT |
|||||
|
0 |
0 |
1 |
0 |
– CM SERVICE REJECT |
|||||
|
0 |
0 |
1 |
1 |
– CM SERVICE ABORT |
|||||
|
0 |
1 |
0 |
0 |
– CM SERVICE REQUEST |
|||||
|
0 |
1 |
0 |
1 |
– CM SERVICE PROMPT |
|||||
|
0 |
1 |
1 |
0 |
– Reserved (see NOTE) |
|||||
|
1 |
0 |
0 |
0 |
– CM RE-ESTABLISHMENT REQUEST |
|||||
|
1 |
0 |
0 |
1 |
– ABORT |
|||||
|
x |
x |
1 |
1 |
– |
– |
– |
– |
Miscellaneous messages: |
|
|
0 |
0 |
0 |
0 |
– MM NULL |
|||||
|
0 |
0 |
0 |
1 |
– MM STATUS |
|||||
|
0 |
0 |
1 |
0 |
– MM INFORMATION |
|||||
NOTE: This value was allocated but never used in earlier phases of the protocol.
When the radio connection started with a core network node of earlier than R99, bit 8 shall be set to 0 and bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007 [20].
When the radio connection started with a core network node of R’99 or later, bits 7 and 8 are reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007 [20].
Table 10.3/3GPP TS 24.008: Message types for Call Control and call related SS messages
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
x |
x |
0 |
0 |
0 |
0 |
0 |
0 |
escape to nationally specific |
|
|
message types; see 1) below |
|||||||||
|
x |
x |
0 |
0 |
– |
– |
– |
– |
Call establishment messages: |
|
|
0 |
0 |
0 |
1 |
– ALERTING |
|||||
|
1 |
0 |
0 |
0 |
– CALL CONFIRMED |
|||||
|
0 |
0 |
1 |
0 |
– CALL PROCEEDING |
|||||
|
0 |
1 |
1 |
1 |
– CONNECT |
|||||
|
1 |
1 |
1 |
1 |
– CONNECT ACKNOWLEDGE |
|||||
|
1 |
1 |
1 |
0 |
– EMERGENCY SETUP |
|||||
|
0 |
0 |
1 |
1 |
– PROGRESS |
|||||
|
0 |
1 |
0 |
0 |
– CC-ESTABLISHMENT |
|||||
|
0 |
1 |
1 |
0 |
– CC-ESTABLISHMENT CONFIRMED |
|||||
|
1 |
0 |
1 |
1 |
– RECALL |
|||||
|
1 |
0 |
0 |
1 |
– START CC |
|||||
|
0 |
1 |
0 |
1 |
– SETUP |
|||||
|
x |
x |
0 |
1 |
– |
– |
– |
– |
Call information phase messages: |
|
|
0 |
1 |
1 |
1 |
– MODIFY |
|||||
|
1 |
1 |
1 |
1 |
– MODIFY COMPLETE |
|||||
|
0 |
0 |
1 |
1 |
– MODIFY REJECT |
|||||
|
0 |
0 |
0 |
0 |
– USER INFORMATION |
|||||
|
1 |
0 |
0 |
0 |
– HOLD |
|||||
|
1 |
0 |
0 |
1 |
– HOLD ACKNOWLEDGE |
|||||
|
1 |
0 |
1 |
0 |
– HOLD REJECT |
|||||
|
1 |
1 |
0 |
0 |
– RETRIEVE |
|||||
|
1 |
1 |
0 |
1 |
– RETRIEVE ACKNOWLEDGE |
|||||
|
1 |
1 |
1 |
0 |
– RETRIEVE REJECT |
|||||
|
x |
x |
1 |
0 |
– |
– |
– |
– |
Call clearing messages: |
|
|
0 |
1 |
0 |
1 |
– DISCONNECT |
|||||
|
1 |
1 |
0 |
1 |
– RELEASE |
|||||
|
1 |
0 |
1 |
0 |
– RELEASE COMPLETE |
|||||
|
x |
x |
1 |
1 |
– |
– |
– |
– |
Miscellaneous messages: |
|
|
1 |
0 |
0 |
1 |
– CONGESTION CONTROL |
|||||
|
1 |
1 |
1 |
0 |
– NOTIFY |
|||||
|
1 |
1 |
0 |
1 |
– STATUS |
|||||
|
0 |
1 |
0 |
0 |
– STATUS ENQUIRY |
|||||
|
0 |
1 |
0 |
1 |
– START DTMF |
|||||
|
0 |
0 |
0 |
1 |
– STOP DTMF |
|||||
|
0 |
0 |
1 |
0 |
– STOP DTMF ACKNOWLEDGE |
|||||
|
0 |
1 |
1 |
0 |
– START DTMF ACKNOWLEDGE |
|||||
|
0 |
1 |
1 |
1 |
– START DTMF REJECT |
|||||
|
1 |
0 |
1 |
0 |
– FACILITY |
|||||
1): When used, the message type is defined in the following octet(s), according to the national specification.
When the radio connection started with a core network node of earlier than R99, bit 8 shall be set to 0 and bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007 [20].
When the radio connection started with a core network node of R’99 or later, bits 7 and 8 are reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007 [20].
Table 10.4/3GPP TS 24.008: Message types for GPRS mobility management
|
Bits |
|||||||||
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
0 |
0 |
– |
– |
– |
– |
– |
– |
Mobility management messages |
|
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
Attach request |
|
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
Attach accept |
|
|
0 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
Attach complete |
|
|
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
Attach reject |
|
|
0 |
0 |
0 |
0 |
0 |
1 |
0 |
1 |
Detach request |
|
|
0 |
0 |
0 |
0 |
0 |
1 |
1 |
0 |
Detach accept |
|
|
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
Routing area update request |
|
|
0 |
0 |
0 |
0 |
1 |
0 |
0 |
1 |
Routing area update accept |
|
|
0 |
0 |
0 |
0 |
1 |
0 |
1 |
0 |
Routing area update complete |
|
|
0 |
0 |
0 |
0 |
1 |
0 |
1 |
1 |
Routing area update reject |
|
|
0 |
0 |
0 |
0 |
1 |
1 |
0 |
0 |
Service Request |
|
|
0 |
0 |
0 |
0 |
1 |
1 |
0 |
1 |
Service Accept |
|
|
0 |
0 |
0 |
0 |
1 |
1 |
1 |
0 |
Service Reject |
|
|
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
P-TMSI reallocation command |
|
|
0 |
0 |
0 |
1 |
0 |
0 |
0 |
1 |
P-TMSI reallocation complete |
|
|
0 |
0 |
0 |
1 |
0 |
0 |
1 |
0 |
Authentication and ciphering req |
|
|
0 |
0 |
0 |
1 |
0 |
0 |
1 |
1 |
Authentication and ciphering resp |
|
|
0 |
0 |
0 |
1 |
0 |
1 |
0 |
0 |
Authentication and ciphering rej |
|
|
0 |
0 |
0 |
1 |
1 |
1 |
0 |
0 |
Authentication and ciphering failure |
|
|
0 |
0 |
0 |
1 |
0 |
1 |
0 |
1 |
Identity request |
|
|
0 |
0 |
0 |
1 |
0 |
1 |
1 |
0 |
Identity response |
|
|
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
GMM status |
|
|
0 |
0 |
1 |
0 |
0 |
0 |
0 |
1 |
GMM information |
|
Table 10.4a/3GPP TS 24.008: Message types for GPRS session management
|
Bits |
|||||||||
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
0 |
1 |
– |
– |
– |
– |
– |
– |
Session management messages |
|
|
0 |
1 |
0 |
0 |
0 |
0 |
0 |
1 |
Activate PDP context request |
|
|
0 |
1 |
0 |
0 |
0 |
0 |
1 |
0 |
Activate PDP context accept |
|
|
0 |
1 |
0 |
0 |
0 |
0 |
1 |
1 |
Activate PDP context reject |
|
|
0 |
1 |
0 |
0 |
0 |
1 |
0 |
0 |
Request PDP context activation |
|
|
0 |
1 |
0 |
0 |
0 |
1 |
0 |
1 |
Request PDP context activation rej. |
|
|
0 |
1 |
0 |
0 |
0 |
1 |
1 |
0 |
Deactivate PDP context request |
|
|
0 |
1 |
0 |
0 |
0 |
1 |
1 |
1 |
Deactivate PDP context accept |
|
|
0 |
1 |
0 |
0 |
1 |
0 |
0 |
0 |
Modify PDP context request(Network to MS direction) |
|
|
0 |
1 |
0 |
0 |
1 |
0 |
0 |
1 |
Modify PDP context accept (MS to network direction) |
|
|
0 |
1 |
0 |
0 |
1 |
0 |
1 |
0 |
Modify PDP context request(MS to network direction) |
|
|
0 |
1 |
0 |
0 |
1 |
0 |
1 |
1 |
Modify PDP context accept (Network to MS direction) |
|
|
0 |
1 |
0 |
0 |
1 |
1 |
0 |
0 |
Modify PDP context reject |
|
|
0 |
1 |
0 |
0 |
1 |
1 |
0 |
1 |
Activate secondary PDP context request |
|
|
0 |
1 |
0 |
0 |
1 |
1 |
1 |
0 |
Activate secondary PDP context accept |
|
|
0 |
1 |
0 |
0 |
1 |
1 |
1 |
1 |
Activate secondary PDP context reject |
|
|
0 |
1 |
0 |
1 |
0 |
0 |
0 |
0 |
Reserved: was allocated in earlier phases of the protocol |
|
|
0 |
1 |
0 |
1 |
0 |
0 |
0 |
1 |
Reserved: was allocated in earlier phases of the protocol |
|
|
0 |
1 |
0 |
1 |
0 |
0 |
1 |
0 |
Reserved: was allocated in earlier phases of the protocol |
|
|
0 |
1 |
0 |
1 |
0 |
0 |
1 |
1 |
Reserved: was allocated in earlier phases of the protocol |
|
|
0 |
1 |
0 |
1 |
0 |
1 |
0 |
0 |
Reserved: was allocated in earlier phases of the protocol |
|
|
0 |
1 |
0 |
1 |
0 |
1 |
0 |
1 |
SM Status |
|
|
0 |
1 |
0 |
1 |
0 |
1 |
1 |
0 |
Activate MBMS Context Request |
|
|
0 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
Activate MBMS Context Accept |
|
|
0 |
1 |
0 |
1 |
1 |
0 |
0 |
0 |
Activate MBMS Context Reject |
|
|
0 |
1 |
0 |
1 |
1 |
0 |
0 |
1 |
Request MBMS Context Activation |
|
|
0 |
1 |
0 |
1 |
1 |
0 |
1 |
0 |
Request MBMS Context Activation Reject |
|
|
0 |
1 |
0 |
1 |
1 |
0 |
1 |
1 |
Request Secondary PDP Context Activation |
|
|
0 |
1 |
0 |
1 |
1 |
1 |
0 |
0 |
Request Secondary PDP Context Activation Reject |
|
|
0 |
1 |
0 |
1 |
1 |
1 |
0 |
1 |
Notification |
|