附录 F，GSM 无线资源管理的详尽原因

Cause value = 0  Normal release;正常释放

indicatesthat the channel is released because of a normal event.

Cause value = 1 Abnormal release, unspecified;异常释放，没有具体说明

indicatesthat the channel is released because of an abnormal event withoutspecifyingfurther reasons.

Cause value = 2 Abnormal release, channelunacceptable;

indicatesthat the channel type or channel characteristics are not acceptable.

Cause value = 3  Abnormal release, timer expired;

indicatingthat the release is caused by a timer expiry.

Cause value = 4  Abnormal release, no activity onradio path;

indicatingthat some supervisory function has detected that channel is notactive.

Cause value = 5  Preemptive release;

indicatesthat the channel is released in order to be allocated to a call withpriority(e.g. an emergency call).

Cause value = 65Call already cleared;

indicatingthat a handover is unsuccessful because the connection has beenreleased bythe 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;SeeAnnex H, section H6.3

Cause value = 100 Invalid information element contents;See Annex H, section H6.5

Cause value = 111Protocol error unspecified;See Annex H, section H6.8.

ANNEX G(to Recommendation GSM 04.08)

GSM specific cause values for mobilitymanagement

G.1  Causes related to MSidentification

Cause value = 1 Unallocated TMSI.

This cause issent to the MS if the MS identifies itself by a TMSI which is notallocated inthe relevant location area and open identification is not requested.

Cause value = 2 IMSI unknown in HLR

This cause issent to the MS if the MS is not known (registered) in the HRL.

Cause value = 3 Illegal MS

This cause issent 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 VLR

This cause issent to the MS when the given IMSI is not known at the VLR.

Cause value = 5 IMEI not accepted

This cause issent to the MS if the IMEI given cannot be accepted by thenetwork.

G.2  Cause related tosubscription options

Cause value = 11PLMN not allowed

This cause issent to the MS if it requests location updating in a PLMN wherethe MS, bysubscription is not allowed to operate.

Cause value = 12 Location Area not allowed

This cause issent to the MS if it requests location updating in a Locationnarea wherethe MS, by subscription, is not allowed to operate.

G.3  Causes related toPLMN specific network failures and congestion

Cause value = 17Network failure

This cause issent to the MS if the MSC cannot service an MS generated requestbecause ofPLMN failures, e.g. problems in MAP.

Cause value = 22 Congestion

This cause issent if the service request cannot be actioned because ofcongestion(e.g. no channel, facility busy/congested etc.)

G.4  Causes related tonature of request

Cause value = 32Service option not supported

This cause issent when the MS requests a service/facility in the CM SERVICEREQUESTmessage which is not supported by the PLMN.

Cause value = 33 Requested service option not subscribed

This causeist sent when the MS requests a service option for which it has nosubscription.

Cause value = 34Service option temporarily out of order

This cause issent when the MSC cannot service the request because of temporaryoutage of oneor more functions required for supporting the service.

Cause value = 38 Call cannot be identified

This cause issent when the network cannot identify the call associated with acall re-establishment request.

G.5  Causes related toinvalid messages

Cause 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 = 98Message non compatible with call state or message type non-existent or notimplemented.seeAnnex H, sect. H.6.3.

Cause value = 99Information element non-existent or not implemented。See Annex H, sect. H.6.4.

Cause value = 100 Invalid information element contents。SeeAnnex H, sect. H.6.5.

Cause value = 101Message not compatible with call state。SeeAnnex H, sect. H.6.6.

Cause value = 111 Protocol error, unspecified。SeeAnnex H, sect. H.6.8.

Annex H(to Recommendation GSM 04.08)

Cause definitions for Call Control

H.1       Normal class

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

This causeindicates that the destination requested by the Mobile Stationcannot bereached because, although the number is in a valid format, it is notcurrentlyassigned (allocated).

H.1.2    Cause No. 2 "no route to specified transit network"

Note:     For further study

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

This causeindicates that the called user cannot be reached because the networkthrough whichthe call has been routed does not serve the destination desired.

H.1.4    Cause No. 6 "channel unacceptable"

This causeindicates the channel most recently identified is not acceptable tothe sendingentity for use in this call.

H.1.5    Cause No. 7 "call awarded and being delivered in an establishedchannel"

Note:     Not supported

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

This causeindicates that the call is being cleared because one of the usersinvolved inthe call has requested that the call be cleared.

Under normalsituation, the source of this cause is not thenetwork.

H.1.7    Cause No.17 "user busy"

This cause isused when the called user has indicated the inability to acceptanother call.It is notedthat the user equipment is compatible with the call.

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

This cause isused when a user does not respond to a call establishment messagewith eitheran alerting or connect indication within the prescribed period of timeallocated (defined by the expiry of either timer T303 or T310).

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

This cause isused when a user has provided an alerting indication but has notprovided aconnect indication within a prescribed period of time.

H.1.10   Cause No. 21 "call rejected"

This causeindicates that the equipment sending this cause does not wish toaccept thiscall, although it could have accepted the call because theequipmentsending this cause is neither busy nor incompatible.

H.1.11   Cause No. 22 "number changed"

