The C interface is the MSC-HLR interface and the D interface is the VLR-HLR interface. Since the MSC and the VLR are integrated into one entity, the C and D interfaces become one interface physically, while the MSC-VLR becomes the internal interface. The C/D interface is an important interface within the NSS. The MAP messages are transmitted over the C/D interface.
In the previous chapter, the MAP message and codes have been described, where the MAP messages transmitted over the C/D interface include:
- updateLocation
- ForwardCheckSs_Indication
- CancelLocation
- ProvideRoamingNumber
- SendAuthenticationInfo
- SendParameters
- SendImsi
- SendRoutingInfo
- InsertSubscriberData
- DeleteSubscriberData
- Reset
- RegisterSS
- EraseSS
- ActivateSS
- DeactivateSS
- RegisterPassword
- InterrogateSS
- GetPassword
- ReadyForSM
- PurgeMs
2 Signaling Analysis of Typical Flow
Many contents we have learned before will be used in the signaling analysis, including signaling and communication flow. In this section, we set the location updating and call flow as an example to describe the signaling analysis of the C/d interface.
2.1 Call Flow
The call flow of the C/D is as follows:
MSC/VLRMAP HLRMAP
SEND_ROUTING_INFORMATION
---------------------------------------------->
PROVIDE_ROAMING_NUMBER
<----------------------------------------------
PROVIDE_ROAMING_NUMBER_RSP
---------------------------------------------->
SEND_ROUTING_INFORMATION_RSP
<----------------------------------------------
The specific MAP messages on the C/D interface will be described as follows.
1) SEND_ROUTING_INFO
SCCP NAT 4613 00b 000008 000009 09 81 03 0C 16 09 12 06 00 12 04 68 31 28 07 0A 12 08 00 11 04 68 31 09 82 F0 54 62 80 48 04 39 01 00 38 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 60 80 A1 80 06 07 04 00 00 01 00 05 02 00 00 00 00 00
00 00 00 00 00 6C 80 A1 80 02 01 00 02 01 16 30 14 80 07 91 68 31 28 07 10 55 AA 09 0A 01 04 04 04 04 02 80 90 00 00 00 00 00 00
The message analysis is as follows:
SCCP NAT 4613 00b 000008 000009 09(Message type: UDT) 81(Protocol type: Sequential connectionless service of Class 1 messages, message return) 03(Pointer 1 of mandatory variable length part : Called address)0C(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 09(Length of the called address) 12 06 00 12 04 68 31 28 07 0A (Length of the calling address) 12 08 00 11 04 68 31 09 82 F0 54(Subscriber data length) 62(BEGIN) 80 48 (Source transaction identifier)04 39 01 00 38 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 60(Dialogue request tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 05 02 00 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A1(Component type tag: Invoke) 80 02(Invoke tag) 01 00(INVOKE ID)02(Operation code tag)01 16(SEND_ROUTING_INFO) 30(SEQUENCE)14 80(MSISDN) 07 91 68 31 28 07 10 55 AA(IMPL SEQU:A) 09 0A(ENUM:4) 01 04 04(OCTET STRING) 04 04 02 80 90 00 00 00 00 00 00
2) PROVIDE_ROAMING_NO
SCCP NAT 4645 004 000009 000008 09 81 03 0D 16 0A 52 07 00 11 04 68 31 09 82 F1 09 12 06 00 12 04 68 31 28 07 6B 62 80 48 04 38 01 01 8A 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 60 80 A1 80 06 07 04 00 00 01 00 03 02 00 00 00 00 00 00 00 00 00 00 6C 80 A1 80 02 01 04 02 01 04 302B 80 08 64 00 22 07 08 00 51 F5 81 06 91 68 31 09 82 F0 82 07 91 68 31 28 07 10 55 84 04 13 26 00 0D A5 08 0A 01 01 04 03 04 01 A0 00 00 00 00 00 00
Message analysis:
SCCP NAT 4645 004 000009 000008 09(Message type: UDT) 81(Protocol type: Sequential connectionless service of Class 1 messages, message return) 03(Pointer 1 of mandatory variable length part : Called address) 0D(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 0A(Length of the called address) 52 07 00 11 04 68 31 09 82 F1 09 (Length of the calling address) 12 06 00 12 04 68 31 28 07 6B(Subscriber data length) 62(BEGIN) 80 48 (Source transaction identifier) 04 38 01 01 8A 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 60(Dialogue request tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 03 02 00 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A1(Component type tag: Invoke) 80 02(Invoke tag) 01 04(INVOKE ID)02(Operation code tag)01
04(PROVIDE_ROAMING_NO) 30(SEQUENCE)2B 80(IMPL OCTET STRING:0) 08 64 00 22 07 08 00 51 F5 81(IMPL OCTET STRING:1) 06 91 68 31 09 82 F0 82(IMPL OCTET STRING:2) 07 91 68 31 28 07 10 55 84(IMPL OCTET STRING:4) 04 13 26 00 0D A5(IMPL SEQU:5) 08 0A(ENUM:1) 01 01 04(OCTET STRING) 03 04 01 A0 00 00 00 00 00 00
3) PROVIDE_ROAMING_NO_RSP
SCCP NAT 4662 003 000008 000009 09 00 03 0C 16 09 12 06 00 12 04 68 31 28 07 0A 52 07 00 11 04 68 31 09 82 F1 57 64 80 49 04 38 01 01 8A 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 61 80 A1 80 06 07 04 00 00 01 00 03 02 00 00 A2 03 02 01 00 A3 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C 80 A2 80 02 01 04 30 80 02 01 04 04 07 91 68 31 09 82 00 10 00 00 00 00 00 00 00 00
Message analysis:
SCCP NAT 4662 003 000008 000009 09(Message type: UDT) 00(Protocol type: Category 0 basic connectionless service without returned message)03(Pointer 1 of mandatory variable length part : Called address) 0C(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 09(Length of the called address) 12 06 00 12 04 68 31 28 07 0A (Length of the calling address) 52 07 00 11 04 68 31 09 82 F1 57(Subscriber data length) 64(END) 80 49 (Destination transaction identifier) 04 38 01 01 8A 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 61(Dialogue response tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 03 02 00 00 A2(Result tag) 03 02 01 00 A3(Result source diagnosis tag) 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A2(Component type tag: Final returned results) 80 02(Invoke tag) 01 04(INVOKE ID)30(Sequence tag)80 02(Operation code tag) 01 04(PROVIDE_ROAMING_NO)04(OCTET STRING) 07 91 68 31 09 82 00 10 00 00 00 00 00 00 00 00
4) SEND_ROUTING_INFO_RSP
SCCP NAT 4684 009 000009 000008 09 00 03 0D 16 0A 52 08 00 11 04 68 31 09 82 F0 09 52 06 00 12 04 68 31 28 07 63 64 80 49 04 39 01 00 38 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 61 80 A1 80 06 07 04 00 00 01 00 05 02 00 00 A2 03 02 01 00 A3 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C 80 A2 80 02 01 00 30 80 02 01 16 30 13 04 08 64 00 22 07 08 00 51 F5 04 07 91 68 31 09 82 00 10 00 00 00 00 00 00 00 00
Message analysis:
SCCP NAT 4684 009 000009 000008 09(Message type: UDT) 00(Protocol type: Category 0 basic connectionless service without returned message)03(Pointer 1 of mandatory variable length part : Called address) 0D(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 0A(Length of the called address) 52 08 00 11 04 68 31 09 82 F0 09 (Length of the calling address) 52 06 00 12 04 68 31 28 07 63(Subscriber data length) 64(END)80 49 (Destination transaction identifier) 04 39 01 00 38 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 61(Dialogue response tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 05 02 00 00 A2(Result tag) 03 02 01 00 A3(Result source diagnosis tag) 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A2(Component type tag: Final returned results) 80 02(Invoke tag) 01 00(INVOKE ID)30(Sequence tag)80 02(Operation code tag) 01 16(SEND_ROUTING_INFO)30(SEQUENCE) 13 04(OCTET STRING) 08 64 00 22 07 08 00 51 F5 04(OCTET STRING) 07 91 68 31 09 82 00 10 00 00 00 00 00 00 00 00
5.2.2 Location Updating Flow
The location updating flow of the C/D interface is as follows:
VLRMAP
HLRMAP
SEND_AUTHENTICATION_INFO
---------------------------------------------->
SEND_AUTHENTICATION_INFO_RSP
<----------------------------------------------
UPDATE_LOCATION
---------------------------------------------->
INSERT_SUBSCRIBER_DATA
<----------------------------------------------
INSERT_SUBSCRIBER_DATA_ACK
---------------------------------------------->
UPDATE_LOCATION_ACK
<----------------------------------------------
The specific messages on the C/D interface are as follows:
1) SEND_AUTHENTICATION_INFO
SCCP NAT 9100 005 000008 000009 09 81 03 0C 16 09 12 06 00 12 04 68 31 28 07 0A 12 08 00 11 04 68 31 09 82 F0 48 62 80 48 04 39 01 00 2C 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 60 80 A1 80 06 07 04 00 00 01 00 0E 02 00 00 00 00 00 00 00 00 00 00 6C 80 A1 80 02 01 00 02 01 38 04 08 64 00 22 07 08 00 51 F4 00 00 00 00 00 00
Message analysis:
SCCP NAT 9100 005 000008 000009 09(Message type: UDT) 81(Protocol type: Sequential connectionless service of Class 1 messages, message return)03(Pointer 1 of mandatory variable length part : Called address) 0C(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part)09(Length of the called address)12 06 00 12 04 68 31 28 07 0A (Length of the calling address) 12 08 00 11 04 68 31 09 82 F0 48(Subscriber data length)62(BEGIN)80 48 (Source transaction identifier)04 39 01 00 2C 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 60(Dialogue request tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 0E 02 00 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A1(Component type tag: Invoke) 80 02(Invoke tag) 01 00(INVOKE ID) 02(Operation code tag) 01 38(SEND_AUTH_INFO) 04(OCTET STRING) 08 64 00 22 07 08 00 51 F4 00 00 00 00 00 00
2) SEND_AUTHENTICATION_INFO_RSP
SCCP NAT 9137 00d 000009 000008 09 00 03 0D 16 0A 52 08 00 11 04 68 31 09 82 F0 09 52 06 00 12 04 68 31 28 07 E1 64 80 49 04 39 01 00 2C 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 61 80 A1 80 06 07 04 00 00 01 00 0E 02 00 00 A2 03 02 01 00 A3 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C 80 A2 80 02 01 00 30 80 02 01 38 30 81 90 30 22 04 10 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 04 04 02 02 02 02 04 08 03 03 03 03 03 03 03 03 30 22 04 10 11 11 11 11 11...
Message analysis:
SCCP NAT 9137 00d 000009 000008 09(Message type: UDT) 00(Protocol type: Class 0 basic connectionless service without returned message)03(Pointer 1 of mandatory variable length part : Called address) 0D(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 0A(Length of the called address) 52 08 00 11 04 68 31 09 82 F0 09 (Length of the calling address) 52 06 00 12 04 68 31 28 07 E1(Subscriber data length) 64(END) 80 49 (Destination transaction identifier)04 39 01 00 2C 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 61(Dialogue response tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 0E
02 00 00 A2(Result tag) 03 02 01 00 A3(Result source diagnosis tag) 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A2(Component type tag: Final returned results) 80 02(Invoke tag) 01 00(INVOKE ID) 30(Sequence tag)80 02(Operation code tag)01 38(SEND_AUTH_INF) 30(SEQUENCE) 81 90 30 22 04 10 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 04 04 02 02 02 02 04 08 03 03 03 03 03 03 03 03 30 22 04 10 11 11 11 11 11...
3) UPDATE_LOCATION
SCCP NAT 9299 006 000008 000009 09 81 03 0C 16 09 12 06 00 12 04 68 31 28 07 0A 12 08 00 11 04 68 31 09 82 F0 5A 62 80 48 04 39 01 00 2E 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 60 80 A1 80 06 07 04 00 00 01 00 01 02 00 00 00 00 00 00 00 00 00 00 6C 80 A1 80 02 01 00 02 01 02 30 1A 04 08 64 00 22 07 08 00 51 F4 81 06 91 68 31 09 82 F0 04 06 91 68 31 09 82 F1 00 00 00 00 00 00
Message analysis:
SCCP NAT 9299 006 000008 000009 09(Message type: UDT) 81(Protocol type: Sequential connectionless service of Class 1 messages, message return) 03(Pointer 1 of mandatory variable length part : Called address) 0C(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 09(Length of the called address) 12 06 00 12 04 68 31 28 07 0A (Length of the calling address) 12 08 00 11 04 68 31 09 82 F0 5A(Subscriber data length) 62(BEGIN) 80 48 (Source transaction identifier) 04 39 01 00 2E 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 60(Dialogue request tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 01 02 00 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A1(Component type tag: Invoke) 80 02(Invoke tag) 01 00(INVOKE ID) 02(Operation code tag) 01 02(UPDATE_LOCATION) 30(SEQUENCE) 1A 04(OCTET STRING) 08 64 00 22 07 08 00 51 F4 81(IMPL OCTET STRING:1) 06 91 68 31 09 82 F0 04(OCTET STRING) 06 91 68 31 09 82 F1 00 00 00 00 00 00
4) 4 INSERT_SUBSCRIBER_DATA
SCCP NAT 9354 00e 000009 000008 09 00 03 0D 16 0A 52 08 00 11 04 68 31 09 82 F0 09 52 06 00 12 04 68 31 28 07 70 65 80 48 04 38 01 00 CD 49 04 39 01 00 2E 6B 80 28 80 06 07 00 11 86 05 01 01 01 A0 80 61 80 A1 80 06 07 04 00 00 01 00 01 02 00 00 A2 03 02 01 00 A3 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C 80 A1 80 02 01 03 02 01 07 30 1E 8008 64 00 22 07 08 00 51 F4 81 07 91 68 31 28 07 10 45 82 01 01 83 01 00 A6 03 04 01 11 00 00 00 00 00 00
Message analysis:
SCCP NAT 9354 00e 000009 000008 09(Message type: UDT) 00(Protocol type: Class 0 basic connectionless service without returned message) 03(Pointer 1 of mandatory variable length part : Called address) 0D(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 0A(Length of the called address) 52 08 00 11 04 68 31 09 82 F0 09 (Length of the calling address) 52 06 00 12 04 68 31 28 07 70(Subscriber data length) 65(CONTINUE)80 48 (Source transaction identifier) 04 38 01 00 CD 49 (Destination transaction identifier) 04 39 01 00 2E 6B(Dialogue part tag) 80 28(External tag) 80 06(Destination identification tag: Dialogue PDU) 07 00 11 86 05 01 01 01 A0(Single ASN1 tag) 80 61(Dialogue response tag) 80 A1(Context-specific tag) 80 06(Destination identification tag) 07 04 00 00 01 00 01 02 00 00 A2(Result tag) 03 02 01 00 A3(Result source diagnosis tag) 05 A1 03 02 01 00 00 00 00 00 00 00 00 00 6C(Component part tag) 80 A1(Component type tag: Invoke) 80 02(Invoke tag) 01 03(INVOKE ID) 02(Operation code tag) 01 07(INSERT_SUBSCRIBER_DATA) 30(SEQUENCE) 1E 80(IMPL OCTET STRING:0) 08 64 00 22 07 08 00 51 F4 81(IMPL OCTET STRING:1) 07 91 68 31 28 07 10 45 82(IMPL OCTET STRING:2) 01 01 83(IMPL OCTET STRING:3) 01 00 A6(IMPL SEQUENCE) 03 04 01 11 00 00 00 00 00 00
5) INSERT_SUBSCRIBER_DATA_ACK
SCCP NAT 9355 007 000008 000009 09(Message type: UDT) 00(Protocol type: Class 0 basic connectionless service without returned message) 03(Pointer 1 of mandatory variable length part : Called address) 0C(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 09(Length of the called address) 12 06 00 12 04 68 31 28 07 0A (Length of the calling address) 12 08 00 11 04 68 31 09 82 F0 1B(Subscriber data length) 65(CONTINUE)80 48 (Source transaction identifier) 04 39 01 00 2E 49 (Destination transaction identifier) 04 38 01 00 CD 6C(Component part tag) 80 A2(Result tag) 80 02(Invoke tag) 01 03(INVOKE ID)00 00 00 00 00 00
6) UPDATE_LOCATION_ACK
SCCP NAT 9375 000 000009 000008 09 00 03 0D 16 0A 52 08 00 11 04 68 31 09 82 F0 09 52 06 00 12 04 68 31 28 07 23 64 80 49 04 39 01 00 2E 6C 80 A2 80 02 01 00 30 80 02 01 02 04 05 91 68 31 28 07 00 00 00 00 00 00 00 00
Message analysis:
SCCP NAT 9375 000 000009 000008 09(Message type: UDT) 00(Protocol type: Class 0 basic connectionless service without returned message) 03(Pointer 1 of mandatory variable length part : Called address) 0D(Pointer 2 of mandatory variable length part : Calling address ) 16(Start pointer of optional part) 0A(Length of the called address) 52 08 00 11 04 68 31 09 82 F0 09 (Length of the calling address) 52 06 00 12 04 68 31 28 07 23(Subscriber data length) 64(END) 80 49 (Destination transaction identifier)04 39 01 00 2E 6C(Component part tag) 80 A2(Result tag) 80 02(Invoke tag) 01 00(INVOKE ID) 30(SEQUENCE) 80 02(Operation code tag) 01 02(UPDATE_LOCATION) 04(OCTET STRING) 05 91 68 31 28 07 00 00 00 00 00 00 00 00
According to the analysis of the call flow and the location updating flow, it have already been known that the specific MAP service message exists in the TCAP message in the form of component. Generally, the message types of the MAP service correspond to the operation codes in the TCAP message one by one. However, during the message transfer, one message corresponds to an invoke ID. An invoke ID is the only ID of a message during the MAP dialogue. With the differentiation of the invoke ID, a component can be “translated” into the corresponding MAP service message.
3. Brief Introduction to C/D Interface Flow
In the above section, we have set the call flow and normal location updating flow of the C/D interface as an example to describe the common considerations and methods of message analysis. In this section, some other flows and standard MAP error codes on the C/D are described, which will help the signalling analysis greatly.
3.1) cancel location
Figure4-4 Deleting location
After receiving the location updating request, the VLR will judge the location area: For the location area updating in the same VLR, the location updating request will not be sent to the HLR, or the location updating will be requested from the HLR. Before returning the VLR location updating confirmation signal, the HLR will start another process to insert the subscriber data. Furthermore, the location updating confirmation signal returned to the VLR will carry the HLR number.
During the location updating, if a subscriber roams to a new VLR, then in the location register program, the HLR will send a delete command to the VLR so as to delete the data of the subscriber.
3.2) Data updating in VLR
During the location updating, the HLR transfers the data to be inserted into the VLR to the VLR, or due to management reason, the HLR informs the VLR of the new subscriber data (after the OMC modification), including the deletion of the subscriber data.
Figure4-5 Data updating in VLR
3) Procedures for obtaining routing data during call setup
Figure4-6 Procedures for obtaining routing information during call setup
When the HLR returns signal, if the called subscriber activates some supplementary services, the HLR will use the number (forwarding number) of the supplementary services to replace the roaming number.
In the book of Communication Flow, the main communication flow of the whole GSM system has been described in detail, so we emphasize on the interface flow in the signaling analysis.
In Chapter 3, we have already introduced the operation codes used in the MAP. Here, we will introduce the standard error codes of the MAP for the convenience of application in later signaling analysis.
/*Definitions of standard MAP errors*/
UNKNOWN_SUBSCRIBER, /*1*/
UNKNOWN_BASE_STATION, /*2*/
UNKNOWN_MSC, /*3*/
UNKNOWN_LOC_AREA, /*4*/
UNIDENTIFIED_SUBSCRIBER, /*5*/
UNALLOCATED_ROAMING_NUMBER, /*6*/
UNKNOWN_EQUIPMENT, /*7*/
ROAMING_NOT_ALLOWED, /*8*/
ILLEGAL_MS, /*9*/
BEARER_SERVICE_NOT_PROVISIONED, /*10*/
TELESERVICE_NOT_PROVISIONED, /*11*/
INSUFFICIENT_BEARER_CAPABILITIES, /*12*/
CALL_BARRED, /*13*/
FORWARDING_VIOLATION, /*14*/
CUG_REJECT, /*15*/
ILLEGAL_SS_OPERATION, /*16*/
SS_ERROR_STATUS, /*17*/
SS_NOT_AVAILABLE, /*18*/
SS_SUBSCRIPTION_VIOLATION, /*19*/
SS_INCOMPATIBILITY, /*20*/
FACILITY_NOT_SUPPORTED, /*21*/
INVALID_TARGET_BASE_STATION=23, /*23*/
NO_RADIO_RESOURCE_AVAILABLE, /*24*/
NO_HANDOVER_NUMBER_AVAILABLE, /*25*/
SUBSEQUENT_HANDOVER_FAILURE, /*26*/
ABSENT_SUBSCRIBER, /*27*/
BUSY_SUBSCRIBER, /*28*/
NO_SUBSCRIBER_REPLY, /*29*/
RADIO_CONGESTION, /*30*/
IMPOSSIBLE_CALL_COMPLETION, /*31*/
SUBSCRIBER_BUSY_FOR_MT_SMS = \
IMPOSSIBLE_CALL_COMPLETION , // 31
SM_DELIVERY_FAILURE = 32, /*32*/
MESSAGE_WAITING_LIST_FULL, /*33*/
SYSTEM_FAILURE, /*34*/
DATA_MISSING, /*35*/
UNEXPECTED_DATA_VALUE, /*36*/
PASSWORD_REGISTRATION_FAILURE, /*37*/
NEGATIVE_PASSWORD_CHECK, /*38*/
NO_ROAMING_NUMBER_AVAILABLE, /*39*/
TRACING_BUFFER_FULL, /*40*/
NUM_OF_PW_ATTEMPTS_VIOLATION , /*43*/
NUMBER_CHANGED=44, /*44*/
//_FOR_SMS
ILLEGAL_EQUIPMENT 12,
ERROR_IN_MS 50,
SMS_LOWER_LAYERS_CAPABILITIES_NOT_PROVISIONED 51 ,
MEMORY_CAPACITY_EXCEEDED 52 ,
SC_CONGESTION 53 ,
MS_NOT_SC_SUBSCRIBER 54,
INVALID_SME_ADDRESS 55,
ABSENT_SUBSCRIBER_WITHOUT_PARA= 56,
//end of _FOR_SMS
ERROR_CODE_BUTT /*41 end tag*/
4. Summary
This chapter mainly describes the flow and message analysis method of the C/D interface. Through the learning of this chapter, we can conduct the message analysis of the C/D interface with the combination of the flow of the C/D interface.
5. Exercise
In a laboratory, please trace the location updating process of a mobile phone in the link of the C/D interface and analyze the traced information.
