Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 27.007  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   6…   6.10…   6.20…   7…   7.10…   7.20…   7.30…   7.40…   8…   8.10…   8.20…   8.30…   8.40…   8.50…   8.55   8.56…   8.60…   8.70…   8.80…   9…   10…   10.1.3…   10.1.10…   10.1.20…   10.1.30…   10.1.40…   10.1.50…   10.1.60…   10.1.70…   10.1.80…   10.2…   11…   12…   13…   14…   15…   16…   17…   18…   19…   20…   A   B   C…   E   F   G… 
9 Mobile termination errors  9.1 Report mobile termination error +CMEE  9.1A Report mobile originated location request error +CMOLRE  9.1B Report network error codes +CNEC  9.2 Mobile termination error result code +CME ERROR  9.2.0 General  9.2.1 General errors  9.2.2 CS, GPRS, UMTS, EPS and 5GS-related errors  9.2.3 VBS, VGCS and eMLPP-related errors  9.3 Mobile termination error result code +CMOLRE  9.3.1 General  9.3.2 Errors  9.4 Informative examples 
...

 

9  Mobile termination errors  p. 237

9.1  Report mobile termination error +CMEE  p. 237

Command Possible response(s)
+CMEE=[<n>]
+CMEE? +CMEE: <n>
+CMEE=? +CMEE: (list of supported <n>s)
Description
Set command disables or enables the use of final result code +CME ERROR: <err> as an indication of an error relating to the functionality of the MT. When enabled, MT related errors cause +CME ERROR: <err> final result code instead of the regular ERROR final result code. ERROR is returned normally when error is related to syntax, invalid parameters, or TA functionality.
Read command returns the current setting of <n>.
Test command returns values supported as a compound value.
Defined values
<n>
integer type.
0 (default)
disable +CME ERROR: <err> result code and use ERROR instead
1
enable +CME ERROR: <err> result code and use numeric <err> values (refer to clause 9.2)
2
enable +CME ERROR: <err> result code and use verbose <err> values (refer to clause 9.2)
Implementation
Mandatory for <n> values 0 and 1.
Up

9.1A  Report mobile originated location request error +CMOLRE |R12|  p. 237

Command Possible response(s)
+CMOLRE=[<n>]
+CMOLRE? +CMOLRE: <n>
+CMOLRE=? +CMOLRE: (list of supported <n>s)
Description
Set command disables or enables the verbose format of unsolicited result code +CMOLRE: <err> as an indication of an error relating to the functionality for the mobile originated location request (MO-LR) error reporting format. When enabled, MT related verbose error cause is given.
Read command returns the current setting of <n>.
Test command returns values supported as a compound value.
Defined values
<n>
integer type.
0 (default)
disable. This will give +CMOLRE: <err> result code with numeric <err> values (refer to clause 9.3)
1
enable. This will give +CMOLRE: <err> result code with verbose <err> values (refer to clause 9.3)
Implementation
Optional.
Up

9.1B  Report network error codes +CNEC |R12|  p. 238