This cause isreturned to a calling Mobile Station when the called party numberindicated bythe calling Mobile Station is no longer assigned. The new called party numbermay optionally be included in the diagnostic field. If a networkdoes notsupport this capability, cause No. 1 "unassigned (unallocated)number"shall beused.

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

Note:     Not supported

H.1.13   Cause No 27 "destinationout of order"目标故障

This causeindicates that the destination indicated by the Mobile Stationcannot bereached because the interface to the destination is not functioningcorrectly.The term "not functioning correctly" indicates that a signallingmessage wasunable to be delivered to the remote user; e.g., a physical layeror data linklayer failure at the remote user, user equipment off-line, etc.

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

This causeindicates that the called user cannot be reached because the calledparty numberis not a valid format or is not complete.

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

This cause isincluded in STATUS messages if the message is sent in response toa STATUSENQUIRY message. See also section 5.5.3.

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

This cause isused to report a normal event only when no other cause in thenormal classapplies.

H.2      Resource unavailable class

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

This causeindicates that there is no appropriate circuit/channel presentlyavailable tohandle the call.

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

This causeindicates that the network is not functioning correctly and that thecondition is likelyto 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 causeindicates that the network is not functioning correctly and that thecondition isnot likely to last a long period of time; e.g., the Mobile Stationmay wish totry another call attempt almost immediately.

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

This causeindicates that the switching equipment generating this cause isexperiencinga period of high traffic.

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

This causeindicates that the network could not deliver access information tothe remoteuser as requested; i.e., a user-to-user information, low layercompatibility,high layer compatibility, or sub-address as indicated in the

diagnostic.It is notedthat the particular type of access information discarded isoptionallyincluded in the diagnostic.

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

This cause isreturned when the circuit or channel indicated by the requestingentity cannotbe provided by the other side of the interface.

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

This cause isused to report a resource unavailable event only when no othercause in theresource unavailable class applies.

H.3      Service or option not available class

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

This causeindicates that the Mobile Station has requested a bearer capabilitywhich isimplemented by the equipment which generated this cause but the MobileStation isnot authorized to use.

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

This causeindicates that the Mobile Station has requested a bearer capabilitywhich isimplemented by the equipment which generated this cause but which isnot availableat this time.

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

This cause isused to report a service or option not available event only whenno othercause in the service or option not available class applies.

H.4      Service or option not implemented class

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

This causeindicates that the equipment sending this cause does not support thebearercapability requested.

H.4.2    Cause No. 66 "channel type not implemented"

Note:     Not supported

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

This causeindicates that one equipment has requested an unrestricted bearerservice, butthat the equipment sending this cause only supports the restrictedversion ofthe requested bearer capability.

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

This cause isused to report a service or option not implemented event onlywhen no othercause 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 causeindicates that the equipment sending this cause has received amessage witha 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 supported

H.5.3    Cause No. 83 "a suspended call exists, but this call identity doesnot"

Note:     Not supported

H.5.4    Cause No. 84 "call identity in use"

Note:     Not supported

H.5.5    Cause No. 85 "no call suspended"

Note:     Not supported

H.5.6    Cause No. 86 "call having the requested call identity has beencleared"

Note:     Not supported

H.5.7    Cause No. 88 "incompatible destination"

This causeindicates that the equipment sending this cause has received arequest toestablish a call which has low layer compatibility, high layercompatibility,or other compatibility attributes (e.g., data rate) which cannotbeaccomodated.

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

Note:     For further study

H.5.9    Cause No. 94 "incomplete segmented message"

Note:     Not supported, no segmentation at layer 3

H.5.10   Cause No. 95 "invalid message, unspecified"

This cause isused to report an invalid message event only when no other causein theinvalid message class applies.

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

H.6.1    Cause No. 96 "mandatory information element error"

This causeindicates that the equipment sending this cause has received amessage wherea mandatory information element is missing and/or has a contenterror (thetwo cases are undistinguishable).

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

This causeindicates that the equipment sending this cause has received amessage witha message type it does not recognize either because this is amessage notdefined or defined but not implemented by the equipment sendingthis cause.

H.6.3    Cause No. 98 "message not compatible with call state or messagetype non-existent

or not implemented"

This causeindicates that the equipment sending this cause has received amessage suchthat the procedures do not indicate that this is a permissiblemessage toreceive while in the call state, or a STATUS message was receivedindicating anincompatible call state.

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

This causeindicates that the equipment sending this cause has received amessage whichincludes information elements not recognized because theinformationelement identifier is not defined or it is defined but notimplementedby the equipment sending the cause. However, the informationelement isnot required to be present in the message in order for the equipmentsending thecause to process the message.

H.6.5    Cause No. 100 "invalid information element contents"

This causeindicates that the equipment sending this cause has received aninformationelement which it has implemented; however, one or more of thefields in theinformation element are coded in such a way which has not beenimplementedby the equipment sending this cause.

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

This causeindicates that a message has been received which is incompatiblewith the callstate.

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

This causeindicates that a procedure has been initiated by the expiry of atimer inassociation with Rec. 04.08 error handling procedures.

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

This cause isused to report a protocol error event only when no other cause inthe protocolerror class applies.

H.7      Interworking class

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

This causeindicates that there has been interworking with a network which doesnot providecauses for actions it takes; thus, the precise cause for a messagewhich isbeing sent cannot be ascertained.