BMSat-36.423V1.0.0 (2013-08)
Technical Specification
China Communications Standards Association (CCSA);
BMSatRadio Interface Specifications;
Evolved Universal Satellite Radio Access Network (E-USRAN);
X2 application protocol (X2AP)
(Release 1)
The present document has been developed within China Communications Standards Association (CCSA) and may be further elaborated for the purposes of CCSA.
BMSat-36.423 V1.0.0 (2013-08)
1
Release 1
Keywords
BMSat, radio
CCSA
Postal address
CCSA Secretariat office address
No.52 Hua Yuan Bei Road
Haidian District
Beijing, China 100083
Telephone: +86 10 62304228
Fax: +86 10 62301849
Email:
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.
© 2012, China Communications Standards Association
All rights reserved.
Contents
Contents
Foreword
Introduction
1Scope
2References
3Definitions, symbols and abbreviations
3.1Definitions
3.2Symbols
3.3Abbreviations
4General
5X2AP services
6Services expected from signalling transport
7Functions of X2AP
8X2AP procedures
8.1Elementary procedures
8.2Basic mobility procedures
8.2.1Handover Preparation
8.2.2 SN Status Transfer
8.2.3UE Context Release
8.2.4Handover Cancel
8.3 Global Procedures
9Elements for X2AP Communication
9.0General
9.1Message Functional Definition and Content
9.1.1Messages for Basic Mobility Procedures
9.1.2Messages for global procedures
9.2Information Element definitions
9.2.0General
9.2.1GTP Tunnel Endpoint
9.2.2Trace Activation
9.2.3Handover Restriction List
9.2.4PLMN Identity
9.2.5DL Forwarding
9.2.6Cause
9.2.7Criticality Diagnostics
9.2.8Served Cell Information
9.2.9E-RAB Level QoS Parameters
9.2.10GBR QoS Information
9.2.11Bit Rate
9.2.12UE Aggregate Maximum Bit Rate
9.2.13Message Type
9.2.14ECGI
9.2.15COUNT Value
9.2.16GUMMEI
9.2.17UL Interference Overload Indication
9.2.18UL High Interference Indication
9.2.19Relative Narrowband Tx Power (RNTP)
9.2.20GU Group Id
9.2.21Location Reporting Information
9.2.22Global SAT-eNB ID
9.2.23E-RAB ID
9.2.24SAT-eNB UE X2AP ID
9.2.25Subscriber Profile ID for RAT/Frequency priority
9.2.26EARFCN
9.2.27Transmission Bandwidth
9.2.28E-RAB List
9.2.29UE Security Capabilities
9.2.30AS Security Information
9.2.31Allocation and Retention Priority
9.2.32Time to Wait
9.2.33SRVCC Operation Possible
9.2.34Hardware Load Indicator
9.2.35S1 TNL Load Indicator
9.2.36Load Indicator
9.2.37Radio Resource Status
9.2.38UE History Information
9.2.39Last Visited Cell Information
9.2.40Last Visited E-UTRAN Cell Information
9.2.41Last Visited GERAN Cell Information
9.2.42Cell Type
9.2.43Number of Antenna Ports
9.2.44Composite Available Capacity Group
9.2.45Composite Available Capacity
9.2.46Cell Capacity Class Value
9.2.47Capacity Value
9.2.48Mobility Parameters Information
9.2.49Mobility Parameters Modification Range
9.2.50PRACH Configuration
9.2.51Subframe Allocation
9.2.52CSG Membership Status
9.2.53CSG ID
9.2.54Uplink Synchronization
9.3Message and Information Element Abstract Syntax (with ASN.1)
9.4Message transfer syntax
9.5Timers
10Handling of unknown, unforeseen and erroneous protocol data
Foreword
This Technical Specification has been produced byChina Communications Standards Association (CCSA).
The contents of the present document are subject to continuing work within CCSA and may change following formal CCSA approval. Should CCSA modify the contents of the present document, it will be re-released by CCSA with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
xthe first digit:
1or greater indicates CCSA approved document under change control.
ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
zthe third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
Broadband Mobile Satellite (BMSat)radio interface is mainly used for mobile satellite services(MSS) utilizing geostationary satellite(s). BMSatis derived from the terrestrial LTE-Advanced specifications (also known as LTE Release 10 and beyond developed by 3GPP)andsupports access to LTE-Advanced core networks.Currently,BMSatsupportsonlyFDDmode,andthedescriptionsofTDDmodeintheterrestrialLTE-AdvancedspecificationsarenotappliedtoBMSat.
NOTE: The LTE-Advanced standards documents referenced in BMSat specifications are the transposed documents provided by CCSA which is one of the identified Transposing Organizations of 3GPP LTE-Advanced specifications in ITU-R Recommendation M.2012. The detailed transposing relationship between CCSA transposed LTE-Advanced documents and 3GPP LTE-Advanced documents is shown in ITU-R Recommendation M.2012.
Due to the differences between terrestrial and satellite channels, a number of modifications to LTE-Advanced are made to adapt to satellite radio transmission.
Some LTE-Advanced specifications are directly applicable, whereas others are applicable with modifications. Similarly, someLTE-Advanced specifications do not apply, while some BMSat specifications have no corresponding LTE-Advanced specification.
Since BMSat is derived from LTE-Advanced, the organization of the BMSat specifications closely follows that of LTE-Advanced. The BMSat numbers have been designed to correspond to the LTE-Advanced numbering system. All BMSat specifications are allocated aunique BMSat number as follows:
BMSat xx.yyy.z
where:
-xx.yyy.z (z = 0) is used for BMSat specifications that have a corresponding LTE-Advanced specification. In this case, thenumbers xx and yyy correspond to the LTE-Advanced numbering scheme.
-xx.yyy.z (z = 2) is used for BMSat specifications that do not correspond to a LTE-Advanced specification. In this case,only the number xx corresponds to the LTE-Advanced numbering scheme and the number yyy is allocated by BMSat.
A BMSat system is defined by the combination of a family of BMSat specifications and LTE-Advanced specifications as follows:
-If a BMSat specification exists it takes precedence over the corresponding LTE-Advanced specification (if any). Thisprecedence rule applies to any references in the corresponding LTE-Advanced specifications.
NOTE: Any references to LTE-Advanced specifications within the BMSat specifications are not subject to this precedencerule. For example, a BMSat specification may contain specific references to the corresponding LTE-Advanced specification.
-If a BMSat specification does not exist, the corresponding LTE-Advanced specification may or may not apply. Theapplicability of the LTE-Advanced specifications is defined inBMSat-36.001.2 [1].
1Scope
The present document specifies the radio network layer signalling procedures of the control plane between Satellite eNBs in E-USRAN. 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].
2References
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 nonspecific.
- 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]BMSat-36.001.2: “Introduction to the BMSat family”
[2] CCSA-TSD-LTE-36.423: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN);X2 application protocal (X2AP) ;”
[3] CCSA-TSD-LTE-36.420: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 General Aspects and Principles”.
3Definitions, symbols and abbreviations
3.1Definitions
Same as clause 3.1 of CCSA-TSD-LTE-36.423 [2]
3.2Symbols
Same as clause 3.2 of CCSA-TSD-LTE-36.423 [2]
3.3Abbreviations
For the purposes of the present document, the following abbreviations apply：
E-USRANEvolved USRAN
Other abbreviations used in the present document are same as clause 3.3 of CCSA-TSD-LTE-36.423 [2].
4General
Same as clause 4 of CCSA-TSD-LTE-36.423 [2]
5X2AP services
Same as clause 5 of CCSA-TSD-LTE-36.423 [2]
6Services expected from signalling transport
Same as clause 6 of CCSA-TSD-LTE-36.423 [2]
7Functions of X2AP
Same as clause 7 of CCSA-TSD-LTE-36.423 [2]
8X2AP procedures
8.1Elementary procedures
Same as clause 8.1 of CCSA-TSD-LTE-36.423 [2]
8.2Basic mobility procedures
8.2.1Handover Preparation
8.2.1.1General
This procedure is used to establish necessary resources in a target node for an incoming handover.
The procedure uses UE-associated signalling.
8.2.1.2Successful Operation
Figure 8.2.1.2-1: Handover Preparation, successful operation
The source node initiates the procedure by sending the HANDOVER REQUEST message to the target node. When the source node sends the HANDOVER REQUEST message, it shall start the timer TRELOCprep.
The allocation of resources according to the values of the Allocation and Retention Priority IE shall follow the principles described for the E-RAB Setup procedure in [4].
The source node may include in the GUMMEI IE any GUMMEI corresponding to the source MME node.
If at least one of the requested non-GBR E-RABs is admitted to the cell indicated by the Target Cell ID IE, the target node shall reserve necessary resources, and send the HANDOVER REQUEST ACKNOWLEDGE message back to the source node. The target node shall include the E-RABs for which resources have been prepared at the target cell in the E-RABs Admitted List IE. The target node shall include the E-RABs that have not been admitted in the E-RABs Not Admitted List IE with an appropriate cause value.
At reception of the HANDOVER REQUEST message the target node shall:
-prepare configuration of the AS security relation between UE and target node using the information in UE Security Capabilities IE and the AS Security Information IE in the UE Context Information IE.
For each E-RAB for which the source node proposes to do forwarding of downlink data, the source node shall include the DL Forwarding IE within the E-RABs To be Setup Item IE of the HANDOVER REQUEST message. For each E-RAB that it has decided to admit, the target node may include the DL GTP Tunnel Endpoint IE within the E-RABs Admitted Item IE of the HANDOVER REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding of downlink data for this bearer. This GTP tunnel endpoint may be different from the corresponding GTP TEID IE in the E-RAB To Be Switched in Downlink List IE of the PATH SWITCH REQUEST message (see [4]) depending on implementation choice.
For each bearer in the E-RABs Admitted List IE, the target node may include the UL GTP Tunnel Endpoint IE to indicate that it requests data forwarding of uplink packets to be performed for that bearer.
Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message the source node shall stop the timer TRELOCprep, start the timer TX2RELOCoverall and terminate the Handover Preparation procedure. The source node is then defined to have a Prepared Handover for that X2 UE-associated signalling.
If the Trace Activation IE is included in the HANDOVER REQUEST message then the target node shall, if supported initiate the requested trace function as described in [6].
If the Handover Restriction List IE is
-contained in the HANDOVER REQUEST message, the target node shall store the information received in the Handover Restriction List IE in the UE context and the target node shall use this information to determine a target for the UE during subsequent mobility action for which the node provides information about the target of the mobility action towards the UE, except when one of the E-RABs has some particular ARP values [12] in which case the information shall not apply.
-not contained in the HANDOVER REQUEST message, the target node shall consider that no roaming, no area and no access restriction applies to the UE.
If the Location Reporting Information IE is included in the HANDOVER REQUEST message then the target node should initiate the requested location reporting functionality as defined in [4].
If the SRVCC Operation Possible IE is included in the HANDOVER REQUEST message, the target node shall store the received ‘SRVCC Operation Possible’ in the UE context and use it as defined in [20].
If the UE Security Capabilities IE included in the HANDOVER REQUEST message only contains the EIA0 algorithm as defined in [18] and if this EIA0 algorithm is defined in the configured list of allowed integrity protection algorithms in the node [18], the node shall take it into use and ignore the keys received in the AS Security Information IE.
The HANDOVER REQUEST message shall contain the Subscriber Profile IDfor RAT/Frequency priority IE, if available.
If the Subscriber Profile ID for RAT/Frequency priority IE is
-contained in the HANDOVER REQUEST message, the target node shall store this information and the target node should use the information as defined in [15].
Upon reception of UE History Information IE in the HANDOVER REQUEST message, the target node shall collect the information defined as mandatory in the UE History Information IE, for as long as the UE stays in one of its cells, and store the collected information to be used for future handover preparations.
If the Uplink SynchronizationIE is included in the HANDOVER REQUEST message then the target node shall, if supported consider the handover UE has obtained the uplinksynchronization in the target cell in advance.
8.2.1.3Unsuccessful Operation
Same as clause 8.2.1.3 of CCSA-TSD-LTE-36.423 [2]
8.2.1.4Abnormal Conditions
Same as clause 8.2.1.4 of CCSA-TSD-LTE-36.423 [2]
8.2.2SN Status Transfer
Same as clause 8.2.2 of CCSA-TSD-LTE-36.423 [2]
8.2.3UE Context Release
Same as clause 8.2.3 of CCSA-TSD-LTE-36.423 [2]
8.2.4Handover Cancel
Same as clause 8.2.4 of CCSA-TSD-LTE-36.423 [2]
8.3Global Procedures
Same as clause 8.3 of CCSA-TSD-LTE-36.423 [2]
9Elements for X2AP Communication
9.0General
Same as clause 9.0 of CCSA-TSD-LTE-36.423 [2]
9.1Message Functional Definition and Content
9.1.1Messages for Basic Mobility Procedures
9.1.1.1HANDOVER REQUEST
This message is sent by the source SAT-eNB to the target SAT-eNB to request the preparation of resources for a handover.
Direction: source SAT-eNB target SAT-eNB.
IE/Group Name / Presence / Range / IE type and reference / Semantics description / Criticality / Assigned CriticalityMessage Type / M / 9.2.13 / YES / reject
Old SAT-eNB UE X2AP ID / M / SAT-eNB UE X2AP ID
9.2.24 / Allocated at the source SAT-eNB / YES / reject
Cause / M / 9.2.6 / YES / ignore
Target Cell ID / M / ECGI
9.2.14 / YES / reject
GUMMEI / M / 9.2.16 / YES / reject
UE Context Information / 1 / YES / reject
> MME UE S1AP ID / M / INTEGER (0..232 -1) / MME UE S1AP ID allocated at the MME / – / –
> UE Security Capabilities / M / 9.2.29 / – / –
>AS Security Information / M / 9.2.30 / – / –
> UE Aggregate Maximum Bit Rate / M / 9.2.12 / – / –
Subscriber Profile ID for RAT/Frequency priority / O / 9.2.25 / – / –
>E-RABs To Be Setup List / 1 / – / –
>E-RABs To Be Setup Item / 1 to <maxnoof Bearers> / EACH / ignore
> E-RAB ID / M / 9.2.23 / – / –
> E-RAB Level QoS Parameters / M / 9.2.9 / Includes necessary QoS parameters / – / –
> DL Forwarding / O / 9.2.5 / – / –
> UL GTP Tunnel Endpoint / M / GTP Tunnel Endpoint 9.2.1 / SGW endpoint of the S1 transport bearer. For delivery of UL PDUs / – / –
>RRC Context / M / OCTET STRING / Includes the RRC Handover Preparation Information message as defined in subclause 10.2.2 of [9]. / – / –
>Handover Restriction List / O / 9.2.3 / – / –
>Location Reporting Information / O / 9.2.21 / Includes the necessary parameters for location reporting / – / –
UE History Information / M / 9.2.38 / Same definition as in [4]. / YES / ignore
Trace Activation / O / 9.2.2 / YES / ignore
SRVCC Operation Possible / O / 9.2.33 / YES / ignore
CSG Membership Status / O / 9.2.52 / YES / reject
Uplink Synchronization / O / 9.2.54
Range bound / Explanation
maxnoofBearers / Maximum no. of E-RABs. Value is 256
9.1.1.2HANDOVER REQUEST ACKNOWLEDGE
Same as clause 9.1.1.2 of CCSA-TSD-LTE-36.423 [2]
9.1.1.3HANDOVER PREPARATION FAILURE
Same as clause 9.1.1.3 of CCSA-TSD-LTE-36.423 [2]
9.1.1.4SN STATUS TRANSFER
Same as clause 9.1.1.4 of CCSA-TSD-LTE-36.423 [2]
9.1.1.5UE CONTEXT RELEASE
Same as clause 9.1.1.5 of CCSA-TSD-LTE-36.423 [2]
9.1.1.6HANDOVER CANCEL
Same as clause 9.1.1.6 of CCSA-TSD-LTE-36.423 [2]
9.1.2Messages for global procedures
Same as clause 9.1.2 of CCSA-TSD-LTE-36.423 [2]
9.2Information Element definitions
9.2.0General
Same as clause 9.2.0 of CCSA-TSD-LTE-36.423 [2]
9.2.1GTP Tunnel Endpoint
Same as clause 9.2.1 of CCSA-TSD-LTE-36.423 [2]
9.2.2Trace Activation
Same as clause 9.2.2 of CCSA-TSD-LTE-36.423 [2]
9.2.3Handover Restriction List
Same as clause 9.2.3 of CCSA-TSD-LTE-36.423 [2]
9.2.4PLMN Identity
Same as clause 9.2.4 of CCSA-TSD-LTE-36.423 [2]
9.2.5DL Forwarding
Same as clause 9.2.5 of CCSA-TSD-LTE-36.423 [2]
9.2.6Cause
Same as clause 9.2.6 of CCSA-TSD-LTE-36.423 [2]
9.2.7Criticality Diagnostics
Same as clause 9.2.7 of CCSA-TSD-LTE-36.423 [2]
9.2.8Served Cell Information
Same as clause 9.2.8 of CCSA-TSD-LTE-36.423 [2]
9.2.9E-RAB Level QoS Parameters
Same as clause 9.2.9 of CCSA-TSD-LTE-36.423 [2]
9.2.10GBR QoS Information
Same as clause 9.2.10 of CCSA-TSD-LTE-36.423 [2]
9.2.11Bit Rate
Same as clause 9.2.11 of CCSA-TSD-LTE-36.423 [2]
9.2.12UE Aggregate Maximum Bit Rate
Same as clause 9.2.12 of CCSA-TSD-LTE-36.423 [2]
9.2.13Message Type
Same as clause 9.2.13 of CCSA-TSD-LTE-36.423 [2]
9.2.14ECGI
Same as clause 9.2.14 of CCSA-TSD-LTE-36.423 [2]
9.2.15COUNT Value
Same as clause 9.2.15 of CCSA-TSD-LTE-36.423 [2]
9.2.16GUMMEI
Same as clause 9.2.16 of CCSA-TSD-LTE-36.423 [2]
9.2.17UL Interference Overload Indication
Same as clause 9.2.17 of CCSA-TSD-LTE-36.423 [2]
9.2.18UL High Interference Indication
Same as clause 9.2.18 of CCSA-TSD-LTE-36.423 [2]
9.2.19Relative Narrowband Tx Power (RNTP)
Same as clause 9.2.19 of CCSA-TSD-LTE-36.423 [2]
9.2.20GU Group Id
Same as clause 9.2.20 of CCSA-TSD-LTE-36.423 [2]
9.2.21Location Reporting Information
Same as clause 9.2.21 of CCSA-TSD-LTE-36.423 [2]
9.2.22Global SAT-eNB ID
Same as clause 9.2.22 of CCSA-TSD-LTE-36.423 [2]
9.2.23E-RAB ID
Same as clause 9.2.23 of CCSA-TSD-LTE-36.423 [2]
9.2.24SAT-eNB UE X2AP ID
Same as clause 9.2.24 of CCSA-TSD-LTE-36.423 [2]
9.2.25Subscriber Profile ID for RAT/Frequency priority
Same as clause 9.2.25 of CCSA-TSD-LTE-36.423 [2]
9.2.26EARFCN
Same as clause 9.2.26 of CCSA-TSD-LTE-36.423 [2]
9.2.27Transmission Bandwidth
Same as clause 9.2.27 of CCSA-TSD-LTE-36.423 [2]
9.2.28E-RAB List
Same as clause 9.2.28 of CCSA-TSD-LTE-36.423 [2]
9.2.29UE Security Capabilities
Same as clause 9.2.29 of CCSA-TSD-LTE-36.423 [2]
9.2.30AS Security Information
Same as clause 9.2.30 of CCSA-TSD-LTE-36.423 [2]
9.2.31Allocation and Retention Priority
Same as clause 9.2.31 of CCSA-TSD-LTE-36.423 [2]
9.2.32Time to Wait
Same as clause 9.2.32 of CCSA-TSD-LTE-36.423 [2]
9.2.33SRVCC Operation Possible
Same as clause 9.2.33 of CCSA-TSD-LTE-36.423 [2]
9.2.34Hardware Load Indicator
Same as clause 9.2.34 of CCSA-TSD-LTE-36.423 [2]
9.2.35S1 TNL Load Indicator
Same as clause 9.2.35 of CCSA-TSD-LTE-36.423 [2]
9.2.36Load Indicator
Same as clause 9.2.36 of CCSA-TSD-LTE-36.423 [2]
9.2.37Radio Resource Status
Same as clause 9.2.37 of CCSA-TSD-LTE-36.423 [2]
9.2.38UE History Information
Same as clause 9.2.38 of CCSA-TSD-LTE-36.423 [2]
9.2.39Last Visited Cell Information
Same as clause 9.2.39 of CCSA-TSD-LTE-36.423 [2]
9.2.40Last Visited E-UTRAN Cell Information
Same as clause 9.2.40 of CCSA-TSD-LTE-36.423 [2]
9.2.41Last Visited GERAN Cell Information
Same as clause 9.2.41 of CCSA-TSD-LTE-36.423 [2]
9.2.42Cell Type
Same as clause 9.2.42 of CCSA-TSD-LTE-36.423 [2]
9.2.43Number of Antenna Ports
Same as clause 9.2.43 of CCSA-TSD-LTE-36.423 [2]
9.2.44Composite Available Capacity Group
Same as clause 9.2.44 of CCSA-TSD-LTE-36.423 [2]
9.2.45Composite Available Capacity
Same as clause 9.2.45 of CCSA-TSD-LTE-36.423 [2]
9.2.46Cell Capacity Class Value
Same as clause 9.2.46 of CCSA-TSD-LTE-36.423 [2]
9.2.47Capacity Value
Same as clause 9.2.47 of CCSA-TSD-LTE-36.423 [2]
9.2.48Mobility Parameters Information
Same as clause 9.2.48 of CCSA-TSD-LTE-36.423 [2]
9.2.49Mobility Parameters Modification Range
Same as clause 9.2.49 of CCSA-TSD-LTE-36.423 [2]
9.2.50PRACH Configuration
Same as clause 9.2.50 of CCSA-TSD-LTE-36.423 [2]
9.2.51SubframeAllocation
Same as clause 9.2.51 of CCSA-TSD-LTE-36.423 [2]
9.2.52CSG Membership Status
Same as clause 9.2.52 of CCSA-TSD-LTE-36.423 [2]
9.2.53CSG ID
Same as clause 9.2.53 of CCSA-TSD-LTE-36.423 [2]
9.2.54Uplink Synchronization
The IE indicates that the handover UE has obtained the uplink synchronization with the target satellite cell.
IE/Group Name / Presence / Range / IE type and reference / Semantics descriptionUplink Synchronization / M / ENUMERATED(Synchronization, …)
9.3Message and Information Element Abstract Syntax (with ASN.1)
Same as clause 9.3 of CCSA-TSD-LTE-36.423 [2].
9.4Message transfer syntax
Same as clause 9.4 of CCSA-TSD-LTE-36.423 [2].
9.5Timers
Same as clause 9.5 of CCSA-TSD-LTE-36.423 [2].
10Handling of unknown, unforeseen and erroneous protocol data
Same as clause 10 of CCSA-TSD-LTE-36.423 [2].
Annex A (informative):
Change History
Version 1.0.0 / August 2013
CCSA