3gpp ts 36.423.pdf

7/18/2019 3GPP TS 36.423.pdf

http://slidepdf.com/reader/full/3gpp-ts-36423pdf 1/78

3GPP TS 36.423 V8.2.0 (2008-06)Technical Specification

3rd Generation Partnership Project;Technical Specification Group Radio Access Network;

Evolved Universal Terrestrial Radio Access Network (EUTRAN);X2 application protocol (X2AP)

(Release 8)

The present document has been developed within the 3 rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)2Release 8

KeywordsUMTS, radio

3GPP

Postal address

3GPP support office address650 Route des Lucioles - Sophia Antipolis

Valbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internethttp://www.3gpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

© 2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).All rights reserved.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)3Release 8

Contents

Foreword ............................................................................................................................................................ 6

1 Scope........................................................................................................................................................ 7 2 References ................................................................................................................................................ 7

3 Definitions, symbols and abbreviations ................................................................................................... 7 3.1 Definitions ............................................................... ....................................................................... ................... 7 3.2 Symbols ............................................................... ................................................................ .............................. 7 3.3 Abbreviations..................................................................................................................................................... 8

4 General ..................................................................................................................................................... 8 4.1 Procedure specification principles ................................................................. .................................................... 8 4.2 Forwards and backwards compatibility .................................................................. ........................................... 8 4.3 Specification notations....................................................................................................................................... 9

5 X2AP services .......................................................................................................................................... 9 5.1 X2AP procedure modules.................................................................................................................................. 9 5.2 Parallel transactions .................................................................. ................................................................. ........ 9

6 Services expected from signalling transport ............................................................................................ 9

7 Functions of X2AP................................................................................................................................... 9

8 X2AP procedures ................................................................................................................................... 10 8.1 Elementary procedures ..................................................................... ............................................................... 10 8.2 Basic mobility procedures ................................................................ ............................................................... 10 8.2.1 Handover Preparation................................................................................................................................. 10 8.2.1.1 General .............................................................. .................................................................. ................. 10 8.2.1.2 Successful Operation ............................................................. ............................................................... 11 8.2.1.2.1 UE History Information ............................................................... ................................................... 11 8.2.1.3 Unsuccessful Operation........................................................................................................................ 12 8.2.1.4 Abnormal Conditions ..................................................................... ...................................................... 12 8.2.2 SN Status Transfer ..................................................................... ............................................................... 12 8.2.2.1 General .............................................................. .................................................................. ................. 12 8.2.2.2 Successful Operation ............................................................. ............................................................... 12 8.2.2.2 Abnormal Conditions ..................................................................... ...................................................... 13 8.2.3 UE Context Release ............................................................ ................................................................ ....... 13 8.2.3.1 General .............................................................. .................................................................. ................. 13 8.2.3.2 Successful Operation ............................................................. ............................................................... 14 8.2.3.3 Unsuccessful Operation........................................................................................................................ 14 8.2.3.4 Abnormal Conditions ..................................................................... ...................................................... 14 8.2.4 Handover Cancel........................................................................................................................................ 14

8.2.4.1 General .............................................................. .................................................................. ................. 14 8.2.4.2 Successful Operation ............................................................. ............................................................... 14 8.2.4.3 Unsuccessful Operation........................................................................................................................ 15 8.2.4.4 Abnormal Conditions ..................................................................... ...................................................... 15 8.3 Global Procedures........................................................................................................................................... 15 8.3.1 Load Indication ........................................................ ............................................................... .................. 15 8.3.1.1 General .............................................................. .................................................................. ................. 15 8.3.1.2 Successful Operation ............................................................. ............................................................... 15 8.3.1.3 Unsuccessful Operation........................................................................................................................ 16 8.3.1.4 Abnormal Conditions ..................................................................... ...................................................... 16 8.3.2 Error Indication ............................................................. ...................................................................... ....... 16 8.3.2.1 General .............................................................. .................................................................. ................. 16 8.3.2.2 Successful Operation ............................................................. ............................................................... 16

8.3.2.3 Unsuccessful Operation........................................................................................................................ 16 8.3.2.4 Abnormal Conditions ..................................................................... ...................................................... 16 8.3.3 X2 Setup..................................................................................................................................................... 16 8.3.3.1 General .............................................................. .................................................................. ................. 16

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)4Release 8

8.3.3.2 Successful Operation ............................................................. ............................................................... 17 8.3.3.3 Unsuccessful Operation........................................................................................................................ 17 8.3.3.4 Abnormal Conditions ..................................................................... ...................................................... 17 8.3.4 Reset........................................................................................................................................................... 17 8.3.4.1 General .............................................................. .................................................................. ................. 17 8.3.4.2 Successful Operation ............................................................. ............................................................... 18

8.3.4.3 Unsuccessful Operation........................................................................................................................ 18 8.3.4.4 Abnormal Conditions ..................................................................... ...................................................... 18 8.3.5 eNB Configuration Update......................................................................................................................... 18 8.3.5.1 General .............................................................. .................................................................. ................. 18 8.3.5.2 Successful Operation ............................................................. ............................................................... 18 8.3.5.3 Unsuccessful Operation........................................................................................................................ 19 8.3.6 Resource Status Update Initiation ................................................................. ............................................ 19 8.3.6.1 General....................................................................................................................................................... 19 8.3.6.2 Successful Operation.................................................................................................................................. 19 8.3.6.3 Unsuccessful Operation........................................................................................................................ 20 8.3.6.4 Abnormal Conditions ................................................................ ................................................................. 20 8.3.7 Resource Status Reporting ................................................................... ...................................................... 20 8.3.7.1 General .............................................................. .................................................................. ................. 20 8.3.7.2 Successful Operation ............................................................. ............................................................... 20 9 Elements for X2AP Communication...................................................................................................... 21 9.1 Message Functional Definition and Content.................................................................................................... 21 9.1.1 Messages for Basic Mobility Procedures ............................................................ ....................................... 21 9.1.1.1 HANDOVER REQUEST..................................................................................................................... 21 9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE................................................................. .................... 22 9.1.1.3 HANDOVER PREPARATION FAILURE............................................................................... ........... 23 9.1.1.4 SN STATUS TRANSFER........................................................................................................ ............ 24 9.1.1.5 UE CONTEXT RELEASE................................................................................................................... 25 9.1.1.6 HANDOVER CANCEL....................................................................................................................... 25 9.1.2 Messages for global procedures .................................................................... ............................................. 25 9.1.2.1 LOAD INFORMATION......................................................... ............................................................. 25 9.1.2.2

ERROR INDICATION ............................................................. ........................................................... 26

9.1.2.3 X2 SETUP REQUEST............ ..................................................................... ........................................ 26 9.1.2.4 X2 SETUP RESPONSE ..................................................................... .................................................. 27 9.1.2.5 X2 SETUP FAILURE............................................................. ............................................................. 27 9.1.2.6 RESET REQUEST............................................................................................................................... 27 9.1.2.7 RESET RESPONSE............................................................................................................................. 27 9.1.2.8 ENB CONFIGURATION UPDATE....................................................................................... ............. 28 9.1.2.9 ENB CONFIGURATION UPDATE ACKNOWLEDGE.............................................................. ...... 28 9.1.2.10 ENB CONFIGURATION UPDATE FAILURE......... ..................................................................... .... 28 9.1.2.11 RESOURCE STATUS REQUEST ................................................................. ..................................... 29 9.1.2.12 RESOURCE STATUS RESPONSE ........................................................................ ............................ 29 9.1.2.13 RESOURCE STATUS FAILURE ........................................................... ............................................ 29 9.1.2.14 RESOURCE STATUS UPDATE................................................................................................ ......... 29

9.2 Information Element definitions ................................................................. ..................................................... 30 9.2.1 GTP Tunnel Endpoint ................................................................. ............................................................... 30 9.2.2 Trace activation.......................................................................................................................................... 30 9.2.3 UE History Information ................................................................ ............................................................. 31 9.2.4 Last Visited Cell Information..................................................................................................................... 31 9.2.5 Handover Restriction list............................................................................................................................ 31 9.2.6 PLMN Identity ................................................................ .................................................................... ....... 32 9.2.7 DL Forwarding........................................................................................................................................... 33 9.2.8 Cause.......................................................................................................................................................... 33 9.2.9 Criticality Diagnostics................................................................................................................................ 36 9.2.10 Served Cell Information............................................................................................................................. 36 9.2.11 SAE Bearer Level QoS Parameters............................................................................................................ 37 9.2.12 SAE Bearer Type .............................................................. .................................................................. ....... 37

9.2.13 SAE Bearer Bit Rate ............................................................. .............................................................. ....... 37 9.2.14 Aggregate Maximum Bit Rate ............................................................... .................................................... 38 9.2.15 Message Type............................................................................................................................................. 38 9.2.16 CGI............................................................................................................................................................. 38

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)5Release 8

9.2.17 COUNT value .......................................................... ................................................................ .................. 38 9.2.18 GUMMEI......... ..................................................................... .............................................................. ....... 39 9.2.19 UL Interference Overload Indication .............................................................. ........................................... 39 9.2.20 UL High Interference Indication..... ............................................................................ ............................... 39 9.2.21 Maximum Tx Power per PRB normalized ................................................................. ................................ 39 9.2.22 GU Group Id ............................................................. ............................................................... .................. 40

9.2.23 Location Reporting Information................................................................................................................. 40 9.3 Message and Information Element Abstract Syntax (with ASN.1) ................................................................. 41 9.3.1 General....................................................................................................................................................... 41 9.3.2 Usage of Private Message Mechanism for Non-standard Use ........................................................... ........ 41 9.3.3 Elementary Procedure Definitions ..................................................................... ........................................ 41 9.3.4 PDU Definitions......................................................................................................................................... 46 9.3.5 Information Element definitions .......................................................... ...................................................... 59 9.3.6 Common definitions................................................................................................................................... 69 9.3.7 Constant definitions .................................................................. ................................................................. 70 9.3.8 Container definitions.................................................................................................................................. 72 9.4 Message transfer syntax................................................................................................................................... 77 9.5 Timers.............................................................................................................................................................. 77

10 Handling of unknown, unforeseen and erroneous protocol data............................................................ 77

Annex A (informative): Change history ............................................................................................... 78

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)6Release 8

ForewordThis Technical Specification has been produced by the 3 rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formalTSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with anidentifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)7Release 8

1 ScopeThe present document specifies the radio network layer signalling procedures of the control plane between eNBs inEUTRAN. X2AP supports the functions of X2 interface by signalling procedures defined in this document. X2AP is

developed in accordance to the general principles stated in [2] and [3].

2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.

• References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.

• For a specific reference, subsequent revisions do not apply.

• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (includinga GSM document), a non-specific reference implicitly refers to the latest version of that document in the same

Release as the present document .

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 36.401: “E-UTRAN Architecture Description”.

[3] 3GPP TS 36.420: “X2 General Aspects and Principles”.

[4] 3GPP TS 36.413: “S1 Application Protocol (S1AP)”.

[5] ITU-T Recommendation X.691 (07/2002): "Information technology - ASN.1 encoding rules -Specification of Packed Encoding Rules (PER)

[6] 3GPP TS 32.422: “Subscriber and Equipment Trace; Trace Control and ConfigurationManagement ”.

[7] 3GPP TS 32.421: "Trace concepts and requirements".

[8] 3GPP TS 36.424: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 datatransport”.

3 Definitions, symbols and abbreviations

3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in [1] and the following apply. A termdefined in the present document takes precedence over the definition of the same term, if any, in [1].

<defined term> : <definition>.

3.2 SymbolsFor the purposes of the present document, the following symbols apply:

<symbol> <Explanation>

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)8Release 8

3.3 AbbreviationsFor the purposes of the present document, the abbreviations given in [1] and the following apply. An abbreviationdefined in the present document takes precedence over the definition of the same abbreviation, if any, in [1].

DL Downlink

eNB E-UTRAN NodeBEP Elementary ProcedureEPC Evolved Packet CoreE-UTRAN Evolved UTRANGUMMEI Globally Unique MME IdentifierHFN Hyper Frame NumberIE Information ElementMME Mobility Management EntityPDCP Packet Data Convergence ProtocolPLMN Public Land Mobile NetworkSN Sequence NumberUE User EquipmentUL Uplink

4 General

4.1 Procedure specification principlesThe principle for specifying the procedure logic is to specify the functional behaviour of the terminating eNB exactlyand completely. Any rule that specifies the behaviour of the originating eNB shall be possible to be verified withinformation that is visible within the system.

The following specification principles have been applied for the procedure text in clause 8:

- The procedure text discriminates between:

1) Functionality which "shall" be executed

The procedure text indicates that the receiving node "shall" perform a certain function Y under a certaincondition. If the receiving node supports procedure X but cannot perform functionality Y requested in theREQUEST message of a Class 1 EP, the receiving node shall respond with the message used to reportunsuccessful outcome for this procedure, containing an appropriate cause value.

2) Functionality which "shall, if supported" be executed

The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y

under a certain condition. If the receiving node supports procedure X, but does not support functionalityY, the receiving node shall proceed with the execution of the EP, possibly informing the requesting nodeabout the not supported functionality.

- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, theoptional IE shall not be included. For requirements on including Criticality Diagnostics IE, see section 10.

4.2 Forwards and backwards compatibilityThe forwards and backwards compatibility of the protocol is assured by a mechanism where all current and futuremessages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will

not be changed in the future. These parts can always be decoded regardless of the standard version.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)9Release 8

4.3 Specification notationsFor the purposes of the present document, the following notations apply:

Procedure When referring to an elementary procedure in the specification the Procedure Name is written withthe first letters in each word in upper case characters followed by the word "procedure", e.g.

Handover Preparation procedure.

Message When referring to a message in the specification the MESSAGE NAME is written with all lettersin upper case characters followed by the word "message", e.g. HANDOVER REQUEST message.

IE When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic fontfollowed by the abbreviation "IE", e.g. SAE Bearer ID IE.

Value of an IE When referring to the value of an information element (IE) in the specification the "Value" iswritten as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Value".

5 X2AP servicesThe present clause describes the services an eNB offers to its neighbours.

5.1 X2AP procedure modulesThe X2 interface X2AP procedures are divided into two modules as follows:

1. X2AP Basic Mobility Procedures;

2. X2AP Global Procedures;

The X2AP Basic Mobility Procedures module contains procedures used to handle the mobility within E-UTRAN.

The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this moduleare in contrast to the above module involving two peer eNBs.

5.2 Parallel transactionsUnless explicitly indicated in the procedure specification, at any instance in time one protocol peer shall have amaximum of one ongoing X2AP procedure related to a certain UE.

6 Services expected from signalling transportEditors Note: More clarification to be added here when definition clearer in 36.401.

The signalling connection shall provide in sequence delivery of X2AP messages. X2AP shall be notified if thesignalling connection breaks.

7 Functions of X2APThe X2AP protocol provides the following functions:

- Mobility Management. This function allows the eNB to move the responsibility of a certain UE to another eNB.Forwarding of user plane data is a part of the mobility management.

- Load Management. This function is used by eNBs to indicate overload and traffic load to each other.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)10Release 8

- Reporting of General Error Situations. This function allows reporting of general error situations, for whichfunction specific error messages have not been defined.

- Resetting the X2. This function is used to completely reset the X2 interface.

- Setting up the X2. This function is used to exchange necessary data for the eNB for setup the X2 interface.

8 X2AP procedures

8.1 Elementary proceduresIn the following tables, all EPs are divided into Class 1 and Class 2 EPs.

Table 8.1-1: Class 1 Elementary Procedures

Successful Outcome Unsuccessful OutcomeElementaryProcedure

Initiating MessageResponse message Response message

HandoverPreparation

HANDOVERREQUEST

HANDOVERREQUEST

ACKNOWLEDGE

HANDOVERPREPARATION FAILURE

Reset RESET REQUEST RESET RESPONSE

X2 Setup X2 SETUP REQUEST X2 SETUPRESPONSE

X2 SETUP FAILURE

eNBConfigurationUpdate

ENBCONFIGURATIONUPDATE

