Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download 3GPP TS 36.300
Transcript
BMSat-36.300 V1.0.0 (2013-08) Technical Specification China Communications Standards Association (CCSA); BMSat Radio Interface Specifications; Evolved Universal Satellite Radio Access (E-USRA) and Evolved Universal Satellite Radio Access Network (E-USRAN); Overall description; (Release 1) The present document has been developed within China Communications Standards Association (CCSA) and may be further elaborated for the purposes of CCSA. Release 1 2 BMSat-36.300 V1.0.0 (2013-08) Keywords BMSat, radio, architecture 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: [email protected] 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. CCSA Release 1 3 BMSat-36.300 V1.0.0 (2013-08) Contents Foreword............................................................................................................................................................. 5 Introduction ........................................................................................................................................................ 5 1 Scope ........................................................................................................................................................ 7 2 References ................................................................................................................................................ 7 3 Definitions, symbols and abbreviations ................................................................................................... 7 3.1 3.2 4 Definitions ......................................................................................................................................................... 7 Abbreviations ..................................................................................................................................................... 7 Overall architecture .................................................................................................................................. 7 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5 4.7.6 4.7.7 5 Functional Split .................................................................................................................................................. 7 Void .................................................................................................................................................................... 7 Radio Protocol architecture ............................................................................................................................... 8 Synchronization ................................................................................................................................................. 8 IP fragmentation................................................................................................................................................. 8 Support of HeNBs.............................................................................................................................................. 8 Support for relaying ........................................................................................................................................... 8 General ......................................................................................................................................................... 8 Architecture .................................................................................................................................................. 8 S1 and X2 user plane aspects ....................................................................................................................... 9 S1 and X2 control plane aspects................................................................................................................... 9 Radio protocol aspects ................................................................................................................................. 9 Signalling procedures ................................................................................................................................... 9 Relay Node OAM Aspects ........................................................................................................................... 9 Physical Layer for E-USRA ..................................................................................................................... 9 5.1 5.2 5.3 5.3.1 5.4 5.5 Downlink Transmission Scheme...................................................................................................................... 10 Uplink Transmission Scheme .......................................................................................................................... 10 Transport Channels .......................................................................................................................................... 10 Mapping between transport channels and physical channels ..................................................................... 10 E-USRA physical layer model ......................................................................................................................... 11 Carrier Aggregation ......................................................................................................................................... 11 6 Layer 2 ................................................................................................................................................... 11 7 RRC ........................................................................................................................................................ 11 8 E-UTRAN identities............................................................................................................................... 11 9 ARQ and HARQ .................................................................................................................................... 11 10 Mobility .................................................................................................................................................. 12 10.1 10.1.1 10.1.2 10.1.3 10.1.4 10.1.5 10.1.5.1 10.1.5.2 10.1.5.3 10.1.6 10.1.7 10.1.8 10.2 10.3 10.4 10.5 Intra E-UTRAN ............................................................................................................................................... 12 Mobility Management in ECM-IDLE ........................................................................................................ 12 Mobility Management in ECM-CONNECTED ......................................................................................... 12 Measurements ............................................................................................................................................ 12 Paging and C-plane establishment ............................................................................................................. 12 Random Access Procedure ......................................................................................................................... 12 Contention based random access procedure ......................................................................................... 12 Non-contention based random access procedure .................................................................................. 14 Interaction model between L1 and L2/3 for Random Access Procedure .............................................. 14 Radio Link Failure ..................................................................................................................................... 14 Radio Access Network Sharing .................................................................................................................. 14 Handling of Roaming and Area Restrictions for UEs in ECM-CONNECTED ......................................... 14 Inter RAT ......................................................................................................................................................... 14 Mobility between E-UTRAN and Non-3GPP radio technologies ................................................................... 14 Area Restrictions ............................................................................................................................................. 14 Mobility to and from CSG and Hybrid cells .................................................................................................... 14 CCSA Release 1 10.6 10.7 11 11.1 11.2 11.3 11.4 11.5 11.6 11.7 4 BMSat-36.300 V1.0.0 (2013-08) Measurement Model ........................................................................................................................................ 14 Hybrid Cells ..................................................................................................................................................... 14 Scheduling and Rate Control.................................................................................................................. 15 Basic Scheduler Operation............................................................................................................................... 15 Activation/Deactivation Mechanism................................................................................................................ 15 Measurements to Support Scheduler Operation ............................................................................................... 15 Rate Control of GBR, MBR and UE-AMBR................................................................................................... 15 CQI reporting for Scheduling .......................................................................................................................... 15 Explicit Congestion Notification ..................................................................................................................... 15 Contention base uplink date transmission ........................................................................................................ 15 12 DRX in RRC_CONNECTED ................................................................................................................ 16 13 QoS ......................................................................................................................................................... 16 14 Security .................................................................................................................................................. 16 15 MBMS .................................................................................................................................................... 16 16 Radio Resource Management aspects .................................................................................................... 16 17 Void ........................................................................................................................................................ 16 18 UE capabilities ....................................................................................................................................... 17 19 S1 Interface ............................................................................................................................................ 17 20 X2 Interface ............................................................................................................................................ 17 21 Void ........................................................................................................................................................ 17 22 Support for self-configuration and self-optimisation ............................................................................. 17 23 Others ..................................................................................................................................................... 17 CCSA Release 1 5 BMSat-36.300 V1.0.0 (2013-08) Foreword This Technical Specification has been produced by China 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: x the first digit: 1 or greater indicates CCSA 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. Introduction Broadband Mobile Satellite (BMSat) radio interface is mainly used for mobile satellite services (MSS) utilizing geostationary satellite(s). BMSat is derived from the terrestrial LTE-Advanced specifications (also known as LTE Release 10 and beyond developed by 3GPP) and supports access to LTE-Advanced core networks. Currently, BMSat supports only FDD mode, and the descriptions of TDD mode in the terrestrial LTE-Advanced specifications are not applied to BMSat. 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, some LTE-Advanced specifications do not apply, while some BMSat specifications have no corresponding LTEAdvanced specification. Since BMSat is derived from LTE-Advanced, the organization of the BMSat specifications closely follows that of LTEAdvanced. The BMSat numbers have been designed to correspond to the LTE-Advanced numbering system. All BMSat specifications are allocated a unique 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, the numbers 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). This precedence rule applies to any references in the corresponding LTE-Advanced specifications. CCSA Release 1 6 BMSat-36.300 V1.0.0 (2013-08) NOTE: Any references to LTE-Advanced specifications within the BMSat specifications are not subject to this precedence rule. For example, a BMSat specification may contain specific references to the corresponding LTEAdvanced specification. - If a BMSat specification does not exist, the corresponding LTE-Advanced specification may or may not apply. The applicability of the LTE-Advanced specifications is defined in BMSat-36.001.2 [1]. CCSA Release 1 1 7 BMSat-36.300 V1.0.0 (2013-08) Scope The present document provides an overview and overall description of the E-USRAN radio interface protocol architecture. Details of the radio interface protocols are specified in companion specifications of the 36 series. 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] BMSat-36.001.2: “Introduction to the BMSat family” [2] CCSA-TSD-LTE-36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN);Overall description;” 3 Definitions, symbols and abbreviations 3.1 Definitions Same as clause 3.1 of CCSA-TSD-LTE-36.300 [2] 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply： E-PPCH Enhanced Physical Paging Channel Other abbreviations used in the present document are same as clause 3.2 of CCSA-TSD-LTE-36.300 [2]. 4 Overall architecture Same as clause 4 of CCSA-TSD-LTE-36.300 [2]. 4.1 Functional Split Same as clause 4.1 of CCSA-TSD-LTE-36.300 [2]. 4.2 Void Same as clause 4.2 of CCSA-TSD-LTE-36.300 [2]. CCSA Release 1 4.3 8 BMSat-36.300 V1.0.0 (2013-08) Radio Protocol architecture Same as clause 4.3 of CCSA-TSD-LTE-36.300 [2]. 4.4 Synchronization Same as clause 4.4 of CCSA-TSD-LTE-36.300 [2]. 4.5 IP fragmentation Same as clause 4.5 of CCSA-TSD-LTE-36.300 [2]. 4.6 Support of HeNBs Same as clause 4.6 of CCSA-TSD-LTE-36.300 [2]. 4.7 Support for relaying Same as clause 4.7 of CCSA-TSD-LTE-36.300 [2]. 4.7.1 General Same as clause 4.7.1 of CCSA-TSD-LTE-36.300 [2]. 4.7.2 Architecture The radio-access network interfaces for BMSat supporting CGCs are shown in Fig.4.7.2-1. The CGC terminates the S1, X2 and Un interfaces. The Donor SAT-GW(DSAT-GW) provides S1 and X2 proxy functionality between the CGC and other network nodes (other SAT-GWs, MMEs and S-GWs). The S1 and X2 proxy functionality includes passing UEdedicated S1 and X2 signalling messages as well as GTP data packets between the S1 and X2 interfaces associated with the CGC and the S1 and X2 interfaces associated with other network nodes. Due to the proxy functionality, the DSATGW appears as an MME (for S1-c), an SAT-GW (for X2) and an S-GW (for S1-u) to the CGC. Core Network MME MME S-GW S1 -u S1 S 1- 1-u u c S11S1-c S1 - c S-GW X2 Donor Satellite Gateway Satellite Gateway X2S1-c u S1- Un CGC Figure 4.7.2-1: Radio-access network interfaces of BMSat supporting CGC CCSA Release 1 4.7.3 9 BMSat-36.300 V1.0.0 (2013-08) S1 and X2 user plane aspects Same as clause 4.7.3 of CCSA-TSD-LTE-36.300 [2]. 4.7.4 S1 and X2 control plane aspects Same as clause 4.7.4 of CCSA-TSD-LTE-36.300 [2]. 4.7.5 Radio protocol aspects Same as clause 4.7.5 of CCSA-TSD-LTE-36.300 [2]. 4.7.6 Signalling procedures Same as clause 4.7.6 of CCSA-TSD-LTE-36.300 [2]. 4.7.7 Relay Node OAM Aspects Same as clause 4.7.7 of CCSA-TSD-LTE-36.300 [2]. 5 Physical Layer for E-USRA Downlink and uplink transmissions are organized into radio frames with 10 ms duration. Frame structure is illustrated in Figure 5.1-1. Each 10 ms radio frame is divided into ten equally sized sub-frames. Each sub-frame consists of two equally sized slots. For FDD, 10 subframes are available for downlink transmission and 10 subframes are available for uplink transmissions in each 10 ms interval. Uplink and downlink transmissions are separated in the frequency domain. #0 #1 #2 #18 #19 slot Sub-frame One radio frame = 10ms Figure 5.1-1: Frame structure Table 5.1-1: Uplink-downlink allocations. Configuration Switch-point periodicity 0 1 2 3 4 5 6 5 ms 5 ms 5 ms 10 ms 10 ms 10 ms 5 ms 0 D D D D D D D 1 S S S S S S S 2 U U U U U U U Subframe number 3 4 5 6 7 U U D S U U D D S U D D D S U U U D D D U D D D D D D D D D U U D S U 8 U U D D D D U 9 U D D D D D D The physical channels of E-USRA are: Physical broadcast channel (PBCH) - The coded BCH transport block is mapped to four subframes within a 40 ms interval; - 40 ms timing is blindly detected, i.e. there is no explicit signalling indicating 40 ms timing; - Each subframe is assumed to be self-decodable, i.e. the BCH can be decoded from a single reception, assuming sufficiently good channel conditions. CCSA Release 1 10 BMSat-36.300 V1.0.0 (2013-08) Physical control format indicator channel (PCFICH) - Informs the UE about the number of OFDM symbols used for the PDCCHs; - Transmitted in every downlink or special subframe. Physical downlink control channel (PDCCH) - Informs the UE about the resource allocation of PCH and DL-SCH, and Hybrid ARQ information related to DL-SCH; - Carries the uplink scheduling grant. Physical Hybrid ARQ Indicator Channel (PHICH) - Carries Hybrid ARQ ACK/NAKs in response to uplink transmissions. Physical downlink shared channel (PDSCH) - Carries the DL-SCH and PCH. Physical multicast channel (PMCH) - Carries the MCH. Physical uplink control channel (PUCCH) - Carries Hybrid ARQ ACK/NAKs in response to downlink transmission; - Carries Scheduling Request (SR); - Carries CQI reports. Physical uplink shared channel (PUSCH) - Carries the UL-SCH. Physical random access channel (PRACH) - Carries the random access preamble. Enhanced Physical Paging Channel (E-PPCH) - 5.1 Carries enhanced paging information Downlink Transmission Scheme Same as clause 5.1 of CCSA-TSD-LTE-36.300 [2]. 5.2 Uplink Transmission Scheme Same as clause 5.2 of CCSA-TSD-LTE-36.300 [2]. 5.3 Transport Channels Same as clause 5.3 of CCSA-TSD-LTE-36.300 [2]. 5.3.1 Mapping between transport channels and physical channels The figures below depict the mapping between transport and physical channels: CCSA Release 1 11 BCH PBCH MCH PMCH PCH E-PPCH BMSat-36.300 V1.0.0 (2013-08) DL-SCH Downlink Transport channels PDSCH PDCCH Downlink Physical channels Figure 5.3.1-1: Mapping between downlink transport channels and downlink physical channels UL-SCH PUSCH RACH PRACH Uplink Transport channels PUCCH Uplink Physical channels Figure 5.3.1-2: Mapping between uplink transport channels and uplink physical channels 5.4 E-USRA physical layer model Same as clause 5.4 of CCSA-TSD-LTE-36.300 [2] 5.5 Carrier Aggregation Same as clause 5.5 of CCSA-TSD-LTE-36.300 [2] 6 Layer 2 Same as clause 6 of CCSA-TSD-LTE-36.300 [2] 7 RRC Same as clause 7 of CCSA-TSD-LTE-36.300 [2] 8 E-UTRAN identities Same as clause 8 of CCSA-TSD-LTE-36.300 [2] 9 ARQ and HARQ Same as clause 9 of CCSA-TSD-LTE-36.300 [2] CCSA Release 1 10 12 BMSat-36.300 V1.0.0 (2013-08) Mobility Same as clause 10 of CCSA-TSD-LTE-36.300 [2] 10.1 Intra E-UTRAN Same as clause 10.1 of CCSA-TSD-LTE-36.300 [2] 10.1.1 Mobility Management in ECM-IDLE Same as clause 10.1 of CCSA-TSD-LTE-36.300 [2] 10.1.2 Mobility Management in ECM-CONNECTED Same as clause 10.1.2 of CCSA-TSD-LTE-36.300 [2] 10.1.3 Measurements Same as clause 10.1.3 of CCSA-TSD-LTE-36.300 [2] 10.1.4 Paging and C-plane establishment Same as clause 10.1.4 of CCSA-TSD-LTE-36.300 [2] 10.1.5 Random Access Procedure Same as clause 10.1.5 of CCSA-TSD-LTE-36.300 [2] 10.1.5.1 Contention based random access procedure The contention based random access procedure is outlined on Figure 10.1.5.1-1 below: satellite gateway UE 1 Random Access Preamble Random Access Response 3 2 Scheduled Transmission Contention Resolution 4 Figure 10.1.5.1-1: Contention based Random Access Procedure The four steps of the contention based random access procedures are: 1) Random Access Preamble on RACH in uplink: CCSA Release 1 - 13 BMSat-36.300 V1.0.0 (2013-08) There are two possible groups defined and one is optional. If both groups are configured the size of message 3 is used to determine which group a preamble is selected from. The group to which a preamble belongs provides an indication of the size of the message 3 and the radio conditions at the UE. The preamble group information along with the necessary thresholds are broadcast on system information. 2) Random Access Response generated by MAC on DL-SCH: - Semi-synchronous (within a flexible window of which the size is one or more TTI) with message 1; - No HARQ; - Addressed to RA-RNTI on PDCCH; - Conveys at least RA-preamble identifier, Timing Alignment information, initial UL grant and assignment of Temporary C-RNTI (which may or may not be made permanent upon Contention Resolution); - Intended for a variable number of UEs in one DL-SCH message. 3) First scheduled UL transmission on UL-SCH: - Size of the transport blocks depends on the UL grant conveyed in step 2 and is at least 80 bits. - For initial access: - - - - Conveys the RRC Connection Request generated by the RRC layer and transmitted via CCCH; - Conveys at least NAS UE identifier but no NAS message; - RLC TM: no segmentation; For RRC Connection Re-establishment procedure: - Conveys the RRC Connection Re-establishment Request generated by the RRC layer and transmitted via CCCH; - RLC TM: no segmentation; - Does not contain any NAS message. After handover, in the target cell: - Conveys the ciphered and integrity protected RRC Handover Confirm generated by the RRC layer and transmitted via DCCH; - Conveys the C-RNTI of the UE (which was allocated via the Handover Command); - Includes an uplink Buffer Status Report when possible. For other events: - Conveys at least the C-RNTI of the UE. 4) Contention Resolution on DL: - Early contention resolution shall be used i.e. satellite gateway does not wait for NAS reply before resolving contention - Not synchronised with message 3; - Addressed to: - - The Temporary C-RNTI on PDCCH for initial access and after radio link failure; - The C-RNTI on PDCCH for UE in RRC_CONNECTED; For initial access and RRC Connection Re-establishment procedure, no segmentation is used (RLC-TM). CCSA Release 1 14 BMSat-36.300 V1.0.0 (2013-08) The Temporary C-RNTI is promoted to C-RNTI for a UE which detects RA success and does not already have a CRNTI; it is dropped by others. A UE which detects RA success and already has a C-RNTI, resumes using its C-RNTI. When CA is configured, the first three steps of the contention based random access procedures occur on the PCell while contention resolution (step 4) can be cross-scheduled by the PCell. 10.1.5.2 Non-contention based random access procedure Same as clause 10.1.5 of CCSA-TSD-LTE-36.300 [2] 10.1.5.3 Interaction model between L1 and L2/3 for Random Access Procedure Same as clause 10.1.5.3 of CCSA-TSD-LTE-36.300 [2] 10.1.6 Radio Link Failure Same as clause 10.1.6 of CCSA-TSD-LTE-36.300 [2] 10.1.7 Radio Access Network Sharing Same as clause 10.1.7 of CCSA-TSD-LTE-36.300 [2] 10.1.8 Handling of Roaming and Area Restrictions for UEs in ECMCONNECTED Same as clause 10.1.8 of CCSA-TSD-LTE-36.300 [2] 10.2 Inter RAT Same as clause 10.2 of CCSA-TSD-LTE-36.300 [2] 10.3 Mobility between E-UTRAN and Non-3GPP radio technologies Same as clause 10.3 of CCSA-TSD-LTE-36.300 [2] 10.4 Area Restrictions Same as clause 10.4 of CCSA-TSD-LTE-36.300 [2] 10.5 Mobility to and from CSG and Hybrid cells Same as clause 10.5 of CCSA-TSD-LTE-36.300 [2] 10.6 Measurement Model Same as clause 10.6 of CCSA-TSD-LTE-36.300 [2] 10.7 Hybrid Cells Same as clause 10.7 of CCSA-TSD-LTE-36.300 [2] CCSA Release 1 11 15 BMSat-36.300 V1.0.0 (2013-08) Scheduling and Rate Control Same as clause 11 of CCSA-TSD-LTE-36.300 [2] 11.1 Basic Scheduler Operation Same as clause 11.1 of CCSA-TSD-LTE-36.300 [2] 11.2 Activation/Deactivation Mechanism Same as clause 11.2 of CCSA-TSD-LTE-36.300 [2] 11.3 Measurements to Support Scheduler Operation Same as clause 11.3 of CCSA-TSD-LTE-36.300 [2] 11.4 Rate Control of GBR, MBR and UE-AMBR Same as clause 11.4 of CCSA-TSD-LTE-36.300 [2] 11.5 CQI reporting for Scheduling Same as clause 11.5 of CCSA-TSD-LTE-36.300 [2] 11.6 Explicit Congestion Notification Same as clause 11.5 of CCSA-TSD-LTE-36.300 [2] 11.7 Contention base uplink date transmission For UE has established the uplink synchronization in advance, contention uplink resource can be used if no dedicated resource is assigned. The method UE establishes the uplink synchronization is left to UE implementation, three example cases are followings: 1) The UE has accessed the satellite and obtained the TA value before. And the TA value stored by UE in still valid for the time span between the last access and current access is short. 2) The UE deduces the TA value between itself and the satellite through implementation method, e.g. the UE can obtain the propagation time between itself and the satellite using the global navigation satellite system (GNSS). 3) A satellite broadcast a reference time in UTC, a UE equipped with GNSS can deduce the TA value according to the time difference between the time it receives the broadcast message and the reference time value from the satellite. In contention base uplink date transmission procedure, the satellite gateway broadcasts a set of contention-based PRBs, the access UE chooses one contention-based PRB to send data with its identifier. If the data transmission is successful, the satellite gateway should send UE a response. Otherwise, an access collision may occur, UE may retry the access procedure after a random back-off time. CCSA Release 1 16 UE BMSat-36.300 V1.0.0 (2013-08) Satellite GW 1. Obtain TA 2. broadcast contention-based resource 3.data transmission on contention-based resource 4.ACK for data transmission Figure 11.7-1: Contention base uplink date transmission 12 DRX in RRC_CONNECTED Same as clause 12 of CCSA-TSD-LTE-36.300 [2] 13 QoS Same as clause 13 of CCSA-TSD-LTE-36.300 [2] 14 Security Same as clause 14 of CCSA-TSD-LTE-36.300 [2] 15 MBMS Same as clause 15 of CCSA-TSD-LTE-36.300 [2] 16 Radio Resource Management aspects Same as clause 16 of CCSA-TSD-LTE-36.300 [2] 17 Void Same as clause 17 of CCSA-TSD-LTE-36.300 [2] CCSA Release 1 18 17 BMSat-36.300 V1.0.0 (2013-08) UE capabilities Same as clause 18 of CCSA-TSD-LTE-36.300 [2] 19 S1 Interface Same as clause 19 of CCSA-TSD-LTE-36.300 [2] 20 X2 Interface Same as clause 20 of CCSA-TSD-LTE-36.300 [2] 21 Void Same as clause 21 of CCSA-TSD-LTE-36.300 [2] 22 Support for self-configuration and self-optimisation Same as clause 22 of CCSA-TSD-LTE-36.300 [2] 23 Others Same as clause 23 of CCSA-TSD-LTE-36.300 [2] Annex A (informative): NAS Overview Same as Annex A of CCSA-TSD-LTE-36.300 [2]. Annex B (informative): MAC and RRC Control Same as Annex B of CCSA-TSD-LTE-36.300 [2]. Annex C (informative): Void Same as Annex C of CCSA-TSD-LTE-36.300 [2]. CCSA Release 1 18 BMSat-36.300 V1.0.0 (2013-08) Annex D (informative): Void Same as Annex D of CCSA-TSD-LTE-36.300 [2]. Annex E (informative): Void Same as Annex E of CCSA-TSD-LTE-36.300 [2]. Annex F (informative): Void Same as Annex F of CCSA-TSD-LTE-36.300 [2] Annex G (informative): Guideline for E-USRAN UE capabilities Same as Annex G of CCSA-TSD-LTE-36.300 [2] Annex H (informative): Void Same as Annex H of CCSA-TSD-LTE-36.300 [2] Annex I (informative): SPID ranges ad mapping of SPID values to cell reselection and inter-RAT/inter frequency handover priorities Same as Annex I of CCSA-TSD-LTE-36.300 [2] Annex J (informative): Carrier Aggregation Same as Annex J of CCSA-TSD-LTE-36.300 [2] Annex K (informative): Time domain ICIC Same as Annex K of CCSA-TSD-LTE-36.300 [2] CCSA Release 1 19 Annex J (informative): Carrier Aggregation Same as Annex J of CCSA-TSD-LTE-36.300 [2] Annex K (informative): Time domain ICIC Same as Annex K of CCSA-TSD-LTE-36.300 [2] Annex L (informative): Relaying Same as Annex L of CCSA-TSD-LTE-36.300 [2] Annex M (informative): history Document history Version 1.0.0 August 2013 CCSA BMSat-36.300 V1.0.0 (2013-08)
