8.1.5 UE capability

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

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

8.1.5.1 UE Capability in CELL_DCH state: Success

8.1.5.1.1 Definition

8.1.5.1.2 Conformance requirement

The UE shall initiate the UE capability update procedure in the following situations:

1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN;

…

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall:

1> include the IE "RRC transaction identifier"; and

1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

1> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE system specific capability".

The UE RRC shall submit the UE CAPABILITY INFORMATION message to the lower layers for transmission on the uplink DCCH using AM RLC. When the message has been delivered to lower layers for transmission the UE RRC shall start timer T304 and set counter V304 to 1.

Upon reception of a UE CAPABILITY INFORMATION CONFIRM message, the UE shall:

1> stop timer T304;

…

1> and the procedure ends.

If the UE receives a UE CAPABILITY INFORMATION CONFIRM message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to TS 25.331 clause 9, the UE shall perform procedure specific error handling as follows:

1> stop timer T304;

1> transmit an RRC STATUS message on the uplink DCCH using AM RLC;

1> include the IE "Identification of received message"; and

1> set the IE "Received message type" to UE CAPABILITY INFORMATION CONFIRM; and

1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY INFORMATION CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; and

1> clear that entry;

1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION;

1> when the RRC STATUS message has been submitted to lower layers for transmission:

2> restart timer T304 and continue with any ongoing procedures or processes as if the invalid UE CAPABILITY INFORMATION CONFIRM message has not been received.

…

If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, containing an undefined critical message extension, the UE shall:

1> set the variable PROTOCOL_ERROR_REJECT to TRUE;

1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Message extension not comprehended";

1> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS:

2> store the IE "Message type" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and

2> set the IE "RRC transaction identifier" to zero in that table entry.

1> perform procedure specific error handling according to TS 25.331 clause 8.

Reference

3GPP TS 25.331 clauses 8.1.6, 8.1.7 and 9.3b.

8.1.5.1.3 Test purpose

1. To confirm that the UE transmits a UE CAPABILITY INFORMATION message after it receives a UE CAPABILITY ENQUIRY message from the SS.

2. To confirm that the UE indicates an invalid message reception when invalid UE CAPABILITY ENQUIRY and UE CAPABILITY INFORMATION CONFIRM messages are received. The UE shall transmit RRC STATUS message with the correct error cause value to SS.