ENBCONFIGURATIONUPDATE

ACKNOWLEDGE

ENB CONFIGURATIONUPDATE FAILURE

Resource StatusReportingInitiation

RESOURCE STATUSREQUEST

RESOURCE STATUSRESPONSE

RESOURCE STATUSFAILURE

Table 8.1-2: Class 2 Elementary Procedures

Elementary Procedure Initiati ng MessageLoad Indication LOAD INFORMATIONHandover Cancel HANDOVER CANCELSN Status Transfer SN STATUS TRANSFERUE Context Release UE CONTEXT RELEASEResource Status Reporting RESOURCE STATUS UPDATEError Indication ERROR INDICATION

8.2 Basic mobility procedures

8.2.1 Handover Preparation

8.2.1.1 General

This procedure is used to establish necessary resources in a eNB for an incoming handover.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)11Release 8

8.2.1.2 Successful Operation

sourceeNB

HANDOVER REQUEST

HANDOVER REQUEST ACKNOWLEDGE

targeteNB

Figure 8.2.1.2-1: Handover Preparation, successful operation

The source eNB initiates the procedure by sending the HANDOVER REQUEST message to the target eNB. When thesource eNB sends the HANDOVER REQUEST message, it shall start the timer T RELOCprep

If at least one of the requested SAE bearers is admitted to the cell, the target eNB shall reserve necessary resources, andsend the HANDOVER REQUEST ACKNOWLEDGE message back to the source eNB. The target eNB shall includethe SAE Bearers for which resources have been prepared at the target cell in the SAE Bearers Admitted List IE. Thetarget eNB shall include the SAE bearers that have not been admitted in the SAE Bearers Not Admitted List IE with anappropriate cause value.

For each bearer for which the source eNB proposes to do forwarding of downlink data, the source eNB shall include the DL forwarding IE within the SAE Bearer Info IE of the HANDOVER REQUEST message. For each bearer that it hasdecided to admit, the target eNB may include the DL GTP Tunnel endpoint IE within the SAE Bearer Info IE of theHANDOVER REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding of downlinkdata for this bearer. This GTP tunnel endpoint may be different than the corresponding GTP TEID IE in the SAE BearerTo Be Switched in Downlink List of the PATH SWITCH REQUEST message (see [4]) depending on implementationchoice.

For each bearer in the SAE Bearers Admitted List IE, the target eNB may include the UL GTP Tunnel Endpoint IE if itrequests data forwarding of uplink packets to be performed for that bearer.

Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message the source eNB shall stop the timerTRELOCprep , start the timer TX2 RELOCOverall and terminate the Handover Preparation procedure. The source eNB is thendefined to have a Prepared Handover for that X2 UE-associated signalling.

If the Trace activation IE is included in the HANDOVER REQUEST message then the target eNB should initiate therequested trace function as described in [6] .

The HANDOVER REQUEST message shall contain the Handover Restriction List IE, if available.

If the Handover Restriction List IE is

- contained in the HANDOVER REQUEST message, the target eNB shall store this information and the targeteNB should use the information in Handover Restriction List IE to determine a target cell for subsequenthandover attempts.

- not contained in the HANDOVER REQUEST message, the target eNB shall consider that no access restrictionapplies to the UE.

If the Location Reporting Information IE is included in the HANDOVER REQUEST message then the eNB shallinitiate the requested location reporting procedure as defined in [4].

Editor’s Note: The reporting of Cell ID with regard to cell change caused by X2 handover is FFS.

8.2.1.2.1 UE History Information

Configuration may be used to instruct an eNB about collection of UE historical information.

When configured to collect UE historical information, the eNB shall:

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)12Release 8

- Collect information about the UE for as long as the UE stays in one of its cells, and store the collectedinformation to be used for future handover preparations.

- At handover preparation, add the stored information to the Last Visited Cell IE and include the UE History Information IE in the HANDOVER REQUEST message.

- At reception of the HANDOVER REQUEST message in where the UE History Information IE is included,collect the same type of information as that included in the UE History Information IE and act according to the

bullets above.

8.2.1.3 Unsuccessful Operation

sourceeNB

HANDOVER REQUEST

HANDOVER PREPARATION FAILURE

targeteNB

Figure 8.2.1.3-1: Handover Preparation, uns uccess ful operation

If the target eNB is not able to accept any of the SAE bearers or a failure occurs during the Handover Preparation, thetarget eNB shall send the HANDOVER PREPARATION FAILURE message to the source eNB. The message shallcontain the Cause IE with an appropriate value.

Interactions with Handover Cancel procedure:

If there is no response from the target eNB to the HANDOVER REQUEST message before timer T RELOCprep expires inthe source eNB, the source eNB should cancel the Handover Preparation procedure towards the target eNB by initiatingthe Handover Cancel procedure with the appropriate value for the Cause IE, e.g. "T RELOCprep expiry".

8.2.1.4 Abnormal Conditions

Void.

8.2.2 SN Status Transfer

8.2.2.1 GeneralThe purpose of the SN Status Transfer procedure is to transfer the uplink PDCP-SN and HFN receiver status and thedownlink PDCP-SN and HFN transmitter status from the source to the target eNB during an X2 handover for eachrespective SAE bearer for which PDCP SN and HFN status preservation applies.


7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)13Release 8

sourceeNB

SN STATUS TRANSFER

targeteNB

Figure 8.2.2.2-1: SN Status Transfer, successful operation

The source eNB initiates the procedure by sending the SN STATUS TRANSFER message to the target eNB at the time point when it considers the transmitter/receiver status to be frozen. After sending this message the source eNB shall stopassigning PDCP SNs to downlink SDUs and shall stop delivering UL SDUs toward the EPC. At that point of time, thesource eNB shall either:

- discard the uplink packets received out of sequence for each bearer for which PDCP SN status preservationapplies but not forwarding,

- forward the uplink packets received out of sequence for each bearer for which the source eNB has accepted therequest from the target eNB for uplink forwarding,

- send the uplink packets received out of sequence to the EPC for each bearer for which the PDCP SN status preservation doesn’t apply.

For each bearer for which PDCP SN status preservation applies, the source eNB shall include the UL COUNT value IEwithin the SAE Bearers Subject to Status Transfer Item IE.

The source eNB shall also include in the SN STATUS TRANSFER message the missing and received uplink SDUs inthe Receive status of UL PDCP SDUs IE for each bearer for which the source eNB has accepted the request from thetarget eNB for uplink forwarding.

For each bearer for which the UL COUNT value IE is received in the SN STATUS TRANSFER message, the targeteNB shall use it and not deliver any uplink packet which has a PDCP SN lower than the value contained in the PDCP-SN IE of this IE.

If the Receive status of UL PDCP SDUs IE is included in the SN STATUS TRANSFER message for at least one bearer,the target eNB may use it in a Status Report message sent to the UE over the radio.

For each bearer for which PDCP SN status preservation applies, the source eNB shall include the DL COUNT value IEwithin SAE Bearers Subject to Status Transfer Item IE.

If the DL COUNT value IE is received in the SN STATUS TRANSFER message for one bearer, the target eNB shalluse it to mark with the value contained in the PDCP-SN IE of this IE the first downlink packet for which there is noPDCP SN yet assigned.


If the target eNB receives this message for a UE for which no prepared handover exists at the target eNB, the targeteNB shall ignore the message.

8.2.3 UE Context Release

8.2.3.1 General

The UE Context Release procedure is initiated by the target eNB to signal to the source eNB that control planeresources for the handed over UE context can be released.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)14Release 8


sourceeNB

UE CONTEXT RELEASE

targeteNB

Figure 8.2.3.2-1: UE Context Release, successful operation

The UE Context Release procedure is initiated by the target eNB. By sending UE CONTEXT RELEASE the target eNBinforms success of Handover to source eNB and triggers the release of resources.

Upon reception of the UE CONTEXT RELEASE message, the source eNB can release radio and control plane relatedresources associated to the UE context. For bearers for which data forwarding has been performed, the source eNBshould continue forwarding of U-plane data as long as packets are received at the source eNB from the EPC or thesource eNB buffer has not been emptied (an implementation dependent mechanism decides that data forwarding can bestopped).


Not applicable.


If the UE Context Release procedure is not initiated towards the source eNB from any prepared eNB before the expiryof the timer TX2 RELOCoverall , the source eNB shall release all resources associated to the UE context and request theMME to release the UE context.

If the UE returns to source eNB before the reception of the UE CONTEXT RELEASE message or the expiry of thetimer TX2 RELOCoverall , the source eNB shall stop the TX2 RELOCoverall and continue.

8.2.4 Handover Cancel

8.2.4.1 General

The Handover Cancel procedure is used to cancel an already prepared handover.


sourceeNB

HANDOVER CANCEL

targeteNB

Figure 8.2.4.2-1: Handover Cancel, succ essful operation

The source eNB initiates the procedure by sending the HANDOVER CANCEL message to the target eNB. The sourceeNB shall indicate the reason for cancelling the handover by means of an appropriate cause value.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)15Release 8

At the reception of the HANDOVER CANCEL message, the target eNB shall remove any reference to, and release anyresources previously reserved to the concerned UE context.


Not applicable.


Should the HANDOVER CANCEL message refer to a context that does not exist, the target eNB shall ignore themessage.

8.3 Global Procedures

8.3.1 Load Indication

8.3.1.1 GeneralThe purpose of the Load Indication procedure is to transfer load and interference co-ordination information betweenintra-frequency neighboring eNBs.

The procedure uses non UE associated signalling.


eNB 1

LOAD INFORMATION

eNB 2

Figure 8.3.1.2-1: Load Indication

An eNB initiates the procedure by sending LOAD INFORMATION message to intra-frequency neighbouring eNBs.

If the UL Interference Overload Indication IE is received in the LOAD INFORMATION message, it indicates the

interference level experienced by the sending eNB on some resource blocks. The receiving eNB may take suchinformation into account when setting its scheduling policy and shall consider the received UL Interference Overload Indication IE value valid until reception of a new LOAD INFORMATION message carrying an update of the same IE.

If the UL High Interference Indication IE is received in the LOAD INFORMATION message, it indicates, per PRB, theoccurrence of high interference sensitivity, as seen from the sending eNB. The receiving eNB should try to avoidscheduling cell edge UEs in its cells for the concerned PRBs. The Target Cell ID IE received within the UL High

Interference Information IE group in the LOAD INFORMATION message indicates the cell for which thecorresponding UL High Interference Indication is meant. The receiving eNB shall consider the value of the UL High

Interference Information IE group valid until reception of a new LOAD INFORMATION message carrying an update.

If the Maximum Tx Power per PRB Normalized IE is received in the LOAD INFORMATION message, it indicates, perPRB, whether downlink transmission power exceeds a certain threshold (FFS). The receiving eNB may take suchinformation into account when setting its scheduling policy and shall consider the received Maximum Tx Power perPRB Normalized IE value valid until reception of a new LOAD INFORMATION message carrying an update.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)16Release 8


Not applicable.


Void.

8.3.2 Error IndicationEditor Note: Used by peer node to report detected errors in a received message.

8.3.2.1 General

The Error Indication procedure is initiated by an eNB to report detected errors in one incoming message, provided theycannot be reported by an appropriate failure message.

If the error situation arises due to reception of a message utilising UE associated signalling, then the Error Indication

procedure uses UE associated signalling. Otherwise the procedure uses non UE associated signalling.


eNB 2eNB 1

ERROR INDICATION

Figure 8.3.2.2-1: Error Indication, successful operation.

When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERRORINDICATION message sent from the node detecting the error situation.

The ERROR INDICATION message shall contain at least either the Cause IE or the Criticality Diagnostics IE.

In case the Error Indication procedure is triggered by UE associated signalling the Old eNB UE X2AP ID IE and New eNB UE X2AP ID IE shall be included in the ERROR INDICATION message. If one or both of Old eNB UE X2AP ID IE and New eNB UE X2AP ID IE are not correct, the cause shall be set to appropriate value e.g. “unknown Old eNB UEX2AP ID”, “unknown New eNB UE X2AP ID” or “unknown pair of UE X2AP ID ”.

8.3.2.3 Unsuccessful Operation Not applicable.


Not applicable.

8.3.3 X2 Setup

8.3.3.1 General

The purpose of the X2 Setup procedure is to exchange application level data needed for two eNBs to interoperatecorrectly over the X2 interface.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)17Release 8



eNB 1

X2 SETUP REQUEST

eNB 2

X2 SETUP RESPONSE

Figure 8.3.3.2-1: X2 Setup, successf ul operation

An eNB, initiates the procedure by sending an X2 SETUP REQUEST to a candidate eNB. Candidate eNB replies withX2 SETUP RESPONSE. The initiating eNB transfers a list of served cells to the candidate eNB. Candidate eNB replieswith a list of its served cells.


eNB 1

X2 SETUP REQUEST

eNB 2

X2 SETUP FAILURE

Figure 8.3.3.3-1: X2 Setup, unsucc essful operation

If the candidate eNB can not accept the setup it shall respond with an X2 SETUP FAILURE with appropriate causevalue.

If the X2 SETUP FAILURE messages include the Time To Wait IE the eNB shall wait at least for the indicated time before reinitiating the X2 setup towards the same eNB.


If X2 SETUP REQUEST is not the first message received for a specific TNL association then this shall be treated as alogical error.

8.3.4 Reset

8.3.4.1 General

The purpose of the Reset procedure is to align the resources in eNB1 and eNB2 in the event of an abnormal failure. The procedure resets the whole X2 interface.


7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)18Release 8


eNB 1

RESET REQUEST

eNB 2

RESET RESPONSE

Figure 8.3.4.2-1: Reset, successful operation

The procedure is initiated with a RESET REQUEST message sent from the eNB 1 to the eNB 2. Upon receipt of thismessage, eNB 2 shall abort any other ongoing procedures over X2 between eNB 1 and eNB 2. The eNB 2 shall delete all thecontext information related to the eNB 1 including the X2AP ID for the contexts. After completion of release of theresources, the eNB 2 shall respond with a RESET RESPONSE message.


Void.


If the RESET REQUEST message is received, any other ongoing procedure (except another Reset procedure) on thesame X2 interface shall be aborted.

If Reset procedure is ongoing and eNB receives a RESET REQUEST message from the peer entity on the same X2interface, the eNB shall respond with RESET RESPONSE message as described in 8.3.4.2.

8.3.5 eNB Configuration Update

8.3.5.1 General

The purpose of the eNB Configuration Update procedure is to update application level data needed for two eNBs tointeroperate correctly over the X2 interface.


eNB 1

ENB CONFIGURATION UPDATE

eNB 2

ENB CONFIGURATION UPDATE ACKNOWLEDGE

Figure 8.3.5.2-1: eNB Configuration Update, success ful operation

An eNB initiates the procedure by sending an ENB CONFIGURATION UPDATE to a peer eNB. The initiating eNBexchanges all Served Cell information for cells added or modified, modified cells are also identified by adding the oldCell Global Identifier to the list of Served Cell information. Deleted cells are identified through the old Cell GlobalIdentifier only.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)19Release 8

Upon reception of ENB CONFIGURATION UPDATE, the eNB shall update cell information accordingly and replywith the ENB CONFIGURATION UPDATE ACKNOWLEDGE message to inform the initiating eNB that therequested update of application data was performed successfully. In case the peer eNB receives an ENBCONFIGURATION UPDATE without any Served Cells to add IE, Served Cells to modify IE or Served Cells to delete IE it should reply with ENB CONFIGURATION UPDATE ACKNOWLEDGE message without performing anyupdates to the existing configuration.


eNB 1

ENB CONFIGURATION UPDATE

eNB 2

ENB CONFIGURATION UPDATEFAILURE

Figure 8.3.x.3-1: eNBConfiguration Update, unsuccessful operation

If the eNB can not accept the update it shall respond with an ENB CONFIGURATION UPDATE FAILURE messageand appropriate cause value.

If the ENB CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE the eNB shall wait at leastfor the indicated time before reinitiating the eNB Configuration Update procedure towards the same eNB. Both nodesshall continue to operate the X2 with the existing configuration data.

