HO Message

3GPP TS 36.423 V8.0.
0 (2007-12)
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 3rd 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.
Release 8 2 3GPP TS 36.423 V8.0.0 (2007-12)
Keywords
UMTS, radio
3GPP
Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://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.
© 2007, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.
3GPP
Release 8 3 3GPP TS 36.423 V8.0.0 (2007-12)
Contents
Foreword ............................................................................................................................................................5
1 Scope ........................................................................................................................................................6
2 References ................................................................................................................................................6
3 Definitions, symbols and abbreviations ...................................................................................................6
3.1 Definitions ......................................................................................................................................................... 6
3.2 Symbols ............................................................................................................................................................. 6
3.3 Abbreviations..................................................................................................................................................... 7
4 General .....................................................................................................................................................7
4.1 Procedure specification principles ..................................................................................................................... 7
4.2 Forwards and backwards compatibility ............................................................................................................. 7
4.3 Specification notations....................................................................................................................................... 7
5 X2AP services ..........................................................................................................................................8
5.1 X2AP procedure modules .................................................................................................................................. 8
5.2 Parallel transactions ........................................................................................................................................... 8
6 Services expected from signalling transport ............................................................................................8
7 Functions of X2AP...................................................................................................................................8
8 X2AP procedures .....................................................................................................................................8
8.1 Elementary procedures ...................................................................................................................................... 8
8.2 Basic mobility procedures ................................................................................................................................. 9
8.2.1 Handover Preparation................................................................................................................................... 9
8.2.1.1 General ................................................................................................................................................... 9
8.2.1.2 Successful Operation .............................................................................................................................. 9
8.2.1.2.1 UE History Information .................................................................................................................. 10
8.2.1.3 Unsuccessful Operation........................................................................................................................ 10
8.2.1.4 Abnormal Conditions ........................................................................................................................... 11
8.2.2 SN Status Transfer .................................................................................................................................... 11
8.2.2.1 General ................................................................................................................................................. 11
8.2.2.2 Successful Operation ............................................................................................................................ 11
8.2.3 Release Resource ....................................................................................................................................... 12
8.2.3.1 General ................................................................................................................................................. 12
8.2.4 Handover Cancel........................................................................................................................................ 13
8.2.4.1 General ................................................................................................................................................. 13
8.3 Global Procedures........................................................................................................................................... 13
8.3.1 Load indication.......................................................................................................................................... 13
8.3.1.1 General ................................................................................................................................................. 13
8.3.2 Error Indication .......................................................................................................................................... 14
8.3.2.1 General ................................................................................................................................................. 14
8.3.3 X2 Setup..................................................................................................................................................... 15
8.3.3.1 General ................................................................................................................................................. 15
3GPP
Release 8 4 3GPP TS 36.423 V8.0.0 (2007-12)

8.3.4 Reset........................................................................................................................................................... 16
8.3.4.1 General ................................................................................................................................................. 16
9 Elements for X2AP Communication......................................................................................................16
9.1 Message Functional Definition and Content.................................................................................................... 16
9.1.1 Messages for Basic Mobility Procedures ................................................................................................... 16
9.1.1.1 HANDOVER REQUEST..................................................................................................................... 16
9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE ..................................................................................... 17
9.1.1.3 HANDOVER PREPARATION FAILURE.......................................................................................... 18
9.1.1.4 SN STATUS TRANSFER.................................................................................................................... 19
9.1.1.5 RELEASE RESOURCE....................................................................................................................... 19
9.1.1.6 HANDOVER CANCEL....................................................................................................................... 20
9.1.2 Messages for global procedures ................................................................................................................. 20
9.1.2.1 LOAD INFORMATION ...................................................................................................................... 20
9.1.2.2 ERROR INDICATION ........................................................................................................................ 21
9.1.2.3 X2 SETUP REQUEST ......................................................................................................................... 21
9.1.2.4 X2 SETUP RESPONSE ....................................................................................................................... 21
9.1.2.5 X2 SETUP FAILURE .......................................................................................................................... 22
9.1.2.6 Reset Request ....................................................................................................................................... 22
9.1.2.7 Reset Response..................................................................................................................................... 22
9.2 Information Element definitions ...................................................................................................................... 22
9.2.1 GTP Tunnel Endpoint ................................................................................................................................ 22
9.2.2 Trace activation.......................................................................................................................................... 22
9.2.3 UE History Information ............................................................................................................................. 23
9.2.4 Last Visited Cell Information..................................................................................................................... 23
9.2.5 Handover Restriction list............................................................................................................................ 23
9.2.6 PLMN Identity ........................................................................................................................................... 24
9.2.7 DL Forwarding........................................................................................................................................... 25
9.2.8 Cause.......................................................................................................................................................... 25
9.2.9 Criticality Diagnostics................................................................................................................................ 27
9.2.10 Served Cell Information ............................................................................................................................. 28
9.2.11 SAE Bearer Level QoS Parameters............................................................................................................ 29
9.2.12 SAE Bearer Type ....................................................................................................................................... 29
9.2.13 SAE Bearer Bit Rate .................................................................................................................................. 29
9.2.14 Aggregate Maximum Bit Rate ................................................................................................................... 30
9.2.15 Message Type............................................................................................................................................. 30
9.2.16 CGI............................................................................................................................................................. 30
9.3 Message and Information Element Abstract Syntax (with ASN.1) ................................................................. 31
9.3.1 General ....................................................................................................................................................... 31
9.3.2 Usage of Private Message Mechanism for Non-standard Use ................................................................... 31
9.3.3 Elementary Procedure Definitions ............................................................................................................. 31
9.3.4 PDU Definitions......................................................................................................................................... 35
9.3.5 Information Element definitions ................................................................................................................ 44
9.3.6 Common definitions................................................................................................................................... 52
9.3.7 Constant definitions ................................................................................................................................... 53
9.3.8 Container definitions.................................................................................................................................. 55
9.4 Message transfer syntax................................................................................................................................... 59
9.5 Timers .............................................................................................................................................................. 59
10 Handling of unknown, unforeseen and erroneous protocol data............................................................59
Annex A (informative): Change history ...............................................................................................60
3GPP
Release 8 5 3GPP TS 36.423 V8.0.0 (2007-12)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying 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.
3GPP
Release 8 6 3GPP TS 36.423 V8.0.0 (2007-12)
1 Scope
This clause shall start on a new page.
The present document specifies the radio network layer signalling procedures of the control plane between eNodeBs in
EUTRAN. 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 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-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 (including
a 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)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [x] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [x].
<defined term>: <definition>.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
3GPP
Release 8 7 3GPP TS 36.423 V8.0.0 (2007-12)
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [x] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [x].
<ACRONYM> <Explanation>
4 General
4.1 Procedure specification principles

The principle for specifying the procedure logic is to specify the functional behaviour of the eNB exactly and
completely. The eNB that originates the procedure functional behaviour is left unspecified.
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 certain
condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the
REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report
unsuccessful 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 functionality
Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node
about 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, the
optional IE shall not be included. For requirements on including Criticality Diagnostics IE, see section 10.
4.2 Forwards and backwards compatibility

The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future
messages, 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.
4.3 Specification notations

For 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 with
the 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 letters
in 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 font
followed by the abbreviation "IE", e.g. SAE Bearer ID IE.
3GPP
Release 8 8 3GPP TS 36.423 V8.0.0 (2007-12)
Value of an IE When referring to the value of an information element (IE) in the specification the "Value" is
written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Value".
5 X2AP services
Editors Note: Services an eNodeB offers to its neighbours.
5.1 X2AP procedure modules

The 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 EUTRAN.
The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this module
are in contrast to the above modules involving two peer eNBs.
5.2 Parallel transactions

Unless explicitly indicated in the procedure specification, at any instance in time one protocol peer shall have a
maximum of one ongoing X2AP procedure related to a certain UE.
6 Services expected from signalling transport

Editors 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 the
signalling connection breaks.
7 Functions of X2AP
The 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 eNBs to indicate overload and traffic load to eachother.
- Reporting of General Error Situations. This function allows reporting of general error situations, for which
function specific error messages have not been defined.
8 X2AP procedures
8.1 Elementary procedures

In the following tables, all EPs are divided into Class 1 and Class 2 EPs.
3GPP
Release 8 9 3GPP TS 36.423 V8.0.0 (2007-12)
Table 2: Class 1 Elementary Procedures
Elementary Initiating Message Successful Outcome Unsuccessful Outcome

Procedure Response message Response message
Handover HANDOVER HANDOVER HANDOVER
Preparation REQUEST REQUEST PREPARATION FAILURE
ACKNOWLEDGE
Handover Cancel HANDOVER CANCEL

Reset RESET REQUEST RESET RESPONSE
X2 Setup X2 SETUP REQUEST X2 SETUP X2 SETUP FAILURE
RESPONSE
Table 3: Class 2 Elementary Procedures

