4 Common requirements of test equipment

34.1083GPPCommon test environments for User Equipment (UE)Conformance testingRelease 15TS

Mobile conformance testing can be categorized into 3 distinct areas:

  • RF Conformance Testing.
  • EMC Conformance Testing.
  • Signalling Conformance Testing.

The test equipment required for each category of testing may or not be different, depending on the supplier of the test equipment. However, there will be some generic requirements of the test equipment that are essential for all three categories of test, and these are specified in this clause.

In addition, there will be requirements to test operation in multi-system configurations (e.g. UTRA plus GSM/DCS1800). However, these would not form a common test equipment requirement for the three test areas and are not considered in the present document.

4.1 General Functional Requirements

NOTE: This clause has been written such that it does not constrain the implementation of different architectures and designs of test equipment.

All test equipment used to perform conformance testing on a UE shall provide a platform suitable for testing UE’s that are either:

a) FDD Mode; or

b) TDD Mode; or

c) both FDD/TDD Modes.

All test equipment shall provide (for the mode(s) supported) the following minimum functionality.

– The capability of emulating a single UTRA cell with the appropriate channels to allow the UE to register on the cell.

– The capability to allow the UE to set up an RRC connection with the System Simulator, and to maintain the connection for the duration of the test.

– The capability (for the specific test):

– to select and support an appropriate Radio Bearer for the downlink;

– to set the appropriate downlink power levels;

– to set up and support the appropriate Radio Bearer for the uplink;

– to set and control the uplink power levels.

4.2 Minimum performance levels

4.2.1 Supported Cell Configuration

The System Simulator shall provide the capability to simulate a minimum number of cells (of the appropriate UTRA Mode) whose number and capabilities are governed by the test cases that need to be performed (test cases are defined in 3GPP TS 34.123-1 [1] (Signalling), 3GPP TS 34.121 [2] (RF-FDD) and 3GPP TS 34.122 [5] (RF-TDD)). For this purpose test cases can be split into two different categories: Tests that require only one cell and Tests that require several cells.

To perform test cases requiring one cell, the system simulator must provide a Cell offering the capabilities to perform all the test cases in this category.

To perform test cases requiring several cells, additional cells must be provided by the system simulator. The additional cells, however, need only provide a minimum set of capabilities so as to support the first cell in carrying out the multi‑cell test cases.

To perform test cases for MBMS in MBSFN mode the SS must provide simultaneous support for both the MBSFN cell(s) (TDD or FDD) directly applicable to the test cases and must also provide support for cells(s) on a unicast carrier providing other necessary services to the UE such as PLMN registration. The choice of supporting unicast carrier cell(s) may be TDD or FDD decided by the capabilities of the UE under test, and the choice may be independent of the mode (TDD or FDD) of the MBSFN cell(s).

The type and number of channels (especially physical channels) constitute an important set of capabilities for a cell. The following clauses list possible channels that may be supported by the SS. Each channel type, however, and the minimum number of channels needed are only mandatory if specific test cases require them.

The mapping between Logical and Transport channels is as described in 3GPP TS 25.301 [7]. Similarly the mapping between Transport channels and Physical channels is as described in 3GPP TS 25.211 [13] for the FDD mode, and 3GPP TS 25.221 [28] for the TDD mode. The reference measurement channels (mapping between Transport channels and Physical channels for DTCH/DCCH to be tested) are defined in 3GPP TS 34.121 [2] annex C for FDD and 3GPP TS 34.122 [5] annex C for TDD.

4.2.1.1 Supported Channels for FDD Mode

4.2.1.1.1 Logical channels

Logical channel

Minimum number

Comments

BCCH

1

CCCH

1

DCCH

4

2 for RRC testing, 2 for NAS testing

PCCH

1

DTCH

n <FFS>

Depending on SS’s support for RB service testing (See clause 14 of 3GPP TS 34.123-1 [1])
4.2.1.1.2 Transport channels

Transport channel

Minimum number

Comments

BCH

1

FACH

1

PCH

1

DCH

n <FFS>

DSCH

1

Release 99 and Release 4 only.

RACH

2

CPCH

1

Release 99 and Release 4 only.

FAUSCH

N/A

Not in Release 1999
4.2.1.1.3 Physical channels

Physical channel

Minimum number

Comments

