Cause_value(路测使用)

附录 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.
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
1

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

check, i.e. the SRES received from the MS is different from
that generated by
the network.
Cause value = 4 IMSI unknown in VLR
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 request
because of PLMN failures, e.g. problems in MAP.
Cause value = 22 Congestion
3

This cause is sent if the service request cannot be actioned
because of
congestion (e.g. no channel, facility busycongested 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 servicefacility 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 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.
4

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. 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
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
Note: For further study
H.1.3 Cause No. 3
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.
5

H.1.4 Cause No. 6
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
established channel
Note: Not supported
H.1.6 Cause No.16
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
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.8 Cause No. 18
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
6

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
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.11 Cause No. 22
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
(unallocated) number
shall be used.
H.1.12 Cause No. 26
Note: Not supported
H.1.13 Cause No 27 目标故障
This cause indicates that the destination indicated by the
Mobile Station
cannot be reached because the interface to the destination is
not functioning
7

correctly. The term
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
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
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
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
This cause indicates that there is no appropriate
circuitchannel presently
available to handle the call.
H.2.2 Cause No. 38
This cause indicates that the network is not functioning
correctly and that the
8

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
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
This cause indicates that the switching equipment generating
this cause is
experiencing a period of high traffic.
H.2.5 Cause No. 43
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
available
9

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
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
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.2 Cause No. 58
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
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.
10

H.4 Service or option not implemented class
H.4.1 Cause No. 65
This cause indicates that the equipment sending this cause
does not support the
bearer capability requested.
H.4.2 Cause No. 66
Note: Not supported
H.4.3 Cause No. 70
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
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
This cause indicates that the equipment sending this cause has
received a
message with a call reference which is not currently in use on
the MS-network
interface.
11

H.5.2 Cause No. 82
Note: Not supported
H.5.3 Cause No. 83
identity does not
Note: Not supported
H.5.4 Cause No. 84
Note: Not supported
H.5.5 Cause No. 85
Note: Not supported
H.5.6 Cause No. 86
identity has been cleared
Note: Not supported
H.5.7 Cause No. 88
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
Note: For further study
H.5.9 Cause No. 94
Note: Not supported, no segmentation at layer 3
H.5.10 Cause No. 95
This cause is used to report an invalid message event only
when no other cause
12

in the invalid message class applies.
H.6 Protocol error (e.g., unknown message) class
H.6.1 Cause No. 96
This cause indicates that the equipment sending this cause has
received a
message where a mandatory information element is missing
andor has a content
error (the two cases are undistinguishable).
H.6.2 Cause No. 97
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
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
message to receive while in the call state, or a STATUS
message was received
indicating an incompatible call state.
13

H.6.4 Cause No. 99
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
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
implemented by the equipment sending this cause.
H.6.6 Cause No. 101
state
This cause indicates that a message has been received which is
incompatible
with the call state.
H.6.7 Cause No. 102
14

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






15