8.3.6 Resource Status Update Initiation

8.3.6.1 GeneralThis procedure is used by an eNB to request the reporting of load measurements to another eNB.


eNB 1 eNB 2

RESOURCE STATUS REQUEST

RESOURCE STATUS RESPONSE

Figure 8.3.6.2-1: Resource Status Initiation, successful operation

The procedure is initiated with a RESOURCE STATUS REQUEST message sent from eNB1 to eNB2. Upon receipt,eNB2 shall initiate the requested measurement according to the parameters given in the request in case the Registration

Request IE set to “start” and shall terminate the reporting in case the Registration Request IE set to “stop”.

Reporting Periodicity

If Reporting Period IE is included, eNB2 shall use it as the reporting period. If this value is not specified, eNB2 shallapply a default value or shall fail the procedure.

Cell Id List

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)20Release 8

If the cell Id list is included, eNB2 shall perform and report measurements only for the cells included in the list. If thisvalue is not specified, eNB2 shall report all the cells it controls.

Response messageIf eNB2 was able to initiate the measurement requested by eNB1, it shall respond with the RESOURCE STATUSRESPONSE message.


eNB 1 eNB 2

RESOURCE STATUS REQUEST

RESOURCE STATUS FAILURE

Figure 8.3.6.3-1: Resource Status Initiation, unsuccessful operation

If the requested measurement cannot be initiated, eNB2 shall send a RESOURCE STATUS FAILURE message. Themessage shall include the Cause IE set to an appropriate value.


Void

8.3.7 Resource Status Reporting

8.3.7.1 General

This procedure is used by a eNB2 to report the result of measurements requested by eNB1 using the Resource StatusUpdate Initiation.


eNB 1 eNB 2

RESOURCE STATUS UPDATE

Figure 8.3.7.2-1: Resource Status Reporting, successful operation

Report Contents

The eNB2 shall report the results of the measurements in RESOURCE STATUS UPDATE message for each requestedcell.

Editor Note: The report contents are FFS.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)21Release 8

9 Elements for X2AP Communication

9.1 Message Functional Definition and Content

Editors Note: Details on the Connection Management Identifiers is FFS. When general principles and consistencywith S1AP has been decided all X2AP procedures will need to be revised.

9.1.1 Messages for Basic Mobility Procedures

9.1.1.1 HANDOVER REQUEST

This message is sent by the source eNB to the target eNB to request the preparation of resources for a handover.

Direction: source eNB → target eNB.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)22Release 8

IE/Group Name Presence Range IE type andreference

Semanticsdescription

Criticality AssignedCriticality

Message Type M 9.2.15 YES rejectOld eNB UE X2AP ID M INTEGER

(0..4095)eNB UEX2AP IDallocated atthe old eNB

YES reject

Cause M 9.2.8 YES ignoreTarget Cell ID M CGI

9.2.16YES reject

GUMMEI M 9.2.18 YES rejectUE Context Information M YES reject

> MME UE S1AP ID M INTEGER(0..2 32 -1)

MME UES1AP IDallocated atthe MME

– –

> Aggregate MaximumBit Rate

O 9.2.14 – –

> SAE Bearers To BeSetup List

M – –

>> SAE Bearer Info 1 to <maxnoofSAEbearers>

EACH ignore

>>> SAE Bearer ID M BIT STRING(SIZE (8))

– –

>>> SAE BearerLevel QoSParameters

M 9.2.11 InlcudesnecessaryQoSparameters

– –

>>> DL Forwarding O 9.2.7 – –>>> UL GTP TunnelEndpoint

M GTP TunnelEndpoint9.2.1

SGW tunnelendpoint.For delivery

of UL PDUs

– –

> RRC Context M OCTETSTRING

to transferUE RANcontext,details areFFS

– –

>Handover Restriction List O 9.2.5 – –

>Location ReportingInformation

O 9.2.23 Includes thenecessaryparametersfor locationreporting

– –

UE History Information O 9.2.3 YES ignore

Trace activation O 9.2.2 YES ignoreEditors Note: The details of required IEs to transfer RRC context, security information, roaming restriction

information, potentially some user plane related context, etc., are left FFS.

9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE

This message is sent by the target eNB to inform the source eNB about the prepared resources at the target.

Direction: target eNB → source eNB.

Range bound ExplanationmaxnoofSAEbearers Maximum no. of SAE bearers. Value is 256(FFS).

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)23Release 8






YES reject

New eNB UE X2AP ID M INTEGER(0..4095)

New eNBUE X2AP IDallocated atthe new eNB

YES reject

SAE Bearers Admitted List O YES ignore> SAE Bearer Info 1 to <maxnoof

SAEbearers>EACH ignore

>> SAE Bearer ID M BIT STRING(SIZE (8))

– –

>> UL GTP TunnelEndpoint

O GTP TunnelEndpoint

9.2.1

Target eNBtunnelendpoint.For deliveryof UL PDUs

– –

>> DL GTP TunnelEndpoint

O GTP TunnelEndpoint

9.2.1

Target eNBtunnelendpoint.For deliveryof DL PDUs

– –

SAE Bearers Not Admitt edList

O YES ignore

> SAE Bearer Info 1 to <maxnoofSAEbearers>

EACH ignore


– –

>> Cause M 9.2.8 – –

Target eNodeB to SourceeNodeB TransparentContainer

M OCTETSTRING

It includesHO info forthe UE

YES ignore

Criticality Diagnostics O 9.2.9 YES ignore

9.1.1.3 HANDOVER PREPARATION FAILURE

This message is sent by the target eNB to inform the source eNB that the Handover Preparation has failed.







YES reject

Cause M 9.2.8 YES ignoreCriticality Diagnostics O 9.2.9 YES ignore

Range bound ExplanationmaxnoofSAEbearers Maximum no. of SAE bearers. Value is 256(FFS).

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)24Release 8

9.1.1.4 SN STATUS TRANSFER

This message is sent by the source eNB to the target eNB to transfer the uplink/downlink PDCP-SN status during ahandover.





Message Type M 9.2.15 YES ignoreOld eNB UE X2AP ID M INTEGER


YES reject


eNB UEX2AP IDallocated atthe new eNB

YES reject

SAE Bearers Subject toStatus Transfer List

M YES ignore

>SAE Bearers Subject toStatus Transfer Item

1 to <maxnoofSAEbearers>

EACH ignore


– –

>> Receive status of ULPDCP SDUs

O BIT STRING(SIZE

(4096))

PDCPSequenceNumber =(FirstMissing SDUNumber + bitposition)modulo 4096

0: PDCPSDU has notbeenreceived.1: PDCPSDU hasbeenreceivedcorrectly.

– –

>> UL COUNT value M 9.2.17 PDCP-SNand HyperFrameNumber of

the firstmissing ULSDU

– –

>> DL COUNT value M 9.2.17 PDCP-SNand Hyperframenumber thatthe targeteNB shouldassign forthe next DLSDU nothaving anSN yet

– –

Range bound ExplanationmaxnoofSAEbearers Maximum no. of SAE bearers. Value is 256 FFS.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)25Release 8

9.1.1.5 UE CONTEXT RELEASE

This message is sent by the target eNB to the source eNB to indicate that resources can be released.







YES reject


eNB UEX2AP ID

allocated atthe new eNB

YES reject

9.1.1.6 HANDOVER CANCEL

This message is sent by the source eNB to the target eNB to cancel an ongoing handover.







YES reject


eNB UEX2AP IDallocated atthe new eNB

YES reject

Cause M 9.2.8 YES ignore

9.1.2 Messages for global procedures

9.1.2.1 LOAD INFORMATION

This message is sent by an eNB to neighbouring eNBs to transfer load and interference co-ordination information.

Direction: eNB 1 → eNB 2.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)26Release 8




Message Type M 9.2.15 YES ignoreCell Information 1 to

maxCellineNB EACH ignore

>Cell ID M 9.2.16 Id of thesource cell

-

>UL InterferenceOverload Indication

O 9.2.19 -

> UL High InterferenceInformation

0 tomaxCellineNB

-

>>UL HighInterference Indication

M 9.2.20 -

>>Target Cell ID M 9.2.16 Id of thecell for

which theHII is

meant

-

>Maximum Tx Power perPRB normalized

O 9.2.21 -

Range bound ExplanationmaxCellineNB Maximum no. cells that can be served by an eNB. Value is 256 FFS.

9.1.2.2 ERROR INDICATION

This message is used to indicate that some error has been detected in the eNB.

Direction: eNB 1 eNB 2




Message Type M 9.2.15 YES ignoreOld eNB UE X2AP ID O INTEGER(0..4095)

YES ignore

New eNB UE X2AP ID O INTEGER(0..4095)

YES ignore

Cause O 9.2.8 YES ignoreCriticality Diagnostics O 9.2.9 YES ignore

9.1.2.3 X2 SETUP REQUEST

This message is sent by an eNB to a neighbouring eNB to transfer the initialization information for a TNL association.

Direction: eNB 1 eNB 2.




Message Type M 9.2.15 YES rejecteNB Global ID M INTEGER

(0..65535)Coding FFS YES reject

Served Cells 1 tomaxnoofCelline

NB

This is allthe eNB

cells

YES reject

>Served Cell information M 9.2.10 – –GU Group Id List 0 to

maxnoofPoolsThis is all

the pools towhich the

eNB belongsto

YES reject

>GU Group Id M 9.2.22 - -

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)27Release 8

Range bound ExplanationmaxnoofPools Maximum no. of pools an eNB can belong to. Value is 16 FFS.

9.1.2.4 X2 SETUP RESPONSE

This message is sent by an eNB to a neighbouring eNB to transfer the initialization information for a TNL association.





Message Type M 9.2.15 YES rejecteNB Global ID M INTEGER

(0..65535)Coding FFS YES reject

Served Cells 1 tomaxnoofCelline

NB

This is allthe eNB

cells

YES reject

>Served Cell information M 9.2.10 – –GU Group Id List 0 to

maxnoofPools

This is all

the pools towhich theeNB belongs

to

YES reject

>GU Group Id M 9.2.22 - - Criticality Diagnostics O 9.2.9 YES ignore

Range bound ExplanationmaxnoofPools Maximum no. of pools an eNB can belong to. Value is 16 FFS.

9.1.2.5 X2 SETUP FAILURE

This message is sent by the eNB to indicate X2 Setup failure.





Message Type M 9.2.15 YES rejectCause M 9.2.8 YES ignoreTime To Wait O OCTET

STRINGCoding FFS YES ignore


9.1.2.6 RESET REQUEST

This message is sent from one eNB to another eNB and is used to request that the X2 interface between the two eNB to be reset.





Message Type M 9.2.15 YES rejectCause M 9.2.8 YES ignore

9.1.2.7 RESET RESPONSEThis message is sent by a eNB as a response to a RESET REQUEST message.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)28Release 8





Message Type M 9.2.15 YES rejectCriticality Diagnostics O 9.2.9 YES ignore

9.1.2.8 ENB CONFIGURATION UPDATE

This message is sent by an eNB to a peer eNB to transfer updated information for a TNL association.





Message Type M 9.2.15 YES rejectServed Cells to add 0 to

maxnoofCellineNB

GLOBAL reject

>Served Cell information M 9.2.10 – –Served Cells to modify 0 to

maxnoofCellineNB

GLOBAL reject

>Old CGI M 9.2.16 This is theold CellGlobal

Indentfier

- -

>Served Cell information M 9.2.10 – –Served Cells to delete 0 to

maxnoofCellineNB

GLOBAL reject

>Old CGI M 9.2.16 This is theold Cell

GlobalIndentfier ofthe cell to be

deleted

- -

9.1.2.9 ENB CONFIGURATION UPDATE ACKNOWLEDGE

This message is sent by an eNB to a peer eNB to acknowledge update of information for a TNL association.






9.1.2.10 ENB CONFIGURATION UPDATE FAILURE

This message is sent by an eNB to a peer eNB to indicate eNB Configuration Update Failure.


7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)29Release 8




Message Type M 9.2.15 YES rejectCause M 9.2.8 YES ignoreTime to wait M OCTET

STRINGYES ignore


9.1.2.11 RESOURCE STATUS REQUEST

This message is sent by an eNB1 to neighbouring eNB2 to initiate the requested measurement according to the parameters given in the message.

Direction: eNB1 → eNB2.

IE/Grou p Name Presence Range IE type andreference


Cr it ic al it y AssignedCriticality

Message Type M 9.2.15 YES rejectRegistration Request M ENUMERATE

D(Start, Stop)

Cell To Report List 0 tomaxCellineNB

EACH ignore

>Cell ID M 9.2.16 Cell ID list for whichmeasurement is

neededReporting Periodicity O ENUMERATE

D (FFS)Unit: FFSRange:FFS

YES ignore

9.1.2.12 RESOURCE STATUS RESPONSE

This message is sent by the eNB2 to indicate that the requested measurements are successfully initiated. Direction:eNB2 → eNB1.



Cr it ic al it y AssignedCriticality


9.1.2.13 RESOURCE STATUS FAILURE

This message is sent by the eNB2 to indicate requested measurements cannot be initiated.





Message Type M 9.2.15 YES rejectCause M 9.2.8 YES ignoreCriticality Diagnostics O 9.2.9 YES ignore

9.1.2.14 RESOURCE STATUS UPDATE

This message is sent by eNB2 to neighbouring eNB1 to report the results of the requested measurements.

Range bound ExplanationmaxCellineNB Maximum no. cells that can be served by an eNB. Value is 256 FFS

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)30Release 8





Message Type M 9.2.15 YES rejectCell Measurement Result 1 to

maxCellineNB EACH ignore

>Cell ID M 9.2.16> Resource Status O INTEGER The content

is FFS.

9.2 Information Element definitions

9.2.1 GTP Tunnel Endpoint




Transport Layer Address M BIT STRING(SIZE(1..160

, ...))

For detailson theTransportLayer

Address, seeref. [8]

GTP TEID M OCTET

STRING(SIZE (4))

9.2.2 Trace activation

Defines parameters related to trace activation.




Trace Reference M OCTETSTRING (8)

Interfaces To Trace 1 to

<maxInterfaces>>Interface M ENUMERATED (s1, x2Uu, ...)

>Trace depth M ENUMERATED(minimum,medium,maximum,vendorMinimum,vendorMedium,vendorMaximum, ...)

Defined in[7]

Range bound ExplanationmaxCellineNB Maximum no. cells that can be served by an eNB. Value is 256 FFS

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)31Release 8

9.2.3 UE History InformationIE/Group Name Presence Range IE type and

referenceSemanticsdescription


Last Visited Cell L ist 1 to MaxNrOfCells Most recentinformationis added tothe top of

this list

>Last Visited CellInformation

M 9.2.4

Editors Note: Maximum size of the list (MaxNrOfCells) is FFS.

9.2.4 Last Visited Cell InformationIE/Group Name Presence Range IE type and



Global Cell ID M 9.2.16

Cell type M ENUMERATED(macro,micro, pico,

femto)Time UE stayed in cell O INTEGER In seconds

Editors Note: The definition of “Cell Type” is FFS

9.2.5 Handover Restriction listThis IE defines area roaming or access restrictions for handover. If the eNB receives the Handover Restriction List, itshall overwrite previously received restriction information.

Range bound ExplanationmaxInterfaces Maximum no. of Interface. Value is FFS.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)32Release 8




Serving PLMN M 9.2.6 Equivalent PLMNs 0..<maxnoofEPLM

Ns> AllowedPLMNs inaddition toServingPLMN.This listcorrespondsto the list of“equivalentPLMNs” asdefined in[TS 24.008].

>PLMN Identity M 9.2.6Forbidden TAs 0..<maxnoofEPLM

NsPlusOne>intra E-UTRANroamingrestrictions

>PLMN Identity M 9.2.6 The PLMN of

forbiddenTACs

>Forbidden TACs 1..<maxnoofForbT ACs>

>>TAC M OCTETSTRING

TheforbiddenTAC

Forbidden LAs 0..<maxnoofEPLMNsPlusOne>

