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