2024年5月5日发(作者：)

附录 F

GSM 无线资源管理的详尽原因

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 without

specifying 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 not

active.

1

Cause value = 5 Preemptive release;

indicates that the channel is released in order to be allocated to a call with

priority (e.g. an emergency call).

Cause value = 65 Call already cleared;

indicating that a handover is unsuccessful because the connection has been

released 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 not

implemented;See Annex H, section H6.3

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

H6.5

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

2

ANNEX G(to Recommendation GSM 04.08)

GSM specific cause values for mobility management

G.1 Causes related to MS identification

Cause value = 1 Unallocated TMSI.

This cause is sent to the MS if the MS identifies itself by a TMSI which is not

allocated in the relevant location area and open identification is not

requested.

Cause value = 2 IMSI unknown in HLR

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

Cause value = 3 Illegal MS

This cause is sent to the MS when the MS does not pass the authentication

check, i.e. the SRES received from the MS is different from that generated by

the network.

Cause value = 4 IMSI unknown in VLR

3

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

Cause value = 5 IMEI not accepted

This cause is sent to the MS if the IMEI given cannot be accepted by the

network.

G.2 Cause related to subscription options

Cause value = 11 PLMN not allowed

This cause is sent to the MS if it requests location updating in a PLMN where

the MS, by subscription is not allowed to operate.

Cause value = 12 Location Area not allowed

This cause is sent to the MS if it requests location updating in a Locationn

area where the MS, by subscription, is not allowed to operate.

G.3 Causes related to PLMN specific network failures and congestion

Cause value = 17 Network failure

This cause is sent to the MS if the MSC cannot service an MS generated

4

request

because of PLMN failures, e.g. problems in MAP.

Cause value = 22 Congestion

This cause is sent if the service request cannot be actioned because of

congestion (e.g. no channel, facility busy/congested etc.)

G.4 Causes related to nature of request

Cause value = 32 Service option not supported

This cause is sent when the MS requests a service/facility in the CM SERVICE

REQUEST message which is not supported by the PLMN.

Cause value = 33 Requested service option not subscribed

This cause ist sent when the MS requests a service option for which it has no

subscription.

Cause value = 34 Service option temporarily out of order

This cause is sent when the MSC cannot service the request because of

5

temporary

outage of one or more functions required for supporting the service.

Cause value = 38 Call cannot be identified

This cause is sent when the network cannot identify the call associated with a

call re- establishment request.

G.5 Causes related to invalid messages

Cause value = 96 Mandatory information element Annex H, sect.

H.6.1.

Cause value = 97 Message type non-existent or not Annex

H, sect. H.6.2.

Cause value = 98 Message non compatible with call state or message type

non-existent or not

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.

6

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 Control

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. 2 "no route to specified transit network"

Note: For further study

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

7

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.4 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.5 Cause No. 7 "call awarded and being delivered in an established

channel"

Note: Not supported

H.1.6 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 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 accept

8

another 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

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.9 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.10 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.

9

H.1.11 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.12 Cause No. 26 "non-selected user clearing"

Note: Not supported

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

10

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. 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 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 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

11

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

12

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. 57 "bearer capability not authorized"

This cause indicates that the Mobile Station has requested a bearer capability

13

which is implemented by the equipment which generated this cause but the

Mobile

Station 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 capability

which is implemented by the equipment which generated this cause but

which is

not 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 when

no other cause 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 cause indicates that the equipment sending this cause does not support

the

14

bearer capability 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 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 call reference value"

This cause indicates that the equipment sending this cause has received a

15

message with a call reference which is not currently in use on the MS-network

interface.

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 does

not"

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

cleared"

Note: Not supported

H.5.7 Cause No. 88 "incompatible destination"

Cause No. 86 "call having the requested call identity has been

16

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 accomodated.

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 is used to report an invalid message event only when no other

cause

in the invalid message class applies.

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

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

17

This cause indicates that the equipment sending this cause has received a

message where a mandatory information element is missing and/or has a

content

error (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 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 not compatible with call state or message

type non-existent

or not implemented"

This cause indicates that the equipment sending this cause has received a

message such that the procedures do not indicate that this is a permissible

18

message to receive while in the call state, or a STATUS message was received

indicating 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 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 "invalid information element contents"

This cause indicates that the equipment sending this cause has received an

information element which it has implemented; however, one or more of the

fields in the information element are coded in such a way which has not been

19

implemented 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 incompatible

with the 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 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

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

20

not provide causes for actions it takes; thus, the precise cause for a message

which is being sent cannot be ascertained.

21