8.1.5.1.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_DCH state (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE is brought to the CELL_DCH state after a successful outgoing call attempt. The SS transmits a UE CAPABILITY ENQUIRY message containing an unexpected critical message extension. After receiving such a message, the UE shall report the error using RRC STATUS message with the appropriate error cause specified. Then SS transmits a correct UE CAPABILITY ENQUIRY message, the UE receives this message and transmits a UE CAPABILITY INFORMATION message on the uplink DCCH which includes the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

Then SS initiates another UE capability enquiry procedure. The UE shall reply with a UE CAPABILITY INFORMATION message on the uplink DCCH. When SS receives this message, it transmits a UE CAPABILITY INFORMATION CONFIRM message containing an unexpected critical message extension. The UE shall detect an error and send an RRC STATUS message to report this event. After submitting this message to lower layers for transmission, the UE shall re-transmit a UE CAPABILITY INFORMATION message on the uplink DCCH after the expiry of restarted T304. SS then hen transmits an error-free UE CAPABILITY INFORMATION CONFIRM message similar to the message sent in step 6.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1				The UE is brought to CELL_DCH state after an outgoing call has been established successfully.
2			UE CAPABILITY ENQUIRY	See specific message contents for this message
3			RRC STATUS	See specific message contents for this message
4			UE CAPABILITY ENQUIRY	See specific message contents for this message.
5			UE CAPABILITY INFORMATION	See specific message contents for this message.
6			UE CAPABILITY INFORMATION CONFIRM	Use default message.
7			UE CAPABILITY ENQUIRY	Same as in step 4.
8			UE CAPABILITY INFORMATION	Shall be the same message content as in step 5.
9			UE CAPABILITY INFORMATION CONFIRM	See specific message contents for this message
10			RRC STATUS	UE shall detect an error and then transmit this message.
11			UE CAPABILITY INFORMATION	UE shall re-transmit this message after the restarted T304 expires.
12			UE CAPABILITY INFORMATION CONFIRM	SS sends an error-free message to acknowledge the receipt of the uplink message.

Specific Message Contents

UE CAPABILITY ENQUIRY (Step 2)

SS sends a message containing a critical extension not defined for the protocol release supported by the UE, as indicated in the IE "Access stratum release indicator":

Information Element	Value/remark
Message Type
RRC transaction identifier	Arbitrarily selects an integer between 0 and 3
Integrity check info
– Message authentication code	SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	SS provides the value of this IE, from its internal counter.
Critical extensions	’FF’H

RRC STATUS (Step 3)

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element

Value/remark

Identification of received message

– Received message type

– RRC transaction identifier

Protocol Error Information

– Protocol Error Cause

UE Capability Enquiry

Message extension not comprehended

Information Element	Value/remark
Identification of received message
– Received message type	UE Capability Enquiry
– RRC transaction identifier	Checked to see if the value is identical to the same IE in the downlink UE CAPABILITY ENQUIRY message.
Protocol Error Information
– Protocol Error Cause	Message extension not comprehended

UE CAPABILITY ENQUIRY (Steps 4) (FDD)

Use the UE CAPABILITY ENQUIRY message as defined in [9] (TS 34.108) Clause 9, with the following exceptions:

Information Element	Value/remark
Capability update requirement
– UE radio access FDD capability update requirement	TRUE
– UE radio access TDD capability update requirement	FALSE
– System specific capability update requirement list	Gsm

UE CAPABILITY ENQUIRY (Steps 4) (3.84 Mcps TDD)

Use the UE CAPABILITY ENQUIRY message as defined in [9] (TS 34.108) Clause 9, with the following exceptions:

Information Element	Value/remark
Capability update requirement
– UE radio access FDD capability update requirement	FALSE
– UE radio access TDD capability update requirement	TRUE
– System specific capability update requirement list	Gsm

UE CAPABILITY ENQUIRY (Steps 4) (1.28 Mcps TDD)

Use the UE CAPABILITY ENQUIRY message as defined in [9] (TS 34.108) Clause 9, with the following exceptions.

Information Element	Value/remark
Capability update requirement
– UE radio access FDD capability update requirement	FALSE
– UE radio access TDD capability update requirement	TRUE
UE radio access 1.28 Mcps TDD capability update requirement	TRUE
– System specific capability update requirement list	Gsm

UE CAPABILITY ENQUIRY (Steps 4) (7.68 Mcps TDD)

Use the UE CAPABILITY ENQUIRY message as defined in [9] (TS 34.108) Clause 9, with the following exceptions:

Information Element	Value/remark
Capability update requirement
– UE radio access FDD capability update requirement	FALSE
– UE radio access 3.84 Mcps TDD capability update requirement	FALSE
– UE radio access 7.68 Mcps TDD capability update requirement	TRUE
– UE radio access 1.28 Mcps TDD capability update requirement	FALSE
– System specific capability update requirement list	Gsm

UE CAPABILITY INFORMATION (Step 5)

Check to see if the same message type found in [9] (TS 34.108) Clause 9 is received, with the following exceptions:

Information Element	Value/remark
UE system specific capability	Presence and value will be checked. Stated capability must be compatible with 34.123-2 (ICS statements) and the user settings

UE CAPABILITY INFORMATION CONFIRM (Step 9)

SS sends a message containing a critical extension not defined for the protocol release supported by the UE, as indicated in the IE "Access stratum release indicator". Use the UE CAPABILITY INFORMATION CONFIRM message as defined in [9] (TS 34.108) Clause 9, with the following addition:

Information Element	Value/remark
Critical extensions	’FF’H

RRC STATUS (Step 10)

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element	Value/remark
Identification of received message
– Received message type	UE Capability Information Confirm
– RRC transaction identifier	0
Protocol Error Information
– Protocol Error Cause	Message extension not comprehended

8.1.5.1.5 Test requirement

After step 2, the UE shall transmit a RRC STATUS message on the uplink DCCH, reporting the error with protocol error cause set to "Message extension not comprehended" correct transaction identifier.

After step 4 and 7 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the UE CAPABILITY ENQUIRY message with correct contents.

After step 9, the UE shall transmit a RRC STATUS message on the uplink DCCH. The protocol error cause shall be set to "Message extension not comprehended" and the transaction identifier set to the same value as used in the UE CAPABILITY ENQUIRY message of step 7.

After step 10, the UE shall re-transmit the UE CAPABILITY INFORMATION message with a similar content as in step 8 after the expiry of restarted T304.

8.1.5.2 UE Capability in CELL_DCH state: Success after T304 timeout

8.1.5.2.1 Definition

8.1.5.2.2 Conformance requirement

The UE shall initiate the UE capability update procedure in the following situations:

1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN on the DCCH using UM or AM RLC;

1> while in connected mode the UE capabilities change compared to those stored in the variable UE_CAPABILITY_TRANSFERRED.

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall:

1> include the IE "RRC transaction identifier"; and

1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

1> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE system specific capability".

If the UE CAPABILITY INFORMATION message is sent because one or more of the UE capabilities change compared to those stored in the variable UE_CAPABILITY_TRANSFERRED while in connected state, the UE shall include the information elements associated with the capabilities that have changed in the UE CAPABILITY INFORMATION message.

…

Upon expiry of timer T304, the UE shall check the value of V304 and:

1> if V304 is smaller than or equal to N304:

2> prior to retransmitting the UE CAPABILITY INFORMATION message:

3> if the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started":

4> include the same IEs as in the last unsuccessful attempt of this message, except for the IE "Integrity check info", which is modified as follows:

5> increment the "Uplink RRC Message sequence number" for signalling radio bearer RB2 in the variable INTEGRITY_PROTECTION_INFO by one;

5> set the IE "RRC Message sequence number" in the IE "Integrity check info" by the value of the "Uplink RRC Message sequence number" for signalling radio bearer RB2 in the variable INTEGRITY_PROTECTION_INFO in this message;

5> recalculate the IE "Message authentication code" in the IE "Integrity check info" in this message, in accordance with TS 25.331 subclause 8.5.10.3.

3> else:

4> include the same IEs as in the last unsuccessful attempt of this message.

2> send the UE CAPABILITY INFORMATION message on signalling radio bearer RB2;

2> restart timer T304;

2> increment counter V304.

…

Reference

3GPP TS 25.331 clause 8.1.6 and 8.1.7.

8.1.5.2.3 Test purpose

To confirm that the UE re-transmits a UE CAPABILITY INFORMATION message until V304 is greater than N304, after the expiry of timer T304 when the UE cannot receive a UE CAPABILITY INFORMATION CONFIRM message in response to a UE CAPABILITY INFORMATION message.

8.1.5.2.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_DCH state (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE is brought to CELL_DCH state. When the SS transmits a UE CAPABILITY ENQUIRY message which includes the "Capability update requirement" IE, the UE shall reply with a UE CAPABILITY INFORMATION message on the uplink DCCH which includes the "UE radio access capability" IE. The SS does not transmit a UE CAPABILITY INFORMATION CONFIRM message to the UE, resulting in the T304 timer to expire. SS shall observe that the UE attempts to transmit a UE CAPABILITY INFORMATION message again. The UE shall re-transmit N304 times, and SS transmits a UE CAPABILITY INFORMATION CONFIRM message to answer the last request and completes this test procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is brought to CELL_DCH state. SS sets internal counter K =0
2			UE CAPABILITY ENQUIRY	Including the IE "Capability update requirement".
3			UE CAPABILITY INFORMATION	Including the "UE radio access capability".
4				If K is equal to N304, then proceed to step 6.
5				The SS does not transmit a response and wait for T304 timer to expire. K=K+1 and goes to step 3.
6			UE CAPABILITY INFORMATION CONFIRM	Use default message contents

Specific Message Contents

None

8.1.5.2.5 Test requirement

After step 3 the UE shall re-transmits a UE CAPABILITY INFORMATION message on the uplink DCCH, after each expiry of timer T304. The UE CAPABILITY INFORMATION message shall contain IE "UE radio access capability" indicating the settings found in PIC/PIXIT statements. After (N304) re-transmissions, the UE shall receive a UE CAPABILITY INFORMATION CONFIRM message.

8.1.5.3 UE Capability in CELL_DCH state: Failure (After N304 re-transmissions)

8.1.5.3.1 Definition

8.1.5.3.2 Conformance requirement

The UE shall initiate the UE capability update procedure in the following situations:

1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN on the DCCH using UM or AM RLC;

1> while in connected mode the UE capabilities change compared to those stored in the variable UE_CAPABILITY_TRANSFERRED.

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall:

1> include the IE "RRC transaction identifier"; and

1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

1> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE system specific capability".

…

Upon expiry of timer T304, the UE shall check the value of V304 and:

1> if V304 is smaller than or equal to N304:

2> prior to retransmitting the UE CAPABILITY INFORMATION message:

3> if the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started":

4> include the same IEs as in the last unsuccessful attempt of this message, except for the IE "Integrity check info", which is modified as follows:

5> increment the "Uplink RRC Message sequence number" for signalling radio bearer RB2 in the variable INTEGRITY_PROTECTION_INFO by one;

5> recalculate the IE "Message authentication code" in the IE "Integrity check info" in this message, in accordance with TS 25.331 subclause 8.5.10.3.

3> else:

4> include the same IEs as in the last unsuccessful attempt of this message.

2> send the UE CAPABILITY INFORMATION message on signalling radio bearer RB2;

2> restart timer T304;

2> increment counter V304.

1> if V304 is greater than N304:

2> initiate the Cell update procedure as specified in TS 25.331 subclause 8.3.1, using the cause "Radio link failure".

Reference

3GPP TS 25.331 clauses 8.1.6 and 8.1.7.

8.1.5.3.3 Test purpose

To confirm that the UE stops retrying to transmit a UE CAPABILITY INFORMATION message if V304 is greater than N304. It then initiates cell update procedure.

8.1.5.3.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_DCH state (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE is brought to CELL_DCH state. When the SS transmits a UE CAPABILITY ENQUIRY message which includes the "Capability update requirement" IE, the UE receives this message and transmits a UE CAPABILITY INFORMATION message on the uplink DCCH which includes the "UE radio access capability" IE. The SS does not respond with a UE CAPABILITY INFORMATION CONFIRM message but keeps a count on the number of messages received. When the T304 timer expires, the UE shall transmit a UE CAPABILITY INFORMATION message again. After sending (N304+1) messages, the UE shall stop sending UE CAPABILITY INFORMATION messages and initiates the cell update procedure. SS allows UE to return to "connected state" by issuing CELL UPDATE CONFIRM message on the downlink DCCH. Then the UE shall reconfigure its physical channel according to the CELL UPDATE CONFIRM message and respond with PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to SS.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE starts from CELL_DCH state. SS sets counter K to 0
2			UE CAPABILITY ENQUIRY	Use default message
3			UE CAPABILITY INFORMATION	Use default message
4				The SS does not transmit a response and allows T304 timer to expire. SS increments counter K If K is greater than N304, proceeds to step 5 else returns to 3.
5			CELL UPDATE	The UE assumes that radio link failure has occurred and transmits this message which includes IE "Cell update cause" set to "radio link failure".
6			CELL UPDATE CONFIRM	This message includes IE "Physical channel information elements".
7				The SS configure the dedicated physical channel according to the IE "Physical channel information elements" included in the CELL UPDATE CONFIRM message.
8			PHYSICAL CHANNEL RECONFIGURATION COMPLETE

Specific Message Contents

CELL UPDATE CONFIRM (Step 6) – FDD

The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found in clause 9 of TS 34.108 with the following exceptions:

Information Element	Value/remark	Version
U-RNTI	Same as CELL UPDATE message in step 5
RRC State indicator	CELL_DCH
Frequency info
– CHOICE mode	FDD
– UARFCN uplink(Nu)	Reference to TS 34.108 clause 5.1 Test frequencies
– UARFCN downlink(Nd)	Reference to TS 34.108 clause 5.1 Test frequencies
Maximum allowed UL TX power	33dBm
CHOICE Mode	FDD
Downlink information for each radio links
– Primary CPICH info
– Primary scrambling code	100
– PDSCH with SHO DCH info	Not Present	R99 and Rel-4 only
– PDSCH code mapping	Not Present	R99 and Rel-4 only
– Downlink DPCH info for each RL
– CHOICE mode	FDD
– Primary CPICH usage for channel estimation	Primary CPICH may be used
– DPCH frame offset	0 chips
– Secondary CPICH info	Not Present
– DL channelization code
– Secondary scrambling code	2
– Spreading factor	Reference to TS 34.108 clause 6.10 Parameter Set
– Code number	SF-1(SF is reference to TS 34.108 clause 6.10 Parameter Set)
– Scrambling code change	No change
– TPC combination index	0
– SSDT Cell Identity	-a	R99 and Rel-4 only
– Closed loop timing adjustment mode	Not Present
– SCCPCH information for FACH	Not Present	R99 and Rel-4 only

CELL UPDATE CONFIRM (Step 6) – 3.84 Mcps TDD

The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found in clause 9 of TS 34.108 with the following exceptions:

Information Element	Value/remark
U-RNTI	Same as CELL UPDATE message in step 5
RRC State indicator	CELL_DCH
Frequency info
– CHOICE mode	TDD
– UARFCN (Nt)	Reference to TS 34.108 clause 5.1 Test frequencies
Maximum allowed UL TX power	30dBm
CHOICE Mode	TDD
Downlink information for each radio links
– Primary CCPCH info
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– CHOICE SyncCase	Not Present
– Cell Parameters ID	Not Present
– Block STTD indicator	FALSE
– Downlink DPCH info for each RL
– CHOICE mode	TDD
– DL CCTrCh List
– TFCS ID	1
– Time info
– Activation time	Not Present (default)
– Duration	Not Present (default)
– Common timeslot info	Not Present (default)
– Downlink DPCH timeslots and codes	Not Present (default)
– UL CCTrCH TPC List	Not Present (default)

CELL UPDATE CONFIRM (Step 6) – 1.28 Mcps TDD

The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found in clause 9 of TS 34.108 with the following exceptions:

Information Element	Value/remark
U-RNTI	Same as CELL UPDATE message in step 5
RRC State indicator	CELL_DCH
Frequency info
– CHOICE mode	TDD
– UARFCN (Nt)	Reference to TS 34.108 clause 5.1 Test frequencies
Maximum allowed UL TX power	30dBm
CHOICE Mode	TDD
Downlink information for each radio links
– Primary CCPCH info
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– TSTD indicator	FALSE
– Cell Parameters ID	Not Present
– Block STTD indicator	FALSE
– Downlink DPCH info for each RL
– CHOICE mode	TDD
– DL CCTrCh List
– TFCS ID	1
– Time info
– Activation time	Not Present (default)
– Duration	Not Present (default)
– Common timeslot info	Not Present (default)
– Downlink DPCH timeslots and codes	Not Present (default)
– UL CCTrCH TPC List	Not Present (default)

CELL UPDATE CONFIRM (Step 6) – 7.68 Mcps TDD

The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found in clause 9 of TS 34.108 with the following exceptions:

Information Element	Value/remark
U-RNTI	Same as CELL UPDATE message in step 5
RRC State indicator	CELL_DCH
Frequency info
– CHOICE mode	TDD
– UARFCN (Nt)	Reference to TS 34.108 clause 5.1 Test frequencies
Maximum allowed UL TX power	30dBm
CHOICE Mode	TDD
Downlink information for each radio links
– Primary CCPCH info
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– CHOICE SyncCase	Not Present
– Cell Parameters ID	Not Present
– Block STTD indicator	FALSE
– Downlink DPCH info for each RL
– CHOICE mode	TDD
– DL CCTrCh List
– TFCS ID	1
– Time info
– Activation time	Not Present (default)
– Duration	Not Present (default)
– Common timeslot info	Not Present (default)
– Downlink DPCH timeslots and codes	Not Present (default)
– UL CCTrCH TPC List	Not Present (default)

8.1.5.3.5 Test requirement

After step 2, the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH. The UE shall re-transmit this message for N304 times.

After step 4, the UE shall initiate the cell update procedure.

After step 6, UE shall respond with a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message after it has configured L1 according to the CELL UPDATE CONFIRM message in step 6.

8.1.5.4 UE Capability in CELL_FACH state: Success

8.1.5.4.1 Definition

8.1.5.4.2 Conformance requirement

The UE shall initiate the UE capability update procedure in the following situations:

1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN;

…

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall:

1> include the IE "RRC transaction identifier"; and

1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

1> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE system specific capability".

Upon reception of a UE CAPABILITY INFORMATION CONFIRM message, the UE shall:

1> stop timer T304;

…

1> and the procedure ends.

1> stop timer T304;

1> transmit an RRC STATUS message on the uplink DCCH using AM RLC;

1> include the IE "Identification of received message"; and

1> set the IE "Received message type" to UE CAPABILITY INFORMATION CONFIRM; and

1> clear that entry;

1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION;

1> when the RRC STATUS message has been submitted to lower layers for transmission:

2> restart timer T304 and continue with any ongoing procedures or processes as if the invalid UE CAPABILITY INFORMATION CONFIRM message has not been received.

…

1> set the variable PROTOCOL_ERROR_REJECT to TRUE;

1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Message extension not comprehended";

1> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS:

2> store the IE "Message type" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and

2> set the IE "RRC transaction identifier" to zero in that table entry.

1> perform procedure specific error handling according to TS 25.331 clause 8.

Reference

3GPP TS 25.331 clauses 8.1.6, 8.1.7 and 9.3b.

8.1.5.4.3 Test purpose

1. To confirm that the UE transmits a UE CAPABILITY INFORMATION message after it receives a UE CAPABILITY ENQUIRY message from the SS.

8.1.5.4.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_FACH state (state 6-11) as specified in clause 7.4 of TS 34.108.

Test Procedure

The UE is brought to the CELL_FACH state after a successful outgoing call attempt. The SS transmits a UE CAPABILITY ENQUIRY message containing an unexpected critical message extension. After receiving such a message, the UE shall report an error using RRC STATUS message with the appropriate error cause specified. Then SS transmits a UE CAPABILITY ENQUIRY message which includes the IE "Capability update requirement". After UE receives this message, it transmits a UE CAPABILITY INFORMATION message on the uplink DCCH, which includes the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

Then SS initiates another UE capability enquiry procedure. The UE shall reply with a UE CAPABILITY INFORMATION message on the uplink DCCH. When SS receives this message, it transmits a UE CAPABILITY INFORMATION CONFIRM message containing an unexpected critical message extension. The UE shall detect an error and send an RRC STATUS message to report this event. After submitting this message to lower layers for transmission, the UE shall re-transmit a UE CAPABILITY INFORMATION message on the uplink DCCH upon the expiry of restarted T304. SS completes this test by sending an error-free UE CAPABILITY INFORMATION CONFIRM message similar to the message sent in step 6.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1				The UE is brought to CELL_FACH state after an outgoing call has been established successfully.
2			UE CAPABILITY ENQUIRY	See specific message contents for this message
3			RRC STATUS	See specific message contents for this message.
4			UE CAPABILITY ENQUIRY	Use default message.
5			UE CAPABILITY INFORMATION	Use default message.
6			UE CAPABILITY INFORMATION CONFIRM	Use default message.
7			UE CAPABILITY ENQUIRY	Same as in step 4.
8			UE CAPABILITY INFORMATION	The message content shall be the same as in step 5.
9			UE CAPABILITY INFORMATION CONFIRM	See specific message contents for this message
10			RRC STATUS	UE shall detect an error and then transmit this message on uplink DCCH.
11			UE CAPABILITY INFORMATION	UE shall re-transmit this message after the restarted T304 expires.
12			UE CAPABILITY INFORMATION CONFIRM	SS sends an error-free message to acknowledge the receipt of the uplink message.

Specific Message Contents

UE CAPABILITY ENQUIRY (Step 2)

Use the UE CAPABILITY ENQUIRY message as defined in [9] (TS 34.108) Clause 9, with the following exceptions:

Information Element	Value/remark
Message Type
RRC transaction identifier	Arbitrarily selects an integer between 0 and 3
Integrity check info
– Message authentication code	SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	SS provides the value of this IE, from its internal counter.
Critical extensions	’FF’H

RRC STATUS (Step 3)

Check to be the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element	Value/remark
Identification of received message
– Received message type	UE Capability Enquiry
RRC transaction identifier	0
Protocol Error Information
– Protocol Error Cause	Message extension not comprehended

UE CAPABILITY INFORMATION CONFIRM (Step 9)

Information Element	Value/remark
Critical extensions	’FF’H

RRC STATUS (Step 10)

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element	Value/remark
Identification of received message
– Received message type	UE Capability Information Confirm
– RRC transaction identifier	0
Protocol Error Information
– Protocol Error Cause	Message extension not comprehended

8.1.5.4.5 Test requirement

After step 2, the UE shall transmit a RRC STATUS message on the uplink DCCH, reporting the error with protocol error cause set to "Message extension not comprehended" correct transaction identifier.

After step 4 and 7 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the downlink UE CAPABILITY ENQUIRY message with correct contents.

After step 10, the UE shall re-transmit the UE CAPABILITY INFORMATION message with a similar content as in step 8 upon the expiry of restarted T304.

8.1.5.5 UE Capability in CELL_FACH state: Success after T304 timeout

8.1.5.5.1 Definition

8.1.5.5.2 Conformance requirement

The UE shall initiate the UE capability update procedure in the following situations:

1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN on the DCCH using UM or AM RLC;

1> while in connected mode the UE capabilities change compared to those stored in the variable UE_CAPABILITY_TRANSFERRED.

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall:

1> include the IE "RRC transaction identifier"; and

1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

1> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE system specific capability".

…

Upon expiry of timer T304, the UE shall check the value of V304 and:

1> if V304 is smaller than or equal to N304:

2> prior to retransmitting the UE CAPABILITY INFORMATION message:

3> if the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started":

4> include the same IEs as in the last unsuccessful attempt of this message, except for the IE "Integrity check info", which is modified as follows:

5> increment the "Uplink RRC Message sequence number" for signalling radio bearer RB2 in the variable INTEGRITY_PROTECTION_INFO by one;

5> recalculate the IE "Message authentication code" in the IE "Integrity check info" in this message, in accordance with TS 25.331 subclause 8.5.10.3.

3> else:

4> include the same IEs as in the last unsuccessful attempt of this message.

2> send the UE CAPABILITY INFORMATION message on signalling radio bearer RB2;

2> restart timer T304;

2> increment counter V304.

…

Reference

3GPP TS 25.331 clauses 8.1.6 and 8.1.7.

8.1.5.5.3 Test purpose

To confirm that the UE re-transmits a UE CAPABILITY INFORMATION message until V304 is greater than N304, after the expiry of timer T304 when it fails to receive a downlink UE CAPABILITY INFORMATION CONFIRM message in response to the uplink UE CAPABILITY INFORMATION message sent.

8.1.5.5.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_FACH state (state 6-11) as specified in clause 7.4 of TS 34.108.

Test Procedure

The UE is brought to CELL_FACH state. When the SS transmits a UE CAPABILITY ENQUIRY message which includes the IE "Capability update requirement", the UE shall reply with a UE CAPABILITY INFORMATION message on the uplink DCCH that contains the IE "UE radio access capability". The SS waits and does not transmit a UE CAPABILITY INFORMATION CONFIRM message to the UE, resulting in the T304 timer to expire. SS shall observe that the UE attempts to transmit a UE CAPABILITY INFORMATION message again. The UE shall re‑transmit N304 times, and SS transmits a UE CAPABILITY INFORMATION CONFIRM message to answer the last request and completes this test procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is brought to CELL_FACH state. SS sets internal counter K =0
2			UE CAPABILITY ENQUIRY	Including the IE "Capability update requirement".
3			UE CAPABILITY INFORMATION	Including the IE "UE radio access capability".
4				If K equals N304, then proceeds to step 6. Else, continue with step 5.
5				The SS does not transmit a response and wait for T304 timer to expire. K=K+1 and goes to step 3.
6			UE CAPABILITY INFORMATION CONFIRM	Use default message contents

Specific Message Contents

None

8.1.5.5.5 Test requirement

After step 3 the UE shall re-transmit a UE CAPABILITY INFORMATION message on the uplink DCCH, after each expiry of timer T304. The UE CAPABILITY INFORMATION message shall contain IE "UE radio access capability" with the value matching those stated in the ICS/IXIT statements. After (N304) re-transmissions, the UE shall receive a UE CAPABILITY INFORMATION CONFIRM message.

8.1.5.6 UE Capability Information/ Reporting Of InterRAT Specific UE RadioAccessCapability.

8.1.5.6.1 Definition

8.1.5.6.2 Conformance requirement

The UE shall initiate the UE capability update procedure in the following situations:

1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN;

…

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall:

1> include the IE "RRC transaction identifier"; and

1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

1> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

1> include this in IE "UE system specific capability".

Reference

3GPP TS 25.331 clauses 8.1.6

8.1.5.6.3 Test purpose

To confirm that a multi-RAT UE responds with a UE CAPABILITY INFORMATION message after it receives a UE CAPABILITY ENQUIRY message from the UTRAN and it includes the inter-RAT-specific UE radio access capability information element.

8.1.5.6.4 Method of test

Initial Condition

System Simulator: 1 cell – Cell 1 is UTRAN.

UE: CELL_DCH state (state 6-9) as specified in clause 7.4 of TS 34.108

Related ICS/IXIT statement(s)

– UE supports both GSM and UTRAN Radio Access Technologies,

– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.

Test Procedure

The SS starts the UTRAN cell.The UE is brought into the CELL_DCH state after a successful outgoing call attempt on the UTRAN cell. The SS transmits a UE CAPABILITY ENQUIRY message with System Specific Cap Update Req set to GSM. The UE shall respond with a UE CAPABILITY INFORMATION message on the uplink DCCH that includes the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is brought to CELL_DCH 6-9 state after an outgoing call has been established successfully.
2			UE CAPABILITY ENQUIRY	See specific message contents
3			UE CAPABILITY INFORMATION	See specific message contents
4			UE CAPABILITY INFORMATION CONFIRM	Use default message.

Specific Message Contents

UE CAPABILITY ENQUIRY (Step 2)

Use the UE CAPABILITY ENQUIRY message as defined in (TS 34.108) Clause 9, with the following exceptions:

Information Element	Value/remark
Capability update requirement
– UE radio access FDD capability update requirement	TRUE
– UE radio access TDD capability update requirement	FALSE
– System specific capability update requirement list	GSM

UE CAPABILITY INFORMATION (Step 3)

Check to see if the same message type found in (TS 34.108) Clause 9 is received, with the following exceptions:

Information Element

Value/remark

UE_RadioAccessCapability

This IE should reflect the corresponding fdd capability and the IE

UE_MultimodeRATCapability should indicate GSM capability according to PICS.

InterRAT_UE_RadioAccessCapability

GSM

GSM Classmark 2

GSM Classmark 3

Presence and value will be checked. Stated capability must be compatible with 34.123-3 (ICS statements) and the user settings

8.1.5.6.5 Test requirement

After step 2 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the UE CAPABILITY ENQUIRY message as per the specific message contents.

8.1.5.7 UE Capability Information / Audit of UE Capabilities

8.1.5.7.1 Definition

8.1.5.7.2 Conformance requirement

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

…

1> if the UE only supports HS-DSCH but not E-DCH:

2> include the IE "UE capability indication" and set it to the "HS-DSCH" value.

1> if the UE supports HS-DSCH and E-DCH:

2> include the IE "UE capability indication" and set it to the "HS-DSCH+E-DCH" value.

1> if, according to [4], the High-mobility state is applicable and it has been detected by the UE:

2> include the IE "UE Mobility State Indicator" and set it to the "High-MobilityDetected" value.

…

1> if the UE supports MAC-ehs:

2> include the IE "MAC-ehs support" and set it to TRUE.

1> if the UE supports HS-DSCH reception in CELL_FACH state:

2> include the IE "HS-PDSCH in CELL_FACH" and set it to TRUE.

1> if the UE supports Enhanced Uplink in CELL_FACH state and Idle mode:

2> include the IE "Support of common E-DCH" and set it to TRUE.

NOTE: In 1.28 Mcps TDD, UE supporting HS-DSCH reception in CELL_FACH state always supports Enhanced Uplink in CELL_FACH state and Idle mode, and vice versa.

1> if the UE supports MAC-i/is:

2> include the IE "Support of MAC-i/is" and set it to TRUE.

1> if the UE supports E-UTRA:

2> if the variable EUTRA_FREQUENCY_INFO_LIST contains no E-UTRA frequencies:

3> include the IE "Pre-Redirection info";

3> if the UE supports E-UTRA FDD:

4> set the IE "Support of E-UTRA FDD" to TRUE.

3> if the UE supports E-UTRA TDD:

4> set the IE "Support of E-UTRA TDD" to TRUE.

2> if the UE supports any of the bands that the E-UTRA frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:

3> include the IE "Pre-Redirection info";

3> if the UE supports any of the bands that the E-UTRA FDD frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:

4> set the IE "Support of E-UTRA FDD" to TRUE.

3> if the UE supports any of the bands that the E-UTRA TDD frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:

4> set the IE "Support of E-UTRA TDD" to TRUE.

1> if the UE supports dual cell operation on adjacent frequencies

2> include the IE "Multi cell support" and set it to TRUE.

1> if the UE supports CS voice over HSPA

2> include the IE "Support for CS Voice over HSPA" and set it to TRUE.

The UE shall not include the IE "UE Specific Behaviour Information 1 idle".

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

…

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per subclause 8.6.3.3, with the contents set as specified below:

2> …

2> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE radio access capability" and IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

2> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE system specific capability";

…

The UE shall initiate the UE capability update procedure in the following situations:

1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN;

…

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall:

1> include the IE "RRC transaction identifier"; and

1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> for the UE capabilities defined prior to REL-6:

2> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

2> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

2> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and

2> include this in IE "UE system specific capability".

1> for the UE capabilities defined in REL-6 or later:

2> include the information elements associated with the capabilities included in the variable UE_CAPABILITY_REQUESTED and the variable UE_CAPABILITY_TRANSFERRED.

…

If the UE is MAC-ehs or dual cell capable, the UE shall signal a value in the "HS-DSCH physical layer category extension" IE.

If the UE signals an "HS-DSCH physical layer category extension" of 13, 15, 17 or 19, it shall signal an "HS-DSCH physical layer category" of 9.

If the UE signals an "HS-DSCH physical layer category extension" of 14, 16, 18 or 20, it shall signal an "HS-DSCH physical layer category" of 10.

If the UE is dual cell capable, the UE shall signal a value in the "HS-DSCH physical layer category extension 2" IE.

If the UE signals an "HS-DSCH physical layer category extension 2" of 21, it shall signal an "HS-DSCH physical layer category extension" of 9, 10, 13, 14, 15, 16, 17 or 18.

If the UE signals an "HS-DSCH physical layer category extension 2" of 22, it shall signal an "HS-DSCH physical layer category extension" of 10, 14, 16 or 18.

If the UE signals an "HS-DSCH physical layer category extension 2" of 23, it shall signal an "HS-DSCH physical layer category extension" of 13, 14, 17, 18, 19 or 20.

If the UE signals an "HS-DSCH physical layer category extension 2" of 24, it shall signal an "HS-DSCH physical layer category extension" of 14, 18 or 20.

The UE shall use the "Total number of soft channel bits" (defined in Table 5.1a of [35]) for the category it has signalled, as follows:

1> If MAC-hs is configured, the UE uses the category it has signalled in the IE "HS-DSCH physical layer category";

1> If MAC-ehs is configured without dual cell operation, the UE uses the category it has signalled in the IE "HS-DSCH physical layer category extension";

1> If dual cell operation is configured, the UE uses the category it has signalled in the IE "HS-DSCH physical layer category extension 2".

Reference

3GPP TS 25.331 clauses 8.1.3.3, 8.1.3.6, 8.1.6.2

8.1.5.7.3 Test purpose

To check that the entire UE capabilities the UE reported in RRC CONNECTION REQUEST, RRC CONNECTION SETUP COMPLETE and UE CAPABILITY INFORMATION messages are compatible with the ICS statements in 3GPP TS 34.123-2[3], TS 36.523-2[46], TS 51.010-2[45] and with IXIT statements in TS 34.123-3[12] and TS 36.523-3[47].

8.1.5.7.4 Method of test

Initial Condition

System Simulator: 1 cell – Cell 1 is UTRAN.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by attempting to make an outgoing call. SS then transmits a RRC CONNECTION SETUP message containing an IE "Initial UE Identity" that matches the IE "Initial UE Identity". SS then waits for the UE to transmit an RRC CONNECTION SETUP COMPLETE message on the DCCH. The SS transmits a UE CAPABILITY ENQUIRY message. The UE shall respond with a UE CAPABILITY INFORMATION message on the uplink DCCH that includes the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST (CCCH)
2			RRC CONNECTION SETUP
3			RRC CONNECTION SETUP COMPLETE	See specific message contents
4			UE CAPABILITY ENQUIRY	See specific message contents
5			UE CAPABILITY INFORMATION	See specific message contents
6			UE CAPABILITY INFORMATION CONFIRM	Use default message.

Step 2 is release-branched (R99, Rel-5, Rel-6, Rel-7, Rel-8, Rel-9, Rel-10, Rel-11, Rel-12).

Specific Message Contents

RRC CONNECTION REQUEST (Step 1) (FDD)

Information Element	Value/remark	Version
Message Type
Predefined configuration status information	Not checked	Rel-5
Initial UE identity
– CHOICE UE id type
– TMSI and LAI (GSM-MAP)	Set to the UE’s TMSI and LAI.
Establishment cause	To be checked against requirement if specified
Protocol error indicator	FALSE
UE Specific Behaviour Information 1 idle	Not present
UE capability indication	To be checked against ICS statements pc_HSDPA and pc_HSUPA	Rel-6
MBMS Selected Services	Not present	Rel-6
Support for F-DPCH	To be checked against ICS statements pc_FDPCH	Rel-6
UE Mobility State Indicator	Not Present	Rel-7
Support for Enhanced F-DPCH	To be checked against ICS statements pc_EnhancedF_DPCH	Rel-7
HS-PDSCH in CELL_FACH	To be checked against ICS statements pc_HS_FACH	Rel-7
MAC-ehs support	To be checked against ICS statements pc_MAC_ehs	Rel-7
DPCCH Discontinuous Transmission support	To be checked against ICS statements pc_UL_DTX	Rel-7
Support of common E-DCH	To be checked against ICS statements pc_HS_RACH_EDCH	Rel-8
Multi cell support	To be checked against ICS statements pc_DualCell	Rel-8
Dual cell MIMO support	To be checked against ICS statements pc_DualCellMIMO	Rel-9
More than two cell support or MIMO mode with four transmit antennas support	To be checked against ICS statements pc_MultiCell, pc_ThreeCellMIMO, pc_FourCellMIMO, pc_ThreeCell, pc_FourCell, pc_SB_SF_DC, pc_SB_DF_3C, pc_DB_DF_3C	Rel-10
Pre-redirection info	To be checked against ICS statements in 36.523-2 pc_eFDD / pc_eTDD	Rel-8
Support of MAC-i/is	To be checked against ICS statements pc_MAC_iis	Rel-8
Support of SPS operation	TDD not checked	Rel-8
Support for CS Voice over HSPA	To be checked against ICS statements pc_CSVoHS	Rel-7
System Information Container Stored Indicator	Not checked	Rel-9
Support of the first Frequency Band	Not checked	Rel-10
Support of the second Frequency Band	Not checked	Rel-10
CSFB Indication	Not present
Measured results on RACH	Not checked
Access stratum release indicator	Value used for test case execution	Rel-4

RRC CONNECTION SETUP COMPLETE (Step 3) (FDD)

Information Element	Value/remark	Version
Message Type
RRC transaction identifier	The value of this IE is checked to see that it matches the value of the same IE transmitted in the downlink RRC CONNECTION SETUP message.
START list	This IE is checked to see if it is present.
UE radio access capability	See detail content below
UE radio access capability extension	See detail content below	Rel-5
UE system specific capability
>Inter-RAT UE radio access capability	See detail content below
Deferred measurement control reading	Not checked	Rel-7
Logged Meas Available	Not checked	Rel-10
ANR Logging Results Available	Not checked	Rel-10
Connection Establishment Failure Info Available	Not checked	Rel-11

UE CAPABILITY ENQUIRY (Step 4) (FDD)

Use the UE CAPABILITY ENQUIRY message as defined in (TS 34.108) Clause 9, with the following exceptions:

Information Element	Value/remark
Capability update requirement
– UE radio access FDD capability update requirement	TRUE
– UE radio access 3.84 Mcps TDD capability update requirement	FALSE
– UE radio access 7.68 Mcps TDD capability update requirement	FALSE
– UE radio access 1.28 Mcps TDD capability update requirement	FALSE
– System specific capability update requirement list – Requested E-UTRA Frequency Band list	GSM, E-UTRA Not present

UE CAPABILITY INFORMATION (Step 5) (FDD)

Check to see if the same message type found in (TS 34.108) Clause 9 is received, with the following exceptions:

Information Element	Value/remark
UE_RadioAccessCapability	See detail content below
UE radio access capability extension	See detail content below
UE system specific capability	See detail content below
>InterRAT_UE_RadioAccessCapability	See detail content below

UE radio access capability content (Step 3 and 5) (FDD)

Information Element	Value/remark	Version
Access stratum release indicator	Shall be the same value as in RRC CONNECTION REQUEST received in step 1.	Rel-4
DL capability with simultaneous HS-DSCH configuration	To be checked against ICS statements pc_CapabilityWithSimultaneousHS_DSCHConfig	Rel-5
PDCP capability
> Support for lossless SRNS relocation	To be checked against ICS statements pc_LosslessSRNS_Reloc
> Support for lossless DL RLC PDU size change	Not checked	Rel-5
> Support for RFC2507	To be checked against ICS statements pc_RFC2507
> Max HC context space	To be checked against ICS statements pc_MaxHcContextSpace_r5_ext
> Support for RFC 3095	To be checked against ICS statements pc_RFC3095	Rel-4
>> Maximum number of ROHC context sessions	To be checked against IXIT statements px_MaxNumberROHC_ContextSessions	Rel-4
>>Reverse decompression depth	Not checked	Rel-4
>>Support for RFC 3095 context relocation	To be checked against ICS statements pc_SupportForRfc3095ContextRelocation	Rel-5
> Support for CS Voice over HSPA	To be checked against ICS statements pc_CSVoHS	Rel-7
RLC capability	To be checked against ICS/IXIT statements px_TotalRLC_AM_BufferSize px_MaxRLC_WindowSize px_MaxAM_EntityNumberRLC_Cap
Transport channel capability	To be checked against ICS/IXIT statements px_DL_MaxTB_Bits px_DL_MaxCC_TB_Bits pc_DL_TC px_DL_MaxTrCHs px_DL_MaxCCTrCH px_DL_MaxTTI_TB px_DL_MaxTFS px_DL_MaxTF px_UL_MaxTB_Bits px_UL_MaxCC_TB_Bits pc_UL_TC px_UL_MaxTrCHs px_UL_MaxTTI_TB px_UL_MaxTFS px_UL_MaxTF
RF capability FDD
> UE power class	To be checked against ICS statements pc_UE_PowerClass1, pc_UE_PowerClass2, pc_UE_PowerClass3, pc_UE_PowerClass4
> Tx/Rx frequency separation > Support of Multiple Frequency Band Indicators	default TxRx separation Not checked	Rel-10
RF capability TDD	TDD Not checked	Rel-4
RF capability TDD 1.28 Mcps	TDD Not checked	Rel-4
Physical channel capability
> FDD downlink physical channel capability
>>Max no DPCH codes	To be checked against IXIT statements px_MaxNoDPCH_PDSCH_Codes
>>Max no physical channel bits received	To be checked against IXIT statements px_MaxNoPhysChBitsReceived
>>Support for SF 512 and 80 ms TTI for DPCH	To be checked against ICS statements pc_SupportForSF_512
>>Support for DCH Enhancements	To be checked against pc_DCH_Enhancement_BASIC and pc_DCH_Enhancement_FULL	Rel-12
>>Simultaneous support for DCH Enhancements and Compressed Mode operation	Not checked	Rel-12
>>Simultaneous support for DCH Enhancements and DPCCH Discontinuous Transmission	Not checked	Rel-12
>>Support of Enhanced Serving Cell Change for Event 1c	Not checked	Rel-12
>>Support of DPCCH2	Not checked	Rel-12
>>CHOICE Support of HS-PDSCH
>>>Supported	To be checked against ICS statements pc_HSDPA	Rel-5
>>>>HS-DSCH physical layer category	To be checked against ICS statements pc_HSDSCH_UE_Category	Rel-5
>>>>HS-DSCH physical layer category extension	To be checked against ICS statements pc_HSDSCH_UE_Category_Extension pc_MAC_ehs	Rel-7
>>>>HS-DSCH physical layer category extension 2	To be checked against ICS statements pc_HSDSCH_UE_Category_Extension2 pc_DualCell pc_SB_SF_DC	Rel-8
>>>>HS-DSCH physical layer category extension 3	To be checked against ICS statements pc_HSDSCH_UE_Category_Extension3	Rel-9
>>>HS-DSCH physical layer category extension 4	To be checked against ICS statements pc_HSDSCH_UE_Category_Extension4 pc_SB_DF_3C pc_DB_DF_3C	Rel-10
>>>HS-DSCH physical layer category extension 5	To be checked against ICS statements pc_HSDSCH_UE_Category_Extension5	Rel-10
>>>HS-DSCH physical layer category extension 6	Not checked	Rel-11
>>>HS-DSCH physical layer category extension 7	Not checked	Rel-11
>>>HS-DSCH physical layer category extension 8	Not checked	Rel-11
>>>HS-SCCHless HS-DSCH operation support	To be checked against ICS statements pc_HS_SCCH_less	Rel-7
>>>Enhanced F-DPCH support	To be checked against ICS statements pc_EnhancedF_DPCH	Rel-7
>>>HS-PDSCH in CELL_FACH	To be checked against ICS statements pc_HS_FACH	Rel-7
>>>HS-PDSCH in CELL_PCH and URA_PCH	To be checked against ICS statements pc_HS_PCH	Rel-7
>>>Target Cell Pre-Configuration	To be checked against ICS statements pc_TargetCell_PreConf_HSDSCH	Rel-8
>>>Support of HS-DSCH DRX operation	To be checked against ICS statements pc_HS_FACH_DRX	Rel-8
>>>Support of MIMO only with single stream restriction	Not checked	Rel-9
>>> Non-contiguous multi-cell with MIMO	Not checked	Rel-11
>>>Support of MIMO mode with four transmit antennas only with dual stream restriction	Not checked	Rel-11
>>>Support of NodeB triggered HS-DPCCH transmission	Not checked	Rel-11
>>>Support of HS-DSCH DRX operation with second DRX cycle	pc_HS_FACH_DRX_2ndDRXcycle	Rel-11
>>DRX enhancements	Not checked	Rel-12
>>HS-DPCCH overhead reduction	Not checked	Rel-12
>3.84 Mcps TDD downlink physical channel capability	TDD Not checked	Rel-5
>7.68 Mcps TDD downlink physical channel capability	TDD Not checked	Rel-7
>1.28 Mcps TDD downlink physical channel capability	TDD Not checked	Rel-4
> Uplink physical channel capability information elements
>> FDD uplink physical channel capability
>>> Maximum number of DPDCH bits transmitted per 10 ms	To be checked against IXIT statements px_MaxNoDPDCH_BitsTransmitted
>>>Support of cell reselection indication reporting	Not checked	Rel-12
>>>Support of Serving E-DCH cell decoupling	Not checked	Rel-12
>>>Support of Radio Links without DPCH/F-DPCH	Not checked	Rel-12
>>>CHOICE Support of E-DCH	To be checked against ICS statements pc_HSUPA	Rel-6
>>>>Supported		Rel-6
>>>>>E-DCH physical layer category	To be checked against ICS statements pc_EDCH_UE_Category	Rel-6
>>>>>E-DCH physical layer category extension	To be checked against ICS statements pc_UL_16QAM	Rel-7
>>>>>E-DCH physical layer category extension 2	To be checked against ICS statements pc_EDCH_UE_Category_Extension2	Rel-9
>>>>>E-DCH physical layer category extension 3	Not checked	Rel-11
>>>>>DPCCH Discontinuous Transmission support	To be checked against ICS statements pc_UL_DTX	Rel-7
>>>>Slot Format #4 support	To be checked against ICS statements pc_SlotFormat4	Rel-7
>>>Access Groups based access control	Not checked	Rel-12
>>>Enhanced TTI switching	Not checked	Rel-12
>>>Implicit Grant handling	Not checked	Rel-12
>>>DTX enhancements	Not checked	Rel-12
>>3.84 Mcps TDD uplink physical channel capability	TDD Not checked	Rel-4
>>7.68 Mcps TDD uplink physical channel capability	TDD Not checked	Rel-7
>>1.28 Mcps TDD uplink physical channel capability	TDD Not checked	Rel-4
UE multi-mode/multi-RAT capability
> Support of GSM	To be checked against ICS statements pc_GERAN
> Support of multi-carrier	To be checked against ICS statements pc_SupportOfMultiCarrier
> Multi-mode capability	Fdd
> Support of UTRAN to GERAN NACC	To be checked against ICS statements pc_SupportOfUTRAN_ToGERAN_NACC	Rel-5
> Support of Handover to GAN	To be checked against ICS statements in 51.010-2 pc_UTRAN_TO_GAN_CS_Handover	Rel-6
> Support of Inter-RAT PS handover	To be checked against ICS statements in 51.010-2 pc_PS_Handover	Rel-6
> Support of PS Handover to GAN	To be checked against ICS statements pc_PS_Handover_To_GAN	Rel-7
> Support of E-UTRA FDD	To be checked against ICS statements in 36.523-2 pc_eFDD	Rel-8
> Support of Inter-RAT PS Handover to E-UTRA FDD	To be checked against ICS statements pc_HO_from_UTRA_to_eFDD in 36.523-2	Rel-8
> Support of E-UTRA TDD	To be checked against ICS statements in 36.523-2 pc_eTDD	Rel-8
> Support of Inter-RAT PS Handover to E-UTRA TDD	To be checked against ICS statements pc_HO_from_UTRA_to_eTDD in 36.523-2
> EUTRA Feature Group Indicators	To be checked against ICS statements pc_PCH_StatesToEUTRA_IdleReselection pc_EUTRAN_MeasurementInConnected	Rel-8
> Support of E-UTRA Multiple Frequency Band Indicators	Not checked	Rel-10
> Support of E-UTRA FDD measurements and reporting in CELL_FACH	Not checked	Rel-11
> Support of E-UTRA TDD measurements and reporting in CELL_FACH	TDD Not checked	Rel-11
> Support of RAN-assisted WLAN interworking based on RAN rules	To be checked against ICS statements pc_UTRAN_WLAN_offload	Rel-12
> Support of RAN-assisted WLAN interworking based on ANDSF policies	To be checked against ICS statements pc_ANDSF_RAN_Rules_Co	Rel-12
Security capability	To be checked against ICS statements pc_UEA2_UIA2
UE positioning capability	To be checked against ICS/IXIT statements pc_UE_PositioningStandaloneLocMethodsSup pc_UE_PositioningBasedOTDOA_Sup px_UE_PositioningNetworkAssistedGPS_Sup pc_UE_PositioningGPS_TimingOfCellFramesSup pc_UE_PositioningIPDL_Sup
Measurement capability
> Inter-frequency detected set measurements	Not checked	Rel-10
> Cells excluded from detected set measurements	Not checked	Rel-11
> Wideband RSRQ FDD measurements	Not checked	Rel-11
> Event 2g reporting on a configured secondary downlink frequency	Not checked	Rel-12
> Enhanced UPH reporting	Not checked	Rel-12
> Increased UE carrier monitoring UTRA	Not checked	Rel-12
> Increased UE carrier monitoring E-UTRA	Not checked	Rel-12
> Extended RSRQ lower value range	Not checked	Rel-12
> RSRQ measurement on all symbols	Not checked	Rel-12
> Wideband RSRQ TDD measurements	Not checked	Rel-11
> Need for downlink compressed mode
>> FDD measurements	Checked it is present pc_InterFreq_DL_CompressedModeRequired
>>3.84 Mcps TDD measurements	TDD Not checked	Rel-4
>>7.68 Mcps TDD measurements	TDD Not checked	Rel-7
>>1.28 Mcps TDD measurements	TDD Not checked	Rel-4
>> GSM measurements
>>>GSM 900	To be checked against ICS statements pc_DL_CompressedModeRequiredForGSM_900P
>>>DCS 1800	To be checked against ICS statements pc_DL_CompressedModeRequiredForDCS_1800
>>>GSM 1900	To be checked against ICS statements pc_DL_CompressedModeRequiredForGSM_1900
>>Multi-carrier measurement	To be checked against ICS statements pc_DL_CompressedModeRequiredForMultiCarrier_Meas
>>Adjacent Frequency measurements without compressed mode	To be checked against ICS statements pc_DL_CompressedModeRequiredForAdjacentCarriers	Rel-8
>>Inter-band Frequency measurements without compressed mode	Not checked	Rel-9
>>Enhanced inter-frequency measurements without compressed mode	Not checked	Rel-10
>> Frequency specific compressed mode	Not checked	Rel-10
>> Inter-frequency measurements on configured carriers without compressed mode	Not checked	Rel-11
>Need for uplink compressed mode
>>FDD measurements	Checked it is present pc_InterFreq_UL_CompressedModeRequired
>>3.84 Mcps TDD measurements	TDD Not checked	Rel-4
>>7.68 Mcps TDD measurements	TDD Not checked	Rel-7
>>1.28 Mcps TDD measurements	TDD Not checked	Rel-4
>> GSM measurements
>>>GSM 900	To be checked against ICS statements pc_UL_CompressedModeRequiredForGSM_900P
>>>DCS 1800	To be checked against ICS statements pc_UL_CompressedModeRequiredForDCS_1800
>>>GSM 1900	To be checked against ICS statements pc_UL_CompressedModeRequiredForGSM_1900
>> Multi-carrier measurement	To be checked against ICS statements pc_UL_CompressedModeRequiredForMultiCarrier_Meas
Measurement capability TDD	TDD Not checked	Rel-8
Device type	To be checked against ICS statements pc_DeviceType	Rel-6
Support for System Information Block type 11bis	To be checked against ICS statements pc_SupportSIB11bis	Rel-6
Support for F-DPCH	To be checked against ICS statements pc_FDPCH	Rel-6
MAC-ehs support	To be checked against ICS statements pc_MAC_ehs	Rel-7
UE specific capability Information LCR TDD	TDD Not checked	Rel-7
Support for E-DPCCH Power Boosting	Not checked	Rel-7
Support of common E-DCH	To be checked against ICS statements pc_HS_RACH_EDCH	Rel-8
Support of MAC-i/is	To be checked against ICS statements pc_MAC_iis	Rel-8
Support of Common E-RGCH based interference control	Not checked	Rel-11
Support of Fallback to R99 PRACH	Not checked	REL-11
Support of Concurrent deployment	Not checked	REL-11
Support of TTI alignment and Per HARQ process	Not checked	REL-11
Support of SPS operation	TDD Not checked	Rel-8
Support of Control Channel DRX operation	TDD Not checked	Rel-8
Support of CSG	To be checked against ICS statements pc_CSG	Rel-8
Support for Two DRX schemes in URA_PCH and CELL_PCH	To be checked against ICS statements pc_TwoDRX_InPCH_States	Rel-7
Support for E-DPDCH power interpolation formula	Not checked	Rel-7
Support for absolute priority based cell re-selection in UTRAN	To be checked against ICS statements pc_AbsolutePriorityReselection	Rel-8
Support of MU-MIMO	Not checked	Rel-10
Radio Access Capability Band Combination List		Rel-9
>Band Combination	To be checked against ICS statements pc_DB_DC_HSDPA_Band1_8 pc_DB_DC_HSDPA_Band2_4 pc_DB_DC_HSDPA_Band1_5 pc_DB_DC_HSDPA_Band1_11 pc_DB_DC_HSDPA_Band2_5	Rel-9
>Supported Carrier Combination
>>Carrier Combination (1,2)	pc_4C_DBCC12	Rel-10
>>Carrier Combination (2,1)	pc_DB_4C_CC21	Rel-10
>>Carrier Combination (1,3)	Not checked	Rel-10
>>Carrier Combination (3,1)	pc_4C_DBCC31	Rel-10
>>Carrier Combination (2,2)	pc_4C_DBCC22	Rel-10
>>Carrier Combination (1,4)	Not checked	Rel-11
>>Carrier Combination (4,1)	Not checked	Rel-11
>>Carrier Combination (1,5)	Not checked	Rel-11
>>Carrier Combination (5,1)	Not checked	Rel-11
>>Carrier Combination (1,6)	Not checked	Rel-11
>>Carrier Combination (6,1)	Not checked	Rel-11
>>Carrier Combination (1,7)	Not checked	Rel-11
>>Carrier Combination (7,1)	Not checked	Rel-11
>>Carrier Combination (2,3)	Not checked	Rel-11
>>Carrier Combination (3,2)	Not checked	Rel-11
>>Carrier Combination (2,4)	Not checked	Rel-11
>>Carrier Combination (4,2)	Not checked	Rel-11
>>Carrier Combination (2,5)	Not checked	Rel-11
>>Carrier Combination (5,2)	Not checked	Rel-11
>>Carrier Combination (2,6)	Not checked	Rel-11
>>Carrier Combination (6,2)	Not checked	Rel-11
>>Carrier Combination (3,3)	Not checked	Rel-11
>>Carrier Combination (3,4)	Not checked	Rel-11
>>Carrier Combination (4,3)	Not checked	Rel-11
>>Carrier Combination (4,4)	Not checked	Rel-11
>>Carrier Combination (3,5)	Not checked	Rel-11
>>Carrier Combination (5,3)	Not checked	Rel-11
>Supported Multiflow Combination	Not checked	Rel-11
>>Number of cells in band A	Not checked	Rel-11
>>Number of frequencies in band A	Not checked	Rel-11
>>Number of cells in band B	Not checked	Rel-11
>>Number of frequencies in band B	Not checked	Rel-11
Support of multi-cell configuration in inter-RAT handover	Not checked	Rel-11
Support of TX Diversity on DL Control Channels by MIMO Capable UE when MIMO operation is active	Not checked	Rel-7
Support of enhanced TS0	TDD Not checked	Rel-9
Support for cell-specific Tx diversity configuration for dual-cell operation	Not checked	Rel-8
CSG proximity indication capability		Rel-9
> Support of intra-frequency proximity indication	To be checked against ICS statements pc_Indicating_CSG_Proximity_IntraF	Rel-9
> Support of inter-frequency proximity indication	To be checked against ICS statements pc_Indicating_CSG_Proximity_InterF	Rel-9
> Support of E-UTRA proximity indication	Not checked	Rel-9
Neighbour Cell SI acquisition capability		Rel-9
> Support of intra-frequency SI acquisition for HO	To be checked against ICS statements pc_Acquiring_IntraF_SI	Rel-9
> Support of inter-frequency SI acquisition for HO	To be checked against ICS statements pc_Acquiring_InterF_SI	Rel-9
> Support of E-UTRA SI acquisition for HO	Not checked	Rel-9
Extended measurements Support	Not checked	Rel-10
Support for dual cell with MIMO operation in different bands	Not checked	Rel-10
UE based network performance measurements parameters		Rel-10
>Support of Logged Measurements Idle PCH	pc_Loggedmeasurements_idle_PCH	Rel-10
Support of UTRAN ANR	To be checked against ICS statements pc_UTRAN ANR	Rel-10
IMS Voice capability	Not checked	REL-9
Multiflow capability		REL-11
> Support for Multiflow with MIMO operation in different bands	Not checked	Rel-11
> Longer HARQ processing time	Not checked	Rel-11
Support of MAC-ehs window size extension	TDD Not checked	REL-9
Support of UM RLC re-establishment via reconfiguration	Not checked	Rel-10
Support of HS-DPCCH power offset extension	Not checked	Rel-11
Support of STTD on DL Control Channels when Multiflow operation is active	Not checked	Rel-11
Support of F-TPICH feedback from the Multiflow assisting cell	Not checked	Rel-12
Support of DSAC and PPAC update in CELL_DCH	Not checked	Rel-12

UE radio access capability extension (Step 3 and 5) (FDD)

Information Element	Value/remark	Version
Frequency band specific capability list
>Frequency band	To be checked against ICS statements pc_BandXX_Supp (indicating the coded supporting bands) It is not checked against ICS statement pc_Band6_Supp (indicating the coded supporting band VI)
>Frequency band 2	To be checked against ICS statements pc_BandXX_Supp (indicating the coded supporting bands)
>Frequency band 3	To be checked against ICS statements pc_BandXX_Supp (indicating the coded supporting bands)	Rel-10
>RF capability FDD extension
>> UE power class	To be checked against ICS statements pc_UE_PowerClass1, pc_UE_PowerClass2, pc_UE_PowerClass3, pc_UE_PowerClass4
>> Tx/Rx frequency separation	default TxRx separation
>Measurement capability extension
>> FDD measurements
>>>FDD Frequency band	To be checked against ICS statements pc_BandXX_Supp (indicating the coded supporting bands) It is not checked against ICS statement pc_Band6_Supp (indicating the coded supporting band VI)
>>>FDD Frequency band 2	To be checked against ICS statements pc_BandXX_Supp (indicating the coded supporting bands)
>>>FDD Frequency band 3	To be checked against ICS statements pc_BandXX_Supp (indicating the coded supporting bands)	Rel-10
>>>Need for DL compressed mode	Not checked
>>>Need for UL compressed mode	Not checked
>> TDD measurements	TDD Not checked
>> GSM measurements
>>>GSM Frequency band	To be checked against ICS statements in 51.010-2 [45] with the exception mentioned below pc_Type_GSM_450_Band pc_Type_GSM_480_Band pc_Type_GSM_850_Band If (pc_Type_GSM_P_Band is TRUE and pc_Type_GSM_E_Band is FALSE) GSM900P must be present in the list of supported GSM frequency bands ELSE the settings of pc_Type_GSM_P_Band and the presence of GSM900P is not checked against each other pc_Type_GSM_E_Band pc_Type_DCS_Band pc_Type_PCS_Band
>>>Need for DL compressed mode	Not checked
>>>Need for UL compressed mode	Not checked
>> Multi-carrier measurement
>>>Need for DL compressed mode	Not checked
>>>Need for UL compressed mode	Not checked
>> E-UTRA measurements		Rel-8
>>>E-UTRA Frequency band	For eBands<64 and if the UE needs to report E-UTRA measurement capability for less than 16 E-UTRA bands: to be checked against ICS statements in 36.523-2 [46] pc_eBandX_Supp else not checked	Rel-8
>>>Need for compressed mode	Checked it is present	Rel-8
>>E-UTRA measurements extension		Rel-11
>>>E-UTRA Frequency band extension	For eBands>64 and if the UE needs to report E-UTRA measurement capability for less than 16 E-UTRA bands: to be checked against ICS statements in 36.523-2 [46] pc_eBandX_Supp else not checked	Rel-11
>>E-UTRA measurements extension 1		Rel-11
>>>E-UTRA Frequency band extension 1	If the UE needs to report E-UTRA measurement capability for more than 16 E-UTRA bands: To be checked against ICS statements in 36.523-2 [46] pc_eBandX_Supp else not checked	Rel-11
>>>Need for compressed mode	Not checked	Rel-11
>Additional Secondary Cells	Not checked	Rel-10
>Additional Secondary Cells 2	Not checked	Rel-11
>Non-contiguous multi-cell		Rel-10
>>Aggregated cells	Not checked	Rel-10
>>Gap size	Not checked	Rel-10
>>Non-contiguous multi-cell Combination (2,2)	Not checked	Rel-10
>>Non-contiguous multi-cell Combination (3,1) (1,3)	Not checked	Rel-10
>Support of uplink closed loop transmit diversity	Not checked	Rel-11
>Support of uplink open loop transmit diversity	Not checked	Rel-11
>Multiflow per band capability	Not checked	Rel-11
>Support of Uplink MIMO	Not checked	Rel-11
>MIMO mode with four transmit antennas per band capability	Not checked	Rel-11
>Frequency specific compressed mode for non-contiguous operation	Not checked	Rel-11

Inter-RAT UE radio access capability (Step 3 and 5) (FDD)

Information Element	Value/remark	Version
CHOICE system
>GSM
>>Mobile Station Classmark 2	To be checked against ICS/IXIT statements px_MS_ClsmkRevLvl px_MS_ClsmkESIND pc_UMTS_GSM pc_MS_ClsmkPS_Cap pc_SS_Screening_Indicator pc_MS_ClsmkSM_Cap pc_MS_ClsmkVBS pc_MS_ClsmkVGCS pc_MS_ClsmkCM3 pc_MS_ClsmkLCSVA_Cap pc_MS_ClsmkUCS2 pc_MS_ClsmkSoLSA pc_MS_ClsmkCMSP pc_MS_ClsmkA5_3_CS
>>Mobile Station Classmark 3	To be checked against ICS statements pc_FDD pc_1xRTT pc_HRPD pc_eFDD pc_eTDD, pc_P_GSM_900_BAND pc_E_GSM_900_BAND pc_R_GSM_900_BAND pc_DCS_1800_BAND pc_PCS_1900_BAND pc_GSM_450_BAND pc_GSM_480_BAND pc_GSM_710_BAND pc_GSM_750_BAND pc_T_GSM_810_BAND pc_GSM_850_BAND pc_Feat_A54 pc_DTM_SingleSlotAllocation pc_EOTD_Assist pc_UeAssistedAgps pc_UeBasedAgps pc_Conv_GPS pc_EOTD_MS_Based pc_GERANFeaturePackage1 pc_GERANFeaturePackage2 pc_DTMEnhancedCap pc_8PSKPowerProfile1 pc_8PSKPowerProfile2 pc_8PSKPowerProfile3 pc_GMSKPowerProfile1 pc_GMSKPowerProfile2 pc_GMSKPowerProfile3 pc_EGPRS_8PSK_uplink pc_CipherModeSetCap pc_AddPositionCap pc_EUTRA_MeasReporting pc_PriorityBasedCellReselection pc_G_HSCSD_MultislotClass pc_ECSD_MultislotClass pc_SMS_Value pc_SM_Value pc_TypeDCSClass1 pc_TypeDCSClass2 pc_TypeDCSClass3 pc_TypeGSMClass2 pc_TypeGSMClass3 pc_TypeGSMClass4 pc_TypeGSMClass5 pc_DTM_Multislotclass5 pc_DTM_Multislotclass6 pc_DTM_Multislotclass9 pc_DTM_Multislotclass10 pc_DTM_Multislotclass11 pc_DTM_Multislotclass31 pc_DTM_Multislotclass32 pc_DTM_Multislotclass33 pc_DTM_Multislotclass36 pc_DTM_Multislotclass37 pc_DTM_Multislotclass38 pc_DTM_Multislotclass41 pc_DTM_Multislotclass42 pc_DTM_Multislotclass43 pc_DTM_Multislotclass44 pc_DTM_EGPRS_Multislotclass5 pc_DTM_EGPRS_Multislotclass9 pc_DTM_EGPRS_Multislotclass11 pc_DTM_EGPRS_MultislotClass31 pc_DTM_EGPRS_MultislotClass32 pc_DTM_EGPRS_MultislotClass33 pc_DTM_EGPRS_MultislotClass36 pc_DTM_EGPRS_MultislotClass37 pc_DTM_EGPRS_MultislotClass38 pc_DTM_EGPRS_MultislotClass41 pc_DTM_EGPRS_MultislotClass42 pc_DTM_EGPRS_MultislotClass43 pc_DTM_EGPRS_MultislotClass44 px_ExtDTM_EGPRS_MultiSlotClass px_HighMultiSlotCap pc_TypeGSMClassE1 pc_TypeGSM850ClassE1 pc_TypeGSMClassE2 pc_TypeGSM850ClassE2 pc_TypeGSMClassE3 pc_TypeGSM850ClassE3 pc_TypeDCSClassE1 pc_TypePCSClassE1 pc_TypeDCSClassE2 pc_TypePCSClassE2 pc_TypeDCSClassE3 pc_TypePCSClassE3 pc_DARP_Phase1 pc_DARP_Phase2 pc_ExtMeasCap pc_MS_ClsmkUCS2 pc_RepeatedFACCH pc_RepeatedSACCH pc_TypeGSM400Class2 pc_TypeGSM400Class3 pc_TypeGSM400Class4 pc_TypeGSM400Class5 pc_TypeTGSM400Class2 pc_TypeTGSM400Class3 pc_TypeTGSM400Class4 pc_TypeTGSM400Class5 pc_TypeGSM710Class2 pc_TypeGSM710Class3 pc_TypeGSM710Class4 pc_TypeGSM710Class5 pc_TypeGSM750Class2 pc_TypeGSM750Class3 pc_TypeGSM750Class4 pc_TypeGSM750Class5 pc_TypeTGSM810Class2 pc_TypeTGSM810Class3 pc_TypeTGSM810Class4 pc_TypeTGSM810Class5 pc_TypeGSM850Class2 pc_TypeGSM850Class3 pc_TypeGSM850Class4 pc_TypeGSM850Class5 pc_TypePCSClass1 pc_TypePCSClass2 pc_TypePCSClass3 pc_T_GSM_380_BAND pc_T_GSM_410_BAND
>>MS Radio Access Capability	See detail content below	Rel-6
>GERAN Iu	Not checked	Rel-5
>cdma2000	CDMA Not checked
>E-UTRA		Rel-8
>>UE E-UTRA Capability
>>> accessStratumRelease	Should not be having the value less than Rel-8.
>>> ue-Category	To be checked against IXIT statements in 36.523-3 px_eUE_Category_Type
>>> pdcp-Parameters
>>>> supportedROHC-Profiles	Checked it is present
>>>> maxNumberROHC-ContextSessions	Checked it is present
>>> phyLayerParameters
>>>> ul-AntennaSelectionSupported	Checked it is present
>>>> ue-SpecificRefSigsSupported	Checked it is present
>>> rf-Parameters
>>>> supportedEUTRA-BandList
>>>>> eutra-Band	To be checked against ICS statements in 36.523-2 pc_eBandXX_Supp (indicating the coded supporting bands)
>>>>> halfDuplex	Checked it is present
>>> measParameters
>>>> eutra-BandList
>>>>> interFreqBandList	Checked it is present
>>>>> interRAT-BandList	Not checked
>>> featureGroupIndicators	To be checked against ICS statements in 36.523-2 pc_FeatrGrp_XX_F
>>> interRAT-Parameters
>>>> utraFDD	To be checked against ICS statements pc_FDD pc_BandXX (indicating the coded supporting bands)
>>>> utraTDD128	TDD Not checked
>>>> utraTDD384	TDD Not checked
>>>> utraTDD768	TDD Not checked
>>>> geran	To be checked against ICS statements pc_UMTS_GSM
>>>> cdma2000-HRPD	CDMA Not checked
>>>> cdma2000-1xRTT	CDMA Not checked
>>> nonCriticalExtension	Not checked	Rel-9

MS Radio Access Capability (Step 3 and 5) (FDD)

Information Element	Value/remark	Version
if Access Technology Type exclude 1111:	Value not checked
Access Capabilities:
> Length	Not checked
> RF Power Capability	px_GMSK_PowerCap
> A5 Bits:
>> A5/1	’1’B
>> A5/2	The MS shall set this bit to ‘0’.
>> A5/3	pc_MS_ClsmkA5_3_CS
>> A5/4	pc_Feat_A54
>> A5/5	not checked does not exist
>> A5/6	not checked does not exist
>> A5/7	not checked does not exist
> ESIND	px_MS_ClsmkESIND
> PS	pc_MS_ClsmkPS_Cap
> VGCS	pc_MS_ClsmkVGCS
> VBS	pc_MS_ClsmkVBS
> MultiSlot Capability:
>> HSCSD Multislot Class	pc_G_HSCSD_MultislotClass
>> GPRS Multislot Class	px_GPRS_MultislotClass
>>> GPRS Extended Dynamic Allocation Capability	if (pc_Type_GPRS_Multislot_Class11, pc_Type_GPRS_Multislot_Class32, pc_Type_GPRS_Multislot_Class33, pc_Type_GPRS_Multislot_Class37, pc_Type_GPRS_Multislot_Class38, pc_Type_GPRS_Multislot_Class42, pc_Type_GPRS_Multislot_Class43 or pc_Type_GPRS_Multislot_Class44) then 1
>> SMS Value	pc_SMS_VALUE_SMS
>>> SM Value	pc_SMS_VALUE_SM
>> ECSD Multislot Class	pc_Type_ECSD_Multislot_Class
>> EGPRS Multislot Class	px_EGPRS_MultislotClass
>>> EGPRS Extended Dynamic Allocation Capability	if (pc_Type_EGPRS_Multislot_Class11, pc_Type_EGPRS_Multislot_Class32, pc_Type_EGPRS_Multislot_Class33, pc_Type_EGPRS_Multislot_Class37, pc_Type_EGPRS_Multislot_Class38, pc_Type_EGPRS_Multislot_Class42, pc_Type_EGPRS_Multislot_Class43 or pc_Type_EGPRS_Multislot_Class44) then 1
>> DTM GPRS Multislot Class	pc_DTM_GPRS_Multislot_Class_5, pc_DTM_GPRS_Multislot_Class_9 pc_DTM_GPRS_Multislot_Class_11
>>> Single Slot DTM	pc_DTM_GPRS_Singleslot_Allocation
>>> DTM EGPRS Multislot Class	pc_DTM_EGPRS_Multislot_Class_5, pc_DTM_EGPRS_Multislot_Class_9 pc_DTM_EGPRS_Multislot_Class_11
> 8PSK Power Capability	px_8PSK_PowerCap
> COMPACT Interference Measurement Capability	pc_COMPACT
> Revision Level Indicator	’1’B
> UMTS FDD Radio Access Technology Capability	’1’B
> UMTS 3.84 Mcps TDD Radio Access Technology Capability	Not checked
> CDMA 2000 Radio Access Technology Capability	CDMA not checked
> UMTS 1.28 Mcps TDD Radio Access Technology Capability	Not checked
> GERAN Feature Package 1	pc_GERANFeaturePackage1
> Extended DTM GPRS Multislot Class	pc_DTM_Multislotclass6, pc_DTM_Multislotclass9, pc_DTM_Multislotclass10, pc_DTM_Multislotclass31, pc_DTM_Multislotclass36, pc_DTM_Multislotclass41
>> Extended DTM EGPRS Multislot Class	px_ExtDTM_EGPRS_MultiSlotClass
> Modulation Based Multislot Class Support	pc_Type_EGPRS_8PSK_uplink
> High Multislot Capability	px_HighMultiSlotCap
> GMSK Multislot Power Profile	pc_GMSKPowerProfile1, pc_GMSKPowerProfile2, pc_GMSKPowerProfile3
> 8-PSK Multislot Power Profile	pc_8PSKPowerProfile1, pc_8PSKPowerProfile2, pc_8PSKPowerProfile3
> Multiple TBF Capability	pc_Multiple_TBF
> Downlink Advanced Receiver Performance	pc_DARP_Phase1, pc_DARP_Phase2
> Extended RLC/MAC Control Message Segmentation Capability	pc_Xtd_Ctrl_Message_Segmentation
> DTM Enhancements Capability	pc_DTMEnhancedCap
> DTM GPRS high Multi Slot Class	pc_DTM_Multislotclass31, pc_DTM_Multislotclass32, pc_DTM_Multislotclass33, pc_DTM_Multislotclass36, pc_DTM_Multislotclass37, pc_DTM_Multislotclass38, pc_DTM_Multislotclass41, pc_DTM_Multislotclass42, pc_DTM_Multislotclass43, pc_DTM_Multislotclass44
>> DTM EGPRS high Multi Slot Class	pc_DTM_EGPRS_Multislotclass31, pc_DTM_EGPRS_Multislotclass32, pc_DTM_EGPRS_Multislotclass33, pc_DTM_EGPRS_Multislotclass36, pc_DTM_EGPRS_Multislotclass37, pc_DTM_EGPRS_Multislotclass38, pc_DTM_EGPRS_Multislotclass41, pc_DTM_EGPRS_Multislotclass42, pc_DTM_EGPRS_Multislotclass43, pc_DTM_EGPRS_Multislotclass44
> PS Handover Capability	pc_PS_Handover
> DTM Handover Capability	Not checked
> Multislot Capability Reduction for Downlink Dual Carrier	px_Multislot_Capability_Reduction_for_Downlink_Dual_Carrier
>> Downlink Dual Carrier for DTM Capability	pc_Downlink_DualCarrier
> Flexible Timeslot Assignment	pc_Flexible_Timeslot
> GAN PS Handover Capability	Not checked
> RLC Non-persistent Mode	Not checked
> Reduced Latency Capability	pc_Latency_Reductions
> Uplink EGPRS2	Not checked
> Downlink EGPRS2	Not checked
> E-UTRA FDD support	pc_eFDD
> E-UTRA TDD support	pc_eTDD
> GERAN to E-UTRA support in GERAN packet transfer mode	px_GERAN_to_EUTRA_Support
> Priority-based reselection support	pc_Priority_Based_Cell_Reselection
> Enhanced Flexible Timeslot Assignment:
>> Alternative EFTA Multislot Class	Not checked
>> EFTA Multislot Capability Reduction for Downlink Dual Carrier	Not checked
> Indication of Upper Layer PDU Start Capability for RLC UM	pc_UpperLayer_PDU_Start_Ind
> EMST Capability	pc_EMST
>MTTI capability	pc_MTTI
>UTRA CSG Cells Reporting	Not checked
>E- UTRA CSG Cells Reporting	Not checked
>DTR Capability	Not checked
>EMSR Capability	Not checked
>Fast Downlink Frequency Switching Capability	Not checked
>TIGHTER Capability	Not checked
>FANR Capability	Not checked
>IPA Capability	Not checked
>GERAN Network Sharing Support	Not checked
>E-UTRA Wideband RSRQ Measurements Support	Not checked
>UTRA Multiple Frequency Band Indicators Support	Not checked
>E- UTRA Multiple Frequency Band Indicators Support	Not checked
> DLMC Capability	Not checked
> Extended TSC Set Capability Support	Not checked
if Access Technology Type equals 1111:	1111
Length
Additional Access Technologies:	Repeated Structure
> Access Technology Type	Value not checked
> GMSK Power Class	px_GMSK_PowerCap
> 8-PSK Power Class	px_8PSK_PowerCap

8.1.5.7.5 Test requirement

At step 5 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the UE CAPABILITY ENQUIRY message as per the specific message contents.

All ICS and IXIT parameters concerned shall be correctly set to those values which are reported by the UE so that the whole ICS / IXIT values can be used as the audit file of the UE entire capabilities.