Command Possible response(s)
+CNEC=[<n>]
+CNEC? +CNEC: <n>
+CNEC=? +CNEC: (list of supported <n>s)
Description
The command activates or deactivates unsolicited reporting of error codes sent by the network. When activated, based on the setting of <n>, the ME will report CS mobility management, GPRS mobility management, GPRS session management, EPS mobility management and EPS session management related error codes sent by the network. The following unsolicited result codes can be reported:
+CNEC_MM: <error_code>CS Mobility Management
+CNEC_GMM: <error_code>GPRS Mobility Management
+CNEC_GSM: <error_code>[,<cid>]GPRS Session Management
+CNEC_EMM: <error_code>[,<cid>]EPS Mobility Management
+CNEC_ESM: <error_code>[,<cid>]EPS Session Management
+CNEC_5GMM: <error_code>[,<cid>]5GS Mobility Management
+CNEC_5GSM: <error_code>[,<cid>]5GS Session Management
The parameter <n> is specified as a sum of integers, each representing the category of error codes that the MT is interested in receiving.
The read command returns the current setting of <n>.
Test command returns the supported values as a compound value.
Parameters
<n>
integer type. The parameter is a sum of integers each representing a certain category of error codes. The value consists of the sum of the individual values for <n> for the required unsolicited result codes.
0 (default)
Disable unsolicited error reporting
1
Enable unsolicited result code +CNEC_MM to report CS mobility management errors coded as specified in TS 24.008 Table 10.5.95/3GPP TS 24.008
2
Enable unsolicited result code +CNEC_GMM to report GPRS mobility management errors coded as specified in TS 24.008 Table 10.5.147/3GPP TS 24.008
4
Enable unsolicited result code +CNEC_GSM to report GPRS session management errors coded as specified in TS 24.008 Table 10.5.157/3GPP TS 24.008
8
Enable unsolicited result code +CNEC_EMM to report EPS mobility management errors coded as specified in TS 24.301 Table 9.9.3.9.1
16
Enable unsolicited result code +CNEC_ESM to report EPS session management errors coded as specified in TS 24.301 Table 9.9.4.4.1
32
Enable unsolicited result code +CNEC_5GMM to report 5GS mobility management errors coded as specified in TS 24.501 Table 9.11.3.2.1
64
Enable unsolicited result code +CNEC_5GSM to report 5GS session management errors coded as specified in TS 24.501 Table 9.11.4.2.1
Example:
If the MT wants to receive only CS mobility management errors, then <n>=1 must be specified.
AT+CNEC=1
If the MT wants to receive CS mobility management errors and GPRS session management errors, then <n>=5 must be specified (1 for enabling CS mobility management error and 4 for enabling GPRS session management error).
AT+CNEC=5
To enable reporting of all error codes, then <n>=127 must be specified (equals 1+2+4+8+16+32+64).
AT+CNEC=127
<error_code>
integer type. Error codes as appropriate according to:
3GPP TS 24.008 Table 10.5.95/3GPP TS 24.008 for CS mobility management errors codes
3GPP TS 24.008 Table 10.5.147/3GPP TS 24.008 for GPRS mobility management errors codes
3GPP TS 24.008 Table 10.5.157/3GPP TS 24.008 for GPRS session management errors codes
3GPP TS 24.301 Table 9.9.3.9.1 for EPS mobility management errors codes
3GPP TS 24.301 Table 9.9.4.4.1 for EPS session management errors codes
3GPP TS 24.501 Table 9.11.3.2.1 for 5GS mobility management errors codes
3GPP TS 24.501 Table 9.11.4.2.1 for 5GS session management errors codes
<cid>
integer type. Specifies a particular PDP context definition.
Implementation
Optional.
Up

9.2  Mobile termination error result code +CME ERROR  p. 240

9.2.0  General |R8|  p. 240

The operation of +CME ERROR: <err> final result code is similar to the regular ERROR result code: if +CME ERROR: <err> is the result code for any of the commands in a command line, none of the following commands in the same command line is executed (neither ERROR nor OK result code shall be returned as a result of a completed command line execution). The format of <err> can be either numeric or verbose. This is set with command +CMEE (refer to clause 9.1).
<err>
values (numeric format followed by verbose format):
All values below 256 are reserved.
Values in the range 0 - 100 are reserved for general errors.
Values in the range 101 - 150 are reserved for use by CS, GPRS, EPS and 5GS.
Values in the range 151 - 170 are reserved for use by VBS/VGCS and eMLPP.
Values in the range 171 - 256 can be used by GPRS, EPS and 5GS.
Up

9.2.1  General errors  p. 240

