Beamforming in Spec

1 © Nokia Siemens Networks

Beamforming in TD-LTEAeroflex &NSN

2 © Nokia Siemens Networks Beamforming in TD-LTE / Peter Skov / 29-12-2009For internal use

UE specific reference signals can be pre-coded, UE estimates combined precoder and radio channel Hw (pure channel H can not be derived.)

Beamforming in Spec36.211

Four common reference ports

Dedicated reference port

R5

R5

R5

R5

R5

R5

R5

R5

R5

R5

R5

Control symbols

Datasymbols

R5



Mode 7 DCI format 1A

Common andUE specific by C-RNTI

If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

DCI format 1 UE specific by C-RNTI

Single-antenna port; port 5 (see subclause 7.1.1)

Table 7.1-5: PDCCH and PDSCH configured by C-RNTI

https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D417891453



UE-EUTRA-Capability information elementPhyLayerParameters ::= SEQUENCE {

ue-TxAntennaSelectionSupported BOOLEAN,

ue-SpecificRefSigsSupported BOOLEAN

}


Dual polarized antenna array

eNB configuration:

• 4 pairs of ±45° Cross-polarized antenna.

• 8 antenna elements are divided into 2 beamforming groups, and 2 groups perform DL beamforming individually.

• 2 CRS enabled

• 1 DRS

UE configuration:

• 2 antennas and 1 PA.

• 2 antennas RX & 1 antenna Tx (antenna TX switching is an option)

Tx TxAntenna Port 0

Antenna Port 1

TxAntenna Port 5

Rx_1 Rx_2

Virtual 2x2 Channel


UE Radio Capability Handling – eNB retrieves UE Radio Capability from UE (1/3)

During below procedures and the precondition fulfilled

- Attach

- Or TAU for “first TAU following GERAN/UTRAN attach” or for a “UE radio capability update”,

- Or Service Request, but MME does not have the UE radio capability.

Then following procedures performed

- MME – not send any UE Radio Capability info in INITIAL CONTEXT SETUP REQUEST

- eNB – request UE Radio Capability from UE and upload it to the MME, the related procedures as following

1) 36.331, eNB triggers “UE capability transfer” on Uu

2) 36.413, eNB triggers “UE Capability Info Indication” on S1



UL NAS Transfersd

UE eNB MME

Attach Procedure or TAU for "first TAU following GERAN/UTRAN attach" or for a "UE radio capability update"

1 : S1AP:INITIAL CONTEXT SETUP REQUEST

2 : RRC: SecurityModeCommand(integrityProtected, not ciphered)

3 : RRC: UECapabilityEnquiry(integrityProtected, ciphered)

4 : RRC:SecurityCommandComplete(integrityProtected, not ciphered)

5 : RRC:UECapabilityInformation(integrityProtected, ciphered)

UE Radio Capability Available

6 : RRC:RRCConnectionReconfiguration(integrityProtected,ciphered)

7 : RRC:RRCConnectionReconfigurationComplete(integrityProtected,ciphered)8 : S1AP:INITIAL CONTEXT SETUP RESPONSE

9 : S1AP: UE CAPABILITY INFO INDICATION

a parallel UL NAS transfer procedure for a NAS PDU from UE, e.g. Attach Response, or optional the dedicated Bearer Setup Respnse

MME should not send any UE Radio Capability

UE Security Establishment

UE UserPlaneConfiguration

If UEspecificRSSupported = TRUETranmission mode for DRB will be set to 7



UECapabilityEnquiry messageInformation Element/

Group nameNeed Sou

rceSemantics description /

comments

rrc-TransactionIdentifier

eNB Set to an unused transaction identifier.

ueCapabilityEnquiry eNB

> ue-CapabilityRequest

eNB SEQUENCE of RAT-Types in this release.For number of RAT-Types see text below.

>> RAT-Type eNB RAT-TYPE according 3GPP {eutra, utra, geran-cs, geran-ps, cdma2000-1XRTT}UECapabilityInformation message

Information Element/Group name

Need Source

Semantics description / comments

rrc-TransactionIdentifier UE Shall be the same transaction identifier as in the UE CAPABILITY ENQUIRY message.

ue-CapabilityRAT-ContainerList

UE SEQUENCE of RAT-Types in this release.

> UE-CapabilityRAT-Container UE

>> rat-Type UE List of rat-types shall be the same as in UECapabilityEnquiry message.

>> ueCapabilityRAT-Container UE OCTET STRING - container of RAT related UE capabilities:

For “eutra” the container contains the structure UE-EUTRA-Capability


UE Radio Capability Handling – eNB receives UE Radio Capability from MMEIf UE performing the Service Request, and If MME has UE Radio Capability, then no UE

radio capability specific procedure involved

UL NAS Transferopt

eNB MMEUE

performing Service Request, and MME has the UE Radio Capability

1 : S1AP: INITIAL CONTEXT SETUP

MME has the UE Radio Capability at least for E-TRUA and send to eNB2 : RRC:SecurityModeCommand(IntegrityProtected, not ciphered)

3 : RRC:RRCConnectionReconfiguration(IntegrityProtected, ciphered)

4 : RRC:SecurityCommandComplete(IntegrityProtected, not ciphered)

5 : RRC:RRCConnectionReconfigurationComplete(IntegrityProtected,ciphered)

6 : S1AP:INITIAL CONTEXT SETUP RESPONSE

UE Security Establishment

UE UserPlaneConfiguration

one optinal UL NAS transfer Procedure, e.g. the dedicated bearer setup response

Transmission Mode 7 could be set


UE Radio Capability Handling – Handover ProcedureIntra eNB/inter eNB via X2 Handover - UE capability should be transferred from Source to Target in Handover Request, no UE Radio Capability specific procedure needed

Inter RAT HO – if there are no UE capabilities of other RATs that UE and eNB can support, then eNB need retrieve them from UE using RRC UE Capability Transfer Procedure before starting the inter-RAT measurement.

????Inter RAT HO – After handover completion when UE other RAT capabilities not received during handover, Target eNB will trigger the UE Radio Capability Transfer procedure to obtain it.

Documents

Beamforming in Spec