Table 8.2/3GPP TS 24.011: Content and coding of CP-Cause
Cause value Cause nr. Cause 7 6 5 4 3 2 1 0 0 1 0 0 0 1 0 0 1 0 1 1 0 1 0 1 0 0 0 1 1 0 1 1 1 1 1 1 1 0 0 0 0 0 1 1 0 0 0 0 1 1 1 0 0 0 1 0 1 1 0 0 0 1 1 1 1 0 1 1 1 1 # 17 22 81 95 96 97 98 99 111 Network failure Congestion Invalid Transaction Identifier value Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message not compatible with the short message protocol state Information element non-existent or not implemented Protocol error, unspecified All other cause values shall be treated as cause number 111.
Rp
8.2.5.4 RP-Cause element
This element is a variable length element always included in the RP-ERROR message, conveying a negative result of a RP-DATA message transfer attempt or RP-SMMA notification attempt. The element contains a cause value and optionally a diagnostic field giving further details of the error cause.
The coding of the cause value is given in table 8.4/3GPP TS 24.011. The mapping between error causes in 3GPP TS 24.011 and 3GPP TS 29.002 (MAP) is specified in 3GPP TS 23.040. Parameters included in the return error from MAP (e.g. System Failure) are mapped directly into the diagnostic field.
8 0 7 1 6 0 5 0 4 0 3 0 2 1 1 0 1 octet 1 octet 1 octet 1 octet *
RP-Cause IEI Length indicator 0 ext Cause value Cause value Diagnostic field
Figure 8.8/3GPP TS 24.011: RP-Cause element layout
Table 8.4/3GPP TS 24.011 (part 1): Cause values that may be contained in an RP-ERROR
message
in a mobile originating SM-transfer attempt
Cause value Class value 7 6 5 4 3 2 1 0 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 1 0 1 0 0 0 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 0 1 1 0 0 1 1 1 0 0 0 0 1 1 1 0 1 0 0 1 1 1 1 0 0 1 0 0 1 1 0 0 1 0 1 0 0 1 0 1 0 1 0 1 0 0 1 0 1 1 1 1 0 1 1 0 0 1 0 1 0 0 0 1 0 1 1 0 1 0 0 0 1 1 0 1 1 1 1 1 1 1 0 0 0 0 0 1 1 0 0 0 0 1 1 1 0 0 0 1 0 1 1 0 0 0 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 # 1 8 10 11 21 27 28 29 30 38 41 42 47 50 69 81 95 96 97 98 99 111 127 Cause number Unassigned (unallocated) number Operator determined barring Call barred Reserved Short message transfer rejected Destination out of order Unidentified subscriber Facility rejected Unknown subscriber Network out of order Temporary failure Congestion Resources unavailable, unspecified Requested facility not subscribed Requested facility not implemented Invalid short message transfer reference value Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message not compatible with short message protocol state Information element non-existent or not implemented Protocol error, unspecified Interworking, unspecified Cause All other cause values shall be treated as cause number 41, \
Table 8.4/3GPP TS 24.011 (part 2): Cause values that may be contained in an RP-ERROR
message in a mobile terminating SM-transfer attempt
Cause value Class value 7 6 5 4 3 2 1 0 0 1 0 1 1 0 1 0 1 0 0 0 1 1 0 1 1 1 1 1 1 1 0 0 0 0 0 1 1 0 0 0 0 1 1 1 0 0 0 1 0 1 1 0 0 0 1 1 1 1 0 1 1 1 1 # 22 81 95 96 97 98 99 111 Cause number Memory capacity exceeded Invalid short message transfer reference value Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message not compatible with short message protocol state Information element non-existent or not implemented Protocol error, unspecified Cause All other cause values shall be treated as cause number 111, \
Table 8.4/3GPP TS 24.011 (part 3): Cause values that may be contained in an RP-ERROR
message in a memory available notification attempt
Cause value Class value 7 6 5 4 3 2 1 0 0 1 1 1 1 0 0 1 0 0 1 1 0 0 1 0 1 0 0 1 0 1 0 1 0 1 0 0 1 0 1 1 1 1 1 0 0 0 1 0 1 1 0 1 1 1 1 1 1 1 0 0 0 0 0 1 1 0 0 0 0 1 1 1 0 0 0 1 0 1 1 0 0 0 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 column. # 30 38 41 42 47 69 95 96 97 98 99 111 127 Cause number P T T T T P P P P P P P P Cause type Unknown Subscriber Network out of order Temporary failure Congestion Resources unavailable, unspecified Requested facility not implemented Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message not compatible with short message protocol state Information element non-existent or not implemented Protocol error, unspecified Interworking, unspecified Cause All other cause values are treated as cause number 41, \Each cause is classified as \
HANDOVER FAILURE 同 assgmnet fail
INFORMATION ELEMENT Message Type Cause bss RR Cause Circuit Pool Circuit Pool List GERAN Classmark REFERENCE 3.2.2.1 3.2.2.5 3.2.2.22 3.2.2.45 3.2.2.46 3.2.2.78 DIRECTION BSS-MSC BSS-MSC BSS-MSC TYPE M M O LEN 1 3-4 2 2 V V 2-n 2-n 2 3-n BSS-MSC O (note 1) BSS-MSC O (note 2) BSS-MSC O (note 3) New BSS to Old BSS Information 3.2.2.80 Inter-System Information Talker Priority Codec List (BSS Supported) interface. 3.2.2.81 3.2.2.89 3.2.2.103 BSS-MSC O (note 4) BSS-MSC O (note 5) BSS-MSC BSS-MSC O (note 6) O (note 7) NOTE 1: Shall be included when several circuit pools are present on the BSS MSC NOTE 2: May be included when cause is \to indicate circuit pool preferences. NOTE 3: May be included in case of inter-system handover to GERAN Iu-mode via the E interface, if the \(see 3GPP TS 43.051). NOTE 4: In the case of an external handover, this information element may be included by the target BSS when traffic load information of the target cell is to be sent to the source BSS. NOTE 5: In the case of an inter-system handover from UTRAN or cdma2000 to GSM, this information element may be included by the target BSS when traffic load information of the target cell is to be sent to the source system. NOTE 6: This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. NOTE 7: This information element may be included if the radio access network supports an IP based user plane interface.
HANDOVER REQUIRED REJECT
This message is sent from the MSC to the BSS via the relevant SCCP connection. It indicates to the BSS that the HANDOVER REQUIRED message has not resulted in handover. INFORMATION ELEMENT Message Type Cause bss New BSS to Old BSS Information Talker Priority REFERENCE 3.2.2.1 3.2.2.5 3.2.2.78 3.2.2.89 DIRECTION MSC-BSS MSC-BSS TYPE M M LEN 1 3-4 2-n 2 MSC-BSS O (note 1) MSC-BSS O (note 2) NOTE 1: This information element may be included if received from the target BSS or target system. Its contents shall be equal to the received element. NOTE 2: This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing.
百度搜索“77cn”或“免费范文网”即可找到本站免费阅读全部范文。收藏本站方便下次阅读，免费范文网，提供经典小说综合文库GSM异常事件原因值总结(3)在线全文阅读。
相关推荐：