移動(dòng)通信網(wǎng) 首頁(yè) 搜索新聞問(wèn)答論壇人才博客通信圈

善于提問(wèn)，勤于回答，你也是專家

問(wèn)題已開啟 (普通問(wèn)題)

WCDMA原因值詳解

幫忙提供一份WCDMA的原因值詳解，或者提供對(duì)應(yīng)的協(xié)議也可以，謝謝�。�！

提問(wèn)者: 無(wú)線優(yōu)化提問(wèn)時(shí)間: 2013-12-18

	我要回答：

	請(qǐng)先登錄或注冊(cè) 再回答問(wèn)題

更多 CDMA 相關(guān)問(wèn)題

• 現(xiàn)在還有必要學(xué)GSM和CDMA嗎 2020-09-29
• CDMA2000網(wǎng)絡(luò)中如何有效控制用戶的發(fā)射功率實(shí)現(xiàn)具體流程 2020-06-20
• CDMA中的2000是什么意思 2020-05-15
• 華為CDMA主控板登錄不了 2019-11-17
• 聯(lián)通wCDMA專項(xiàng)日常優(yōu)化中興中興資料 2019-10-18
• WCDMA導(dǎo)頻功率是什么 2019-08-13
• WCDMA室內(nèi)分布系統(tǒng)拿什么軟件畫圖 2019-06-12
• 有沒有關(guān)于WCDMA所以資料 2019-05-16

問(wèn)題答案 ( 3 )

原因值指的是什么��？

回答者： yinkai_feng 回答時(shí)間：2013-12-18 17:11

CAUSE VALUE

無(wú)線優(yōu)化 2013-12-18 17:12

詳細(xì)可參考24008 附錄H，文檔地址：http://www.etsi.org/deliver/etsi_ts/124000_124099/124008/10.10.00_60/

H.1 Normal class

H.1.1 Cause No. 1 "unassigned (unallocated) number"

This cause indicates that the destination requested by the mobile station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).

H.1.2 Cause No. 3 "no route to destination"

This cause indicates that the called user cannot be reached because the network through which the call has been routed does not serve the destination desired.

H.1.3 Cause No. 6 "channel unacceptable"

This cause indicates the channel most recently identified is not acceptable to the sending entity for use in this call.

H.1.4 Cause No. 8 "operator determined barring"

This cause indicates that the MS has tried to access a service that the MS's network operator or service provider is not prepared to allow.

H.1.5 Cause No.16 "normal call clearing"

This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared.
Under normal situations, the source of this cause is not the network.

H.1.6 Cause No.17 "user busy"

This cause is used when the called user has indicated the inability to accept another call.
It is noted that the user equipment is compatible with the call.

H.1.7 Cause No. 18 "no user responding"

This cause is used when a user does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated (defined by the expiry of either timer T303 or T310).

H.1.8 Cause No. 19 "user alerting, no answer"

This cause is used when a user has provided an alerting indication but has not provided a connect indication within a prescribed period of time.

H.1.9 Cause No. 21 "call rejected"

This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible.

H.1.10 Cause No. 22 "number changed"

This cause is returned to a calling mobile station when the called party number indicated by the calling mobile station is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this capability, cause No. 1 "unassigned (unallocated) number" shall be used.

H.1.10a Cause No. 24 "call rejected due to feature at the destination"

This cause is returned when the call is rejected due to a feature at the destination, e.g. Anonymous Call Rejection. This cause is only generated by the network. This cause is not generated by the MS.

H.1.11 Cause No. 25 "pre-emption"

This cause is returned to the network when a mobile station clears an active call which is being pre-empted by another call with higher precedence.

H.1.12 Cause No. 26 "non-selected user clearing"

Not supported. Treated as cause no. 31.

H.1.13 Cause No. 27 "destination out of order"

This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

H.1.14 Cause No. 28 "invalid number format (incomplete number)"

This cause indicates that the called user cannot be reached because the called party number is not a valid format or is not complete.

H.1.15 Cause No. 29 "facility rejected"

This cause is returned when a facility requested by user can not be provided by the network.

H.1.16 Cause No. 30 "response to STATUS ENQUIRY"

This cause is included in STATUS messages if the message is sent in response to a STATUS ENQUIRY message. See also subclause 5.5.3.

H.1.17 Cause No. 31 "normal, unspecified"

This cause is used to report a normal event only when no other cause in the normal class applies.

H.2 Resource unavailable class