inter-3GPPRAT roamingrestrictions

>PLMN Identity M 9.2.6>Forbidden LACs 1..<maxnoofForbL

ACs>>>LAC M OCTET

STRING(2)

Forbidden inter RATs O ENUMERATED(ALL,GERAN,

UTRAN, …)

inter-3GPPRAT accessrestrictions

9.2.6 PLMN IdentityThis information element indicates the PLMN Identity.

Range bound ExplanationmaxnoofEPLMNs Maximum no. of equivalent PLMN Ids. Value is 15.maxnooffEPLMNsPlusOne Maximum no. of equivalent PLMN Ids plus one. Value is 16.maxnoofforbiddenTACs Maximum no. of forbidden Tracking Area Codes. Value is 256.maxnoofforbiddenLACs Maximum no. of forbidden Location Area Codes. Value is 256.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)33Release 8


Semantics description

PLMN identity M OCTET STRING(SIZE (3))

- digits 0 to 9, encoded0000 to 1001,- 1111 used as filler digit,two digits per octet,- bits 4 to 1 of octet nencoding digit 2n-1- bits 8 to 5 of octet nencoding digit 2n

-The Selected PLMNidentity consists of 3 digitsfrom MCC followed byeither-a filler digit plus 2 digitsfrom MNC (in case of 2digit MNC) or-3 digits from MNC (in caseof a 3 digit MNC).

9.2.7 DL Forwarding

This element indicates that the SAE bearer is proposed for forwarding of downlink packets.



DL Forwarding M ENUMERATED(DL forwardingproposed, …)

9.2.8 CauseThe purpose of the cause information element is to indicate the reason for a particular event for the whole protocol.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)34Release 8

IE/Group Name Presence Range IE Type and Reference SemanticsDescription

CHOICE Cause Group M>Radio Network Layer

>>Radio Network LayerCause

M ENUMERATED(Unspecified,Handover Desirable for Radio

Reasons,Time Critical Handover,Resource Optimisation Handover,Reduce Load in Serving Cell,Partial Handover,Unknown New eNB UE X2AP ID,Unknown Old eNB UE X2AP ID,Unknown Pair of UE X2AP ID ,HO Target not Allowed,TRELOCoverall Expiry,TRELOCprep Expiry,Cell not Available,No Radio Resources Available inTarget Cell,

Invalid MME Group ID,Unknown MME Code,...)

>Transport Layer>>Transport Layer Cause M ENUMERATED

(Transport Resource Unavailable,Unspecified,...)

>Protocol >>Protocol Cause M ENUMERATED

(Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and

Notify),Message not Compatible withReceiver State,Semantic Error,Unspecified,

Abstract Syntax Error (FalselyConstructed Message),...)

>Misc>>Miscellaneous Cause M ENUMERATED

(Control Processing Overload,Hardware Failure,O&M Intervention,Not enough User PlaneProcessing Resources,Unspecified,...)

The meaning of the different cause values is described in the following table. In general, "not supported" cause valuesindicate that the concerned capability is missing. On the other hand, "not available" cause values indicate that theconcerned capability is present, but insufficient resources were available to perform the requested action.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)35Release 8

Radio Network Layer cause MeaningHandover Desirable for RadioReasons

The reason for requesting handover is radio related.

Time Critical Handover handover is requested for time critical reason i.e. this cause value isreserved to represent all critical cases where the connection is likely to bedropped if handover is not performed.

Resource Optimisation Handover The reason for requesting handover is to improve the load distributionwith the neighbour cells.

Reduce Load in Serving Cell Load on serving cell needs to be reduced.Partial Handover Provides a reason for the handover cancellation. The target eNB did not

admit all SAE Bearers included in the HANDOVER REQUEST and thesource eNB estimated service continuity for the UE would be better by notproceeding with handover towards this particular target eNB.

Unknown New eNB UE X2AP ID The action failed because the New eNB UE X2AP ID is unknownUnknown Old eNB UE X2AP ID The action failed because the Old eNB UE X2AP ID is unknownUnknown Pair of UE X2AP ID The action failed because the pair of UE X2 AP IDs is unknownHandover Target not Allowed Handover to the indicated target cell is not allowed for the UE in questionTRELOCoverall Expiry The reason for the action is expiry of timer T RELOCoverall TRELOCprep Expiry Handover Preparation procedure is cancelled when timer T RELOCprep

expires.Cell not Available The concerned cell is not available.No Radio Resources Available inTarget Cell

The target cell doesn’t have sufficient radio resources available.

Invalid MME Group ID The target eNB doesn’t belong to the same pool area of the source eNBi.e. S1 handovers should be attempted instead.

Unknown MME Code The target eNB belongs to the same pool area of the source eNB andrecognizes the MME Group ID. However, the MME Code is unknown tothe target eNB.

Unspecified Sent when none of the above cause values applies but still the cause isRadio Network Layer related

Transport Network Layer cause MeaningTransport resource unavailable The required transport resources are not availableUnspecified Sent when none of the above cause values applies but still the cause is

Transport Network Layer related

Protoco l cause Meaning Abstract Syntax Error (Reject) The received message included an abstract syntax error and the

concerned criticality indicated "reject" (see subclause 10.3) Abstract Syntax Error (Ignore andNotify)

The received message included an abstract syntax error and theconcerned criticality indicated "ignore and notify" (see subclause 10.3)

Abstract syntax error (falselyconstructed message)

The received message contained IEs or IE groups in wrong order or withtoo many occurrences (see subclause 10.3)

Message not Compatible withReceiver State

The received message was not compatible with the receiver state (seesubclause 10.4)

Semantic Error The received message included a semantic error (see subclause 10.4)Transfer Syntax Error The received message included a transfer syntax error (see subclause

10.2)Unspecified Sent when none of the above cause values applies but still the cause is

Protocol related

Miscellaneous cause MeaningControl Processing Overload eNB control processing overloadHardware Failure eNB hardware failureNot enough User Plane ProcessingResources

eNB has insufficient user plane processing resources available

O&M Intervention Operation and Maintenance intervention related to eNB equipmentUnspecified Sent when none of the above cause values applies and the cause is not

related to any of the categories Radio Network Layer, Transport NetworkLayer or Protocol.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)36Release 8

9.2.9 Criticality DiagnosticsThe Criticality Diagnostics IE is sent by the RNC or the CN when parts of a received message have not beencomprehended or were missing, or if the message contained logical errors. When applicable, it contains informationabout which IEs were not comprehended or were missing.

IE/Group Name Presence Range IE type andreference Semantics descripti on

Criticality Diagnostics>Procedure Code O INTEGER

(0..255)Procedure Code is to be usedif Criticality Diagnostics is partof Error Indication procedure,and not within the responsemessage of the sameprocedure that caused theerror

>Triggering Message O ENUMERATED(initiatingmessage,successfuloutcome,unsuccessfuloutcome,outcome)

The Triggering Message isused only if the CriticalityDiagnostics is part of ErrorIndication procedure.

>Procedure Criticality O ENUMERATED(reject,ignore,notify)

This Procedure Criticality isused for reporting theCriticality of the Triggeringmessage (Procedure).

Information ElementCriticality Diagnostics

0 to <maxnooferrors>

>IE Criticality M ENUMERATED(reject,ignore,notify)

The IE Criticality is used forreporting the criticality of thetriggering IE. The value'ignore' shall not be used.

>IE ID M INTEGER(0..65535)

The IE ID of the notunderstood or missing IE

>Type of Error M ENUMERATED(notunderstood,missing, …)

Range bound Explanationmaxnooferrors Maximum no. of IE errors allowed to be reported with a single

message. The value for maxnooferrors is 256.

9.2.10 Served Cell InformationIE/Group Name Presence Range IE type and



PhyCID M OCTETSTRING

Physical CellID

-

Cell ID M CGI9.2.16

-

TAC M OCTETSTRING

Tracking Area Code

-

Broadcast PLMNs 1..<maxnoofBPLMNs>

BroadcastPLMNs

-

>PLMN Identity M 9.2.6 -Frequency M OCTET

STRING(Center

frequencyand/or

frequencyband)

-

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)37Release 8

9.2.11 SAE Bearer Level QoS ParametersThis IE defines the QoS to be applied to a SAE bearer.


Semantics descripti on

SAE Bearer Level QoSParameters

>QCI M INTEGER(1..256)

Coded as specified in TS23.401, which will be definedin SA2

>Allocation and RetentionPriority

M (FFS) OCTETSTRING

The ARP definition is left FFSin SA2.

>SAE Bearer Type M 9.2.12Either GBR or non-GBRBearer

9.2.12 SAE Bearer TypeIE/Group Name Presence Range IE type and

referenceSemantics descripti on

Choice SAE Bearer Type > SAE GBR bearer

>> SAE Bearer MaximumBit Rate Downlink

M SAE BearerBit Rate9.2.13

to be added

>> SAE Bearer MaximumBit Rate Uplink


to be added

>> SAE BearerGuaranteed Bit RateDownlink


to be added

>> SAE BearerGuaranteed Bit RateUplink


to be added

>SAE Non-GBR bearer>> Non GBR bearer ENUMERAT

ED (NonGBR

bearer,…)

9.2.13 SAE Bearer Bit RateIE/Group Name Presence Range IE type and


SAE Bearer Bit Rate M INTEGER(0..10,000,0

00,000)

This IE indicates the numberof bits delivered by E-UTRANand to E-UTRAN within aperiod of time, divided by theduration of the period.The unit is: bit/s

Range bound ExplanationmaxnoofBPLMNs Maximum no. of Broadcast PLMN Ids. Value is FFS.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)38Release 8

9.2.14 Aggregate Maximum Bit RateIE/Group Name Presence Range IE type and


Aggregat e Maximum Bi tRate

Applicable for non-GBR SAEBearers, provided at initialcontext setup

>Aggregate Maximum BitRate Downlink


to be added

>Aggregate Maximum BitRate Uplink


to be added

9.2.15 Message TypeThe Message Type IE uniquely identifies the message being sent. It is mandatory for all messages.

IE/Group Name Presence Range IE type and reference Semantics descr ip tionMessage Type Assumed max no of messages

is 256.>Procedure Code M (Handover Preparation,

SN Status Transfer,Release Resource,Handover Cancel, LoadIndication, ErrorIndication, X2 Setup,Reset,…)

>Type of Message M CHOICE(Initiating Message,Successful Outcome,Unsuccessful Outcome,Outcome,…)

9.2.16 CGI

9.2.17 COUNT value




PDCP-SN M INTEGER(0..4095)

– –

HFN M INTEGER(0..1048575) – –




CGI -

> PLMN identity M 9.2.6 -> LAC M OCTETSTRING (2)

0000 and FFFE notallowed.

-

>CI M OCTETSTRING (2)

-

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)39Release 8

9.2.18 GUMMEIThis information element indicates the global unique MME identity.



GUMMEI>GU Group ID M 9.2.22>MME code M OCTET STRING

(SIZE(1))

9.2.19 UL Interference Overload IndicationThis IE provides, per PRB, a report on interference overload. The interaction between the indication of UL InterferenceOverload and UL High Interference is implementation specific.



UL Interference OverloadIndication List

0 to<maxnoofPRBs>

>UL Interference OverloadIndication

M ENUMERATED(highinterference,mediuminterference, lowinterference, …)

Each PRB is identified byits position in the list: thefirst element in the listcorresponds to PRB 0, thesecond to PRB 1, etc.

Range bound ExplanationmaxnoofPRBs Maximum no. Physical Resource Blocks. Value is 100 or 110 (FFS).

9.2.20 UL High Interference IndicationThis IE provides, per PRB, a 2 level report on interference sensitivity. The interaction between the indication of ULOverload and UL High Interference is implementation specific.



HII O BIT STRING(SIZE (1..110,…))

Each position in the bitmaprepresents a PRB (firstbit=PRB 0 and so on), forwhich value ‘1’ indicates‘high interferencesensitivity’ and value ‘0’indicates ’low interferencesensitivity’.The maximum number ofPhysical Resource Blocksis 100 or 110 (FFS)

9.2.21 Maximum Tx Power per PRB normalizedThis IE provides per PRB an indication whether DL PRBs transmission power exceeds a threshold.

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)40Release 8



DL Tx Power per PRB O BIT STRING(SIZE (1..110,…))

Each position in the bitmaprepresents a PRB (firstbit=PRB 0 and so on), forwhich value ‘1’ indicates‘Tx exceeding threshold’and value ‘0’ indicates ‘Txnot exceeding threshold’.The maximum number ofPhysical Resource Blocksis 100 or 110 (FFS)

9.2.22 GU Group IdThe GU Group Id IE is the globally unique group id corresponding to a pool area.




GU Group Id

>PLMN Id M 9.2.6

>MME Group Id M OCTETSTRING

( SIZE(2) )

9.2.23 Location Reporting InformationThis information element indicates how the location information should be reported.



Location ReportingRequest Information

>Event M ENUMERATED(Change ofserving cell, …)

>Report Area M ENUMERATED(E-UTRAN CGI,…)

7/18/2019 3GPP TS 36.423.pdf


7/18/2019 3GPP TS 36.423.pdf


3GPP

42Release 8- -- - **************************************************************

X2AP- PDU- Descr i pt i ons {i t u- t ( 0) i dent i f i ed- organi zat i on ( 4) et s i ( 0) mobi l eDomai n (0)eps- Access ( 21) modul es ( 3) x2ap ( 2) ver si on1 (1) x2ap- PDU- Descri pt i ons ( 0) }

DEFI NI TI ONS AUTOMATI C TAGS : : =

BEGI N

- - **************************************************************- -- - I E paramet er t ypes f r omot her modul es.- -- - **************************************************************

I MPORTSCr i t i cal i t y,Pr ocedureCode

FROM X2AP- CommonDat aTypes

Er r or I ndi cat i on,HandoverRequest ,Handover Request Acknowl edge,Handover Preparat i onFai l ur e,SNSt atusTr ansf er ,UECont ext Rel ease,HandoverCancel ,LoadI nf ormati on,ResetRequest ,Reset Response,X2Set upRequest ,X2Set upResponse,X2Set upFai l ur e,ENBConf i gur at i onUpdat e,ENBConf i gur at i onUpdat eAcknowl edge,ENBConf i gur ati onUpdat eFai l ur e,Resour ceSt at usRequest ,Resour ceSt at usResponse,Resour ceSt atusFai l ur e,

ResourceStat usUpdat e

FROM X2AP- PDU- Cont ent s

i d- er r or I ndi cat i on,i d- handover Preparat i on,i d- snSt at usTransf er,i d- uECont ext Rel ease,i d- handoverCancel ,

7/18/2019 3GPP TS 36.423.pdf


3GPP

43Release 8i d- l oadI ndi cat i on,i d- r es et ,i d- x2Set up,i d- eNBConf i gur ati onUpdat e,i d- r esour ceSt atusUpdat eI ni t i at i on,i d- r esour ceSt atusReport i ng

FROM X2AP- Const ant s;

- - **************************************************************- -- - I nt erf ace El ement ary Procedur e Cl ass- -- - **************************************************************

X2AP- ELEMENTARY- PROCEDURE : : = CLASS {&I ni t i ati ngMessage ,&Successf ul Out come OPTI ONAL,&Unsuccessf ul Out come OPTI ONAL,&pr ocedur eCode Pr ocedureCode UNI QUE,&cri t i cal i t y Cri t i cal i t y DEFAULT i gnor e

}WI TH SYNTAX {

I NI TI ATI NG MESSAGE &I ni t i at i ngMessage[ SUCCESSFUL OUTCOME &Successf ul Out come][ UNSUCCESSFUL OUTCOME &Unsuccessf ul Out come]PROCEDURE CODE &pr ocedur eCode[ CRI TI CALI TY &cri t i cal i t y]

}

- - **************************************************************- -- - I nt er f ace PDU Def i ni t i on- -- - **************************************************************

X2AP- PDU : : = CHOI CE {i ni t i ati ngMessage I ni t i at i ngMessage,success f ul Out come Success f ul Out come,unsuccess f ul Out come Unsuccessf ul Out come,

. . .}

