Cause_value(路测使用)

附录 FGSM 无线资源管理的详尽原因Cause value = 0 Normal release;正常释放indicates that the channel is released because of a normal event.Cause value = 1 Abnormal release, unspecified;异常释放，没有具体说明indicates that the channel is released because of an abnormal event withoutspecifying further reasons.Cause value = 2 Abnormal release, channel unacceptable; indicates that the channel type or channel characteristics are not acceptable.Cause value = 3 Abnormal release, timer expired;indicating that the release is caused by a timer expiry. Cause value = 4 Abnormal release, no activity on radio path; indicating that some supervisory function has detected that channel is notactive.Cause value = 5 Preemptive release;indicates that the channel is released in order to be allocated to a call withpriority (e.g. an emergency call).Cause value = 65 Call already cleared;indicating that a handover is unsuccessful because the connection has beenreleased by the network or the remote user.Cause value = 95 Invalid message, unspecified;See Annex H, section H5.10.Cause value = 97 Message type non-existent or not implemented;See Annex H, section H6.2.Cause value = 98 Message not compatible with call state or message type non-existent or notimplemented;See Annex H, section H6.3Cause value = 100 Invalid information element contents;See Annex H, section H6.5Cause value = 111 Protocol error unspecified;See Annex H, section H6.8.ANNEX G(to Recommendation GSM 04.08)GSM specific cause values for mobility managementG.1 Causes related to MS identificationCause value = 1 Unallocated TMSI.This cause is sent to the MS if the MS identifies itself by a TMSI which is notallocated in the relevant location area and openidentification is notrequested.Cause value = 2 IMSI unknown in HLRThis cause is sent to the MS if the MS is not known (registered) in the HRL.Cause value = 3 Illegal MSThis cause is sent to the MS when the MS does not pass the authenticationcheck, i.e. the SRES received from the MS is different from that generated bythe network.Cause value = 4 IMSI unknown in VLRThis cause is sent to the MS when the given IMSI is not known at the VLR.Cause value = 5 IMEI not acceptedThis cause is sent to the MS if the IMEI given cannot be accepted by thenetwork.G.2 Cause related to subscription optionsCause value = 11 PLMN not allowedThis cause is sent to the MS if it requests location updating in a PLMN wherethe MS, by subscription is not allowed to operate.Cause value = 12 Location Area not allowedThis cause is sent to the MS if it requests location updating in a Locationnarea where the MS, by subscription, is not allowed to operate.G.3 Causes related to PLMN specific network failures and congestionCause value = 17 Network failureThis cause is sent to the MS if the MSC cannot service an MS generated requestbecause of PLMN failures, e.g. problems in MAP.Cause value = 22 CongestionThis cause is sent if the service request cannot be actioned because ofcongestion (e.g. no channel, facility busy/congested etc.) G.4 Causes related to nature of requestCause value = 32 Service option not supportedThis cause is sent when the MS requests a service/facility in the CM SERVICEREQUEST message which is not supported by the PLMN.Cause value = 33 Requested service option not subscribedThis cause ist sent when the MS requests a service option for which it has nosubscription.Cause value = 34 Service option temporarily out of orderThis cause is sent when the MSC cannot service the request because of temporaryoutage of one or more functions required for supporting the service.Cause value = 38 Call cannot be identifiedThis cause is sent when the network cannot identify the call associated with acall re- establishment request.G.5 Causes related to invalid messagesCause value = 96 Mandatory information element error.See Annex H, sect. H.6.1.Cause value = 97 Message type non-existent or not implemented.see Annex H, sect. H.6.2.Cause value = 98 Message non compatible with call state or message type non-existent or notimplemented.see Annex H, sect. H.6.3.Cause value = 99 Information element non-existent or not implemented。

See Annex H, sect. H.6.4.Cause value = 100 Invalid information element contents。

See Annex H, sect. H.6.5.Cause value = 101 Message not compatible with call state。

See Annex H, sect. H.6.6.Cause value = 111 Protocol error, unspecified。

