11.2.1 Emergency bearer services / Normal cell / NORMAL-SERVICE / Local Emergency Numbers List sent in the Attach / PDN connect new emergency EPS bearer context / Service request / Emergency PDN disconnect

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

11.2.1.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state and EMM-IDLE mode }

ensure that {

when { UE is requested to make an outgoing emergency call }

then { UE establishes the RRC connection with the RRC establishmentCause set to ‘emergency’ and sends a SERVICE REQUEST message }

}

(2)

with { UE is in EMM-REGISTERED state }

ensure that {

when { UE is triggered to request connectivity to an additional PDN for emergency bearer service }

then { the UE transmits a PDN CONNECTIVITY REQUEST message with the request type set to "emergency" and not 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 }

then { UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message containing the EPS bearer identity }

}

(4)

with { UE is in EMM-REGISTERED state and PDN connection for emergency bearer service established }

ensure that {

when { UE is triggered to request connectivity to an additional PDN for emergency bearer service }

then { the UE does not transmit a PDN CONNECTIVITY REQUEST message }

}

(5)

with { UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message for Emergency bearer service }

then { UE deletes the emergency EPS bearer context identified by the EPS bearer identity and transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT }

}

11.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clauses 5.3.3.2 and 5.3.3.3, and, TS 24.301, clauses 5.3.7, 6.5.1.1, 6.5.1.2, 6.4.1.3, 6.4.4.2, 5.5.3.2.4, 5.6.1.4, 6.4.4.3 and 6.4.4.6. Unless otherwise stated these are Rel-9 requirements.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

…

1> else if the UE is establishing the RRC connection for emergency calls:

2> if SystemInformationBlockType2 includes the ac-BarringInfo:

…

2> else:

3> consider access to the cell as not barred;

…

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

[TS 36.331, clause 5.3.3.3]

The UE shall set the contents of RRCConnectionRequest message as follows:

…

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

The purpose of the UE requested PDN connectivity procedure is for a UE to request the setup of a default EPS bearer to a PDN. The UE requests connectivity to a PDN by sending a PDN CONNECTIVITY REQUEST message to the network. If accepted by the network, this procedure initiates the establishment of a default EPS bearer context. The procedure is used either to establish the first default bearer by including the PDN CONNECTIVITY REQUEST message into the initial attach message, or to establish subsequent default bearers to additional PDNs in order to allow the UE simultaneous access to multiple PDNs by sending the message stand-alone.

If there is already a PDN connection for emergency bearer services established, the UE shall not request an additional PDN connection for emergency bearer services.

[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 to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.1.2.1). If the additional PDN connection is for emergency bearer services, the UE shall not include an APN in the PDN CONNECTIVITY REQUEST message; otherwise the UE shall include the requested APN.

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 a new PDN connectivity to a PDN in an attach procedure or in a stand-alone PDN connectivity procedure. The UE shall set the request type to "emergency" when the UE is requesting a new PDN connectivity for emergency bearer services. 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.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).

Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message, the MME shall enter the state BEARER CONTEXT ACTIVE and stop the timer T3485, if the timer is running.

[TS 24.301, clause 6.4.4.2]

…

When the MME wants to deactivate all EPS bearer contexts to a PDN and thus disconnect the UE from the PDN, the MME shall include the EPS bearer identity of the default bearer associated to the PDN in the DEACTIVATE EPS BEARER CONTEXT REQUEST message.

If no NAS signalling connection exists when the MME initiates the EPS bearer context deactivation, the ESM entity in the MME shall locally deactivate the EPS bearer context towards the UE without any peer-to-peer ESM signalling between the MME and the UE.

NOTE: The EPS bearer context state(s) can be synchronized between the UE and the MME at the next EMM-IDLE to EMM-CONNECTED transition, e.g. during a service request or tracking area updating procedure.

[TS 24.301, clause 6.4.4.3]

Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall delete the EPS bearer context identified by the EPS bearer identity. After deactivating the identified EPS bearer context, the UE shall respond to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT.

If the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST is that of the default bearer to a PDN, the UE shall delete all EPS bearer contexts associated to the PDN. After deactivating all EPS bearer contexts, the UE shall respond to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT.

Upon sending the DEACTIVATE EPS BEARER CONTEXT ACCEPT message, the UE shall enter the state BEARER CONTEXT INACTIVE

If the PTI is included in the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE uses the PTI to identify the UE requested bearer resource modification procedure or UE requested PDN disconnect procedure to which the EPS bearer context deactivation is related (see subclause 6.5.4).

If the PTI is included in the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall release the traffic flow aggregate description associated to the PTI value provided.

[TS 24.301 clause 5.3.7]

The network may send a Local Emergency Numbers List in the ATTACH ACCEPT or in the TRACKING AREA UPDATE ACCEPT messages, by including the Emergency Number List IE. The user equipment shall store the Local Emergency Numbers List, as provided by the network, except that any emergency number that is already stored in the USIM shall be removed from the Local Emergency Numbers List before it is stored by the user equipment. If there are no emergency numbers stored on the USIM, then before storing the received Local Emergency Numbers List, the user equipment shall remove from the Local Emergency Numbers List any emergency number stored permanently in the user equipment for use in this case (see 3GPP TS 22.101 [8]). The Local Emergency Numbers List stored in the user equipment shall be replaced on each receipt of a new Emergency Number List IE.

