hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3 Elementary Procedures | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.1 Scheduling and Beamforming Commands Transfer procedure | This procedure is used to exchange C-Plane messages between O-DU and O-RU. The main purpose of these messages is to transmit data-associated control information required for processing of user data (e.g., scheduling and beamforming commands) if such information is not provided via M-Plane (see clause 8.2.2 for more det... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.2 Mixed Numerology and PRACH Handling | 5G NR defines Physical Resource Block (PRB) where the number of subcarriers per PRB is the same for all numerologies (twelve). However, subcarrier spacing may differ, resulting in mixed numerology used in time and frequency domains respectively. Likewise, mixed numerologies may be applied to both DL and UL respectively... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.3 DL Precoding configuration parameters and indications | This clause addresses the method of specifying the precoding operation in the O-RU, which is expected when Category B O-RUs are supported. For Category A O-RUs the precoding is implemented in the O-DU so the descriptions in this clause are not relevant. Annex I contains more information and examples regarding this prec... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.4 LAA Commands Transfer procedure | This procedure is used to exchange C-Plane messages between O-DU and O-RU. The main purpose of these messages is to support LAA feature in the O-RU/O-DU. See Annex G for more details on the LAA message flow. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.4.1 LBT procedure overview | The LBT procedure is used to configure the O-RU with the parameters needed to do LBT prior to PDSCH or DRS transmission OTA. The O-RU needs to report the LBT process outcome (either success or failure) in the indication message. In contrast to licensed spectrum, where the O-RU may continuously send data or reference si... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.4.2 Definitions | • : Maximum one-way fronthaul latency • : Maximum O-DU processing time (reading an upstream O-RU c-plane message, MAC processing, sending the downstream U-plane data) • : Maximum O-RU processing time (sending an upstream c-plane message, receiving downstream U-plane data, transmitting U-plane data OTA) • : ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.4.3 General Guidelines for the LAA-procedure | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.4.3.1 PDSCH Transmission | • O-DU should avoid buffer overflow or underflow at the O-RU: • O-DU should only send worth of data to the O-RU for every single transmission • O-DU should plan for the data to be received at the O-RU only before the actual OTA transmission time at the O-RU • O-RU should avoid buffer overflow or underflow at th... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.4.3.2 DRS Transmission | • Recall: 1. PSS/SSS being part of a DRS may occur outside subframe 0 and 5 2. CRS/CSI-RS/PSS/SSS do not vary with subframe number but are kept unchanged across subframes 0–4 (call it DRS_v1) and 5–9 (DRS_v2). • Assumption: DRS OTA transmission starts at the SF boundaries. • The DRS signal may be received before or aft... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.4.3.3 Congestion Window Information Transmission | • O-DU should send information regarding a congestion window adjustment to O-RU • HARQ feedback information for the reference subframe and number of TB are included • O-RU should adjust its managed congestion window value and notify to O-DU the packet reception status • O-RU should adjust its congestion window value ba... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.5 Symbol Numbering and Duration | For the NR case, data symbol numbering in a slot shall be from zero to thirteen (for extended CP, eleven). For LTE the symbol numbering shall be mapped to the NR numbering as follows: LTE with normal prefix maps to NR with same μ and normal prefix: LTE symbol of slot 2 is mapped to NR slot , symbol ′ = LTE... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.6 Dynamic Spectrum Sharing (DSS) | Dynamic Spectrum sharing allows different technologies – 4G LTE and 5G NR in this version of the specification, to share same frequency carrier dynamically, i.e. the O-DU may allocate one or more set(s) of frequency-time resources (or PRBs) to LTE or NR dynamically. The O-RU also shall support this feature for the O-DU... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.6.1 Dynamic Spectrum Sharing (DSS) via Dedicated Endpoints | Dedicated endpoints are configured in the O-RU for LTE and NR (hence dedicated eAxC ids) to implement DSS. For e.g. when an O-DU allocates a set of PRBs for LTE, O-DU uses an eAxC id dedicated for LTE (assigned to a carrier identified as an LTE carrier) to address the LTE endpoint; at a different time when the O-DU all... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.6.2 Dynamic Spectrum Sharing (DSS) via Section Extension =9 for DSS | Using Section Extension =9 for DSS, the O-DU can use a single eAxC id (and hence a single endpoint) for conveying LTE and NR PRB allocations if the O-RU is capable of handling both LTE and NR processing using one endpoint (i.e. ETSI ETSI TS 103 859 V7.0.2 (2022-09) 78 the O-RU indicates support for Section Extension =9... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.3.7 Channel Information based Beamforming | In channel information based beamforming method, the O-DU provides channel information per UE periodically (generally less often than every slot) using Section Type 6 C-plane message and then on a slot-by-slot basis the O-DU provides scheduling information using Section Type 5 C-plane message which the O-RU uses along ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4 Elements for the C-plane Protocol | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.1 General | C-Plane messages are encapsulated using a two-layered header approach. The first layer consists of a eCPRI common header or IEEE 1914.3 common header, including corresponding fields used to indicate the message type, while the second layer is an application layer including necessary fields for control and synchronizati... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.1.1 Section Extensions | Within a data section description, the section header in most cases includes an “extension flag” which indicates parameters that apply to the section beyond those within the section header (the extension flag is most often adjacent to the beamId or ueId fields). The presence of this extension flag indicates that follow... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.1.2 Coupling of C-Plane and U-Plane | Selected types of C-Plane messages (Section Types 1, 3 and 5) carry data section descriptions that convey information applicable to data sections carried in U-Plane messages. This clause describes a method of coupling data section descriptions from C-Plane and data sections in U-Plane. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.1.2.1 Coupling via sectionId Value | This method of C-Plane and U-Plane coupling is used by default. O-DU may configure O-RU to use the other method via M-Plane. In this method, information from section description D in C-Plane message CM is applied to resource element R in PRB P (PRB understood as 12 resource elements of one OFDM symbol consecutive in fr... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.1.2.2 Coupling via Frequency and Time | This coupling method is used if a corresponding capability is reported by O-RU via M-Plane and use for an eAxC is configured via M-Plane. In this method, information from section description D in C-Plane message CM is applied to resource element R in PRB P (PRB understood as 12 resource elements of one OFDM symbol cons... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.1.2.3 Coupling via Frequency and Time with Priorities | This optional coupling method is used if a corresponding capability is reported by O-RU via M-Plane and use for an eAxC is configured via M-plane. In this method information from section description D in C-Plane message CM is applied to resource element R in PRB P (PRB understood as 12 resource elements of one OFDM sym... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.1.2.4 Coupling via Frequency and Time with Priorities (Optimized) | All the restrictions remain same as coupling via frequency and time with priorities except restriction 5: 5. Sender of C-Plane shall send in sectionId value 4095 for section description with lower priority. For highest priority sections unique sectionIds shall be set in a defined range starting from “0” to “max-highest... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.2 Scheduling and Beamforming Commands | A common frame format is used for C-Plane messages, consisting of a transport layer and an application layer. The application layer is within the transport layer payload and consists of a common header for time reference, followed by information and parameters dependent and specific to the Section Type in use. Multiple... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.1 dataDirection (data direction (gNB Tx/Rx)) | Description: This parameter indicates the gNB data direction. Value range: {0b=Rx (i.e. UL), 1b=Tx (i.e. DL)}. Type: binary bit. Field length: 1 bit. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.2 payloadVersion (payload version) | Description: This parameter defines the payload protocol version valid for the following IEs in the application layer. In this version of the specification payloadVersion=001b shall be used. Value range: {000b-111b=Payload version}. Type: unsigned integer. Field length: 3 bits. Default Value: 001b (version 1 assumed). ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.3 filterIndex (filter index) | Description: This parameter defines an index to the channel filter to be used between IQ data and air interface, both in DL and UL. For most physical channels filterIndex =0000b is used which indexes the standard channel filter, e.g. 100MHz channel filter for 100MHz nominal carrier bandwidth. Another use case is PRACH ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.4 frameId (frame identifier) | Description: This parameter is a counter for 10 ms frames (wrapping period 2.56 seconds), specifically frameId = frame number modulo 256. Value range: {0000 0000b-1111 1111b}. Type: unsigned integer. Field length: 8 bits. ETSI ETSI TS 103 859 V7.0.2 (2022-09) 94 |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.5 subframeId (subframe identifier) | Description: This parameter is a counter for 1 ms sub-frames within 10ms frame. Value range: {0000b-1111b}. Type: unsigned integer. Field length: 4 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.6 slotId (slot identifier) | Description: This parameter is the slot number within a 1ms sub-frame. All slots in one sub-frame are counted by this parameter, slotId running from 0 to Nslot-1. In this version of the specification the maximum Nslot=16, All other values of the 6 bits are reserved for future use. Value range: {00 0000b-00 1111b=slotID... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.7 startSymbolid (start symbol identifier) | Description: This parameter identifies the symbol number (within a slot) of the earliest symbol, to which the information of this message is applicable. Value range: {00 0000b-11 1111b}. Type: unsigned integer. Field length: 6 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.8 numberOfsections (number of sections) | Description: This parameter indicates the number of data section descriptions (separate citations of section ID even for multiple citations of the same sectionId) included in this C-Plane message. Value range: {0000 0000b-1111 1111b}. Type: unsigned integer. Field length: 8 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.9 sectionType (Section Type) | Description: This parameter determines the characteristics of U-plane data to be transferred or received from a beam with one pattern id. Value range: {0000 0000b-1111 1111b=Section Type, see table at the start of this clause for Section Type meanings} Type: unsigned integer. Field length: 8 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.10 udCompHdr (user data compression header) | See clause 8.3.3.13 for the description of this parameter. The udCompHdr information is provided on the U-Plane, instructing the O-RU (on DL) and O-DU (on UL) how to interpret and decompress the received U-Plane data. However, the O-RU is not expected to decide by itself the best UL data format and data compression met... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.11 numberOfUEs (number Of UEs) | Description: This parameter applies to Section Type 6 messages and indicates the number of UEs (for which channel information is provided) are included in the message. This allows the parser to determine when the last UE’s data has been parsed. Value range: {0000 0000b-1111 1111b}. Type: unsigned integer. Field length:... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.12 timeOffset (time offset) | Description: This parameter defines the time_offset from the start of the slot to the start of the Cyclic Prefix (CP) in number of samples Ts (=1/30.72MHz as specified in 3GPP TS38.211 clause 4.1). The value shall be less than the slot length. The slot length is based on the SCS on which the startSymbolId numerology is... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.13 frameStructure (frame structure) | Description: This parameter defines the frame structure. The first 4 bits define the FFT/iFFT size being used for all IQ data processing related to this message. The second 4 bits define the sub carrier spacing as well as the number of slots per 1ms sub-frame according to 3GPP TS 38.211, taking for completeness also 3G... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.4.14 cpLength (cyclic prefix length) | Description: This parameter defines the length CP_length of the Cyclic Prefix (CP) as follows, based on Ts (=1/30.72MHz as specified in 3GPP TS38.211 clause 4.1): CP_length = cpLength * Ts NOTE: cpLength parameter is used with Section Types 0 and 3, and is applicable to all symbols addressed by the C- plane message. In... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.1 sectionId (section identifier) | Description: If C-Plane and U-Plane coupling via sectionId (see clause 7.4.1.2.1) is used then this parameter identifies individual data sections that are described by data section descriptions within the C-Plane message. The purpose of the sectionId is to map U-Plane data sections to the corresponding C-Plane message ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.2 rb (resource block indicator) | Description: This parameter is used to indicate if every RB is used or every other RB is used. The starting RB is defined by startPrbc and total number of used RBs is defined by numPrbc. Example: RB=1, startPrb=1, numPrb=3, then the PRBs used are 1, 3, and 5. If numPrbc=0 (i.e., all PRBs), then the sending node shall s... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.3 symInc (symbol number increment command) | Description: If the section description does not include Section Extension #6, #12 and #19, this parameter is used to indicate which symbol number is relevant to the given section description. If the section description includes Section ETSI ETSI TS 103 859 V7.0.2 (2022-09) 98 Extension #6, #12 or #19 then set of symbo... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.4 startPrbc (starting PRB of data section description) | Description: In absence of Section Extensions #6, #12 and #13 in the section description, startPrbc parameter conveys the first (lowest frequency) PRB described by the section description. The interpretation of startPrbc is affected by presence of Section Extensions #6, #12 and #13; see clause 7.4.7.6, 7.4.7.12 and 7.4... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.5 reMask (resource element mask) | Description: This parameter defines the Resource Element (RE) mask within a PRB. Each bit setting in the reMask indicates if the section control is applicable to the RE sent in U-Plane messages (0=not applicable; 1=applicable). MSB indicates the value for the RE of the lowest frequency in a PRB. Note that different REs... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.6 numPrbc (number of contiguous PRBs per data section description) | Description: In absence of Section Extensions #6, #12 and #13 in the section description, the numPrbc parameter conveys the number of PRBs described by the section description. The interpretation of numPrbc is affected by presence of Section Extensions #6, #12 and #13; see clause 7.4.7.6, 7.4.7.12 and 7.4.7.13 for more... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.7 numSymbol (number of symbols) | Description: In section description without Section Extension #6, #12 and #19, this parameter defines number of symbols, or number of PRACH repetitions in the case of PRACH, to which the section control is applicable. At minimum, the section control shall be applicable to at least one symbol. However, possible optimiza... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.8 ef (extension flag) | Description: This parameter is used to indicate if this section has any Section Extensions as described in clause 7.4.6 included in the message Value range: {0b=no Section Extensions; 1b=one or more Section Extensions are included in this section}. Type: binary bit. Field length: 1 bit. Default Value: 0b (no Section Ex... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.9 beamId (beam identifier) | Description: This parameter defines the beam pattern to be applied to the U-Plane data. beamId = 0 means no beamforming operation will be performed. No beamforming operation implies that the RU shall not apply any phase or amplitude weights to the U-plane data and that the resulting RF signal will be applied to all ant... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.10 ueId (UE identifier) | Description: This parameter provides a label for the UE for which the section contents apply. This is used to support channel information sending from the O-DU to the O-RU. This is just a label and the specific value has no meaning regarding types of UEs that may be supported within the system. Value range: {000 0000 0... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.11 freqOffset (frequency offset) | Description: This parameter defines the frequency offset with respect to the carrier center frequency before additional filtering (e.g. for PRACH) and FFT processing (in UL) in steps of one half the subcarrier spacings Δf. The frequency offset shall be consistent per data section (one cannot use reMask to allow differe... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.12 regularizationFactor (regularization Factor) | Description: This parameter provides a signed value to support MMSE operation within the O-RU when beamforming weights are supported in the O-RU, so related to Section Type 6. Value range: {0000 0000 0000 0000b-1111 1111 1111 1111b} Type: unsigned integer. Field length: 16 bits. ETSI ETSI TS 103 859 V7.0.2 (2022-09) 10... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.13 ciIsample, ciQsample (channel information I and Q values) | Description: These values are the channel information complex values relayed from the O-DU to the O-RU, related to Section Type 6. The order of transmission is first Prbc for the first antenna to the last antenna, then second Prbc for the first to last antenna, and so on until reaching the last Prbc for the first to la... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.14 laaMsgType (LAA message type) | Description: This parameter defines the LAA message type being conveyed within the Section Type 7 C-Plane message. Note that here the C-Plane messages may flow from the O-DU to the O-RU (as usual) or from the O-RU to the O-DU. All of these messages relate to the listen-before-talk (LBT) LAA operation and provide a “han... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.15 laaMsgLen (LAA message length) | Description: This parameter defines number of 32-bit words in the LAA section, where “1” means one 32-bit word, “2” means 2 32-bit words, etc. – including the word containing the lssMsgLen parameter. Zero is a reserved value. Value range: {0001b-1111b=number of 32-bit words in the section from 1 to 16 words (4 to 64 by... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.16 lbtHandle | Description: This parameter provides a label that is included in the configuration request message (e.g., LBT_PDSCH_REQ, LBT_DRS_REQ) transmitted from the O-DU to the O-RU and returned in the corresponding response message (e.g., LBT_PDSCH_RSP, LBT_DRS_RSP). Value range: {0000 0000 0000 0000b-1111 1111 1111 1111b} ETSI... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.17 lbtDeferFactor (listen-before-talk defer factor) | Description: Defer factor in sensing slots as described in 3GPP TS 36.213 [14] clause 15.1.1. This parameter is used for LBT CAT 4 and can take one of three values: {1,3, 7} based on the priority class. Four priority classes are defined in 3GPP TS 36.213 [14]. Value range: {001b, 011b, 111b} or {1, 3, 7} in decimal Typ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.18 lbtBackoffCounter (listen-before-talk backoff counter) | Description: LBT backoff counter in sensing slots as described in 3GPP TS 36.213 [14] clause 15.1.1. Value range: {00 0000 0000b – 11 1111 1111b} (0-1023 decimal) Type: unsigned integer Field length: 10 bits |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.19 lbtOffset (listen-before-talk offset) | Description: LBT start time in microseconds from the beginning of the subframe scheduled by this message Value range: {00 0000 0000b – 11 1110 0111b} or {0 – 999} in decimal Type: unsigned integer Field length: 10 bits |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.20 MCOT (maximum channel occupancy time) | Description: LTE TXOP duration in subframes as described in 3GPP TS 36.213 [14] clause 15.1.1. The maximum values for this parameter are {2, 3, 8, 10} based on the priority class. Four priority classes are defined in 3GPP TS 36.213 [14]. Value range: {1-10} in decimal Type: unsigned integer Field length: 4 bits |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.21 lbtMode (LBT Mode) | Description: Part of multi-carrier support. Indicates whether full LBT process is carried or partial LBT process is carried (multi carrier mode B according to 3GPP TS 36.213 [14] clause 15.1.5.2). 00b = full LBT (regular LBT, sending reservation signal until the beginning of the SF/slot) 01b = Partial LBT (looking back... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.22 lbtPdschRes (LBT PDSCH Result) | Description: LBT result of SFN/SF o 00b = not sensing – indicates that the O-RU is transmitting data o 01b = currently sensing – indicates the O-RU has not yet acquired the channel o 10b = success – indicates that the channel was successfully acquired o 11b = Failure – indicates expiration of the LBT timer. The LBT pro... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.23 sfStatus (subframe status) | Description: indicates whether the subframe was dropped or transmitted o 0 – subframe was dropped o 1 – subframe was transmitted Value range: {0,1} Type: binary bit Field length: 1 bit |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.24 lbtDrsRes (LBT DRS Result) | Description: LBT result of SFN/SF o 0 – SUCCESS – indicates that DRS is sent o 1 – FAILURE – indicates that DRS is not sent Value range: {0,1} Type: binary bit Field length: 1 bit |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.25 initialPartialSF (Initial partial SF) | Description: Indicates whether the initial SF in the LBT process is full or partial. o 0 – full SF (two slots, 14 symbols) o 1 – partial SF (only second slot, last 7 symbols) Value range: {0, 1} Type: binary bit Field length: 1 bit |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.26 lbtBufErr (LBT Buffer Error) | Description: Indicates when an LBT buffer overflow has occurred. o 0 – reserved ETSI ETSI TS 103 859 V7.0.2 (2022-09) 105 o 1 – buffer overflow – data received at O-RU is larger than the available buffer size Value range: {0, 1} Type: binary bit |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.27 sfnSf (SFN/SF End) | Description: SFN/SF which is dropped by O-RU because of time expired or successfully transmitted Value range: SFN: {0000 0000b – 1111 1111b} or {0 – 255} in decimal, SF: {0000b – 1001b} or {0 – 9} in decimal Type: unsigned integer Field length: 12 bits |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.28 lbtCWConfig_H (HARQ Parameters for Congestion Window management) | Description: Total number of HARQ NACK feedback messages received for the lbtCWConfig_T transport blocks transmitted over LAA cell(s)to be used for adjusting the Congestion Window. Value range: {0000 0000b – 1111 1111b} or {0 – 255} in decimal Type: unsigned integer Field length: 8 bits |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.29 lbtCWConfig_T (TB Parameters for Congestion Window management) | Description: Total number of Transport Blocks (TB) transmitted over the LAA cell to be used for adjusting the Congestion Window. Value range: {0000 0000b – 1111 1111b} or {0 – 255} in decimal Type: unsigned integer Field length: 8 bits |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.30 lbtTrafficClass (Traffic class priority for Congestion Window management) | Description: Channel access priority class as defined in TS 36.213 [14] Value range: {000 - 111} or {0 - 7} in decimal 1 - 4: traffic class priority 0, 5 - 7: reserved Type: unsigned integer Field length: 3 bits |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.31 lbtCWR_Rst (Notification about packet reception successful or not) | Description: Notifies to O-DU whether the O-RU receives LBT_CWCONFIG_REQ message successfully or not o 0 – SUCCESS – indicates successful reception of LBT_CWCONFIG_REQ o 1 – FAILURE – indicates failure of receiving LBT_CWCONFIG_REQ Value range: {0, 1} Type: binary bit ETSI ETSI TS 103 859 V7.0.2 (2022-09) 106 Field len... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.5.32 reserved (reserved for future use) | Description: This parameter is reserved for future use. Transmitter shall send value “0”, while receiver shall ignore the value received. Value range: {variable}. Type: variable. Field length: variable. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.6 Section Extension Commands | The following Section Extension parameters are defined within the C-Plane: Table 7-14: Section Extension Commands extType meaning extLen extension parameters octets meaning 0 reserved 1 (1 word) reserved reserved 1 1 for future use for future use 1 beamforming weights var bfwCompHdr bfwCompParam bfwI (for TRX 0) bfwQ (... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.6.1 extType (extension type) | Description: This parameter provides the extension type which provides additional parameters specific to the subject data extension. An O-RU or O-DU receiving a “reserved” Section Extension shall ignore the extension and all parameters contained within it. ETSI ETSI TS 103 859 V7.0.2 (2022-09) 109 Value range: {all zer... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.6.2 ef (extension flag) | Description: This parameter is used to indicate if there is another extension present (ef=1) or this is the last extension ef=0) Value range: {0b=no more extensions; 1b=one or more extensions are included after this one}. Type: binary bit. Field length: 1 bit. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.6.3 extLen (extension length) | Description: This parameter provides the length of the Section Extension in units of 32-bit (or 4-byte) words. The value zero is reserved, so there is always at least one word in the extension (the word containing the extType and extLen). Value range: {all zeros – all ones} – from one word to 255 words (8 bits) or 6553... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.1 ExtType=1: Beamforming Weights Extension Type | This section applies to the sending of beamforming weights from the O-DU to the O-RU. When this is done, the weights are sent along with a beamID which is meant to allow those same weights to be used in future C-Plane messages by invoking the same beamID (without the need to send the weights again). This allows downloa... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.1.1 bfwCompHdr (beamforming weight compression header) | Description: This parameter defines the compression method and IQ bit width for the beamforming weights in the specific section in the C-Plane message. In this way each set of weights may employ a separate compression method. ETSI ETSI TS 103 859 V7.0.2 (2022-09) 110 Note that for the block compression methods, the blo... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.1.2 bfwCompParam (beamforming weight compression parameter) | Description: This parameter applies to the compression method specified by the associated bfwCompMeth value. Value range: {0000 0000b-1111 1111b}. Bit allocations bfwCompMeth 0 (msb) 1 2 3 4 5 6 7 (lsb) compParam size 0000b = no compression absent 0 octets 0001b = block fl. point reserved (set to all zeros) Exponent (u... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.1.3 bfwI (beamforming weight in-phase value) | Description: This parameter is the In-phase beamforming weight value. Refer to Annex D.1 for details on the usual weight byte order. When optional “little endian byte order” is chosen via M-plane, refer to Annex D.2 for details on byte order. The total number of weights in the section is O-RU-specific and is conveyed f... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.1.4 bfwQ (beamforming weight quadrature value) | Description: This parameter is the Quadrature beamforming weight value. Refer to Annex D.1 for details on the usual weight byte order. When optional “little endian byte order” is chosen via M-plane, refer to Annex D.2 for detail on byte order. The total number of weights in the section is O-RU-specific and is conveyed ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2 ExtType=2: Beamforming Attributes Extension Type | This Section Extension applies only to Section Types 1 and 3. Section Extension 2 applies to the sending of beamforming attributes from the O-DU to the O-RU which is described in Annex J. The following table shows the format of this Section Extension. Table 7-18 : Extension Type 2 Data Format ef extType = 0x02 1 Octet ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.1 bfaCompHdr (beamforming attributes compression header) | Description: This parameter defines the bit width for the beamforming attributes extension parameters. In this way each set of beamforming attributes may employ a different bit width. Value range: {0000 0000 0000b-1111 1111 1111b} Bit allocations ETSI ETSI TS 103 859 V7.0.2 (2022-09) 112 0 (msb) 1 2 3 4 5 6 7 (lsb) Num... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.2 bfAzPt (beamforming azimuth pointing parameter) | Description: This parameter is the azimuth beamforming pointing angle in degrees. The valid range of values is O-RU- specific and is conveyed from the O-RU to the O-DU as part of the initialization procedure via the M-Plane. Value range: {all zeros – all ones}. Type: signed integer. Field length: 0-8 bits. ETSI ETSI TS... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.3 bfZePt (beamforming zenith pointing parameter) | Description: This parameter is the zenith beamforming pointing angle in degrees. The valid range of values is O-RU- specific and is conveyed from the O-RU to the O-DU as part of the initialization procedure via the M-Plane. Value range: {all zeros – all ones}. Type: unsigned integer. Field length: 0-8 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.4 bfAz3dd (beamforming azimuth beamwidth parameter) | Description: This parameter is the azimuth beamforming beamwidth in degrees. The valid range of values is O-RU- specific and is conveyed from the O-RU to the O-DU as part of the initialization procedure via the M-Plane. The value (000b) corresponds to the minimum valid beamwidth. Value range: {all zeros – all ones}. Ty... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.5 bfZe3dd (beamforming zenith beamwidth parameter) | Description: This parameter is the zenith beamforming beamwidth in degrees. The valid range of values is O-RU- specific and is conveyed from the O-RU to the O-DU as part of the initialization procedure via the M-Plane. The value (000b) corresponds to the minimum valid beamwidth. Value range: {all zeros – all ones}. Typ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.6 bfAzSl (beamforming azimuth sidelobe parameter) | Description: This parameter is the azimuth beamforming sidelobe suppression value in dB. The valid range of values is O-RU-specific and is conveyed from the O-RU to the O-DU as part of the initialization procedure via the M-Plane. The value of bfAzSl corresponds to a value of 10 dB for all zeros and increments in 5 dB ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.7 bfZeSl (beamforming zenith sidelobe parameter) | Description: This parameter is the zenith beamforming sidelobe suppression value in dB. The valid range of values is O-RU-specific and is conveyed from the O-RU to the O-DU as part of the initialization procedure via the M-Plane. The value of bfZeSl corresponds to a value of 10 dB for all zeros and increments in 5 dB s... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.2.8 zero-padding | Description: This parameter is intended to pad out the data to the next 4-byte boundary. Because the preceding parameters are of varying bitwidth, extra padding in most cases will be needed to achieve the 4-byte boundary condition. Transmitter shall send value “0”, while receiver shall ignore the value received. Value ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3 ExtType=3: DL Precoding Extension Type | This Section Extension applies only to Section Types 1 and 3 and is to be used only for LTE TM2, TM3 and TM4. For other LTE transmission modes and for NR, precoding is assumed to be included in the beamforming operation (that is, encoded in the beamforming weights). The following table shows the format of this Section ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.1 codebookIndex (precoder codebook used for transmission) | Description: This parameter defines the indices of the precoder codebook that are used for precoding. It is to be used in conjunction with the numLayers field. (Invalid for TM1, TM2 and TM3) Value range: {0000 0000b - 1111 1111b}. Type: unsigned integer. Field length: 8 bits. DefaultValue: 0000 0000b (used for invalid ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.2 layerID (Layer ID for DL transmission) | Description: This parameter defines the layer ID that are used for DL transmission in TM1 – TM4. Value range: {0000b-1111b}. 0000b implies layer0, 0001b implies layer1, 0010b implies layer2, 0011b implies layer3. (for TxD, set to all ones) Type: unsigned integer. Field length: 4 bits. DefaultValue: 1111b (used for TxD ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.3 txScheme (transmission scheme) | Description: This parameter defines the TM scheme used in this Section Type. Value range: {0000b-1111b} txScheme TM scheme 0000b Spatial multiplexing (CDD) 0001b Spatial multiplexing (no CDD) 0010b Transmit diversity 0011b-111b Reserved Type: unsigned integer. Field length: 4 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.4 numLayers (number of layers used for DL transmission) | Description: This parameter defines the number of layers that are used for DL transmission in TM1 – TM6. Value range: {0000b-1111b}. 0000b implies 1 layer, 0001 implies 2 layers, 0010 implies 3 layers, 0011b implies 4 layers, Type: unsigned integer. ETSI ETSI TS 103 859 V7.0.2 (2022-09) 116 Field length: 4 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.5 crsReMask (CRS resource element mask) | Description: This parameter defines the CRS Resource Element (RE) mask within a PRB. Each bit setting in the crsReMask indicates if the section control is applicable to the RE sent in U-Plane messages (0=not applicable, 1=applicable). MSB indicates the value for the RE of the lowest frequency in a PRB. Value range: {00... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.6 crsSymNum (CRS symbol number indication) | Description: This parameter defines the CRS symbol number within a PRB. The value of the crsSymNum index indicates the symbol number to the RE sent in U-Plane messages (0=not applicable, 1=applicable) Value range: {0000b-1111b}, value indicates symbol number. 0000b – 1101b : use symbol number 0 – 13 respectively; 1110b... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.7 crsShift (crsShift used for DL transmission) | Description: This parameter indicates the shift pattern to pick up the right index for CRS positions for N Antennas (see Figure I-8) Value range: 0 or 1, implying shift patterns that are layer-dependent according to the table below (see Tables I-1 through I-3 for vShift) 1 Layer 2 Layers 4 Layers crsShift =0 for 0 ≤ vs... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.8 beamIdAP1 (beam id to be used for antenna port 1) | Description: This parameter defines the beam pattern to be applied to the U-Plane data. beamId = 0 means no beamforming operation will be performed. No beamforming operation implies that the RU shall not apply any phase or amplitude weights to the U-plane data and that the resulting RF signal will be applied to all ant... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.9 beamIdAP2 (beam id to be used for antenna port 2) | Description: This parameter defines the beam pattern to be applied to the U-Plane data. beamId = 0 means no beamforming operation will be performed. No beamforming operation implies that the RU shall not apply any phase or amplitude weights to the U-plane data and that the resulting RF signal will be applied to all ant... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.3.10 beamIdAP3 (beam id to be used for antenna port 3) | Description: This parameter defines the beam pattern to be applied to the U-Plane data. beamId = 0 means no beamforming operation will be performed. No beamforming operation implies that the RU shall not apply any phase or amplitude weights to the U-plane data and that the resulting RF signal will be applied to all ant... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.