Numeric
Text
0
phone failure
1
no connection to phone
2
phone-adaptor link reserved
3
operation not allowed
4
operation not supported
5
PH-SIM PIN required
6
PH-FSIM PIN required
7
PH-FSIM PUK required
10
SIM not inserted (See NOTE 1)
11
SIM PIN required
12
SIM PUK required
13
SIM failure (See NOTE 1)
14
SIM busy (See NOTE 1)
15
SIM wrong (See NOTE 1)
16
incorrect password
17
SIM PIN2 required
18
SIM PUK2 required
20
memory full
21
invalid index
22
not found
23
memory failure
24
text string too long
25
invalid characters in text string
26
dial string too long
27
invalid characters in dial string
30
no network service
31
network timeout
32
network not allowed - emergency calls only
40
network personalization PIN required
41
network personalization PUK required
42
network subset personalization PIN required
43
network subset personalization PUK required
44
service provider personalization PIN required
45
service provider personalization PUK required
46
corporate personalization PIN required
47
corporate personalization PUK required
48
hidden key required (See NOTE 2)
49
EAP method not supported
50
Incorrect parameters
51
command implemented but currently disabled
52
command aborted by user
53
not attached to network due to MT functionality restrictions
54
modem not allowed - MT restricted to emergency calls only
55
operation not allowed because of MT functionality restrictions
56
fixed dial number only allowed - called number is not a fixed dial number (refer TS 22.101)
57
temporarily out of service due to other MT usage
58
language/alphabet not supported
59
unexpected data value
60
system failure
61
data missing
62
call barred
63
message waiting indication subscription failure
100
unknown
Up

9.2.2  CS, GPRS, UMTS, EPS and 5GS-related errors  p. 241

9.2.2.1  Errors related to a failure to perform an attach  p. 241