I ni t i at i ngMessage : : = SEQUENCE {pr ocedur eCode X2AP- ELEMENTARY- PROCEDURE. &pr ocedur eCode ( {X2AP- ELEMENTARY- PROCEDURES}) ,cr i t i cal i t y X2AP- ELEMENTARY- PROCEDURE. &cr i t i cal i t y ( {X2AP- ELEMENTARY- PROCEDURES}{@pr ocedur eCode}) ,val ue X2AP- ELEMENTARY- PROCEDURE. &I ni t i at i ngMess age ( {X2AP- ELEMENTARY- PROCEDURES}{@pr ocedur eCode})

}

Success f ul Out come : : = SEQUENCE {pr ocedur eCode X2AP- ELEMENTARY- PROCEDURE. &pr ocedur eCode ( {X2AP- ELEMENTARY- PROCEDURES}) ,

7/18/2019 3GPP TS 36.423.pdf


3GPP

44Release 8cr i t i cal i t y X2AP- ELEMENTARY- PROCEDURE. &cr i t i cal i t y ( {X2AP- ELEMENTARY- PROCEDURES}{@pr ocedur eCode}) ,val ue X2AP- ELEMENTARY- PROCEDURE. &Successf ul Out come ( {X2AP- ELEMENTARY- PROCEDURES}{@pr ocedur eCode})

}

Unsuccessf ul Out come : : = SEQUENCE {pr ocedur eCode X2AP- ELEMENTARY- PROCEDURE. &pr ocedur eCode ( {X2AP- ELEMENTARY- PROCEDURES}) ,cr i t i cal i t y X2AP- ELEMENTARY- PROCEDURE. &cr i t i cal i t y ( {X2AP- ELEMENTARY- PROCEDURES}{@pr ocedur eCode}) ,val ue X2AP- ELEMENTARY- PROCEDURE. &Unsuccessf ul Out come ( {X2AP- ELEMENTARY- PROCEDURES}{@pr ocedur eCode})

}

- - **************************************************************- -- - I nt erf ace El ement ary Pr ocedur e Li st- -- - **************************************************************

X2AP- ELEMENTARY- PROCEDURES X2AP- ELEMENTARY- PROCEDURE : : = {X2AP- ELEMENTARY- PROCEDURES- CLASS- 1 |X2AP- ELEMENTARY- PROCEDURES- CLASS- 2 ,. . .

}

X2AP- ELEMENTARY- PROCEDURES- CLASS- 1 X2AP- ELEMENTARY- PROCEDURE : : = {handoverPr eparat i on |r e set |x2Set up |r esour ceSt atusUpdat eI ni t i at i on |eNBConf i gur at i onUpdat e ,. . .

}

X2AP- ELEMENTARY- PROCEDURES- CLASS- 2 X2AP- ELEMENTARY- PROCEDURE : : = {snSt at usTr ansf er |uECont ext Rel ease |handover Cancel |er r or I ndi cat i on |r esour ceSt atusRepor t i ng | l oadI ndi cat i on ,. . .

}

- - **************************************************************- -- - I nt erf ace El ement ary Pr ocedur es- -- - **************************************************************

handoverPr eparat i on X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE Handover RequestSUCCESSFUL OUTCOME Handover Request Acknowl edgeUNSUCCESSFUL OUTCOME Handover Pr epar at i onFai l ur e

7/18/2019 3GPP TS 36.423.pdf


3GPP

45Release 8PROCEDURE CODE i d- handoverPr eparat i onCRI TI CALI TY r ej ect

}

snSt at usTr ansf er X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE SNSt at usTr ansf erPROCEDURE CODE i d- snSt at usTr ansf erCRI TI CALI TY i gnore

}

uECont ext Rel ease X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE UECont ext Rel easePROCEDURE CODE i d- uECont ext Rel easeCRI TI CALI TY i gnore

}

handover Cancel X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE Handover CancelPROCEDURE CODE i d- handover CancelCRI TI CALI TY i gnore

}

er r or I ndi cat i on X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE Err orI ndi cati onPROCEDURE CODE i d- er r or I ndi cat i onCRI TI CALI TY i gnore

}

r eset X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE Reset RequestSUCCESSFUL OUTCOME Reset Respons ePROCEDURE CODE i d- r esetCRI TI CALI TY r ej ect

}

x2Set up X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE X2Set upRequestSUCCESSFUL OUTCOME X2Set upResponseUNSUCCESSFUL OUTCOME X2Set upFai l ur ePROCEDURE CODE i d- x2Set upCRI TI CALI TY r ej ect

}

l oadI ndi cat i on X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE LoadI nf or mat i onPROCEDURE CODE i d- l oadI ndi cat i onCRI TI CALI TY i gnore

}

eNBConf i gurat i onUpdat e X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE ENBConf i gur at i onUpdat e

7/18/2019 3GPP TS 36.423.pdf


3GPP

46Release 8SUCCESSFUL OUTCOME ENBConf i gur at i onUpdat eAcknowl edgeUNSUCCESSFUL OUTCOME ENBConf i gur at i onUpdat eFai l ur ePROCEDURE CODE i d- eNBConf i gurat i onUpdat eCRI TI CALI TY r ej ect

}

r esour ceSt at usUpdat eI ni t i at i on X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE Resourc eSt at usRequestSUCCESSFUL OUTCOME Resour ceSt at usResponseUNSUCCESSFUL OUTCOME Resour ceSt at usFai l ur ePROCEDURE CODE i d- r esour ceSt at usUpdat eI ni t i at i onCRI TI CALI TY r ej ect

}

r esourceSt at usRepor t i ng X2AP- ELEMENTARY- PROCEDURE : : = {I NI TI ATI NG MESSAGE Resourc eSt at usUpdat ePROCEDURE CODE i d- r esour ceSt at usRepor t i ngCRI TI CALI TY i gnore

}

END

9.3.4 PDU Definitions- - **************************************************************- -- - PDU def i ni t i ons f or X2AP.- -- - **************************************************************

X2AP- PDU- Cont ent s {i t u- t ( 0) i dent i f i ed- organi zat i on ( 4) et s i ( 0) mobi l eDomai n (0)eps- Access ( 21) modul es ( 3) x2ap ( 2) ver si on1 ( 1) x2ap- PDU- Cont ent s ( 1) }


BEGI N


I MPORTSAggregateMaxi mumBi t Rat e,Bearer - I D,Cause,CGI ,COUNTval ue,Cr i t i cal i tyDi agnos t i cs,

7/18/2019 3GPP TS 36.423.pdf


3GPP

47Release 8DL- For wardi ng,ENB- Gl obal - I D,GUGr oupI DLi st ,GUMMEI ,Handover Rest r i cti onLi st ,

MaxTxPower PRBNor m,Locat i onReport i ngI nf ormati on,PDCP- SN,PLMN- I dent i t y,UE- S1AP- I D,Recei veSt at usof ULPDCPSDUs,Regi st r at i on- Request ,RRC- Cont ext ,SAE- Bear erLevel - QoS- Par ameter s,Ser vedCel l - I nf or mat i on,Ser vedCel l s,

Ti meToWai t , Tr aceAct i vat i on, Tar get eNBtoSour ce- eNBTr anspar ent Cont ai ner , Tr aceDept h, Tr aceRef er ence, Tr anspor t Layer Address ,UE- Hi st or yI nf ormati on,UL- I nt er f er enceOver l oadI ndi cat i on,UL- Hi ghI nt er f er enceI ndi cat i onI nf o,GTPt unnel Endpoi nt ,UE- X2AP- I D

FROM X2AP- I Es

Pr i vat eI E- Cont ai ner {},Prot ocol Extensi onCont ai ner{},Protocol I E- Cont ai ner Li st{},Pr otocol I E- Cont ai ner Pai r {},Protocol I E- Cont ai ner Pai rLi st{},Pr otocol I E- Cont ai ner {},Pr otocol I E- Si ngl e- Cont ai ner {},X2AP- PRI VATE- I ES,X2AP- PROTOCOL- EXTENSI ON,X2AP- PROTOCOL- I ES,X2AP- PROTOCOL- I ES- PAI R

FROM X2AP- Cont ai ner s

i d- Bearers- Admi t t ed- I t em,i d- Bearers- Admi t t ed- Li st ,i d- Bearers- NotAdmi t t ed- I t em,i d- Bearer s- Not Admi t t ed- Li st ,i d- Bearer s- Subj ectToSt at usTr ansf er - Li st ,i d- Bearer s- Subj ectToSt at usTr ansf er - I t em,i d- Cause,i d- Cel l ToRepor t ,i d- Cel l ToRepor t - I t em,i d- Cel l Measurement Resul t ,

7/18/2019 3GPP TS 36.423.pdf


3GPP

48Release 8i d- Cel l Measurement Resul t - I t em,i d- Cel l I nf ormat i on,i d- Cel l I nf ormat i on- I t em,i d- Cr i t i c al i t y Di agnos t i cs ,i d- ENB- Gl obal - I D,i d- GUGr oupI DLi st ,i d- GUMMEI - I D,i d- UE- Cont ext I nf ormati on,i d- Bearers- ToBeSetup- I t em,i d- New- eNB- UE- X2AP- I D,i d- Ol d- eNB- UE- X2AP- I D,i d- Regi st r ati on- Request ,i d- Report i ngPeri odi ci t y,i d- Ser vedCel l s ,i d- Target Cel l - I D,i d- Tar geteNBt oSour ce- eNBTransparentCont ai ner ,i d- Ti meToWai t ,i d- TraceActi vat i on,i d- UE- Hi st oryI nf ormati on,i d- UE- X2AP- I D,i d- Ser vedCel l sToAdd,i d- Ser vedCel l sToModi f y,i d- Ser vedCel l sToDel ete,

maxnoof Bear ers ,maxnoof PDCP- SN,maxCel l i neNB

FROM X2AP- Const ant s;

- - **************************************************************- -- - HANDOVER REQUEST- -- - **************************************************************

Handover Request : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{Handover Request - I Es}},. . .

}

HandoverRequest - I Es X2AP- PROTOCOL- I ES : : = {

{ I D i d- Ol d- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D PRESENCE mandat or y } |{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE mandator y } |{ I D i d- Target Cel l - I D CRI TI CALI TY r ej ect TYPE CGI PRESENCE mandat or y } |{ I D i d- GUMMEI - I D CRI TI CALI TY r ej ect TYPE GUMMEI PRESENCE mandat or y } |{ I D i d- UE- Cont extI nf or mat i on CRI TI CALI TY r ej ect TYPE UE- Cont ext I nf or mat i on PRESENCE mandat or y } |{ I D i d- UE- Hi st oryI nf ormat i on CRI TI CALI TY i gnore TYPE UE- Hi st oryI nf ormat i on PRESENCE opt i onal } |{ I D i d- TraceAct i vat i on CRI TI CALI TY i gnore TYPE TraceAct i vat i on PRESENCE opt i onal } ,. . .

}

UE- Cont ext I nf or mat i on : : = SEQUENCE {

7/18/2019 3GPP TS 36.423.pdf


3GPP

49Release 8mME- UE- S1AP- I D UE- S1AP- I D,aggr egateMaxi mumBi t Rat e Aggregat eMaxi mumBi t Rat e OPTI ONAL,bearers- ToBeSetup- Li st Bearers- ToBeSetup- Li st ,r RC- Cont ext RRC- Cont ext ,

l ocati onReport i ngI nf ormati on Locat i onReport i ngI nf ormati on OPTI ONAL,handover Rest r i ct i onLi st Handover Rest r i ct i onLi st OPTI ONAL,

i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {UE- Cont ext I nf ormat i on- Ext I Es} } OPTI ONAL,. . .

}

UE- Cont ext I nf or mat i on- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

Bear ers- ToBeSetup- Li st : : = SEQUENCE ( SI ZE( 0. . maxnoof Bear ers) ) OF Pr ot ocol I E- Si ngl e- Cont ai ner { {Bear ers- ToBeSetup- I t emI Es} }

Bear ers - ToBeSet up- I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Bear ers- ToBeSetup- I t em CRI TI CALI TY i gnore TYPE Bear ers- ToBeSetup- I t em PRESENCE mandat ory },. . .

}

Bear ers- ToBeSetup- I t em : : = SEQUENCE {sAE- Bear er- I D Bearer- I D,sAE- Bear er Level - QoS- Paramet er s SAE- Bear erL evel - QoS- Paramet er s,dL- For war di ng DL- For war di ng OPTI ONAL,uL- GTPtunnel Endpoi nt GTPt unnel Endpoi nt,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {Bear ers- ToBeSetup- I t emExt I Es} } OPTI ONAL,. . .

}

Bear er s- ToBeSet up- I t emExt I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

- - **************************************************************- -- - HANDOVER REQUEST ACKNOWLEDGE- -

- - **************************************************************Handover Request Acknowl edge : : = SEQUENCE {

prot ocol I Es Prot ocol I E- Cont ai ner {{HandoverRequest Acknowl edge- I Es}},. . .

}

HandoverRequest Acknowl edge- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Ol d- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D { I D i d- New- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D { I D i d- Bear ers- Admi t t ed- Li st CRI TI CALI TY i gnor e TYPE Bear ers- Admi t t ed- Li st

7/18/2019 3GPP TS 36.423.pdf


3GPP

50Release 8{ I D i d- Bear ers- NotAdmi t t ed- Li st CRI TI CALI TY i gnore TYPE Bear ers- NotAdmi t t ed- Li st { I D i d- Target eNBt oSour ce- eNBTr ansparent Cont ai ner CRI TI CALI TY i gnor e TYPE Target eNBt oSour ce- eNBTr ansparent Cont ai ner PR{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs

. . .}

Bear er s- Admi t t ed- Li st : : = SEQUENCE ( SI ZE ( 1. . maxnoof Bear er s) ) OF Prot ocol I E- Si ngl e- Cont ai ner { {Bear er s- Admi t t ed- I t emI Es} }

Bear ers - Admi t t ed- I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Bearers- Admi t t ed- I t em CRI TI CALI TY i gnore TYPE Bearers- Admi t t ed- I t em PRESENCE mandator y }

}

Bear ers- Admi t t ed- I t em : : = SEQUENCE {bearer - I D Bear er - I D,uL- GTP- Tunnel Endpoi nt GTPt unnel Endpoi nt OPTI ONAL,dL- GTP- Tunnel Endpoi nt GTPt unnel Endpoi nt OPTI ONAL,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {Bear ers- Admi t t ed- I t em- Ext I Es} } OPTI ONAL,. . .

}

Bear ers - Admi t t ed- I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

Bear ers- Not Admi t t ed- Li st : : = SEQUENCE ( SI ZE ( 1. . maxnoof Bear ers) ) OF Prot ocol I E- Si ngl e- Cont ai ner { {Bear ers- Not Admi t t ed- I t emI

Bear ers - Not Admi t t ed- I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Bearers- NotAdmi t t ed- I t em CRI TI CALI TY i gnore TYPE Bearers- NotAdmi t t ed- I t em PRESENCE mandator y }

}

Bear ers- Not Admi t t ed- I t em : : = SEQUENCE {bearer - I D Bear er - I D,cause Cause,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {Bear ers- Not Admi t t ed- I t em- Ext I Es} } OPTI ONAL,. . .

}

Bear ers - Not Admi t t ed- I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

- - **************************************************************- -- - HANDOVER PREPARATI ON FAI LURE- -- - **************************************************************

HandoverPr epar at i onFai l ure : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{Handover Preparat i onFai l ur e- I Es}},. . .

}

7/18/2019 3GPP TS 36.423.pdf


3GPP

51Release 8

Handover Preparat i onFai l ure- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Ol d- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D PRESENCE mandat or y} |{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE mandat or y} |{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },

. . .}

- - **************************************************************- -- - SN St atus Tr ansf er- -- - **************************************************************

SNSt at usTransf er : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{SNSt atusTr ansf er - I Es}},. . .

}

