22.5.9 NB-IoT / UE in NB-S1 mode supporting CIoT Optimizations / Paging with not matching identity / Control Plane Service request Rejected (IMSI invalid / Illegal ME / EPS services not allowed / UE identity cannot be derived by the network / UE implicitly detached)
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
22.5.9.1.1 Test Purpose (TP)
(1)
with { UE in ECM-IDLE }
ensure that {
when { the network initiates a paging procedure for EPS services using S-TMSI }
then { the UE responds to the paging by establishing an RRC connection and transmitting a SERVICE REQUEST message providing correct S-TMSI in the RRCConnectionRequest }
}
(2)
with { UE in E-UTRA RRC_IDLE state }
ensure that {
when { UE receives a Paging message including an ue-Identity set an unmatched S-TMSI i.e. other than the one allocated to the UE at the UE registration procedure }
then { UE does not establish an RRC connection }
}
(3)
with { UE having sent a CONTROL PLANE SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Illegal UE’ }
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, deletes any GUTI, last visited registered TAI, TAI list and KSI, considers the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed, enters the state EMM-DEREGISTERED }
}
(4)
with { UE having sent a CONTROL PLANE SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Illegal ME’ }
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, deletes any GUTI, last visited registered TAI, TAI list and KSI, considers the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed, enters the state EMM-DEREGISTERED }
}
(5)
with { UE having sent a CONTROL PLANE SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘EPS services not allowed’ }
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, deletes any GUTI, last visited registered TAI, TAI list and KSI, considers the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed and enters the state EMM-DEREGISTERED }
}
(6)
with { UE having sent a CONTROL PLANE SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause value = 9 (UE identity cannot be derived by the network) }
then { UE sets the EPS update status to EU2 NOT UPDATED and deletes any GUTI, last visited registered TAI, TAI list and KSI and automatically initiate the attach procedure }
}
(7)
with { UE having sent a CONTROL PLANE SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Implicitly detached’ }
then { UE enters the state EMM-DEREGISTERED.NORMAL-SERVICE, delete the EPS mapped EPS security context if any and performs a new attach procedure }
}
22.5.9.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.6.1.5, 5.6.2.2.1, TS 33.401 clause 7.2.6.2, TS 36.331 clauses 5.3.2.3, 5.3.3.2, 5.3.3.3 and 5.3.3.4. [TS 24.301, clause 5.6.2.2.1]
To initiate the procedure the EMM entity in the network requests the lower layer to start paging (see 3GPP TS 36.300 [20], 3GPP TS 36.413 [23]) and shall start the timer:
– T3415 for this paging procedure, if the network accepted to use eDRX for the UE.
– Otherwise, T3413 for this paging procedure.
If the network starts timer T3415, the network shall set timer T3415 to a value smaller than the value of timer T3-RESPONSE (see 3GPP TS 29.274 [16D] for further details on timer T3-RESPONSE).
The EMM entity may provide the lower layer with a list of CSG IDs, including the CSG IDs of both the expired and the not expired subscriptions. If there is a PDN connection for emergency bearer services established, the EMM entity in the network shall not provide the list of CSG IDs to the lower layer.
Upon reception of a paging indication, if control plane CIoT EPS optimization is not used by the UE, the UE shall stop the timer T3346, if running, and shall initiate:
– a service request procedure to respond to the paging (see 3GPP TS 23.401 [10] and 3GPP TS 36.413 [23]); or
– a tracking area update procedure as specified in subclauses 5.5.3.2.2 and 5.5.3.3.2.
and additionally if the UE is in the EMM-IDLE mode with suspend indication, resume the suspended NAS signalling connection to the MME as specified in subclause 5.3.1.3.
Upon reception of a paging indication, if control plane CIoT EPS optimization is used by the UE, the UE shall stop the timer T3346, if running, and shall additionally:
– initiate a service request procedure as specified in subclause 5.6.1.2.2 if the UE is in the EMM-IDLE mode without suspend indication; or
– proceed the behaviour as specified in subclause 5.3.1.3 if the UE is in the EMM-IDLE mode with suspend indication.
NOTE 2: If the UE is in the EMM-IDLE mode without suspend indication and has an uplink user data to be sent to the network using control plane CIoT EPS optimization when receiving the paging indication, the UE can piggyback the uplink user data during the service request procedure initiated to respond to the paging, as specified in subclause 5.6.1.2.2.
If the paging for EPS services was received during an ongoing UE-initiated EMM specific procedure or service request procedure, then the UE shall ignore the paging. The network shall proceed with the EMM specific procedure or the service request procedure, and stop the timer for the paging procedure (i.e. either timer T3413 or timer T3415). If the network receives an ATTACH REQUEST message when the paging procedure is ongoing, it should be considered as an abnormal case, and the behaviour of the UE for this case is specified in subclause 5.6.2.2.1.2.
[TS 33.401 clause 7.2.6.2]
The procedure the UE uses to transit from ECM-IDLE to ECM-CONNECTED when in EMM-REGISTERED state is initiated by a NAS Service Request message from the UE to the MME. As the UE is in EMM-REGISTERED state, a EPS security context exists in the UE and the MME, and this EPS security context further contains uplink and downlink NAS COUNTs. The NAS Service Request message sent in EMM-REGISTERED shall be integrity protected and contain the uplink NAS sequence number.
[TS 36.331, clause 5.3.2.3]
Upon receiving the Paging message, the UE shall:
1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:
2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:
3> forward the ue-Identity and, except for NB-IoT, the cn-Domain to the upper layers;
[TS 36.331, clause 5.3.3.3]
The UE shall set the contents of RRCConnectionRequest message as follows:
1> set the ue-Identity as follows:
2> if upper layers provide an S-TMSI:
3> set the ue-Identity to the value received from upper layers;
2> else:
3> draw a random value in the range 0 .. 240-1 and set the ue-Identity to this value;
NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.
1> if the UE supports mo-VoiceCall establishment cause and UE is establishing the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes voiceServiceCauseIndication:
2> set the establishmentCause to mo-VoiceCall;
1> else:
2> set the establishmentCause in accordance with the information received from upper layers;
1> if the UE is a NB-IoT UE:
2> if the UE supports multi-tone transmission, include multiToneSupport;
2> if the UE supports multi-carrier operation, include multiCarrierSupport;
The UE shall submit the RRCConnectionRequest message to lower layers for transmission.
The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.
[TS 36.331, clause 5.3.3.4]
NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];
The UE shall:
1> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest:
2> discard the stored UE AS context and resumeIdentity;
2> indicate to upper layers that the RRC connection resume has been fallbacked;
1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;
1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;
1> stop timer T300;
1> stop timer T302, if running;
1> stop timer T303, if running;
1> stop timer T305, if running;
1> stop timer T306, if running;
1> stop timer T308, if running;
1> perform the actions as specified in 5.3.3.7;
1> stop timer T320, if running;
1> stop timer T350, if running;
1> perform the actions as specified in 5.6.12.4;
1> release rclwi-Configuration, if configured, as specified in 5.6.16.2;
1> stop timer T360, if running;
1> enter RRC_CONNECTED;
1> stop the cell re-selection procedure;
1> consider the current cell to be the PCell;
1> set the content of RRCConnectionSetupComplete message as follows:
2> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest:
3> if upper layers provide an S-TMSI:
4> set the s-TMSI to the value received from upper layers;
2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]) from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1 (or SystemInformationBlockType1-NB in NB-IoT);
2> if upper layers provide the ‘Registered MME’, include and set the registeredMME as follows:
3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers:
4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the ‘Registered MME’ received from upper layers;
3> set the mmegi and the mmec to the value received from upper layers;
2> except for NB-IoT, if upper layers provided the ‘Registered MME’:
3> include and set the gummei-Type to the value provided by the upper layers;
2> if the UE supports CIoT EPS optimisation(s):
3> include attachWithoutPDN-Connectivity if received from upper layers;
3> include up-CIoT-EPS-Optimisation if received from upper layers;
3> except for NB-IoT, include cp-CIoT-EPS-Optimisation if received from upper layers;
2> if connecting as an RN:
3> include the rn-SubframeConfigReq;
2> set the dedicatedInfoNAS to include the information received from upper layers;
2> except for NB-IoT:
3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:
4> include rlf-InfoAvailable;
3> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:
4> include logMeasAvailableMBSFN;
3> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:
4> include logMeasAvailable;
3> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:
4> include connEstFailInfoAvailable;
3> include the mobilityState and set it to the mobility state (as specified in TS 36.304 [4]) of the UE just prior to entering RRC_CONNECTED state;
3> if the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport:
4> include the mobilityHistoryAvail;
2> if UE needs UL gaps during continuous uplink transmission:
3> include ue-CE-NeedULGaps;
2> submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the procedure ends;
[TS 24.301, clause 5.6.1.5]
If the service request cannot be accepted, the network shall return a SERVICE REJECT message to the UE including an appropriate EMM cause value.
…
The UE shall take the following actions depending on the received EMM cause value in the SERVICE REJECT message.
#3 (Illegal UE);
#6 (Illegal ME); or
…
#7 (EPS services not allowed);
The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.7a. The UE shall enter the state EMM-DEREGISTERED.
A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services.
A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, shall attempt to select GERAN or UTRAN radio access technology and proceed with appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN radio access technology until switching off or the UICC containing the USIM is removed.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008 [13] for the case when the service request procedure is rejected with the GMM cause with the same value.
#9 (UE identity cannot be derived by the network);
The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall enter the state EMM-DEREGISTERED.
If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer.
If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures.
If the service request was initiated for 1xCS fallback and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure.
If the service request was initiated for any reason other than CS fallback, 1x CS fallback or initiating a PDN connection for emergency bearer services, the UE shall perform a new attach procedure.
NOTE 4: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008 [13] for the case when the service request procedure is rejected with the GMM cause with the same value.
A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services.
A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED.
#10 (Implicitly detached);
A UE in CS/PS mode 1 or CS/PS mode 2 of operation is IMSI detached for both EPS services and non-EPS services.
The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped EPS security context or partial native EPS security context.
If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer.
If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures.
If the service request was initiated for 1xCS fallback and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure.
If the service request was initiated for any reason other than CS fallback, 1x CS fallback or initiating a PDN connection for emergency bearer services, the UE shall perform a new attach procedure.
NOTE 5: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM state as specified in 3GPP TS 24.008 [13] for the case when the service request procedure is rejected with the GMM cause with the same value.
A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED.
22.5.9.1.3 Test description
22.5.9.1.3.1 Pre-test conditions
System Simulator:
– NB-IoT Ncell 1, set to "Serving cell";
– NB-IoT Ncell 2, set to Non-Suitable cell".
UE:
– none.
Preamble:
– The UE is in state Registered, Idle mode (State 3-NB) on Ncell 1, according to TS 36.508 [18] Table 8.1.5.1-1.
22.5.9.1.3.2 Test procedure sequence
Table 22.5.9.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
– |
The following messages are to be observed on Ncell 1 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
1 |
The SS transmits a Paging message including an unmatched identity (incorrect S-TMSI). |
<– |
Paging-NB |
– |
– |
|
2 |
Check: Does the UE transmit an RRCConnectionRequest-NB message within 5 s? |
–> |
RRCConnectionRequest-NB |
2 |
F |
|
3-6b |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.2 indicate that the UE responds to the paging message? |
– |
– |
1 |
P |
|
7 |
The SS transmits a SERVICE REJECT message with the EMM cause set to ‘Illegal UE’. |
<– |
SERVICE REJECT |
– |
– |
|
8 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
9 |
Set the cell type of Ncell 1 to the "non-Suitable cell". Set the cell type of Ncell 2 to the "Serving cell". |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 2 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
10 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
3 |
F |
|
If possible (see ICS) switch off is performed. Otherwise the power is removed, or the USIM is removed. |
– |
– |
– |
– |
|
|
11 |
Set the cell type of the Ncell 2 to the "non-Suitable cell". Set the cell type of Ncell 1 to the "Serving cell". |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 1 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
12 |
The UE is brought back to operation or the USIM is inserted. |
– |
– |
– |
– |
|
13-25b1 |
Check: Does the UE perform the attach procedure by executing steps 2 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
3 |
P |
|
26 |
The SS releases the RRC connection |
– |
– |
– |
– |
|
27-30b |
The generic test procedure in TS 36.508 subclause 8.1.5A.2 is performed? |
– |
– |
´- |
– |
|
31 |
The SS transmits a SERVICE REJECT message with the EMM cause set to ‘Illegal ME’. |
<– |
SERVICE REJECT |
– |
– |
|
32 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
33 |
Set the cell type of Ncell 1 to the "non-Suitable cell". Set the cell type of Ncell 2 to the "Serving cell". |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 2 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
34 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
4 |
F |
|
If possible (see ICS) switch off is performed. Otherwise the power is removed, or the USIM is removed. |
– |
– |
– |
– |
|
|
35 |
Set the cell type of the Ncell 2 to the "non-Suitable cell". Set the cell type of Ncell 1 to the "Serving cell". |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 1 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
36 |
The UE is brought back to operation or the USIM is inserted. |
– |
– |
– |
– |
|
37-49b1 |
Check: Does the UE perform the attach procedure by executing steps 2 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
4 |
P |
|
50 |
The SS releases the RRC connection |
– |
– |
– |
– |
|
51-54b |
The generic test procedure in TS 36.508 subclause 8.1.5A.2 is performed? |
– |
– |
´- |
– |
|
55 |
The SS transmits a SERVICE REJECT message with the EMM cause set to ‘EPS services not allowed’. |
<– |
SERVICE REJECT |
– |
– |
|
56 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
57 |
Set the cell type of Ncell 1 to the "non-Suitable cell". Set the cell type of Ncell 2 to the "Serving cell". |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 2 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
58 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
5 |
F |
|
If possible (see ICS) switch off is performed. Otherwise the power is removed, or the USIM is removed. |
– |
– |
– |
– |
|
|
59 |
Set the cell type of the Ncell 2 to the "non-Suitable cell". Set the cell type of Ncell 1 to the "Serving cell". |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 1 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
60 |
The UE is brought back to operation or the USIM is inserted. |
– |
– |
– |
– |
|
61-73b1 |
Check: Does the UE perform the attach procedure by executing steps 2 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
5 |
P |
|
74 |
The SS releases the RRC connection |
– |
– |
– |
– |
|
75-78b |
The generic test procedure in TS 36.508 subclause 8.1.5A.2 is performed? |
– |
– |
´- |
– |
|
79 |
The SS transmits a SERVICE REJECT message with the EMM cause set to ‘UE identity cannot be derived by the network’. |
<– |
SERVICE REJECT |
– |
– |
|
– |
EXCEPTION: Steps 79a1-79a2 describes the behaviour that depends on UE behaviour (Note 1). |
– |
– |
– |
– |
|
79a1 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 79a2 describes a behaviour which depends on the UE capability |
– |
– |
– |
– |
|
79a2 |
IF NOT pc_Automatic_EPS_Re_Attach, the user initiates an attach by MMI or by AT command. |
– |
– |
– |
– |
|
80-92b1 |
Check: Does the UE perform the attach procedure by executing steps 2 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
6 |
P |
|
93 |
The SS releases the RRC connection |
– |
– |
– |
– |
|
94-97b |
The generic test procedure in TS 36.508 subclause 8.1.5A.2 is performed? |
– |
– |
´- |
– |
|
98 |
The SS transmits a SERVICE REJECT message with the EMM cause set to ‘Implicitly detached’. |
<– |
SERVICE REJECT |
– |
– |
|
– |
EXCEPTION: Steps 99a1-99a2 describes the behaviour that depends on UE behaviour (Note 1). |
– |
– |
– |
– |
|
99a1 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 99a2 describes a behaviour which depends on the UE capability |
– |
– |
– |
– |
|
99a2 |
IF NOT pc_Automatic_EPS_Re_Attach, the user initiates an attach by MMI or by AT command. |
– |
– |
– |
– |
|
100-112b1 |
Check: Does the UE perform the attach procedure by executing steps 2 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
6 |
P |
|
113 |
The SS releases the RRC connection |
– |
– |
– |
– |
|
Note 1: SS waits for 1.5 second to receive the Attach Request on the existing RRC Connection. In case Attach Request is not received within 1.5 second, existing RRC Connection is released. |
|||||
22.5.9.1.3.3 Specific message contents
Table 22.5.9.1.3.3-1: Paging-NB (step 1, Table 22.5.9.1.3.2-1)
|
Derivation Path: 36.508 Table 8.1.6.1-2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Paging-NB ::= SEQUENCE { |
|||
|
pagingRecordList SEQUENCE (SIZE (1..maxPageRec)) OF SEQUENCE { |
1 entry |
||
|
ue-Identity[1] CHOICE { |
|||
|
s-TMSI SEQUENCE { |
|||
|
mmec |
Set to the different value from the S-TMSI of the UE |
||
|
m-TMSI |
Set to the different value from the S-TMSI of the UE |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 22.5.9.1.3.3-2: RRCConnectionRequest-NB (step 4, Table 22.5.9.1.3.2-1)
|
Derivation Path: Table 8.1.6.1-10 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRequest-NB ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionRequest-r13 SEQUENCE { |
|||
|
ue-Identity[1] CHOICE { |
|||
|
s-TMSI |
Set to the value of the S-TMSI of the UE |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 22.5.9.1.3.3-3: SERVICE REJECT (step 7, Table 22.5.9.1.3.2-1)
|
Derivation Path: Table 4.7.2.22 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EMM Cause |
‘0000 0011’B |
Illegal UE |
||
Table 22.5.9.1.3.3-4: SERVICE REJECT (step 31, Table 22.5.9.1.3.2-1)
|
Derivation Path: Table 4.7.2.22 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EMM Cause |
‘0000 0110’B |
Illegal ME |
||
Table 22.5.9.1.3.3-5: SERVICE REJECT (step 55, Table 22.5.9.1.3.2-1)
|
Derivation Path: Table 4.7.2.22 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EMM Cause |
‘0000 0111’B |
EPS services not allowed |
||
Table 22.5.9.1.3.3-6: SERVICE REJECT (step 79, Table 22.5.9.1.3.2-1)
|
Derivation Path: Table 4.7.2.22 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EMM Cause |
‘0000 1001’B |
UE identity cannot be derived by the network |
||
Table 22.5.9.1.3.3-7: ATTACH REQUEST (step 80-92b1, Table 22.5.9.1.3.2-1)
|
Derivation Path: 36.508, Table 4.7.2-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
NAS key set identifier |
‘111’B |
no key is available |
|
|
Old GUTI or IMSI |
IMSI |
||
|
Last visited registered TAI |
Not present |
||
Table 22.5.9.1.3.3-8: SERVICE REJECT (step 98, Table 22.5.9.1.3.2-1)
|
Derivation Path: Table 4.7.2.22 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EMM Cause |
‘0000 1001’B |
UE identity cannot be derived by the network |
||
Table 22.5.9.1.3.3-9: ATTACH REQUEST (step 100-112b1, Table 22.5.9.1.3.2-1)
|
Derivation Path: 36.508, Table 4.7.2-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
NAS key set identifier |
‘111’B |
no key is available |
|
|
Old GUTI or IMSI |
IMSI |
||
|
Last visited registered TAI |
Not present |
||