7.1.10 Coordinated Multi-Point Operation (CoMP) for LTE

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

7.1.10.1 Sending SR on PUCCH with DMRS generated by using virtual cell identity / nPUCCH-Identity

7.1.10.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with nPUCCH-Identity-r11 configured }

ensure that {

when { UE has UL data available for transmission and UE has no UL-SCH resources available and SR_COUNTER is less than dsr-TransMax }

then { the UE transmits an SR on every available PUCCH until resources are granted }

}

7.1.10.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.211 clauses 5.4, 5.5.1.3, and 5.5.1.5. Unless otherwise stated these are Rel-11 requirements.

[TS 36.211, clause 5.4]

The physical uplink control channel, PUCCH, carries uplink control information. Simultaneous transmission of PUCCH and PUSCH from the same UE is supported if enabled by higher layers. For frame structure type 2, the PUCCH is not transmitted in the UpPTS field.

The physical uplink control channel supports multiple formats as shown in Table 5.4-1.
Formats 2a and 2b are supported for normal cyclic prefix only.

Table 5.4-1: Supported PUCCH formats

PUCCH format

Modulation scheme

Number of bits per subframe,

1

N/A

N/A

1a

BPSK

1

1b

QPSK

2

2

QPSK

20

2a

QPSK+BPSK

21

2b

QPSK+QPSK

22

3

QPSK

48

All PUCCH formats use a cyclic shift, , which varies with the symbol number and the slot number according to

where the pseudo-random sequence is defined by clause 7.2. The pseudo-random sequence generator shall be initialized with , where is given by clause 5.5.1.5 with corresponding to the primary cell, at the beginning of each radio frame.

…

[TS 36.211, clause 5.5.1.3]

The sequence-group number in slot is defined by a group hopping pattern and a sequence-shift pattern according to

There are 17 different hopping patterns and 30 different sequence-shift patterns. Sequence-group hopping can be enabled or disabled by means of the cell-specific parameter Group-hopping-enabled provided by higher layers. Sequence-group hopping for PUSCH can be disabled for a certain UE through the higher-layer parameter Disable-sequence-group-hopping despite being enabled on a cell basis unless the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure.

The group-hopping pattern may be different for PUSCH, PUCCH and SRS and is given by

where the pseudo-random sequence is defined by clause 7.2. The pseudo-random sequence generator shall be initialized with at the beginning of each radio frame where is given by clause 5.5.1.5.

The sequence-shift pattern definition differs between PUCCH, PUSCH and SRS.

For PUCCH, the sequence-shift pattern is given by where is given by clause 5.5.1.5.

…

[TS 36.211, clause 5.5.1.5]

The definition of depends on the type of transmission.

…

Transmissions associated with PUCCH:

– if no value for is configured by higher layers,

– otherwise.

7.1.10.1.3 Test description

7.1.10.1.3.1 Pre-test conditions

System Simulator:

2 Cells

– Cell 1 is the macro cell with higher power level that is further from UE than Cell 2.

– Cell 2 is the micro cell with lower power level that is nearer to UE compared to Cell 1.

– Two cells have the same virtual cell identity as configured in Table 7.1.10.1.3.3-3.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18].

7.1.10.1.3.2 Test procedure sequence

Table 7.1.10.1.3.2-1shows the cell configurations used during the test. The configuration T0 indicates the initial conditions.

Table 7.1.10.1.3.2-1: Cell configuration

 

Parameter

Unit

Cell 1

Cell 2

Remarks

T0

RS EPRE

dBm/15kHz

-85

-97

Table 7.1.10.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0A

The SS transmits RRCConnectionReconfiguration containing a radioResourceConfiguration with a physical channel reconfiguration

<–

–

–

–

0B

The UE transmits RRCConnectionReconfigurationComplete

–>

–

–

–

1

The SS indicates a new transmission on PDCCH and transmits a MAC PDU.

<–

MAC PDU

–

–

2