SNSt atusTr ansf er- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Ol d- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D { I D i d- New- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D { I D i d- Bear ers- Subj ect ToSt at usTr ansf er- Li st CRI TI CALI TY i gnore TYPE Bear ers - Subj ectToSt at usTr ansf er- Li st PRESENCE . . .

}

Bear er s- Subj ect ToSt atusTr ansf er - Li st : : = SEQUENCE ( SI ZE ( 1. . maxnoof Bearers) ) OF Prot ocol I E- Si ngl e- Cont ai ner { { Bear ers- Subj ect ToI t emI Es} }

Bear ers- Subj ectToSt at usTr ansf er- I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Bearers- Subj ect ToSt atusTr ansf er - I t em CRI TI CALI TY i gnore TYPE Bear ers- Subj ect ToSt atusTr ansf er - I t em PRESENCE mand

}

Bear er s- Subj ect ToSt atusTr ansf er - I t em: : = SEQUENCE {bearer - I D Bear er - I D,

r ecei veSt at usof ULPDCPSDUs Recei veSt at usof ULPDCPSDUs OPTI ONAL,uL- COUNTval ue COUNTval ue,dL- COUNTval ue COUNTval ue,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {Bear ers - Subj ectToSt at usTr ansf er- I t emExt I Es} } OPTI ONAL. . .

}Bear ers - Subj ect ToSt at usTransf er- I t emExt I Es X2AP- PROTOCOL- EXTENSI ON : : = {

. . .}

- - **************************************************************

7/18/2019 3GPP TS 36.423.pdf


3GPP

52Release 8- -- - UE Cont ext Rel ease- -- - **************************************************************

UEContext Rel ease : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{UECont extRel ease- I Es}},. . .

}

UECont extRel ease- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Ol d- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D PRESENCE mandat or y} |{ I D i d- New- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D PRESENCE mandator y} ,. . .

}

- - **************************************************************- -- - HANDOVER CANCEL- -- - **************************************************************

Handover Cancel : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{Handover Cancel - I Es}},. . .

}

HandoverCancel - I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Ol d- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D PRESENCE mandat or y} |{ I D i d- New- eNB- UE- X2AP- I D CRI TI CALI TY r ej ect TYPE UE- X2AP- I D PRESENCE mandator y} |{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE mandat or y} ,. . .

}

- - **************************************************************- -- - ERROR I NDI CATI ON- -- - **************************************************************

Er r orI ndi cat i on : : = SEQUENCE {

pr otocol I Es Pr ot ocol I E- Cont ai ner {{Er r or I ndi cat i on- I Es}},. . .}

Er r orI ndi cat i on- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Ol d- eNB- UE- X2AP- I D CRI TI CALI TY i gnor e TYPE UE- X2AP- I D PRESENCE opt i onal } |{ I D i d- New- eNB- UE- X2AP- I D CRI TI CALI TY i gnor e TYPE UE- X2AP- I D PRESENCE opt i onal } |{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE opt i onal } |{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal } ,. . .

}

7/18/2019 3GPP TS 36.423.pdf


3GPP

53Release 8

- - **************************************************************- -- - Reset Request- -- - **************************************************************

Reset Request : : = SEQUENCE {

pr otocol I Es Prot ocol I E- Cont ai ner {{ResetRequest - I Es}},. . .}

Reset Request - I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE mandat or y },. . .

}

- - **************************************************************- -- - Reset Response- -- - **************************************************************

Reset Response : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{ResetResponse- I Es}},. . .

}

Reset Response- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },. . .

}

- - **************************************************************- -- - X2 SETUP REQUEST- -- - **************************************************************

X2Set upRequest : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{X2Set upRequest - I Es}},

. . .}

X2Set upRequest - I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- ENB- Gl obal - I D CRI TI CALI TY r ej ect TYPE ENB- Gl obal - I D PRESENCE mandat or y} |{ I D i d- Ser vedCel l s CRI TI CALI TY r ej ect TYPE Ser vedCel l s PRESENCE mandat or y} |{ I D i d- GUGr oupI DLi st CRI TI CALI TY r ej ect TYPE GUGr oupI DLi st PRESENCE opt i onal },

. . .}

7/18/2019 3GPP TS 36.423.pdf


3GPP

54Release 8

- - **************************************************************- -- - X2 SETUP RESPONSE- -- - **************************************************************

X2Set upResponse : : = SEQUENCE {prot ocol I Es Prot ocol I E- Cont ai ner {{X2Set upResponse- I Es}},. . .

}

X2Set upResponse- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- ENB- Gl obal - I D CRI TI CALI TY r ej ect TYPE ENB- Gl obal - I D PRESENCE mandat or y} |{ I D i d- Ser vedCel l s CRI TI CALI TY r ej ect TYPE Ser vedCel l s PRESENCE mandat or y} |{ I D i d- GUGr oupI DLi st CRI TI CALI TY r ej ect TYPE GUGr oupI DLi st PRESENCE opt i onal }|{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },

. . .}

- - **************************************************************- -- - X2 SETUP FAI LURE- -- - **************************************************************

X2Set upFai l ure : : = SEQUENCE {pr otocol I Es Pr ot ocol I E- Cont ai ner {{X2Set upFai l ur e- I Es}},. . .

}

X2SetupFai l ur e- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE mandat or y} |{ I D i d- Ti meToWai t CRI TI CALI TY i gnor e TYPE Ti meToWai t PRESENCE opt i onal } |{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },

. . .}

- - **************************************************************- -- - LOAD I NFORMATI ON- -- - **************************************************************

LoadI nf or mat i on : : = SEQUENCE {pr otocol I Es Pr ot ocol I E- Cont ai ner {{LoadI nf ormati on- I Es}},

7/18/2019 3GPP TS 36.423.pdf


3GPP

55Release 8. . .

}

LoadI nf ormati on- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cel l I nf ormat i on CRI TI CALI TY i gnore TYPE Cel l I nf ormat i on- Li st PRESENCE mandat ory} ,. . .

}

Cel l I nf ormati on- Li st : : = SEQUENCE ( SI ZE ( 1. . maxCel l i neNB) ) OF Prot ocol I E- Si ngl e- Cont ai ner { {Cel l I nf ormati on- I t emI Es} }

Cel l I nf ormati on- I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cel l I nf or mat i on- I t em CRI TI CALI TY i gnor e TYPE Cel l I nf or mat i on- I t em PRESENCE mandatory }

}

Cel l I nf ormati on- I t em : : = SEQUENCE {gl obal - Cel l - I D CGI ,ul - I nt er f er enceOver l oadI ndi cat i on UL- I nt erf erenceOver l oadI ndi cat i on OPTI ONAL,ul - Hi ghI nt er f er enceI ndi cat i onI nf o UL- Hi ghI nt er f er enceI ndi cat i onI nf o OPTI ONAL,maxTxPower PRBNor m MaxTxPower PRBNor m OPTI ONAL,i E- Extensi ons Prot ocol Extensi onCont ai ner { {Cel l I nf ormati on- I t em- ExtI Es} } OPTI ONAL,. . .

}

Cel l I nf ormati on- I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

- - **************************************************************- -- - ENB CONFI GURATI ON UPDATE- -- - **************************************************************

ENBConf i gur at i onUpdat e : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{ENBConf i gur ati onUpdate- I Es}},. . .

}

ENBConf i gur at i onUpdat e- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Ser vedCel l sToAdd CRI TI CALI TY r ej ect TYPE ServedCel l s PRESENCE opt i onal } |{ I D i d- Ser vedCel l sToModi f y CRI TI CALI TY r ej ect TYPE ServedCel l sToModi f y PRESENCE opt i onal } |{ I D i d- Ser vedCel l sToDel ete CRI TI CALI TY r ej ect TYPE Ol d- CGI s PRESENCE opt i onal } ,

. . .}

ServedCel l sToModi f y: : = SEQUENCE ( SI ZE ( 1. . maxCel l i neNB) ) OF ServedCel l sToModi f y- I t em Ser vedCel l sToModi f y- I t em: : = SEQUENCE {

ol d- cgi CGI ,ser vedcel l s Ser vedCel l - I nf ormati on,. . .

}

7/18/2019 3GPP TS 36.423.pdf


3GPP

56Release 8Ol d- CGI s: : = SEQUENCE ( SI ZE ( 1. . maxCel l i neNB) ) OF CGI

- - **************************************************************- -- - ENB CONFI GURATI ON UPDATE ACKNOWLEDGE- -- - **************************************************************

ENBConf i gur at i onUpdat eAcknowl edge : : = SEQUENCE {prot ocol I Es Prot ocol I E- Cont ai ner {{ENBConf i gur ati onUpdat eAcknowl edge- I Es}},. . .

}

ENBConf i gur at i onUpdat eAcknowl edge- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },

. . .}

- - **************************************************************- -- - ENB CONFI GURATI ON UPDATE FAI URE- -- - **************************************************************

ENBConf i gur at i onUpdat eFai l ure : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{ENBConf i gur ati onUpdateFai l ur e- I Es}},. . .

}

ENBConf i gurat i onUpdat eFai l ure- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE mandat or y }|{ I D i d- Ti meToWai t CRI TI CALI TY i gnor e TYPE Ti meToWai t PRESENCE opt i onal }|{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },. . .

}

- - **************************************************************- -

- - Resour ce St at us Request- -- - **************************************************************

ResourceSt at usRequest : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{Resour ceSt atusRequest- I Es}},. . .

}

Resour ceSt at usRequest - I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Regi st r at i on- Request CRI TI CALI TY r ej ect TYPE Regi st r ati on- Request PRESENCE mandat ory} |

7/18/2019 3GPP TS 36.423.pdf


3GPP

57Release 8{ I D i d- Cel l ToReport CRI TI CALI TY i gnor e TYPE Cel l ToReport - Li st PRESENCE opt i onal } |{ I D i d- Report i ngPeri odi ci t y CRI TI CALI TY i gnor e TYPE Report i ngPer i od PRESENCE opt i onal } ,. . .

}

Cel l ToReport - Li st : : = SEQUENCE ( SI ZE ( 1. . maxCel l i neNB) ) OF Prot ocol I E- Si ngl e-Cont ai ner { {Cel l ToReport - I t emI Es} }

Cel l ToReport - I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cel l ToReport - I t em CRI TI CALI TY i gnore TYPE Cel l ToReport - I t em PRESENCE mandator y }

}

Cel l ToReport - I t em: : = SEQUENCE {cel l - I D CGI ,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {Cel l ToReport - I t em- Ext I Es} } OPTI ONAL,. . .

}

Cel l ToRepor t - I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

Report i ngPer i od : : = ENUMERATED {f f s, . . . }- - The Report Per i od gi ves t he r eport i ng peri odi ci t y i n number of f f s ms per i ods.- - E. g. val ue f f s means f f s ms- - Uni t ms, St ep f f s ms

- - **************************************************************- -- - Resour ce St at us Response- -- - **************************************************************

ResourceSt at usResponse : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{Resour ceSt atusResponse-I Es}},. . .

}

Resour ceSt at usResponse- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },. . .

}

- - **************************************************************- -- - Resour ce St at us Fai l ur e- -- - **************************************************************

Resour ceSt at usFai l ure : : = SEQUENCE {pr otocol I Es Pr ot ocol I E- Cont ai ner {{Resour ceSt atusFai l ur e- I Es}},

7/18/2019 3GPP TS 36.423.pdf


3GPP

58Release 8. . .

}

Resour ceSt atusFai l ur e- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cause CRI TI CALI TY i gnor e TYPE Cause PRESENCE mandat or y} |{ I D i d- Cr i t i cal i t yDi agnost i cs CRI TI CALI TY i gnor e TYPE Cr i t i cal i t yDi agnost i cs PRESENCE opt i onal },. . .

}

- - **************************************************************- -- - Resour ce Stat us Report i ng- -- - **************************************************************

ResourceSt at usUpdat e : : = SEQUENCE {pr otocol I Es Prot ocol I E- Cont ai ner {{Resour ceSt atusUpdate- I Es}},. . .

}

Resour ceSt at usUpdat e- I Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cel l Measur ement Resul t CRI TI CALI TY i gnor e TYPE Cel l Measur ement Resul t - Li st PRESENCE mandat or y},. . .

}

Cel l Measurement Resul t - Li st : : = SEQUENCE ( SI ZE ( 1. . maxCel l i neNB) ) OF Prot ocol I E- Si ngl e- Cont ai ner { {Cel l Measurement Resul t - I t emI

Cel l Measur ement Resul t - I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- Cel l Measurement Resul t - I t em CRI TI CALI TY i gnore TYPE Cel l Measurement Resul t - I t em PRESENCE mandat ory }

}

Cel l Measur ement Resul t - I t em : : = SEQUENCE {cel l - I D CGI ,r esour eSt at us Resour ceSt at us OPTI ONAL,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {Cel l Measurement Resul t - I t em- Ext I Es} } OPTI ONAL,. . .

}

Cel l Measur ement Resul t - I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

Resour ceSt atus : : = I NTEGER

- - **************************************************************- -- - PRI VATE MESSAGE- -- - **************************************************************

Pr i vat eMessage : : = SEQUENCE {pr i vat eI Es Pri vat eI E- Cont ai ner {{Pri vat eMessage-I Es}},

7/18/2019 3GPP TS 36.423.pdf


3GPP

59Release 8. . .

}

Pri vat eMessage- I Es X2AP- PRI VATE- I ES : : = {. . .

}

END

9.3.5 Information Element definitions- - **************************************************************- -- - I nf ormati on El ement Def i ni t i ons- -- - **************************************************************

X2AP- I Es {i t u- t ( 0) i dent i f i ed- organi zat i on ( 4) et s i ( 0) mobi l eDomai n (0)eps- Access ( 21) modul es (3) x2ap ( 2) vers i on1 ( 1) x2ap- I Es (2) }


BEGI N

I MPORTSi d- I nt er f acesToTr ace- I t em,maxInterfaces,maxNr Of Er r or s,

maxnoof Cel l s,maxnoof EPLMNs,maxnoof EPLMNsPl usOne,maxnoof For bLACs,maxnoof For bTACs,maxCel l i neNB,maxnoof BPLMNs,maxnoof PRBs,maxPool s

FROM X2AP- Const ant s

Cr i t i cal i t y,Pr ocedur eCode,Pro tocol I E- I D,

Tr i gger i ngMessageFROM X2AP- CommonDat aTypes

Pr otocol I E- Si ngl e- Cont ai ner {},Prot ocol Extensi onCont ai ner{},X2AP- PROTOCOL- I ES,X2AP- PROTOCOL- EXTENSI ON

7/18/2019 3GPP TS 36.423.pdf


3GPP

60Release 8FROM X2AP- Cont ai ners;

- - A

AggregateMaxi mumBi t Rat e : : = SEQUENCE {aggregat eMaxi mumBi t Rat eDownl i nk SAE- Bear er - Bi t Rat e,aggregat eMaxi mumBi t Rat eUpl i nk SAE- Bear er- Bi t Rat e,. . .

}

Al l ocati onAndRet ent i onPri ori t y : : = OCTET STRI NG

- - B

Bear er - I D : : = BI T STRI NG ( SI ZE ( 8) ) - - To be checked, FFS

Br oadcast PLMNs- I t em : : = SEQUENCE ( SI ZE( 1. . maxnoof BPLMNs) ) OF PLMN- I dent i t y

- - C

Cause : : = CHOI CE {r adi oNet wor k CauseRadi oNet wor k,t r ansport CauseTr ansport ,pr otocol CausePr otocol ,mi sc CauseMi sc,. . .

}

CauseMi sc : : = ENUMERATED {cont r ol - pr ocessi ng- over l oad,har dware- f ai l ur e,om- i nt er vent i on,not- enough- user- pl ane- pr ocessi ng- r esour ces,unspeci f i ed,. . .

}

CausePr ot ocol : : = ENUMERATED {t ransf er- synt ax- err or,abstr act- synt ax- err or- rej ect ,

abstr act- synt ax- err or- i gnore- and- not i f y,message- not- compati bl e-wi t h- r ecei ver - st ate,semant i c- er r or ,unspeci f i ed,abst r act - synt ax- er r or- f al sel y-const r ucted- message,. . .

}