The emergency number(s) received in the Emergency Number List IE are valid only in networks with the same MCC as in the cell on which this IE is received. If no Local Emergency Numbers List is contained in the ATTACH ACCEPT or in the TRACKING AREA UPDATE ACCEPT message, then the stored Local Emergency Numbers List in the user equipment shall be kept, except if the user equipment has successfully registered to a PLMN with an MCC different from that of the last registered PLMN.

The Local Emergency Numbers List shall be deleted at switch off and removal of the USIM. The user equipment shall be able to store up to ten local emergency numbers received from the network.

11.2.1.3 Test description

11.2.1.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18] and is the serving cell.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18] on Cell A. UE received local emergency numbers list in ‘Attach Accept’ message. The local emergency number list is different from all emergency numbers stored in the UE.

11.2.1.3.2 Test procedure sequence

Table 11.2.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 for emergency bearer service and an emergency call to one of the numbers received in Attach Accept message (see Note 1)	–	–	–	–
2A	Check: Does the UE transmit an RRCConnectionRequest message with establishmentCause set to ‘emergency’?	–>	RRCConnectionRequest	1	P
2	Check: Does UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	1	P
3-13	Steps 5 to 15 of the generic test procedure for IMS Emergency call establishment in EUTRA: in EUTRA: Normal Service (TS 36.508 subclause 4.5A.4.3-1).	–	–	2,3	P
13A	Release IMS Call (see Note 4)	–	–	–	–
14	The SS releases the RRC connection.	–	–	–	–
15	Cause the UE to request connectivity to an additional PDN for emergency bearer service (see Note 1)	–	–	–	–
16	Check: Does UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	4	F
17	The SS transmits a Paging message to the UE using S-TMSI with CN domain indicator set to ”PS”.	–	–	–	–
18	The UE transmits the SERVICE REQUEST message	–>	SERVICE REQUEST	–	–
19	The SS establishes SRB2 and DRBs associated with two default EPS bearer context (a first PDN obtained during the attach procedure and an additional PDN).( see Note 2)	–	–	–	–
20	The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity of the default EPS bearer to the additional PDN.	<–	DEACTIVATE EPS BEARER CONTEXT REQUEST	–	–
21	Check: Does the UE transmit a DEACTIVATE EPS BEARER CONTEXT ACCEPT? (see Note 3)	–>	DEACTIVATE EPS BEARER CONTEXT ACCEPT	5	P
Note 1: The request of connectivity to an additional PDN and the sending of data may be performed by MMI or AT command. (e.g. AT command +cgdcont with <Emergency Indication> set to 1) Note 2: After a correct SERVICE REQUEST is received then the SS performs the Radio Bearer Establishment procedure. The UE transmission of the RRCConnectionReconfigurationComplete message indicates the completion of the radio bearer establishment procedure and that the UE has changed EMM mode from EMM-IDLE to EMM-CONNECTED. Note 3: It can be confirmed that the additional default EPS bearer has been deactivated by UE. Note 4: The IMS Call is released using the generic procedure in TS 34.229-1 [35] subclause C.32.

11.2.1.3.3 Specific message contents

Table 11.2.1.3.3-1: ATTACH ACCEPT (Preamble)

Derivation path: 36.508 table 4.7.2-1
Information Element	Value/Remark	Comment	Condition
Emergency number list	2 numbers TS 24.008, 10.5.3.13	The numbers shall be different than any of those indicated in TS 22.101 clause 10.1.1 AND the numbers stored in the USIM AND any emergency number stored permanently in the ME
EPS network feature support	‘0000 0111’B	– IMS voice over PS session in S1 mode supported – emergency bearer services in S1 mode supported – location services via EPC supported – no information about support of location services via CS domain is available

Table 11.2.1.3.3-2A: RRCConnectionRequest (step 2A, Table 11.2.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	emergency
}
}
}

Table 11.2.1.3.3-2: Message PDN CONNECTIVITY REQUEST (step 4, Table 11.2.1.3.2-1)

Derivation Path: 36.508 table 4.7.2-1
Information Element	Value/Remark	Comment	Condition
Request type	‘0100’B	emergency
Access point name	Not present

Table 11.2.1.3.3-3: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 5, Table 11.2.1.3.2-1)

Derivation path: 36.508 table 4.7.3-6 and table 4.6.1-8 with condition UM-DRB-ADD(2)
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	6	SS assigns an additional EPS Bearer Id different from default EPS Bearer Id between 5 and 15.
Access point name	APN-1

Table 11.2.1.3.3-4: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 13, Table 11.2.1.3.2-1)

Derivation path: 36.508 table 4.7.3-12 and table 4.6.1-8 with condition and condition NETWORK-INITIATED
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	Default EBId-2	Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST of step 3
ESM cause	00100100	regular deactivation