Showing posts with label Quick Notes. Show all posts
Showing posts with label Quick Notes. Show all posts

Wednesday, 8 October 2014

UE Feedback: The Measurement Report - Part 1

As UEs have become smarter and the air interface more complex, the need for more detailed communication between the UE and the network has increased dramatically.  The UE has become the eyes and the ears of the radio access network.  Its main goal is to find the best cell and maximize performance with that cell.

To help the UE accomplish this, the eNodeB gathers several pieces of information from the UE and then adjusts its’ downlink transmissions accordingly. The UE tells the network what cells it can see and how strong it can see them, its current channel conditions, the current state of its’ memory buffer, which antennas should be transmitting in the downlink, how many different transmission streams can be supported simultaneously, acknowledgements when data is received successfully, and any other information that the network wants to know.

This is the first in a series of blogs on these different types of UE feedback.  This blog will focus on the measurement report.  The measurement report is the mechanism used by the UE to tell the network whatever results have been requested. Typically, these are measurements of the surrounding cells.  They can also include requested measurements of block error rate, transmit power and other UE-based parameters. The UE learns the requested information using a measurement configuration.

When a UE is in RRC-CONNECTED mode, this measurement configuration is provided to the UE by means of dedicated signaling; typically using the RRCConnectionReconfiguration message.

The measurement configuration provided to the UE includes the following parameters:

Measurement Objects:  the objects on which the UE shall perform the measurements; i.e. frequencies and cells.  In other words:  who should the UE measure? These include intra- and inter- frequency neighbors, IRAT UMTS neighbors, IRAT GSM neighbors and IRAT CDMA2000 HRPD and 1xRTT neighbors.
Reporting Configurations:  the criteria used by the UE to trigger the transmission of a measurement report and the quantities that the UE includes in the report. In other words: when should the UE send a report?  This trigger can either be periodical or event-based.
Measurement Identities: an identifier that links one measurement object with one reporting configuration.  In other words: the UE needs to keep track of the objects to be measured and their specific triggers.  The measurement identity is used as a reference number in the measurement report.
Quantity configurations: the measurement quantities and associated filtering used for all event evaluation and related reporting per Radio Access Technology.
Measurement gaps:  periods of time that the UE may use to perform measurements while in connected mode.
The UE maintains a single measurement object list, a single reporting configuration list and a single measurement identities list.  Any measurement object can be linked to any reporting configuration of the same RAT type.

As mentioned earlier, a report can be event-triggered or periodical.  An event-based measurement report will be transmitted when the criteria for any of the following events have been met:


A1:  Serving Cell becomes better than a defined threshold

A2:  Serving Cell becomes worse than a defined threshold

A3:  Neighbor cell becomes some offset better than the primary cell

A4:  Neighbor cell becomes better than a defined threshold

A5:  Primary cell becomes worse than a defined threshold and a neighbor becomes better than a second threshold

A6:  Neighbor cell becomes some offset better than the serving cell

B1:  Inter-RAT neighbor becomes better a defined threshold

B2:  Primary cell becomes worse than a defined threshold and inter-RAT neighbor becomes better than a second threshold

Periodical measurement reports are sent based on the reporting configuration.  For instance, it could be configured that the UE report its’ transmit power every 2 seconds or its’ transport channel block error rate every second.  This is operator-specific.

We have discussed the vehicle used by the UE to tell the network what it can see as well as other operator-configured parameters.  Another piece of information that the network needs to be successful is some indication of the channel conditions at the UE.  This will help the network adapt its downlink transmission to match the UE’s capability at that time.   These channel quality indicators or CQI’s will be the subject of the next blog in this series.


Source:  LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (3GPP TS 36.331 version 10.5.0 Release 10)

LTE data transmissions.

We have seen a lot of terms around when we discuss LTE data transmissions, especially when we get into some of the details of sending data over the PDSCH using multiple antenna techniques. We describe transport blocks as holding the data we're trying to send, but how do they relate to codewords? Assigning bits to different layers can be used to improve reliability or throughput, but are layers the same as antenna ports? Let's have a closer look at what's going on down in the Physical (PHY) Layer.