Elementary Procedure Initiating Message
Load Indication LOAD INFORMATION
Error Indication
SN Status Transfer SN STATUS TRANSFER
Release Resource RELEASE RESOURCE
Error 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 eNodeB for an incoming handover.
8.2.1.2 Successful Operation
source target
eNodeB eNodeB
HANDOVER REQUEST
HANDOVER REQUEST ACKNOWLEDGE
Figure 8.2.1.2-1: Handover preparation: successful operation
The source eNodeB initiates the procedure by sending the HANDOVER REQUEST message to the target eNodeB.
When the source eNodeB sends the HANDOVER REQUEST message, it shall start the timer TRELOCprep
If at least one of the requested SAE bearers is admitted to the cell, the target eNodeB shall reserve necessary resources,
and send the HANDOVER REQUEST ACKNOWLEDGE message back to the source eNodeB. The target eNodeB
shall include the SAE Bearers for which resources have been prepared at the target cell in the SAE Bearers Admitted
List IE. The target eNodeB shall include the SAE bearers that have not been admitted in the SAE Bearers Not Admitted
List IE with an appropriate cause value.
For each bearer for which the source eNodeB proposes to do forwarding of downlink data, the source eNodeB shall
include the DL forwarding IE within the SAE Bearer Info IE of the HANDOVER REQUEST message. For each bearer
that it has decided to admit, the target eNB may include the DL GTP Tunnel endpoint IE within the SAE Bearer Info IE
of the HANDOVER REQUEST ACKNOWLEDGE message that it accepts the proposed forwarding of downlink data
for this bearer.
3GPP
Release 8 10 3GPP TS 36.423 V8.0.0 (2007-12)
For each bearer in the SAE Bearers Admitted List IE, the target eNodeB may include the UL GTP Tunnel Endpoint IE if
it requests data forwarding of uplink packets to be performed for that bearer.
Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message the source eNodeB shall stop the timer
TRELOCprep, start the timer TX2RELOCOverall and terminate the Handover Preparation procedure. The source eNodeB is
then defined to have a Prepared Handover for that X2 UE-associated signalling.
Editors note: The following topics related to data forwarding have been identified (non exhaustive list):
- The relation between the GTP tunnel end point allocated by the HANDOVER REQUEST ACKNOWLEDGE
message, and corresponding GTP tunnel endpoints allocated in the S1 Path Switching message is FFS.
If the Trace activation IE is included in the HANDOVER REQUEST message then eNB should initiate the requested
trace function as described in 32.422.
The HANDOVER REQUEST message may contain the Serving PLMN IE, and shall contain this Information Element
if source eNB serves more than one PLMN identity. If the Serving PLMN IE is contained in the HANDOVER
REQUEST message, the target eNB shall store this information.
The eNB should use the information in Handover Restriction List IE to determine a target cell for subsequent handover
attempts.
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.
- not contained in the HANDOVER REQUEST message, the target eNB shall consider that no access restriction
applies to the UE.
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:
• Collect information about the UE for as long as the UE stays in one of its cells, and store the collected
information 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 was included in the UE History Information IE and act according to the
bullets above.
8.2.1.3 Unsuccessful Operation
source target
eNodeB eNodeB
HANDOVER REQUEST
HANDOVER PREPARATION FAILURE
Figure 8.2.1.3-1: Handover preparation: unsuccessful operation
3GPP
Release 8 11 3GPP TS 36.423 V8.0.0 (2007-12)
If the target eNodeB is not able to accept any of the SAE bearers or a failure occurs during the Handover Preparation,
the target eNodeB shall send the HANDOVER PREPARATION FAILURE message to the source eNodeB. The
message shall contain the Cause IE with an appropriate value.
Interactions with Handover Cancel procedure:
If there is no response from the target eNodeB to the HANDOVER REQUEST message before timer TRELOCprep expires
in the source eNodeB, the source eNodeB should cancel the Handover Preparation procedure towards the target eNodeB
by initiating the Handover Cancel procedure with the appropriate value for the Cause IE, e.g. "TRELOCprep expiry".
8.2.1.4 Abnormal Conditions
8.2.2 SN Status Transfer
8.2.2.1 General
The purpose of the SN Status Transfer procedure is to transfer the uplink PDCP-SN receiver status and the downlink
PDCP-SN transmitter status from the source to the target eNodeB during an X2 handover for each respective SAE
bearer for which PDCP SN status preservation applies.
source target
eNodeB eNodeB
SN STATUS TRANSFER
Figure 8.2.2.2-1: SN Status transfer
The source eNodeB initiates the procedure by sending the SN STATUS TRANSFER message to the target eNodeB at
the time point when it considers the transmitter/receiver status to be freezed. After sending this message the source
eNodeB shall stop assigning PDCP SNs to downlink SDUs and shall stop delivering UL SDUs toward the EPC . At
that point of time, the source eNodeB shall either:
- discard the uplink packets received out of sequence for each bearer for which PDCP SN status preservation
applies but not forwarding,
- forward the uplink packets received out of sequence for each bearer for which the source eNodeB has
accepted the request from the target eNodeB 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. If the target eNodeB receives this message for a UE for which no prepared
handover exists at the target eNodeB, the target eNodeB shall ignore the message.
For each bearer for which PDCP SN status preservation applies, the source eNB shall include the UL PDCP-SN Next
In-Sequence Expected IE within the SAE Bearers Subject to Status Transfer Item IE.
The source eNodeB shall also include in the STATUS TRANSFER message the list of uplink SDUs received out of
sequence within the PDCP-SN of UL SDUs Not To Be Retransmitted List IE (FFS) for each bearer for which the source
eNB has accepted the request from the target eNodeB for uplink forwarding.
3GPP
Release 8 12 3GPP TS 36.423 V8.0.0 (2007-12)
For each bearer for which the UL PDCP-SN Next In-Sequence Expected IE is received in the STATUS TRANSFER
message, the target eNodeB shall use it and not deliver any uplink packet which has a PDCP SN lower than the value
contained in this IE.
If the PDCP-SN of UL SDUs Not To Be Retransmitted List IE is included in the STATUS TRANSFER message for at
least one bearer, the target eNodeB may use it to build and send a Status Report message to the UE over the radio.
For each bearer for which PDCP SN status preservation applies, the source eNB shall include the DL PDCP-SN Next To
Assign IE within SAE Bearers Subject to Status Transfer Item IE.
If the DL PDCP-SN Next To Assign IE is received in the STATUS TRANSFER message for one bearer, the target
eNodeB shall use it to mark with the value contained in this IE the first downlink packet for which there is no PDCP SN
yet assigned.

If the target eNodeB receives this message for a UE for which no prepared handover exists at the target eNodeB, the
target eNodeB shall ignore the message.
8.2.3 Release Resource

Editor Note: Used by target eNodeB to release resources in the source eNodeB.
8.2.3.1 General
The Release Resource procedure is initiated by the target eNB to signal to the source eNB that control plane resources
for the handed over UE context can be released.
Source Target
eNB eNB
[X2 AP] Release Resource
Figure 8.2.3.2-1: Release Resource procedure
The Release Resource procedure is initiated by the target eNB. By sending RELEASE RESOURCE the target eNB
informs success of HO to source eNB and triggers the release of resources.
Upon reception of the RELEASE RESOURCE message, the source eNB can release radio and control plane related
resources associated to the UE context. For bearers that data forwarding has been performed. The source eNB should
continue forwarding of U-plane data as long as packets are received at the source eNB from the EPC or the source eNB
buffer has not been emptied (an implementation dependent mechanism decides that data forwarding can be stopped).
3GPP
Release 8 13 3GPP TS 36.423 V8.0.0 (2007-12)

If the Release Resource procedure is not initiated towards the source eNodeB from the target eNodeB before the expiry
of the timer TX2RELOCoverall, the source eNodeB shall release all resources associated to the UE context and request the
MME to release the UE context.
8.2.4 Handover Cancel
8.2.4.1 General
The Handover Cancel procedure is used to cancel an already prepared handover.
source target
eNodeB eNodeB
HANDOVER CANCEL
Figure 8.2.4.2-1: Handover cancel
The source eNodeB initiates the procedure by sending the HANDOVER CANCEL message to the target eNodeB. The
source eNodeB shall indicate the reason for cancelling the handover by an appropriate cause value.
At the reception of the HANDOVER CANCEL message, the target eNodeB shall remove any reference to, and release
any previously reserved resources to the referred UE context.

Should the HANDOVER CANCEL message refer to a context that does not exist, the target eNodeB shall ignore the
message.
8.3 Global Procedures

8.3.1 Load indication
8.3.1.1 General
The purpose of the Load indication procedure is to transfer the uplink Interference Overload Indication between intra-
frequency neighboring eNodeBs for interference coordination purpose.
3GPP
Release 8 14 3GPP TS 36.423 V8.0.0 (2007-12)
eNB eNB
LOAD INFORMATION
Figure 8.3.1.2-1: Load Indication
An eNodeB initiates the procedure by sending LOAD INFORMATION message to intra-frequency neighbouring
eNodeBs. The LOAD INFORMATION message can carry interference overload indication. The Load indication
procedure shall be used to send interference overload indication when the eNB experiences too high interference level
on some resource blocks.
Whether an eNB receiving a LOAD INFORMATION message should respond with a LOAD INFORMATION
message is FFS.
8.3.2 Error Indication

Editor 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 a node to report detected errors in one incoming message, provided they
cannot 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.
eNB1 eNB2
ERROR INDICATION
Figure 8.3.2.2-1: Error Indication procedure, Successful operation.
When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR
INDICATION message sent from the receiving node.
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 UE
X2AP ID”, “unknown New eNB UE X2AP ID” or “unknown the pair of UE X2AP ID ” FFS.
3GPP
Release 8 15 3GPP TS 36.423 V8.0.0 (2007-12)

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 eNodeBs to interoperate
correctly over the X2 interface.
eNodeB eNodeB
X2 SETUP REQUEST
X2 SETUP RESPONSE
Figure 8.3.3.2-1
An eNodeB, initiates the procedure by sending an X2 SETUP REQUEST to a candidate eNodeB. Candidate eNodeB
replies with X2 SETUP RESPONSE. The initiating eNodeB transfers a list of served cells to the candidate eNodeB.
Candidate eNodeB replies with a list of its served cells.
eNodeB eNodeB
X2 SETUP REQUEST
X2 SETUP FAILURE
Figure 8.3.3.3-1
If the candidate eNodeB can not accept the setup it should respond with an X2 SETUP FAILURE with appropriate
cause value.
If the X2 SETUP FAILURE messages include the time to wait information element the eNodeB shall wait at least for
the indicated time before reinitiation the X2 setup towards the same eNodeB.
3GPP
Release 8 16 3GPP TS 36.423 V8.0.0 (2007-12)
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 uses non UE associated signalling.
eNB1 eNB2
RESET REQUEST
RESET RESPONSE
Figure 8.3.4.2-1: Reset procedure, Successful Operation
The procedure is initiated with a RESET REQUEST message sent from the eNB1 to the eNB2. Upon receipt of this
message, eNB2 shall abort any other ongoing procedures over X2 between eNB1 and eNB2. The eNB2 shall delete all the
context information related to the eNB1..
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 consistency
with 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 eNodeB to the target eNodeB to request the preparation of resources for a handover.
Direction: eNodeB → eNodeB.
3GPP
Release 8 17 3GPP TS 36.423 V8.0.0 (2007-12)
IE/Group Name Presence Range IE type and Semantics Criticality Assigned