P-CCPCH

1

Primary Common Control Physical channel. This is used by the Cell to Broadcast System Information messages; it is transmitted using the Primary Scrambling Code for the Cell.

P-CPICH

1

Primary Common Pilot Channel using the Primary Scrambling Code for the Cell.

S-CPICH

1 (For RF Tests)

Secondary Common Pilot Channel. This signal is used as the phase reference for some RF tests.

SCH

1

Synchronization Channel (includes P-SCH and S-SCH)

S-CCPCH

2

Secondary Common Control Physical channel.

PICH

1

To identify when the UE should access the PCCH for Paging Messages.

AICH

1

General Acquisition Indicator Channel that can be used for:

– Acquisition Indicator Channel, for PRACH

– Access Preamble Acquisition Indicator Channel (AP-ICH), for

PCPCH. (For release 99 and release 4 only)

– Collision-Detection/Channel-Assignment Indicator Channel

(CD/CA‑ICH), for PCPCH. (For release 99 and release 4 only)

DPDCH

3

Downlink Physical Data Channel. There will be a single DPCCH associated with all the DPDCHs used for Layer 1 signalling.

This number is for the First Cell. Additional Cells may define a lower number which should be at least 1.

PDSCH

1

Physical Downlink Shared Channel. Release 99 and Release 4 only.

DPCH

1

Uplink Dedicated Physical channel

PRACH

2

Physical Random Access Channel.

PCPCH

1

Physical Common Packet Channel. (For release 99 and release 4 only)

CSICH

1

CPCH Status Indicator Channel. (For release 99 and release 4 only)

4.2.1.2 Supported Channels for TDD Mode

4.2.1.2.1 Logical channels

Logical channel

Minimum number

Comments

Control channels

BCCH

1

Broadcast Control Channel: DL channel for broadcasting system control information.

CCCH

1

Common Control Channel: Bi-directional channel for transmitting control information between network and UEs. This channel is commonly used by the UEs having no RRC connection with the network and by the UEs using common transport channels when accessing a new cell after cell reselection.

DCCH

4

Dedicated Control Channel: A point-to-point bi-directional channel that transmits dedicated control information between a UE and the network. This channel is established through RRC connection setup procedure. 2 channels for RRC testing and 2 channels for NAS testing estimated.

PCCH

1

Paging Control Channel: DL channel that transfers paging information. This channel is used when the network does not know the location cell of the UE, or, the UE is in the cell connected state

SHCCH

1

Shared Channel Control Channel: Bi-directional channel that transmits control information for uplink and downlink shared channels between network and UEs. This channel is for TDD only.

Traffic channels

DTCH

1

Dedicated Traffic Channel is a point-to-point channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both UL and DL.

CTCH

1

Common Traffic Channel is a point-to-multipoint unidirectional channel for transfer of dedicated user information for all or a group of specified UEs.
4.2.1.2.2 Transport channels

Transport channel

Minimum number

Comments

BCH

1

Broadcast Channel: DL channel used to broadcast system and cell-specific information.

FACH

1

Forward Access Channel: DL channel used to carry control information to a mobile station when the system knows the location cell of the mobile station (may also carry short user packets).

PCH

1

Paging Channel: DL channel used to carry control information to a mobile station when the system does not know the location cell of the mobile station.

DCH

2

Dedicated Channel: UL or DL channel used to carry user or control information between the UTRAN and a UE

DSCH

1

DL shared channel: DL channel shared by several UEs carrying dedicated control or traffic data.

USCH

1

UL shared channel: UL channel shared by several UEs carrying dedicated control or traffic data.

RACH

1

Random Access Channel: UL channel used to carry control information from mobile station. The RACH may also carry short user packets.
4.2.1.2.3 Physical channels (3.84 Mcps option)

Physical channel

Minimum number

Comments

P-CCPCH

1

Primary Common Control Physical channel. . The BCH as described in clause 4.2.1 is mapped onto the P-CCPCH. The position (time slot / code) of the P-CCPCH is known from PSCH.

SCH

1

Synchronization Channel. Code group of a cell can be derived from the synchronization channel. In order not to limit the uplink/downlink asymmetry the SCH is mapped on one or two downlink slots per frame only.

S-CCPCH

2