Check: Does the UE transmit a Scheduling Request on PUCCH whose DMRS is generated by using the configured nPUCCH-Identity-r11 encoded so that it can be received on Cell 1 and Cell 2?

–>

(SR)

1

P

3

The SS sends an UL grant suitable for the loop back PDU to be transmitted

<–

(UL Grant)

–

–

4

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 1.

–>

MAC PDU

–

–

7.1.10.1.3.3 Specific message contents

Table 7.1.10.1.3.3-1: RRCConnectionReconfiguration (step 0A, Table 7.1.10.1.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

Not present

dedicatedInfoNASList

Not present

radioResourceConfigDedicated

RadioResourceConfigDedicated-DEFAULT

securityConfigHO

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.1.10.1.3.3-1A: RadioResourceConfigDedicated-DEFAULT (step 0A, Table 7.1.10.1.3.2-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-HO ::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList

Not present

drb-ToReleaseList

Not present

mac-MainConfig

Not present

sps-Config

Not present

physicalConfigDedicated

PhysicalConfigDedicated -DEFAULT

}

Table 7.1.10.1.3.3-2: PhysicalConfigDedicated-DEFAULT (Table 7.1.10.1.3.3-1A)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

pucch-ConfigDedicated-v1020

PUCCH-ConfigDedicated-v1020-DEFAULT

2TX AND FDD, TDD

pucch-ConfigDedicated-v1130 SEQUENCE {

PUCCH-ConfigDedicated-v1130

pusch-ConfigDedicated-v1130

Not present

uplinkPowerControlDedicated-v1130

Not present

}

Note : All other IE’s are not present

Table 7.1.10.1.3.3-3: PUCCH-ConfigDedicated-v1130 (Table 7.1.10.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3-9AA

Information Element

Value/remark

Comment

Condition

PUCCH-ConfigDedicated-v1130 ::= SEQUENCE {

n1PUCCH-AN-CS-v1130 CHOICE {

setup SEQUENCE {

2 entries

n1PUCCH-AN-CS-ListP1-r11[1]

5

n1PUCCH-AN-CS-ListP1-r11[2]

6

}

}

nPUCCH-Param-r11 CHOICE {

setup SEQUENCE {

nPUCCH-Identity-r11

2

n1PUCCH-AN-r11

3

}

}

}

7.1.10.2 Transmitting data on PUSCH with DMRS generated by using virtual cell identity / nPUSCH-Identity

7.1.10.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with nPUSCH-Identity-r11 configured }

ensure that {

when { UE has UL data available for transmission }

then { UE transmits the data to the network on PUSCH with DMRS generated by using nPUSCH-Identity-r11 }

}

7.1.10.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.211 clauses 5.5.1.3, 5.5.1.4, 5.5.1.5 and 5.5.2.1.1. Unless otherwise stated these are Rel-11 requirements.

[TS 36.211, clause 5.5.1.3]

The sequence-group number in slot is defined by a group hopping pattern and a sequence-shift pattern according to

There are 17 different hopping patterns and 30 different sequence-shift patterns. Sequence-group hopping can be enabled or disabled by means of the cell-specific parameter Group-hopping-enabled provided by higher layers. Sequence-group hopping for PUSCH can be disabled for a certain UE through the higher-layer parameter Disable-sequence-group-hopping despite being enabled on a cell basis unless the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure.

The group-hopping pattern may be different for PUSCH, PUCCH and SRS and is given by

where the pseudo-random sequence is defined by clause 7.2. The pseudo-random sequence generator shall be initialized with at the beginning of each radio frame where is given by clause 5.5.1.5.

The sequence-shift pattern definition differs between PUCCH, PUSCH and SRS.

…

For PUSCH, the sequence-shift pattern is given by , where is configured by higher layers, if no value for is provided by higher layers or if the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure, otherwise it is given by with given by clause 5.5.1.5.

…

[TS 36.211, clause 5.5.1.4]

Sequence hopping only applies for reference-signals of length .

For reference-signals of length , the base sequence number within the base sequence group is given by .

For reference-signals of length , the base sequence number within the base sequence group in slot is defined by

where the pseudo-random sequence is given by clause 7.2. The parameter Sequence-hopping-enabled provided by higher layers determines if sequence hopping is enabled or not. Sequence hopping for PUSCH can be disabled for a certain UE through the higher-layer parameter Disable-sequence-group-hopping despite being enabled on a cell basis unless the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure.

For PUSCH, the pseudo-random sequence generator shall be initialized with at the beginning of each radio frame where is given by clause 5.5.1.5.

…

[TS 36.211, clause 5.5.1.5]

The definition of depends on the type of transmission.

Transmissions associated with PUSCH:

– if no value for is configured by higher layers or if the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure,

– otherwise.

…

7.1.10.2.3 Test description

7.1.10.2.3.1 Pre-test conditions

System Simulator:

2 Cells

– Cell 1 is the macro cell with higher power level that is further from UE than Cell 2.

– Cell 2 is the micro cell with lower power level that is nearer to UE compared to Cell 1.

– Two cells have the same virtual cell identity as configured in Table 7.1.10.2.3.3-3.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18].