reference description Criticality
Message Type M 9.2.15 YES reject
Old eNB UE X2AP ID M INTEGER eNB UE X2AP YES reject

(0..4095) ID allocated at
the old eNB
Target Cell ID M 9.2.16 YES reject

UE Context Information M YES reject
> MME UE S1AP ID M INTEGER MME UE – –
(0..4095) S1AP ID
allocated at
the MME
> Aggregate Maximum O 9.2.14 YES reject

Bit Rate
> SAE Bearers To Be M – –
Setup List
>> SAE Bearer Info 1 to <maxnoof EACH ignore
SAEbearers>
>>> SAE Bearer ID M BIT STRING – –

(SIZE (8))
>>> SAE Bearer M 9.2.11 Inlcudes – –
Level QoS necessary
Parameters QoS
parameters
>>> DL Forwarding O 9.2.7 – –
>>> UL GTP Tunnel M 9.2.1 SGW tunnel – –

Endpoint endpoint. For
delivery of UL
PDUs
>>> RB type (QCI) M INTEGER – –
> RRC Context M OCTET to transfer UE – –
STRING RAN context,
details are
FFS
>Serving PLMN O 9.2.6 – –
>Handover Restriction O 9.2.5 – –

List
UE History Information O 9.2.3 YES reject
Trace activation O 9.2.2 YES ignore
Editors 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.
Editors Note: It has been identified that this message also needs to include information on how target eNB should
contact MME.
9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE

This message is sent by the target eNodeB to inform the source eNodeB about the prepared resources at the target.
3GPP
Release 8 18 3GPP TS 36.423 V8.0.0 (2007-12)


the old
eNodeB
New eNB UE X2AP ID M INTEGER New eNB UE YES reject

(0..4095) X2AP ID
allocated at
the new
eNodeB
SAE Bearers Admitted List O YES ignore

> SAE Bearer Info 1 to <maxnoof EACH ignore
SAEbearers>
>> SAE Bearer ID M BIT STRING – –

(SIZE (8))
>> UL GTP Tunnel O 9.2.1 Target eNB – –
Endpoint tunnel
endpoint. For
delivery of UL
PDUs
>> DL GTP Tunnel O 9.2.1 Target eNB – –
Endpoint tunnel
endpoint. For
delivery of DL
PDUs
SAE Bearers Not Admitted O YES ignore
List
> SAE Bearer Info 1 to <maxnoof EACH ignore
SAEbearers>
>> SAE Bearer ID M BIT STRING – –
(SIZE (8))
>> Cause M 9.2.8 – –
Target eNodeB to Source M OCTET It includes HO YES ignore

eNodeB Transparent STRING info for the UE
Container
9.1.1.3 HANDOVER PREPARATION FAILURE

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


(0..4095) ID allocated
at the old
eNodeB
Cause M 9.2.8 YES ignore
3GPP
Release 8 19 3GPP TS 36.423 V8.0.0 (2007-12)
9.1.1.4 SN STATUS TRANSFER

This message is sent by the source eNodeB to the target eNodeB to transfer the uplink/downlink PDCP-SN status
during a handover.

Message Type M 9.2.15 YES ignore
Old eNB UE X2AP ID M INTEGER eNB UE YES reject
(0..4095) X2AP ID
allocated at
the old
eNodeB
New eNB UE X2AP ID M INTEGER eNB UE YES reject

(0..4095) X2AP ID
allocated at
the new
eNodeB
SAE Bearers Subject to M YES ignore

Status Transfer List
>SAE Bearers Subject to 1 to <maxnoof EACH ignore
Status Transfer Item SAEbearers>
>> SAE bearer Identity M BIT STRING – –
(SIZE (8))
>> PDCP-SN of UL O 1 to PDCP SNs – –
SDUs Not To Be <maxnoofPDCP- of UL SDUs
Retransmitted List SN> received out
of sequence
(FFS)
>>> PDCP-SN M INTEGER – –
>> UL PDCP-SN Next M INTEGER PDCP-SN of – –
In-Sequence Expected the next in-
sequence
expected UL
SDU by the
target eNB
(upper
window
edge)
> DL PDCP-SN Next to M INTEGER PDCP-SN – –
Assign that the
target eNB
should
assign for
the next DL
SDU not
having an
SN yet
9.1.1.5 RELEASE RESOURCE

This message is sent by the target eNodeB to the source eNodeB to indicate that resources can be released.
3GPP
Release 8 20 3GPP TS 36.423 V8.0.0 (2007-12)


the old
eNodeB
New eNB UE X2AP ID M INTEGER eNB UE X2AP YES reject

the new
eNodeB
9.1.1.6 HANDOVER CANCEL

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


the old
eNodeB
New eNB UE X2AP ID M INTEGER eNB UE X2AP YES reject

the new
eNodeB
9.1.2 Messages for global procedures
9.1.2.1 LOAD INFORMATION

This message is sent by an eNodeB to neighbouring eNodeBs to transfer the Interference Overload Indication.
Additional load information might be added to this message FFS.
3GPP
Release 8 21 3GPP TS 36.423 V8.0.0 (2007-12)

Cell Information 1 to EACH ignore
maxCellineNB
>Cell ID M 9.2.16 -
>Interference Overload O OCTET Intercell -
Indication STRING interference
indicator for
each
resource
block
(coding is
FFS)
9.1.2.2 ERROR INDICATION

This message is used to indicate that some error has been detected in the node.
Direction: eNodeB Æ eNodeB

Cause O 9.2.8 YES ignore
Criticality Diagnostics O 9.2.9 YES ignore
Old eNB UE X2AP ID O INTEGER YES ignore
(0..4095)
New eNB UE X2AP ID O INTEGER YES ignore
(0..4095)
9.1.2.3 X2 SETUP REQUEST

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

eNB ID M INTEGER Coding FFS YES reject
(0..65535)
Served Cells 1 to This is all – –
maxnoofCelline the eNB
NB cells
>Served Cell information M 9.2.10 – –
9.1.2.4 X2 SETUP RESPONSE

This message is sent by an eNodeB to a neighbouring eNodeB to transfer the initialization information for a TNL
association.
3GPP
Release 8 22 3GPP TS 36.423 V8.0.0 (2007-12)

eNB ID M INTEGER Coding FFS YES reject
(0..65535)
Served Cells 1 to This is all – –
maxnoofCelline the eNB
NB cells
>Served Cell information M 9.2.10 – –
9.1.2.5 X2 SETUP FAILURE

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

Time To Wait O OCTET YES Ignore
STRING
9.1.2.6 Reset Request


9.1.2.7 Reset Response

9.2 Information Element definitions

9.2.1 GTP Tunnel Endpoint

Transport Layer Address M BIT STRING
(SIZE(1..160
, ...))
GTP TEID M OCTET
STRING
(SIZE (4))
9.2.2 Trace activation

Defines parameters related to a trace activation.
3GPP
Release 8 23 3GPP TS 36.423 V8.0.0 (2007-12)

Trace Reference M OCTET
STRING (3)
Interfaces To Trace 1 to
<maxInterfaces>
>Interface M ENUMERAT
ED (s1, x2
Uu, ...)
>Trace depth M ENUMERAT
ED(
Minimum,
Medium,
Maximum, ...
)
9.2.3 UE History Information

Last Visited Cell List 1 to MaxNrOfCells Most recent
information
is added to
the top of
this list
>Last Visited Cell M 9.2.4

Information
Editors Note: Maximum size of the list (MaxNrOfCells) is FFS.
9.2.4 Last Visited Cell Information

Global Cell ID M 9.2.16
Cell type M ENUMERAT

ED(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 list

This IE defines area roaming or access restrictions for handover. If the eNB receives the Handover Restriction List, it
shall overwrite previously received restriction information.
3GPP
Release 8 24 3GPP TS 36.423 V8.0.0 (2007-12)

Equivalent PLMNs 0..<maxnoofEPLM Allowed
Ns> PLMNs
together with
Serving
PLMN.
This list
corresponds
to the list of
“equivalent
PLMNs” as
defined in
[TS 24.008].
>PLMN Identity M 9.2.6
Forbidden TAs 0..<maxnoofEPLM intra LTE
NsPlusOne> roaming
restrictions
>Forbidden TAIs 1..<maxnoofForbT
AIs>
>>TAI M OCTET
STRING
Forbidden LAs 0..<maxnoofEPLM inter-3GPP
NsPlusOne> RAT roaming
restrictions
>Forbidden LACs 1..<maxnoofForbL
ACs>
>>LAC M OCTET
STRING(2)
Forbidden inter RATs O ENUMERAT inter-3GPP
ED(ALL, RAT access
GSM, restrictions
WCDMA, …)
Range bound Explanation

maxnoofEPLMNs Maximum no. of equivalent PLMN Ids. Value is 15.
maxnooffEPLMNsPlusOne Maximum no. of equivalent PLMN Ids plus one. Value is 16.
maxnoofforbiddenTAIs Maximum no. of forbidden Tracking Area Identities. Value is 256.
maxnoofforbiddenLACs Maximum no. of forbidden Location Area Codes. Value is 256.
9.2.6 PLMN Identity

This information element indicates the PLMN Identity.
3GPP
Release 8 25 3GPP TS 36.423 V8.0.0 (2007-12)
IE/Group Name Presence Range IE type and Semantics description

reference
PLMN identity M OCTET STRING - digits 0 to 9, encoded
(SIZE (3)) 0000 to 1001,
- 1111 used as filler digit,
two digits per octet,
- bits 4 to 1 of octet n
encoding digit 2n-1
- bits 8 to 5 of octet n
encoding digit 2n
-The Selected PLMN

identity consists of 3 digits
from MCC followed by
either
-a filler digit plus 2 digits
from MNC (in case of 2
digit MNC) or
-3 digits from MNC (in case
of a 3 digit MNC).
9.2.7 DL Forwarding
This element indicates that the SAE bearer is proposed for forwarding of downlink packets.
reference
DL Forwarding
>DL Forwarding M ENUMERATED
(DL forwarding
proposed, …)
9.2.8 Cause
The purpose of the cause information element is to indicate the reason for a particular event for the whole protocol.
3GPP
Release 8 26 3GPP TS 36.423 V8.0.0 (2007-12)
IE/Group Name Presence Range IE Type and Reference Semantics

Description
CHOICE Cause Group M
>Radio Network Layer
>>Radio Network Layer M ENUMERATED
Cause (Unspecified,
...
)
>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 with
Receiver State,
Semantic Error,
Unspecified,
Abstract Syntax Error (Falsely
Constructed Message),...)
>Misc
>>Miscellaneous Cause M ENUMERATED
(Control Processing Overload,
Hardware Failure,
O&M Intervention,
Not enough User Plane Processing
Resources,
Unspecified,...)
The meaning of the different cause values is described in the following table. In general, "not supported" cause values
indicate that the concerned capability is missing. On the other hand, "not available" cause values indicate that the
concerned capability is present, but insufficient resources were available to perform the requested action.
Radio Network Layer cause Meaning
Unspecified Sent when none of the above cause values applies but still the cause is
Radio Network Layer related
Transport Network Layer cause Meaning
Transport resource unavailable The required transport resources are not available
Transport Network Layer related
Protocol cause Meaning
3GPP
Release 8 27 3GPP TS 36.423 V8.0.0 (2007-12)
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 and The received message included an abstract syntax error and the
Notify) concerned criticality indicated "ignore and notify" (see subclause 10.3)
Abstract syntax error (falsely The received message contained IEs or IE groups in wrong order or with
constructed message) too many occurrences (see subclause 10.3)
Message not Compatible with The received message was not compatible with the receiver state (see
Receiver State subclause 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)
Protocol related
Miscellaneous cause Meaning
Control Processing Overload eNodeB control processing overload

