This document contains information about detach types, GMM causes, SM causes, and location and routing area update reject causes in mobile networks. It lists the decimal values, bit representations, and descriptions for each detach type, GMM cause, and SM cause. It also lists the possible cause values that can be sent in location and routing area update reject messages. Lastly, it provides a brief overview of the protocol layers and some of the messages supported in a mobile network test set for testing purposes.
This document contains information about detach types, GMM causes, SM causes, and location and routing area update reject causes in mobile networks. It lists the decimal values, bit representations, and descriptions for each detach type, GMM cause, and SM cause. It also lists the possible cause values that can be sent in location and routing area update reject messages. Lastly, it provides a brief overview of the protocol layers and some of the messages supported in a mobile network test set for testing purposes.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online from Scribd
This document contains information about detach types, GMM causes, SM causes, and location and routing area update reject causes in mobile networks. It lists the decimal values, bit representations, and descriptions for each detach type, GMM cause, and SM cause. It also lists the possible cause values that can be sent in location and routing area update reject messages. Lastly, it provides a brief overview of the protocol layers and some of the messages supported in a mobile network test set for testing purposes.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online from Scribd
Detach Type (decimal) (bits) Mnemonic 1 001 REQ Re-attach Required 2 010 NREQ Re-attach not Required IMSI Detach (after VLR 3 011 IMSI failure) GMM Cause Information Element GMM Cause Information Element Cause Value (decimal) Cause Value (bits) Cause 2 00000010 IMSI Unknown 3 00000011 Illegal MS 4 00000100 IMSI UKNOWN IN VLR 5 00000101 IMEI NOT ACCEPTED 6 00000110 Illegal ME 7 00000111 GPRS Services Not Allowed 8 00001000 GPRS/Non-GPRS Services Not Allowed 9 00001001 MS Identity Cannot Be Derived 10 00001010 Implicitly Detached 11 00001011 PLMN Not Allowed 12 00001100 Location Area Not Allowed 13 00001101 Roaming Not Allowed In This LA 16 00010000 MSC Temporarily Not Reachable 17 00010001 Network Failure 22 00010110 Congestion 32 00100000 Service Option Not Supported 33 00100001 Requested Service Option Not Subscribed 34 00100010 Service Option Temporarily Out of Order 48 00110000 Retry Upon Entry Into A New Cell 95 01011111 Semantically Incorrect Message 96 01100000 Invalid Mandatory Information 97 01100001 Message Type Nonexistent 98 01100010 Msg Type Incompatible With Prot State 99 01100011 Information Element Nonexistent 100 01100100 Conditional IE Error 101 01100101 Msg Incompatible With Protocol State 111 01101111 Protocol Error, Unspecified SM Cause Information Element SM Cause Information Element Cause Value Cause Value Cause (decimal) (bits) 24 00011000 MBMS Bearer Insufficient For Service 25 00011001 LLC or SNDCP Failure 26 00011010 Insufficient Resources 27 00011011 Missing or Unknown APN 28 00011100 Unknown PDP Address or PDP Type 29 00011101 User Authentication Failed 30 00011110 Activation Rejected By GGSN 31 00011111 Activation Rejected, Unspecified 32 00100000 Service Option Not Supported 33 00100001 Requested Service Opt Not Subscribed 34 00100010 Service Opt Temporarily Out of Order 35 00100011 NSAPI Already Used 36 00100100 Regular Deactivation 37 00100101 QoS Not Accepted 38 00100110 Network Failure 39 00100111 Reactivation Required 40 00101000 Feature Not Supported 41 00101001 Semantic Error In the TFT Operation 42 00101010 Syntactical Error In the TFT Operation 43 00101011 Unknown PDP Context 44 00101100 Semantic Errors in Packet Filter(s) 45 00101101 Syntactical Errors in Packet Filter(s) 46 00101110 PDP Context without TFT Already Activated 47 00101111 Multicast Group Membership Timeout 81 01010001 Invalid Transaction Identifier Value 95 01011111 Semantically Incorrect Message 96 01100000 Invalid Mandatory Information 97 01100001 Msg Type Nonexistent/Not Implemented 98 01100010 Msg Type Incompatible With Protocol State 99 01100011 IE Non-existent or Not Implemented 100 01100100 Conditional IE Error 101 01100101 Msg Not Compatible With Protocol State 111 01101111 Protocol Error, Unspecified APN Restrict Value Incompatible without PDP 112 01110000 Context Location Area Update Reject Cause You can choose which cause value is sent to the mobile station in the Location Area Update Reject message. the reject cause can be either of the followings: 00000010 (#2) - IMSI Unknown 00000011 (#3) - Illegal MS 00000100 (#4) - IMSI Unknown IN VLR 00000101 (#5) - IMEI Not Accepted 00000110 (#6) - Illegal MS 00000111 (#7) - GPRS Services Not Allowed 00001000 (#8) - GPRS Services and Non-GPRS Services Not Allowed 00001001 (#9) - MS Identity Cannot Be Derived By the Network 00001010 (#10) - Implicitly Detached 00001011 (#11) - PLMN not allowed 00001100 (#12) - Location Area not allowed 00001101 (#13) - Roaming not allowed in LA 00001110 (#14) - GPRS Services Not Allowed In This PLMN 00001111 (#15) - No suitable cells in LA 00010000 (#16) - MSC Temporarily Not Reachable 00010001 (#17) - Network Failure 00010100 (#20) - MAC Failure 00010101 (#21) - Synch Failure 00010110 (#22) - Congestion 00010111 (#23) - GSM Authentication Unacceptable 00100000 (#32) - Service Option Not Supported 00100001 (#33) - Requested Service Option Not Subscribed 00100010 (#34) - Service Option Temporarily Out of Order 00100110 (#38) - Call Cannot Be Identified 00101000 (#40) - No PDP Context Activated 00110000 (#48) - Retry Upon Entry Into a New Call 01011111 (#95) - Semantically Incorrect Message 01100000 (#96) - Invalid Mandatory Information 01100001 (#97) - Message Type Non-Existent or Not Implemented 01100010 (#98) - Message Type Not Compatible With the Protocol State 01100011 (#99) - Information Element Non-Existent or Not Implemented 01100100 (#100) - Conditional IE Error 01100101 (#101) - Message Not Compatible With the Protocol State 01101111 (#111) - Protocol Error, Unspecified Routing Area Update Reject Cause You can choose which cause value is sent to the mobile station in the Routing Area Update Reject message. You can choose the following reject causes from the front panel: 00000010 (#2) - IMSI Unknown inHLR 00000011 (#3) - Illegal MS 00000011 (#4) - IMSI Unknown in VLR 00000011 (#5) - IMEI Not Accepted 00000110 (#6) - Illegal ME 00000111 (#7) - GPRS Services Not Allowed 00001000 (#8) - GPRS/Non-GPRS Services Not Allowed 00001001 (#9) - MS Identity Cannot Be Derived 00001010 (#10) - Implicitly Detached 00001011 (#11) - PLMN not allowed 00001100 (#12) - Location Area not allowed 00001101 (#13) - Roaming not allowed in LA 00001110 (#14) - GPRS Services Not Allowed In This PLMN 00001111 (#15) - No suitable cells in LA 00010000 (#16) - MSC Temporarily Not Reachable 00010001 (#17) - Network Failure 00010100 (#20) - MAC Failure 00010101 (#21) - Synch Failure 00010110 (#22) - Congestion 00010111 (#23) - GSM Authentication Unacceptable 00100000 (#32) - Service Option Not Supported 00100001 (#33) - Requested Service Option Not Subscribed 00100010 (#34) - Service Option Temporarily Out of Order 00100110 (#38) - Call Cannot Be Identified 00101000 (#40) - No PDP Context Activated 00110000 (#48) - Retry Upon Entry Into a New Call 01011111 (#95) - Semantically Incorrect Message 01100000 (#96) - Invalid Mandatory Information 01100001 (#97) - Message Type Non-Existent or Not Implemented 01100010 (#98) - Message Type Not Compatible With the Protocol State 01100011 (#99) - Information Element Non-Existent or Not Implemented 01100100 (#100) - Conditional IE Error 01100101 (#101) - Message Not Compatible With the Protocol State 01101111 (#111) - Protocol Error, Unspecified Protocol Layers and Messages Last updated: December 3, 2008 This section is only applicable to the lab applications. This section outlines in a very general sense, the test set's support for individual protocol layers, the procedures associated with them, and their respective messages. Messages not included here may be supported. Certain parameters of messages included here may not be supported. Observation Point 1 - LAPDm Over-the-Air Messages The Link Access Procedure on the Dm channel (LAPDm) is the protocol for use by the data link layer on the radio interface. The frame structure and procedures for proper operation of the LAPDm are described in GSM 04.06. Operating Considerations This observation point is not enabled by default. If you want to capture LAPDm messages using the WPA, you should enable LAPDm in the Test Set Message Filter Settings. Observation Point 2- RLC/MAC Over-the-Air Messages This layer contains two functions: The Radio Link Control function provides a radio-solution- dependent reliable link. The Medium Access Control function controls the access signaling (request and grant) procedures for the radio channel, and the mapping of LLC frames onto the GSM physical channel. RLC/MAC is defined in GSM 04.60 for functions operating on the Packet Data Channel (PDCH), and in GSM 04.08 for functions operating on the CCCH (Common Control Channel). Messages Uplink TBF establishment messages Message Reference Supported Uplink TBF establishment messages Message Reference Supported Packet Channel Request 04.60/11.2.5 No EGPRS Packet Channel Request 04.60/11.2.5a No Packet Queuing Notification 04.60/11.2.15 No Packet Resource Request 04.60/11.2.16 Yes Packet Uplink Assignment 04.60/11.2.29 Yes Additional MS Radio Access Capabilities 04.60/11.2.32 Yes Downlink TBF establishment messages Message Reference Supported Packet Downlink Assignment 04.60/11.2.7 Yes TBF release messages Message Reference Supported Packet TBF Release 04.60/11.2.26 Yes Packet Paging messages Message Reference Supported Packet Paging Request 04.60/11.2.10 Yes RLC messages Message Reference Supported Packet Downlink Ack/Nack 04.60/11.2.6 Yes EGPRS Packet Downlink Ack/Nack 04.60/11.2.6a Yes Packet Uplink Ack/Nack 04.60/11.2.28 Yes Miscellaneous messages Message Reference Supported Packet Control Acknowledgment 04.60/11.2.2 Yes Packet Cell Change Failure 04.60/11.2.3 No Packet Cell Change Order 04.60/11.2.4 Yes Packet Downlink Dummy Control Block 04.60/11.2.8 Yes Packet Uplink Dummy Control Block 04.60/11.2.8b Yes Packet Measurement Report 04.60/11.2.9 Yes Packet Measurement Order 04.60/11.2.9b No Packet Mobile TBF Status 04.60/11.2.9c Yes Packet Enhanced Measurement Report 04.60/11.2.9d Yes Packet PDCH Release 04.60/11.2.11 No Packet Polling Request 04.60/11.2.12 Yes Packet Power Control/Timing Advance 04.60/11.2.13 Yes Packet PRACH Parameters 04.60/11.2.14 No Packet PSI Status 04.60/11.2.17 Yes Packet Timeslot Reconfigure 04.60/11.2.31 Yes Procedures Radio Control Link Procedures Incremental Redundancy Retransmission MCS Switching Medium Access Control Procedures PBCCH Medium Access Mode Packet Paging Observation Point 3 - LLC Over-the-Air Messages Logical Link Control (LLC): LLC was designed to be independent of the underlying radio interface protocols in order to allow introduction of alternative GPRS radio solutions with minimum changes to the NSS (Network Subsystem). The procedures for the LLC layer are described in GSM 04.64. Observation Point 4 -GMM/SM Over-the-Air Messages GPRS Mobility Management and Session Management (GMM/SM): This protocol supports mobility management functionality such as GPRS attach, GPRS detach (also applicable to the test application), security, routing area update, location update, PDP context activation, and PDP context deactivation. GMM/SM is defined in GSM 04.08 GMM Messages Message Reference Supported Attach Request 9.4.1 Yes Attach Accept 9.4.2 Yes Attach Complete 9.4.3 Yes Attach Reject 9.4.4 Yes Detach Request 9.4.5 Yes Detach Accept 9.4.6 Yes P-TMSI Reallocation Command 9.4.7 No P-TMSI Reallocation Complete 9.4.8 No Authentication and Ciphering Request 9.4.9 No Authentication and Ciphering Response 9.4.10 No Authentication and Ciphering Reject 9.4.11 No Identity Request 9.4.12 Yes Identity Response 9.4.13 Yes Routing Area Update Request 9.4.14 Yes Routing Area Update Accept 9.4.15 Yes Routing Area Update Complete 9.4.16 Yes Routing Area Update Reject 9.4.17 No GMM Status 9.4.18 No GMM Information 9.4.19 Yes SM Messages Messages Reference Supported Activate PDP Context Request 9.5.1 Yes Activate PDP Context Accept 9.5.2 Yes Activate PDP Context Reject 9.5.3 Yes Request PDP context Activation 9.5.4 Yes Request PDP context Activation Reject 9.5.5 No Modify PDP context Request 9.5.6 No Modify PDP context Accept 9.5.7 No Deactivate PDP context Request 9.5.8 Yes Deactivate PDP context Accept 9.5.9 Yes Activate AA PDP context Request 9.5.10 No Activate AA PDP context Accept 9.5.11 No Activate AA PDP context Reject 9.5.12 No Deactivate AA PDP context Request 9.5.13 No Deactivate AA PDP context Accept 9.5.14 No SM Status 9.5.15 No Observation Point 5- SMS Over-the-Air Messages This observation point captures the messages exchanged between the LLC layer and the SMS sub-layers. See SMS Logging Control for more information. Observation Point 6- GSM L3 Over-the-Air Messages GSM Layer 3 (GSM L3) is defined in GSM 04.08. GSM L3 includes messages that are transmitted over the Common Control Channels. These are: BCCH information (System information messages) PAGCH messages (Immediate assignments) RACH accesses CCCH messages are useful mainly for the purpose of verifying correct channel allocation through the logging of RACH accesses and the related assignments. Note that the System Information Messages will only be visible whenever changes are made to the base station parameters. They are no continuously logged, although they are continuously broadcast on the BCCH. All references in this section are relative to GSM 04.08 or GSM 04.60. Message Reference Supported Location Updating Request 04.08/9.2.15 Yes Location Updating Accept 04.089.2.13 Yes Channel Request 04.08/9.1.8 Yes Immediate Assignment 04.08/9.1.18 Yes Packet System information 1 04.60/11.2.18 Yes Packet System information 13 04.60/11.2.25 Yes Packet System information 2 04.60/11.2.19 Yes Message Reference Supported Packet System information 3 04.60/11.2.20 Yes Packet System information 3bis 04.60/11.2.21 Yes Observation Point 7 - SNDCP Over-the-Air Messages Subnetwork Dependent Convergence Protocol (SNDCP): This transmission functionality maps network-level characteristics onto the characteristics of the underlying network. SNDCP is specified in GSM 04.65. Message Reference Supported SN-DATA 7.2 Yes SN-UNITDATA 7.2 Yes SNDCP-XID 6.8 Yes Observation Point 8 - IP Messages Unlike most of the other protocols, IP only has a single type of message: the datagram. For each datagram, the IP header fields will be displayed by name and the user data will be displayed as a hex dump. For each datagram, the following fields will be displayed: Version Internet Header Length Type of Service Total Length Identification Flags Fragment Offset Time to Live Protocol Header Checksum Source Address - Only the IP address is displayed. No attempt is made to look up the host name Destination Address - Only the IP address is displayed. No attempt is made to look up the host name Data - This contains the user data and any IP options displayed in hex. For a more detailed explanation of these fields, refer to the Internet Engineering Task Force (IETF) document RFC 791.
AUTHENTICATION REJECT: Causes – MAC Failure, SQN (Synch failure) Failure, Fraudulent Network (UE treats the cell as barred),
GSM A interface - BSS Application Part
The A interface is located between the MSC (mobile service switching centre) and the BSS (base station system or radio sub-system). Standard reference: GSM 08-08 § 2, MSC to BSS - Layer 3 The A interface supports several Applications Parts: BSSMAP: Base Station System Management Application Part. DTAP : Direct Transfer Application Part. o RR:Radio Resources. o MM:Mobility Management. o CC:Call Control. BSSMAP messages Standard reference: GSM 08-08 § 3, MSC to BSS - Layer 3 BSSMAP messages (Base Station System Management Application Part), for a GSM A interface located between the MSC (mobile service switching centre) and the BSS (base station system or radio sub-system) are listed and ordered according to their hexadecimal code or their type (abreviation). Message list: hex codes Code Abreviation BSSMAP: message designation 01 ASS-REQ Assignment request. 02 ASS-COM Assignment complete. 03 ASS-FAIL Assignment failure. 20 CLEAR-COM Clear command. 21 CLEAR-COMP Clear complete. 22 CLEAR-REQ Clear request. 23 SAPI-CL-COM SAPI "n" clear request. 24 SAPI-CL-COMP SAPI "n" clear complete. 25 SAPI-REJ SAPI "n" rejected. 30 RESET Reset. 31 RESET-ACK Reset acknowledge. 32 OVERLOAD Overload. 33 TRACE-INV Trace investigation. 34 RESET-CIR Reset circuit. 35 RST-CI-ACK Reset circuit acknowledge. 40 BLOCK Resource blocked. 41 BLOCK-ACK Acknowledgement resource blocked. 42 UNBLOCK Resource un-blocked. 43 UNBLOCK-ACK Acknowledgement resource un-blocked. 50 RESOURC-REQ Resource request. 51 RESOURC-IND Resource indication. 52 PAGING Paging. 53 CYPHER-COM Cypher mode command. 54 CLASS-UPD "Classmark" update. 55 CYPHER-COMP Cypher mode complete. 56 QUEUEING-IN Queuing-in. 57 LAYER-3-INF Layer 3 information. 80 HAND-REQ Handover request. 81 HAND-RQD Handover requested. 82 HND-RQ-ACK Handover request acknowledge. 83 HAND-COM Handover command. 84 HAND-COMP Handover complete. 86 HAND-FAIL Handover failure. 87 HAND-PERFORM Handover performed. 88 HND-CAND-ENQ Handover candidate enquiry. 89 HND-CAND-REQ Handover candidate request. 8A HAND-REQ-REJ Handover request rejection. 8B HAND-DETECT Handover detection. Message list: types Abreviation Code BSSMAP: message designation ASS-COM 02 Assignment complete. ASS-FAIL 03 Assignment failure. ASS-REQ 01 Assignment request. BLOCK 40 Resource blocked. BLOCK-ACK 41 Acknowledgement resource blocked. CLASS-UPD 54 "Classmark" update. CLEAR-COM 20 Clear command. CLEAR-COMP 21 Clear complete. CLEAR-REQ 22 Clear request. CYPHER-COM 53 Cypher mode command. CYPHER-COMP 55 Cypher mode complete. HAND-COM 83 Handover command. HAND-COMP 84 Handover complete. HAND-DETECT 8B Handover detection. HAND-FAIL 86 Handover failure. HAND-PERFORM 87 Handover performed. HAND-REQ 80 Handover request. HAND-REQ-REJ 8A Handover request rejection. HAND-RQD 81 Handover requested. HND-CAND-ENQ 88 Handover candidate enquiry. HND-CAND-REQ 89 Handover candidate request. HND-RQ-ACK 82 Handover request acknowledge. LAYER-3-INF 57 Layer 3 information. OVERLOAD 32 Overload. PAGING 52 Paging. QUEUEING-IN 56 Queuing-in. RESET 30 Reset. RESET-ACK 31 Reset acknowledge. RESET-CIR 34 Reset circuit. RESOURC-IND 51 Resource indication. RESOURC-REQ 50 Resource request. RST-CI-ACK 35 Reset circuit acknowledge. SAPI-CL-COM 23 SAPI "n" clear request. SAPI-CL-COMP 24 SAPI "n" clear complete. SAPI-REJ 25 SAPI "n" rejected. TRACE-INV 33 Trace investigation. UNBLOCK 42 Resource un-blocked. UNBLOCK-ACK 43 Acknowledgement resource un-blocked. DTAP Call Control messages Standard reference: GSM 04-08 § 5, §9.3, §10.4, MSC to BSS - Layer 3 DTAP (Direct Transfer Application Part) Call Control messages , for a GSM A interface located between the MSC (mobile service switching centre) and the BSS (base station system or radio sub-system) are listed and ordered according to their hexadecimal code or their type (abreviation). Message list: hex codes Code Abreviation DTAP Call Control message 01 ALERTING Alerting. 02 CALL-PROCEED Call proceeding. 03 PROGRESS Progress. 05 SETUP Setup. 07 CONNECT Connect. 08 CALL-CONFIRM Call confirmed. 0D EMERG-SETUP Emergency setup. 0F CONNECT-ACK Connect acknowledged. 10 USER-INFO User information. 13 MODIFY-REJ” Modify reject. 17 MODIFY Modify 1F MODIFY-COMP Modify complete. 25 DISCONNECT Disconnect. 2A RELEASE-COMP Release complete. 2D RELEASE Release. 31 STOP-DTMF Stop DTMF. 32 STOP-DTMF-ACK Stop DTMF acknowledge. 34 STATUS-ENQ Status enquiry. 35 START-DTMF Start DTMF. 36 START-DTMF-AC Start DTMF acknowledge. 37 START-DTMF-RE Start DTMF reject. 39 CONGEST-CTRL Congestion control. 3D STATUS Status. 3E NOTIFY Notify. Message list: types Abreviation Code DTAP Call Control message ALERTING 01 Alerting. CALL-CONFIRM 08 Call confirmed. CALL-PROCEED 02 Call proceeding. CONGEST-CTRL 39 Congestion control. CONNECT 07 Connect. CONNECT-ACK 0F Connect acknowledged. DISCONNECT 25 Disconnect. EMERG-SETUP 0D Emergency setup. MODIFY 17 Modify MODIFY-COMP 1F Modify complete. MODIFY-REJ” 13 Modify reject. NOTIFY 3E Notify. PROGRESS 03 Progress. RELEASE 2D Release. RELEASE-COMP 2A Release complete. SETUP 05 Setup. START-DTMF 35 Start DTMF. START-DTMF-AC 36 Start DTMF acknowledge. START-DTMF-RE 37 Start DTMF reject. STATUS 3D Status. STATUS-ENQ 34 Status enquiry. STOP-DTMF 31 Stop DTMF. STOP-DTMF-ACK 32 Stop DTMF acknowledge. USER-INFO 10 User information. DTAP Radio Resources Management messages Standard reference: GSM 04-08 § 3, §9.1, §10.4, MSC to BSS- Layer 3 DTAP (Direct Transfer Application Part) Radio Resources Management messages , for a GSM A interface located between the MSC (mobile service switching centre) and the BSS (base station system or radio sub-system) are listed and ordered according to their hexadecimal code or their type (abreviation). Message list: hex codes Code Abreviation DTAP Radio Resources Management 0A PARTIAL-REL Partial release. 0D CHANNEL-REL Channel release. 0F PART-REL-COM Partial release complete. 10 CHAN-MODIFY Channel mode modify. 12 RR-STATUS RR status. 14 FREQ-REDEF Frequency redefinition. 15 MEASUR-REP Measurement report. 16 CLASSM-CHG Classmark change. 17 CHAN-MOD-ACK Channel mode modify acknowledge. 19 SYS-INFO-T1 System information type 1. 1A SYS-INFO-T2 System information type 2. 1B SYS-INFO-T3 System information type 3. 1C SYS-INFO-T4 System information type 4. 1D SYS-INFO-T5 System information type 5. 1E SYS-INFO-T6 System information type 6. 21 PAG-REQ-T1 Paging request type 1. 22 PAG-REQ-T2 Paging request type 2. 24 PAG-REQ-T3 Paging request type 3. 26 ASS-COMMAND Assignment command. 27 PAGING-REP Paging response. 28 HAND-FAILURE Handover failure. 29 ASS-COMPLETE Assignment complete. 2B HAND-COMM Handover command. 2C HAND-COMP Handover complete. 2D PHYS-INFO Physical layer information. 2F ASS-FAILURE Assignment failure. 32 CIPH-M-COMP Ciphering mode complete. 35 CIPH-M-COMM Ciphering mode command. 39 IMM-ASS-EXT Immediate assignment extended. 3A IMM-ASS-REJ Immediate assignment reject. 3B ADD-ASS Additional assignment. 3F IMM-ASS Immediate assignment. Message list: types Abreviation Code DTAP Radio Resources Management ADD-ASS 3B Additional assignment. ASS-COMMAND 26 Assignment command. ASS-COMPLETE 29 Assignment complete. ASS-FAILURE 2F Assignment failure. CHAN-MOD-ACK 17 Channel mode modify acknowledge. CHAN-MODIFY 10 Channel mode modify. CHANNEL-REL 0D Channel release. CIPH-M-COMM 35 Ciphering mode command. CIPH-M-COMP 32 Ciphering mode complete. CLASSM-CHG 16 Classmark change. FREQ-REDEF 14 Frequency redefinition. HAND-COMM 2B Handover command. HAND-COMP 2C Handover complete. HAND-FAILURE 28 Handover failure. IMM-ASS 3F Immediate assignment. IMM-ASS-EXT 39 Immediate assignment extended. IMM-ASS-REJ 3A Immediate assignment reject. MEASUR-REP 15 Measurement report. PAG-REQ-T1 21 Paging request type 1. PAG-REQ-T2 22 Paging request type 2. PAG-REQ-T3 24 Paging request type 3. PAGING-REP 27 Paging response. PART-REL-COM 0F Partial release complete. PARTIAL-REL 0A Partial release. PHYS-INFO 2D Physical layer information. RR-STATUS 12 RR status. SYS-INFO-T1 19 System information type 1. SYS-INFO-T2 1A System information type 2. SYS-INFO-T3 1B System information type 3. SYS-INFO-T4 1C System information type 4. SYS-INFO-T5 1D System information type 5. SYS-INFO-T6 1E System information type 6. DTAP Mobility Management messages Standard reference: GSM 04-08 § 4, §9.2, §10.4, MSC to BSS - Layer 3 DTAP (Direct Transfer Application Part) Mobility Management messages , for a GSM A interface located between the MSC (mobile service switching centre) and the BSS (base station system or radio sub-system) are listed and ordered according to their hexadecimal code or their type (abreviation). Message list: hex codes Code Abreviation DTAP Mobility Management message 01 IMSI-DET-IND IMSI detach indication. 02 LOC-UPD-ACC Location updating accept. 04 LOC-UPD-REJ Location updating reject. 08 LOC-UPD-REQ Location updating request. 11 AUTHENT-REJ Authentication reject. 12 AUTHENT-REQ Authentication request. 14 AUTHENT-RESP Authentication response. 18 IDENTITY-REQ Identity request. 19 IDENTITY-RESP Identity response. 1A TMSI-REA-COMM Temporary mobile identity reallocation command. 1B TMSI-REA-COMP Temporary mobile identity reallocation complete. 21 CM-SERV-ACC Connection management service accept. 22 CM-SERV-REJ Connection management service reject. 26 CM-SERV-REQ Connection management service request. 28 CM-REESTABL Connection management re-establishment request. 31 MM-STATUS Status. Message list: types Abreviation Code DTAP Mobility Management message AUTHENT-REJ 11 Authentication reject. AUTHENT-REQ 12 Authentication request. AUTHENT-RESP 14 Authentication response. CM-REESTABL 28 Connection management re-establishment request. CM-SERV-ACC 21 Connection management service accept. CM-SERV-REJ 22 Connection management service reject. CM-SERV-REQ 26 Connection management service request. IDENTITY-REQ 18 Identity request. IDENTITY-RESP 19 Identity response. IMSI-DET-IND 01 IMSI detach indication. LOC-UPD-ACC 02 Location updating accept. LOC-UPD-REJ 04 Location updating reject. LOC-UPD-REQ 08 Location updating request. MM-STATUS 31 Status. TMSI-REA-COMM 1A Temporary mobile identity reallocation command. TMSI-REA-COMP 1B Temporary mobile identity reallocation complete.