BMSat-36.0216V1.0.0(2013-08)

Technical Specification

China Communication Standards Association (CCSA);

BMSat Radio Interface Specifications;

Evolved Universal Satellite Radio Access (E-USRA);

Physical layer for CGC operation

(Release 1)

The present document has been developed within China Communication Standards Association(CCSA) and may be further elaborated for the purposes of CCSA.

BMSat-36.0216 V1.0.0(2013-08)

1

Release 1

Keywords

BMSat, CGC, layer1

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 Communication Standards Association

All rights reserved.

Contents

Foreword

Introduction

1Scope

2References

3Definitions, symbols and abbreviations

3.1Definitions

3.2Symbols

3.3Abbreviations

4General

5Physical Channels and Modulation

6Multiplexing and channel coding

7CGC Node procedures

7.1General

7.2CGC node procedures for receiving the physical downlink shared channel

7.3CGC node procedures for transmitting the physical uplink shared channel

7.4CGC node procedure for receiving the CGC physical downlink control channel

7.5CGC node procedures for transmitting the physical uplink control channel

7.5.1CGC node procedure for determining physical uplink control channel assignment

Foreword

This Technical Specification has been produced by the China Communication Standards Association (CCSA).

The contents of the present document are subject to continuing work within the 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). 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 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 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, 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. The applicability of the LTE-Advanced specifications is defined inBMSat-36.001.2 [1].

1Scope

The present document describes the characteristics of SAT-eNB-CGC node transmissions.

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.216: “Evolved Universal Terrestrial Radio Access (E-UTRA)”

[3] BMSat-36.212: "Evolved Universal Satellite Radio Access (E-USRA); Multiplexing and channel coding".

[4] BMSat-36.213: "Evolved Universal Satellite Radio Access (E-USRA); Physical layer procedures".

3Definitions, symbols and abbreviations

3.1Definitions

Same as clause 3.1 of CCSA-TSD-LTE-36.216[2].

3.2Symbols

Same as clause 3.2 of CCSA-TSD-LTE-36.216[2].

3.3Abbreviations

For the purposes of the present document, the following abbreviations apply：

CGC Complementary ground component

C-PDCCH CGC Physical Downlink Control Channel

C-PUCCH CGC Physical Uplink Control Channel

V-HARQ Virtual HARQ

Other abbreviations used in the present document are same as clause3.3 of CCSA-TSD-LTE-36.216 [2].

4General

Same as clause 4 in CCSA-TSD-LTE-36.216[2].

5Physical Channels and Modulation

Same as clause 5 in CCSA-TSD-LTE-36.216[2].

6Multiplexing and channel coding

Multiplexing and channel coding is done according to [3] with the addition that DCI shall be mapped to the C-PDCCH. The provisions in [3] for the PDCCH apply to the C-PDCCH.

7CGC Node procedures

7.1General

The CGC node acts according to the UE procedures as described in [4] with the exceptions defined in Section 7, where DCI shallbe transmitted by means of C-PDCCH. The CGC nodeshall not expect DCI format 3/3A.

7.2CGC node procedures for receiving the physical downlink shared channel

A CGC shall upon detection of aC-PDCCH intended for the CGC node in a subframe, decode the corresponding PDSCH in the same subframe with the following assumptions.

-If the CGC node receives a resource allocation which overlaps a PRB pair in which a downlink assignment is detected in the first slot, the CGC nodeshall assume that there is PDSCH transmission for it in the second slot of that PRB pair.

-For a PRB pair where the CGC node detects at least part of a downlink assignment in the first slot, the CGC node shall assume that the first slot of the PRB pair is not used for PDSCH transmission.

7.3CGC node procedures for transmitting the physical uplink shared channel

The physical uplink shared channel shall be processed as described in Section8 of [4] with the following exceptions.

Only V-HARQ shall be used for transmitting the physical uplink shared channel.

7.4CGC node procedure for receiving the CGC physical downlink control channel

Same as clause 7 of CCSA-TSD-LTE-36.216[2].

7.5CGC node procedures for transmitting the physical uplink control channel

7.5.1CGC node procedure for determining physical uplink control channel assignment

The physical uplink control channel shall be processed as described in Section 10 of [4] with the following exceptions.

There is no HARQ-ACK transmitted on PUCCH.

Annex (informative):
history

Document history
Version 1.0.0 / August 2013

CCSA