Hardware Failure eNodeB hardware failure
Not enough User Plane Processing eNodeB has insufficient user plane processing resources available
Resources
O&M Intervention Operation and Maintenance intervention related to eNodeB equipment
Unspecified Sent when none of the above cause values applies and the cause is not
related to any of the categories Radio Network Layer, Transport Network
Layer or Protocol.
9.2.9 Criticality Diagnostics

The Criticality Diagnostics IE is sent by the RNC or the CN when parts of a received message have not been
comprehended or were missing, or if the message contained logical errors. When applicable, it contains information
about which IEs were not comprehended or were missing.
3GPP
Release 8 28 3GPP TS 36.423 V8.0.0 (2007-12)

reference
Criticality Diagnostics
>Procedure Code O INTEGER Procedure Code is to be used
(0..255) if Criticality Diagnostics is part
of Error Indication procedure,
and not within the response
message of the same
procedure that caused the
error
>Triggering Message O ENUMERAT The Triggering Message is
ED(initiating used only if the Criticality
message, Diagnostics is part of Error
successful Indication procedure.
outcome,
unsuccessful
outcome,
outcome)
>Procedure Criticality O ENUMERAT This Procedure Criticality is
ED(reject, used for reporting the
ignore, Criticality of the Triggering
notify) message (Procedure).
Information Element 0 to <maxnoof
Criticality Diagnostics errors>
>IE Criticality M ENUMERAT The IE Criticality is used for
ED(reject, reporting the criticality of the
ignore, triggering IE. The value
notify) 'ignore' shall not be used.
>IE ID M INTEGER The IE ID of the not
(0..65535) understood or missing IE
>Type of Error M ENUMERAT

ED(not
understood,
missing, …)
Range bound Explanation

maxnooferrors Maximum no. of IE errors allowed to be reported with a single
message. The value for maxnooferrors is 256.
9.2.10 Served Cell Information

PhyCID M OCTET Physical Cell -
STRING ID
Cell ID M OCTET -
STRING
TAI M OCTET Tracking -
STRING Area Identity
Broadcast PLMNs 1..<maxnoofBPL Broadcast -
MNs> PLMNs
>PLMN Identity M 9.2.6 -
Frequency M OCTET (Center -
STRING frequency
and/or
frequency
band)
3GPP
Release 8 29 3GPP TS 36.423 V8.0.0 (2007-12)
9.2.11 SAE Bearer Level QoS Parameters

This IE defines the QoS to be applied to a SAE bearer.

reference
SAE Bearer Level QoS
Parameters
>Label M INTEGER Coded as specified in TS
(1..256) 23.xxx, which will be defined in
SA2
>Allocation and Retention M (FFS) OCTET The ARP definition is left FFS
Priority STRING in SA2.
>SAE Bearer Type M 9.2.12 Desc.:
Either GBR or non-GBR
Bearer
9.2.12 SAE Bearer Type

reference
Choice SAE Bearer Type
> SAE GBR bearer
>> SAE Bearer Maximum M SAE Bearer Desc.: to be added
Bit Rate Downlink Bit Rate
9.2.13
>> SAE Bearer Maximum M SAE Bearer Desc.: to be added
Bit Rate Uplink Bit Rate
9.2.13
>> SAE Bearer M SAE Bearer Desc:: to be added
Guaranteed Bit Rate Bit Rate
Downlink 9.2.13
>> SAE Bearer M SAE Bearer Desc.: to be added
Guaranteed Bit Rate Bit Rate
Uplink 9.2.13
>SAE Non-GBR bearer
>> Non GBR bearer ENUMERAT
ED (Non
GBR
bearer,…)
9.2.13 SAE Bearer Bit Rate

reference
SAE Bearer Bit Rate M INTEGER Desc.: This IE indicates the
(0..10,000,0 maximum number of bits
00,000) delivered by E-UTRAN and to
E-UTRAN within a period of
time, divided by the duration of
the period.
The unit is: bit/s
3GPP
Release 8 30 3GPP TS 36.423 V8.0.0 (2007-12)
9.2.14 Aggregate Maximum Bit Rate

reference
Aggregate Maximum Bit Desc::

Rate Applicable for non-GBR SAE
Bearers, provided at initial
context setup
>Aggregate Maximum Bit M SAE Bearer Desc.: to be added
Rate Downlink Bit Rate
9.2.13
>Aggregate Maximum Bit M SAE Bearer Desc.: to be added
Rate Uplink Bit Rate
9.2.13
9.2.15 Message Type

The 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 description

Message Type Assumed max no of messages
is 256.
>Procedure Code M
>Type of Message M CHOICE
(Initiating Message,
Successful Outcome,
Unsuccessful Outcome,
…)
9.2.16 CGI

CGI -
> PLMN identity M 9.2.6 -
> LAC M OCTET 0000 and FFFE not -
STRING (2) allowed.
>CI M OCTET -
STRING (2)
3GPP
Release 8 31 3GPP TS 36.423 V8.0.0 (2007-12)
9.3 Message and Information Element Abstract Syntax (with ASN.1)

9.3.1 General
Subclause 9.3 presents the Abstract Syntax of the X2AP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this subclause and the tabular format
in subclause 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, in which the tabular format shall take
precedence.
The ASN.1 definition specifies the structure and content of X2AP messages. X2AP messages can contain any IEs specified in the object set definitions for that message without
the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a X2AP message according to the PDU
definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than
once in one object set, then the different occurrences have different IE ids):
• IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
• Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at
most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the
corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list in which the list elements reside. The second part
defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
If a X2AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for
Abstract Syntax Error in subclause 10.3.6.
Editors Note: Yellow highlight indicate text that has been proposed to be removed (further checking needed)
9.3.2 Usage of Private Message Mechanism for Non-standard Use

The private message mechanism for non-standard use may be used:
- for special operator (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality
specification in order to guarantee multivendor inter-operability.
- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.
The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.
9.3.3 Elementary Procedure Definitions

-- **************************************************************
--
-- Elementary Procedure definitions
3GPP
Release 8 32 3GPP TS 36.423 V8.0.0 (2007-12)
--
-- **************************************************************
X2AP-PDU-Descriptions {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) x2ap (2) version1 (1) x2ap-PDU-Descriptions (0) }
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
-- **************************************************************
--
-- IE parameter types from other modules.
--
-- **************************************************************
IMPORTS
Criticality,
ProcedureCode
FROM X2AP-CommonDataTypes
ErrorIndication,
HandoverRequest,
HandoverRequestAcknowledge,
HandoverPreparationFailure,
SNStatusTransfer,
ReleaseResource,
HandoverCancel,
LoadInformation,
ResetRequest,
ResetResponse,
X2SetupRequest,
X2SetupResponse,
X2SetupFailure
FROM X2AP-PDU-Contents
id-errorIndication,
id-handoverPreparation,
id-snStatusTransfer,
id-releaseResource,
id-handoverCancel,
id-loadIndication,
id-reset,
id-x2Setup
FROM X2AP-Constants;
-- **************************************************************
--
3GPP
Release 8 33 3GPP TS 36.423 V8.0.0 (2007-12)
-- Interface Elementary Procedure Class
--
-- **************************************************************
X2AP-ELEMENTARY-PROCEDURE ::= CLASS {

&InitiatingMessage ,
&SuccessfulOutcome OPTIONAL,
&UnsuccessfulOutcome OPTIONAL,
&procedureCode ProcedureCode UNIQUE,
&criticality Criticality DEFAULT ignore
}
WITH SYNTAX {
INITIATING MESSAGE &InitiatingMessage
[SUCCESSFUL OUTCOME &SuccessfulOutcome]
[UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome]
PROCEDURE CODE &procedureCode
[CRITICALITY &criticality]
}
-- **************************************************************
--
-- Interface PDU Definition
--
-- **************************************************************
X2AP-PDU ::= CHOICE {

initiatingMessage InitiatingMessage,
successfulOutcome SuccessfulOutcome,
unsuccessfulOutcome UnsuccessfulOutcome,
...
}
InitiatingMessage ::= SEQUENCE {

procedureCode X2AP-ELEMENTARY-PROCEDURE.&procedureCode ({X2AP-ELEMENTARY-PROCEDURES}),
criticality X2AP-ELEMENTARY-PROCEDURE.&criticality ({X2AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
value X2AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({X2AP-ELEMENTARY-PROCEDURES}{@procedureCode})
}
SuccessfulOutcome ::= SEQUENCE {

value X2AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({X2AP-ELEMENTARY-PROCEDURES}{@procedureCode})
}
UnsuccessfulOutcome ::= SEQUENCE {

value X2AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({X2AP-ELEMENTARY-PROCEDURES}{@procedureCode})
}
-- **************************************************************
--
3GPP
Release 8 34 3GPP TS 36.423 V8.0.0 (2007-12)
-- Interface Elementary Procedure List
--
-- **************************************************************
X2AP-ELEMENTARY-PROCEDURES X2AP-ELEMENTARY-PROCEDURE ::= {

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

handoverPreparation |
reset |
x2Setup ,
...
}
X2AP-ELEMENTARY-PROCEDURES-CLASS-2 X2AP-ELEMENTARY-PROCEDURE ::= {

snStatusTransfer |
releaseResource |
handoverCancel |
errorIndication |
loadIndication ,
...
-- **************************************************************
--
-- Interface Elementary Procedures
--
-- **************************************************************
handoverPreparation X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE HandoverRequest
SUCCESSFUL OUTCOME HandoverRequestAcknowledge
UNSUCCESSFUL OUTCOME HandoverPreparationFailure
PROCEDURE CODE id-handoverPreparation
CRITICALITY reject
}
snStatusTransfer X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE SNStatusTransfer
PROCEDURE CODE id-snStatusTransfer
CRITICALITY ignore
}
releaseResource X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE ReleaseResource
PROCEDURE CODE id-releaseResource
CRITICALITY ignore
}
3GPP
Release 8 35 3GPP TS 36.423 V8.0.0 (2007-12)
handoverCancel X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE HandoverCancel
PROCEDURE CODE id-handoverCancel
CRITICALITY ignore
}
errorIndication X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE ErrorIndication
PROCEDURE CODE id-errorIndication
CRITICALITY ignore
}
reset X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE ResetRequest
SUCCESSFUL OUTCOME ResetResponse
PROCEDURE CODE id-reset
CRITICALITY reject
}
x2Setup X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE X2SetupRequest
SUCCESSFUL OUTCOME X2SetupResponse
UNSUCCESSFUL OUTCOME X2SetupFailure
PROCEDURE CODE id-x2Setup
CRITICALITY reject
}
loadIndication X2AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE LoadInformation
PROCEDURE CODE id-loadIndication
CRITICALITY ignore
}
END
9.3.4 PDU Definitions