7.1.10.2.3.2 Test procedure sequence

Table 7.1.10.2.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions.

Table 7.1.10.2.3.2-1: Cell configuration

 

Parameter

Unit

Cell 1

Cell 2

Remarks

T0

RS EPRE

dBm/15kHz

-85

-97

Table 7.1.10.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0A

The SS transmits RRCConnectionReconfiguration containing a radioResourceConfiguration with a physical channel reconfiguration

<–

–

–

–

0B

The UE transmits RRCConnectionReconfigurationComplete

–>

–

–

–

1

The SS indicates a new transmission on PDCCH and transmits a MAC PDU.

<–

MAC PDU

–

–

2

The UE transmit a Scheduling Request on PUCCH whose DMRS is generated by using the configured nPUCCH-Identity-r11?

–>

(SR)

–

–

3

The SS sends an UL grant suitable for the loop back PDU to be transmitted

<–

(UL Grant)

–

–

4

Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 1 with the DMRS generated by using the configured nPUSCH-Identity-r11 encoded so that it can be received on Cell 1 and Cell 2?

–>

MAC PDU

1

P

7.1.10.2.3.3 Specific message contents

Table 7.1.10.2.3.3-1: RRCConnectionReconfiguration (step 0A, Table 7.1.10.2.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

Not present

dedicatedInfoNASList

Not present

radioResourceConfigDedicated

RadioResourceConfigDedicated-DEFAULT

securityConfigHO

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.1.10.2.3.3-1A: RadioResourceConfigDedicated-DEFAULT (step 0A, Table 7.1.10.2.3.2-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-HO ::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList

Not present

drb-ToReleaseList

Not present

mac-MainConfig

Not present

sps-Config

Not present

physicalConfigDedicated

PhysicalConfigDedicated-DEFAULT

}

Table 7.1.10.2.3.3-2: PhysicalConfigDedicated-DEFAULT (Table 7.1.10.2.3.3-1A)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

pucch-ConfigDedicated-v1130

Not present

pusch-ConfigDedicated-v1130

PUSCH-ConfigDedicated-v1130

uplinkPowerControlDedicated-v1130

Not present

}

Note: All other IE’s are not present

Table 7.1.10.2.3.3-3: PUSCH-ConfigDedicated-v1130 (Table 7.1.10.2.3.3-2)

Derivation Path: 36.508 clause 4.6.3-11AA

Information Element

Value/remark

Comment

Condition

PUSCH-ConfigDedicated-v1130 ::= SEQUENCE {

pusch-DMRS-r11 CHOICE {

setup SEQUENCE {

nPUSCH-Identity-r11

3

nDMRS-CSH-Identity-r11

4

}

}

}