H.2.1 Cause No. 34 "no circuit/channel available"

This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

H.2.2 Cause No. 38 "network out of order"

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately re-attempting the call is not likely to be successful.

H.2.3 Cause No. 41 "temporary failure"

This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the mobile station may wish to try another call attempt almost immediately.

H.2.4 Cause No. 42 "switching equipment congestion"

This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.

H.2.5 Cause No. 43 "access information discarded"

This cause indicates that the network could not deliver access information to the remote user as requested; i.e., a user-to-user information, low layer compatibility, high layer compatibility, or sub-address as indicated in the diagnostic.
It is noted that the particular type of access information discarded is optionally included in the diagnostic.

H.2.6 Cause No. 44 "requested circuit/channel not available"

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.

H.2.7 Cause No. 47 "resource unavailable, unspecified"

This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

H.3 Service or option not available class

H.3.1 Cause No. 49 "quality of service unavailable"

This cause indicates to the mobile station that the requested quality of service, as defined in ITU-T Recommendation X.213, cannot be provided.

H.3.2 Cause No. 50 "Requested facility not subscribed"

This cause indicates that the requested supplementary service could not be provided by the network because the user has no completed the necessary administrative arrangements with its supporting networks.

H.3.3 Cause No. 55 "Incoming calls barred within the CUG"

This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed within this CUG.

H.3.4 Cause No. 57 "bearer capability not authorized"

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but the mobile station is not authorized to use.

H.3.5 Cause No. 58 "bearer capability not presently available"

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time.

H.3.6 Cause No. 63 "service or option not available, unspecified"

This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies.

H.3.7 Cause No. 68 "ACM equal to or greater than ACMmax"

This cause is used by the mobile to indicate that call clearing is due to ACM being greater than or equal to ACMmax.

H.4 Service or option not implemented class

H.4.1 Cause No. 65 "bearer service not implemented"

This cause indicates that the equipment sending this cause does not support the bearer capability requested.

H.4.2 Cause No. 69 "Requested facility not implemented"

This cause indicates that the equipment sending this cause does not support the requested supplementary service.

H.4.3 Cause No. 70 "only restricted digital information bearer capability is available"

This cause indicates that one equipment has requested an unrestricted bearer service, but that the equipment sending this cause only supports the restricted version of the requested bearer capability.

H.4.4 Cause No. 79 "service or option not implemented, unspecified"

This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.

H.5 Invalid message (e.g., parameter out of range) class

H.5.1 Cause No. 81 "invalid transaction identifier value"

This cause indicates that the equipment sending this cause has received a message with a transaction identifier which is not currently in use on the MS-network interface.

H.5.2 Cause No. 87 "user not member of CUG"

This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG.

H.5.3 Cause No. 88 "incompatible destination"

This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) which cannot be accommodated.

H.5.4 Cause No. 91 "invalid transit network selection"

For further study. Treated as cause no. 95.

H.5.5 Cause No. 95 "semantically incorrect message"

This cause is used to report receipt of a message with semantically incorrect contents (see subclause 8.8).

H.6 Protocol error (e.g., unknown message) class

H.6.1 Cause No. 96 "invalid mandatory information"

This cause indicates that the equipment sending this cause has received a message with a non-semantical mandatory IE error (see subclause 8.5).

H.6.2 Cause No. 97 "message type non-existent or not implemented"

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.

H.6.3 Cause No. 98 "message type not compatible with protocol state"

This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state (subclause 8.4).

H.6.4 Cause No. 99 "information element non-existent or not implemented"

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

H.6.5 Cause No. 100 "conditional IE error"

This cause indicates that the equipment sending this cause has received a message with conditional IE errors (see subclause 8.7.2).

H.6.6 Cause No. 101 "message not compatible with protocol state"

This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state.

H.6.7 Cause No. 102 "recovery on timer expiry"

This cause indicates that a procedure has been initiated by the expiry of a timer in association with 3GPP TS 24.008 error handling procedures.

H.6.8 Cause No. 111 "protocol error, unspecified"

This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

H.7 Interworking class

H.7.1 Cause No. 127 "interworking, unspecified"

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained.

回答者： wwwmscbsccom 回答時(shí)間：2013-12-18 18:57

大哥，這是GSM網(wǎng)絡(luò)的。。。我要的是WCDMA網(wǎng)絡(luò)的。

無(wú)線優(yōu)化 2013-12-19 14:24

樓主，這個(gè)東西具體的解釋在TS24.008協(xié)議中。