-- **************************************************************
--
-- PDU definitions for X2AP.
--
-- **************************************************************
X2AP-PDU-Contents {
eps-Access (21) modules (3) x2ap (2) version1 (1) x2ap-PDU-Contents (1) }
3GPP
Release 8 36 3GPP TS 36.423 V8.0.0 (2007-12)
BEGIN
-- **************************************************************
--
--
-- **************************************************************
IMPORTS
AggregateMaximumBitRate,
Bearer-ID,
Cause,
CGI,
CriticalityDiagnostics,
DL-Forwarding,
ENB-ID,
HandoverRestrictionList,
InterferenceOverloadIndication,
PDCP-SN,
PLMN-Identity,
UE-S1AP-ID,
RB-type,
RRC-Context,
SAE-BearerLevel-QoS-Parameters,
ServedCells,
TimeToWait,
TraceActivation,
TargeteNBtoSource-eNBTransparentContainer,
TraceDepth,
TraceReference,
TransportLayerAddress,
UE-HistoryInformation,
GTPtunnelEndpoint,
UE-X2AP-ID
FROM X2AP-IEs
PrivateIE-Container{},
ProtocolExtensionContainer{},
ProtocolIE-ContainerList{},
ProtocolIE-ContainerPair{},
ProtocolIE-ContainerPairList{},
ProtocolIE-Container{},
ProtocolIE-Single-Container{},
X2AP-PRIVATE-IES,
X2AP-PROTOCOL-EXTENSION,
X2AP-PROTOCOL-IES,
X2AP-PROTOCOL-IES-PAIR
FROM X2AP-Containers
id-Bearers-Admitted-Item,
id-Bearers-Admitted-List,
3GPP
Release 8 37 3GPP TS 36.423 V8.0.0 (2007-12)
id-Bearers-NotAdmitted-Item,
id-Bearers-NotAdmitted-List,
id-Bearers-SubjectToStatusTransfer-List,
id-Bearers-SubjectToStatusTransfer-Item,
id-Cause,
id-CellInformation,
id-CellInformation-Item,
id-CriticalityDiagnostics,
id-ENB-ID,
id-UE-ContextInformation,
id-Bearers-ToBeSetup-Item,
id-New-eNB-UE-X2AP-ID,
id-Old-eNB-UE-X2AP-ID,
id-ServedCells,
id-TargetCell-ID,
id-TargeteNBtoSource-eNBTransparentContainer,
id-TimeToWait,
id-TraceActivation,
id-UE-HistoryInformation,
id-UE-X2AP-ID,
maxnoofBearers,
maxnoofPDCP-SN,
maxCellineNB
FROM X2AP-Constants;
-- **************************************************************
--
-- HANDOVER REQUEST
--
-- **************************************************************
HandoverRequest ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{HandoverRequest-IEs}},
...
}
HandoverRequest-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-Old-eNB-UE-X2AP-ID CRITICALITY reject TYPE UE-X2AP-ID PRESENCE mandatory } |
{ ID id-TargetCell-ID CRITICALITY reject TYPE CGI PRESENCE mandatory } |
{ ID id-UE-ContextInformation CRITICALITY reject TYPE UE-ContextInformation PRESENCE mandatory } |
{ ID id-UE-HistoryInformation CRITICALITY reject TYPE UE-HistoryInformation PRESENCE optional } |
{ ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE optional } ,
...
}
UE-ContextInformation ::= SEQUENCE {

mME-UE-S1AP-ID UE-S1AP-ID,
aggregateMaximumBitRate AggregateMaximumBitRate,
bearers-ToBeSetup-List Bearers-ToBeSetup-List,
rRC-Context RRC-Context,
servingPLMN PLMN-Identity OPTIONAL,
handoverRestrictionList HandoverRestrictionList OPTIONAL,
3GPP
Release 8 38 3GPP TS 36.423 V8.0.0 (2007-12)
iE-Extensions ProtocolExtensionContainer { {UE-ContextInformation-ExtIEs} } OPTIONAL,
...
}
UE-ContextInformation-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
Bearers-ToBeSetup-List ::= SEQUENCE (SIZE(0..maxnoofBearers)) OF ProtocolIE-Single-Container { {Bearers-ToBeSetup-ItemIEs} }
Bearers-ToBeSetup-ItemIEs X2AP-PROTOCOL-IES ::= {

{ ID id-Bearers-ToBeSetup-Item CRITICALITY ignore TYPE Bearers-ToBeSetup-Item PRESENCE mandatory },
...
}
Bearers-ToBeSetup-Item ::= SEQUENCE {

sAE-Bearer-ID Bearer-ID,
sAE-BearerLevel-QoS-Parameters SAE-BearerLevel-QoS-Parameters,
dL-Forwarding DL-Forwarding,
uL-GTPtunnelEndpoint GTPtunnelEndpoint,
rB-type RB-type,
iE-Extensions ProtocolExtensionContainer { {Bearers-ToBeSetup-ItemExtIEs} } OPTIONAL,
...
}
Bearers-ToBeSetup-ItemExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
-- **************************************************************
--
-- HANDOVER REQUEST ACKNOWLEDGE
--
-- **************************************************************
HandoverRequestAcknowledge ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{HandoverRequestAcknowledge-IEs}},
...
}
HandoverRequestAcknowledge-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-Old-eNB-UE-X2AP-ID CRITICALITY reject TYPE UE-X2AP-ID PRESENCE mandatory} |
{ ID id-New-eNB-UE-X2AP-ID CRITICALITY reject TYPE UE-X2AP-ID PRESENCE mandatory} |
{ ID id-Bearers-Admitted-List CRITICALITY ignore TYPE Bearers-Admitted-List PRESENCE optional } |
{ ID id-Bearers-NotAdmitted-List CRITICALITY ignore TYPE Bearers-NotAdmitted-List PRESENCE optional } |
{ ID id-TargeteNBtoSource-eNBTransparentContainer CRITICALITY ignore TYPE TargeteNBtoSource-eNBTransparentContainer PRESENCE },
...
}
Bearers-Admitted-List ::= SEQUENCE (SIZE (1..maxnoofBearers)) OF ProtocolIE-Single-Container { {Bearers-Admitted-ItemIEs} }
3GPP
Release 8 39 3GPP TS 36.423 V8.0.0 (2007-12)
Bearers-Admitted-ItemIEs X2AP-PROTOCOL-IES ::= {
{ ID id-Bearers-Admitted-Item CRITICALITY ignore TYPE Bearers-Admitted-Item PRESENCE mandatory }
}
Bearers-Admitted-Item ::= SEQUENCE {

bearer-ID Bearer-ID,
uL-GTP-TunnelEndpoint GTPtunnelEndpoint OPTIONAL,
dL-GTP-TunnelEndpoint GTPtunnelEndpoint OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {Bearers-Admitted-Item-ExtIEs} } OPTIONAL,
...
}
Bearers-Admitted-Item-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
Bearers-NotAdmitted-List ::= SEQUENCE (SIZE (1..maxnoofBearers)) OF ProtocolIE-Single-Container { {Bearers-NotAdmitted-ItemIEs} }
Bearers-NotAdmitted-ItemIEs X2AP-PROTOCOL-IES ::= {

{ ID id-Bearers-NotAdmitted-Item CRITICALITY ignore TYPE Bearers-NotAdmitted-Item PRESENCE mandatory }
}
Bearers-NotAdmitted-Item ::= SEQUENCE {

cause Cause,
iE-Extensions ProtocolExtensionContainer { {Bearers-NotAdmitted-Item-ExtIEs} } OPTIONAL,
...
}
Bearers-NotAdmitted-Item-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
-- **************************************************************
--
-- HANDOVER PREPARATION FAILURE
--
-- **************************************************************
HandoverPreparationFailure ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{HandoverPreparationFailure-IEs}},
...
}
HandoverPreparationFailure-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory} ,
...
}
-- **************************************************************
--
3GPP
Release 8 40 3GPP TS 36.423 V8.0.0 (2007-12)
-- SN Status Transfer
--
-- **************************************************************
SNStatusTransfer ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{SNStatusTransfer-IEs}},
...
}
SNStatusTransfer-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-Bearers-SubjectToStatusTransfer-List CRITICALITY ignore TYPE Bearers-SubjectToStatusTransfer-List PRESENCE mandatory} ,
...
}
Bearers-SubjectToStatusTransfer-List ::= SEQUENCE (SIZE (1..maxnoofBearers)) OF ProtocolIE-Single-Container { { Bearers-SubjectToStatusTransfer-

ItemIEs} }
Bearers-SubjectToStatusTransfer-ItemIEs X2AP-PROTOCOL-IES ::= {

{ ID id-Bearers-SubjectToStatusTransfer-Item CRITICALITY ignore TYPE Bearers-SubjectToStatusTransfer-Item PRESENCE mandatory }
}
Bearers-SubjectToStatusTransfer-Item ::= SEQUENCE {

pDCP-SNofULSDUsNotToBeRetransmitted-List PDCP-SNofULSDUsNotToBeRetransmitted-List OPTIONAL,
uL-PDCP-SN-NextInSequenceExpected PDCP-SN,
dL-PDCP-SN-NextToAssign PDCP-SN,
iE-Extensions ProtocolExtensionContainer { {Bearers-SubjectToStatusTransfer-ItemExtIEs} } OPTIONAL,
...
}
Bearers-SubjectToStatusTransfer-ItemExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
PDCP-SNofULSDUsNotToBeRetransmitted-List ::= SEQUENCE (SIZE (1..maxnoofPDCP-SN)) OF PDCP-SN
-- **************************************************************
--
-- Release Resource
--
-- **************************************************************
ReleaseResource ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{ReleaseResource-IEs}},
...
}
ReleaseResource-IEs X2AP-PROTOCOL-IES ::= {
3GPP
Release 8 41 3GPP TS 36.423 V8.0.0 (2007-12)
{ ID id-New-eNB-UE-X2AP-ID CRITICALITY reject TYPE UE-X2AP-ID PRESENCE mandatory} ,
...
}
-- **************************************************************
--
-- HANDOVER CANCEL
--
-- **************************************************************
HandoverCancel ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{HandoverCancel-IEs}},
...
}
HandoverCancel-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory} ,
...
}
-- **************************************************************
--
-- ERROR INDICATION
--
-- **************************************************************
ErrorIndication ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{ErrorIndication-IEs}},
...
}
ErrorIndication-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-Old-eNB-UE-X2AP-ID CRITICALITY ignore TYPE UE-X2AP-ID PRESENCE optional} |
{ ID id-New-eNB-UE-X2AP-ID CRITICALITY ignore TYPE UE-X2AP-ID PRESENCE optional} |
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional} |
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional} ,
...
}
-- **************************************************************
--
-- Reset Request
--
-- **************************************************************
ResetRequest ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{ResetRequest-IEs}},
3GPP
Release 8 42 3GPP TS 36.423 V8.0.0 (2007-12)
...
}
ResetRequest-IEs X2AP-PROTOCOL-IES ::= {

...
}
-- **************************************************************
--
-- Reset Response
--
-- **************************************************************
ResetResponse ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{ResetResponse-IEs}},
...
}
ResetResponse-IEs X2AP-PROTOCOL-IES ::= {

...
}
-- **************************************************************
--
-- X2 SETUP REQUEST
--
-- **************************************************************
X2SetupRequest ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{X2SetupRequest-IEs}},
...
}
X2SetupRequest-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-ENB-ID CRITICALITY reject TYPE ENB-ID PRESENCE mandatory} |
{ ID id-ServedCells CRITICALITY reject TYPE ServedCells PRESENCE mandatory} ,
...
}
-- **************************************************************
--
-- X2 SETUP RESPONSE
--
-- **************************************************************
X2SetupResponse ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{X2SetupResponse-IEs}},
...
}
X2SetupResponse-IEs X2AP-PROTOCOL-IES ::= {
3GPP
Release 8 43 3GPP TS 36.423 V8.0.0 (2007-12)
{ ID id-ENB-ID CRITICALITY reject TYPE ENB-ID PRESENCE mandatory} |
{ ID id-ServedCells CRITICALITY reject TYPE ServedCells PRESENCE mandatory} ,
...
}
-- **************************************************************
--
-- X2 SETUP FAILURE
--
-- **************************************************************
X2SetupFailure ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{X2SetupFailure-IEs}},
...
}
X2SetupFailure-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory} |
{ ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional} ,
...
}
-- **************************************************************
--
-- LOAD INFORMATION
--
-- **************************************************************
LoadInformation ::= SEQUENCE {

protocolIEs ProtocolIE-Container {{LoadInformation-IEs}},
...
}
LoadInformation-IEs X2AP-PROTOCOL-IES ::= {

{ ID id-CellInformation CRITICALITY ignore TYPE CellInformation-List PRESENCE mandatory} ,
...
}
CellInformation-List ::= SEQUENCE (SIZE (1..maxCellineNB)) OF ProtocolIE-Single-Container { {CellInformation-ItemIEs} }
CellInformation-ItemIEs X2AP-PROTOCOL-IES ::= {

{ ID id-CellInformation-Item CRITICALITY ignore TYPE CellInformation-Item PRESENCE mandatory }
}
CellInformation-Item ::= SEQUENCE {

global-Cell-ID CGI,
interferenceOverloadIndication InterferenceOverloadIndication OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {CellInformation-Item-ExtIEs} } OPTIONAL,
...
3GPP
Release 8 44 3GPP TS 36.423 V8.0.0 (2007-12)
}
CellInformation-Item-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
-- **************************************************************
--
-- PRIVATE MESSAGE
--
-- **************************************************************
PrivateMessage ::= SEQUENCE {

privateIEs PrivateIE-Container {{PrivateMessage-IEs}},
...
}
PrivateMessage-IEs X2AP-PRIVATE-IES ::= {

...
}
END
9.3.5 Information Element definitions

