8 Message functional definitions and contents
24.3013GPPNon-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)Release 18Stage 3TS
8.1 Overview
This clause defines the structure of the messages of the Layer 3 (L3) protocols defined in the present document. These are standard L3 messages as defined in 3GPP TS 24.007 [12].
Each definition given in the present clause includes:
a) a brief description of the message direction and use, including whether the message has:
1. Local significance, i.e. relevant only on the originating or terminating access;
2. Access significance, i.e. relevant in the originating and terminating access, but not in the network;
3. Dual significance, i.e. relevant in either the originating or terminating access and in the network; or
4. Global significance, i.e. relevant in the originating and terminating access and in the network.
b) a table listing the Information Elements (IE) known in the message and the order of their appearance in the message. All IEs that may be repeated are explicitly indicated (The V, LV and LV-E formatted IEs, which compose the imperative part of the message, occur before the T, TV, TLV and TLV-E formatted IEs which compose the non-imperative part of the message, see 3GPP TS 24.007 [12]). In a (maximal) sequence of consecutive IEs with half octet length, the first IE with half octet length occupies bits 1 to 4 of octet N, the second IE bits 5 to 8 of octet N, the third IE bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements.
For each information element the table indicates:
1. The Information Element Identifier (IEI), in hexadecimal notation, if the IE has format T, TV, TLV or TLV‑E. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-).
NOTE: The same IEI can be used for different information element types in different messages of the same protocol.
2. The name of the information element (which may give an idea of the semantics of the element). The name of the information element followed by "IE" or "information element" is used in this technical report as reference to the information element within a message.
3. The name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced clause of clause 9 of the present document describing the value part of the information element.
4. The presence requirement indication (M, C, or O) for the IE as defined in 3GPP TS 24.007 [12].
5. The format of the information element (T, V, TV, LV, TLV, LV-E or TLV-E) as defined in 3GPP TS 24.007 [12].
6. The length of the information element (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by link layer protocol. This indication is non-normative.
c) clauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant message which together with other conditions specified in the present document define when the information elements shall be included or not, what non-presence of such IEs means, and – for IEs with presence requirement C – the static conditions for presence or non-presence of the IEs or for both cases (see 3GPP TS 24.007 [12]).
8.2 EPS mobility management messages
8.2.1 Attach accept
8.2.1.1 Message definition
This message is sent by the network to the UE to indicate that the corresponding attach request has been accepted. See table 8.2.1.1.
Message type: ATTACH ACCEPT
Significance: dual
Direction: network to UE
Table 8.2.1.1: ATTACH ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Attach accept message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
EPS attach result |
EPS attach result 9.9.3.10 |
M |
V |
1/2 |
|||||||
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|||||||
T3412 value |
GPRS timer 9.9.3.16 |
M |
V |
1 |
|||||||
TAI list |
Tracking area identity list 9.9.3.33 |
M |
LV |
7-97 |
|||||||
ESM message container |
ESM message container 9.9.3.15 |
M |
LV-E |
5-n |
|||||||
50 |
GUTI |
EPS mobile identity 9.9.3.12 |
O |
TLV |
13 |
||||||
13 |
Location area identification |
Location area identification 9.9.2.2 |
O |
TV |
6 |
||||||
23 |
MS identity |
Mobile identity 9.9.2.3 |
O |
TLV |
7-10 |
||||||
53 |
EMM cause |
EMM cause 9.9.3.9 |
O |
TV |
2 |
||||||
17 |
T3402 value |
GPRS timer 9.9.3.16 |
O |
TV |
2 |
||||||
59 |
T3423 value |
GPRS timer 9.9.3.16 |
O |
TV |
2 |
||||||
4A |
Equivalent PLMNs |
PLMN list 9.9.2.8 |
O |
TLV |
5-47 |
||||||
34 |
Emergency number list |
Emergency number list 9.9.3.37 |
O |
TLV |
5-50 |
||||||
64 |
EPS network feature support |
EPS network feature support 9.9.3.12A |
O |
TLV |
3-4 |
||||||
F- |
Additional update result |
Additional update result 9.9.3.0A |
O |
TV |
1 |
||||||
5E |
T3412 extended value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
6A |
T3324 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
||||||
6E |
Extended DRX parameters |
Extended DRX parameters 9.9.3.46 |
O |
TLV |
3 |
||||||
65 |
DCN-ID |
DCN-ID 9.9.3.48 |
O |
TLV |
4 |
||||||
E- |
SMS services status |
SMS services status 9.9.3.4B |
O |
TV |
1 |
||||||
D- |
Non-3GPP NW provided policies |
Non-3GPP NW provided policies 9.9.3.49 |
O |
TV |
1 |
||||||
6B |
T3448 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
||||||
C- |
Network policy |
Network policy 9.9.3.52 |
O |
TV |
1 |
||||||
6C |
T3447 value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
7A |
Extended emergency number list |
Extended emergency number list 9.9.3.37A |
O |
TLV-E |
7-65538 |
||||||
7C |
Ciphering key data |
Ciphering key data 9.9.3.56 |
O |
TLV-E |
35-2291 |
||||||
66 |
UE radio capability ID |
UE radio capability ID 9.9.3.60 |
O |
TLV |
3-n |
||||||
B- |
UE radio capability ID deletion indication |
UE radio capability ID deletion indication 9.9.3.61 |
O |
TV |
1 |
||||||
35 |
Negotiated WUS assistance information |
WUS assistance information 9.9.3.62 |
O |
TLV |
3-n |
||||||
36 |
Negotiated DRX parameter in NB-S1 mode |
NB-S1 DRX parameter 9.9.3.63 |
O |
TLV |
3 |
||||||
38 |
Negotiated IMSI offset |
IMSI offset 9.9.3.64 |
O |
TLV |
4 |
||||||
1D |
Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
||||||
1E |
Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
8.2.1.2 GUTI
This IE may be included to assign a GUTI to the UE during attach or combined EPS/IMSI attach.
8.2.1.3 Location area identification
This IE may be included to assign a new location area identification to a UE during a combined attach.
8.2.1.4 MS identity
This IE may be included to assign or unassign a new TMSI to a UE during a combined attach.
8.2.1.5 EMM cause
This IE shall be included when IMSI attach for non-EPS services is not successful during a combined EPS/IMSI attach procedure.
8.2.1.6 T3402 value
This IE may be included to indicate a value for timer T3402.
8.2.1.7 T3423 value
This IE may be included to indicate a value for timer T3423.
If this IE is not included, the UE shall use the default value.
8.2.1.8 Equivalent PLMNs
This IE may be included in order to assign an equivalent PLMNs list to a UE.
8.2.1.9 Emergency number list
This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers valid within the same country as in the PLMN from which this IE is received.
8.2.1.9A Extended emergency number list
This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers (with URN information) valid within the same country as in the PLMN from which this IE is received or valid only in the PLMN from which this IE is received.
8.2.1.10 EPS network feature support
The network may include this IE to inform the UE of the support of certain features. If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero, except for the S1-u data transfer (S1-U data) (octet 4, bit 2).
NOTE: In this exceptional case, the UE deems that the network supports S1-u data transfer.
8.2.1.11 Additional update result
The network may include this IE to provide the UE with additional information about the result of:
– a combined attach procedure if the procedure was successful for EPS services and non-EPS services, or for EPS services and "SMS only"; or
– an attach procedure requested for CIoT EPS optimizations if the procedure was successful for EPS services and "SMS only".
8.2.1.12 T3412 extended value
The network may include this IE to provide the UE with longer periodic tracking area update timer.
8.2.1.13 T3324 value
The network shall include the T3324 value IE if:
– the UE included the T3324 value IE in the ATTACH REQUEST message; and
– the network supports PSM and accepts the use of PSM.
8.2.1.14 Extended DRX parameters
The network shall include the Extended DRX parameters IE if:
– the UE included the Extended DRX parameters IE in the ATTACH REQUEST message; and
– the network supports eDRX and accepts the use of eDRX.
8.2.1.15 DCN-ID
This IE is included in the message when the network wishes to provide a DCN-ID to the UE.
8.2.1.16 SMS services status
This IE may be included when a normal attach procedure for EPS services and "SMS only" was successful for EPS services only.
8.2.1.17 Non-3GPP NW provided policies
This IE is included if the network needs to indicate whether emergency numbers provided via non-3GPP access can be used to initiate UE detected emergency calls (see 3GPP TS 24.302 [48]). If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero.
8.2.1.18 T3448 value
The network may include this IE if the congestion control for transport of user data via the control plane is active and the UE supports timer T3448.
8.2.1.19 Network policy
This IE is included if the network needs to indicate network policy information to the UE, If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero.
8.2.1.20 T3447 value
The network may include T3447 value IE if:
– the UE has indicated support for service gap control in the ATTACH REQUEST message; and
– the EMM context contains a service gap time value.
8.2.1.21 Ciphering key data
This IE is included if the network needs to send ciphering key data to the UE for ciphered broadcast assistance data.
8.2.1.22 UE radio capability ID
This IE may be included in WB-S1 mode if both the UE and the network supports RACS and the network needs to assign a network-assigned UE radio capability ID to the UE.
8.2.1.23 UE radio capability ID deletion indication
This IE may be included in WB-S1 mode if both the UE and the network supports RACS and the network needs to trigger the UE to delete all network-assigned UE radio capability IDs stored at the UE for the serving PLMN.
8.2.1.24 Negotiated WUS assistance information
The network shall include the Negotiated WUS assistance information IE if:
– the UE supports WUS assistance;
– the MME supports and accepts the use of WUS assistance; and
– the UE is not attaching for emergency bearer services.
8.2.1.25 Negotiated DRX parameter in NB-S1 mode
The network shall include the Negotiated DRX parameter in NB-S1 mode IE if the UE has included the DRX parameter in NB-S1 mode IE in the ATTACH REQUEST message.
8.2.1.26 Negotiated IMSI offset
The network shall include the Negotiated IMSI offset IE if the network supports paging timing collision control and the MUSIM UE has included the Requested IMSI offset IE in the ATTACH REQUEST message.
8.2.1.27 Forbidden TAI(s) for the list of "forbidden tracking areas for roaming"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.1.28 Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.2 Attach complete
This message is sent by the UE to the network in response to an ATTACH ACCEPT message. See table 8.2.2.1.
Message type: ATTACH COMPLETE
Significance: dual
Direction: UE to network
Table 8.2.2.1: ATTACH COMPLETE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Attach complete message identity |
Message type 9.8 |
M |
V |
1 |
|
ESM message container |
ESM message container 9.9.3.15 |
M |
LV-E |
5-n |
8.2.3 Attach reject
8.2.3.1 Message definition
This message is sent by the network to the UE to indicate that the corresponding attach request has been rejected. See table 8.2.3.1.
Message type: ATTACH REJECT
Significance: dual
Direction: network to UE
Table 8.2.3.1: ATTACH REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Attach reject message identity |
Message type 9.8 |
M |
V |
1 |
|
EMM cause |
EMM cause 9.9.3.9 |
M |
V |
1 |
|
78 |
ESM message container |
ESM message container 9.9.3.15 |
O |
TLV-E |
6-n |
5F |
T3346 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
16 |
T3402 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
A- |
Extended EMM cause |
Extended EMM cause 9.9.3.26A |
O |
TV |
1 |
1C |
Lower bound timer value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
1D |
Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
1E |
Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
8.2.3.2 ESM message container
This IE is included to carry a single ESM message.
8.2.3.3 T3346 value
The MME may include this IE when the NAS level mobility management congestion control is active.
8.2.3.4 T3402 value
This IE may be included to indicate a value for timer T3402.
8.2.3.5 Extended EMM cause
This IE may be included by the network to indicate additional information associated with the EMM cause.
8.2.3.5A Lower bound timer value
The MME may include this IE when the EMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum timer value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
8.2.3.6 Forbidden TAI(s) for the list of "forbidden tracking areas for roaming"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.3.7 Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.4 Attach request
8.2.4.1 Message definition
This message is sent by the UE to the network in order to perform an attach procedure. See table 8.2.4.1.
Message type: ATTACH REQUEST
Significance: dual
Direction: UE to network
Table 8.2.4.1: ATTACH REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Attach request message identity |
Message type 9.8 |
M |
V |
1 |
|
EPS attach type |
EPS attach type 9.9.3.11 |
M |
V |
1/2 |
|
NAS key set identifier |
NAS key set identifier 9.9.3.21 |
M |
V |
1/2 |
|
EPS mobile identity |
EPS mobile identity 9.9.3.12 |
M |
LV |
5-12 |
|
UE network capability |
UE network capability 9.9.3.34 |
M |
LV |
3-14 |
|
ESM message container |
ESM message container 9.9.3.15 |
M |
LV-E |
5-n |
|
19 |
Old P-TMSI signature |
P-TMSI signature 9.9.3.26 |
O |
TV |
4 |
50 |
Additional GUTI |
EPS mobile identity 9.9.3.12 |
O |
TLV |
13 |
52 |
Last visited registered TAI |
Tracking area identity 9.9.3.32 |
O |
TV |
6 |
5C |
DRX parameter |
DRX parameter 9.9.3.8 |
O |
TV |
3 |
31 |
MS network capability |
MS network capability 9.9.3.20 |
O |
TLV |
4-10 |
13 |
Old location area identification |
Location area identification 9.9.2.2 |
O |
TV |
6 |
9- |
TMSI status |
TMSI status 9.9.3.31 |
O |
TV |
1 |
11 |
Mobile station classmark 2 |
Mobile station classmark 2 9.9.2.4 |
O |
TLV |
5 |
20 |
Mobile station classmark 3 |
Mobile station classmark 3 9.9.2.5 |
O |
TLV |
2-34 |
40 |
Supported Codecs |
Supported Codec List 9.9.2.10 |
O |
TLV |
5-n |
F- |
Additional update type |
Additional update type |
O |
TV |
1 |
5D |
Voice domain preference and UE’s usage setting |
Voice domain preference and UE’s usage setting 9.9.3.44 |
O |
TLV |
3 |
D- |
Device properties |
Device properties 9.9.2.0A |
O |
TV |
1 |
E- |
Old GUTI type |
GUTI type 9.9.3.45 |
O |
TV |
1 |
C- |
MS network feature support |
MS network feature support 9.9.3.20A |
O |
TV |
1 |
10 |
TMSI based NRI container |
Network resource identifier container 9.9.3.24A |
O |
TLV |
4 |
6A |
T3324 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
5E |
T3412 extended value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
6E |
Extended DRX parameters |
Extended DRX parameters 9.9.3.46 |
O |
TLV |
3 |
6F |
UE additional security capability |
UE additional security capability 9.9.3.53 |
O |
TLV |
6 |
6D |
UE status |
UE status 9.9.3.54 |
O |
TLV |
3 |
17 |
Additional information requested |
Additional information requested 9.9.3.55 |
O |
TV |
2 |
32 |
N1 UE network capability |
N1 UE network capability 9.9.3.57 |
O |
TLV |
3-15 |
34 |
UE radio capability ID availability |
UE radio capability ID availability 9.9.3.58 |
O |
TLV |
3 |
35 |
Requested WUS assistance information |
WUS assistance information 9.9.3.62 |
O |
TLV |
3-n |
36 |
DRX parameter in NB-S1 mode |
NB-S1 DRX parameter 9.9.3.63 |
O |
TLV |
3 |
38 |
Requested IMSI offset |
IMSI offset 9.9.3.64 |
O |
TLV |
4 |
8.2.4.2 Old P-TMSI signature
The UE shall include this IE if the UE holds a valid P-TMSI signature, P-TMSI and RAI, and the TIN either indicates "P-TMSI" or is deleted. If the UE is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17] and is attaching in a new PLMN that is neither the registered PLMN nor in the list of equivalent PLMNs, the UE shall not include this IE.
8.2.4.3 Additional GUTI
The UE shall include this IE if the TIN indicates "P-TMSI" and the UE holds a valid GUTI, P-TMSI and RAI. If the UE is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17] and is attaching in a new PLMN that is neither the registered PLMN nor in the list of equivalent PLMNs, the UE shall not include this IE.
8.2.4.4 Last visited registered TAI
This IE shall be included if the UE holds a valid last visited registered TAI.
8.2.4.5 DRX parameter
This IE is included if UE supports A/Gb mode or Iu mode or if the UE wants to indicate its UE specific DRX parameters to the network.
8.2.4.6 MS network capability
A UE supporting A/Gb mode or Iu mode shall include this IE to indicate its capabilities to the network.
8.2.4.7 Old location area identification
The UE shall include this IE during a combined attach procedure if it has a valid location area identification.
8.2.4.8 TMSI status
The UE shall include this IE during combined attach procedure if it has no valid TMSI available.
8.2.4.9 Mobile station classmark 2
This IE shall be included if the UE supports SRVCC to GERAN or UTRAN or supports vSRVCC to UTRAN (see 3GPP TS 23.216 [8]), or if the UE is performing a combined attach procedure.
8.2.4.10 Mobile station classmark 3
This IE shall be included if the UE supports SRVCC to GERAN.
8.2.4.11 Supported Codecs
This IE shall be included if the UE supports SRVCC to GERAN or UTRAN or supports vSRVCC to UTRAN to indicate its supported speech codecs for CS speech calls.
8.2.4.12 Additional update type
The UE shall include this IE if the UE requests "SMS only" or CIoT EPS optimizations.
8.2.4.13 Voice domain preference and UE’s usage setting
This IE shall be included in WB-S1 mode if and only if the UE supports:
– CS fallback and SMS over SGs; or
– if the UE is configured to support IMS voice, but does not support 1xCS fallback.
8.2.4.14 Device properties
This IE shall be included if the UE is configured for NAS signalling low priority.
8.2.4.15 Old GUTI type
The UE shall include this IE if the type of identity in the EPS mobile identity IE is set to "GUTI".
8.2.4.16 MS network feature support
This IE shall be included if the UE supports extended periodic timer T3412.
8.2.4.17 TMSI based NRI container
The UE shall include this IE during a combined attach procedure if it has a valid TMSI.
8.2.4.18 T3324 value
The UE may include this IE to request the use of PSM.
8.2.4.19 T3412 extended value
The UE may include this IE to request a particular T3412 value if the T3324 value IE is included.
8.2.4.20 Extended DRX parameters
The UE may include this IE to request the use of eDRX.
8.2.4.21 UE additional security capability
The UE shall include this IE if the UE supports dual connectivity with NR or if the UE supports N1 mode.
8.2.4.22 UE status
This IE shall be included if the UE wants to provide the network with information concerning aspects of the current UE registration status which is used for interworking with 5GS.
8.2.4.23 Additional information requested
The UE shall include this IE if the UE supports ciphered broadcast assistance data and the UE needs to obtain new ciphering keys for ciphered broadcast assistance data.
8.2.4.24 N1 UE network capability
The UE shall include this IE if the UE supports N1 mode and needs to indicate the supported CIoT network behaviour for 5GCN.
8.2.4.25 UE radio capability ID availability IE
The UE shall include this IE in WB-S1 mode if the UE supports RACS and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected PLMN.
8.2.4.26 Requested WUS assistance information
The UE may include this IE if it supports WUS assistance and it is not attaching for emergency bearer services.
8.2.4.27 DRX parameter in NB-S1 mode
This IE is included if the UE intends to use the UE specific DRX parameter in NB-S1 mode.
8.2.4.28 Requested IMSI offset
The MUSIM UE may include this IE if the UE needs to indicate an IMSI offset value to the network as specified in 3GPP TS 23.401 [10] that is used for deriving the paging occasion as specified in 3GPP TS 36.304 [21].
8.2.5 Authentication failure
8.2.5.1 Message definition
This message is sent by the UE to the network to indicate that authentication of the network has failed. See table 8.2.5.1.
Message type: AUTHENTICATION FAILURE
Significance: dual
Direction: UE to network
Table 8.2.5.1: AUTHENTICATION FAILURE message content
IEI |
Information element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Authentication failure message type |
Message type 9.8 |
M |
V |
1 |
|
EMM cause |
EMM cause 9.9.3.9 |
M |
V |
1 |
|
30 |
Authentication failure parameter |
Authentication failure parameter 9.9.3.1 |
O |
TLV |
16 |
8.2.5.2 Authentication failure parameter
This IE shall be sent if and only if the EMM cause was #21 "synch failure". It shall include the response to the authentication challenge from the USIM, which is made up of the AUTS parameter (see 3GPP TS 33.102 [18]).
8.2.6 Authentication reject
This message is sent by the network to the UE to indicate that the authentication procedure has failed and that the UE shall abort all activities. See table 8.2.6.1.
Message type: AUTHENTICATION REJECT
Significance: dual
Direction: network to UE
Table 8.2.6.1: AUTHENTICATION REJECT message content
IEI |
Information element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Authentication reject message type |
Message type 9.8 |
M |
V |
1 |
8.2.7 Authentication request
This message is sent by the network to the UE to initiate authentication of the UE identity. See table 8.2.7.1.
Message type: AUTHENTICATION REQUEST
Significance: dual
Direction: network to UE
Table 8.2.7.1: AUTHENTICATION REQUEST message content
IEI |
Information element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Authentication request message type |
Message type 9.8 |
M |
V |
1 |
|
NAS key set identifierASME |
NAS key set identifier 9.9.3.21 |
M |
V |
1/2 |
|
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|
Authentication parameter RAND (EPS challenge) |
Authentication parameter RAND 9.9.3.3 |
M |
V |
16 |
|
Authentication parameter AUTN (EPS challenge) |
Authentication parameter AUTN 9.9.3.2 |
M |
LV |
17 |
8.2.8 Authentication response
This message is sent by the UE to the network to deliver a calculated authentication response to the network. See table 8.2.8.1.
Message type: AUTHENTICATION RESPONSE
Significance: dual
Direction: UE to network
Table 8.2.8.1: AUTHENTICATION RESPONSE message content
IEI |
Information element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Authentication response message type |
Message type 9.8 |
M |
V |
1 |
|
Authentication response parameter |
Authentication response parameter 9.9.3.4 |
M |
LV |
5-17 |
8.2.9 CS service notification
8.2.9.1 Message definition
This message is sent by the network when a paging request with CS call indicator was received via SGs for a UE, and a NAS signalling connection is already established for the UE. See table 8.2.9.1.
Message type: CS SERVICE NOTIFICATION
Significance: dual
Direction: network to UE
Table 8.2.9.1: CS SERVICE NOTIFICATION message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
CS service notification message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
Paging identity |
Paging identity 9.9.3.25A |
M |
V |
1 |
|||||||
60 |
CLI |
CLI 9.9.3.38 |
O |
TLV |
3-14 |
||||||
61 |
SS Code |
SS Code 9.9.3.39 |
O |
TV |
2 |
||||||
62 |
LCS indicator |
LCS indicator 9.9.3.40 |
O |
TV |
2 |
||||||
63 |
LCS client identity |
LCS client identity 9.9.3.41 |
O |
TLV |
3-257 |
8.2.9.2 CLI
The network shall send this IE if it was received via SGs. It contains the identification of the calling line for the mobile terminating call in the CS domain, which triggered the paging via SGs.
8.2.9.3 SS Code
The network shall send this IE if it was received via SGs. It contains information on the supplementary service transaction in the CS domain, which triggered the paging via SGs.
8.2.9.4 LCS indicator
The network shall send this IE if it was received via SGs. It indicates that the paging was triggered by a terminating LCS request in the CS domain.
8.2.9.5 LCS client identity
The network shall send this IE if received via SGs. It contains information related to the requestor of the terminating LCS request in the CS domain.
8.2.9.6 Void
Void.
8.2.10 Detach accept
8.2.10.1 Detach accept (UE originating detach)
This message is sent by the network to indicate that the detach procedure has been completed. See table 8.2.10.1.1.
Message type: DETACH ACCEPT
Significance: dual
Direction: network to UE
Table 8.2.10.1.1: DETACH ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Detach accept message identity |
Message type 9.8 |
M |
V |
1 |
8.2.10.2 Detach accept (UE terminated detach)
This message is sent by the UE to indicate that the detach procedure has been completed. See table 8.2.10.2.1.
Message type: DETACH ACCEPT
Significance: dual
Direction: UE to network
Table 8.2.10.2.1: DETACH ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Detach accept message identity |
Message type 9.8 |
M |
V |
1 |
8.2.11 Detach request
8.2.11.1 Detach request (UE originating detach)
This message is sent by the UE to request the release of an EMM context. See table 8.2.11.1.1.
Message type: DETACH REQUEST
Significance: dual
Direction: UE to network
Table 8.2.11.1.1: DETACH REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Detach request message identity |
Message type 9.8 |
M |
V |
1 |
|
Detach type |
Detach type 9.9.3.7 |
M |
V |
1/2 |
|
NAS key set identifier |
NAS key set identifier 9.9.3.21 |
M |
V |
1/2 |
|
EPS mobile identity |
EPS mobile identity 9.9.3.12 |
M |
LV |
5-12 |
8.2.11.2 Detach request (UE terminated detach)
8.2.11.2.1 Message definition
This message is sent by the network to request the release of an EMM context. See table 8.2.11.2.1.
Message type: DETACH REQUEST
Significance: dual
Direction: network to UE
Table 8.2.11.2.1: DETACH REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Detach request message identity |
Message type 9.8 |
M |
V |
1 |
|
Detach type |
Detach type 9.9.3.7 |
M |
V |
1/2 |
|
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|
53 |
EMM cause |
EMM cause 9.9.3.9 |
O |
TV |
2 |
1C |
Lower bound timer value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
1D |
Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
9-98 |
1E |
Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
9-98 |
8.2.11.2.2 EMM cause
This information element is included if an EMM cause is provided.
8.2.11.2.3 Forbidden TAI(s) for the list of "forbidden tracking areas for roaming"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.11.2.4 Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.11.2.5 Lower bound timer value
The MME may include this IE when the EMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum timer value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
8.2.12 Downlink NAS Transport
This message is sent by the network to the UE in order to carry an SMS message in encapsulated format. See table 8.2.12.1.
Message type: DOWNLINK NAS TRANSPORT
Significance: dual
Direction: network to UE
Table 8.2.12.1: DOWNLINK NAS TRANSPORT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Downlink NAS transport message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
NAS message container |
NAS message container 9.9.3.22 |
M |
LV |
3-252 |
8.2.13 EMM information
8.2.13.1 Message definition
This message is sent by the network at any time during EMM context is established to send certain information to the UE. See table 8.2.13.1.
Message type: EMM INFORMATION
Significance: local
Direction: network to UE
Table 8.2.13.1: EMM INFORMATION message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
EMM information message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
43 |
Full name for network |
Network name 9.9.3.24 |
O |
TLV |
3-n |
||||||
45 |
Short name for network |
Network name 9.9.3.24 |
O |
TLV |
3-n |
||||||
46 |
Local time zone |
Time zone 9.9.3.29 |
O |
TV |
2 |
||||||
47 |
Universal time and local time zone |
Time zone and time 9.9.3.30 |
O |
TV |
8 |
||||||
49 |
Network daylight saving time |
Daylight saving time 9.9.3.6 |
O |
TLV |
3 |
8.2.13.2 Full name for network
This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the "full length name of the network" that the network wishes the UE to associate with the MCC and MNC contained in the last visited tracking area identification.
8.2.13.3 Short name for network
This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the "abbreviated name of the network" that the network wishes the UE to associate with the MCC and MNC contained in the last visited tracking area identification.
8.2.13.4 Local time zone
This IE may be sent by the network. The UE should assume that this time zone applies to the tracking area of the current cell, and also applies to the tracking area list if available in the UE.
NOTE: The time information can be inaccurate, especially when the TAI list includes tracking areas belonging to different time zones.
If the local time zone has been adjusted for daylight saving time, the network shall indicate this by including the Network daylight saving time IE.
8.2.13.5 Universal time and local time zone
This IE may be sent by the network. The UE should assume that this time zone applies to the tracking area the UE is currently in, and also applies to the tracking area list if available in the UE. The UE shall not assume that the time information is accurate.
NOTE: The time information can be inaccurate, especially when the TAI list includes tracking areas belonging to different time zones.
If the local time zone has been adjusted for daylight saving time, the network shall indicate this by including the Network daylight saving time IE.
8.2.13.6 Network daylight saving time
This IE may be sent by the network. If this IE is sent, the contents of this IE indicates the value that has been used to adjust the local time zone.
8.2.14 EMM status
This message is sent by the UE or by the network at any time to report certain error conditions listed in clause 7. See table 8.2.14.1.
Message type: EMM STATUS
Significance: local
Direction: both
Table 8.2.14.1: EMM STATUS message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
EMM status message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
EMM cause |
EMM cause 9.9.3.9 |
M |
V |
1 |
8.2.15 Extended service request
8.2.15.1 Message definition
This message is sent by the UE to the network
– to initiate a CS fallback or 1xCS fallback call or respond to a mobile terminated CS fallback or 1xCS fallback request from the network; or
– to request the establishment of a NAS signalling connection and of the radio and S1 bearers for packet services, if the UE needs to provide additional information that cannot be provided via a SERVICE REQUEST message.
See table 8.2.15.1.
Message type: EXTENDED SERVICE REQUEST
Significance: dual
Direction: UE to network
Table 8.2.15.1: EXTENDED SERVICE REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Extended service request message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
Service type |
Service type 9.9.3.27 |
M |
V |
1/2 |
|||||||
NAS key set identifier |
NAS key set identifier 9.9.3.21 |
M |
V |
1/2 |
|||||||
M-TMSI |
Mobile identity 9.9.2.3 |
M |
LV |
6 |
|||||||
B- |
CSFB response |
CSFB response 9.9.3.5 |
C |
TV |
1 |
||||||
57 |
EPS bearer context status |
EPS bearer context status 9.9.2.1 |
O |
TLV |
4 |
||||||
D- |
Device properties |
Device properties 9.9.2.0A |
O |
TV |
1 |
||||||
29 |
UE request type |
UE request type 9.9.3.65 |
O |
TLV |
3 |
||||||
28 |
Paging restriction |
Paging restriction 9.9.3.66 |
O |
TLV |
3-5 |
8.2.15.2 CSFB response
The UE shall include this IE only if the Service type information element indicates "mobile terminating CS fallback or 1xCS fallback".
NOTE: The UE does not include this IE for mobile terminating 1xCS fallback.
8.2.15.3 EPS bearer context status
This IE shall be included if the UE wants to indicate the EPS bearer contexts that are active within the UE.
8.2.15.4 Device properties
The UE shall include this IE if the UE is configured for NAS signalling low priority.
8.2.15.5 UE request type
The UE shall include this IE if the MUSIM UE requests the release of the NAS signalling connection or rejects the paging request from the network.
8.2.15.6 Paging restriction
The UE shall include this IE if the Request type is set to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE and the UE requests the network to restrict paging.
8.2.16 GUTI reallocation command
8.2.16.1 Message definition
This message is sent by the network to the UE to reallocate a GUTI and optionally to provide a new TAI list or a new DCN-ID or both. See table 8.2.16.1.
Message type: GUTI REALLOCATION COMMAND
Significance: dual
Direction: network to UE
Table 8.2.16.1: GUTI REALLOCATION COMMAND message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
GUTI reallocation command message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
GUTI |
EPS mobile identity 9.9.3.12 |
M |
LV |
12 |
|||||||
54 |
TAI list |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
||||||
65 |
DCN-ID |
DCN-ID 9.9.3.48 |
O |
TLV |
4 |
||||||
66 |
UE radio capability ID |
UE radio capability ID 9.9.3.60 |
O |
TLV |
3-n |
||||||
B- |
UE radio capability ID deletion indication |
UE radio capability ID deletion indication 9.9.3.61 |
O |
TV |
1 |
8.2.16.2 TAI list
This IE may be included to assign a TAI list to the UE.
8.2.16.3 DCN-ID
This IE may be included to assign a new DCN-ID to the UE.
8.2.16.4 UE radio capability ID
This IE may be included in WB-S1 mode if both the UE and the network support RACS and the network needs to assign a network-assigned UE radio capability ID to the UE.
8.2.16.5 UE radio capability ID deletion indication
This IE may be included in WB-S1 mode if both the UE and the network support RACS and the network needs to trigger the UE to delete all network-assigned UE radio capability IDs stored at the UE for the serving PLMN.
8.2.17 GUTI reallocation complete
This message is sent by the UE to the network to indicate that reallocation of a GUTI has taken place. See table 8.2.17.1.
Message type: GUTI REALLOCATION COMPLETE
Significance: dual
Direction: UE to network
Table 8.2.17.1: GUTI REALLOCATION COMPLETE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
GUTI reallocation complete message identity |
Message type 9.8 |
M |
V |
1 |
8.2.18 Identity request
This message is sent by the network to the UE to request the UE to provide the specified identity. See table 8.2.18.1.
Message type: IDENTITY REQUEST
Significance: dual
Direction: network to UE
Table 8.2.18.1: IDENTITY REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Identity request message identity |
Message type 9.8 |
M |
V |
1 |
|
Identity type |
Identity type 2 9.9.3.17 |
M |
V |
1/2 |
|
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
8.2.19 Identity response
This message is sent by the UE to the network in response to an IDENTITY REQUEST message and provides the requested identity. See table 8.2.19.1.
Message type: IDENTITY RESPONSE
Significance: dual
Direction: UE to network
Table 8.2.19.1: IDENTITY RESPONSE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Identity response message |
Message type 9.8 |
M |
V |
1 |
|
Mobile identity |
Mobile identity 9.9.2.3 |
M |
LV |
4-10 |
8.2.20 Security mode command
8.2.20.1 Message definition
This message is sent by the network to the UE to establish NAS signalling security. See table 8.2.20.1.
Message type: SECURITY MODE COMMAND
Significance: dual
Direction: network to UE
Table 8.2.20.1: SECURITY MODE COMMAND message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Security mode command message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
Selected NAS security algorithms |
NAS security algorithms 9.9.3.23 |
M |
V |
1 |
|||||||
NAS key set identifier |
NAS key set identifier 9.9.3.21 |
M |
V |
1/2 |
|||||||
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|||||||
Replayed UE security capabilities |
UE security capability 9.9.3.36 |
M |
LV |
3-6 |
|||||||
C- |
IMEISV request |
IMEISV request 9.9.3.18 |
O |
TV |
1 |
||||||
55 |
Replayed nonceUE |
Nonce 9.9.3.25 |
O |
TV |
5 |
||||||
56 |
NonceMME |
Nonce 9.9.3.25 |
O |
TV |
5 |
||||||
4F |
HashMME |
HashMME 9.9.3.50 |
O |
TLV |
10 |
||||||
6F |
Replayed UE additional security capability |
UE additional security capability 9.9.3.53 |
O |
TLV |
6 |
||||||
37 |
UE radio capability ID request |
UE radio capability ID request 9.9.3.59 |
O |
TLV |
3 |
8.2.20.2 IMEISV request
The MME may include this information element to request the UE to send its IMEISV with the corresponding SECURITY MODE COMPLETE message.
8.2.20.3 Replayed nonceUE
The MME may include this information element to indicate to the UE to use the replayed nonceUE.
8.2.20.4 NonceMME
The MME may include this information element to indicate to the UE to use the nonceMME.
8.2.20.5 HashMME
The MME shall include this information element when the MME is initiating a SECURITY MODE COMMAND during an attach or tracking area updating procedure and the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message was received without integrity protection or did not successfully pass the integrity check at the MME.
8.2.20.6 Replayed UE additional security capability
The MME shall include this IE if the MME supports handling of UE additional security capabilities, the MME is initiating a SECURITY MODE COMMAND during an attach or tracking area updating procedure and the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message included a UE additional security capability IE.
8.2.20.7 UE radio capability ID request
The MME may include this information element in WB-S1 mode to request the UE to send its UE radio capability ID with the corresponding SECURITY MODE COMPLETE message.
8.2.21 Security mode complete
8.2.21.1 Message definition
This message is sent by the UE to the network in response to a SECURITY MODE COMMAND message. See table 8.2.21.1.
Message type: SECURITY MODE COMPLETE
Significance: dual
Direction: UE to network
Table 8.2.21.1: SECURITY MODE COMPLETE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Security mode complete message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
23 |
IMEISV |
Mobile identity 9.9.2.3 |
O |
TLV |
11 |
||||||
79 |
Replayed NAS message container |
Replayed NAS message container 9.9.3.51 |
O |
TLV-E |
3-n |
||||||
66 |
UE radio capability ID |
UE radio capability ID 9.9.3.60 |
O |
TLV |
3-n |
8.2.21.2 IMEISV
The UE shall include this information element, if the IMEISV was requested within the corresponding SECURITY MODE COMMAND message.
8.2.21.3 Replayed NAS message container
The UE shall include this information element, if during an ongoing attach or tracking area updating procedure, the MME included HASHMME in the SECURITY MODE COMMAND message and HASHMME has a different value from the hash value locally calculated at the UE as described in 3GPP TS 33.401 [19].
8.2.21.4 UE radio capability ID
The UE shall include this information element in WB-S1 mode if the UE radio capability ID was requested within the corresponding SECURITY MODE COMMAND message.
8.2.22 Security mode reject
This message is sent by the UE to the network to indicate that the corresponding security mode command has been rejected. See table 8.2.22.1.
Message type: SECURITY MODE REJECT
Significance: dual
Direction: UE to network
Table 8.2.22.1: SECURITY MODE REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Security mode reject message identity |
Message type 9.8 |
M |
V |
1 |
|
EMM cause |
EMM cause 9.9.3.9 |
M |
V |
1 |
8.2.23 Security protected NAS message
This message is sent by the UE or the network to transfer a NAS message together with the sequence number and the message authentication code protecting the message. See table 8.2.23.1.
Message type: SECURITY PROTECTED NAS MESSAGE
Significance: dual
Direction: both
Table 8.2.23.1: SECURITY PROTECTED NAS MESSAGE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Message authentication code |
Message authentication code 9.5 |
M |
V |
4 |
|
Sequence number |
Sequence number 9.6 |
M |
V |
1 |
|
NAS message |
NAS message 9.7 |
M |
V |
1-n |
8.2.24 Service reject
8.2.24.1 Message definition
This message is sent by the network to the UE in order to reject the service request procedure. See table 8.2.24.1.
Message type: SERVICE REJECT
Significance: dual
Direction: network to UE
Table 8.2.24.1: SERVICE REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Service reject message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
EMM cause |
EMM cause 9.9.3.9 |
M |
V |
1 |
|||||||
5B |
T3442 value |
GPRS timer 9.9.3.16 |
C |
TV |
2 |
||||||
5F |
T3346 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
||||||
6B |
T3448 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
||||||
1C |
Lower bound timer value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
1D |
Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
9-98 |
||||||
1E |
Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
9-98 |
8.2.24.2 T3442 value
The MME shall include this IE when the EMM cause value is #39 "CS service temporarily not available".
8.2.24.3 T3346 value
The MME may include this IE when the general NAS level mobility management congestion control is active.
8.2.24.4 T3448 value
The network may include this IE if the congestion control for transport of user data via the control plane is active and the UE supports timer T3448.
8.2.24.5 Forbidden TAI(s) for the list of "forbidden tracking areas for roaming"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.24.6 Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.24.7 Lower bound timer value
The MME may include this IE when the EMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum timer value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
8.2.25 Service request
This message is sent by the UE to the network to request the establishment of a NAS signalling connection and of the radio and S1 bearers. Its structure does not follow the structure of a standard layer 3 message. See table 8.2.25.1.
Message type: SERVICE REQUEST
Significance: dual
Direction: UE to network
Table 8.2.25.1: SERVICE REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
KSI and sequence number |
KSI and sequence number 9.9.3.19 |
M |
V |
1 |
|||||||
Message authentication code (short) |
Short MAC 9.9.3.28 |
M |
V |
2 |
8.2.26 Tracking area update accept
8.2.26.1 Message definition
This message is sent by the network to the UE to provide the UE with EPS mobility management related data in response to a tracking area update request message. See table 8.2.26.1.
Message type: TRACKING AREA UPDATE ACCEPT
Significance: dual
Direction: network to UE
Table 8.2.26.1: TRACKING AREA UPDATE ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Tracking area update accept message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
EPS update result |
EPS update result 9.9.3.13 |
M |
V |
1/2 |
|||||||
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|||||||
5A |
T3412 value |
GPRS timer 9.9.3.16 |
O |
TV |
2 |
||||||
50 |
GUTI |
EPS mobile identity 9.9.3.12 |
O |
TLV |
13 |
||||||
54 |
TAI list |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
||||||
57 |
EPS bearer context status |
EPS bearer context status 9.9.2.1 |
O |
TLV |
4 |
||||||
13 |
Location area identification |
Location area identification 9.9.2.2 |
O |
TV |
6 |
||||||
23 |
MS identity |
Mobile identity 9.9.2.3 |
O |
TLV |
7-10 |
||||||
53 |
EMM cause |
EMM cause 9.9.3.9 |
O |
TV |
2 |
||||||
17 |
T3402 value |
GPRS timer 9.9.3.16 |
O |
TV |
2 |
||||||
59 |
T3423 value |
GPRS timer 9.9.3.16 |
O |
TV |
2 |
||||||
4A |
Equivalent PLMNs |
PLMN list 9.9.2.8 |
O |
TLV |
5-47 |
||||||
34 |
Emergency number list |
Emergency number list 9.9.3.37 |
O |
TLV |
5-50 |
||||||
64 |
EPS network feature support |
EPS network feature support 9.9.3.12A |
O |
TLV |
3-4 |
||||||
F- |
Additional update result |
Additional update result |
O |
TV |
1 |
||||||
5E |
T3412 extended value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
6A |
T3324 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
||||||
6E |
Extended DRX parameters |
Extended DRX parameters 9.9.3.46 |
O |
TLV |
3 |
||||||
68 |
Header compression configuration status |
Header compression configuration status 9.9.4.27 |
O |
TLV |
4 |
||||||
65 |
DCN-ID |
DCN-ID 9.9.3.48 |
O |
TLV |
4 |
||||||
E- |
SMS services status |
SMS services status 9.9.3.4B |
O |
TV |
1 |
||||||
D- |
Non-3GPP NW policies |
Non-3GPP NW provided policies 9.9.3.49 |
O |
TV |
1 |
||||||
6B |
T3448 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
||||||
C- |
Network policy |
Network policy 9.9.3.52 |
O |
TV |
1 |
||||||
6C |
T3447 value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
7A |
Extended emergency number list |
Extended emergency number list 9.9.3.37A |
O |
TLV-E |
7-65538 |
||||||
7C |
Ciphering key data |
Ciphering key data 9.9.3.56 |
O |
TLV-E |
35-2291 |
||||||
66 |
UE radio capability ID |
UE radio capability ID 9.9.3.60 |
O |
TLV |
3-n |
||||||
B- |
UE radio capability ID deletion indication |
UE radio capability ID deletion indication 9.9.3.61 |
O |
TV |
1 |
||||||
35 |
Negotiated WUS assistance information |
WUS assistance information 9.9.3.62 |
O |
TLV |
3-n |
||||||
36 |
Negotiated DRX parameter in NB-S1 mode |
NB-S1 DRX parameter 9.9.3.63 |
O |
TLV |
3 |
||||||
38 |
Negotiated IMSI offset |
IMSI offset 9.9.3.64 |
O |
TLV |
4 |
||||||
37 |
EPS additional request result |
EPS additional request result 9.9.3.67 |
O |
TLV |
3 |
||||||
1D |
Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
||||||
1E |
Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service " |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
8.2.26.2 T3412 value
The MME shall include this IE during normal and combined tracking area updating procedure, and may include this IE during periodic tracking area updating procedure.
The MME shall include this IE if it includes the T3412 extended value IE.
8.2.26.3 GUTI
This IE may be included to assign a GUTI to a UE.
8.2.26.4 TAI list
This IE may be included to assign a TAI list to a UE.
8.2.26.5 EPS bearer context status
This IE shall be included if the network wants to indicate the EPS bearer contexts that are active for the UE in the network.
8.2.26.6 Location area identification
This IE may be included to assign a new location area identification to a UE during a combined TA/LA update.
8.2.26.7 MS identity
This IE may be included to assign or unassign a new TMSI to a UE during a combined TA/LA update.
8.2.26.8 EMM cause
This IE shall be included if the combined tracking area updating procedure was successful for EPS services only.
8.2.26.9 T3402 value
This IE may be included to indicate a value for timer T3402.
8.2.26.10 T3423 value
This IE may be included to indicate a value for timer T3423.
If this IE is not included, the UE shall use the default value.
8.2.26.11 Equivalent PLMNs
This IE may be included in order to assign an equivalent PLMNs list to a UE.
8.2.26.12 Emergency number list
This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers valid within the same country as in the PLMN from which this IE is received.
8.2.26.12A Extended emergency number list
This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers (with URN information) valid within the same country as in the PLMN from which this IE is received or valid only in the PLMN from which this IE is received.
8.2.26.13 EPS network feature support
The network may include this IE to inform the UE of the support of certain features. If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero, except for the S1-u data transfer (S1-U data) (octet 4, bit 2).
NOTE: In this exceptional case, the UE deems that the network supports S1-u data transfer.
8.2.26.14 Additional update result
The network may include this IE to provide the UE with additional information about the result of:
– a combined tracking area updating procedure if the procedure was successful for EPS services and non-EPS services, or for EPS services and "SMS only"; or
– a normal tracking area updating procedure requested for CIoT EPS optimizations if the procedure was successful for EPS services and "SMS only".
8.2.26.15 T3412 extended value
The network may include this IE to provide the UE with a longer periodic tracking area update timer.
8.2.26.16 T3324 value
The network shall include the T3324 value IE if:
– the UE included the T3324 value IE in the TRACKING AREA UPDATE REQUEST message; and
– the network supports PSM and accepts the use of PSM.
8.2.26.17 Extended DRX parameters
The network shall include the Extended DRX parameters IE if:
– the UE included the Extended DRX parameters IE in the TRACKING AREA UPDATE REQUEST message; and
– the network supports eDRX and accepts the use of eDRX.
8.2.26.18 DCN-ID
This IE is included in the message when the network wishes to provide a DCN-ID to the UE.
8.2.26.19 SMS services status
This IE may be included when a normal tracking area updating procedure for EPS services and "SMS only" was successful for EPS services only.
8.2.26.20 Non-3GPP NW provided policies
This IE is included if the network needs to indicate whether emergency numbers provided via non-3GPP access can be used to initiate UE detected emergency calls (see 3GPP TS 24.302 [48]). If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero.
8.2.26.21 T3448 value
The network may include this IE if the congestion control for transport of user data via the control plane is active and the UE supports timer T3448.
8.2.26.22 Network policy
This IE is included if the network needs to indicate network policy information to the UE. If this IE is not included, then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero.
8.2.26.23 T3447 value
The network may include T3447 value IE if:
– the UE has indicated support for service gap control in the TRACKING AREA UPDATE REQUEST messages; and
– the EMM context contains a service gap time value.
8.2.26.24 Ciphering key data
This IE is included if the network needs to send ciphering key data to the UE for ciphered broadcast assistance data.
8.2.26.25 UE radio capability ID
This IE may be included in WB-S1 mode if both the UE and the network supports RACS and the network needs to assign a network-assigned UE radio capability ID to the UE.
8.2.26.26 UE radio capability ID deletion indication
This IE may be included in WB-S1 mode if both the UE and the network supports RACS and the network needs to trigger the UE to delete all network-assigned UE radio capability IDs stored at the UE for the serving PLMN.
8.2.26.27 Negotiated WUS assistance information
The network shall include the Negotiated WUS assistance information IE if:
– the UE supports WUS assistance;
– the MME supports and accepts the use of WUS assistance; and
– the UE is not attaching for emergency bearer services.
8.2.26.28 Negotiated DRX parameter in NB-S1 mode
The network shall include the Negotiated DRX parameter in NB-S1 mode IE if the UE has included the DRX parameter in NB-S1 mode IE in the TRACKING AREA UPDATE REQUEST message.
8.2.26.29 Negotiated IMSI offset
The network shall include the Negotiated IMSI offset IE if the network supports paging timing collision control and the MUSIM UE has included the Requested IMSI offset IE in the TRACKING AREA UPDATE REQUEST message.
8.2.26.30 EPS additional request result
The network may include this IE to inform the UE about the result of additional request.
8.2.26.31 Forbidden TAI(s) for the list of "forbidden tracking areas for roaming"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.26.32 Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.27 Tracking area update complete
This message shall be sent by the UE to the network in response to a tracking area update accept message if a GUTI has been changed or a new TMSI has been assigned. See table 8.2.27.1.
Message type: TRACKING AREA UPDATE COMPLETE
Significance: dual
Direction: UE to network
Table 8.2.27.1: TRACKING AREA UPDATE COMPLETE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Tracking area update complete message identity |
Message type 9.8 |
M |
V |
1 |
8.2.28 Tracking area update reject
8.2.28.1 Message definition
This message is sent by the network to the UE in order to reject the tracking area updating procedure. See table 8.2.28.1.
Message type: TRACKING AREA UPDATE REJECT
Significance: dual
Direction: network to UE
Table 8.2.28.1: TRACKING AREA UPDATE REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Tracking area update reject message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
EMM cause |
EMM cause 9.9.3.9 |
M |
V |
1 |
|||||||
5F |
T3346 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
||||||
A- |
Extended EMM cause |
Extended EMM cause 9.9.3.26A |
O |
TV |
1 |
||||||
1C |
Lower bound timer value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
1D |
Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
9-98 |
||||||
1E |
Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
9-98 |
8.2.28.2 T3346 value
The MME may include this IE when the general NAS level mobility management congestion control is active.
8.2.28.3 Extended EMM cause
This IE may be included by the network to indicate additional information associated with the EMM cause.
8.2.28.4 Forbidden TAI(s) for the list of "forbidden tracking areas for roaming"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.28.5 Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.28.6 Lower bound timer value
The MME may include this IE when the EMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum timer value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
8.2.29 Tracking area update request
8.2.29.1 Message definition
The purposes of sending the tracking area update request by the UE to the network are described in clause 5.5.3.1. See table 8.2.29.1.
Message type: TRACKING AREA UPDATE REQUEST
Significance: dual
Direction: UE to network
Table 8.2.29.1: TRACKING AREA UPDATE REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Tracking area update request message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
EPS update type |
EPS update type 9.9.3.14 |
M |
V |
1/2 |
|||||||
NAS key set identifier |
NAS key set identifier 9.9.3.21 |
M |
V |
1/2 |
|||||||
Old GUTI |
EPS mobile identity 9.9.3.12 |
M |
LV |
12 |
|||||||
B- |
Non-current native NAS key set identifier |
NAS key set identifier 9.9.3.21 |
O |
TV |
1 |
||||||
8- |
GPRS ciphering key sequence number |
Ciphering key sequence number 9.9.3.4a |
O |
TV |
1 |
||||||
19 |
Old P-TMSI signature |
P-TMSI signature 9.9.3.26 |
O |
TV |
4 |
||||||
50 |
Additional GUTI |
EPS mobile identity 9.9.3.12 |
O |
TLV |
13 |
||||||
55 |
NonceUE |
Nonce 9.9.3.25 |
O |
TV |
5 |
||||||
58 |
UE network capability |
UE network capability 9.9.3.34 |
O |
TLV |
4-15 |
||||||
52 |
Last visited registered TAI |
Tracking area identity 9.9.3.32 |
O |
TV |
6 |
||||||
5C |
DRX parameter |
DRX parameter 9.9.3.8 |
O |
TV |
3 |
||||||
A- |
UE radio capability information update needed |
UE radio capability information update needed 9.9.3.35 |
O |
TV |
1 |
||||||
57 |
EPS bearer context status |
EPS bearer context status 9.9.2.1 |
O |
TLV |
4 |
||||||
31 |
MS network capability |
MS network capability 9.9.3.20 |
O |
TLV |
4-10 |
||||||
13 |
Old location area identification |
Location area identification 9.9.2.2 |
O |
TV |
6 |
||||||
9- |
TMSI status |
TMSI status 9.9.3.31 |
O |
TV |
1 |
||||||
11 |
Mobile station classmark 2 |
Mobile station classmark 2 9.9.2.4 |
O |
TLV |
5 |
||||||
20 |
Mobile station classmark 3 |
Mobile station classmark 3 9.9.2.5 |
O |
TLV |
2-34 |
||||||
40 |
Supported Codecs |
Supported Codec List 9.9.2.10 |
O |
TLV |
5-n |
||||||
F- |
Additional update type |
Additional update type |
O |
TV |
1 |
||||||
5D |
Voice domain preference and UE’s usage setting |
Voice domain preference and UE’s usage setting 9.9.3.44 |
O |
TLV |
3 |
||||||
E- |
Old GUTI type |
GUTI type 9.9.3.45 |
O |
TV |
1 |
||||||
D- |
Device properties |
Device properties 9.9.2.0A |
O |
TV |
1 |
||||||
C- |
MS network feature support |
MS network feature support 9.9.3.20A |
O |
TV |
1 |
||||||
10 |
TMSI based NRI container |
Network resource identifier container 9.9.3.24A |
O |
TLV |
4 |
||||||
6A |
T3324 value |
GPRS timer 2 9.9.3.16 |
O |
TLV |
3 |
||||||
5E |
T3412 extended value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
6E |
Extended DRX parameters |
Extended DRX parameters 9.9.3.46 |
O |
TLV |
3 |
||||||
6F |
UE additional security capability |
UE additional security capability 9.9.3.53 |
O |
TLV |
6 |
||||||
6D |
UE status |
UE status 9.9.3.54 |
O |
TLV |
3 |
||||||
17 |
Additional information requested |
Additional information requested 9.9.3.55 |
O |
TV |
2 |
||||||
32 |
N1 UE network capability |
N1 UE network capability 9.9.3.57 |
O |
TLV |
3-15 |
||||||
34 |
UE radio capability ID availability |
UE radio capability ID availability 9.9.3.58 |
O |
TLV |
3 |
||||||
35 |
Requested WUS assistance information |
WUS assistance information 9.9.3.62 |
O |
TLV |
3-n |
||||||
36 |
DRX parameter in NB-S1 mode |
NB-S1 DRX parameter 9.9.3.63 |
O |
TLV |
3 |
||||||
38 |
Requested IMSI offset |
IMSI offset 9.9.3.64 |
O |
TLV |
4 |
||||||
29 |
UE request type |
UE request type 9.9.3.65 |
O |
TLV |
3 |
||||||
28 |
Paging restriction |
Paging restriction 9.9.3.66 |
O |
TLV |
3-5 |
8.2.29.2 Non-current native NAS key set identifier
The UE shall include this IE if the UE has a valid non-current native EPS security context when the UE performs an A/Gb mode or Iu mode or N1 mode to S1 mode inter-system change in EMM-CONNECTED mode and the UE uses a mapped EPS security context to protect the TRACKING AREA UPDATE REQUEST message.
8.2.29.3 GPRS ciphering key sequence number
The UE shall include this IE if the UE performs an A/Gb mode or Iu mode to S1 mode inter-system change in EMM-IDLE mode and the TIN indicates "P-TMSI".
8.2.29.4 Old P-TMSI signature
The UE shall include this IE if the TIN indicates "P-TMSI" and the UE holds a valid P-TMSI signature, P-TMSI and RAI.
8.2.29.5 Additional GUTI
The UE shall include this IE:
a) if the TIN indicates "P-TMSI" and the UE holds a valid GUTI, P-TMSI and RAI; or
b) if the UE performs an N1 mode to S1 mode inter-system change and the UE holds a valid GUTI.
8.2.29.6 NonceUE
This IE is included if the UE performs an A/Gb mode or Iu mode to S1 mode inter-system change in idle mode and the TIN is set to "P-TMSI".
8.2.29.7 UE network capability
The UE shall include this IE, unless the UE performs a periodic tracking area updating procedure.
8.2.29.8 Last visited registered TAI
This IE shall be included if the UE holds a valid last visited registered TAI.
8.2.29.9 DRX parameter
This IE is included by the UE to indicate a change of UE specific DRX parameters to the network.
8.2.29.10 UE radio capability information update needed
The UE shall include this IE if the UE radio capability information in the network needs to be updated.
8.2.29.11 EPS bearer context status
This IE shall be included if the UE wants to indicate the EPS bearer contexts that are active within the UE.
8.2.29.12 MS network capability
A UE supporting A/Gb mode or Iu mode shall include this IE, unless the UE performs a periodic tracking area updating procedure.
8.2.29.13 Old location area identification
The UE shall include this IE during a combined tracking area updating procedure if it has a valid location area identification.
8.2.29.14 TMSI status
The UE shall include this IE during a combined tracking area updating procedure if it has no valid TMSI available.
8.2.29.15 Mobile station classmark 2
This IE shall be included if the UE supports SRVCC to GERAN or UTRAN or supports vSRVCC to UTRAN (see 3GPP TS 23.216 [8]), or if the UE is performing a combined tracking area updating procedure.
8.2.29.16 Mobile station classmark 3
This IE shall be included if the UE supports SRVCC to GERAN.
8.2.29.17 Supported Codecs
This IE shall be included if the UE supports SRVCC to GERAN or UTRAN or supports vSRVCC to UTRAN to indicate its supported speech codecs for CS speech calls.
8.2.29.18 Additional update type
The UE shall include this IE if the UE requests "SMS only" or CIoT EPS optimizations, unless the UE performs a periodic tracking area updating procedure.
8.2.29.19 Voice domain preference and UE’s usage setting
This IE shall be included in WB-S1 mode if and only if the UE supports:
– CS fallback and SMS over SGs; or
– if the UE is configured to support IMS voice, but does not support 1xCS fallback.
8.2.29.20 Old GUTI type
The UE shall include this IE.
8.2.29.21 Device properties
This IE shall be included if the UE is configured for NAS signalling low priority.
8.2.29.22 MS network feature support
This IE shall be included if the UE supports extended periodic timer T3412.
8.2.29.23 TMSI based NRI container
The UE shall include this IE if it has a valid TMSI.
8.2.29.24 T3324 value
The UE may include this IE to request the use of PSM.
8.2.29.25 T3412 extended value
The UE may include this IE to request a particular T3412 value if the T3324 value IE is included.
8.2.29.26 Extended DRX parameters
The UE may include this IE to request the use of eDRX.
8.2.29.27 UE additional security capability
The UE shall include this IE if the UE supports dual connectivity with NR or if the UE supports N1 mode.
8.2.29.28 UE status
This IE shall be included if the UE wants to provide the network with information concerning aspects of the current UE registration status which is used for interworking with 5GS.
8.2.29.29 Additional information requested
The UE shall include this IE if the UE supports ciphered broadcast assistance data and the UE needs to obtain new ciphering keys for ciphered broadcast assistance data.
8.2.29.30 N1 UE network capability
The UE shall include this IE if the UE supports N1 mode and needs to indicate the supported CIoT network behaviour for 5GCN, unless the UE performs a periodic tracking area updating procedure.
8.2.29.31 UE radio capability ID availability IE
The UE may include this IE in WB-S1 mode if the UE supports RACS and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected PLMN.
8.2.29.32 DRX parameter in NB-S1 mode
This IE is included if the UE intends to use or change the UE specific DRX parameter in NB-S1 mode, except when the UE performs a periodic tracking area updating procedure.
8.2.29.33 Requested WUS assistance information
The UE may include this IE if it supports WUS assistance and it is not attaching for emergency bearer services.
8.2.29.34 Requested IMSI offset
The MUSIM UE may include this IE if the UE needs to indicate an IMSI offset value to the network as specified in 3GPP TS 23.401 [10] that is used for deriving the paging occasion as specified in 3GPP TS 36.304 [21].
8.2.29.35 UE request type
The UE shall include this IE if the MUSIM UE requests the release of the NAS signalling connection.
8.2.29.36 Paging restriction
The UE shall include this IE if the Request type is set to "NAS signalling connection release" in the UE request type IE and the UE requests the network to restrict paging.
8.2.30 Uplink NAS Transport
This message is sent by the UE to the network in order to carry an SMS message in encapsulated format. See table 8.2.30.1.
Message type: UPLINK NAS TRANSPORT
Significance: dual
Direction: UE to network
Table 8.2.30.1: UPLINK NAS TRANSPORT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Uplink NAS transport message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
NAS message container |
NAS message container 9.9.3.22 |
M |
LV |
3-252 |
8.2.31 Downlink generic NAS transport
8.2.31.1 Message definition
This message is sent by the network to the UE in order to carry an application message in encapsulated format. See table 8.2.31.1.
Message type: DOWNLINK GENERIC NAS TRANSPORT
Significance: dual
Direction: network to UE
Table 8.2.31.1: DOWNLINK GENERIC NAS TRANSPORT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Downlink generic NAS transport message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
Generic message container type |
Generic message container type 9.9.3.42 |
M |
V |
1 |
|||||||
Generic message container |
Generic message container 9.9.3.43 |
M |
LV-E |
3-n |
|||||||
65 |
Additional information |
Additional information 9.9.2.0 |
O |
TLV |
3-n |
8.2.31.2 Additional information
The MME may include this information element if the application wants to send any additional information.
8.2.32 Uplink generic NAS transport
8.2.32.1 Message definition
This message is sent by the UE to the network in order to carry an application protocol message in encapsulated format. See table 8.2.32.1.
Message type: UPLINK GENERIC NAS TRANSPORT
Significance: dual
Direction: UE to network
Table 8.2.32.1: UPLINK GENERIC NAS TRANSPORT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|||||||
Uplink generic NAS transport message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
Generic message container type |
Generic message container type 9.9.3.42 |
M |
V |
1 |
|||||||
Generic message container |
Generic message container 9.9.3.43 |
M |
LV-E |
3-n |
|||||||
65 |
Additional information |
Additional information 9.9.2.0 |
O |
TLV |
3-n |
8.2.32.2 Additional information
The UE may include this information element if the application wants to send any additional information.
8.2.33 CONTROL PLANE SERVICE REQUEST
8.2.33.1 Message definition
This message is sent by the UE to the network when the UE is using EPS services with control plane CIoT EPS optimization. See table 8.2.33.1.
Message type: CONTROL PLANE SERVICE REQUEST
Significance: dual
Direction: UE to network
Table 8.2.33.1: CONTROL PLANE SERVICE REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Control plane service request message identity |
Message type 9.8 |
M |
V |
1 |
|
Control plane service type |
Control plane service type 9.9.3.47 |
M |
V |
1/2 |
|
NAS key set identifier |
NAS key set identifier 9.9.3.21 |
M |
V |
1/2 |
|
78 |
ESM message container |
ESM message container 9.9.3.15 |
O |
TLV-E |
3-n |
67 |
NAS message container |
NAS message container 9.9.3.22 |
O |
TLV |
4-253 |
57 |
EPS bearer context status |
EPS bearer context status 9.9.2.1 |
O |
TLV |
4 |
D- |
Device properties |
Device properties 9.9.2.0A |
O |
TV |
1 |
29 |
UE request type |
UE request type 9.9.3.65 |
O |
TLV |
3 |
28 |
Paging restriction |
Paging restriction 9.9.3.66 |
O |
TLV |
3-5 |
8.2.33.2 ESM message container
The UE shall include this IE, if it wants to send an ESM message to the network.
8.2.33.3 NAS message container
The UE shall include this IE, if it is in EMM-IDLE mode and has pending SMS messages to be sent.
8.2.33.4 EPS bearer context status
The UE shall include this IE, if it wants to indicate the EPS bearer contexts that are active within the UE.
8.2.33.5 Device properties
The UE shall include this IE if the UE is configured for NAS signalling low priority.
8.2.33.6 UE request type
The UE shall include this IE if the MUSIM UE requests the release of the NAS signalling connection or rejects the paging request from the network.
8.2.33.7 Paging restriction
The UE shall include this IE if the Request type is set to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE and the UE requests the network to restrict paging.
8.2.34 Service Accept
8.2.34.1 Message definition
This message is sent by the network in response to the SERVICE REQUEST message, the EXTENDED SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message. See table 8.2.34.1.
Message type: SERVICE ACCEPT
Significance: dual
Direction: network to UE
Table 8.2.34.1: SERVICE ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
Security header type |
Security header type 9.3.1 |
M |
V |
1/2 |
|
Service accept message identity |
Message type 9.8 |
M |
V |
1 |
|
57 |
EPS bearer context status |
EPS bearer context status 9.9.2.1 |
O |
TLV |
4 |
6B |
T3448 value |
GPRS timer 2 9.9.3.16A |
O |
TLV |
3 |
37 |
EPS additional request result |
EPS additional request result 9.9.3.67 |
O |
TLV |
3 |
1D |
Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
1E |
Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" |
Tracking area identity list 9.9.3.33 |
O |
TLV |
8-98 |
8.2.34.2 EPS bearer context status
This IE shall be included if the network wants to indicate the EPS bearer contexts that are active for the UE in the network.
8.2.34.3 T3448 value
The network may include this IE if the congestion control for transport of user data via the control plane is active and the UE supports timer T3448.
8.2.34.4 EPS additional request result
The network may include this IE to inform the UE about the result of additional request.
8.2.34.5 Forbidden TAI(s) for the list of "forbidden tracking areas for roaming"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite E-UTRAN access.
8.2.34.6 Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service"
This IE is included to indicate the forbidden TAI(s) to be stored in the list of "forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite E-UTRAN access.
8.3 EPS session management messages
8.3.1 Activate dedicated EPS bearer context accept
8.3.1.1 Message definition
This message is sent by the UE to the network to acknowledge activation of a dedicated EPS bearer context associated with the same PDN address(es) and APN as an already active EPS bearer context. See table 8.3.1.1.
Message type: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
Significance: dual
Direction: UE to network
Table 8.3.1.1: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
|||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
||||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
||||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
||||||||
Activate dedicated EPS bearer context accept message identity |
Message type 9.8 |
M |
V |
1 |
||||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
|||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
|||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.1.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.1.3 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.1.4 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.2 Activate dedicated EPS bearer context reject
8.3.2.1 Message definition
This message is sent by UE to the network to reject activation of a dedicated EPS bearer context. See table 8.3.2.1.
Message type: ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT
Significance: dual
Direction: UE to network
Table 8.3.2.1: ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
Activate dedicated EPS bearer context reject message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
|||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.2.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.2.3 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.2.4 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.3 Activate dedicated EPS bearer context request
8.3.3.1 Message definition
This message is sent by the network to the UE to request activation of a dedicated EPS bearer context associated with the same PDN address(es) and APN as an already active default EPS bearer context. See table 8.3.3.1.
Message type: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
Significance: dual
Direction: network to UE
Table 8.3.3.1: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||||||||
Activate dedicated EPS bearer context request message identity |
Message type 9.8 |
M |
V |
1 |
|||||||||||||
Linked EPS bearer identity |
Linked EPS bearer identity 9.9.4.6 |
M |
V |
1/2 |
|||||||||||||
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|||||||||||||
EPS QoS |
EPS quality of service 9.9.4.3 |
M |
LV |
2-14 |
|||||||||||||
TFT |
Traffic flow template 9.9.4.16 |
M |
LV |
2-256 |
|||||||||||||
5D |
Transaction identifier |
Transaction identifier 9.9.4.17 |
O |
TLV |
3-4 |
||||||||||||
30 |
Negotiated QoS |
Quality of service 9.9.4.12 |
O |
TLV |
14-22 |
||||||||||||
32 |
Negotiated LLC SAPI |
LLC service access point identifier 9.9.4.7 |
O |
TV |
2 |
||||||||||||
8- |
Radio priority |
Radio priority 9.9.4.13 |
O |
TV |
1 |
||||||||||||
34 |
Packet flow Identifier |
Packet flow Identifier 9.9.4.8 |
O |
TLV |
3 |
||||||||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||||||||
C- |
WLAN offload indication |
WLAN offload acceptability 9.9.4.18 |
O |
TV |
1 |
||||||||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
||||||||||||
5C |
Extended EPS QoS |
Extended quality of service 9.9.4.30 |
O |
TLV |
12 |
8.3.3.2 Transaction identifier
If the UE supports A/Gb mode or Iu mode or both, a network supporting mobility from S1 mode to A/Gb mode or Iu mode or both shall include this IE
8.3.3.3 Negotiated QoS
If the UE supports A/Gb mode or Iu mode or both, a network supporting mobility from S1 mode to A/Gb mode or Iu mode or both shall include the corresponding R99 QoS parameter values of a PDP context.
8.3.3.4 Negotiated LLC SAPI
If the UE supports A/Gb mode, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.3.5 Radio priority
If the UE supports A/Gb mode, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.3.6 Packet flow identifier
If the UE supports A/Gb mode and BSS packet flow procedures, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.3.7 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.3.8 WLAN offload indication
This IE shall be included in the message when the network wishes to indicate if the UE is allowed to offload the traffic of the associated PDN connection to WLAN(s), as specified in clause 9.9.4.18.
8.3.3.9 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.3.10 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.3.11 Extended EPS QoS
This IE shall be included in the message only if the network wishes to transmit the maximum and guaranteed bit rate values to the UE and at least one of the values to be transmitted exceeds the maximum value specified in the EPS quality of service information element in clause 9.9.4.3.
8.3.4 Activate default EPS bearer context accept
8.3.4.1 Message definition
This message is sent by the UE to the network to acknowledge activation of a default EPS bearer context. See table 8.3.4.1.
Message type: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT
Significance: dual
Direction: UE to network
Table 8.3.4.1: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||||||||
Activate default EPS bearer context accept message identity |
Message type 9.8 |
M |
V |
1 |
|||||||||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.4.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.4.3 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.5 Activate default EPS bearer context reject
8.3.5.1 Message definition
This message is sent by UE to the network to reject activation of a default EPS bearer context. See table 8.3.5.1.
Message type: ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT
Significance: dual
Direction: UE to network
Table 8.3.5.1: ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
Activate default EPS bearer context reject message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
|||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.5.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.5.3 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.6 Activate default EPS bearer context request
8.3.6.1 Message definition
This message is sent by the network to the UE to request activation of a default EPS bearer context. See table 8.3.6.1.
Message type: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST
Significance: dual
Direction: network to UE
Table 8.3.6.1: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||||||||||||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||||||||||||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||||||||||||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||||||||||||||||
Activate default EPS bearer context request message identity |
Message type 9.8 |
M |
V |
1 |
|||||||||||||||||||||
EPS QoS |
EPS quality of service 9.9.4.3 |
M |
LV |
2-14 |
|||||||||||||||||||||
Access point name |
Access point name 9.9.4.1 |
M |
LV |
2-101 |
|||||||||||||||||||||
PDN address |
PDN address 9.9.4.9 |
M |
LV |
6-14 |
|||||||||||||||||||||
5D |
Transaction identifier |
Transaction identifier 9.9.4.17 |
O |
TLV |
3-4 |
||||||||||||||||||||
30 |
Negotiated QoS |
Quality of service 9.9.4.12 |
O |
TLV |
14-22 |
||||||||||||||||||||
32 |
Negotiated LLC SAPI |
LLC service access point identifier 9.9.4.7 |
O |
TV |
2 |
||||||||||||||||||||
8- |
Radio priority |
Radio priority 9.9.4.13 |
O |
TV |
1 |
||||||||||||||||||||
34 |
Packet flow Identifier |
Packet flow Identifier 9.9.4.8 |
O |
TLV |
3 |
||||||||||||||||||||
5E |
APN-AMBR |
APN aggregate maximum bit rate 9.9.4.2 |
O |
TLV |
4-8 |
||||||||||||||||||||
58 |
ESM cause |
ESM cause 9.9.4.4 |
O |
TV |
2 |
||||||||||||||||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||||||||||||||||
B- |
Connectivity type |
Connectivity type 9.9.4.2A |
O |
TV |
1 |
||||||||||||||||||||
C- |
WLAN offload indication |
WLAN offload acceptability 9.9.4.18 |
O |
TV |
1 |
||||||||||||||||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||||||||||||||||
66 |
Header compression configuration |
Header compression configuration 9.9.4.22 |
O |
TLV |
5-257 |
||||||||||||||||||||
9- |
Control plane only indication |
Control plane only indication 9.9.4.23 |
O |
TV |
1 |
||||||||||||||||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
||||||||||||||||||||
6E |
Serving PLMN rate control |
Serving PLMN rate control 9.9.4.28 |
O |
TLV |
4 |
||||||||||||||||||||
5F |
Extended APN-AMBR |
Extended APN aggregate maximum bit rate 9.9.4.29 |
O |
TLV |
8 |
8.3.6.2 Transaction identifier
If the UE supports A/Gb mode or Iu mode or both, a network supporting mobility from S1 mode to A/Gb mode or Iu mode or both shall include this IE.
8.3.6.3 Negotiated QoS
If the UE supports A/Gb mode or Iu mode or both, a network supporting mobility from S1 mode to A/Gb mode or Iu mode or both shall include the corresponding R99 QoS parameter values of a PDP context.
8.3.6.4 Negotiated LLC SAPI
If the UE supports A/Gb mode, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.6.5 Radio priority
If the UE supports A/Gb mode, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.6.6 Packet flow identifier
If the UE supports A/Gb mode and BSS packet flow procedures, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.6.7 APN-AMBR
This IE is included in the message when the network wishes to transmit the APN-AMBR to the UE for possible uplink policy enforcement.
8.3.6.8 ESM cause
The network shall include this IE, if the network allocated a PDN address of a PDN type which is different from the PDN type requested by the UE.
8.3.6.9 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
This IE shall be included if the network supports Local IP address in the traffic flow aggregate description and TFT filter, the PDN Type is different from Non-IP and Ethernet, and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.6.10 Connectivity type
The network shall include the Connectivity type IE if:
– the network is configured to indicate when a PDN connection is a LIPA PDN connection; and
– the present PDN connection is a LIPA PDN connection.
8.3.6.11 WLAN offload indication
This IE shall be included in the message when the network wishes to indicate if the UE is allowed to offload the traffic of the associated PDN connection to WLAN(s), as specified in clause 9.9.4.18.
8.3.6.12 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.6.13 Header compression configuration
The network may include the Header compression configuration IE if:
– the network accepts an IP PDN type; and
– control plane CIoT EPS optimization is selected.
8.3.6.14 Control plane only indication
The network shall include the Control plane only indication IE if the associated PDN connection is only for control plane CIoT EPS optimization.
8.3.6.15 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
This IE shall be included if the network supports Local IP address in the traffic flow aggregate description and TFT filter, the PDN Type is different from Non-IP and Ethernet, and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.6.16 Serving PLMN rate control
This IE shall be included when the network wishes to indicate the maximum number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send per 6 minute interval.
8.3.6.17 Extended APN aggregate maximum bit rate
This IE shall be included in the message only if the network wishes to transmit the APN-AMBR values to the UE for possible uplink policy enforcement and at least one of the values to be transmitted exceeds the maximum value specified in the APN aggregate maximum bit rate information element in clause 9.9.4.2.
8.3.7 Bearer resource allocation reject
8.3.7.1 Message definition
This message is sent by the network to the UE to reject the allocation of a dedicated bearer resource. See table 8.3.7.1.
Message type: BEARER RESOURCE ALLOCATION REJECT
Significance: dual
Direction: network to UE
Table 8.3.7.1: BEARER RESOURCE ALLOCATION REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
Bearer resource allocation reject message identity |
Message type 9.8 |
M |
V |
1 |
|
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
|
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
37 |
Back-off timer value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
6B |
Re-attempt indicator |
Re-attempt indicator 9.9.4.13A |
O |
TLV |
3 |
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.7.2 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.7.3 Back-off timer value
The network may include this IE if the ESM cause is not #65 "maximum number of EPS bearers reached", to request a minimum time interval before procedure retry is allowed.
8.3.7.4 Re-attempt indicator
The network may include this IE only if it includes the Back-off timer value IE and the ESM cause value is not #26 "insufficient resources".
8.3.7.5 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.7.6 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.8 Bearer resource allocation request
8.3.8.1 Message definition
This message is sent by the UE to the network to request the allocation of a dedicated bearer resource. See table 8.3.8.1.
Message type: BEARER RESOURCE ALLOCATION REQUEST
Significance: dual
Direction: UE to network
Table 8.3.8.1: BEARER RESOURCE ALLOCATION REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
Bearer resource allocation request message identity |
Message type 9.8 |
M |
V |
1 |
|
Linked EPS bearer identity |
Linked EPS bearer identity 9.9.4.6 |
M |
V |
1/2 |
|
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|
Traffic flow aggregate |
Traffic flow aggregate description 9.9.4.15 |
M |
LV |
2-256 |
|
Required traffic flow QoS |
EPS quality of service 9.9.4.3 |
M |
LV |
2-14 |
|
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
C- |
Device properties |
Device properties 9.9.2.0A |
O |
TV |
1 |
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
5C |
Extended EPS QoS |
Extended quality of service 9.9.4.30 |
O |
TLV |
12 |
8.3.8.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.8.3 Device properties
The UE shall include this IE if the UE is configured for NAS signalling low priority.
8.3.8.4 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.8.5 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.8.6 Extended EPS QoS
This IE shall be included in the message only if the UE wishes to transmit the maximum and guaranteed bit rate values to the network and at least one of the values to be transmitted exceeds the maximum value specified in the EPS quality of service information element in clause 9.9.4.3.
8.3.9 Bearer resource modification reject
8.3.9.1 Message definition
This message is sent by the network to the UE to reject the modification of a dedicated bearer resource. See table 8.3.9.1.
Message type: BEARER RESOURCE MODIFICATION REJECT
Significance: dual
Direction: network to UE
Table 8.3.9.1: BEARER RESOURCE MODIFICATION REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
Bearer resource modification reject message identity |
Message type 9.8 |
M |
V |
1 |
|
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
|
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
37 |
Back-off timer value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
6B |
Re-attempt indicator |
Re-attempt indicator 9.9.4.13A |
O |
TLV |
3 |
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.9.2 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.9.3 Back-off timer value
The network may include this IE to request a minimum time interval before procedure retry is allowed.
8.3.9.4 Re-attempt indicator
The network may include this IE only if it includes the Back-off timer value IE and the ESM cause value is not #26 "insufficient resources".
8.3.9.5 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.9.6 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.10 Bearer resource modification request
8.3.10.1 Message definition
This message is sent by the UE to the network to request the modification of a dedicated bearer resource, or to request re-negotiation of header compression configuration associated to an EPS bearer context if the network has previously indicated support of Control plane CIoT EPS optimization and Header compression for control plane CIoT EPS optimization. See table 8.3.10.1.
Message type: BEARER RESOURCE MODIFICATION REQUEST
Significance: dual
Direction: UE to network
Table 8.3.10.1: BEARER RESOURCE MODIFICATION REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
Bearer resource modification request message identity |
Message type 9.8 |
M |
V |
1 |
|
EPS bearer identity for packet filter |
Linked EPS bearer identity 9.9.4.6 |
M |
V |
1/2 |
|
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|
Traffic flow aggregate |
Traffic flow aggregate description 9.9.4.15 |
M |
LV |
2-256 |
|
5B |
Required traffic flow QoS |
EPS quality of service 9.9.4.3 |
O |
TLV |
3-15 |
58 |
ESM cause |
ESM cause 9.9.4.4 |
O |
TV |
2 |
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
C- |
Device properties |
Device properties 9.9.2.0A |
O |
TV |
1 |
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
66 |
Header compression configuration |
Header compression configuration 9.9.4.22 |
O |
TLV |
5-257 |
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
5C |
Extended EPS QoS |
Extended quality of service 9.9.4.30 |
O |
TLV |
12 |
8.3.10.2 Required traffic flow QoS
This IE is included in the message when the UE requests a change of QoS for the indicated traffic flows and does not request to release all bearer resources for the EPS bearer context.
8.3.10.3 ESM cause
This IE is included in the message when the UE requests the release of a dedicated bearer resource.
8.3.10.4 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.10.5 Device properties
The UE shall include this IE if the UE is configured for NAS signalling low priority.
8.3.10.6 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.10.7 Header compression configuration
This IE is included in the message if:
a) the UE wishes to re-negotiate header compression configuration associated to an EPS bearer context and both the UE and the network supports Control plane CIoT EPS optimization and header compression; or
b) to negotiate header compression configuration associated to an EPS bearer context after an inter-system change from N1 mode to S1 mode when both the UE and the network support control plane CIoT EPS optimization and header compression, and the UE is operating in single-registration mode and has received the interworking without N26 interface indicator set to "interworking without N26 interface not supported" from the network.
8.3.10.8 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.10.9 Extended EPS QoS
This IE shall be included in the message only if the UE wishes to transmit the maximum and guaranteed bit rate values to the network and at least one of the values to be transmitted exceeds the maximum value specified in the EPS quality of service information element in clause 9.9.4.3.
8.3.11 Deactivate EPS bearer context accept
8.3.11.1 Message definition
This message is sent by the UE to acknowledge deactivation of the EPS bearer context requested in the corresponding Deactivate EPS bearer context request message. See table 8.3.11.1.
Message type: DEACTIVATE EPS BEARER CONTEXT ACCEPT
Significance: dual
Direction: UE to network
Table 8.3.11.1: DEACTIVATE EPS BEARER CONTEXT ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
Deactivate EPS bearer context accept message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.11.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.11.3 Void
8.3.11.4 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.12 Deactivate EPS bearer context request
8.3.12.1 Message definition
This message is sent by the network to request deactivation of an active EPS bearer context. See table 8.3.12.1.
Message type: DEACTIVATE EPS BEARER CONTEXT REQUEST
Significance: dual
Direction: network to UE
Table 8.3.12.1: DEACTIVATE EPS BEARER CONTEXT REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
Deactivate EPS bearer context request message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
|||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
37 |
T3396 value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
||||||
C- |
WLAN offload indication |
WLAN offload acceptability 9.9.4.18 |
O |
TV |
1 |
||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.12.2 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.12.3 T3396 value
The network may include this IE if the ESM cause is #26 "insufficient resources".
8.3.12.4 WLAN offload indication
This IE shall be included in the message when the network wishes to indicate if the UE is allowed to offload the traffic of the associated PDN connection to WLAN(s), as specified in clause 9.9.4.18. If the MME wishes to deactivate all EPS bearer contexts of a PDN connection, MME shall not include this IE.
8.3.12.5 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.12.6 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.12A ESM dummy message
This message is sent by the UE or the network included in an ESM message container information element during an attach procedure, if the UE does not request for PDN connection. See table 8.3.12A.1.
Message type: ESM DUMMY MESSAGE
Significance: dual
Direction: both
Table 8.3.12A.1: ESM DUMMY MESSAGE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
ESM dummy message |
Message type 9.8 |
M |
V |
1 |
8.3.13 ESM information request
This message is sent by the network to the UE to request the UE to provide ESM information, i.e. protocol configuration options or APN or both. See table 8.3.13.1.
Message type: ESM INFORMATION REQUEST
Significance: dual
Direction: network to UE
Table 8.3.13.1: ESM INFORMATION REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
ESM information request message identity |
Message type 9.8 |
M |
V |
1 |
8.3.14 ESM information response
8.3.14.1 Message definition
This message is sent by the UE to the network in response to an ESM INFORMATION REQUEST message and provides the requested ESM information. See table 8.3.14.1.
Message type: ESM INFORMATION RESPONSE
Significance: dual
Direction: UE to network
Table 8.3.14.1: ESM INFORMATION RESPONSE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
ESM information response message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
28 |
Access point name |
Access point name 9.9.4.1 |
O |
TLV |
3-102 |
||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.14.2 Access point name
This IE is included in the message when the UE wishes to request network connectivity as defined by a certain access point name during the attach procedure.
8.3.14.3 Protocol configuration options
This IE shall be included in the message when, during the attach procedure, the UE wishes to transmit security protected (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and:
a) the UE is in WB-S1 mode;
b) the requested PDN Type is different from non-IP and Ethernet; and
c) the requested APN is not for UAS services.
This IE shall be included if:
a) the UE supports local IP address in traffic flow aggregate description and TFT filter;
b) the UE is in WB-S1 mode;
c) the requested PDN Type is different from non-IP and Ethernet; and
d) the requested APN is not for UAS services.
This IE shall not be included if the Extended protocol configuration options IE is included in the message.
8.3.14.4 Extended protocol configuration options
This IE shall be included in the message when, during the attach procedure, the UE wishes to transmit security protected (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and:
a) the UE is in NB-S1 mode;
b) the requested PDN Type is non-IP or Ethernet; or
c) the requested APN is for UAS services.
This IE shall be included if:
a) the UE supports local IP address in traffic flow aggregate description and TFT filter, the UE is in NB-S1 mode and the requested PDN Type is different from non-IP and Ethernet; or
b) the UE supports local IP address in traffic flow aggregate description and TFT filter, the requested PDN Type is different from non-IP and Ethernet, and the requested APN is for UAS services.
This IE shall not be included if the Protocol configuration options IE is included in the message.
8.3.15 ESM status
This message is sent by the network or the UE to pass information on the status of the indicated EPS bearer context and report certain error conditions (e.g. as listed in clause 7). See table 8.3.15.1.
Message type: ESM STATUS
Significance: dual
Direction: both
Table 8.3.15.1: ESM STATUS message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
ESM status message identity |
Message type 9.8 |
M |
V |
1 |
|
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
8.3.16 Modify EPS bearer context accept
8.3.16.1 Message definition
This message is sent by the UE to the network to acknowledge the modification of an active EPS bearer context. See table 8.3.16.1.
Message type: MODIFY EPS BEARER CONTEXT ACCEPT
Significance: dual
Direction: UE to network
Table 8.3.16.1: MODIFY EPS BEARER CONTEXT ACCEPT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
Modify EPS bearer context accept message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.16.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.16.3 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.16.4 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.17 Modify EPS bearer context reject
8.3.17.1 Message definition
This message is sent by the UE or the network to reject a modification of an active EPS bearer context. See table 8.3.17.1.
Message type: MODIFY EPS BEARER CONTEXT REJECT
Significance: dual
Direction: UE to network
Table 8.3.17.1: MODIFY EPS BEARER CONTEXT REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
Modify EPS bearer context reject message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
|||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.17.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.17.3 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.17.4 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.18 Modify EPS bearer context request
8.3.18.1 Message definition
This message is sent by the network to the UE to request modification of an active EPS bearer context, or to request re-negotiation of header compression configuration associated to an EPS bearer context if the UE has previously indicated support of Control plane CIoT EPS optimization and Header compression for control plane CIoT EPS optimization. See table 8.3.18.1.
Message type: MODIFY EPS BEARER CONTEXT REQUEST
Significance: dual
Direction: network to UE
Table 8.3.18.1: MODIFY EPS BEARER CONTEXT REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||||||||
Modify EPS bearer context request message identity |
Message type 9.8 |
M |
V |
1 |
|||||||||||||
5B |
New EPS QoS |
EPS quality of service 9.9.4.3 |
O |
TLV |
3-15 |
||||||||||||
36 |
TFT |
Traffic flow template 9.9.4.16 |
O |
TLV |
3-257 |
||||||||||||
30 |
New QoS |
Quality of service 9.9.4.12 |
O |
TLV |
14-22 |
||||||||||||
32 |
Negotiated LLC SAPI |
LLC service access point identifier 9.9.4.7 |
O |
TV |
2 |
||||||||||||
8- |
Radio priority |
Radio priority 9.9.4.13 |
O |
TV |
1 |
||||||||||||
34 |
Packet flow Identifier |
Packet flow Identifier 9.9.4.8 |
O |
TLV |
3 |
||||||||||||
5E |
APN-AMBR |
APN aggregate maximum bit rate 9.9.4.2 |
O |
TLV |
4-8 |
||||||||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||||||||
C- |
WLAN offload indication |
WLAN offload acceptability 9.9.4.18 |
O |
TV |
1 |
||||||||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||||||||
66 |
Header compression configuration |
Header compression configuration 9.9.4.22 |
O |
TLV |
5-257 |
||||||||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
||||||||||||
5F |
Extended APN-AMBR |
Extended APN aggregate maximum bit rate 9.9.4.29 |
O |
TLV |
8 |
||||||||||||
5C |
Extended EPS QoS |
Extended quality of service 9.9.4.30 |
O |
TLV |
12 |
8.3.18.2 New EPS QoS
When the EPS QoS of the EPS bearer context is modified, the network shall include the modified EPS QoS assigned to the EPS bearer context.
8.3.18.3 TFT
This IE provides the UE with packet filters.
8.3.18.4 New QoS
If the UE supports A/Gb mode or Iu mode or both and when the corresponding R99 QoS of the EPS bearer context is modified, a network supporting mobility from S1 mode to A/Gb mode or Iu mode or both shall include the corresponding R99 QoS parameter values of a PDP context.
8.3.18.5 Negotiated LLC SAPI
If the UE supports A/Gb mode and when the negotiated LLC SAPI is modified, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.18.6 Radio priority
If the UE supports A/Gb mode and when the radio priority is modified, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.18.7 Packet flow identifier
If the UE supports A/Gb mode and BSS packet flow procedures, a network supporting mobility from S1 mode to A/Gb mode shall include this IE.
8.3.18.8 APN-AMBR
This IE is included when the APN-AMBR has been changed by the network.
8.3.18.9 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.18.10 WLAN offload indication
This IE shall be included in the message when the network wishes to indicate if the UE is allowed to offload the traffic of the associated PDN connection to WLAN(s), as specified in clause 9.9.4.18.
8.3.18.11 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.18.12 Header compression configuration
This IE is included in the message if the network wishes to re-negotiate header compression configuration associated to an EPS bearer context and both the UE and the network support Control plane CIoT EPS optimization and header compression.
8.3.18.13 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.18.14 Extended APN-AMBR
This IE shall be included in the message only if at least one of the APN-AMBR values has been changed by the network and at least one of the values to be transmitted exceeds the maximum value specified in the APN aggregate maximum bit rate information element in clause 9.9.4.2.
8.3.18.15 Extended EPS QoS
This IE shall be included in the message only if the network wishes to transmit the maximum and guaranteed bit rate values to the UE and at least one of the values to be transmitted exceeds the maximum value specified in the EPS quality of service information element in clause 9.9.4.3.
8.3.18A Notification
This message is sent by the network to inform the UE about events which are relevant for the upper layer using an EPS bearer context or having requested a procedure transaction. See table 8.3.18A.1.
Message type: NOTIFICATION
Significance: local
Direction: network to UE
Table 8.3.18A.1: NOTIFICATION message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
Notification message identity |
Message type 9.8 |
M |
V |
1 |
|
Notification indicator |
Notification indicator 9.9.4.7A |
M |
LV |
2 |
8.3.19 PDN connectivity reject
8.3.19.1 Message definition
This message is sent by the network to the UE to reject establishment of a PDN connection. See table 8.3.19.1.
Message type: PDN CONNECTIVITY REJECT
Significance: dual
Direction: network to UE
Table 8.3.19.1: PDN CONNECTIVITY REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
|
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
||
PDN connectivity reject message identity |
Message type 9.8 |
M |
V |
1 |
||
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
|
37 |
Back-off timer value |
GPRS timer 3 9.9.3.16B |
O |
TLV |
3 |
|
6B |
Re-attempt indicator |
Re-attempt indicator 9.9.4.13A |
O |
TLV |
3 |
|
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
|
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.19.2 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.19.3 Back-off timer value
The network may include this IE if the ESM cause is not #28 "unknown PDN type", #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #54 "PDN connection does not exist", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed", #61 "PDN type Ethernet only allowed", or #65 "maximum number of EPS bearers reached", to request a minimum time interval before procedure retry is allowed.
8.3.19.4 Re-attempt indicator
The network may include this IE only if the ESM cause value is #28 "unknown PDN type", #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed", #61 "PDN type Ethernet only allowed", or #66 "requested APN not supported in current RAT and PLMN combination", or if the network includes the Back-off timer value IE and the ESM cause value is not #26 "insufficient resources".
8.3.19.5 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.20 PDN connectivity request
8.3.20.1 Message definition
This message is sent by the UE to the network to initiate establishment of a PDN connection. See table 8.3.20.1.
Message type: PDN CONNECTIVITY REQUEST
Significance: dual
Direction: UE to network
Table 8.3.20.1: PDN CONNECTIVITY REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
||||||
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|||||||
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|||||||
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|||||||
PDN connectivity request message identity |
Message type 9.8 |
M |
V |
1 |
|||||||
Request type |
Request type 9.9.4.14 |
M |
V |
1/2 |
|||||||
PDN type |
PDN type 9.9.4.10 |
M |
V |
1/2 |
|||||||
D- |
ESM information transfer flag |
ESM information transfer flag 9.9.4.5 |
O |
TV |
1 |
||||||
28 |
Access point name |
Access point name 9.9.4.1 |
O |
TLV |
3-102 |
||||||
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
||||||
C- |
Device properties |
Device properties 9.9.2.0A |
O |
TV |
1 |
||||||
33 |
NBIFOM container |
NBIFOM container 9.9.4.19 |
O |
TLV |
3-257 |
||||||
66 |
Header compression configuration |
Header compression configuration 9.9.4.22 |
O |
TLV |
5-257 |
||||||
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.20.2 ESM information transfer flag
The UE shall include this IE in the PDN CONNECTIVITY REQUEST message sent during the attach procedure if the UE has protocol configuration options that need to be transferred security protected or wishes to provide an access point name for the PDN connection to be established during the attach procedure.
8.3.20.3 Access point name
This IE is included in the message when the UE wishes to request network connectivity as defined by a certain access point name. This IE shall not be included when the PDN CONNECTIVITY REQUEST message is included in an ATTACH REQUEST message or if the request type indicates "emergency" or "handover of emergency bearer services" or "RLOS".
8.3.20.4 Protocol configuration options
This IE shall be included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and:
a) the UE is in WB-S1 mode;
b) the requested PDN Type is different from non-IP and Ethernet; and
c) the requested APN is not for UAS services.
This IE shall be included if:
a) the UE supports local IP address in traffic flow aggregate description and TFT filter;
b) the UE is in WB-S1 mode;
c) the requested PDN Type is different from non-IP and Ethernet; and
d) the requested APN is not for UAS services.
This IE shall not be included if the Extended protocol configuration options IE is included in the message.
8.3.20.5 Device properties
The UE shall include this IE if the UE is configured for NAS signalling low priority.
8.3.20.6 NBIFOM container
This information element is used to transfer information associated with network-based IP flow mobility, see 3GPP TS 24.161 [36].
8.3.20.7 Header compression configuration
The UE shall include the Header compression configuration IE if:
– the PDN type value of the PDN type IE is set to IPv4 or IPv6 or IPv4v6;
– the UE indicates "Control Plane CIoT EPS optimization supported" in the UE network capability IE of the ATTACH REQUEST message; and
– the UE supports header compression.
8.3.20.8 Extended protocol configuration options
This IE shall be included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and:
a) the UE is in NB-S1 mode;
b) the requested PDN Type is non-IP or Ethernet; or
c) the requested APN is for UAS services.
This IE shall be included if:
a) the UE supports local IP address in traffic flow aggregate description and TFT filter, the UE is in NB-S1 mode and the requested PDN Type is different from non-IP and Ethernet; or
b) the UE supports local IP address in traffic flow aggregate description and TFT filter, the requested PDN Type is different from non-IP and Ethernet, and the requested APN is for UAS services.
This IE shall not be included if the Protocol configuration options IE is included in the message.
8.3.21 PDN disconnect reject
8.3.21.1 Message definition
This message is sent by the network to the UE to reject release of a PDN connection. See table 8.3.21.1.
Message type: PDN DISCONNECT REJECT
Significance: dual
Direction: network to UE
Table 8.3.21.1: PDN DISCONNECT REJECT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
PDN disconnect reject message identity |
Message type 9.8 |
M |
V |
1 |
|
ESM cause |
ESM cause 9.9.4.4 |
M |
V |
1 |
|
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.21.2 Protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.21.3 Extended protocol configuration options
This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.22 PDN disconnect request
8.3.22.1 Message definition
This message is sent by the UE to the network to initiate release of a PDN connection. See table 8.3.22.1.
Message type: PDN DISCONNECT REQUEST
Significance: dual
Direction: UE to network
Table 8.3.22.1: PDN DISCONNECT REQUEST message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
PDN disconnect request message identity |
Message type 9.8 |
M |
V |
1 |
|
Linked EPS bearer identity |
Linked EPS bearer identity 9.9.4.6 |
M |
V |
1/2 |
|
Spare half octet |
Spare half octet 9.9.2.9 |
M |
V |
1/2 |
|
27 |
Protocol configuration options |
Protocol configuration options 9.9.4.11 |
O |
TLV |
3-253 |
7B |
Extended protocol configuration options |
Extended protocol configuration options 9.9.4.26 |
O |
TLV-E |
4-65538 |
8.3.22.2 Protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.22.3 Extended protocol configuration options
This IE is included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).
8.3.23 Remote UE report
8.3.23.1 Message definition
This message is sent by the UE to the network to report connection or disconnection of remote UE(s). See table 8.3.23.1.
Message type: REMOTE UE REPORT
Significance: dual
Direction: UE to network
Table 8.3.23.1: REMOTE UE REPORT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
Remote UE report message identity |
Message type 9.8 |
M |
V |
1 |
|
79 |
Remote UE Context Connected |
Remote UE context list IE 9.9.4.20 |
O |
TLV-E |
3-65538 |
7A |
Remote UE Context Disconnected |
Remote UE context list IE 9.9.4.20 |
O |
TLV-E |
3-65538 |
6F |
ProSe Key Management Function address |
PKMF address IE 9.9.4.21 |
O |
TLV |
3-19 |
8.3.23.2 Remote UE Context Connected
This IE is included in the message by the UE acting as ProSe UE-to-network relay to provide the network with newly connected remote UE information as specified in 3GPP TS 23.303 [31].
8.3.23.3 Remote UE Context Disconnected
This IE is included in the message by the UE acting as ProSe UE-to-Network Relay to provide the network with disconnected remote UE information as specified in 3GPP TS 23.303 [31].
8.3.23.4 ProSe Key Management Function Address
This IE is included in the message by the UE acting as ProSe UE-to-network relay to provide the network with the address of the ProSe Key Management Function associated with the remote UEs connected to or disconnected from the ProSe UE-to-network relay.
8.3.24 Remote UE report response
8.3.24.1 Message definition
This message is sent by the network to the UE to acknowledge receipt of a Remote UE report message. See table 8.3.24.1.
Message type: REMOTE UE REPORT RESPONSE
Significance: dual
Direction: network to UE
Table 8.3.24.1: REMOTE UE REPORT RESPONSE message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
Remote UE report response message identity |
Message type 9.8 |
M |
V |
1 |
8.3.25 ESM DATA TRANSPORT
8.3.25.1 Message definition
This message is sent by the UE or the network in order to carry user data in an encapsulated format. See table 8.3.25.1.
Message type: ESM DATA TRANSPORT
Significance: dual
Direction: both
Table 8.3.25.1: ESM DATA TRANSPORT message content
IEI |
Information Element |
Type/Reference |
Presence |
Format |
Length |
Protocol discriminator |
Protocol discriminator 9.2 |
M |
V |
1/2 |
|
EPS bearer identity |
EPS bearer identity 9.3.2 |
M |
V |
1/2 |
|
Procedure transaction identity |
Procedure transaction identity 9.4 |
M |
V |
1 |
|
ESM data transport message identity |
Message type 9.8 |
M |
V |
1 |
|
User data container |
User data container 9.9.4.24 |
M |
LV-E |
2-n |
|
F- |
Release assistance indication |
Release assistance indication 9.9.4.25 |
O |
TV |
1 |
8.3.25.2 Release assistance indication
The UE may include this IE to inform the network whether
– no further uplink and no further downlink data transmission is expected; or
– only a single downlink data transmission (e.g. acknowledgement or response to uplink data) and no further uplink data transmission subsequent to the uplink data transmission is expected.