Secondary Common Control Physical channel. PCH and FACH as described in clause 4.2.1 are mapped onto one or more S-CCPCH.

PICH

Paging Indicator Channel is a physical channel used to carry the paging indicators.

DPCH (DL)

3

Downlink Dedicated Physical channel. DCH channels are mapped onto DPCH

PDSCH

1

Physical Downlink Shared Channel. DSCH as described in clause 4.2.1 is mapped onto one or more PDSCH.

DPCH (UL)

1

Uplink Dedicated Physical channel. DCH channels are mapped onto DPCH.

PUSCH

1

Physical Uplink Shared Channel. The USCH as described in clause 4.2.1 is mapped onto one or more PUSCH. Timing advance, as described in 3GPP TS 25.224 [27], clause 4.3, is applied to the PUSCH.

PRACH

2

Physical Random Access Channel. The RACH as described in clause 4.2.1 is mapped onto PRACH

PNBSCH

1

Physical node B synchronization channel: In case cell sync bursts are used for Node B synchronization the PNBSCH shall be used for the transmission of the cell sync burst 3GPP TS 25.223 [35]. The PNBSCH shall be mapped on the same timeslot as the PRACH.
4.2.1.2.4 Physical channels (1.28 Mcps option)

Physical channel

Minimum number

Comments

P-CCPCH

2

Primary Common Control Physical channel. The BCH as described in clause 4.2.1 is mapped onto the P‑CCPCH1 and P-CCPCH2. The position (time slot / code) of the P-CCPCHs is fixed in the 1.28 Mcps TDD. The P-CCPCHs are mapped onto the first two code channels of timeslot#0 with spreading factor of 16.

DwPCH

1

Synchronization Channel for DL. Present in each 5 ms subframe.

UpPCH

1

Synchronization Channel for UL. Present in each 5 ms subframe.

S-CCPCH

2

Secondary Common Control Physical channel. PCH and FACH as described in clause 4.2.1 are mapped onto one or more S-CCPCH.

PICH

Paging Indicator Channel is a physical channel used to carry the paging indicators.

DPCH (DL)

3

Downlink Dedicated Physical channel. DCH channels are mapped onto DPCH

PDSCH

1

Physical Downlink Shared Channel. PDSCH provides the possibility for transmission of TFCI, SS, and TPC in downlink.

DPCH (UL)

1

Uplink Dedicated Physical channel. DCH channels are mapped onto DPCH.

PUSCH

1

Physical Uplink Shared Channel. PUSCH provides the possibility for transmission of TFCI, SS, and TPC in uplink.

FPACH

1

Fast Physical Access Channel. FPACH is used by the Node B to carry, in a single burst, the acknowledgement of a detected signature with timing and power level adjustment indication to a user equipment.

PRACH

2

Physical Random Access Channel. The RACH as described in clause 4.2.1 is mapped onto one or more uplink Physical Random Access Channels (PRACH).

4.2.1.2A Supported Channels for MBSFN (FDD and TDD Mode)

4.2.1.2A.1 Logical channels

Logical channel

Minimum number

Comments

Control channels

BCCH

1

Broadcast Control Channel: DL channel for broadcasting system control information.

MCCH

1

MBMS point-to-multipoint Control Channel: A point-to-multipoint downlink channel used for transmitting control information from the network to the UE. This channel is only used by UEs that receive MBMS.

MSCH

1

MBMS point-to-multipoint Scheduling Channel: A point-to-multipoint downlink channel used for transmitting scheduling control information, from the network to the UE, for one or several MTCHs carried on a CCTrCH. This channel is only used by UEs that receive MBMS.

Traffic channels

MTCH

1

MBMS point-to-multipoint Traffic Channel: A point-to-multipoint downlink channel used for transmitting traffic data from the network to the UE. This channel is only used for MBMS.
4.2.1.2A.2 Transport channels

Transport channel

Minimum number

Comments

BCH

1

Broadcast Channel: DL channel used to broadcast system and cell-specific information.

FACH

2

Forward Access Channel: Common downlink channel without closed-loop power control used for transmission of relatively small amounts of data. In addition FACH is used to carry broadcast and multicast data.

4.2.1.2A.3 Physical channels (3.84/7.68 Mcps options)

Physical channel

Minimum number

Comments

P-CCPCH

1