-- **************************************************************
--
-- Information Element Definitions
--
-- **************************************************************
X2AP-IEs {
eps-Access (21) modules (3) x2ap (2) version1 (1) x2ap-IEs (2) }
BEGIN
IMPORTS
id-InterfacesToTrace-Item,
maxInterfaces,
maxNrOfErrors,
maxnoofCells,
maxnoofEPLMNs,
maxnoofEPLMNsPlusOne,
maxnoofForbLACs,
maxnoofForbTAIs,
maxCellineNB,
maxnoofBPLMNs
FROM X2AP-Constants
3GPP
Release 8 45 3GPP TS 36.423 V8.0.0 (2007-12)
Criticality,
ProcedureCode,
ProtocolIE-ID,
TriggeringMessage
FROM X2AP-CommonDataTypes
ProtocolIE-Single-Container{},
ProtocolExtensionContainer{},
X2AP-PROTOCOL-IES,
X2AP-PROTOCOL-EXTENSION
FROM X2AP-Containers;
-- A
AggregateMaximumBitRate ::= SEQUENCE {

aggregateMaximumBitRateDownlink SAE-BearerBitRate,
aggregateMaximumBitRateUplink SAE-BearerBitRate,
...
}
-- B
Bearer-ID ::= BIT STRING (SIZE (8)) -- To be checked, FFS
BroadcastPLMNs-Item ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF PLMN-Identity
-- C
Cause ::= CHOICE {

radioNetwork CauseRadioNetwork,
transport CauseTransport,
protocol CauseProtocol,
misc CauseMisc,
...
}
CauseMisc ::= ENUMERATED {

control-processing-overload,
hardware-failure,
om-intervention,
not-enough-user-plane-processing-resources,
unspecified,
...
}
CauseProtocol ::= ENUMERATED {

transfer-syntax-error,
abstract-syntax-error-reject,
abstract-syntax-error-ignore-and-notify,
message-not-compatible-with-receiver-state,
semantic-error,
3GPP
Release 8 46 3GPP TS 36.423 V8.0.0 (2007-12)
unspecified,
abstract-syntax-error-falsely-constructed-message,
...
}
CauseRadioNetwork ::= ENUMERATED {

unspecified,
...
CauseTransport ::= ENUMERATED {

transport-resource-unavailable,
unspecified,
...
}
CellType ::= ENUMERATED{

macro,
micro,
pico,
femto,
...
}
CellId ::= OCTET STRING
CGI ::= SEQUENCE {

pLMN-Identity PLMN-Identity,
lAC LAC,
cI CI,
iE-Extensions ProtocolExtensionContainer { {CGI-ExtIEs} } OPTIONAL
}
CGI-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
CI ::= OCTET STRING (SIZE (2))
CriticalityDiagnostics ::= SEQUENCE {

procedureCode ProcedureCode OPTIONAL,
triggeringMessage TriggeringMessage OPTIONAL,
procedureCriticality Criticality OPTIONAL,
iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL,
...
}
CriticalityDiagnostics-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
3GPP
Release 8 47 3GPP TS 36.423 V8.0.0 (2007-12)
}
CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF

SEQUENCE {
iECriticality Criticality,
iE-ID ProtocolIE-ID,
typeOfError TypeOfError,
iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL,
...
}
CriticalityDiagnostics-IE-List-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
-- D
DL-data-received ::= INTEGER
DL-Forwarding ::= ENUMERATED {

dL-forwardingProposed,
...
}
-- E
ENB-ID ::= INTEGER (0..65535) -- Value to be checked FFS
EPLMNs ::= SEQUENCE (SIZE(1..maxnoofEPLMNs)) OF PLMN-Identity
-- F
ForbiddenInterRATs ::= ENUMERATED {

all,
gsm,
wcdma,
...
}
ForbiddenTAs ::= SEQUENCE (SIZE(1.. maxnoofEPLMNsPlusOne)) OF ForbiddenTAs-Item
ForbiddenTAs-Item ::= SEQUENCE {

forbiddenTAIs ForbiddenTAIs
}
ForbiddenTAIs ::= SEQUENCE (SIZE(1..maxnoofForbTAIs)) OF TAI
ForbiddenLAs ::= SEQUENCE (SIZE(1..maxnoofEPLMNsPlusOne)) OF ForbiddenLAs-Item
3GPP
Release 8 48 3GPP TS 36.423 V8.0.0 (2007-12)
ForbiddenLAs-Item ::= SEQUENCE {
forbiddenLACs ForbiddenLACs
}
ForbiddenLACs ::= SEQUENCE (SIZE(1..maxnoofForbLACs)) OF LAC
Frequency ::= OCTET STRING
-- G
GTPtunnelEndpoint ::= SEQUENCE {

transportLayerAddress TransportLayerAddress,
gTP-TEID GTP-TEI,
iE-Extensions ProtocolExtensionContainer { {GTPtunnelEndpoint-ExtIEs} } OPTIONAL,
...
}
GTPtunnelEndpoint-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
GTP-TEI ::= OCTET STRING (SIZE (4))
-- H
HandoverRestrictionList ::= SEQUENCE {

equivalentPLMNs EPLMNs OPTIONAL,
forbiddenTAs ForbiddenTAs OPTIONAL,
forbiddenLAs ForbiddenLAs OPTIONAL,
forbiddenInterRATs ForbiddenInterRATs OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {HandoverRestrictionList-ExtIEs} } OPTIONAL,
...
}
HandoverRestrictionList-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
-- I
InterfacesToTrace ::= SEQUENCE (SIZE(0..maxInterfaces)) OF ProtocolIE-Single-Container {{InterfacesToTrace-ItemIEs} }
InterfacesToTrace-ItemIEs X2AP-PROTOCOL-IES ::= {

{ ID id-InterfacesToTrace-Item CRITICALITY ignore TYPE InterfacesToTrace-Item PRESENCE mandatory }
}
InterfacesToTrace-Item ::= SEQUENCE {

traceInterface TraceInterface,
3GPP
Release 8 49 3GPP TS 36.423 V8.0.0 (2007-12)
traceDepth TraceDepth,
iE-Extensions ProtocolExtensionContainer { {InterfacesToTrace-Item-ExtIEs} } OPTIONAL,
...
}
InterfacesToTrace-Item-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
InterferenceOverloadIndication ::= OCTET STRING -- FFS
-- J
-- K
-- L
LAC ::= OCTET STRING (SIZE (2)) --(EXCEPT ('0000'H|'FFFE'H))
LastVisitedCell-Item ::= SEQUENCE {

global-Cell-ID CGI,
cellType CellType,
time-UE-StayedInCell Time-UE-StayedInCell OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {LastVisitedCell-Item-ExtIEs} } OPTIONAL,
...
}
LastVisitedCell-Item-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
-- M
-- N
-- O
-- P
PDCP-SN ::= INTEGER -- FFS
PhyCID ::= OCTET STRING
PLMN-Identity ::= OCTET STRING (SIZE(3))
-- Q
-- R
RB-type ::= INTEGER

-- Editors note: FFS To be replaced by other QCI definition, ENUMERATED??
RRC-Context ::= OCTET STRING
-- S
3GPP
Release 8 50 3GPP TS 36.423 V8.0.0 (2007-12)
SAE-BearerBitRate ::= INTEGER (0..210000000000)
SAE-BearerLevel-QoS-Parameters ::= SEQUENCE {

label INTEGER (1..256),
allocationAndRetentionPriority OCTET STRING, --FFS
sAE-BearerType SAE-BearerType,
...
}
SAE-BearerType ::= CHOICE {

sAE-GBR-bearer SAE-GBR-bearer,
sAE-non-GBR-bearer SAE-Non-GBR-bearer,
...
}
SAE-GBR-Bearer ::= SEQUENCE {

sAE-Bearer-MaximumBitrateDL SAE-Bearer-BitRate,
sAE-Bearer-MaximumBitrateUL SAE-Bearer-BitRate,
sAE-Bearer-GuaranteedBitrateDL SAE-Bearer-BitRate,
sAE-Bearer-GuaranteedBitrateUL SAE-Bearer-BitRate,
iE-Extensions ProtocolExtensionContainer { {SAE-GBR-Bearer-Parameters-ExtIEs} } OPTIONAL,
...
}
SAE-GBR-Bearer-Parameters-ExtIEs S1AP-PROTOCOL-EXTENSION ::= {

...
}
SAE-non-GBR-Bearer ::= SEQUENCE {

sAE-non-GBR-Bearer-Type ENUMERATED {non-GBR-Bearer,...},
iE-Extensions ProtocolExtensionContainer { {SAE-non-GBR-Bearer-Parameters-ExtIEs} } OPTIONAL,
...
}
SAE-non-GBR-Bearer-Parameters-ExtIEs S1AP-PROTOCOL-EXTENSION ::= {

...
}
ServedCells ::= SEQUENCE (SIZE (1..maxCellineNB)) OF ServedCell-Information
ServedCell-Information ::= SEQUENCE {

phyCID PhyCID,
cellId CellId,
tAI TAI,
broadcastPLMNs BroadcastPLMNs-Item,
frequency Frequency,
iE-Extensions ProtocolExtensionContainer { {ServedCell-Information-ExtIEs} } OPTIONAL,
3GPP
Release 8 51 3GPP TS 36.423 V8.0.0 (2007-12)
...
}
ServedCell-Information-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
-- T
TAI ::= OCTET STRING -- FFS
TargeteNBtoSource-eNBTransparentContainer ::= OCTET STRING
Time-UE-StayedInCell ::= INTEGER
TimeToWait ::= OCTET STRING
TraceActivation ::= SEQUENCE {

traceReference TraceReference,
interfacesToTrace InterfacesToTrace,
iE-Extensions ProtocolExtensionContainer { {TraceActivation-ExtIEs} } OPTIONAL,
...
}
TraceActivation-ExtIEs X2AP-PROTOCOL-EXTENSION ::= {

...
}
TraceDepth ::= ENUMERATED {

minimum,
medium,
maximum,
...
}
TraceInterface ::= ENUMERATED {

s1,
x2,
uu,
...
}
TraceReference ::= OCTET STRING (SIZE (3))
TransportLayerAddress ::= BIT STRING (SIZE(1..160, ...))
TypeOfError ::= ENUMERATED {

not-understood,
3GPP
Release 8 52 3GPP TS 36.423 V8.0.0 (2007-12)
missing,
...
}
-- U
UE-HistoryInformation ::= SEQUENCE (SIZE(1..maxnoofCells)) OF LastVisitedCell-Item
UE-S1AP-ID ::= INTEGER (0..4095) –- Value FFS
UE-X2AP-ID ::= INTEGER (0..4095) –- Value FFS
-- V
-- W
-- X
-- Y
-- Z
END
9.3.6 Common definitions

-- **************************************************************
--
-- Common definitions
--
-- **************************************************************
X2AP-CommonDataTypes {
eps-Access (21) modules (3) x2ap (2) version1 (1) x2ap-CommonDataTypes (3) }
BEGIN
-- **************************************************************
--
-- Extension constants
--
-- **************************************************************
maxPrivateIEs INTEGER ::= 65535

maxProtocolExtensions INTEGER ::= 65535
maxProtocolIEs INTEGER ::= 65535
3GPP
Release 8 53 3GPP TS 36.423 V8.0.0 (2007-12)
-- **************************************************************
--
-- Common Data Types
--
-- **************************************************************
Criticality ::= ENUMERATED { reject, ignore, notify }
Presence ::= ENUMERATED { optional, conditional, mandatory }
PrivateIE-ID ::= CHOICE {

local INTEGER (0.. maxPrivateIEs),
global OBJECT IDENTIFIER
}
ProcedureCode ::= INTEGER (0..255)
ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs)
TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome}
END
9.3.7 Constant definitions

-- **************************************************************
--
-- Constant definitions
--
-- **************************************************************
X2AP-Constants {
eps-Access (21) modules (3) x2ap (2) version1 (1) x2ap-Constants (4) }
BEGIN
IMPORTS
ProcedureCode,
ProtocolIE-ID
FROM X2AP-CommonDataTypes;
-- **************************************************************
--
-- Elementary Procedures
--
-- **************************************************************
3GPP
Release 8 54 3GPP TS 36.423 V8.0.0 (2007-12)
id-handoverPreparation ProcedureCode ::= 0

id-handoverCancel ProcedureCode ::= 1
id-loadIndication ProcedureCode ::= 2
id-errorIndication ProcedureCode ::= 3
id-snStatusTransfer ProcedureCode ::= 4
id-releaseResource ProcedureCode ::= 5
id-x2Setup ProcedureCode ::= 6
id-reset ProcedureCode ::= 7
-- **************************************************************
--
-- Lists
--
-- **************************************************************
maxInterfaces INTEGER ::= 16 -- FFS Value to be checked

maxCellineNB INTEGER ::= 256 -- FFS Value to be checked
maxnoofCells INTEGER ::= 16 -- FFS Value to be checked
maxnoofBearers INTEGER ::= 16 -- FFS Value to be checked
maxNrOfErrors INTEGER ::= 256 -- FFS Value to be checked
maxnoofPDCP-SN INTEGER ::= 16 -- FFS Value to be checked
maxnoofEPLMNs INTEGER ::= 15
maxnoofEPLMNsPlusOne INTEGER ::= 16
maxnoofForbLACs INTEGER ::= 256 -- FFS Value to be checked
maxnoofForbTAIs INTEGER ::= 256 -- FFS Value to be checked
maxnoofBPLMNs INTEGER ::= 6
-- **************************************************************
--
-- IEs
--
-- **************************************************************
id-Bearers-Admitted-Item ProtocolIE-ID ::= 0