See Annex H, sect. H.6.8.Annex H(to Recommendation GSM 04.08)Cause definitions for Call ControlH.1 Normal classH.1.1 Cause No. 1 "unassigned (unallocated) number"This cause indicates that the destination requested by the Mobile Stationcannot be reached because, although the number is in a valid format, it is notcurrently assigned (allocated).H.1.2 Cause No. 2 "no route to specified transit network" Note: For further studyH.1.3 Cause No. 3 "no route to destination"This cause indicates that the called user cannot be reached because the networkthrough which the call has been routed does not serve the destination desired.H.1.4 Cause No. 6 "channel unacceptable"This cause indicates the channel most recently identified is not acceptable tothe sending entity for use in this call.H.1.5 Cause No. 7 "call awarded and being delivered in an established channel"Note: Not supportedH.1.6 Cause No.16 "normal call clearing"This cause indicates that the call is being cleared because one of the usersinvolved in the call has requested that the call be cleared. Under normal situation, the source of this cause is not thenetwork.H.1.7 Cause No.17 "user busy"This cause is used when the called user has indicated the inability to acceptanother call.It is noted that the user equipment is compatible with the call.H.1.8 Cause No. 18 " no user responding"This cause is used when a user does not respond to a call establishment messagewith either an alerting or connect indication within the prescribed period oftime allocated (defined by the expiry of either timer T303 or T310).H.1.9 Cause No. 19 " user alerting, no answer"This cause is used when a user has provided an alerting indication but has notprovided a connect indication within a prescribed period of time.H.1.10 Cause No. 21 "call rejected"This cause indicates that the equipment sending this cause does not wish toaccept this call, although it could have accepted the call because theequipment sending this cause is neither busy nor incompatible.H.1.11 Cause No. 22 "number changed"This cause is returned to a calling Mobile Station when the called party numberindicated by the calling Mobile Station is no longer assigned. The new calledparty number may optionally be included in the diagnostic field. If a networkdoes not support this capability, cause No. 1 "unassigned (unallocated) number"shall be used.H.1.12 Cause No. 26 "non-selected user clearing"Note: Not supportedH.1.13 Cause No 27 "destination out of order"目标故障This cause indicates that the destination indicated by the Mobile Stationcannot be reached because the interface to the destination is not functioningcorrectly. The term "not functioning correctly" indicates that a signallingmessage was unable to be delivered to the remote user; e.g., a physical layeror 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 calledparty number is not a valid format or is not complete.H.1.15 Cause No. 30 "response to STATUS ENQUIRY"This cause is included in STATUS messages if the message is sent in response toa STATUS ENQUIRY message. See also section 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 thenormal class applies.H.2 Resource unavailable classH.2.1 Cause No. 34 "no circuit/channel available"This cause indicates that there is no appropriatecircuit/channel presentlyavailable 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 thecondition is likely to last a relatively long period of time; e.g., immediatelyre- 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 thecondition is not likely to last a long period of time; e.g.,the Mobile Stationmay 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 isexperiencing 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 tothe remote user as requested; i.e., a user-to-user information, low layercompatibility, high layer compatibility, or sub-address as indicated in thediagnostic.It is noted that the particular type of access information discarded isoptionally 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 requestingentity 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 othercause in the resource unavailable class applies.H.3 Service or option not available classH.3.1 Cause No. 57 "bearer capability not authorized"This cause indicates that the Mobile Station has requested a bearer capabilitywhich is implemented by the equipment which generated this cause but the MobileStation is not authorized to use.H.3.2 Cause No. 58 "bearer capability not presently available"This cause indicates that the Mobile Station has requested a bearer capabilitywhich is implemented by the equipment which generated this cause but which isnot available at this time.H.3.3 Cause No. 63 "service or option not available, unspecified"This cause is used to report a service or option not available event only whenno other cause in the service or option not available class applies.H.4 Service or option not implemented classH.4.1 Cause No. 65 "bearer service not implemented"This cause indicates that the equipment sending this cause does not support thebearer capability requested.H.4.2 Cause No. 66 "channel type not implemented"Note: Not supportedH.4.3 Cause No. 70 "only restricted digital information bearer capability is available"This cause indicates that one equipment has requested an unrestricted bearerservice, but that the equipment sending this cause only supports the restrictedversion 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 onlywhen 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 call reference value"This cause indicates that the equipment sending this cause has received amessage with a call reference which is not currently in use on the MS-networkinterface.H.5.2 Cause No. 82 "identified channel does not exist" Note: Not supportedH.5.3 Cause No. 83 "a suspended call exists, but this call identity does not"Note: Not supportedH.5.4 Cause No. 84 "call identity in use"Note: Not supportedH.5.5 Cause No. 85 "no call suspended"Note: Not supportedH.5.6 Cause No. 86 "call having the requested callidentity has been cleared"Note: Not supportedH.5.7 Cause No. 88 "incompatible destination"This cause indicates that the equipment sending this cause has received arequest to establish a call which has low layer compatibility, high layercompatibility, or other compatibility attributes (e.g., data rate) which cannotbe accomodated.H.5.8 Cause No. 91 "invalid transit network selection" Note: For further studyH.5.9 Cause No. 94 "incomplete segmented message"Note: Not supported, no segmentation at layer 3H.5.10 Cause No. 95 "invalid message, unspecified"This cause is used to report an invalid message event only when no other causein the invalid message class applies.H.6 Protocol error (e.g., unknown message) classH.6.1 Cause No. 96 "mandatory information element error" This cause indicates that the equipment sending this cause has received amessage where a mandatory information element is missingand/or has a contenterror (the two cases are undistinguishable).H.6.2 Cause No. 97 "message type non-existent or not implemented"This cause indicates that the equipment sending this cause has received amessage with a message type it does not recognize either because this is amessage not defined or defined but not implemented by the equipment sendingthis cause.H.6.3 Cause No. 98 "message not compatible with call state or message type non-existentor not implemented"This cause indicates that the equipment sending this cause has received amessage such that the procedures do not indicate that this is a permissiblemessage to receive while in the call state, or a STATUS message was receivedindicating an incompatible call state.H.6.4 Cause No. 99 "information element non-existent or not implemented"This cause indicates that the equipment sending this cause has received amessage which includes information elements not recognized because theinformation element identifier is not defined or it is defined but notimplemented by the equipment sending the cause. However, the informationelement is not required to be present in the message in order for the equipmentsending the cause to process the message.H.6.5 Cause No. 100 "invalid information element contents" This cause indicates that the equipment sending this cause has received aninformation element which it has implemented; however, one or more of thefields in the information element are coded in such a way which has not beenimplemented by the equipment sending this cause.H.6.6 Cause No. 101 "message not compatible with call state"This cause indicates that a message has been received which is incompatiblewith the call state.H.6.7 Cause No. 102 "recovery on timer expiry"This cause indicates that a procedure has been initiated bythe expiry of atimer in association with Rec. 04.08 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 inthe protocol error class applies.H.7 Interworking classH.7.1 Cause No. 127 "Interworking, unspecified"This cause indicates that there has been interworking with a network which doesnot provide causes for actions it takes; thus, the precise cause for a messagewhich is being sent cannot be ascertained.。