User data and signaling messages are processed by the PDCP, RLC and MAC layers before being passed down to the PHY layer to be sent over the air. A lot happens to a data packet before PHY gets it, but for the moment, let's just treat the MAC PDU (Protocol Data Unit) that PHY receives from MAC as "data". To PHY, it's just a string of bits anyway. This will be our transport block.

Transport Blocks to Codewords

Query: What does PHY do with a transport block? 

First, it converts the transport block into a codeword. There are a number of steps involved in this process, depending on the length of the transport block:
  • Append a 24 bit checksum (CRC) to the transport block. This CRC is used to determine whether the transmission was successful or not, and triggers Hybrid ARQ to send an ACK or NACK, as appropriate
  • Segment the transport block into code blocks. A code block must be between 40 and 6144 bits long. If the transport block is too small, it is padded up to 40 bits; if the TB is too big, it is divided into smaller pieces, each of which gets an additional 24 bit CRC.
  • Process each code block with a 1/3 turbo coder
  • Reassemble the resulting code blocks into a single codeword

A codeword, then, is essentially a transport block with error protection. Note that a UE may be configured to receive one or two transport blocks (and hence one or two codewords) in a single transmission interval.

Codewords to Layers

PHY then converts each codeword into modulation symbols. For each codeword, PHY must:
  • Scramble the contents of each codeword, using a sequence based on the UE's C-RNTI and the cell's Physical Cell ID (PCI) 
  • Convert the bit sequences into the corresponding modulation symbols (using QPSK, 16QAM or 64QAM) 
  • Assign the modulation symbols to one or more layers, depending on the specific transmission scheme being used

In the case of a single transmit antenna, the last step is pretty simple: the contents of the codeword are mapped to a single layer. For transmit diversity, it's almost as easy: the symbols from the codeword are distributed evenly across the 2 or 4 layers in a round-robin fashion.

In spatial multiplexing situations, things get a little more complicated, since one or two codewords may be distributed across 1, 2, 3 or 4 layers. In brief, here's how the mapping is handled:


The number of layers used in any particular transmission depends (at least in part) on the Rank Indication (RI) feedback from the UE, which identifies how many layers the UE can discern.

Layers to Antenna Ports

The final steps apply any required precoding adjustments and assign the modulation symbols to the physical resources:
  • Apply the required precoding factors to the modulation symbols in each layer
  • Map the precoded symbols to the appropriate antenna ports
  • Assign the modulation symbols to be transmitted on each antenna port to specific resource elements (the subcarriers and symbols within the resource blocks)
  • Generate the final time-domain OFDM signal for each antenna port

Note that the number of layers is always less than or equal to the number of antenna ports (transmit antennas). If there's only one antenna port, then it carries just a single layer. In multiple (2 or 4) antenna situations, though, each antenna port may end up carrying a complicated combination of the symbols from multiple layers. 

for more info you can check out spec 36.211, section 6.3.4 if you really want to dig into the details.

Conclude? One transport block -> one codeword -> one or two layers -> one or more antenna ports. Fortunately, the eNodeB and the UE always know what's going on, even if I have trouble keeping it all straight sometimes.

Saturday, 4 October 2014

Scheduling operation in LTE

Basic Scheduling Operations:
- Purpose
* Efficient SCH(Data) Resources Assignments
- Consideration
* Traffic Volume, QoS (Buffer Status, Priority…)
* Channel Condition
- Scheduling Interval
* Dynamic Scheduling by MAC : One TTI (1ms : One Sub-frame)
* Semi-Persistent for VoIP : Multiple TTIs by RRC
- Resource Assignment : PRBs & Associated MCS

Scheduling information: DCI PDCCH


DCI





Resource Assignment
- Per UE # PRBs Assignment
* Channel Dependent Resource Allocation
  •User Assignment based on Channel Quality
- CQI / MCS / TBS


