MM MESSAGE TYPE

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	1
				0	0	1	0		- LOCATION UPDATING ACCEPT	2
				0	1	0	0		- LOCATION UPDATING REJECT	4
				1	0	0	0		- LOCATION UPDATING REQUEST	8
x	x	0	1	-	-	-	-		Security messages:
				0	0	0	1		- AUTHENTICATION REJECT	17
				0	0	1	0		- AUTHENTICATION REQUEST	18
				0	1	0	0		- AUTHENTICATION RESPONSE	20
				1	1	0	0		- AUTHENTICATION FAILURE…………..	28
				1	0	0	0		- IDENTITY REQUEST	24
				1	0	0	1		- IDENTITY RESPONSE	25
				1	0	1	0		- TMSI REALLOCATION COMMAND	26
				1	0	1	1		- TMSI REALLOCATION COMPLETE	27
x	x	1	0	-	-	-	-		Connection management messages:
				0	0	0	1		- CM SERVICE ACCEPT	33
				0	0	1	0		- CM SERVICE REJECT	34
				0	0	1	1		- CM SERVICE ABORT	35
				0	1	0	0		- CM SERVICE REQUEST	36
				0	1	0	1		- CM SERVICE PROMPT	37
				0	1	1	0		- Reserved (see NOTE)	38
				1	0	0	0		- CM RE-ESTABLISHMENT REQUEST	40
				1	0	0	1		- ABORT	41
x	x	1	1	-	-	-	-		Miscellaneous messages:
				0	0	0	0		- MM NULL	48
				0	0	0	1		- MM STATUS	49
				0	0	1	0		- MM INFORMATION	50

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].