9.2.2.1.1  Errors for CS, GPRS and UMTS |R15|  p. 241
Numeric
Text
102
IMSI unknown in HLR (#2) NOTE 2
103
Illegal MS (#3)
104
IMSI unknown in VLR (#4) NOTE 2
105
IMEI not accepted (#5) NOTE 2
106
Illegal ME (#6)
107
GPRS services not allowed (#7)
108
GPRS services and non-GPRS services not allowed (#8)
109
MS identity cannot be derived by the network (#9) NOTE 2
110
Implicitly detached (#10) NOTE 2
111
PLMN not allowed (#11)
112
Location area not allowed (#12)
113
Roaming not allowed in this location area (#13)
114
GPRS services not allowed in this PLMN (#14)
115
No Suitable Cells In Location Area (#15)
116
MSC temporarily not reachable (#16) NOTE 2
117
Network failure (#17) NOTE 2
122
Congestion (#22)
125
Not authorized for this CSG (#25)
132
Service option not supported (#32) NOTE 2
133
Requested service option not subscribed (#33) NOTE 2
134
Service option temporarily out of order (#34) NOTE 2
138
Call cannot be identified (#38) NOTE 2
148
Unspecified GPRS error NOTE 2
150
Invalid mobile class
172
Semantically incorrect message (#95)
173
Invalid mandatory information (#96)
174
Message type non-existent or not implemented (#97)
175
Conditional IE error (#100)
176
Protocol error, unspecified (#111)
183
SMS provided via GPRS in this routing area (#28) NOTE 2
185
No PDP context activated (#40) NOTE 2
186
Message not compatible with protocol state (#101) NOTE 2
187
Recovery on timer expiry (#102) NOTE 2
208
Message type not compatible with protocol state (#98) NOTE 2
209
Information element non-existent or not implemented (#99) NOTE 2
Up
9.2.2.1.2  Errors for EPS |R15|  p. 242
Numeric
Text
102
IMSI unknown in HSS (#2) NOTE 2
103
Illegal UE (#3)
105
IMEI not accepted (#5) NOTE 2
106
Illegal ME (#6)
107
EPS services not allowed (#7)
108
EPS services and non-EPS services not allowed (#8)
109
UE identity cannot be derived by the network (#9) NOTE 2
110
Implicitly detached (#10) NOTE 2
111
PLMN not allowed (#11)
112
Tracking area not allowed (#12)
113
Roaming not allowed in this tracking area (#13)
114
EPS services not allowed in this PLMN (#14)
115
No suitable cells in tracking area (#15)
116
MSC temporarily not reachable (#16) NOTE 2
117
Network failure (#17) NOTE 2
118
CS domain not available (#18)
119
ESM failure (#19)
122
Congestion (#22)
125
Not authorized for this CSG (#25)
139
CS service temporarily not available (#39) NOTE 2
172
Semantically incorrect message (#95)
173
Invalid mandatory information (#96)
174
Message type non-existent or not implemented (#97)
175
Conditional IE error (#100)
176
Protocol error, unspecified (#111)
185
No EPS bearer context activated (#40) NOTE 2
186
Message not compatible with protocol state (#101) NOTE 2
189
Requested service option not authorized in this PLMN (#35) NOTE 2
204
Severe network failure (#42) NOTE 2
208
Message type not compatible with protocol state (#98) NOTE 2
209
Information element non-existent or not implemented (#99) NOTE 2
226
Redirection to 5GCN required (#31)
Up
9.2.2.1.3  Errors for 5GS |R15|  p. 242
Numeric
Text
103
Illegal UE (#3)
105
PEI not accepted (#5)
106
Illegal ME (#6)
107
5GS services not allowed (#7)
109
UE identity cannot be derived by the network (#9)
110
Implicitly deregistered (#10)
111
PLMN not allowed (#11)
112
Tracking area not allowed (#12)
113
Roaming not allowed in this tracking area (#13)
115
No suitable cells in tracking area (#15)
122
Congestion (#22)
172
Semantically incorrect message (#95)
173
Invalid mandatory information (#96)
174
Message type non-existent or not implemented (#97)
175
Conditional IE error (#100)
176
Protocol error, unspecified (#111)
178
Maximum number of PDU sessions reached (#65)
186
Message not compatible with protocol state (#101)
205
Insufficient resources for specific slice and DNN (#67)
207
Insufficient resources for specific slice (#69)
208
Message type not compatible with protocol state (#98)
209
Information element non-existent or not implemented (#99)
210
N1 mode not allowed (#27)
211
Restricted service area (#28)
212
LADN not available (#43)
214
ngKSI already in use (#71)
215
Payload was not forwarded (#90)
216
Non-3GPP access to 5GCN not allowed (#72)
217
Serving network not authorized (#73)
218
DNN not supported or not subscribed in the slice (#91)
219
Insufficient user-plane resources for the PDU session (#92)
227
Redirection to EPC required (#31)
228
Temporarily not authorized for this SNPN (#74)
229
Permanently not authorized for this SNPN (#75)
231
Not authorized for this CAG or authorized for CAG cells only (#76)
232
No network slices available (#62)
233
Wireline access area not allowed (#77)
Up

9.2.2.2  Errors related to a failure to activate a context  p. 243

9.2.2.2.1  Errors for GPRS and UMTS |R15|  p. 243
Numeric
Text
124
MBMS bearer capabilities insufficient for the service (#24) NOTE 2
126
Insufficient resources (#26)
127
Missing or unknown APN (#27)
128
Unknown PDP address or PDP type (#28)
129
User authentication or authorization failed (#29)
130
Activation rejected by GGSN, Serving GW or PDN GW (#30)
131
Activation rejected, unspecified (#31)
132
Service option not supported (#32)
133
Requested service option not subscribed (#33)
134
Service option temporarily out of order (#34)
135
NSAPI already used (#35) NOTE 2
136
Regular deactivation (#36) NOTE 2
140
Feature not supported (#40)
141
Semantic error in the TFT operation (#41)
142
Syntactical error in the TFT operation (#42)
143
Unknown PDP context (#43)
144
Semantic errors in packet filter(s) (#44)
145
Syntactical errors in packet filter(s) (#45)
146
PDP context without TFT already activated (#46)
147
Multicast group membership time-out (#47) NOTE 2
148
Unspecified GPRS error
149
PDP authentication failure
150
Invalid mobile class
172
Semantically incorrect message (#95) NOTE 2
173
Invalid mandatory information (#96) NOTE 2
174
Message type non-existent or not implemented (#97) NOTE 2
175
Conditional IE error (#100) NOTE 2
176
Protocol error, unspecified (#111) NOTE 2
177
Operator determined barring (#8)
178
Maximum number of PDP contexts reached (#65)
179
Requested APN not supported in current RAT and PLMN combination (#66)
180
Request rejected, bearer control mode violation (#48)
182
User data transmission via control plane is congested
186
Message not compatible with protocol state (#101) NOTE 2
188
Invalid transaction identifier value (#81) NOTE 2
190
Network failure (#38) NOTE 2
191
Reactivation requested (#39) NOTE 2
192
PDP type IPv4 only allowed (#50) NOTE 2
193
PDP type IPv6 only allowed (#51) NOTE 2
194
Single address bearers only allowed (#52) NOTE 2
195
Collision with network initiated request (#56) NOTE 2
196
PDP type IPv4v6 only allowed (#57) NOTE 2
197
PDP type non IP only allowed (#58) NOTE 2
198
Bearer handling not supported (#60) NOTE 2
199
APN restriction value incompatible with active PDP context (#112) NOTE 2
200
Multiple accesses to a PDN connection not allowed (#113) NOTE 2
208
Message type not compatible with protocol state (#98) NOTE 2
209
Information element non-existent or not implemented (#99) NOTE 2
Up
9.2.2.2.2  Errors for EPS |R15|  p. 245
Numeric
Text
126
Insufficient resources (#26)
127
Missing or unknown APN (#27)
128
Unknown PDN type (#28)
129
User authentication or authorization failed (#29)
130
Activation rejected by Serving GW or PDN GW (#30)
131
Request rejected, unspecified (#31)
132
Service option not supported (#32)
133
Requested service option not subscribed (#33)
134
Service option temporarily out of order (#34)
135
PTI already in use (#35)
136
Regular deactivation (#36) NOTE 2
137
EPS QoS not accepted (#37) NOTE 2
141
Semantic error in the TFT operation (#41)
142
Syntactical error in the TFT operation (#42)
143
Invalid EPS bearer identity (#43)
144
Semantic errors in packet filter(s) (#44)
145
Syntactical errors in packet filter(s) (#45)
171
Last PDN disconnection not allowed (#49) NOTE 3
172
Semantically incorrect message (#95) NOTE 2
173
Invalid mandatory information (#96) NOTE 2
174
Message type non-existent or not implemented (#97) NOTE 2
175
Conditional IE error (#100) NOTE 2
176
Protocol error, unspecified (#111) NOTE 2
177
Operator determined barring (#8)
178
Maximum number of EPS bearers reached (#65)
179
Requested APN not supported in current RAT and PLMN combination (#66)
181
unsupported QCI value (#59)
184
Invalid PTI value (#81)
186
Message not compatible with protocol state (#101) NOTE 2
190
Network failure (#38) NOTE 2
191
Reactivation requested (#39) NOTE 2
192
PDN type IPv4 only allowed (#50) NOTE 2
193
PDN type IPv6 only allowed (#51) NOTE 2
194
Single address bearers only allowed (#52) NOTE 2
195
Collision with network initiated request (#56) NOTE 2
196
PDN type IPv4v6 only allowed (#57) NOTE 2
197
PDN type non IP only allowed (#58) NOTE 2
198
Bearer handling not supported (#60) NOTE 2
199
APN restriction value incompatible with active EPS bearer context (#112) NOTE 2
200
Multiple accesses to a PDN connection not allowed (#113) NOTE 2
201
ESM information not received (#53) NOTE 2
202
PDN connection does not exist (#54) NOTE 2
203
Multiple PDN connections for a given APN not allowed (#55) NOTE 2
208
Message type not compatible with protocol state (#98) NOTE 2
209
Information element non-existent or not implemented (#99) NOTE 2
221
PTI mismatch (#47)
230
PDN type Ethernet only allowed (#61)
Up
9.2.2.2.3  Errors for 5GS |R15|  p. 246
Numeric
Text
126
Insufficient resources (#26)
127
Missing or unknown DNN (#27)
128
Unknown PDU session type (#28)
129
User authentication or authorization failed (#29)
131
Request rejected, unspecified (#31)
132
Service option not supported (#32)
133
Requested service option not subscribed (#33)
135
PTI already in use (#35)
136
Regular deactivation (#36)
137
5GS QoS not accepted (#37)
141
Semantic error in the TFT operation (#41)
142
Syntactical error in the TFT operation (#42)
143
Invalid PDU session identity (#43)
144
Semantic errors in packet filter(s) (#44)
145
Syntactical errors in packet filter(s) (#45)
172
Semantically incorrect message (#95)
173
Invalid mandatory information (#96)
174
Message type non-existent or not implemented (#97)
175
Conditional IE error (#100)
176
Protocol error, unspecified (#111)
177
Operator determined barring (#8)
181
Unsupported 5QI value (#59)
184
Invalid PTI value (#81)
186
Message not compatible with protocol state (#101)
190
Network failure (#38)
191
Reactivation requested (#39)
192
PDU session type IPv4 only allowed (#50)
193
PDU session type IPv6 only allowed (#51)
196
PDU session type IPv4v6 only allowed (#57)
197
PDU session type Unstructured only allowed (#58)
202
PDU session does not exist (#54)
205
Insufficient resources for specific slice and DNN (#67)
206
Not supported SSC mode (#68)
207
Insufficient resources for specific slice (#69)
208
Message type not compatible with protocol state (#98)
209
Information element non-existent or not implemented (#99)
213
Missing or unknown DNN in a slice (#70)
220
Out of LADN service area (#46)
221
PTI mismatch (#47)
222
Maximum data rate per UE for user-plane integrity protection is too low (#82)
223
Semantic error in the QoS operation (#83)
224
Syntactical error in the QoS operation (#84)
225
Invalid mapped EPS bearer identity (#85)
230
PDU session type Ethernet only allowed (#61)
Up

9.2.2.3  Void

9.2.2.4  Void

9.2.3  VBS, VGCS and eMLPP-related errors  p. 246

Numeric
Text
151
VBS/VGCS not supported by the network
152
No service subscription on SIM
153
No subscription for group ID
154
Group Id not activated on SIM
155
No matching notification
156
VBS/VGCS call already present
157
Congestion
158
Network failure
159
Uplink busy
160
No access rights for SIM file
161
No subscription for priority
162
operation not applicable or not possible
163
Group Id prefixes not supported
164
Group Id prefixes not usable for VBS
165
Group Id prefix value invalid
Implementation
Mandatory for numeric format codes applicable to implemented command set.

9.3  Mobile termination error result code +CMOLRE  p. 247

9.3.1  General |R8|  p. 247

The operation of +CMOLRE: <err> unsolicited result code is similar to the regular ERROR result code. The format of <err> can be either numeric or verbose. This is set with command +CMOLRE (refer to clause 9.1A).
<err> values (numeric format followed by verbose format):

9.3.2  Errors |R8|  p. 247

Numeric
Text
0
Method not supported
1
Additional assistance data reqired
2
Not enough satellites
3
UE busy (See NOTE)
4
Network error
5
Failed to open internet connection, too many connections
6
Failed to open internet connection, too many users
7
Failure due to handover
8
Internet connection failure
9
Memory error
255
Unknown error

9.4  Informative examples |R8|  p. 247

An example of TA responses with all three +CMEE values when MT manufacturer identification is requested but MT is not connected to the TA:
AT+CMEE=0 (+CME ERROR shall not be used)
OK
AT+CGMI
ERROR
AT+CMEE=1 (use numeric <err>)
OK
AT+CGMI
+CME ERROR: 1
AT+CMEE=2 (use verbose <err>)
OK
AT+CGMI
+CME ERROR: no connection to phone

Up   Top   ToC