CQI Reporting for Scheduling
Reporting modes


- In time : Periodic (PUCCH/PUSCH) & Aperiodic (PUSCH)
- In Frequency
• Wide-band CQI : 4 bit
• Differential Sub-band CQI : 2 bit (Sub-band CQI – Wideband CQI)
• Differential Spatial CQI : 3bit for MIMO

Schedulers in LTE

DL Scheduling
DL MAC Scheduler


Friday, 3 October 2014

RNTI

RNTI stands for Radio Network Temporary Identifier. As the name implies, it is a kind of Identification number. Normally we use indentification number to differntiate one thing from all other similar things.
Followings are the brief summary of RNTIs being used in LTE. i hope this diagram will clear you about RNTI what kind of RNTI? what type of RNTI? what are the value for RNTI? what is the mapping of RNTI?



Who issues these RNTI ?
Network issues RNTI.

Exactly what does RNTI do for each of those radio channel ? The detailed process differs with the types of RNTIs, but generally speaking all of these RNTI is used to scramble the CRC part of the radio channel messages. It implies that if UE does not know the exact RNTI values for each of the cases, it cannot decode the radio channel messages even though the message reaches the UE intact.



One of the most common questions that I got about RNTI is "There are a lot of different types of RNTI and I don't see any RNTI information on DCI or Higher layer signaling message. Then how can PHY layer know which RNTI it has to use to decode a data ?". The answer is "MAC or Layer 1 controller would instruct PHY on which RNTI it has to use". Then a next questions comes out. "How MAC or Layer 1 controller would know which RNTI to be used ?". There is no explicit algorithm for this, MAC/L1 controller needs to figure it out "based on context". For example, if it is at the subframe where SIB is transmitted, it would instruct PHY to use SI-RNTI. if UE is in connected mode, it may instruct to use C-RNTI, TPC RNTI etc.

How each of RNTI is used ?
Following is the quotes from 3GPP specification showing how RNTI is used for various cases.. for the exact details, you should see the specification but this partial quote would give you a rough idea of the usage of RNTI.

From 3GPP TS:36.212

5.3.3 Downlink control information
  • A DCI transports downlink or uplink scheduling information, or uplink power control commands for one RNTI. The RNTI is implicitly encoded in the CRC. 
5.3.3.1.3 Format 1A
  • Format 1A is used for random access procedure initiated by a PDCCH order only if format 1A CRC is scrambledwith C-RNTI
  • For distributed VRB: .. if the format 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI
5.3.3.2 CRC attachment
  • This section explain in detail on how CRC is scrambled by RNTI. Following is the summary of this process. As you see, RNTI is used to scramble CRC bits of PDCCH.

MAC PDU Formats

