11 E-UTRAN interfaces

36.4013GPPArchitecture descriptionEvolved Universal Terrestrial Radio Access Network (E-UTRAN)Release 17TS

11.1 General protocol model for E-UTRAN interfaces

The general protocol model for E-UTRAN interfaces is depicted in figure 11.1-1, and described in detail in the following subclauses. The structure is based on the principle that the layers and planes are logically independent of each other. Therefore, as and when required, the standardization body can easily alter protocol stacks and planes to fit future requirements.

Figure 11.1-1: General protocol model for E-UTRAN interfaces

11.1.1 Radio Network Layer (RNL) and Transport Network Layer (TNL)

The protocol structure consists of two main layers, Radio Network Layer (RNL) and Transport Network Layer (TNL).
E-UTRAN functions are realized in the RNL and the TNL represents standard transport technology that is selected to be used for E-UTRAN.

11.1.2 Control plane

The control plane includes the Application Protocol (AP), i.e. S1AP and X2AP and the Signalling Bearer for transporting the AP messages.

The AP is used e.g. for setting up bearers (i.e. E-RAB) in the RNL. The bearer parameters in the AP are not directly tied to the user plane technology, but are rather general bearer parameters.

11.1.3 User plane

The user plane includes the data bearer(s) for the data stream(s). The data stream(s) is characterized by a tunnelling protocol in the TNL.

11.2 Iuant interface – general principles

The Iuant interface for the control of RET antennas or TMAs is a logical part of the E-UTRAN.

The support of any standardised antenna interface technique shall not be prevented; e.g. AISG (Antenna interface standards group) specifications may be used.

Annex A (informative):
Change history

TSG #

TSG Doc.

CR

Rev

Subject/Comment

New

2007-12

–

–

–

Specification approved at TSG-RAN 38 and placed under change control

8.0.0

RP-39

RP-080079

0009

–

RAN3 agreed changes for TS 36.401

8.1.0

RP-40

RP-080303

0011

1

RAN3 agreed changes for TS 36.401

8.2.0

RP-41

RP-080582

0016

 

Uniqueness of eNB UE X2AP ID

8.3.0

RP-41

RP-080582

0017

1

Completion of Cell and eNB identifiers

8.3.0

RP-41

RP-080582

0019

 

Updating the Control Plane Protocol Stack

8.3.0

RP-41

RP-080582

0020

 

Correction of the description of subscriber and equipment trace

8.3.0

RP-42

RP-080844

0022

 

Clarify the relation between GUMMEI and MME UE S1AP ID

8.4.0

RP-42

RP-080844

0023

 

Proposed way forward of FFS item in 36.401

8.4.0

RP-42

RP-080844

0024

1

Adding the reference and correction on the GUMMEI definition reference

8.4.0

RP-42

RP-080844

0025

 

Correction on the eNB UE Context descriptions

8.4.0

RP-42

RP-080844

0026

1

RIM support in E-UTRAN

8.4.0

RP-42

RP-080845

0027

 

Correction of SAE Bearer

8.4.0

RP-42

RP-080844

0029

 

Correction of reference error

8.4.0

RP-43

RP-090246

0031

1

GUMMEI usage for NNSF

8.5.0

RP-43

RP-090245

0032

Measurement ID

8.5.0

RP-43

RP-090089

0034

Description place for Paging Function

8.5.0

RP-44

RP-090636

0035

1

Clarification on the Paging Function in E-UTRAN

8.6.0

RP-45

RP-090964

0036

Coexistence of LTE-TDD systems

8.7.0

12/2009

–

–

–

Creation of Rel-9 version based on v8.7.0

9.0.0

RP-47

RP-100230

0040

Support of time and frequency synchronization for HeNB

9.1.0

RP-48

RP-100600

0041

2

Handling of Positioning Functions

9.2.0

RP-48

RP-100599

0042

2

Handling of CMAS and ETWS

9.2.0

RP-48

RP-100597

0043

Correction of support of eMBMS

9.2.0

RP-48

RP-100598

0044

1

Updating the description of the Load Balancing and RIM functions

9.2.0

12/2010

Created Rel-10 version based on v 9.2.0

10.0.0

SP-49

SP-100629

Clarification on the use of References (TS 21.801 CR#0030)

10.1.0

RP-51

RP-110237

0047

3

Introduction of new synchronization use case for TD ICIC

10.1.0

RP-51

RP-110226

0048

1

Support of PWS in RAN Sharing

10.1.0

RP-52

RP-110689

0049

Limitations of PWS operation in RAN sharing

10.2.0

RP-52

RP-110685

0050

1

Correction to the References in 36.401

10.2.0

RP-53

RP-111196

0052

Correction to the References in 36.401

10.3.0

RP-56

RP-120744

0054

1

Introduction of KPAS delivery function

10.4.0

09/2012

Update to Rel-11 version (MCC)

11.0.0

RP-58

RP-121737

0059

1

Rapporteur update of 36.401

11.1.0

RP-61

RP-131182

0060

1

Correction on LPPa Signalling Transport Function to support UTDOA

11.2.0

RP-61

RP-131183

0061

1

Correction of terminology concerning the mobility restriction function

11.2.0

09/2013

MCC Cleanup

11.2.0

09/2014

Update to Rel-12 version (MCC)

12.0.0

RP-66

RP-142089

0064

4

Introduction of dual connectivity

12.1.0

RP-66

RP-142090

0068

Generic use of the logical synchronisation port

12.1.0

RP-67

RP-150351

0069

1

Correction on AP IDs for Dual Connectivity

12.2.0

RP-70

RP-152085

0072

3

Correction on UE associations in eNB

12.3.0

12/2015

Update to Rel-13 version (MCC)

13.0.0

RP-70

RP-152102

0076

1

Extension of X2AP IDs

13.0.0

RP-71

RP-160443

0079

Addition of loose-SFN synchronisation for extended Idle mode DRX

13.1.0

RP-72

RP-161042

0078

5

Introduction of the UE context resume function

13.2.0

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

03/2017

RP-75

RP-170535

0083

F

Clarification that the Xw UE ID is unique within relevant node

14.0.0

12/2017

RP-78

RP-172672

0084

B

Addition of the gNB UE X2AP ID usage

15.0.0

12/2018

RP-82

RP-182447

0086

1

F

EN-DC Antenna Interface Function support

15.1.0

2020-07

SA#88-e

–

–

–

–

Update to Rel-16 version (MCC)

16.0.0

2022-03

RP#95-e

RP-220217

0090

8

B

CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution

17.0.0

2022-06

RP#96

RP-221147

0091

–

D

Rapporteur Update to TS 36.401

17.1.0