10.5 UE requested PDN connectivity
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
10.5.1 UE requested PDN connectivity accepted by the network
10.5.1.1 Test Purpose (TP)
(1)
with { UE in EMM-REGISTERED state and EMM-IDLE mode }
ensure that {
when { UE has uplink signalling pending }
then { UE establishes the RRC connection with the RRC establishmentCause set to ‘mo-Data’ and sends a SERVICE REQUEST message }
}
(2)
with { UE is in EMM-REGISTERED mode }
ensure that {
when { UE is triggered to request connectivity to an additional PDN }
then { the UE transmits a PDN CONNECTIVITY REQUEST message with the request type set to "initial request" and including APN }
}
(3)
with { UE has sent a PDN CONNECTIVITY REQUEST message }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE Procedure transaction identity matching the PDN CONNECTIVITY REQUEST message and an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message linked to the EPS bearer context activated in the first message}
then { UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message both containing the EPS bearer identity and enters EMM-REGISTERED state }
}
10.5.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.3.3.1, 5.6.1.1, 5.6.1.2, 5.6.1.4, 6.2.2, 6.4.1.3, 6.4.2.3, 6.5.1.2 and Annex D, and TS 25.331 clause 5.3.3.3.
[TS 24.301 clause 5.3.1.1]
When the UE is in EMM-IDLE mode and needs to transmit an initial NAS message, the UE shall request the lower layer to establish a RRC connection. In this request to the lower layer the NAS shall provide to the lower layer the RRC establishment cause and the call type as specified in annex D of this specification.
…
[TS 24.301 clause 5.6.1.1]
The UE shall invoke the service request procedure when:
…
c) the UE, in EMM-IDLE mode, has uplink signalling pending;
…
[TS 24.301 clause 5.6.1.2]
If the UE has pending uplink data or uplink signalling in EMM-IDLE mode to be transmitted or it responds to paging with CN domain indicator set to "PS", the UE initiates the service request procedure by sending a SERVICE REQUEST message to the MME, starts the timer T3417, and enters the state EMM-SERVICE-REQUEST-INITIATED.
…
[TS 24.301 clause 5.6.1.4]
For cases a, b, c and h in subclause 5.6.1.1, the UE shall treat the indication from the lower layers that the user plane radio bearer is set up as successful completion of the procedure. The UE shall stop the timer T3417 and enter the state EMM-REGISTERED.
Upon successful completion of the procedure, the UE shall stop the timer T3417 and enter the state EMM-REGISTERED.
[TS 24.301, Annex D]
…
Table D.1.1: Mapping of NAS procedure to establishment cause and call type
|
NAS procedure |
RRC establishment cause (according 3GPP TS 36.331 [22]) |
Call type |
|
… |
||
|
Service Request |
If a SERVICE REQUEST is to request user plane radio resources, the RRC establishment cause shall be set to MO data. (See Note1) |
"originating calls" |
|
If a SERVICE REQUEST is to request resources for UL signalling, the RRC establishment cause shall be set to MO data. (See Note 1) |
"originating calls" |
|
|
If a SERVICE REQUEST is a response to paging where the CN domain indicator is set to "PS", the RRC establishment cause shall be set to MT access. (See Note 1) |
"terminating calls" |
|
|
If an EXTENDED SERVICE REQUEST has service type set to "mobile originating CS fallback or 1xCS fallback", the RRC establishment cause shall be set to MO data. (See Note1). |
"originating calls" |
|
|
If an EXTENDED SERVICE REQUEST has service type set to "mobile terminating CS fallback or 1xCS fallback", the RRC establishment cause shall be set to MT access. (See Note1). |
"terminating calls" |
|
|
If an EXTENDED SERVICE REQUEST has service type set to "mobile originating CS fallback emergency call or 1xCS fallback emergency call", the RRC establishment cause shall be set to Emergency call. |
"emergency calls" |
|
|
… |
||
|
Note 1: For these NAS procedures initiated by UEs of access class 12, 13 or 14 in their home country, the RRC establishment cause will be set to "High priority access AC 11 – 15". For this purpose the home country is defined as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A]. For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present), the RRC establishment cause will be set to "High priority access AC 11 – 15". |
||
[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> set the establishmentCause in accordance with the information received from upper layers;
The UE shall submit the RRCConnectionRequest message to lower layers for transmission.
…
[TS 24.301, clause 6.2.2]
The UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message, based on its IP stack configuration as follows:
a) A UE, which is IPv6 and IPv4 capable and
– has not been allocated an IP address for this APN, shall set the PDN type IE to IPv4v6.
– has been allocated an IPv4 address for this APN and received the ESM cause #52 "single address bearers only allowed", and is requesting an IPv6 address, shall set the PDN type IE to IPv6.
– has been allocated an IPv6 address for this APN and received the ESM cause #52 "single address bearers only allowed", and is requesting an IPv4 address, shall set the PDN type IE to IPv4.
b) A UE, which is only IPv4 capable, shall set the PDN type IE to IPv4.
c) A UE, which is only IPv6 capable, shall set the PDN type IE to IPv6.
d) When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall set the PDN type IE to IPv4v6.
…
[TS 24.301, clause 6.4.1.3]
Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall send an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. When the default bearer is activated as part of the attach procedure, the UE shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message together with ATTACH COMPLETE message. When the default bearer is activated as the response to the stand-alone PDN CONNECTIVITY REQUEST message, the UE shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message alone.
The UE checks the PTI in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to identify the UE requested PDN connectivity procedure to which the default bearer context activation is related (see subclause 6.5.1).
…
[TS 24.301, clause 6.4.2.3]
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall first check the received TFT before taking it into use. Then the UE shall send an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. The ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message shall include the EPS bearer identity.
The linked EPS bearer identity included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message indicates to the UE to which default bearer, IP address and PDN the dedicated bearer is linked.
If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE uses the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the dedicated bearer context activation is related.
If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message and the PTI is associated to a UE requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the UE shall release the traffic flow aggregate description associated to the PTI value provided.
The UE shall use the received TFT to apply mapping of uplink traffic flows to the radio bearer if the TFT contains packet filters for the uplink direction.
…
[TS 24.301, clause 6.5.1.2]
…
In order to request connectivity to a PDN using the default APN, the UE includes the access point name IE in the PDN CONNECTIVITY REQUEST message or, when applicable, in the ESM INFORMATION RESPONSE message, according to the following conditions:
– if use of a PDN using the default APN requires PAP/CHAP, then the UE should include the access point name IE; and
– in all other conditions, the UE need not include the access point name IE.
In order to request connectivity to an additional PDN, the UE shall send a PDN CONNECTIVITY REQUEST message including a requested APN to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.1.2.1). In the PDN type information element the UE shall indicate the IP version capability of the IP stack associated with the UE as specified in subclause 6.4.1
The UE shall set the request type to "initial request" when the UE is establishing connectivity to a PDN for the first time, i.e. when it is an initial attach to that PDN. The UE shall set the request type to "handover" when the connectivity to a PDN is established upon handover from a non-3GPP access network and the UE was connected to that PDN before the handover to the 3GPP access network.
…
10.5.1.3 Test description
10.5.1.3.1 Pre-test conditions
System Simulator:
– Cell A
UE:
None.
Preamble:
– The UE is in state Registered, Idle mode (state 2) according to [18].10.5.1.3.2 Test procedure sequence
Table 10.5.1.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request connectivity to an additional PDN (see Note) |
– |
– |
– |
– |
|
1A |
Check: Does UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mo-Data’ followed by a SERVICE REQUEST message? |
–> |
SERVICE REQUEST |
1 |
P |
|
1B |
The SS establishes SRB2 and DRB associated with default EPS bearer context (a first PDN obtained during the attach procedure). |
– |
– |
– |
– |
|
2 |
Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN? |
–> |
PDN CONNECTIVITY REQUEST |
2 |
P |
|
3 |
The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context and ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with IE Linked EPS bearer identity set to the new EPS bearer context. Note: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST and ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST are included in dedicatedInfoNASList of RRCConnectionReconfiguration message. |
<– |
ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 4 below, the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane. |
– |
– |
– |
– |
|
– |
EXCEPTION: In parallel with step 4 below, the test steps in the parallel behaviour in table 10.5.1.3.2-2 is taking place |
||||
|
4 |
Check: Does the UE transmit an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS Bearer? |
–> |
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT |
3 |
P |
|
5-6 |
Void |
– |
– |
– |
– |
|
7 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
Note: The request of connectivity to an additional PDN may be performed by MMI or AT command. |
|||||
Table 10.5.1.3.2-2: Parallel behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the dedicated EPS Bearer? |
–> |
ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT |
3 |
P |
10.5.1.3.3 Specific message contents
Table 10.5.1.3.3-0: Message RRCConnectionRequest (step 1a, Table 10.5.1.3.2-1)
|
Derivation path: 36.508 table 4.6.1-16 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
RRCConnectionRequest ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionRequest-r8 SEQUENCE { |
|||
|
establishmentCause |
mo-Data |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 10.5.1.3.3-1: Message PDN CONNECTIVITY REQUEST (step 2, Table 10.5.1.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-20 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
|
|
ESM information transfer flag |
Not present |
This IE is only used during an attach procedure. |
|
|
Access point name |
APN-1(New PDN name) |
The requested PDN is different from default PDN |
|
Table 10.5.1.3.3-1a: Message RRCConnectionReconfiguration (step 3, Table 10.5.1.3.2-1)
|
Derivation path: 36.508 table 4.6.1-8 using condition DRB(2,0) |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE{ |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
dedicatedInfoNASList SEQUENCE { |
2 entries |
||
|
dedicatedInfoNAS[1] |
See table 10.5.1.3.3-2 |
||
|
dedicatedInfoNAS[2] |
See table 10.5.1.3.3-3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 10.5.1.3.3-2: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 3, Table 10.5.1.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-6 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
Procedure transaction identity |
PTI-1 |
SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure. |
|
|
Access point name |
APN-1 |
SS re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure |
|
Table 10.5.1.3.3-3: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 3, Table 10.5.1.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
7 |
||
|
Procedure transaction identity |
0 |
No procedure transaction identity assigned |
|
|
Linked EPS bearer identity |
6 |
||
|
EPS QoS |
According to reference dedicated EPS bearer context #2 – see [18] |
SS defines an additional dedicated EPS QoS |
|
|
TFT |
According to reference dedicated EPS bearer context #2 – see [18] |
||
Table 10.5.1.3.3-4: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 4, Table 10.5.1.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
Procedure transaction identity |
0 |
No procedure transaction identity assigned |
|
Table 10.5.1.3.3-5: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT (step 6, Table 10.5.1.3.2-2)
|
Derivation Path: TS 36.508 Table 4.7.3-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
7 |
||
|
Procedure transaction identity |
0 |
No procedure transaction identity assigned |
|
10.5.1a UE requested PDN connectivity accepted / Dual priority / T3396 override
10.5.1a.1 Test Purpose (TP)
(1)
with { the UE configured for low priority NAS signalling and low priority NAS signalling override and the UE has sent a PDN CONNECTIVITY REQUEST message indicating low NAS signalling priority }
ensure that {
when { the UE receives PDN CONNECTIVITY REJECT message with timer T3396 and ESM cause value #26 "insufficient resources" }
then { if higher layers in the UE request the activation of such a connection/context, the UE sends a PDN CONNECTIVITY REQUEST message with the low priority indicator set to "MS is not configured for NAS signalling low priority" }
}
10.5.1a.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 4.2A and 6.5.5.
[TS 24.301, clause 4.2A]
A UE configured for NAS signalling low priority indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured for NAS signalling low priority", except for the following cases in which the UE shall set the low priority indicator to "MS is not configured for NAS signalling low priority":
– the UE is performing an attach for emergency bearer services;
– the UE has a PDN connection for emergency bearer services established and is performing EPS mobility management procedures, or is establishing a PDN connection for emergency bearer services;
– the UE is accessing the network with access class 11 – 15; or
– the UE is responding to paging.
The network may use the NAS signalling low priority indication for NAS level mobility management congestion control and APN based congestion control.
If the NAS signalling low priority indication is provided in a PDN CONNECTIVITY REQUEST message, the MME stores the NAS signalling low priority indication within the default EPS bearer context activated due to the PDN connectivity request procedure.
[TS 24.301, clause 6.5.5]
If timer T3396 is running for a specific APN, because a PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396 and ESM cause value #26 "insufficient resources", upon request of the upper layers the UE can:
– send a PDN CONNECTIVITY REQUEST message to the same APN, with low priority indicator set to "MS is not configured for NAS signalling low priority"; or,
– send a BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message, with low priority indicator set to "MS is not configured for NAS signalling low priority", for a PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority" exists.
If timer T3396 is running, because a PDN CONNECTIVITY REQUEST without APN sent together an ATTACH REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396 and ESM cause value #26 "insufficient resources", upon request of the upper layers the UE can initiate a new attach procedure with low priority indicator set to "MS is not configured for NAS signalling low priority".
For requests with low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall follow the procedures specified in subclause 6.5.1.4.
10.5.1a.3 Test description
10.5.1a.3.1 Pre-test conditions
System Simulator:
– Cell A.
UE:
– the UE is configured for NAS signalling low priority
– the UE is configured for NAS signalling low priority override
The UE is equipped with a USIM containing values shown in Table 10.5.1a.3.1-1.
Table 10.5.1a.3.1-1: USIM Configuration
|
USIM field |
Value |
|
EFUST |
Service 96 is supported. |
|
EFNASCONFIG |
“NAS_SignallingPriority is set to NAS signalling low priority” as defined in TS 24.368, clause 5.3. |
|
EFNASCONFIG |
“Override_NAS_SignallingLowPriority is set to UE can override the NAS signalling low priority indicator” as defined in TS 24.368, clause 5.9. |
|
EFNASCONFIG |
“ExtendedAccessBarring is set to extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8 |
|
EFNASCONFIG |
“Override_ExtendedAccessBarring is set to UE can override extended access barring” as defined in TS 24.368, clause 5.10. |
|
Note: As per TS 23.401 [22] clause 4.3.17.4, UE’s configuration of low access priority and Extended Access Barring shall match each other and so do their corresponding override configuration. |
|
Preamble:
– The UE is in state Registered, Idle mode (state 2) according to [18] (1 default EPS bearer context is active).
10.5.1a.3.2 Test procedure sequence
Table 10.5.1a.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
||
|
U – S |
Message |
|||||
|
1 |
Cause the UE to request connectivity to an additional PDN (see Note) |
– |
– |
– |
– |
|
|
1A |
The UE transmits an RRCConnectionRequest message with establishment cause set to “delayTolerantAccess_v1020” |
–> |
RRCConnectionRequest |
– |
– |
|
|
2 |
The UE transmits an EXTENDED SERVICE REQUEST message. |
–> |
EXTENDED SERVICE REQUEST |
– |
– |
|
|
3 |
The SS establishes a DRB associated with the default EPS bearer context activated during the preamble. |
– |
– |
– |
– |
|
|
4 |
The UE transmits a PDN CONNECTIVITY REQUEST to request an additional PDN |
–> |
PDN CONNECTIVITY REQUEST |
– |
– |
|
|
5 |
The SS transmits a PDN CONNECTIVITY REJECT message. |
<– |
PDN CONNECTIVITY REJECT |
– |
– |
|
|
6 |
Cause the UE to request connectivity to the same PDN used in step 1 with the NAS signalling low priorityindicator set to indicate normal priority. (see Note) |
|||||
|
7 |
Check: Does the UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN before the time indicated by timer T3396 has passed? |
–> |
PDN CONNECTIVITY REQUEST |
1 |
P |
|
|
8 |
The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context. Note: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST is included in dedicatedInfoNASList of RRCConnectionReconfiguration message. |
<– |
ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
|
|
– |
EXCEPTION: In parallel to the event described in step 9 below, the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane. |
– |
– |
– |
– |
|
|
9 |
The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS bearer |
–> |
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT |
– |
– |
|
|
Note: The trigger in step 1 and 6 is the same as in the generic procedure in 36.508 clause 6.4.3.2. The request of connectivity to an additional PDN may be performed by MMI or AT command. |
||||||
10.5.1a.3.3 Specific message contents
Table 10.5.1a.3.3-0a: Message ATTACH REQUEST (Preamble)
|
Derivation path: TS 36.508 table 4.7.2.-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Device properties |
1 |
“MS is configured for NAS signalling low priority” |
|
Table 10.5.1a.3.3-0b: ATTACH ACCEPT (Preamble)
|
Derivation path: 36.508 table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS network feature support |
‘0010 0000’B |
– network supports use of EXTENDED SERVICE REQUEST to request for packet services |
|
Table 10.5.1a.3.3-0c: Message RRCConnectionRequest (step 1A, Table 10.5.1a.3.2-1)
|
Derivation path: 36.508 table 4.6.1-16 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
RRCConnectionRequest ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionRequest-r8 SEQUENCE { |
|||
|
establishmentCause |
delayTolerantAccess_v1020 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 10.5.1a.3.3-1: Message EXTENDED SERVICE REQUEST (step 2, table 10.5.1a.3.2-1)
|
Derivation path: 36.508 table 4.7.2-14A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Service type |
1000 |
‘packet services via S1’ |
|
|
Device properties |
1 |
‘MS is configured for NAS signalling low priority’ |
|
Table 10.5.1a.3.3-2: Message PDN CONNECTIVITY REQUEST (step 4, table 10.5.1a.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-20 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
|
|
ESM information transfer flag |
Not present |
This IE is only activable during an attach procedure. |
|
|
Access point name |
APN-1(New PDN name) |
The requested PDN is different from default PDN |
|
|
Device properties |
1 |
‘MS is configured for NAS signalling low priority’ |
|
Table 10.5.1a.3.3-3: Message PDN CONNECTIVITY REJECT (step 5, table 10.5.1a.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-1 |
The SS indicates the same value like received in the PDN CONNECTIVITY REQUEST |
|
|
ESM cause |
00011010 |
#26 “insufficient resources” |
|
|
T3396 value |
1010 0101 |
5 minutes |
|
Table 10.5.1a.3.3-4: Message PDN CONNECTIVITY REQUEST (step 7, table 10.5.1a.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-20 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
|
|
ESM information transfer flag |
Not present |
This IE is only activable during an attach procedure. |
|
|
Access point name |
APN-1(New PDN name) |
The requested PDN is the same as in step 4 |
|
|
Device properties |
0 |
‘MS is not configured for NAS signalling low priority’ |
|
10.5.1b UE requested PDN connectivity accepted / Dual priority / T3346 override
10.5.1b.1 Test Purpose (TP)
(1)
with { the UE configured for dual priority NAS signalling and the UE has sent an EXTENDED SERVICE REQUEST message indicating low NAS signalling priority }
ensure that {
when { the UE receives SERVICE REJECT message with timer T3346 and EMM cause value #22 "Congestion" }
then { if higher layers in the UE request the activation of such a connection/context, the UE sends a PDN CONNECTIVITY REQUEST message with the low priority indicator set to "MS is not configured for NAS signalling low priority” }
}
10.5.1b.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.6.1.6.
[TS 24.301, clause 5.6.1.6]
The following abnormal cases can be identified:
…
m) Timer T3346 is running
The UE shall not start the service request procedure unless:
– the UE receives a paging;
– the UE is a UE configured to use AC11 – 15 in selected PLMN;
– the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; or
– the UE is requested by the upper layer for a CS fallback for emergency call or a 1xCS fallback for emergency call; or
– the UE has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication and if the timer T3346 was started due to a NAS request message (ATTACH REQUEST, TRACKING AREA UPDATE REQUEST or EXTENDED SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority".
The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped.
10.5.1b.3 Test description
10.5.1b.3.1 Pre-test conditions
System Simulator:
– Cell A.
UE:
– The UE is configured for NAS signalling low priority
– The UE is configured for NAS signalling low priority override
– The UE is equipped with a USIM containing values shown in Table 10.5.1b.3.1-1.
Table 10.5.1b.3.1–1: USIM Configuration
|
USIM field |
Value |
|
EFUST |
Service 96 is supported. |
|
EFNASCONFIG |
“NAS_SignallingPriority is set to NAS signalling low priority” as defined in TS 24.368, clause 5.3. |
|
EFNASCONFIG |
“Override_NAS_SignallingLowPriority is set to UE can override the NAS signalling low priority indicator” as defined in TS 24.368, clause 5.9. |
|
EFNASCONFIG |
“ExtendedAccessBarring is set to extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8 |
|
EFNASCONFIG |
“Override_ExtendedAccessBarring is set to UE can override extended access barring” as defined in TS 24.368, clause 5.10. |
|
Note: As per TS 23.401 [22] clause 4.3.17.4, UE’s configuration of low access priority and Extended Access Barring shall match each other and so do their corresponding override configuration. |
|
Preamble:
– The UE is in state Registered, Idle mode (state 2) according to [18]
10.5.1b.3.2 Test procedure sequence
Table 10.5.1b.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
||
|
U – S |
Message |
|||||
|
1 |
Cause the UE to request connectivity to an additional PDN (see Note) |
– |
– |
– |
– |
|
|
1A |
The UE transmits an RRCConnectionRequest message with establishment cause set to “delayTolerantAccess_v1020” |
–> |
RRCConnectionRequest |
– |
– |
|
|
2 |
The UE transmits an EXTENDED SERVICE REQUEST message. |
–> |
EXTENDED SERVICE REQUEST |
– |
– |
|
|
3 |
The SS transmits a SERVICE REJECT message with cause 22 “Congestion” and “T3346 value” included |
<– |
SERVICE REJECT |
– |
– |
|
|
4 |
The SS transmits an RRCConnectionRelease message (releaseCause = other) |
<– |
RRCConnectionRelease |
|||
|
5 |
Cause the UE to request connectivity to the same PDN as used in step 1, with the NAS signalling low priority indicator set to indicate normal priority (see Note). |
|||||
|
5A |
The UE transmits an RRCConnectionRequest message with establishment cause set to “mo-Data” |
–> |
RRCConnectionRequest |
– |
– |
|
|
6 |
The UE transmits an EXTENDED SERVICE REQUEST message. |
–> |
EXTENDED SERVICE REQUEST |
|||
|
6A |
The SS establishes a DRB associated with the default EPS bearer context activated during the preamble. |
– |
– |
– |
– |
|
|
7 |
Check: Does the UE transmit a PDN CONNECTIVITY REQUEST as specified to request a PDN before the time indicated by timer T3346 has passed? |
–> |
PDN CONNECTIVITY REQUEST |
1 |
P |
|
|
8 |
The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context. Note: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST is included in dedicatedInfoNASList of RRCConnectionReconfiguration message. |
<– |
ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
|
|
– |
EXCEPTION: In parallel to the event described in step 9 below, the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane. |
– |
– |
– |
– |
|
|
9 |
The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS bearer |
–> |
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT |
– |
– |
|
|
Note: The trigger in steps 1 and 5 is the same as in the generic procedure in 36.508 clause 6.4.3.2. The request for connectivity to an additional PDN may be performed by MMI or AT command. |
||||||
10.5.1b.3.3 Specific message contents
Table 10.5.1b.3.3-0a: Message ATTACH REQUEST (Preamble)
|
Derivation path: TS 36.508 table 4.7.2.-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Device properties |
1 |
“MS is configured for NAS signalling low priority” |
|
Table 10.5.1b.3.3-0b: ATTACH ACCEPT (Preamble)
|
Derivation path: 36.508 table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS network feature support |
‘0010 0000’B |
– network supports use of EXTENDED SERVICE REQUEST to request for packet services |
|
Table 10.5.1b.3.3-0c: Message RRCConnectionRequest (step 1A, Table 10.5.1b.3.2-1)
|
Derivation path: 36.508 table 4.6.1-16 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
RRCConnectionRequest ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionRequest-r8 SEQUENCE { |
|||
|
establishmentCause |
delayTolerantAccess_v1020 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 10.5.1b.3.3-1: Message EXTENDED SERVICE REQUEST (step 2, table 10.5.1b.3.2-1)
|
Derivation path: 36.508 table 4.7.2-14A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Service type |
1000 |
‘packet services via S1’ |
|
|
Device properties |
1 |
‘MS is configured for NAS signalling low priority’ |
|
Table 10.5.1b.3.3-2: Message SERVICE REJECT (step 3, table 10.5.1b.3.2-1)
|
Derivation Path: 36.508 table 4.7.2-22 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
EMM cause |
0001 0110 |
#22 Congestion |
||
|
T3346 value |
0010 0101 |
5 minutes |
||
Table 10.5.1b.3.3-3: Message RRCConnectionRelease (step 4, table 10.5.1b.3.2-1)
|
Derivation Path: 36.508 table 4.6.1-15 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
releaseCause |
other |
|||
Table 10.5.1b.3.3-3ac: Message RRCConnectionRequest (step 5A, Table 10.5.1b.3.2-1)
|
Derivation path: 36.508 table 4.6.1-16 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
RRCConnectionRequest ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionRequest-r8 SEQUENCE { |
|||
|
establishmentCause |
mo-Data |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 10.5.1b.3.3-4: Message EXTENDED SERVICE REQUEST (step 6, table 10.5.1b.3.2-1)
|
Derivation path: 36.508 table 4.7.2-14A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Service type |
1000 |
‘packet services via S1’ |
|
|
Device properties |
0 |
‘MS is not configured for NAS signalling low priority’ |
|
Table 10.5.1b.3.3-5: Message PDN CONNECTIVITY REQUEST (step 7, table 10.5.1b.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-20 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Procedure transaction identity |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
|
|
ESM information transfer flag |
Not present |
This IE is only needed during an attach procedure. |
|
|
Access point name |
APN-1 |
The requested PDN is different from default PDN |
|
|
Device properties |
0 |
‘MS is not configured for NAS signalling low priority’ |
|
10.5.2 Void
10.5.3 UE requested PDN connectivity not accepted
10.5.3.1 Test Purpose (TP)
(1)
with { the UE has sent a PDN CONNECTIVITY REQUEST message to an additional PDN }
ensure that {
when { the UE receives an PDN CONNECTIVITY REJECT message with PTI matching the PDN CONNECTIVITY REQUEST message and including a ESM cause value }
then { the UE enters the state PROCEDURE TRANSACTION INACTIVE }
}
10.5.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.2.2, 6.4.1.3, 6.4.2.3 and 6.5.1.2.
[TS 24.301, clause 6.2.2]
The UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message, based on its IP stack configuration as follows:
a) A UE, which is IPv6 and IPv4 capable and
– has not been allocated an IP address for this APN, shall set the PDN type IE to IPv4v6.
– has been allocated an IPv4 address for this APN and received the ESM cause #52 "single address bearers only allowed", and is requesting an IPv6 address, shall set the PDN type IE to IPv6.
– has been allocated an IPv6 address for this APN and received the ESM cause #52 "single address bearers only allowed", and is requesting an IPv4 address, shall set the PDN type IE to IPv4.
b) A UE, which is only IPv4 capable, shall set the PDN type IE to IPv4.
c) A UE, which is only IPv6 capable, shall set the PDN type IE to IPv6.
d) When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall set the PDN type IE to IPv4v6.
…
[TS 24.301, clause 6.5.1.2]
…
In order to request connectivity to an additional PDN, the UE shall send a PDN CONNECTIVITY REQUEST message including a requested APN to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.1.2.1). In the PDN type information element the UE shall indicate the IP version capability of the IP stack associated with the UE as specified in subclause 6.4.1
The UE shall set the request type to "initial request" when the UE is establishing connectivity to a PDN for the first time, i.e. when it is an initial attach to that PDN. The UE shall set the request type to "handover" when the connectivity to a PDN is established upon handover from a non-3GPP access network and the UE was connected to that PDN before the handover to the 3GPP access network.
…
[TS 24.301, clause 6.5.1.4]
…
Upon receipt of the PDN CONNECTIVITY REJECT message, the UE shall stop timer T3482 and enter the state PROCEDURE TRANSACTION INACTIVE.
The PDN CONNECTIVITY REJECT message contains an ESM cause IE that typically indicates one of the following ESM cause values:
#8: operator determined barring;
#26: insufficient resources;
#27: missing or unknown APN;
#28: unknown PDN type;
#29: user authentication failed;
#30: request rejected by Serving GW or PDN GW;
#31: request rejected, unspecified;
#32: service option not supported;
#33: requested service option not subscribed;
#34: service option temporarily out of order;
#35: PTI already in use;
#38: network failure;
#50: PDN type IPv4 only allowed;
#51: PDN type IPv6 only allowed;
#53: ESM information not received;
#54: PDN connection does not exist;
#55: multiple PDN connections for a given APN not allowed;
#95 – 111: protocol errors;
#112: APN restriction value incompatible with active EPS bearer context.
10.5.3.3 Test description
10.5.3.3.1 Pre-test conditions
System Simulator:
– Cell A.
UE:
None.
Preamble:
– The UE is in state Registered, Idle mode (state 2) according to [18] (1 default EPS bearer context is active).
10.5.3.3.2 Test procedure sequence
Table 10.5.3.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request connectivity to an additional PDN (see Note) |
– |
– |
– |
– |
|
1A |
The UE transmits a SERVICE REQUEST |
–> |
SERVICE REQUEST |
– |
– |
|
1B |
The SS establishes SRB2 and DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure). |
– |
– |
– |
– |
|
2 |
The UE transmits a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN. |
–> |
PDN CONNECTIVITY REQUEST |
– |
– |
|
3 |
The SS transmits a PDN CONNECTIVITY REJECT message. |
<– |
PDN CONNECTIVITY REJECT |
– |
– |
|
4 |
Void |
– |
– |
– |
– |
|
5 |
Void |
– |
– |
– |
– |
|
6 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
7 |
Cause the UE to request connectivity to an additional PDN (see Note) |
– |
– |
– |
– |
|
8 |
The UE transmits a SERVICE REQUEST message. |
–> |
SERVICE REQUEST |
– |
– |
|
9 |
The SS establishes a DRB associated with the default EPS bearer context activated during the preamble. |
– |
– |
– |
– |
|
9A |
Check: Does the UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN? |
–> |
PDN CONNECTIVITY REQUEST |
1 |
P |
|
9B |
The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context. Note: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST is included in dedicatedInfoNASList of RRCConnectionReconfiguration message. |
<– |
ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 10 below, the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane. |
– |
– |
– |
– |
|
10 |
Check: Does the UE transmit an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS bearer? |
–> |
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT |
1 |
P |
|
11 |
The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message included in an RRCConnectionReconfiguration message for the EPS bearer activated in steps 9B and 10. |
<– |
DEACTIVATE EPS BEARER CONTEXT REQUEST |
– |
– |
|
12 |
The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message. |
–> |
DEACTIVATE EPS BEARER CONTEXT ACCEPT |
– |
– |
|
Note: The trigger in step 1 and the RRC messages in steps 1A to 2 and in steps 8 to 10 are the same as in the generic procedure in 36.508 clause 6.4.3.2. The request of connectivity to an additional PDN may be performed by MMI or AT command. |
|||||
10.5.3.3.3 Specific message contents
Table 10.5.3.3.3-1: Message PDN CONNECTIVITY REQUEST (step 2, table 10.5.3.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-20 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
|
|
ESM information transfer flag |
Not present |
This IE is only activable during an attach procedure. |
|
|
Access point name |
APN-1(New PDN name) |
The requested PDN is different from default PDN |
|
Table 10.5.3.3.3-2: Message PDN CONNECTIVITY REJECT (step 3, table 10.5.3.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-1 |
The SS indicates the same value like received in the PDN CONNECTIVITY REQUEST |
|
|
ESM cause |
01101111 |
“Protocol error, unspecified” |
|
|
Protocol configuration options |
Not present |
||
Table 10.5.3.3.3-3: Void
Table 10.5.3.3.3-4: Message PDN CONNECTIVITY REQUEST (step 9A, table 10.5.3.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-20 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-2 |
UE assigns a particular PTI not yet used between 1 and 254 (may be identical to PTI-1) |
|
|
ESM information transfer flag |
Not present |
This IE is only activable during an attach procedure. |
|
|
Access point name |
APN-2 (New PDN name) |
The requested PDN is different from default PDN (may be identical to APN-1) |
|
Table 10.5.3.3.3-5: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 9B, table 10.5.3.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-6 and table 4.6.1-8 with condition AM-DRB-ADD(2) |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
Procedure transaction identity |
PTI-2 |
SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure. |
|
|
Access point name |
APN-2 |
SS re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure |
|
Table 10.5.3.3.3-6: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 10, table 10.5.3.3.2-1)
|
Derivation path: 36.508 table 4.7.3-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
|
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
10.5.4 UE requested PDN connectivity not accepted / Network reject with Extended Wait Timer
10.5.4.1 Test Purpose (TP)
(1)
with { the UE has sent a EXTENDED SERVICE REQUEST message indicating low NAS signalling priority }
ensure that {
when { the UE receives RRC reject with Extended wait timer }
then { the UE activates timer T3346 with the value of the Extended wait time and, if higher layers in the UE request the activation of such a connection/context afterwards, the UE does not initiate any signalling before the timer has expired }
}
(2)
with { UE is in EMM-REGISTERED mode }
ensure that {
when { UE is triggered to request connectivity to an additional PDN after timer T3346 has elapsed }
then { the UE transmits a PDN CONNECTIVITY REQUEST message with the request type set to "initial request" and including the name of the additional APN }
}
10.5.4.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 4.2A, 5.6.1.2, 5.6.1.6 and 6.5.1.2.
[TS 24.301, clause 4.2A]
A UE configured for NAS signalling low priority indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured for NAS signalling low priority", except for the following cases in which the UE shall set the low priority indicator to "MS is not configured for NAS signalling low priority":
– the UE is performing an attach for emergency bearer services;
– the UE has a PDN connection for emergency bearer services established and is performing EPS mobility management procedures, or is establishing a PDN connection for emergency bearer services;
– the UE is accessing the network with access class 11 – 15; or
– the UE is responding to paging.
The network may use the NAS signalling low priority indication for NAS level mobility management congestion control and APN based congestion control.
If the NAS signalling low priority indication is provided in a PDN CONNECTIVITY REQUEST message, the MME stores the NAS signalling low priority indication within the default EPS bearer context activated due to the PDN connectivity request procedure.
[TS 24.301, clause 5.6.1.2]
…
For cases a, b, c, h and k, if the UE is configured for NAS signalling low priority, and the last received ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message from the network indicated that the network supports use of EXTENDED SERVICE REQUEST for packet services, the UE shall send an EXTENDED SERVICE REQUEST message with service type set to "packet services via S1". If the last received ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message from the network did not indicate that the network supports use of EXTENDED SERVICE REQUEST for packet services, the UE shall instead send a SERVICE REQUEST message. After sending the SERVICE REQUEST message or EXTENDED SERVICE REQUEST message with service type set to "packet services via S1", the UE shall start T3417 and enter the state EMM-SERVICE-REQUEST-INITIATED.
[TS 24.301, clause 5.6.1.6]
…
l) "Extended wait time" from the lower layers
The UE shall abort the service request procedure, enter state EMM-REGISTERED, and stop timer T3417 or T3417ext if still running.
If the EXTENDED SERVICE REQUEST message contained the NAS signalling low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall start timer T3346 with the "Extended wait time" value.
In other cases the UE shall ignore the "Extended wait time".
The service request procedure is started, if still necessary, when timer T3346 expires or is stopped.
If the service request was initiated for CS fallback and timer T3246 is not running, the UE in CS/PS mode 1 of operation shall select GERAN or UTRAN radio access technology and disable E-UTRA capability (see subclause 4.5). It then proceeds with appropriate MM and CC specific procedures. The EMM sublayer shall not 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 call processing.
If the service request was initiated due to a request from the SMS entity to send an SMS and timer T3246 is not running, the UE, if operating in CS/PS mode 1 of operation, may select GERAN or UTRAN radio access technology and disable E-UTRA capability (see subclause 4.5). It then proceeds with the appropriate MM procedure.
[TS 24.301, clause 6.5.1.2]
…
In order to request connectivity to an additional PDN, the UE shall send a PDN CONNECTIVITY REQUEST message including a requested APN to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.1.2.1). In the PDN type information element the UE shall indicate the IP version capability of the IP stack associated with the UE as specified in subclause 6.4.1
The UE shall set the request type to "initial request" when the UE is establishing connectivity to a PDN for the first time, i.e. when it is an initial attach to that PDN. The UE shall set the request type to "handover" when the connectivity to a PDN is established upon handover from a non-3GPP access network and the UE was connected to that PDN before the handover to the 3GPP access network.
…
10.5.4.3 Test description
10.5.4.3.1 Pre-test conditions
System Simulator:
– Cell A.
UE:
– the UE is configured for NAS signalling low priority The UE is equipped with a USIM containing values shown in Table 10.5.4.3.1–1.
Table 10.5.4.3.1–1: USIM Configuration
|
USIM field |
Value |
|
EFUST |
Services 96 is supported. |
|
EFNASCONFIG |
“NAS_SignallingPriority is set to NAS signalling low priority” as defined in TS 24.368, clause 5.3. |
|
EFNASCONFIG |
“ExtendedAccessBarring is set to extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8 |
|
Note: As per TS 23.401 [22] clause 4.3.17.4, UE’s configuration of low access priority and Extended Access Barring shall match each other. |
|
Preamble:
– The UE is in state Registered, Idle mode (state 2) according to [18] (1 default EPS bearer context is active).
10.5.4.3.2 Test procedure sequence
Table 10.5.4.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request connectivity to an additional PDN (see Note) |
– |
– |
– |
– |
|
1A |
The UE transmits an RRCConnectionRequest message with establishment cause set to delayTolerantAccess-v1020 |
–> |
RRC: RRCConnectionRequest |
– |
– |
|
2 |
Check: Does the UE transmit an EXTENDED SERVICE REQUEST? |
–> |
EXTENDED SERVICE REQUEST |
1 |
P |
|
3 |
The SS transmits an RRCConnectionRelease message. The SS includes the IE “Extended Wait Time” in the RRCConnectionRelease message. UE starts timer T3346 with the value 120 seconds. |
<– |
RRC: RRCConnectionRelease. |
– |
– |
|
3A |
Cause the UE to request connectivity to an additional PDN (see Note) |
||||
|
4 |
Check: does the UE initiate any signalling before timer T3346 has expired? |
– |
– |
1 |
F |
|
4AA |
Cause the UE to request connectivity to an additional PDN (see Note) |
||||
|
4A |
The UE transmits an RRCConnectionRequest message with establishment cause set to delayTolerantAccess-v1020 |
–> |
RRC: RRCConnectionRequest |
– |
– |
|
5 |
The UE transmits an EXTENDED SERVICE REQUEST message. |
–> |
EXTENDED SERVICE REQUEST |
– |
– |
|
6 |
The SS establishes a DRB associated with the default EPS bearer context activated during the preamble. |
– |
– |
– |
– |
|
7 |
Check: Does the UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN? |
–> |
PDN CONNECTIVITY REQUEST |
2 |
P |
|
8 |
The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context. Note: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST is included in dedicatedInfoNASList of RRCConnectionReconfiguration message. |
<– |
ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 9 below, the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane. |
– |
– |
– |
– |
|
9 |
The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS bearer |
–> |
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT |
– |
– |
|
Note: The trigger in step 1, Step 3A and step 4AA is the same as in the generic procedure in 36.508 clause 6.4.3.2. The request of connectivity to an additional PDN may be performed by MMI or AT command. Different APN names APN-1, APN-2 resp. APN-3 are used. |
|||||
10.5.4.3.3 Specific message contents
Table 10.5.4.3.3-0A: Message ATTACH REQUEST (Preamble)
|
Derivation path: TS 36.508 table 4.7.2.-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Device properties |
1 |
“MS is configured for NAS signalling low priority” |
|
Table 10.5.4.3.3-0B: Message ATTACH ACCEPT (Preamble)
|
Derivation path: TS 36.508 table 4.7.2.-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS network feature support |
‘0010 0001’B |
EXTENDED SERVICE REQUEST to request for packet services supported. IMS voice over PS session in S1 mode supported |
|
Table 10.5.4.3.3-0C: Message RRCConnectionRequest (steps 1A and 4A, Table 10.5.4.3.2-1)
|
Derivation path: 36.508 table 4.6.1-16 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
RRCConnectionRequest ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionRequest-r8 SEQUENCE { |
|||
|
establishmentCause |
delayTolerantAccess-v1020 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 10.5.4.3.3-1: Message EXTENDED SERVICE REQUEST (step 2 and 5, table 10.5.4.3.2-1)
|
Derivation path: 36.508 table 4.7.2-14A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Service type |
1000 |
‘packet services via S1’ |
|
|
Device properties |
1 |
‘MS is configured for NAS signalling low priority’ |
|
Table 10.5.4.3.3-2: Message RRCConnectionRelease (step 3, Table 10.5.4.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-15 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionRelease ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionRelease-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
RRCConnectionRelease-v890-IEs |
||
|
lateNonCriticalExtension |
Not Present |
||
|
nonCriticalExtension SEQUENCE { |
RRCConnectionRelease-v920-IEs |
||
|
cellInfoList-r9 |
Not Present |
||
|
nonCriticalExtension SEQUENCE { |
RRCConnectionRelease-v1020-IEs |
||
|
extendedWaitTime-r10 |
120 seconds |
||
|
nonCriticalExtension |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 10.5.4.3.3-3: Message PDN CONNECTIVITY REQUEST (step 7, Table 10.5.4.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-20 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
0000 |
No EPS bearer identity assigned |
|
|
Procedure transaction identity |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
|
|
Request type |
001 |
initial request |
|
|
ESM information transfer flag |
Not present |
This IE is only activable during an attach procedure. |
|
|
Access point name |
APN-3 (New PDN name) |
The requested PDN is different from default PDN |
|
|
Device properties |
1 |
‘MS is configured for NAS signalling low priority’ |
|
Table 10.5.4.3.3-4: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 8, Table 10.5.4.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.3-6 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
Procedure transaction identity |
PTI-1 |
SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure. |
|
|
Access point name |
APN-3 |
SS re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure |
|