CauseRadi oNet wor k : : = ENUMERATED {handover - desi r abl e- f or - r adi o-r easons,t i me- cri t i cal - handover ,

7/18/2019 3GPP TS 36.423.pdf


3GPP

61Release 8r esour ce- opt i mi sati on- handover ,reduce- l oad- i n- servi ng- cel l ,par t i al - handover ,unknown- new- eNB- UE- X2AP- I D,unknown- ol d- eNB- UE- X2AP- I D,unknown- pai r - of - UE- X2AP- I D,ho- t ar get - not - al l owed,t r el ocovera l l - expi ry,t rel ocprep- expi ry,cel l - not - avai l abl e,no- radi o- resources -avai l abl e- i n- t arget - cel l ,i nval i d- MME- Gr oupI D,unknown- MME- Code,unspeci f i ed,. . .

}

CauseTr anspor t : : = ENUMERATED {t r anspor t - r esour ce- unavai l abl e,unspeci f i ed,. . .

}

Cel l Type : : = ENUMERATED{macr o,mi cro,pi co,f emt o,. . .

}

CGI : : = SEQUENCE {pLMN- I dent i t y PLMN- I dent i t y,l AC LAC,cI CI ,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {CGI - Ext I Es} } OPTI ONAL

}

CGI - Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .}

CI : : = OCTET STRI NG ( SI ZE ( 2) )

Cr i t i cal i t yDi agnost i cs : : = SEQUENCE {pr ocedureCode Pr ocedureCode OPTI ONAL,t r i gger i ngMessage Tr i gger i ngMessage OPTI ONAL,procedureCr i t i cal i t y Cri t i cal i t y OPTI ONAL,i EsCri t i cal i t yDi agnost i cs Cri t i cal i t yDi agnost i cs-I E- Li st OPTI ONAL,

7/18/2019 3GPP TS 36.423.pdf


3GPP

62Release 8i E- Extensi ons Prot ocol Extensi onCont ai ner { {Cr i t i cal i t yDi agnosti cs- ExtI Es} } OPTI ONAL,. . .

}

COUNTval ue : : = SEQUENCE {pDCP- SN PDCP- SN,hFN HFN,. . .

}

Cr i t i cal i t yDi agnost i cs- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

Cr i t i cal i t yDi agnost i cs- I E- Li st : : = SEQUENCE ( SI ZE ( 1. . maxNr Of Er r ors) ) OFSEQUENCE {

i ECr i t i cal i t y Cr i t i cal i t y,i E- I D Pro tocol I E- I D,t ypeOf Er r or TypeOf Er r or,i E- Extensi ons Pr otocol Extensi onCont ai ner { {Cr i t i cal i t yDi agnost i cs- I E- Li st - ExtI Es} } OPTI ONAL,. . .

}

Cr i t i cal i t yDi agnosti cs- I E- Li st - ExtI Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

- - D

DL- For war di ng : : = ENUMERATED {dL- f orwardi ngProposed,. . .

}

- - E

ENB- Gl obal - I D : : = I NTEGER ( 0. . 65535) - - Val ue t o be checked FFS

EPLMNs : : = SEQUENCE ( SI ZE( 1. . maxnoof EPLMNs) ) OF PLMN- I dent i t y

Event Type : : = ENUMERATED{change- of - servi ng- cel l ,. . .

}

- - F

For bi ddenI nt er RATs : : = ENUMERATED {al l ,

7/18/2019 3GPP TS 36.423.pdf


3GPP

63Release 8ger an,ut r an,. . .

}

For bi ddenTAs : : = SEQUENCE ( SI ZE( 1. . maxnoof EPLMNsPl usOne) ) OF For bi ddenTAs- I t em Forbi ddenTAs- I t em : : = SEQUENCE {

pLMN- I dent i t y PLMN- I dent i t y,f or bi ddenTACs For bi ddenTACs

}

For bi ddenTACs : : = SEQUENCE ( SI ZE( 1. . maxnoof For bTACs) ) OF TAC

For bi ddenLAs : : = SEQUENCE ( SI ZE( 1. . maxnoof EPLMNsPl usOne) ) OF For bi ddenLAs- I t em Forbi ddenLAs- I t em : : = SEQUENCE {

pLMN- I dent i t y PLMN- I dent i t y,f or bi ddenLACs For bi ddenLACs

}

For bi ddenLACs : : = SEQUENCE ( SI ZE( 1. . maxnoof For bLACs) ) OF LAC

Fr equency : : = OCTET STRI NG

- - G

GTPt unnel Endpoi nt : : = SEQUENCE {t r anspor t LayerAddress Tr anspor t LayerAddr ess,gTP- TEI D GTP- TEI ,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {GTPt unnel Endpoi nt- Ext I Es} } OPTI ONAL,. . .

}

GTPt unnel Endpoi nt - Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

GTP- TEI : : = OCTET STRI NG ( SI ZE ( 4))

GUGr oupI DLi st : : = SEQUENCE ( SI ZE ( 1. . maxPool s) ) OF GU- Gr oup- I D

GU- Gr oup- I D : : = SEQUENCE {pLMN- I dent i t y PLMN- I dent i t y,mME- Gr oup- I D MME- Gr oup- I D,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {GU- Gr oup- I D- Ext I Es} } OPTI ONAL,. . .

}

GU- Gr oup- I D- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {

7/18/2019 3GPP TS 36.423.pdf


3GPP

64Release 8. . .

}

GUMMEI : : = SEQUENCE {

gU- Gr oup- I D GU- Gr oup- I D,mMME- Code MME- Code,i E- Ext ensi ons Pr ot ocol Ext ensi onCont ai ner { {GUMMEI - Ext I Es} } OPTI ONAL,. . .

}

GUMMEI - Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

- - H

Handover Rest r i ct i onLi st : : = SEQUENCE {servi ngPLMN PLMN- I dent i t y,equi val ent PLMNs EPLMNs OPTI ONAL,f or bi ddenTAs For bi ddenTAs OPTI ONAL,f or bi ddenLAs For bi ddenLAs OPTI ONAL,f or bi ddenI nt er RATs For bi ddenI nt er RATs OPTI ONAL,i E- Extensi ons Prot ocol Extensi onCont ai ner { {Handover Rest r i ct i onLi st - ExtI Es} } OPTI ONAL,. . .

}

HandoverRest r i ct i onLi st - Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

HFN : : = I NTEGER ( 0. . 1048575)

- - I

I nt erf acesToTrace : : = SEQUENCE (SI ZE( 0. . maxI nt er f aces) ) OF Prot ocol I E- Si ngl e-Cont ai ner {{I nt erf acesToTr ace-I t emI Es} }

I nter f acesToTrace- I t emI Es X2AP- PROTOCOL- I ES : : = {{ I D i d- I nt erf acesToTr ace-I t em CRI TI CALI TY i gnore TYPE I nt erf acesToTrace- I t em PRESENCE mandator y }

}

I nt erf acesToTrace- I t em: : = SEQUENCE {t r aceI nt er f ace TraceI nt er f ace,t r aceDept h Tr aceDept h,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {I nter f acesToTrace- I t em- Ext I Es} } OPTI ONAL,. . .

}

7/18/2019 3GPP TS 36.423.pdf


3GPP

65Release 8

I nt er f acesToTrace- I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

- - J- - K- - L

LAC : : = OCTET STRI NG ( SI ZE ( 2) ) - - ( EXCEPT ( ' 0000' H| ' FFFE' H) )

Last Vi si t edCel l - I t em : : = SEQUENCE {gl obal - Cel l - I D CGI ,cel l Type Cel l Type,t i me- UE- StayedI nCel l Ti me- UE- St ayedI nCel l OPTI ONAL,i E- Extensi ons Prot ocol Extensi onCont ai ner { {Last Vi si t edCel l - I t em- ExtI Es} } OPTI ONAL,. . .

}

Last Vi si t edCel l - I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

Locat i onReport i ngI nf ormat i on : : = SEQUENCE {event Type Event Type,r eport Ar ea Report Ar ea,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {Locat i onReport i ngI nf ormat i on- Ext I Es} } OPTI ONAL,. . .

}

Locat i onRepor t i ngI nf or mat i on- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : ={. . .

}

- - M MaxTxPower PRBNorm : : = BI T STRI NG ( SI ZE( 1. . 110, . . . ) )

MME- Gr oup- I D : : = OCTET STRI NG ( SI ZE ( 2))

MME- Code : : = OCTET STRI NG ( SI ZE ( 1) )- - N

- - O- - P

PDCP- SN : : = I NTEGER ( 0. . 4095)

PhyCI D : : = OCTET STRI NG

7/18/2019 3GPP TS 36.423.pdf


3GPP

66Release 8

PLMN- I dent i t y : : = OCTET STRI NG ( SI ZE( 3))

- - Q

QCI : : = I NTEGER ( 1. . 256)

- - R

Recei veSt at usof ULPDCPSDUs : : = BI T STRI NG ( SI ZE( 4096) )

Regi st r at i on- Request : : = ENUMERATED {st ar t ,s top,. . .

}

Repor t Area : : = ENUMERATED{e-ut r an- cgi , - - FFS: The def i ni t i on of E- UTRAN CGI. . .

}

RRC- Context : : = OCTET STRI NG

- - S

SAE- Bear er- Bi t Rat e : : = I NTEGER ( 0. . 210000000000)

SAE- Bear er Level - QoS- Paramet er s : : = SEQUENCE {qCI QCI ,al l ocat i onAndRet ent i onPri or i t y Al l ocat i onAndRet ent i onPr i ori t y, - - FFSsAE- Bear er Type SAE- Bear er Type,. . .

}

SAE- Bear er Type : : = CHOI CE {sAE- GBR- bear er SAE- GBR- Bear er ,sAE- non- GBR- bear er SAE- Non- GBR- Bearer ,. . .

}SAE- GBR- Bearer : : = SEQUENCE {

sAE- Bear er - Maxi mumBi t r at eDL SAE- Bear er- Bi t Rat e,sAE- Bear er - Maxi mumBi t r at eUL SAE- Bear er- Bi t Rat e,sAE- Bear er- GuaranteedBi t r ateDL SAE- Bear er- Bi t Rat e,sAE- Bear er- GuaranteedBi t r ateUL SAE- Bear er- Bi t Rat e,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {SAE- GBR- Bear er- Par ameter s- Ext I Es} } OPTI ONAL,. . .

}

7/18/2019 3GPP TS 36.423.pdf


3GPP

67Release 8SAE- GBR- Bearer - Par amet er s- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {

. . .}

SAE- Non- GBR- Bear er : : = SEQUENCE {sAE- non- GBR- Bear er - Type SAE- Non- GBR- Bear er - Type,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {SAE- non- GBR- Bear er- Par ameter s- Ext I Es} } OPTI ONAL,. . .

}

SAE- non- GBR- Bearer - Par amet er s- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = { . . .

}

SAE- Non- GBR- Bear er - Type : : = ENUMERATED {non- GBR- Bear er ,. . .

}

ServedCel l s : : = SEQUENCE ( SI ZE ( 1. . maxCel l i neNB) ) OF ServedCel l - I nf ormat i on

ServedCel l - I nf ormat i on : : = SEQUENCE {

phyCI D PhyCI D,cel l I d CGI ,t AC TAC,broadcast PLMNs Br oadcast PLMNs- I t em,f r equency Fr equency,i E- Extensi ons Prot ocol Extensi onCont ai ner { {Ser vedCel l - I nf ormati on- ExtI Es} } OPTI ONAL,. . .

}

Ser vedCel l - I nf or mat i on- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

- - T

TAC : : = OCTET STRI NG - - FFS

Tar get eNBt oSour ce- eNBTr anspar ent Cont ai ner : : = OCTET STRI NG

Ti me- UE- St ayedI nCel l : : = I NTEGER

Ti meToWai t : : = OCTET STRI NG

Tr aceAct i vat i on : : = SEQUENCE {t r aceRef erence Tr aceRef erence,

7/18/2019 3GPP TS 36.423.pdf


3GPP

68Release 8i nt er f acesToTr ace I nt erf acesToTrace,i E- Ext ensi ons Prot ocol Ext ensi onCont ai ner { {TraceAct i vat i on- Ext I Es} } OPTI ONAL,. . .

}

Tr aceAct i vat i on- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

Tr aceDept h : : = ENUMERATED {mi ni mum,medi um,maxi mum,vendor Mi ni mum,vendor Medi um,vendor Maxi mum,. . .

}

Tr aceI nt er f ace : : = ENUMERATED {s1,x2,uu,. . .

}

Tr aceRef er ence : : = OCTET STRI NG ( SI ZE ( 8) )

Tr anspor t Layer Address : : = BI T STRI NG ( SI ZE( 1. . 160, . . . ) )

TypeOf Er r or : : = ENUMERATED {not- under st ood,mi ssi ng,. . .

}

- - U

UE- Hi st oryI nf ormati on : : = SEQUENCE ( SI ZE( 1. . maxnoof Cel l s) ) OF Last Vi si t edCel l - I t em

UE- S1AP- I D : : = I NTEGER ( 0. . 42949672954095)

UE- X2AP- I D : : = I NTEGER ( 0. . 4095) - - Val ue FFS

UL- I nt erf erenceOver l oadI ndi cat i on : : = SEQUENCE ( SI ZE( 1. . maxnoof PRBs) ) OF UL- I nt er f er enceOver l oadI ndi cat i on- I t em UL- I nt erf erenceOver l oadI ndi cat i on- I t em : : = ENUMERATED {

hi gh- i nt erf erence,

7/18/2019 3GPP TS 36.423.pdf


3GPP

69Release 8medi um- i nter f erence,l ow- i nt er f erence,. . .

}

UL- Hi ghI nt er f er enceI ndi cat i onI nf o : : = SEQUENCE ( SI ZE( 1. . maxCel l i neNB) ) OF UL- Hi ghI nt er f er enceI ndi cat i onI nf o-I t em UL- Hi ghI nt er f er enceI ndi cat i onI nf o- I t em : : = SEQUENCE {

ul - i nt erf er encei ndi cat i on UL-Hi ghI nt er f er enceI ndi cat i on,t a rget - Cel l - I D CGI ,i E- Extensi ons Prot ocol Extensi onCont ai ner { { UL- Hi ghI nt er f er enceI ndi cat i onI nf o- I t em- ExtI Es} } OPTI ONAL,. . .

}

UL- Hi ghI nt erf erenceI ndi cati onI nf o- I t em- Ext I Es X2AP- PROTOCOL- EXTENSI ON : : = {. . .

}

UL-Hi ghI nt erf erenceI ndi cat i on : : = BI T STRI NG ( SI ZE( 1. . 110, . . . ) )

- - V- - W- - X- - Y- - Z

END

9.3.6 Common definitions- - **************************************************************- -- - Common def i ni t i ons- -- - **************************************************************

X2AP- CommonDat aTypes {i t u- t ( 0) i dent i f i ed- organi zat i on ( 4) et s i ( 0) mobi l eDomai n (0)eps- Access ( 21) modul es (3) x2ap ( 2) ver si on1 ( 1) x2ap- CommonDat aTypes (3) }


BEGI N

- - **************************************************************- -- - Extensi on const ant s- -- - **************************************************************

7/18/2019 3GPP TS 36.423.pdf


3GPP

70Release 8

maxPr i vat eI Es I NTEGER : : = 65535maxPr ot ocol Ext ensi ons I NTEGER : : = 65535maxPr ot ocol I Es I NTEGER : : = 65535

- - **************************************************************- -- - Common Dat a Types- -- - **************************************************************

Cr i t i cal i t y : : = ENUMERATED { r ej ect, i gnor e, noti f y }

Pr esence : : = ENUMERATED { opt i onal , condi t i onal , mandat or y }

Pr i vat eI E- I D : : = CHOI CE {l ocal I NTEGER ( 0. . maxPri vat eI Es) ,gl obal OBJ ECT I DENTI FI ER

}

ProcedureCode : : = I NTEGER ( 0. . 255)

Pr ot ocol I E- I D : : = I NTEGER ( 0. . maxProtocol I Es)

