hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 1 Scope | The present document defines the Bearer Control Layer (BCt) 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 Control Layer (BCt) peer-to-peer interface is described in ETSI TS 102 744-3-1 [8]. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 2 References | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 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 ar... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 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 in... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 3 Symbols and abbreviations | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 3.1 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [5], clause 3 apply. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [5], clause 3 apply. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 4 General Architecture | The Bearer Control Layer (BCt) provides medium access control functionality for both the control and user planes. Figure 4.1 illustrates the position of the Bearer Control Layer within the Family SL air interface protocol stack. An overview of the radio interface layering and relationship to the Bearer Control Layer is... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5 Bearer Control Services | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.1 Bearer Control Service Access Points | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.1.0 General | The internal architecture of the Bearer Control Process for the UE side is shown in simplified form in Figure 5.1. The diagram shows both control plane and user plane. The functionality is broadly categorized into control functions provided by the BCt Manager (BCtM) entity and data transfer functions provided by the UE... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.1.1 Services provided to Upper Layers | The Bearer Control Layer provides media access functions to the upper layers (Bearer Connection Layer and Adaptation Layer) via the following service access points (SAP). • CBCt-SAP: providing services to AL related to initiation of PSAB discovery procedures, providing GPS position for reporting purposes and delivery o... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.1.2 Services Expected from the Lower Layers | The Bearer Control Layer relies on the Physical Layer for transmitting and receiving Bearer Control Protocol Data Units (PDUs) to its peer entity at the RNC side. Three Service Access Points, namely the Physical Layer SAP (PL-SAP), Receive SAP (Rx-SAP) and Transmit SAP (Tx-SAP) are referenced in the present document. T... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.1.3 Services Expected from External Entities | The BCt-NAV-SAP interface is used to obtain geographical location and other navigational information from an external navigational sub-system. This external sub-system may be internal to the mobile terminal (typically the case for portable, maritime and land-vehicular mobile terminals), or may be provided by an externa... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2 Bearer Control Layer Service Primitives | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.1 Data Transfer Service Access Points | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.1.1 BCt-DATA-SAP Primitives and Parameters | The BCt-DATA-SAP is used for the transfer of the Acknowledged Mode and Numbered Mode data between Bearer Connection and Control layer. The BCt-DATA-SAP primitives are shown in Table 5.1. Table 5.1: BCt-DATA-SAP Primitives Primitive Direction Parameters BCt_TxDATA_REQ To BCt BCnID, DataSize, BCnPDU BCt_TxDATA_IND To BCn... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.1.2 BCt-UCDATA-SAP Primitives and Parameters | The BCt-UCDATA-SAP is used for the transfer of the Transparent Mode data between Bearer Connection and Control layer. The BCt-UCDATA-SAP primitives are shown in Table 5.2. Table 5.2: BCt-UCDATA-SAP Primitives Primitive Direction Parameters BCt_TxUCDATA_REQ To BCt BCnID, DataSize, BCnPDU BCt_TxUCDATA_IND To BCn DataSize... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.2 Navigational Interface Service Access Points | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.2.1 BCt-NAV-SAP (Maritime and Land-Mobile Class UE Only) | The BCt-Nav-SAP is used by the BCtM to obtain geographical location and other navigational information from a navigational subsystem external to the Bearer Control layer. The BCt-Nav-SAP primitives for Portable, Maritime and Land Mobile UE are shown in Table 5.3. ETSI ETSI TS 102 744-3-2 V1.1.1 (2015-10) 13 Table 5.3: ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.2.2 BCt_NAV_SAP Interface with avionics (Aeronautical Class UE Only) | The aeronautical UE shall be able to access regular updates of position and velocity from the avionics in order to be able to perform spot-beam selection and compensation for Doppler frequency offset, but the specifics of the interface are implementation-dependent. For aeronautical UE, the BCt-Nav-SAP is used by the BC... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.3 Control Plane SAPs | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.3.1 STATUS-SAP Primitives and Parameters | The STATUS-SAP is the main control interface between the Connection and Control layer. It is used for the setting up of various BCt and for the reports of queue status for each bearer connection. The STATUS-SAP primitives are shown in Table 5.5. ETSI ETSI TS 102 744-3-2 V1.1.1 (2015-10) 15 Table 5.5: STATUS-SAP primiti... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.3.2 BCt-COM-SAP Primitives and Parameters | The BCt-COM-SAP is used for the transfer of Common Signalling data between Bearer Connection and Control layer. The BCt-COM-SAP primitives are shown in Table 5.6. Table 5.6: BCt-COM-SAP Primitives Primitive Direction Parameters BCt_TxCOMSIG_REQ To BCt UE_ID-type, UE_NAS_ID, DataSize, AL-ComPDU BCt_TxCOMSIG_IND To BCn D... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 5.2.3.3 CBCt-SAP Primitives and Parameters | The CBCt-SAP is used by the Adaptation Layer to acquire a PSAB, GPS position data and System Information from the Bearer Control Layer. The CBCt-SAP primitives are shown in Table 5.7. Table 5.7: CBCt-SAP Primitives Primitive Direction Parameters CBCt_DISCOVER_REQ To BCt ALPD, Global Discover Flag, SEQUENCE OF {PSAB Inf... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6 Bearer Control Architecture | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.1 Bearer Control Architecture - UE Side | The Bearer Control architecture on the UE side is illustrated in Figure 6.1. Figure 6.1: Bearer Control Layer - UE Side |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2 Overview of Functional Entities in the Bearer Control Layer | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.0 General | The Bearer Control Layer on the UE side consists of the following entities: • Control plane elements within the Bearer Control Manager (BCtM) comprising: - Connection Control ETSI ETSI TS 102 744-3-2 V1.1.1 (2015-10) 18 - System Information Broadcast Handling unit - Timing Control - Physical Bearer Management - Common ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.1 Bearer Control Manager (BCtM) | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.1.0 General | The Bearer Control Manager (BCtM) provides the main management interface to the Connection Layer above and to the physical layer below. It receives commands from the Connection Layer (via STATUS-SAP) to create or destroy bearer control units for each UE (UE_BCt). It also creates one data SAP (either BCt-DATA-SAP or BCt... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.1.1 System Information Broadcast Handling Unit | The RNC broadcasts a number of information elements to all UE in order to control how they access the system. The System Information Broadcast Handling unit is responsible for receiving and decoding this system information. It will maintain up-to-date system information and is stored in the BCtM for further use. The Ad... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.1.2 Common Signalling Handler (COM_BCt) | The Common Signalling Handler (COM_BCt) manages the common signalling channel and interfaces to the Connection Layer via the BCt-COM-SAP. The architecture for the COM_BCt is illustrated in Figure 6.2. The Common Signalling Manager (COM_BCt_M) is responsible for handling all AVPs associated with the Common Signalling Ch... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.2 UE Bearer Control Unit (UE_BCt) | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.2.1 UE BCt User Plane Handling Function | The UE Bearer Control entity (UE_BCt) is responsible for the UE-Specific Signalling and all data connections associated with a particular UE. The architecture for the UE_BCt is illustrated in Figure 6.3. The connections that are given capacity to send data are signalled from BCt-M. The BCt Manager (BCt_M) will collect ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.2.2 Queue Status Reporting | The Queue Status Reporting functional entity is responsible for generating reporting of queue status to the RNC for each connection. The behaviour for queue reporting is dependent upon both the type of Radio Access Bearer (RAB) connection and the type of signalling specified by the RNC, for instance the following appli... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.2.3 Return Schedule Processing | The Return Schedule Processing functional entity interprets the received Return Schedules and any Broadcast AVPs to determine the opportunity to send in any time-slot. It is responsible for creating a local description of the slots available for communication by the mobile terminal over a specific return scheduling per... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.2.4 Transmit Burst Assembly | The Transmit Burst Assembly function controls the transmissions from the mobile terminal in the return direction, using the information provided by the Return Schedule Processing entity which describes the opportunities for the mobile terminal to transmit. This entity then determines which of the connections (Common si... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.2.5 Bearer Transmit Buffer (Bearer_Tx) | The Bearer Transmit Buffer shall collect the BCtPDUs from COM_BCt and UE_BCt and send them to the Physical layer for transmission on the physical layer. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 6.2.2.6 Bearer Receive Buffer (Bearer_Rx) | The Bearer Receive Buffer collects from the Physical Layer all BCtPDUs decoded within a received FEC block and routes these to the System Information Broadcast Handling Unit, Scheduling Control, Common Signalling or UE Bearer Control as appropriate, for further decoding. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7 Bearer Control Management (BCT-M) Behaviour | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1 Physical Bearer Management | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.1 Forward Bearer Configuration and Initial Bearer Scan | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.1.0 General | Prior to any communications taking place, it is necessary for the UE to acquire a Primary Shared Access Bearer (PSAB) suitable for communications in either a Regional Beam or Narrow Spot Beam. This requires that the UE perform an initial scan of the stored Global Beam frequencies, decode the System information, and the... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.1.1 Global_Scan process | The Global_Scan process requests the Physical Layer (PL) to acquire individual Global Beam bearers in the specific order listed in the PSAB Information parameter. The used acquisition shall be initial (refer to ETSI TS 102 744-2-2 [7] for definitions of acquisition modes). The PSAB at the top of the list shall be scann... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.1.2 Default_Scan process | The Default_Scan process shall instruct the PL to perform a warm acquisition on all the PSABs in the list one by one. If one particular PSAB is not acquired through the warm acquisition mode then a cold acquisition shall be tried. After each successful acquisition the C/No is measured on 6 consecutive frames and the re... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.2 Forward Bearer Frequency Control within a Bearer Control | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.2.1 Retuning a population of UEs | The mechanism for retuning mobile terminals from one forward bearer to another within the same Bearer Control process is based on the use of the ChannelNo AVP. When a UE receives this AVP, it shall retune to the forward bearer specified. The ChannelNo AVP may be used whether the new bearer is within the same 200 kHz ba... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.2.2 Relocation of a specific UE | When the RNC relocates a specific UE to a new forward bearer within the same Bearer Control, all the connections associated with the UE are moved. This shall be signalled by using the ChannelNo AVP with the Ack-Required flag set to 1. The AVP can be sent using any active forward UE Connections. If all UE forward connec... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.3 Forward bearer synchronization loss | Loss of forward bearer shall be signalled from the physical layer if no unique words are detected within a specified time, or detected by continuous CRC failure within the BCt layer (any instance of re-acquisition shall re-start this timer). If the current forward bearer is lost for a default 10 seconds (Land Class UEs... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.1.5 Return Bearer Doppler Compensation (Aeronautical Class UE Only) | An Aeronautical Class UE will typically impart a large offset in the carrier frequency it transmits as seen from the satellite, due to the Doppler effect. At up to 300 m/s, with an L-band receive frequency of ~1,642 GHz (middle of the band), this can represent up to +/- 1,6 kHz of offset. Therefore, the UE shall apply ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.2 System Information Broadcast Handling | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.2.1 Storage of System Information | The UE shall store all system information on an RNC basis. For each rnc-id, the net-ver shall be stored, as well as all information elements, in Table 7.1. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.2.2 Acquisition of System Information | At initial switch-on the UE shall await reception of the SystemInfoIndex SDU and all the broadcast system information elements (applicable to the UE Class and implementation options). To ensure reception of critical system information by Low Gain Antenna (LGA) class mobile terminals, the RNC will transmit a replica of ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.2.3 System Information Index - UE Behaviour | On receiving a BCtSDU the System Information Broadcast Handling (SIBH) entity shall: • Decode BCtSDU of type BulletinBoard, compare the stored values of net-ver, f-bearer, bct-id and spot-beam-id received in the BulletinBoard SDU against that stored for the specified rnc-id and if any of these values have changed, upda... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.2.4 Wrap Around, Instances and Version Number Range | When a UE receives a SystemInfoIndex SDU it checks whether any information elements have different version number or number of instances to that recorded previously or whether any information elements have been added, subtracted or have a version number set to 0. The UE shall determine whether there may have been a "wr... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.3 Common Signalling (Com_BCt) Procedures | Common Signalling is only used for the initial registration procedure. Prior to registration the UE may be untimed and will not have any link adaptation information. Specific procedures for access to the return channel apply during the initial common signalling operation. Upon receipt of a request to utilize the Common... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.4 Connection Control Operations | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.4.0 General | The following clauses cover the bearer control operations required when connections are established and released. It also covers the handover scenarios when connections are moved from one bearer control to another. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.4.1 Connection Set-up Operations | The Embedded Bearer Control SDU (BCtESDU) is the mechanism that allows Bearer Control information to be carried within an Adaptation Layer message. During the registration process, the ConnectionAssociation ESDU may be used to inform the UE of the assigned tBCnID for the UE Specific Signalling Connection. If a Connecti... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.4.2 Connection QoS Control | When a connection is requested by the UE, it shall specify a set of service QoS parameters required. Once accepted by the CN and higher layers, these are translated into Bearer Control QoS parameters. The final negotiated Bearer Control QoS parameters are signalled using the Type0QoS AVP. Certain QoS parameters can be ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.4.3 Connection Release Operations | A connection release can be initiated by either the UE or the RNC. A connection can be released as a result of application closure, Bearer Connection or Control Layer error conditions. ETSI ETSI TS 102 744-3-2 V1.1.1 (2015-10) 28 In the Bearer Control Layer, the UE shall monitor the forward bearer while the UE is not i... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.4.4 Handover Operations | Bearer Connections may be handed over from one bearer control to another as result of: • a UE moving from one spot beam to another; or • a UE being moved from one bearer control process to another within the same beam. The Handover message shall contain the reattached-conn-info-list and hardware-info-list ESDUs providi... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.5 Timing Control Operation | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.5.1 Principles of timing control operation | The Return Channel Timing is derived from broadcast System Information elements and locally derived knowledge regarding the mobile terminal geographical location. The UE receives state vectors on the forward link, which it uses to calculate the instantaneous satellite position. The state-vectors are calculated such tha... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.5.2 Primary and Secondary Timing Modes | The Return Channel Timing Control shall be implemented using two basic approaches: Primary: The Primary timing mode is essentially an open-loop timing correction method, and employs the satellite state vectors broadcast by the RNC using the SatelliteStateVectors AVP, together with geographical position estimates derive... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.5.3 Transition between Primary and Secondary Timing modes | If a UE, which is in Primary Timing Mode, receives a "TimingCorrection" AVP from the RNC with a magnitude greater than 120 microseconds, then it shall transition to the secondary timing mode. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.5.4 Aeronautical Class UE without GPS | A special timing mode combining key aspects of primary and secondary timing shall be used for aeronautical terminals where GPS derived position data is not available, but position source with a slowly varying error is available (e.g. from an Inertial Reference System (IRS)). For these UEs, initial transmissions to the ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 7.6 Sleep Mode Operations | A UE is assigned Sleep Mode from the RNC via the Control Layer signalling during registration The information passed indicates the desired level of power saving to be achieved due to Sleep Mode operation. The desired level of power saving is dictated by a trade-off between the standby-time requirements and paging respo... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8 Bearer Control User Plane (UE-BCT) Behaviour | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1 Ciphering Operations | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.0 General | For Transparent Mode Bearer Connection PDUs, ciphering and deciphering is performed in the Bearer Control Layer. Ciphering shall be implemented in accordance with ETSI TS 133 102 [1] and ETSI TS 133 105 [2], however, some minor modifications are required to accommodate the differences between UTRAN MAC and the satellit... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.1 Input Parameters to the Ciphering Algorithm | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.1.1 CK | The cipher key CK is 128 bits long and shall be applied as specified in [1]. No modification is required for the satellite network. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.1.2 COUNT-C | The ciphering sequence number COUNT-C is 32 bits long and is modified for the satellite network to reflect the counters available in the satellite radio interface protocol stack. In Transparent Mode (TM) COUNT-C is composed as follows: • The 16 least significant bits of COUNT-C consist of two parts: the 12 most signifi... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.1.3 TBCNID | The translated bearer connection identifier TBCNID is 12 bits long and is available in the BCt-PDU header. This is used to replace the radio bearer identifier BEARER used in the UTRAN ciphering configuration. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.1.4 DIRECTION | The direction identifier DIRECTION is 1 bit long. Its value is applied as specified in [1]: DIRECTION = 0 for messages from UE to RNC DIRECTION = 1 for messages from RNC to UE. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.1.5 LENGTH | The length indicator LENGTH is 16 bits long. It specifies the length of the required keystream block in bits and does not affect the actual bits in the keystream block. |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.2 Initialization of Keystream Generator | The initialization of the keystream generator is specified in [3], clause 3.4 for UTRAN. In order to accommodate the input parameters used in the satellite network, the 64-bit register A shall be set to: COUNT-C || TBCNID || DIRECTION || 0…0 (left justified with the right most 19 bits set to 0), such that: A = COUNT-C[... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.1.3 Synchronization of ciphering | When ciphering of a new TM Bearer Connection is started, the 16 most significant bits of the Bearer Control Hyperframe Number (BCT HFN), shown in Figure 8.2, are initialized with the 16 least significant bits of the current value of the parameter START (see [1], clause 6.4.8). The timing of this initialization in terms... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2 Queue Status Reporting | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.0 General | In order for a UE to be allocated sufficient capacity to transmit either signalling or data messages, it needs to report its demand or queue status to the RNC. Three signalling mechanisms exist for the purposes of providing queue status reporting: 1) Status SDU 2) QLen SDU 3) QRate SDU All UEs shall support the Status ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1 Status SDU Queue Reporting Mechanisms | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.0 General | The UE is required to transmit status information on a regular basis on all packet-switched connections, except connections of type constant-bit-rate which shall not generate any Status SDUs. A Status SDU can be sent either in a contention or a reserved slot (Status SDUs are not used in Controlled Random Access or Shar... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.1 Principle of Operation | The basic philosophy is to give the RNC all the information it needs to make the resource-allocation decisions. In principle, whenever the UE queue size changes, it would like to communicate this to the RNC. However, this would take up a lot of capacity on the return link, particularly since it is most likely to occur ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.2 Data Status Update | The parameters required for constructing the Status SDU shall be derived from the latest BCt_DATASTATUS_REQ message received for the connection. ETSI ETSI TS 102 744-3-2 V1.1.1 (2015-10) 36 The Status information is provided by the Bearer Connection Layer to the Bearer Control whenever its queue changes, i.e. when: • N... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.3 Definition of QueueSize parameters sent by Connection Layer | The QueueSize parameters as sent from the Connection layer provide an estimate of the volume of data that need to be sent, including connection layer overhead: this calculation shall be carried out in the Connection Layer where PDUSize is the size of a BCn PDU AllocationSize is set to [32] bytes by default, unless the ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.4 Processing of Status Update | This procedure calculates CN.TReportTime whenever there is a change at the head of the queue. TReportTime is the earliest time this new Status information will normally be reported if a contention slot is used. First, LatestTime calculates the latest time that a Status SDU can be sent in order to still give enough time... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.5 Status SDU Generation | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.5.0 General | The Status information shall reflect the status of the UE queue after the transmission of the data contained in the slot where the Status SDU was received. At initialisation: Let CN.SelectedFrame = 0 end initialisation Whenever BCt_DATASTATUS_req or BCt_COMSIGSTATUS_req signals are received, then, for a connection reco... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.5.1 Criterion A | Criterion A is a large Boolean expression, which is used to control whether or not the UE is allowed to use contention slots for the Status SDU signalling. The Criterion A is fulfilled if one of the following is true: 1) A StatusAck is missed from the RNC. 2) The reserved-slot-timer has expired. 3) The TReportTime has ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.5.2 Criterion B | Criterion B is used to determine if a slot shall be used for a Status SDU if the rest of the data queue fits into the slot (DataSize is the amount of data expected to be sent if the Status SDU is sent), given that the slot shall be used anyway. In addition, if a slot is a contention-slot, and the connection-layer data ... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.6 Status SDU Control | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.6.1 Status Ack | All received Status SDU are acknowledged by the RNC using the StatusAckList SDU, which carries multiple StatusAck. Whenever a Status SDU is sent, the UE shall start a Status-ack-timer with a timeout period of (t-ack-wait + rtt). If the timer expires before the StatusAck is returned, then the UE shall send another Statu... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.6.2 Status SDU Control Mechanisms | A number of system parameters control the operation of Status SDU. The two primary ones are: t-ack-wait: default value 240 ms MaxUnAckStatus: default value 8 These values can be changed by the RNC by using the StatusAckControl AVP. This AVP can be sent using the SpecificAVPList SDU or the AVPList SDU to signal the chan... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.1.6.3 Status Reporting Timers | Each Bearer Connection has the following timers, either or both of which may be running: • Status-ack-timer: waiting for a Status Acknowledgement to the last Status sent • Reserved-slot-timer: waiting for a reserved slot When a recognised StatusAck is received: If (SeqNum in Ack = CN.StatusSeqNum) and (Tnow >= CN.TStat... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.2 QLen SDU Queue Status Reporting Mechanism | The QLen SDU queue status reporting mode is an alternative approach to the use of the Status SDU for signalling the queue status for the UESS and background class RABs to the RNC. The QLen SDU does not require an acknowledgement from the RNC. The QLen SDU queue status reporting mode shall be used if supported by the UE... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.2.3 QRate SDU Queue Status Reporting Mechanism | The QRate SDU queue status reporting mode is an alternative approach to the use of the Status SDU for signalling the queue status to the RNC. It allows the signalling of a perceived required rate rather than a queue length, this being more suitable for certain classes of applications that generate traffic on a continuo... |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.3 Return Schedule Processing | |
7dd505413f382a7ee81a0835c26d2ad7 | 102 744-3-2 | 8.3.1 General Concept of Operation | The Return Schedule Processing entity is responsible for creating the list of radio resources which represent the opportunity to transmit for the mobile terminal. The Return Schedule Processing entity receives all Return Schedules as well as the ControlledRandomAccess and SharedReservationAccess Broadcast AVPs and comp... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.