ETSI TS 102 744-3-4 V1.1.1 (2015-10)
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 4: Bearer Connection Layer Operation
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 4: Bearer Connection Layer Operation
DTS/SES-00299-3-4
General Information
Standards Content (Sample)
TECHNICAL SPECIFICATION
Satellite Earth Stations and Systems (SES);
Family SL Satellite Radio Interface (Release 1);
Part 3: Control Plane and User Plane Specifications;
Sub-part 4: Bearer Connection Layer Operation
2 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
Reference
DTS/SES-00299-3-4
Keywords
3GPP, GPRS, GSM, GSO, interface, MSS, radio,
satellite, TDM, TDMA, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Symbols and abbreviations . 7
3.1 Symbols . 7
3.2 Abbreviations . 7
4 General Architecture . 7
4.0 Overview . 7
4.1 Bearer Connection Layer Entities . 8
4.1.0 General . 8
4.1.1 Bearer Connection Manager (BCnM) . 9
4.1.2 Acknowledged Mode Data Handler (AM_DH) . 10
4.1.3 Transparent Mode Data Handler (TM_DH) . 10
4.1.4 Numbered Frame Data Handler (NUM_DH) . 10
4.1.5 Common Signalling Data Handler (COM_DH) . 10
4.2 Interfaces to Upper Layers . 10
4.2.1 User Plane Interfaces . 10
4.2.1.0 General . 10
4.2.1.1 Acknowledged Mode (AM)-SAP Primitives and Parameters . 11
4.2.1.2 Transparent Mode (TM) SAP Primitives and Parameters . 11
4.2.1.3 Unacknowledged Mode (UM) SAP Primitives and Parameters. 12
4.2.2 Control Plane Interfaces . 12
4.2.2.0 General . 12
4.2.2.1 CBCn-SAP Primitives and Parameters . 12
4.2.2.2 COM-SAP Primitives and Parameters . 15
4.3 Interfaces to the Lower Layer . 15
5 Bearer Connection Operations . 16
5.0 General . 16
5.1 Bearer Connection Manager . 16
5.2 Quality of Service (QoS) Control Function . 16
5.3 Acknowledged Mode Operation . 17
5.3.0 General . 17
5.3.1 AM_DH Architecture . 17
5.3.1.0 Overview . 17
5.3.1.1 Transmit Path Processing . 18
5.3.1.2 Receive Path Processing . 19
5.3.1.3 AM_DH Control Unit . 19
5.3.1.4 Transmit Path Processing in the Suspended State (UESS AM_DH only) . 20
5.3.2 The ARQ Mechanism . 20
5.3.3 Data Packet Structures . 21
5.3.3.0 General . 21
5.3.3.1 Definition of the I-Frame . 21
5.3.3.2 Definition of the RR-Frame . 21
5.3.3.3 Definition of the SREJ-Frame . 22
5.3.3.4 Definition of the Sub-Segment Frame. 22
5.3.4 Sending I-Frames . 22
5.3.5 Receiving I-Frames . 23
5.3.6 Polling Mechanism . 23
5.3.6.0 General . 23
ETSI
4 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
5.3.6.1 ARQ Timer . 24
5.3.6.2 Sending a Poll . 24
5.3.6.3 Response to a Poll . 25
5.3.6.4 Response to a Poll Response . 25
5.3.7 Transmit Behaviour . 26
5.3.7.0 General . 26
5.3.7.1 Support for final-seg-retx-allowed (fsr) Mode . 29
5.3.8 Receive Behaviour . 29
5.3.8.0 General . 29
5.3.8.1 RNC Support for final-seg-retx-allowed ("fsr") Mode . 30
5.3.9 Tx and Rx Window Size Control . 32
5.3.10 Acknowledged Mode Timers . 33
5.3.11 Example Retransmission Sequence . 34
5.4 Transparent Mode Operations . 36
5.4.0 General . 36
5.4.1 Transparent Mode Timers . 37
5.5 Un-Acknowledged Mode Operations . 38
5.5.0 General . 38
5.5.1 Un-Acknowledged Mode Timers . 39
5.6 Common Signalling Data Handler Operation . 39
5.7 Ciphering Operation . 39
5.7.0 General . 39
5.7.1 Input Parameters to the Ciphering Algorithm . 40
5.7.1.0 General . 40
5.7.1.1 CK . 40
5.7.1.2 COUNT-C . 40
5.7.1.3 TBCNID and BCNID . 41
5.7.1.4 DIRECTION . 41
5.7.1.5 LENGTH . 41
5.7.2 Initialization of Keystream Generator. 41
5.7.3 Maintenance of COUNT-C . 41
5.7.4 MBMS Connections . 42
5.8 Handover Operations . 42
History . 43
ETSI
5 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and
Systems (SES).
The present document is part 3, sub-part 4 of a multi-part deliverable. Full details of the entire series can be found in
ETSI TS 102 744-1-1 [i.1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
This multi-part deliverable (Release 1) defines a satellite radio interface that provides UMTS services to users of mobile
terminals via geostationary (GEO) satellites in the frequency range 1 518,000 MHz to 1 559,000 MHz (downlink) and
1 626,500 MHz to 1 660,500 MHz and 1 668,000 MHz to 1 675,000 MHz (uplink).
ETSI
6 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
1 Scope
The present document defines the Bearer Connection Layer operation of the Family SL satellite radio interface between
the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. The Bearer
Connection Layer (BCn) peer-to-peer interface is described in ETSI TS 102 744-3-3 [9].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 125 322: "Universal Mobile Telecommunications System (UMTS); Radio Link Control
(RLC) protocol specification (3GPP TS 25.322 Release 4)".
[2] ETSI TS 133 102: "Universal Mobile Telecommunications System (UMTS); 3G security; Security
architecture (3GPP TS 33.102 Release 4)".
[3] ETSI TS 133 105: "Universal Mobile Telecommunications System (UMTS); Cryptographic
algorithm requirements (3GPP TS 33.105 Release 4)".
[4] ETSI TS 135 201: "Universal Mobile Telecommunications System (UMTS); Specification of the
3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specifications
(3GPP TS 35.201 Release 4)".
[5] ETSI TS 102 744-1-3: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 1: General Specifications; Sub-part 3: Satellite Radio Interface
Overview".
[6] ETSI TS 102 744-1-4: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 1: General Specifications; Sub-part 4: Applicable External
Specifications, Symbols and Abbreviations".
[7] ETSI TS 102 744-3-1: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 1: Bearer
Control Layer Interface".
[8] ETSI TS 102 744-3-2: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 2: Bearer
Control Layer Operation".
[9] ETSI TS 102 744-3-3: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 3: Bearer
Connection Layer Interface".
[10] ETSI TS 102 744-3-5: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 5: Adaptation
Layer Interface".
[11] ETSI TS 102 744-3-6: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 6: Adaptation
Layer Operation".
ETSI
7 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TS 102 744-1-1: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 1: General Specifications; Sub-part 1: Services and Architectures".
3 Symbols and abbreviations
3.1 Symbols
For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [6], clause 3 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [6], clause 3 apply.
4 General Architecture
4.0 Overview
The function of the satellite radio interface Bearer Connection Layer (BCn) is to provide a number of different data
transport services to upper layers. Figure 4.1 illustrates the position of the Bearer Connection Layer within the Family
SL air interface protocol stack. An overview of the radio interface layering and relationship to the Bearer Control Layer
is provided in ETSI TS 102 744-1-3 [5], clause 4 and ETSI TS 102 744-3-3 [9], clause 4. An overview of the Bearer
Connection Layer operation is provided in ETSI TS 102 744-1-3 [5], clause 6.
Figure 4.1: Bearer Connection Layer Position in Protocol Stack (Control Plane Illustrated)
ETSI
8 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
The Bearer Connection Layer is generic to the radio interface and is responsible for the following:
• Queuing;
• QoS Policing;
• QoS Monitoring;
• Segmentation and Re-assembly;
• Ciphering; and
• Selectable ARQ.
The data transport services provided by the Bearer Connection Layer are used to carry signalling and data PDUs across
the satellite radio interface. Three main data transport modes are supported:
• Acknowledged Mode (AM)
• Transparent Mode (TM)
• Unacknowledged (Numbered Frame) Mode (UM)
These are provided to the upper layers via a number of different service access points (SAP). The control plane and user
plane architecture of the Bearer Connection Layer is illustrated in Figure 4.2 and Figure 4.3 respectively.
The following clauses describe the Bearer Connection Layer SAP primitives for the upper interface to the Adaptation
Layer. The SAP primitives for the lower interface to the Bearer Control Layer are described in ETSI
TS 102 744-3-2 [8].
4.1 Bearer Connection Layer Entities
4.1.0 General
The Bearer Connection Layer consists of a Bearer Connection Manager and instances of one of four possible data
handlers (COM_DH, AM_DH, NUM_DH and TM_DH) with their associated Service Access Points (SAPs).
The Control Plane of each UE consists of an AM_DH for the UE Specific Signalling connection, a COM_DH for
managing the Common Signalling connection and a Bearer Connection Manager. On the RNC side, the Control Plane
consists of multiple sets of AM_DH and Bearer Connection Manager entities, one for each UE registered. It also has a
COM_DH for each of the Primary Shared Access Bearer.
ETSI
9 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
Adaptation Layer -
Control Plane
CBCn-
AM-SAP COM-SAP
SAP
Bearer
AM_DH Connection COM_DH
Manager
Bearer Connection
Layer - Control
BCt-DATA-
Plane BCt-COM-
STATUS-SAP
SAP
SAP
Bearer Control Layer
Figure 4.2: Bearer Connection Layer - Control Plane
The User Plane of each UE consists of a Bearer Connection Manager and one data handler (either TM_DH, NUM_DH
or AM_DH) for each data connection that is set up. On the RNC side, the User Plane consists of multiple sets of these
entities, one for each UE registered.
Adaptation Layer - User Plane
TM-SAP UM-SAP AM-SAP
Bearer
Connection
Layer
TM_DH NUM_DH AM_DH
Bearer
Connection
Manager
STATUS-
BCt-UCDATA- BCt-DATA-
SAP
SAP SAP
Bearer Control Layer
Figure 4.3: Bearer Connection Layer - User Plane
4.1.1 Bearer Connection Manager (BCnM)
The Bearer Connection Manager (BCnM) provides bearer connection management services to the Adaptation Layer via
the CBCn-SAP. This includes the creation and removal of a particular connection, and the setting of its QoS parameters.
ETSI
10 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
Four data handlers are supported by the Bearer Connection Layer:
• Acknowledged Mode Data Handler (AM_DH)
• Transparent Mode Data Handler (TM_DH)
• Numbered Frame Data Handler (NUM_DH)
• Common Signalling Data Handler (COM_DH)
These shall be created by the BCnM based on the requests received from the Adaptation Layer.
4.1.2 Acknowledged Mode Data Handler (AM_DH)
The Acknowledged Mode Data Handler shall be created when a reliable delivery message transport is required e.g. for
packet data and signalling connections. In the control plane, it is used to transport UE Specific Signalling (UESS)
messages from the Adaptation Layer (AL). Note that the SIG-SAP as defined in the Adaptation Layer
(see ETSI TS 102 744-3-6 [11]) is an instance of the AM-SAP.
Reliable delivery of data is provided by the AM_DH using an ARQ mechanism. It can also guarantee the ordered
delivery of packets and provide ciphering of data packets. The ciphered data Protocol Data Unit (PDU) is sent to the
Bearer Control Layer via the BCt-DATA-SAP. Queue status in the AM_DH is reported to the Bearer Control Layer by
the BCnM via the STATUS-SAP.
4.1.3 Transparent Mode Data Handler (TM_DH)
The transparent mode data handler (TM_DH) is created when a transparent data link is requested. This is primarily used
to support circuit switched (CS) traffic. In transparent mode, no connection layer overhead is added to the data arriving
from the layer above.
Data coming from the higher layer via the TM-SAP is buffered by the TM_DH before forwarding to the Bearer Control
Layer. No ciphering is performed at the connection layer and the data is sent to the Bearer Control Layer via the BCt-
UCDATA-SAP. The size of the buffer in TM_DH is always reported to the Bearer Control Layer by the BCnM via the
STATUS-SAP.
4.1.4 Numbered Frame Data Handler (NUM_DH)
For Un-Acknowledged Mode data coming from the layer above via the UM-SAP, a Numbered Frame Data Handler
(NUM_DH) shall be used. The NUM_DH provides in-sequence delivery, segmentation and re-assembly, and ciphering
of data. However, packet delivery is not guaranteed. The ciphered data PDUs are sent to the Bearer Control Layer via
the BCt-DATA-SAP.
4.1.5 Common Signalling Data Handler (COM_DH)
The Common Signalling Data Handler exists only in the control plane of the Bearer Connection Layer. This handler
provides buffering for Common Signalling messages from the Adaptation Layer. It also supports the reporting of
STATUS information via the STATUS-SAP to the control layer. No Ciphering is required for Common Signalling
messages in the Connection Layer.
4.2 Interfaces to Upper Layers
4.2.1 User Plane Interfaces
4.2.1.0 General
Three SAPs (AM-SAP, UM-SAP and TM-SAP) are defined between the Bearer Connection Layer and the upper layers
in the user plane. Their definitions are based on [1]. The primitives and parameters used are summarized below.
ETSI
11 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
4.2.1.1 Acknowledged Mode (AM)-SAP Primitives and Parameters
Three primitives are defined for the AM-SAP, as shown in Table 4.1.
Table 4.1: Primitives at the AM-SAP
Primitive Name Direction Parameters
BCn_AM_DATA_REQ To BCn Layer Data-PDU, PDCP-Info, CNF, DiscardReq, MUI, BcnID,
[Unsegmentable], [SUSP]
BCn_AM_DATA_IND From BCn Layer Data-PDU, PDCP-Info, DiscardInfo
BCn_AM_DATA_CNF From BCn Layer Status, MUI
The BCn_AM_DATA_REQ primitive is used by the higher layer to request transmission of a data PDU.
The BCn_AM_DATA_IND primitive is used by the BCn AM_DH to deliver a PDU to the higher layer entity.
The BCn_AM_DATA_CNF primitive is used by the BCn AM_DH to confirm to the higher layer entity that a data PDU
has been successfully transmitted to the peer AM_DH, or to inform it that a data PDU has been discarded. The
definitions of the parameters are as follows:
Data-PDU This is the higher layer data packet that is transferred.
PDCPInfo Optional parameter used by PDCP to transfer up to 5 bits of information to the peer PDCP entity.
CNF Confirmation Request, specifies whether higher layer requires confirmation of delivery of the
PDU.
DiscardReq Indicates whether the higher layer requires notification when the PDU is discarded.
MUI Message Unit ID, identifies the higher layer PDU that is being confirmed or discarded.
BcnID Bearer Connection ID, used to identify the Bearer Connection used.
DiscardInfo Indicates to the higher layer that a PDU has been discarded. It is applicable only when in-sequence
delivery is configured and it is to be used when the higher layer requires reliable data transfer.
Status Indicates whether a higher layer PDU is successfully transmitted or discarded.
Unsegmentable Optional parameter, indicating the fixed segment size to be used when transmitting this PDU.
SUSP Optional parameter used by the UESS AM_DH when in the suspended state, see clause 5.3.1.4.
4.2.1.2 Transparent Mode (TM) SAP Primitives and Parameters
Three primitives are defined for the transparent mode TM-SAP, as shown in Table 4.2.
Table 4.2: Primitives at the TM-SAP
Primitive Name Direction Parameters
BCn_TM_DATA_REQ To BCn Layer Data-PDU, DiscardReq, MUI, BcnID, [Unsegmentable]
BCn_TM_DATA_IND From BCn Layer Data-PDU, Err_ind
BCn_TM_DATA_CNF From BCn Layer MUI
The BCn_TM_DATA_REQ primitive is used by the higher layer to request transmission of a data PDU in transparent
mode.
The BCn_TM_DATA_IND primitive is used by the BCn TM_DH to deliver to the higher layer a PDU that has been
transmitted in transparent mode.
The BCn_TM_DATA_CNF primitive is used by the BCn TM_DH to inform the higher layer of a discarded data PDU.
The parameter definitions are the same as in AM-SAP, with the following addition:
Err_ind Error indicator, indicates that the PDU is erroneous. This is used to support the "delivery of
Erroneous PDU" mode of operation.
ETSI
12 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
4.2.1.3 Unacknowledged Mode (UM) SAP Primitives and Parameters
Three primitives are defined for the UM-SAP, as shown in Table 4.3.
Table 4.3: Primitives at the UM-SAP
Primitive Name Direction Parameters
BCn_UM_DATA_REQ To BCn Layer Data-PDU, PDCP-info, DiscardReq, MUI, BcnID,
[Unsegmentable]
BCn_UM_DATA_IND From BCn Layer Data-PDU, PDCP-info
BCn_UM_DATA_CNF From BCn Layer MUI
The BCn_UM_DATA_REQ primitive is used by the higher layer to request transmission of a data PDU in un-
acknowledged mode.
The BCn_UM_DATA_IND primitive is used by the BCn NUM_DH to deliver to the higher layer a PDU that has been
transmitted in un-acknowledged mode.
The BCn_UM_DATA_CNF primitive is used by the BCn NUM_DH to confirm to the higher layer of a discarded data
PDU.
The parameter definitions are the same as in AM-SAP.
4.2.2 Control Plane Interfaces
4.2.2.0 General
In the Control Plane, the Bearer Connection Layer interfaces to the Adaptation Layer above. Three SAPs are used in the
control plane, namely AM-SAP, CBCn-SAP and COM-SAP.
The AM-SAP in the control plane is used for transporting UE specific signalling messages between Adaptation Layer
peers. The Adaptation Layer SIG-SAP is an instance of AM-SAP and carries the same definitions (see clause 4.2.1.1)
except that it is connected to the AL instead of the PDCP Layer in the User Plane.
4.2.2.1 CBCn-SAP Primitives and Parameters
The CBCn-SAP is used for the exchange of control messages between the Bearer Connection Layer and the Adaptation
Layer. The following primitives are defined for the CBCn-SAP, as shown in Tables 4.4 to 4.6.
Table 4.4: Primitives at the CBCn-SAP common to UE and RNC
Primitive Name Direction Parameters
CBCn_CREATE_REJ To AL ALPD, BcnID, Rejection Cause
CBCn_MODIFY_REJ To AL ALPD, BcnID, Rejection Cause
CBCn_DESTROY_REQ To BCn layer ALPD, SEQUENCE OF {BcnID(SIG-SAP / DATA-SAP)}
CBCn_DESTROY_CNF To AL ALPD, SEQUENCE OF {BcnID}
CBCn_SECURITY_REQ To BCn layer ALPD, Mode (Start / Modify), CK, START, SEQUENCE OF
{BcnID, UL Activation Time, DL Activation Time}
CBCn_SECURITY_CNF To AL ALPD, SEQUENCE OF {BcnID}
CBCn_FAILURE_IND To AL ALPD, BcnID, Failure Cause
CBCn_SUSPEND_REQ To BCn layer ALPD, SEQUENCE OF {BcnID}
CBCn_SUSPEND_CNF To AL ALPD, SEQUENCE OF {BcnID, Next BCn Send Sequence
Number / Frame Number}
CBCn_SUSPEND_REJ To AL ALPD, SEQUENCE OF {BcnID}, Rejection Cause
CBCn_RESUME_REQ To BCn ALPD, SEQUENCE OF {BcnID}
CBCn_RESUME_CNF To AL ALPD, SEQUENCE OF {BcnID}
ETSI
13 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
Table 4.5: Additional Primitives at the RNC CBCn-SAP
Primitive Name Direction Parameters
CBCn_CREATE_REQ To RNC BCn ALPD, BcnID, (SIG-SAP / DATA-SAP), BCn/AL parameter
list, CK OPTIONAL
CBCn_CREATE_CNF To RNC AL ALPD, BcnID, BctID, {BCt EPDU} OPTIONAL
CBCn_MODIFY_REQ To RNC BCn ALPD, BcnID, (SIG-SAP / DATA-SAP), BCn/AL parameter
list, {CK} OPTIONAL
CBCn_MODIFY_CNF To RNC AL ALPD, BcnID, BctID, {BCt EPDU} OPTIONAL
CBCn_HANDOVER_IND To RNC AL ALPD, BCt EPDU
CBCn_HANDOVER_RSP To RNC BCn ALPD
CBCn_HANDOVER_REJ To RNC BCn ALPD, Rejection Cause
CBCn_HANDOVER_REQ To RNC BCn ALPD, Target Spot Beam ID, {Lease Group ID} OPTIONAL
Table 4.6: Additional Primitives at the UE CBCn-SAP
Primitive Name Direction Parameters
CBCn_CREATE_REQ To UE BCn ALPD, BcnID, (SIG-SAP / DATA-SAP), BCn/AL parameter
list, BctID, {BCt EPDU} OPTIONAL,
{CK} OPTIONAL
CBCn_CREATE_CNF To UE AL ALPD, BcnID
CBCn_MODIFY_REQ To UE BCn ALPD, BcnID, (SIG-SAP / DATA-SAP), BCn/AL parameter
list, BctID, {BCt EPDU} OPTIONAL,
{CK,} OPTIONAL
CBCn_MODIFY_CNF To UE AL ALPD, BcnID
CBCn_HANDOVER_REQ To UE BCn ALPD, BctID, BCt EPDU
CBCn_HANDOVER_CNF To UE AL ALPD
The CBCn_CREATE_REQ primitive is used by the Adaptation Layer to request the BCnM to create a new instance of
a data handler and its associated SIG-SAP or DATA-SAP (i.e. AM-SAP, UM-SAP or TM-SAP). The new bearer
connection is identified by the Bearer Connection ID (BcnID) specified in the primitive's parameter. The QoS and
connection setup parameters to be used for the new connection are specified in the BCn/AL parameter list, which
consists of:
BCn_Type, DefUnseg, QoS parameter list
The BCn_Type parameter specifies the type of Connection to be created and is specified in ETSI TS 102 744-3-5 [10].
The mapping between the type and connection configuration parameters is summarized in Table 4.7.
Table 4.7: Bearer Connection Types (BCn-Types)
BCn Type Data Handler Configuration Parameters
0 TM_DH DelvErrSDU = False, InSeqDelv = True
TM_DH DelvErrSDU = True, InSeqDelv = True
2 AM_DH DelvErrSDU = False, InSeqDelv = True
3 AM_DH DelvErrSDU = False, InSeqDelv = False
4 UM_DH DelvErrSDU = False, InSeqDelv = True
5 - (reserved)
6 UM_DH DelvErrSDU = False, InSeqDelv = True, To UE only
7 - (reserved)
For a Transparent Mode connection, the Boolean parameter DelvErrSDU is defined. If set to "true", the Data Handler
shall pass on any erroneous PDUs to the higher layer together with the flag Err_ind set. The default value is "false",
i.e. only error free PDUs are sent to the higher layer.
For an Acknowledged Mode connection, the Boolean parameter InSeqDelv can be specified. When set to "false", the
AM_DH shall deliver completed PDUs as they are received and shall not wait until all previous PDUs have been
completed. This could mean PDUs are delivered to the higher layer out of order. The default value is "true", i.e. all data
shall be delivered in sequence.
The parameter DefUnseg specifies the default unsegmentable size and controls whether any restriction on the segment
size applies to this connection. The default is zero, i.e. un-restricted segmentation.
ETSI
14 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
The QoS parameter list contains all UMTS specific QoS parameters from the AL, and the satellite radio interface QoS
parameters for the connection and control layers as specified in ETSI TS 102 744-3-5 [10] and ETSI
TS 102 744-3-1 [7]. Connection layer parameters in this list include AllocationSize, MeanRate, TargetLatency,
DiscardLatency, ResponseTime and MaxIdleTime.
On the UE side, the CBCn_CREATE_REQ also carries the BctID and any embedded BCt information that the
Adaptation Layer may have received from the RNC. Such BCt EPDU information shall be passed to the Bearer Control
Layer, In addition, at the UE side, any Bearer Connection specific parameters, such as the group CK values to be
applied to a Multimedia Broadcast Multicast Services (MBMS) Connection are received in the CBCn_CREATE_REQ.
After the data handler and SAP have been successfully created, the Bearer Connection Layer shall respond with a
CBCn_CREATE_CNF primitive. On the RNC side, any Bearer Control information (e.g. ConnectionAssociation,
ConnectionReasociation, etc.) that requires to be embedded, shall be passed to the Adaptation Layer via the BCt EPDU
field and in addition, any Bearer Connection specific parameters, such as the group CK values to be applied to a MBMS
Connection.
If for some reason the operation failed, then a CBCn_CREATE_REJ primitive shall be returned with the Rejection
Cause code.
The CBCn_MODIFY_REQ, CBCn_MODIFY_CNF and CBCn_MODIFY_REJ primitives are similar to the
CBCn_CREATE primitives, except that they are only used when modification of an existing connection is requested.
The CBCn_DESTROY_REQ primitive is used by the Adaptation Layer to request the release of a bearer connection
(identified by its BcnID) and the removal of the associated data handler and DATA-SAP. Any un-transmitted data will
be lost. After the connection is removed, the Bearer Connection Layer shall respond with the CBCn_DESTROY_CNF
primitive.
The CBCn_SECURITY_REQ primitive is used by the AL to set up the ciphering operation for a set of bearer
connections (identified by their BcnIDs). The ciphering parameters for all connections shall then be configured
according to the specified CK and START parameters at the specified DL and UL Activation Time. For any
Transparent Mode Connection, the Bearer Connection shall pass the ciphering configuration to the Bearer Control
Layer which shall confirm the setup. It should be noted that this security information only applies to UE-specific
connections, and not the forward direction associated with a MBMS Connection, which uses a group security
association.
After all the ciphering setup is completed (and confirmed from the Bearer Control Layer), the Bearer Connection Layer
shall respond to the Adaptation Layer with the CBCn_SECURITY_CNF primitive.
The CBCn_FAILURE_IND primitive is used by the BCn to signal to the Adaptation Layer a failure of the bearer
connection. This will occur, for example, if the MaxIdle Timer times out. Two Connection Layer Failure Cause codes,
namely ConnFailure and MaxIdleReached, are currently defined. This primitive is also used to forward Bearer Control
Layer error conditions to the Adaptation Layer (i.e. received via the BCt_FAILURE_IND primitive). Valid Bearer
Control failure codes include MaxUnAckReached, NoForwardBearer and IncorrectForwardBearer on the UE side, and
UEChkLimitReachedRelease on the RNC side.
The CBCn_SUSPEND_REQ primitive is used by the AL to stop the transmission of any new (unsegmented) data for
the specified bearer connections. Retransmission of old data, selective reject, poll, poll response signalling are still
allowed. Once all connections are halted, the Bearer Connection Layer shall respond with CBCn_SUSPEND_CNF and
specify the next send sequence number for each connection to the Adaptation Layer. If the operation failed (for
example, if there is an error in the list of connections to be suspended), a CBCn_SUSPEND_REJ primitive shall be
returned with the corresponding Rejection Cause code.
The Bearer Connection Layer shall resume the sending of new data for these connections when the
CBCn_RESUME_REQ primitive is received. It shall reply with CBCn_RESUME_CNF when the connections are
restarted.
The UE Specific Signalling connection shall not be suspended (special transmit path processing rules apply while in the
suspended state, see clause 5.3.1.4), but the next Send Sequence number shall be returned via CBCn_SUSPEND_CNF
primitive. Any Transparent Mode connections shall not be suspended, but the current frame number shall be returned
via the CBCn_SUSPEND_CNF primitive.
ETSI
15 ETSI TS 102 744-3-4 V1.1.1 (2015-10)
The CBCn_HANDOVER_IND primitive is used by the RNC BCn to signal the Adaptation Layer to send a Handover
signal for all of the UE's connections. This is triggered when the RNC Local Resource Manager (LRM) function
initiates a Handover operation in the Bearer Control Layer via the STATUS_SAP. The primitive also specifies all the
associated ConnectionAssociation and ConnectionReassociation information via the BCt EPDU parameter. When the
Adaptation Layer receives the HandoverAck message, it shall return the CBCn_HANDOVER_RSP primitive to the
Bearer Connection Layer. If the handover operation fails, the Adaptation Layer shall send a CBCn_HANDOVER_REJ
primitive to the Bearer Connection Layer with the corresponding Rejection Cause code. The Bearer Connection Layer
shall route this on to the Bearer Control Layer.
The Adaptation Layer on the RNC side can send the CBCn_HANDOVER_REQ primitive to the Bearer Connection
Layer to start the UE-Initiated Handover Procedure or the Lease Mode Handover Procedure in the Bearer Control
Layer. The Bearer Connection Layer shall pass this onto the Bearer Control Layer in order to trigger the LRM functions
to start the Handover procedure.
On the UE side, when the Adaptation Layer receives the Handover signalling PDU, it signals to the Bearer Connection
with the CBCn_HANDOVER_REQ to reconfigure the BCn and BCt layers. When the UE Bearer Connection and
Control Layer finished retuning to the new bearer, the CBCn_HANDOVER_CNF message shall be returned to the
Adaptation Layer. The Adapta
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...