具體的可以見該篇協(xié)議中的附錄H部分，從P631開始的，該協(xié)議已經(jīng)發(fā)到wuxianyouhua@163.com
發(fā)件人是nt_tys@mscbsc.com

希望能幫到你。

中文的相關(guān)解釋如下：
1 Unassigned （unallocated） number（未指定【未分配】號(hào)碼）
3 No route to destination （無(wú)目的地路由
6 Channel unacceptable （不接受的信道）
8 Operator determined barring（運(yùn)營(yíng)商確定阻塞）
16 Normal call clearing （正常呼叫清除）
17 User busy （用戶忙）
18 No user responding（無(wú)用戶響應(yīng)）
19 User alerting, no answer（用戶振鈴，無(wú)應(yīng)答
21 Call rejected（呼叫被拒絕）
22 Number changed（號(hào)碼改變
25 Pre-emption（預(yù)占）
26 Non selected user clearing（非選定用戶清除）
27 Destination out of order（目的地混亂）
28 Invalid number format （incomplete number）（無(wú)效號(hào)碼格式【數(shù)字不完全】）
29 Facility rejected （設(shè)備被拒絕）
30 Response to STATUS ENQUIRY（對(duì)STATUS ENQUIRY作出響應(yīng)）
31 Normal, unspecified （not logged）（正常，未指定【未記錄】）
34 No circuit/channel available （無(wú)可用電路/ 信道）
38 Network out of order （網(wǎng)絡(luò)故障）
41 Temporary failure （臨時(shí)故障）
42 Switching equipment congestion（交換設(shè)備擁塞）
43 Access information discarded （訪問(wèn)信息丟棄）
44 Requested circuit/channel available（請(qǐng)求電路/ 信道不可用）
47 Resources unavailable, unspecified （資源不可用，未指定）
49 Quality of service unavailable（服務(wù)質(zhì)量不可用）
50 Requested facility not subscribed（請(qǐng)求設(shè)備未預(yù)訂）
55 Incoming calls barred within the CUG（CUG內(nèi)的來(lái)電阻斷）
57 Bearer capability not authorized（承載容量未批準(zhǔn)）
58 Bearer capability not presently available（承載容量當(dāng)前不可用）63 Service or option not available, unspecified（服務(wù)或選擇不可用，未指定）
65 Bearer service not implemented（承載服務(wù)未實(shí)施）
68 ACM equal to or greater than ACMmax （ACM等同或大于ACMmax）
69 Requested facility not implemented（請(qǐng)求設(shè)備未實(shí)施）
70 Only restricted digital information bearer capability isavailable （只有有限的數(shù)字信息承載容量）
79 Service or option not available, unspecified（服務(wù)或選擇不可用，未指定）
81 Invalid transaction identifier value（無(wú)效交易標(biāo)識(shí)符值）
87 User not member of CUG（用戶非CUG成員）
88 Incompatible destination （不兼容的目的地）
91 Invalid transit network selection（無(wú)效轉(zhuǎn)接網(wǎng)選擇）
95 Semantically incorrect message（語(yǔ)義錯(cuò)誤消息）
96 Invalid mandatory information（無(wú)效強(qiáng)制信息）
97 Message type non-existent or not implemented（消息類型不存在或未實(shí)施）
98 Message type not compatible with the protocol state（消息類型與協(xié)議狀態(tài)不兼容）
99 Information element non-existent or not implemented（信息元素不存在或未實(shí)施）
100 Conditional IE error（條件IE錯(cuò)誤
101 Message not compatible with protocol state（消息與協(xié)議狀態(tài)不兼容）
102 Recovery on timer expiry （計(jì)時(shí)器到時(shí)恢復(fù)）
111 Protocol error, unspecified （協(xié)議錯(cuò)誤，未指定）
127 Interworking, unspecified（互通，未指定）

回答者： OscarDon 回答時(shí)間：2013-12-18 21:01

大哥，你和前面的兄弟一樣，發(fā)的是DTAP的，我需要的是RANAP的，已經(jīng)找到了，謝謝�。�！

無(wú)線優(yōu)化 2013-12-19 16:16

未找到滿意答案？

移動(dòng)通信論壇，提供全面的通信資料、技術(shù)支持！

最新緊急招聘通信職位

熱點(diǎn)問(wèn)題


聯(lián)系我們 - 問(wèn)通信專家	Powered by MSCBSC 移動(dòng)通信網(wǎng) © 2006 -