Primary Common Control Physical channel: The BCH as described in clause 4.2.1 is mapped onto the P-CCPCH. The position (time slot / code) of the P-CCPCH is known from PSCH.

SCH

1

Synchronization Channel: Code group of a cell can be derived from the synchronization channel. In order not to limit the uplink/downlink asymmetry the SCH is mapped on one or two downlink slots per frame only.

S-CCPCH

2

Secondary Common Control Physical channel: FACH as described in clause 4.2.1 is mapped onto one or more S-CCPCH.

MICH

1

MBMS Indicator Channel: Used to carry the MBMS notification indicators
4.2.1.2A.3A Physical channels (3.84 Mcps TDD IMB option)

Physical channel

Minimum number

Comments

P-CPICH

1

Primary Common Pilot Channel using the Primary Scrambling Code for the Cell.

T-CPICH

1

Time multiplexed Common Pilot Channel using the same Scrambling Code as P-CPICH for the Cell.

P-CCPCH

1

Primary Common Control Physical channel: The BCH as described in clause 4.2.1.2A.2 is mapped onto the P-CCPCH.

SCH

1

Synchronization Channel (includes P-SCH and S-SCH)

S-CCPCH

1

Secondary Common Control Physical channel: FACH carrying MCCH logical channel is mapped onto one S-CCPCH.

S-CCPCH Type 2

1

Secondary Common Control Physical CHannel Type 2: one or more FACH carrying MTCH logical channels is/are mapped onto one S-CCPCH Type 2

MICH

1

MBMS Indicator Channel: Used to carry the MBMS notification indicators

4.2.1.3 Support of Tcell timing offset

In test case parameter declarations, the parameter Tcell may be specified between 0 to 38 399, to allow for extensibility. However, the system simulator is required only to support a maximum Tcell value of 2 304, with a step resolution of 256. The SS may limit a Tcell value of greater than 2 304, and may round Tcell to the nearest multiple of 256.

4.2.2 RF Performance

4.2.2.1 Frequency of Operation

The System Simulator shall be capable of adjusting the Carrier Frequency of the DL channels to any frequency allowed in the DL frequency band. The DL frequency shall be accurate to the level of accuracy set by the core specifications 3GPP TS 25.104 [20] for FDD and 3GPP TS 25.105 [21] for TDD.

For RF tests, the requirement of Test Equipment is described in 3GPP TS 34.121 [2] annex F for FDD and 3GPP TS 34.122 [5] annex F for TDD respectively.

4.2.2.2 Power Level Setting Accuracy

The system simulator shall be able to adjust the average power output of the DL Channels to meet the absolute accuracy of the system simulator DL power levels covered in clause 5.4.1 Downlink Signal Levels.

For RF tests, the requirement of Test Equipment is described in 3GPP TS 34.121 [2] annex F for FDD and 3GPP TS 34.122 [5] annex F for TDD respectively.

The system simulator shall be capable of altering the power of the DL Dedicated channels under control of the UE Layer 1 Signalling information.

4.2.2.3 Uplink Power Control

The system simulator shall be able to command the UE to transmit at the maximum level for its power class or a lower level required for specific tests. The system simulator shall also provide the capability of generating the Layer 1 Signalling information to set the power levels of the Uplink Dedicated Channels from the UE to lower levels if required.

4.2.2.4 Uplink Signal Handling

For FDD mode, the System Simulator shall not be damaged by a Power Class 1 UE transmitting at the maximum power level permitted in 3GPP TS 25.101 [11] and for TDD mode by a Power Class 2 UE transmitting at the maximum power level permitted in 3GPP TS 25.102 [12].

4.2.2.5 Uplink Sensitivity

The simulator shall be able to receive uplink transmissions from the UE when it is transmitting at the minimum power level defined in 3GPP TS 25.101 [11] for FDD mode, and 3GPP TS 25.102 [12] for TDD mode.

Editor’s note: this is obviously a useful feature for the system simulator; however it is <ffs> if it should be an essential common requirement for a protocol test system.

4.2.3 Timers Tolerances

All the timers used during testing are within a tolerance margin given by the equation below. If for a specific test a different tolerance value is required then this should be specified in the relevant test document (i.e. the document where the test is described).

Timer tolerance = 10%, or 2  TTI + tdelta, whichever value is the greater.

Where tdelta is 55 ms.