1. A MAC PDU primarily consists of the MAC header and the MAC payload. (it's very simple and general to say)

2. The MAC header is further composed of MAC subheaders, while the MAC payload is composed of MAC Control Elements, MAC SDUs and padding.


•Each MAC PDU corresponds to a single Transport Block (TB)
•There is one sub-header for each MAC Control Element in the PDU and each MAC SDU in the PDU

3. Each MAC subheader consists of a Logical Channel ID (LCID) and a Length (L) field.
4. The LCID indicates whether the corresponding part of the MAC payload is a MAC Control Element, and if not, to which logical channel the related MAC SDU belongs.
5. The L field indicates the size of the related MAC SDU or MAC Control Element.


MAC header consists of multiple sub-headers
•One sub-header for each Control Element, MAC PDU or Padding
•Each sub-header is 1 or 2, 3 bytes in length
–[R/R/E/LCID]: Used for fixed length MAC SDUs and MAC Control Elements
–[R/R/E/LDID/F/Length]: Used for variable length MAC SDUs


MAC Control Elements are used for MAC-level peer-to-peer signalling, including delivery of BSR information and reports of the UE’s available power headroom in the uplink, and in the downlink DRX commands and timing advance commands. For each type of MAC Control Element, one special LCID is allocated. When a MAC PDU is used to transport data from the PCCH or BCCH logical channels, the MAC PDU includes data from only one logical channel. In this case, because multiplexing is not applied, there is no need to include the LCID field in the header. In addition, if there is a one-to-one correspondence between a MAC SDU and a MAC PDU, the size of the MAC SDU can be known implicitly from the transport block size. Thus, for these cases a headerless MAC PDU format is used as a transparent MAC PDU.

MAC Control Element

Seven Control Elements are defined 
4 for DL
•Timing Alignment (8bits): Sent to provide initial and periodic time synchronization to the UE for UL
•DRX Command (8 bits): Initiates discontinuous reception mode at UE
•UE Contention Resolution Identity (48bits): Used during RACH procedure to resolve possible contention b/w multiple UEs trying to simultaneously access the network 
•MCH Scheduling Information MAC Control Element
3 for UL
•UE Buffer Status Reports (8 or 24bits): Reports UE buffer occupancy for UL scheduling
•UE Power Headroom (8 bits): Reports UE transmit power compared to maximum or if the UE is currently power limited
•C-RNTI (16 bits): Identifies a UE when sending information over CCCH

Monday, 29 September 2014

LTE Transmission Techniques

SISO: is the simplest system using only 1 antenna at each station
SIMO: uses receive diversity at the mobile to combat the effects of multipath and fading in the radio channel. The gain can be up to 3dB.
MISO: uses Space Frequency Block Coding to provide transmit diversity where data is copied onto different frequencies on the two antennas. This is used for most of the physical channels but not the SCH and reference signals. These are received by a single antenna in order to improve signal reception over the channel thus combating the effects of multi-path and fading. MISO does not
increase data rates.
MIMO: relies on Spatial Multiplexing where two data streams are sent via 2 or 4 antennas. This is used on PDSCH and PMCH. Pre-defined orthogonal training sequences are used from each transmitter to enable the receiver to learn to distinguish the separate signals.



Additionally, Cyclic Delay Diversity may be used on the physical downlink shared channel PDSCH in which there is a cyclical shift of the signal between the different antennas. These appear as a phase diversity (a delay of half a symbol for the 2 antenna case) in the received signal so may be separated
more easily. MIMO increases the data throughput.
If 4 antennas are used at the eNode B, there are two data streams and transmit diversity is used for each of these on the second pair of antennas to increase the reliability of transmission.

LTE Band

As per 3GPP Rel 9 revision of the LTE standard defines bands of operation, including both paired and unpaired spectrum. 1-32 bands are for paired (FDD) operation, while bands 33-40 are for unpaired (TDD) operation


Saturday, 27 September 2014

Resource Allocation



System Information Block 2 specifies the resources reserved for the PRACH transmissions. The resource may be specified as 1, 2, 3, 5, ... sub-frames within the frame (the set of options depending on frame type and PRACH preamble type). Initially this will be 6 contiguous resource blocks but additional frequencies could be specified once all the time resource has been allocated.
The mobile sends a PRACH preamble in a randomly chosen PRACH resource and waits for the Random Access Response (RAR).
The Random Access Response comprises a resource assignment which is implicitly addressed to the mobile by scrambling the CRC with the RA-RNTI that was used by the mobile in the PRACH transmission. The Downlink resource is used for transmission of the RAR which is addressed to a number of mobiles which have sent PRACH preambles. For each mobile a grant is given which the mobiles use to send their first RRC message.

PRACH Physical Random Access Channel

• The Access burst comprises a preamble and a few bits of payload data
– Several preamble formats (lengths) are specified
• Initial message from the mobile use nonsynchronised timing
• The eNodeB supplies the required Timing Advance
• Any subsequent transmissions can use synchronised PRACH

Initially, the time delay between the base station and the mobile is not known accurately, so the PRACH transmissions are not synchronised. Subsequently, the timebase at the mobile is adjusted and the transmissions are synchronised with uplink transmissions from other mobiles in the cell.
There are several preamble sequences defined for a cell, the mobile selects one randomly and this is used to identify the mobile in the response sent from the base station.

PMCH - Physical Multicast Channel

• For transmission of multicast and broadcast information
• Format is similar to the PDSCH but it is for reception by several mobiles
• Sub-channel spacing is 7.5 kHz and symbol length is doubled
• Modulation QPSK, 16 QAM or 64 QAM

The longer symbol length means a longer cyclic prefix permitting good reception over large cells or for combination of signals broadcast simultaneously over a set of cells.

PDSCH - Physical Downlink Shared

• Carries DL-SCH - user data and higher layer (RRC, NAS) signalling
• Time sharing of data transmission to mobiles
• Carries the PCH - Paging of mobiles
• Also carries the System Information
– The System Information Blocks are carried on the PDSCH so the transmission bandwidth used and
repetition schedule can be varied
• Modulation QPSK, 16 QAM or 64 QAM

Mobile Identities

• CRC generation depends on UE Identities -
implicitly addresses Resource Assignments
– SI-RNTI = FFFF Assignments for System Information
– P-RNTI = FFFE Assignments for Paging messages
– RA-RNTI based on subframe number in which PRACH was received
Assignment for Random Access Response
– C-RNTI the identity given during RRC Connection Assignment for DLSCH or ULSCH (uplink grant)

Resource Allocation for Uplink

• Allocation may be Dynamic - single TTI or Semi-persistent - periodically repeating
• UE is sent a bitmap to assign the uplink Resource Blocks
– Bitmap type 2 - Assignment of a set of contiguous Resource Blocks

The grant in FDD mode relates to the uplink sub frame which is 4 sub frames delayed from that in which the resource allocation is included to allow the mobile time to process the information. In TDD the delay is different.

Resource Allocation for Downlink

• Allocation may be Dynamic - single TTI or Semi-persistent (periodically repeating)
• UE is sent a bitmap to assign the downlink Resource Blocks in the same TTI
– Direct bitmap - each bit assigns one resource block
– Bitmap type 0 - assigns Resource Block Groups (sets of consecutive Resource Blocks)
– Bitmap type 1 - assigns individual resource blocks (for frequency diversity) from the Resource Block Groups
– Bitmap type 2 - several sets of contiguous blocks (no segmentation of band into Resource Block Groups)

Semi-persistent allocation of Resource Blocks is useful for real-time applications such as VoIP where the transfer of data is constant and repetitive.
The semi-persistent allocation is provided to the mobile’s C-RNTI so if the mobile does not see any further allocation, it may use this repetitive allocation.
If it does see an allocation to its C-RNTI, this takes precedence.
The direct bitmap is only used for up to 10 resource blocks (10 bits) otherwise the bitmap size would become too large.
Assignments are usually made which cover transmissions in both halves of the subframe, but it is also possible to have separate assignments for each half of the subframe.

PDCCH - Physical Downlink Control

• Carries Downlink Control Information (DCI), resource block assignments for transmissions
– Assignment information is sent every subframe
• Sent in a small set of Control Channel Elements
– So UE does not need to decode all the PDCCH
– Space for Control channel assignments is known to all
– Space for Dedicated assignments is per mobile
• CRC of the Assignments depends on the mobile’s active identity (implicit addressing)
• Modulation QPSK

PBCH - Physical Broadcast Channel

• Carries the BCH - System Information
– Only the Master Information Block is carried on the PBCH
– (The System Information Blocks are sent on PDSCH)
• From SCH and BCH the mobile can determine the cell identifiers
• Sent on central 72 subcarriers (6 resource blocks) once a frame (10ms)
• Modulation QPSK for reception over the cell

Downlink Reference Signals

Reference symbols are added to the downlink transmissions for:
Channel quality measurements
Channel estimation and equalisation over the frequency band to allow demodulation of the received signal
Hence the reference symbols are distributed in time and frequency.
If a second antenna is used (MIMO operation) this will transmit reference signals in the alternate resource elements.
In the example above, we assume frame structure type 1 and a short cyclic prefix so there are 7 symbols in the timeslot