Tr i gger i ngMessage : : = ENUMERATED { i ni t i at i ngmessage, success f ul - out come, unsuccess f ul - out come}

END

9.3.7 Constant definitions- - **************************************************************- -- - Constant def i ni t i ons- -- - **************************************************************

X2AP- Const ant s {i t u- t ( 0) i dent i f i ed- organi zat i on ( 4) et s i ( 0) mobi l eDomai n (0)eps- Access ( 21) modul es ( 3) x2ap ( 2) ver si on1 (1) x2ap- Const ant s ( 4) }


BEGI N

I MPORTSPr ocedur eCode,Protocol I E- I D

FROM X2AP- CommonDat aTypes;

7/18/2019 3GPP TS 36.423.pdf


3GPP

71Release 8- - **************************************************************- -- - El ement ary Pr ocedures- -- - **************************************************************

i d- handover Preparat i on Procedur eCode : : = 0i d- handover Cancel Procedur eCode : : = 1i d- l oadI ndi cat i on Procedur eCode : : = 2i d- er r orI ndi cat i on Pr ocedur eCode : : = 3i d- snSt atusTr ansf er Procedur eCode : : = 4i d- uECont ext Rel ease ProcedureCode : : = 5i d- x2Setup Procedur eCode : : = 6i d- r eset Procedur eCode : : = 7i d- eNBConf i gurat i onUpdat e Procedur eCode : : = 8i d- r esour ceSt atusUpdateI ni t i ati on Procedur eCode : : = 9i d- r esour ceSt atusReport i ng Procedur eCode : : = 10

- - **************************************************************- -- - Li st s- -- - **************************************************************

maxI nter f aces I NTEGER : : = 16 - - FFS Val ue t o be checkedmaxCel l i neNB I NTEGER : : = 256 - - FFS Val ue t o be checkedmaxnoof Cel l s I NTEGER : : = 16 - - FFS Val ue t o be checkedmaxnoof Bear er s I NTEGER : : = 16 - - FFS Val ue t o be checkedmaxNr Of Err or s I NTEGER : : = 256 - - FFS Val ue t o be checkedmaxnoof PDCP- SN I NTEGER : : = 16 - - FFS Val ue t o be checkedmaxnoof EPLMNs I NTEGER : : = 15maxnoof EPLMNsPl usOne I NTEGER : : = 16maxnoof For bLACs I NTEGER : : = 256 - - FFS Val ue t o be checkedmaxnoof For bTACs I NTEGER : : = 256 - - FFS Val ue t o be checkedmaxnoof BPLMNs I NTEGER : : = 6maxnoof PRBs I NTEGER : : = 110 - - FFS Val ue t o be checkedmaxPool s I NTEGER : : = 16 - - FFS Val ue t o be checked

- - **************************************************************- -- - I Es- -- - **************************************************************

i d- Bear er s - Admi t t ed- I t em Pr ot ocol I E- I D : : = 0i d- Bear ers- Admi t t ed- Li st Pr ot ocol I E- I D : : = 1

7/18/2019 3GPP TS 36.423.pdf


3GPP

72Release 8i d- Bear ers- Not Admi t t ed- I t em Pr ot ocol I E- I D : : = 2i d- Bear ers- Not Admi t t ed- Li st Pr ot ocol I E- I D : : = 3i d- Bear er s - ToBeSet up- I t e m Pr o t ocol I E- I D : : = 4i d- Cause Pr ot ocol I E- I D : : = 5i d- Cel l I nf ormat i on Pro tocol I E- I D : : = 6i d- Cel l I nf ormat i on- I t em Pro tocol I E- I D : : = 7i d- I nt er f aces ToTr ace- I t em Pr ot ocol I E- I D : : = 8i d- New- eNB- UE- X2AP- I D Prot ocol I E- I D : : = 9i d- Ol d- eNB- UE- X2AP-I D Pr ot ocol I E- I D : : = 10i d- TargetCel l - I D Pro tocol I E- I D : : = 11i d- Tar get eNBt oSour ce- eNBTransparent Cont ai ner Prot ocol I E- I D : : = 12i d- TraceActi vat i on Pr ot ocol I E- I D : : = 13i d- UE- Cont extI nf or mat i on Pr ot ocol I E- I D : : = 14i d- UE- Hi storyI nf or mat i on Pr ot ocol I E- I D : : = 15i d- UE- X2AP-I D Pr ot ocol I E- I D : : = 16i d- Cr i t i cal i t yDi agnos t i cs Pro tocol I E- I D : : = 17i d- Bear ers- Subj ectToSt at usTransf er- Li st Pr ot ocol I E- I D : : = 18i d- Bear ers- Subj ectToSt at usTransf er- I t em Pr ot ocol I E- I D : : = 19i d- ServedCel l s Pr ot ocol I E- I D : : = 20i d- ENB- Gl obal - I D Pr ot ocol I E- I D : : = 21i d- Ti meToWai t Pr ot ocol I E- I D : : = 22i d- GUMMEI - I D Pr ot ocol I E- I D : : = 23i d- GUGr oupI DLi st Pr ot ocol I E- I D : : = 24i d- Ser vedCel l sToAdd Pr ot ocol I E- I D : : = 25i d- Ser vedCel l sToModi f y Pr ot ocol I E- I D : : = 26i d- Ser vedCel l sToDel et e Pr ot ocol I E- I D : : = 27i d- Regi str at i on- Request Pr ot ocol I E- I D : : = 28i d- Cel l ToReport Pr ot ocol I E- I D : : = 29i d- Report i ngPeri odi ci t y Pr ot ocol I E- I D : : = 30i d- Cel l ToRepor t - I t em Pr ot ocol I E- I D : : = 31i d- Cel l Measur ement Resul t Pr ot ocol I E- I D : : = 32i d- Cel l Measurement Resul t - I t em Pro tocol I E- I D : : = 33

END

9.3.8 Container definitions- - **************************************************************- -- - Cont ai ner def i ni t i ons- -- - **************************************************************

X2AP- Cont ai ner s {i t u- t ( 0) i dent i f i ed- organi zat i on ( 4) et s i ( 0) mobi l eDomai n (0)eps- Access ( 21) modul es ( 3) x2ap ( 2) ver si on1 ( 1) x2ap- Cont ai ner s ( 5) }


7/18/2019 3GPP TS 36.423.pdf


3GPP

73Release 8BEGI N


I MPORTSmaxPri vat eI Es,maxProt ocol Ext ensi ons,maxProt ocol I Es,Cr i t i cal i t y,Presence,Pr i vat eI E- I D,Protocol I E- I D

FROM X2AP- CommonDat aTypes;

- - **************************************************************- -- - Cl ass Def i ni t i on f or Pro tocol I Es- -- - **************************************************************

X2AP- PROTOCOL- I ES : : = CLASS {&i d Prot ocol I E- I D UNI QUE,&cr i t i cal i t y Cr i t i cal i t y,&Val ue,&pr esence Pr esence

}WI TH SYNTAX {

I D &i dCRI TI CALI TY &cri t i cal i t y

TYPE &Val uePRESENCE &pr esence

}

- - **************************************************************- -- - Cl ass Def i ni t i on f or Pro tocol I Es- -- - **************************************************************

X2AP- PROTOCOL- I ES- PAI R : : = CLASS {&i d Prot ocol I E- I D UNI QUE,&f i r s t Cr i t i cal i t y Cr i t i cal i t y,&Fi r st Val ue,&secondCr i t i cal i t y Cr i t i cal i ty,&SecondVal ue,&pr esence Pr esence

}WI TH SYNTAX {

I D &i d

7/18/2019 3GPP TS 36.423.pdf


3GPP

74Release 8FI RST CRI TI CALI TY &f i r s tCri t i cal i t yFI RST TYPE &Fi r st Val ueSECOND CRI TI CALI TY &secondCr i t i cal i t ySECOND TYPE &SecondVal uePRESENCE &pr esence

}

- - **************************************************************- -- - Cl ass Def i ni t i on f or Protocol Extensi ons- -- - **************************************************************

X2AP- PROTOCOL- EXTENSI ON : : = CLASS {&i d Prot ocol I E- I D UNI QUE,&cr i t i cal i t y Cr i t i cal i t y,&Ext ensi on,&pr esence Pr esence

}WI TH SYNTAX {

I D &i dCRI TI CALI TY &cri t i cal i t yEXTENSI ON &Ext ensi onPRESENCE &pr esence

}

- - **************************************************************- -- - Cl ass Def i ni t i on f or Pr i vate I Es- -- - **************************************************************

X2AP- PRI VATE- I ES : : = CLASS {&i d Pr i vat eI E- I D,&cr i t i cal i t y Cr i t i cal i t y,&Val ue,&pr esence Pr esence

}WI TH SYNTAX {

I D &i dCRI TI CALI TY &cri t i cal i t y

TYPE &Val ue

PRESENCE &pr esence}

- - **************************************************************- -- - Cont ai ner f or Protocol I Es- -- - **************************************************************

Prot ocol I E- Cont ai ner {X2AP- PROTOCOL- I ES : I EsSet Par am} : : =SEQUENCE (SI ZE (0. . maxPr ot ocol I Es) ) OF

7/18/2019 3GPP TS 36.423.pdf


3GPP

75Release 8Prot ocol I E- Fi el d {{I EsSet Par am}}

Prot ocol I E- Si ngl e- Cont ai ner {X2AP- PROTOCOL- I ES : I EsSetPar am} : : =Prot ocol I E- Fi el d {{I EsSet Par am}}

Pr ot ocol I E- Fi el d {X2AP- PROTOCOL- I ES : I EsSet Param} : : = SEQUENCE {i d X2AP- PROTOCOL- I ES. &i d ( {I EsSet Param}),cri t i cal i t y X2AP- PROTOCOL- I ES. &cr i t i cal i t y ( {I EsSet Par am}{@i d}) ,val ue X2AP- PROTOCOL- I ES. &Val ue ( {I EsSet Par am}{@i d})

}

- - **************************************************************- -- - Cont ai ner f or Protocol I E Pai rs- -- - **************************************************************

Prot ocol I E- Cont ai ner Pai r {X2AP- PROTOCOL- I ES- PAI R : I EsSet Par am} : : =SEQUENCE (SI ZE (0. . maxPr ot ocol I Es) ) OFProt ocol I E- Fi el dPai r {{I EsSetPar am}}

Pr ot ocol I E- Fi el dPai r {X2AP- PROTOCOL- I ES- PAI R : I EsSet Param} : : = SEQUENCE {i d X2AP- PROTOCOL- I ES- PAI R. &i d ( {I EsSet Param}),f i r st Cr i t i cal i t y X2AP- PROTOCOL- I ES- PAI R. &f i r st Cr i t i cal i t y ( {I EsSet Par am}{@i d}) ,f i r st Val ue X2AP- PROTOCOL- I ES- PAI R. &Fi r st Val ue ( {I EsSet Par am}{@i d}),secondCr i t i cal i t y X2AP- PROTOCOL- I ES- PAI R. &secondCr i t i cal i t y ( {I EsSet Par am}{@i d}),secondVal ue X2AP- PROTOCOL- I ES- PAI R. &SecondVal ue ( {I EsSet Par am}{@i d})

}

- - **************************************************************- -- - Cont ai ner Li sts f or Protocol I E Cont ai ners- -- - **************************************************************

Pr ot ocol I E- Cont ai ner Li st {I NTEGER : l ower Bound, I NTEGER : upper Bound, X2AP- PROTOCOL- I ES : I EsSet Param} : : = SEQUENCE ( SI ZE ( l ower Bound. . upper Bound) ) OF

Prot ocol I E- Cont ai ner {{I EsSetPar am}}

Pr ot ocol I E- Cont ai ner Pai r Li st {I NTEGER : l owerBound, I NTEGER : upper Bound, X2AP- PROTOCOL- I ES- PAI R : I EsSet Param} : : = SEQUENCE ( SI ZE ( l ower Bound. . upper Bound) ) OF

Prot ocol I E- Cont ai nerPai r {{I EsSet Par am}}

- - **************************************************************- -- - Cont ai ner f or Protocol Extensi ons- -- - **************************************************************

Pr ot ocol Ext ensi onCont ai ner {X2AP- PROTOCOL- EXTENSI ON : Ext ensi onSet Param} : : =SEQUENCE ( SI ZE ( 1. . maxPr ot ocol Ext ensi ons) ) OFProt ocol Ext ensi onFi el d {{Ext ensi onSetPar am}}

7/18/2019 3GPP TS 36.423.pdf


3GPP

76Release 8Pr ot ocol Ext ensi onFi el d {X2AP- PROTOCOL- EXTENSI ON : Ext ensi onSet Par am} : : = SEQUENCE {

i d X2AP- PROTOCOL- EXTENSI ON. &i d ( {Ext ensi onSet Par am}) ,cr i t i cal i t y X2AP- PROTOCOL- EXTENSI ON. &cr i t i cal i t y ( {Ext ensi onSet Par am}{@i d}) ,ext ensi onVal ue X2AP- PROTOCOL- EXTENSI ON. &Ext ensi on ( {Ext ensi onSet Par am}{@i d})

}

- - **************************************************************- -- - Cont ai ner f or Pri vat e I Es- -- - **************************************************************

Pri vat eI E- Cont ai ner {X2AP-PRI VATE- I ES : I EsSet Par am} : : =SEQUENCE (SI ZE (1. . maxPr i vat eI Es) ) OFPri vat eI E- Fi el d {{I EsSetPar am}}

Pri vat eI E- Fi el d {X2AP- PRI VATE- I ES : I EsSetParam} : : = SEQUENCE {i d X2AP- PRI VATE- I ES. &i d ( {I EsSetPar am}) ,cri t i cal i t y X2AP-PRI VATE- I ES. &cri t i cal i t y ( {I EsSet Param}{@i d}) ,val ue X2AP- PRI VATE- I ES. &Val ue ( {I EsSet Param}{@i d})

}

END

7/18/2019 3GPP TS 36.423.pdf


3GPP

3GPP TS 36.423 V8.2.0 (2008-06)77Release 8

9.4 Message transfer syntaxX2AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specifiedin ref. [5].

9.5 TimersTRELOCprep

- Specifies the maximum time for the Handover Preparation procedure in the source eNB.

TX2 RELOCoverall

- Specifies the maximum time for the protection of the overall handover procedure in the source eNB.

10 Handling of unknown, unforeseen and erroneousprotocol data

Section 10 of [4] is applicable for the purposes of the present document.

7/18/2019 3GPP TS 36.423.pdf


3GPP TS 36.423 V8.2.0 (2008-06)78Release 8

Annex A (informative):Change history

Change histo ry Date TSG # TSG Doc. CR Rev Subject/Comm ent Old New2007-02 First draft 0.0.1

2007-03 Minor editorials according to discussion at RAN3#55. 0.0.1 0.0.2

2007-06 Following email discussion on RAN3 reflector:

Added text on HO Cancel (email discussion 07)l

Added text on HO Preparation (email discussion 06)

Editorial changes:

Correction of numbering and format changes

Moved editors note into section 9.1

Correction of wording in 8.4.1

Other changes:

Added FFS on GTP tunnel endpoints

Added FFS on how target eNB contacts MME

2007-08 Updates according to discussions in RAN3#57 0.1.0 0.2.0

2007-09 37 RP-070585 Presentation to TSG-RAN for information -version 1.0.0 0.2.0 1.0.02007-10 Inclusion of agreements from RAN3#57bis as well aseditorials

1.0.0 1.0.1

2007-11 Inclusion of agreements from RAN3#58 as well as editorials 1.0.1 1.1.02007-11 38 RP-070856 Presentation to TSG-RAN for approval - version 2.0.0 1.1.0 2.0.02007-12 38 Approved at TSG-RAN and placed under change control 2.0.0 8.0.02008-03 39 RP-080081 41 RAN3 agreed changes for TS 36.423 8.0.0 8.1.02008-06 40 RP-080305 42 1 RAN3 agreed changes for TS 36.423 8.1.0 8.2.0

3gpp ts 36.423.pdf

Documents