id-Bearers-Admitted-List ProtocolIE-ID ::= 1
id-Bearers-NotAdmitted-Item ProtocolIE-ID ::= 2
id-Bearers-NotAdmitted-List ProtocolIE-ID ::= 3
id-Bearers-ToBeSetup-Item ProtocolIE-ID ::= 4
id-Cause ProtocolIE-ID ::= 5
id-CellInformation ProtocolIE-ID ::= 6
id-CellInformation-Item ProtocolIE-ID ::= 7
id-InterfacesToTrace-Item ProtocolIE-ID ::= 8
id-New-eNB-UE-X2AP-ID ProtocolIE-ID ::= 9
id-Old-eNB-UE-X2AP-ID ProtocolIE-ID ::= 10
id-TargetCell-ID ProtocolIE-ID ::= 11
id-TargeteNBtoSource-eNBTransparentContainer ProtocolIE-ID ::= 12
id-TraceActivation ProtocolIE-ID ::= 13
3GPP
Release 8 55 3GPP TS 36.423 V8.0.0 (2007-12)
id-UE-ContextInformation ProtocolIE-ID ::= 14
id-UE-HistoryInformation ProtocolIE-ID ::= 15
id-UE-X2AP-ID ProtocolIE-ID ::= 16
id-CriticalityDiagnostics ProtocolIE-ID ::= 17
id-Bearers-SubjectToStatusTransfer-List ProtocolIE-ID ::= 18
id-Bearers-SubjectToStatusTransfer-Item ProtocolIE-ID ::= 19
id-ServedCells ProtocolIE-ID ::= 20
id-ENB-ID ProtocolIE-ID ::= 21
id-TimeToWait ProtocolIE-ID ::= 22
END
9.3.8 Container definitions

-- **************************************************************
--
-- Container definitions
--
-- **************************************************************
X2AP-Containers {
eps-Access (21) modules (3) x2ap (2) version1 (1) x2ap-Containers (5) }
BEGIN
-- **************************************************************
--
--
-- **************************************************************
IMPORTS
maxPrivateIEs,
maxProtocolExtensions,
maxProtocolIEs,
Criticality,
Presence,
PrivateIE-ID,
ProtocolIE-ID
FROM X2AP-CommonDataTypes;
-- **************************************************************
--
-- Class Definition for Protocol IEs
--
-- **************************************************************
3GPP
Release 8 56 3GPP TS 36.423 V8.0.0 (2007-12)
X2AP-PROTOCOL-IES ::= CLASS {
&id ProtocolIE-ID UNIQUE,
&criticality Criticality,
&Value,
&presence Presence
}
WITH SYNTAX {
ID &id
CRITICALITY &criticality
TYPE &Value
PRESENCE &presence
}
-- **************************************************************
--
-- Class Definition for Protocol IEs
--
-- **************************************************************
X2AP-PROTOCOL-IES-PAIR ::= CLASS {

&firstCriticality Criticality,
&FirstValue,
&secondCriticality Criticality,
&SecondValue,
&presence Presence
}
WITH SYNTAX {
ID &id
FIRST CRITICALITY &firstCriticality
FIRST TYPE &FirstValue
SECOND CRITICALITY &secondCriticality
SECOND TYPE &SecondValue
PRESENCE &presence
}
-- **************************************************************
--
-- Class Definition for Protocol Extensions
--
-- **************************************************************
X2AP-PROTOCOL-EXTENSION ::= CLASS {

&Extension,
&presence Presence
}
WITH SYNTAX {
ID &id
EXTENSION &Extension
PRESENCE &presence
3GPP
Release 8 57 3GPP TS 36.423 V8.0.0 (2007-12)
}
-- **************************************************************
--
-- Class Definition for Private IEs
--
-- **************************************************************
X2AP-PRIVATE-IES ::= CLASS {

&id PrivateIE-ID,
&Value,
&presence Presence
}
WITH SYNTAX {
ID &id
TYPE &Value
PRESENCE &presence
}
-- **************************************************************
--
-- Container for Protocol IEs
--
-- **************************************************************
ProtocolIE-Container {X2AP-PROTOCOL-IES : IEsSetParam} ::=

SEQUENCE (SIZE (0..maxProtocolIEs)) OF
ProtocolIE-Field {{IEsSetParam}}
ProtocolIE-Single-Container {X2AP-PROTOCOL-IES : IEsSetParam} ::=

ProtocolIE-Field {{IEsSetParam}}
ProtocolIE-Field {X2AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {

id X2AP-PROTOCOL-IES.&id ({IEsSetParam}),
criticality X2AP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}),
value X2AP-PROTOCOL-IES.&Value ({IEsSetParam}{@id})
}
-- **************************************************************
--
-- Container for Protocol IE Pairs
--
-- **************************************************************
ProtocolIE-ContainerPair {X2AP-PROTOCOL-IES-PAIR : IEsSetParam} ::=

SEQUENCE (SIZE (0..maxProtocolIEs)) OF
ProtocolIE-FieldPair {{IEsSetParam}}
ProtocolIE-FieldPair {X2AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE {

id X2AP-PROTOCOL-IES-PAIR.&id ({IEsSetParam}),
firstCriticality X2AP-PROTOCOL-IES-PAIR.&firstCriticality ({IEsSetParam}{@id}),
3GPP
Release 8 58 3GPP TS 36.423 V8.0.0 (2007-12)
firstValue X2AP-PROTOCOL-IES-PAIR.&FirstValue ({IEsSetParam}{@id}),
secondCriticality X2AP-PROTOCOL-IES-PAIR.&secondCriticality ({IEsSetParam}{@id}),
secondValue X2AP-PROTOCOL-IES-PAIR.&SecondValue ({IEsSetParam}{@id})
}
-- **************************************************************
--
-- Container Lists for Protocol IE Containers
--
-- **************************************************************
ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, X2AP-PROTOCOL-IES : IEsSetParam} ::=

SEQUENCE (SIZE (lowerBound..upperBound)) OF
ProtocolIE-Container {{IEsSetParam}}
ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, X2AP-PROTOCOL-IES-PAIR : IEsSetParam} ::=

SEQUENCE (SIZE (lowerBound..upperBound)) OF
ProtocolIE-ContainerPair {{IEsSetParam}}
-- **************************************************************
--
-- Container for Protocol Extensions
--
-- **************************************************************
ProtocolExtensionContainer {X2AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::=

SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
ProtocolExtensionField {{ExtensionSetParam}}
ProtocolExtensionField {X2AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {

id X2AP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}),
criticality X2AP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}),
extensionValue X2AP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id})
}
-- **************************************************************
--
-- Container for Private IEs
--
-- **************************************************************
PrivateIE-Container {X2AP-PRIVATE-IES : IEsSetParam} ::=

SEQUENCE (SIZE (1..maxPrivateIEs)) OF
PrivateIE-Field {{IEsSetParam}}
PrivateIE-Field {X2AP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE {

id X2AP-PRIVATE-IES.&id ({IEsSetParam}),
criticality X2AP-PRIVATE-IES.&criticality ({IEsSetParam}{@id}),
value X2AP-PRIVATE-IES.&Value ({IEsSetParam}{@id})
}
END
3GPP
Release 8 59 3GPP TS 36.423 V8.0.0 (2007-12)
9.4 Message transfer syntax

X2AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified
in ref. [5].
9.5 Timers
TRELOCprep
- Specifies the maximum time for the Handover Preparation procedure in the source eNodeB.
TX2RELOCoverall
- Specifies the maximum time for the protection of the overall handover procedure in the source eNodeB.
10 Handling of unknown, unforeseen and erroneous

protocol data
Section 10 of [4] is applicable for the purposes of the present document.
3GPP
Release 8 60 3GPP TS 36.423 V8.0.0 (2007-12)
Annex A (informative):
Change history
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Old New
2007-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.0
2007-10 Inclusion of agreements from RAN3#57bis as well as 1.0.0 1.0.1
editorials
2007-11 Inclusion of agreements from RAN3#58 as well as editorials 1.0.1 1.1.0
2007-11 38 RP-070856 Presentation to TSG-RAN for approval - version 2.0.0 1.1.0 2.0.0
2007-12 38 approved at TSG-RAN and placed under change control 2.0.0 8.0.0
3GPP

HO Message

Uploaded by

Copyright:

Available Formats

HO Message

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HO Message

Uploaded by

Copyright:

Available Formats

3GPP TS 36.423 V8.0.

3rd Generation Partnership Project;

3GPP support office address

No part may be reproduced except as authorized by written permission.

8.3.3.3 Unsuccessful Operation........................................................................................................................ 15

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.

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

[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)”.

3 Definitions, symbols and abbreviations

<defined term>: <definition>.

4.1 Procedure specification principles

- The procedure text discriminates between:

1) Functionality which "shall" be executed

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

4.2 Forwards and backwards compatibility

4.3 Specification notations

5.1 X2AP procedure modules

1. X2AP Basic Mobility Procedures;

2. X2AP Global Procedures;

5.2 Parallel transactions

6 Services expected from signalling transport

8.1 Elementary procedures

Table 2: Class 1 Elementary Procedures

Elementary Initiating Message Successful Outcome Unsuccessful Outcome

Handover Cancel HANDOVER CANCEL

Table 3: Class 2 Elementary Procedures

8.2 Basic mobility procedures

8.2.1.2 Successful Operation

HANDOVER REQUEST ACKNOWLEDGE

Figure 8.2.1.2-1: Handover preparation: successful operation

If the Handover Restriction List IE is

8.2.1.2.1 UE History Information

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

8.2.1.3 Unsuccessful Operation

HANDOVER PREPARATION FAILURE

Figure 8.2.1.3-1: Handover preparation: unsuccessful operation

Interactions with Handover Cancel procedure:

8.2.1.4 Abnormal Conditions

8.2.2 SN Status Transfer

8.2.2.2 Successful Operation

Figure 8.2.2.2-1: SN Status transfer

8.2.2.2 Abnormal Conditions

8.2.3 Release Resource

8.2.3.2 Successful Operation

[X2 AP] Release Resource

Figure 8.2.3.2-1: Release Resource procedure

8.2.3.3 Unsuccessful Operation

8.2.3.4 Abnormal Conditions

8.2.4 Handover Cancel

8.2.4.2 Successful Operation

Figure 8.2.4.2-1: Handover cancel

8.2.4.3 Unsuccessful Operation

8.2.4.4 Abnormal Conditions

8.3 Global Procedures