|
|
Currently, the OAI platform includes a full software implementation of the 3GPP LTE protocol stack, both for the RAN (OpenAir4G) and the EPC (OpenAirCN).
|
|
|
|
|
|
---++ RAN
|
|
|
# RAN
|
|
|
|
|
|
---+++ PHY
|
|
|
## PHY
|
|
|
|
|
|
The Physical layer implements 3GPP 36.211, 36.212, 36.213 and provides the following features:
|
|
|
* LTE release 8.6 compliant, and implements a subset of release 10;
|
|
|
* FDD and TDD configurations tested in 5, 10, and 20 MHz bandwidth;
|
|
|
* Transmission mode: 1, 2, 3 (eNB only), 5, and 6;
|
|
|
* CQI/PMI reporting;
|
|
|
* All downlink (DL) channels are supported: PSS, SSS, PBCH, PCFICH, PHICH, PDCCH, PDSCH, PMCH;
|
|
|
* All uplink (UL) channels are supported: PRACH, PUSCH, PUCCH (format 1), SRS (not tested for a long time), DRS;
|
|
|
* HARQ support (UL and DL);
|
|
|
* Highly optimized base band processing (including turbo decoder) .
|
|
|
*not supported yet:*
|
|
|
* PUCCH format 2 (and 3)
|
|
|
* PRACH formats x
|
|
|
*
|
|
|
---+++ MAC
|
|
|
|
|
|
The MAC layer implements a subset of the 3GPP 36-321 release v8.6 in support of BCH, DLSCH, RACH, and ULSCH channels. The eNB MAC implementation includes:
|
|
|
* RRC interface for CCCH, DCCH, and DTCH
|
|
|
* Schedulers
|
|
|
* DCI generation
|
|
|
* HARQ Support
|
|
|
* RA procedures and RNTI management
|
|
|
* RLC interface (AM, UM)
|
|
|
* UL power control
|
|
|
UE MAC implementation includes
|
|
|
* PDU formats: all control elements and logical channels
|
|
|
* RLC interface AM,UM, TM
|
|
|
* RRC transparent interface for CCCH and BCCH
|
|
|
* Buffer status reporting and scheduling request procedures
|
|
|
* Power headroom reporting
|
|
|
|
|
|
---+++ PDCP
|
|
|
|
|
|
* LTE release 8.6 compliant, and implements a subset of release 10;
|
|
|
* FDD and TDD configurations tested in 5, 10, and 20 MHz bandwidth;
|
|
|
* Transmission mode: 1, 2, 3 (eNB only), 5, and 6;
|
|
|
* CQI/PMI reporting;
|
|
|
* All downlink (DL) channels are supported: PSS, SSS, PBCH, PCFICH, PHICH, PDCCH, PDSCH, PMCH;
|
|
|
* All uplink (UL) channels are supported: PRACH, PUSCH, PUCCH (format 1), SRS (not tested for a long time), DRS;
|
|
|
* HARQ support (UL and DL);
|
|
|
* Highly optimized base band processing (including turbo decoder).
|
|
|
|
|
|
**not supported yet:**
|
|
|
|
|
|
* PUCCH format 2 (and 3)
|
|
|
* PRACH formats x
|
|
|
|
|
|
## MAC
|
|
|
|
|
|
The MAC layer implements a subset of the 3GPP 36-321 release v8.6 in support of BCH, DLSCH,
|
|
|
RACH, and ULSCH channels. The eNB MAC implementation includes:
|
|
|
|
|
|
* RRC interface for CCCH, DCCH, and DTCH
|
|
|
* Schedulers
|
|
|
* DCI generation
|
|
|
* HARQ Support
|
|
|
* RA procedures and RNTI management
|
|
|
* RLC interface (AM, UM)
|
|
|
* UL power control
|
|
|
|
|
|
UE MAC implementation includes:
|
|
|
|
|
|
* PDU formats: all control elements and logical channels
|
|
|
* RLC interface AM,UM, TM
|
|
|
* RRC transparent interface for CCCH and BCCH
|
|
|
* Buffer status reporting and scheduling request procedures
|
|
|
* Power headroom reporting
|
|
|
|
|
|
## PDCP
|
|
|
|
|
|
The current PDCP is header compliant with 3GPP 36-323 Rel 10.1.0 and implement the following functions:
|
|
|
* User and control data transfer
|
|
|
* Sequence number management
|
|
|
* RB association with PDCP entity
|
|
|
* PDCP entity association with one or two RLC entities
|
|
|
* Integrity check and encryption using the AES and Sonw3G algorithms
|
|
|
|
|
|
---+++ RLC
|
|
|
|
|
|
The RLC layer implements a full specification of the 3GPP 36-322 release v9.3 for all the three mode: transparent mode (TM), unacknowledged mode (UM), and acknowledge mode (AM) with the following characteristics:
|
|
|
* RLC TM (mainly used for BCCH and CCCH)
|
|
|
* Neither segment nor concatenate RLC SDUs
|
|
|
* Do not include a RLC header in the RLC PDU
|
|
|
* Delivery of received RLC PDUs to upper layers
|
|
|
* RLC UM (mainly used for DTCH)
|
|
|
* Segment or concatenate RLC SDUs according to the TB size selected by MAC
|
|
|
* Include a RLC header in the RLC PDU
|
|
|
* Duplication detection
|
|
|
* PDU reordering and reassembly
|
|
|
* RLC AM, compatible with 9.3
|
|
|
* Segmentation, concatenation, and reassembly
|
|
|
* Padding
|
|
|
* Data transfer to the user
|
|
|
* RLC PDU retransmission in support of error control and correction
|
|
|
* Generation of data/control PDUs
|
|
|
|
|
|
---+++ RRC
|
|
|
|
|
|
The RRC layer, shared between the UE and the ENB, performs the control of the radio interface. It is based on 3GPP 36.331 v9.2.0. The control procedures available in the LTE platform are the following:
|
|
|
* System Information broadcast (SIB 1, 2, 3, and 13)
|
|
|
* RRC connection establishment
|
|
|
* RRC connection reconfiguration (addition and removal of radio bearers, connection release)
|
|
|
* RRC connection release
|
|
|
* inter-frequency measurement collection and reporting at UE and eNB
|
|
|
* eMBMS for multicast and broadcast
|
|
|
*under integration/testing*
|
|
|
* EUTRA handover
|
|
|
* RRC connection re-establishment
|
|
|
* Paging
|
|
|
*not supported*
|
|
|
* most of the SIB formats (except 1, 2, 3, and 13)
|
|
|
* inter-frequency, inter-band, inter-RAT measurements
|
|
|
* counter check
|
|
|
|
|
|
---++ EPC
|
|
|
|
|
|
-- User.FlorianKaltenberger - 05 Feb 2015 |
|
|
|
|
|
* User and control data transfer
|
|
|
* Sequence number management
|
|
|
* RB association with PDCP entity
|
|
|
* PDCP entity association with one or two RLC entities
|
|
|
* Integrity check and encryption using the AES and Sonw3G algorithms
|
|
|
|
|
|
## RLC
|
|
|
|
|
|
The RLC layer implements a full specification of the 3GPP 36-322 release v9.3 for all
|
|
|
the three mode: transparent mode (TM), unacknowledged mode (UM), and acknowledge mode (AM)
|
|
|
with the following characteristics:
|
|
|
|
|
|
* RLC TM (mainly used for BCCH and CCCH)
|
|
|
* Neither segment nor concatenate RLC SDUs
|
|
|
* Do not include a RLC header in the RLC PDU
|
|
|
* Delivery of received RLC PDUs to upper layers
|
|
|
* RLC UM (mainly used for DTCH)
|
|
|
* Segment or concatenate RLC SDUs according to the TB size selected by MAC
|
|
|
* Include a RLC header in the RLC PDU
|
|
|
* Duplication detection
|
|
|
* PDU reordering and reassembly
|
|
|
* RLC AM, compatible with 9.3
|
|
|
* Segmentation, concatenation, and reassembly
|
|
|
* Padding
|
|
|
* Data transfer to the user
|
|
|
* RLC PDU retransmission in support of error control and correction
|
|
|
* Generation of data/control PDUs
|
|
|
|
|
|
## RRC
|
|
|
|
|
|
The RRC layer, shared between the UE and the ENB, performs the control of the radio interface.
|
|
|
It is based on 3GPP 36.331 v9.2.0. The control procedures available in the LTE platform
|
|
|
are the following:
|
|
|
|
|
|
* System Information broadcast (SIB 1, 2, 3, and 13)
|
|
|
* RRC connection establishment
|
|
|
* RRC connection reconfiguration (addition and removal of radio bearers, connection release)
|
|
|
* RRC connection release
|
|
|
* inter-frequency measurement collection and reporting at UE and eNB
|
|
|
* eMBMS for multicast and broadcast
|
|
|
|
|
|
**under integration/testing**
|
|
|
|
|
|
* EUTRA handover
|
|
|
* RRC connection re-establishment
|
|
|
* Paging
|
|
|
|
|
|
**not supported**
|
|
|
|
|
|
* most of the SIB formats (except 1, 2, 3, and 13)
|
|
|
* inter-frequency, inter-band, inter-RAT measurements
|
|
|
* counter check
|
|
|
|
|
|
# EPC
|
|
|
|
|
|
-- @florian.kaltenberger - 05 Feb 2015 |