hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.4 ExtType=4: Modulation Compression Parameters Extension Type | This Section Extension applies only to Section Types 1, 3 and 5. Section Extension 4 enables the O-DU to convey one set of “csf and modCompScaler values” to the O-RU which is needed for modulation compression described in Annex A.5. Table 7-25 shows the Section Extension format. Table 7-25: Section Format for Section E... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.4.1 csf (constellation shift flag) | Description: This binary flag indicates whether to shift the constellation (csf=1) or not (csf=0). “Shift” means subtract from (during compression) or add to (during decompression) the I and Q samples the value 2-udIqWidth where “udIqWidth” is the number of I and Q bits in the U-Plane representation. Table 7-26:Constel... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.4.2 modCompScaler (modulation compression scaler value) | Description: This parameter is the scale factor to apply to the unshifted constellation points during decompression. It is a fractional floating-point value having an unsigned but negative 4-bit exponent and an unsigned fractional 11-bit mantissa. Value range: { 0 through +(1-2-11 ) }. Type: unsigned fractional floatin... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.5 ExtType=5: Modulation Compression Additional Parameters Extension Type | This Section Extension applies only to Section Types 1, 3 and 5. Section Extension #5 enables the O-DU to convey one (or more) set(s) of “mcScaleReMask, csf and mcScaleOffset values” to the O-RU which is needed for modulation compression described in Annex A.5. Table 7-27 and Table 7-28 shows the Section Extension form... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.5.1 mcScaleReMask (modulation compression power scale RE mask) | Description: This parameter defines the Resource Element (RE) mask to indicate the position of RE with same scaling and modulation type within a PRB. Each bit setting in the mcScaleReMask indicates if the mcScaleOffset and csf fields are applicable to the RE sent in U-Plane messages or not (0=not applicable; 1=applicab... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.5.2 csf (constellation shift flag) | Description: refer to clause 7.4.7.4.1 |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.5.3 mcScaleOffset (scaling value for modulation compression) | Description: This parameter is the scale factor to apply to the unshifted constellation points during decompression. It is a fractional floating-point value having an unsigned but negative 4-bit exponent and an unsigned fractional 11-bit mantissa. Value range: {0 through +(1-2-11 ) }. Type: unsigned integer. " "... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.6 ExtType=6: Non-contiguous PRB allocation in time and frequency domain | This Section Extension applies only to Section Types 1, 3 and 5. This Section Extension enables allocation of non-contiguous sets of PRBs (Resource Block Groups, or RBGs) in frequency and time domain. This will reduce significantly the C-Plane overhead when users or channels are allocated with non-contiguous sets of PR... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.6.1 rbgSize (resource block group size) | Description: This parameter indicates the size in number of PRBs of the resource block groups allocated by the bit mask. The size of the resource block group to be used by the application shall be taken from the mapping table given in the Value range field in the rbgMask description below. See rbgMask for special handl... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.6.2 rbgMask (resource block group bit mask) | Description: This parameter is a bit mask where each bit indicates whether a corresponding resource block group is allocated. If bit n in the mask is set, then the resource block group n is allocated where n can take values in range [0, lastRbgid] where lastRbgid = ceiling( (numPrbc + (startPrbc mod rbgSize))/ rbgSize ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.6.3 symbolMask (symbol bit mask) | Description: This parameter is a bit mask where each bit indicates whether the rbgMask applies to a given symbol in the slot. If bit n is set then the rbgMask is applied to symbol n, where n has range [0..13]. If no bits are set this implies the rbgMask may be applied to no RBGs in the slot, in other words there are no... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.6.4 priority | Description: This parameter is used in conjunction with C-Plane and U-Plane coupling via frequency and time with priorities (see clause 7.4.1.2.3). If this coupling method is not used (e.g. O-RU or O-DU do not have corresponding capability) sender shall send value zero. This parameter is used by O-RU to find the sectio... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.6.5 repetition (repetition flag) | Description: This parameter is used to indicate repetition of a highest priority data section inside a C-Plane message. This is an optional field for O-RU i.e., the O-DU shall populate this flag, however, O-RU can choose to process or ignore this flag. This field is applicable only when extension type 6 and extension t... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.7 ExtType=7: eAxC Mask Section Extension | This Section Extension is meant to allow a specific C-Plane message to apply not to just a single eAxC value but to multiple eAxC values. The intended use case applies to Section Type 0, wherein the intention is to allow blanking (designated by Section Type 0) to be indicated for multiple eAxC values e.g., all componen... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.7.1 eAxCmask (eAxC Mask) | Description: This binary mask indicates which eAxC values the C-Plane message applies to. A “0” bit in the mask means the specified eAxC bit is “don’t care” while a “1” bit in the mask means the specified eAxC bit should be considered. An all-zero eAxCmask means “use this message for all eAxC values” while an all-ones ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.8 ExtType=8: Regularization factor | This Section Extension is for regularizationFactor which is used to generate MU beamforming weight for the scheduled UEs in a slot. regularizationFactor is the noise variance used for MMSE (Minimum Mean Square Error) computation of generating MU BFW. The intended use case applies to Section Type 5 for sending regulariz... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.8.1 regularizationFactor (regularization Factor) | Description: This parameter provides a regularization factor to support MMSE operation when UE is scheduled, so related to Section Type 5. Value range: {0000 0000 0000 0000b-1111 1111 1111 1111b} Type: unsigned integer. Field length: 16 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.9 ExtType=9: Dynamic Spectrum Sharing parameters | This Section Extension applies to all Section Types. The following table shows the format of this Section Extension. Table 7-33 : Section Format for Section Extension 9 (DSS parameter) ef extType = 0x09 1 Octet N extLen = 0x01 (1 word) 1 N+1 technology[7:0] 1 N+2 reserved 1 N+3 This Section Extension is needed to suppo... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.9.1 technology (interface name) | Description: This parameter indicates if the data transmitted through eCPRI interface is LTE or NR in real time. In this way, O-RU knows the data format transmitted from O-DU and could decode the associated user data. Value range: {0000 0000b-1111 1111b} : • 0000 0000b : LTE support • 0000 0001b : NR support • 0000 001... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.10 ExtType=10: Section description for group configuration of multiple ports | This Section Extension applies to Section Types 1, 3 and 5. C-plane section information for the multiple ports (i.e., layers or Tx/Rx paths) may be the same except beam IDs or UE IDs in most cell scheduling case. When the multiple ports share the common section information within O-RU, C-plane sections to be sent via t... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.10.1 beamGroupType | Description: This parameter indicates the type of beam grouping. Value range: {00b - 11b}. • 00b (common beam): the beamID in the section header is used as a common beam ID for all the ‘numPortc’ ports which are grouped by M-plane. This type is not used for Section Type 5, and extLen = 0x01. • 01b (beam matrix indicati... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.10.2 numPortc | Description: This parameter indicates the number of eAxC ports indicated by the Section Extension. It can cover up to 64 ports. Value range: {000000b-111111b}. 00 0000b expresses 64 ports. Type: unsigned integer. Field length: 6 bits. Default Value: 000000b. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.10.3 Interaction with other Section Extensions | Section Extension =10 can be used in all situations when same information is present in section headers and in Section Extension headers across multiple eAxC IDs. Table 7-36 : Section Extension =10 Interactions with other Section Extensions Section Extension Title Interaction with existing Section Extensions 1 Beamform... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.11 ExtType=11: Flexible Beamforming Weights Extension Type | This section applies to the flexible sending of beamforming weights from the O-DU to the O-RU. This enables the O- DU to provide different beamforming weights for different PRBs within one section to facilitate, e.g. zero-forcing precoding. The O-DU provides the numBundPrb parameter, which informs the O-RU how many PRB... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.11.1 bfwCompHdr (beamforming weight compression header) | Description: refer to clause 7.4.7.1.1 Note that this parameter defines the compression method and IQ bit width for the beamforming weights in the specific section in the C-Plane message. For the block compression methods, the block size is the vector of beamforming weights for a specific PRB bundle. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.11.2 bfwCompParam for PRB bundle x (beamforming weight compression parameter) | Description: refer to clause 7.4.7.1.2 Note that this parameter applies to the following vector of beamforming weights for a specific PRB bundle (i.e., bundle x). |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.11.3 numBundPrb (Number of bundled PRBs per beamforming weights) | Description: This parameter is the number of bundled PRBs per beamforming weight sets. The number of beamforming weight sets per TRX in Section Extension 11 should be equal to the total number of PRBs selected by section description in the C-plane message (using startPrbc and numPrbc and other parameters present in oth... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.11.4 bfwI (beamforming weight in-phase value) | Description: This parameter is the In-phase beamforming weight value. The total number of weights in the section depends on the number TRX at the RU and the number of bundled PRBs per beamforming weight Value range: {all zeros – all ones}. Type: signed integer. Field length: 1-16 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.11.5 bfwQ (beamforming weight quadrature value) | Description: This parameter is the Quadrature beamforming weight value. The total number of weights in the section depends on the number TRX at the RU and the number of bundled PRBs per beamforming weight Value range: {all zeros – all ones}. Type: signed integer. Field length: 1-16 bits. 7.4.7.11.6 disableBFWs (disable... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.11.7 RAD (Reset After PRB Discontinuity) | Description: This parameter is used when Section Extension =11 is used in conjunction with Section Extension allowing non-contiguous frequency allocation (Section Extensions =6, 12 and 13). In regular cases, where the section parameters refer to a continuous set of PRBs, the default value should be used, which is RAD =... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.12 ExtType=12: Non-Contiguous PRB Allocation with Frequency Ranges | This Section Extension applies only to Section Types 1, 3 and 5. It cannot be used with Section Extension 6 in the same section description. This Section Extension enables allocation of non-contiguous sets of PRBs (Resource Block Groups, or RBGs) in time domain and frequency domain. This extension reduces the C-Plane o... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.12.1 priority (priority of section description) | Description: This parameter has same format and semantics as priority parameter in Section Extension 6 (see clause 7.4.7.6.4). |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.12.2 symbolMask (symbol bit mask) | Description: This parameter has same format and semantics as symbolMask parameter in Section Extension 6 (see clause 7.4.7.6.3). ETSI ETSI TS 103 859 V7.0.2 (2022-09) 131 |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.12.3 offStartPrb(r) (offset of PRB range start) | Description: This parameter indicates the offset to start of the r-th PRB range for r=1, …, R-1. Value range: 0 ... 255. Type: unsigned integer. Field length: 8 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.12.4 numPrb(r) (number of PRBs in PRB range) | Description: This parameter indicates the number of PRBs in the r-th PRB range for r=1, …, R-1. Value range: 0 ... 255. Type: unsigned integer. Field length: 8 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.13 ExtType=13: PRB Allocation with Frequency Hopping | This Section Extension applies only to Section Types 1, 3 and 5. This Section Extension allows to describe two or more PRB allocations starting at different symbols and different PRB. It is intended to be used for allocations with intra-slot frequency hopping. This extension significantly reduces the C- Plane overhead ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.13.1 nextSymbolId(n) (offset of PRB range start) | Description: This parameter indicates the symbol at which n-th frequency hop occurs for n=1, …, R-1. The value shall correspond to one of symbols addressed by the section description. Note that: • if Section Extension #6, #12 and #19 are not present in the section description then set of symbols addressed by the descri... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.13.2 nextStartPrbc(n) (number of PRBs in PRB range) | Description: This parameter indicates the value to be used instead of startPrbc for the n-th frequency hop for n=1, …, R-1. Sender shall set nextSymbolId(n) to value of nextSymbolId(n-1) and set nextStartPrbc(n) to value of nextStartPrbc(n-1) if pair (nextSymbolId(n), nextStartPrbc(n)) is used for padding. Value range:... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.14 ExtType= 14: Nulling-layer Info. for ueId-based beamforming | This Section Extension applies to Section Types 5. This enables the O-DU to provide layer-by-layer indication, which denotes that the corresponding ueId is for nulling-layer indication. The following table shows the format of this Section Extension. Table 7-41: Extension Type 14 ef extType = 0x0E 1 Octet N extLen = 0x0... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.14.1 nullLayerInd (null layer indication) | Description: This parameter indicates whether the corresponding layer is nulling-layer or not. Value range: {0000 0000b - 0000 0001b}. The following mapping shall be used: ETSI ETSI TS 103 859 V7.0.2 (2022-09) 133 0000 0000b = the corresponding ueId is given for actually scheduled layer, no specific operation based on ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.15 ExtType= 15: Mixed-numerology Info. for ueId-based beamforming | This Section Extension applies to Section Types 5 and 6. When this Section Extension is applied to Section Type 6, the value of FFT type in frameStructure and cpLength can be set as ‘0’. The following table shows the format of this Section Extension. Table 7-42: Extension Type 15 ef extType = 0x0F 1 Octet N extLen = 0x... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.15.1 frameSturcture (frame structure) | See clause 7.4.4.13 for the description of this parameter. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.15.2 freqOffset (frequency offset) | See clause 7.4.5.11 for the description of this parameter. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.15.3 cpLength (cyclic prefix length) | See clause 7.4.4.14 for the description of this parameter. 7.4.7.16 ExtType=16: Section description for antenna mapping in UE channel information based UL beamforming This Section Extension applies to Section Type 5. The Section Extension includes bitmask per Rx endpoint to indicate the antennas to be pre-combined into... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.16.1 antMask | Description: This parameter indicates the indices of antennas to be pre-combined per Rx endpoint. Value range: {0x0000 0000 0000 0000 – 0xFFFF FFFF FFFF FFFF}. Each bit indicates whether the antenna of the corresponding digit is pre-combined or not. The maximum number of antennas is 64. Type: unsigned integer. Field le... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.17 ExtType= 17: Section description for indication of user port group | This Section Extension applies to Section Extension 10 for beamGroupType=10b following Section Type 5 and cannot be used in standalone manner. This Section Extension provides the number ueIDs of the users scheduled in preceding Section Type and Section Extension messages. A user may have more than one ueIDs (i.e. more ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.17.1 numUeID | Description: This parameter indicates the number of ueIDs per user Value range: {0001b - 1000b}. {1001b - 1111b} are reserved. Type: unsigned integer. Field length: 4 bits. Default Value: 100b (4 ueIDs per user). ETSI ETSI TS 103 859 V7.0.2 (2022-09) 135 7.4.7.18 ExtType=18: Section description for Uplink Transmission ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.18.1 transmissionWindowOffset | Description: This parameter indicates the start of the transmission window as an offset to when the transmission window would have been without this parameter, i.e. (Ta3_max-Ta3_min). The resolution of the parameter is symbols, where the length in time of a symbol is either as determined via M-plane (when used with mes... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.18.2 transmissionWindowSize | Description: This parameter indicates the size of the transmission window in resolution µs. If window size is set to a value smaller than (ta3_max – ta3_min) the O-RU will if possible, transmit the requested data reliably during that window size. If not possible due to for instance lack of transmission capability on li... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.18.3 Type of Transmission (toT) | Description: This parameter indicates to the O-RU if the associated user plane data should be sent in normal transmission mode or be transmitted uniformly in time over the transmission window. The O-RU will indicate via the M-Plane if it supports the possibility to change the type of transmission. If the O-RU does not ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.18.4 Interaction with other Section Extensions | The Section Extension =18 is used when the UL traffic needs to be managed e.g., avoid peaks in the traffic on shared links between an O-DU and multiple O-RUs. The table below lists how Section Extension 18 is used in combination with other Section Extensions. Section Extension Title Interaction with section extension 1... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.19 ExtType=19: Section Compact multiple port beamforming information | This Section Extension applies to Section Types 1 and 3. This Section Extension is required for sending compact beamforming information for multiple antenna ports (the term ‘port’ used henceforth in context of this Section Extension refers to logical antenna port). CSI-RS channel will benefit the most from using this e... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20 ExtType=20: Puncturing Extension | This extension specifies the Puncturing Pattern to be applied to a section. This extension contains a common header with the number of puncturing patterns, followed by symbolMask, PRB ranges, puncReMask and optionally RBG mask fields for each puncturing pattern. O-RU shall process the fields of the puncturing pattern a... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.1 numPuncPatterns (number of puncturing pattern) | Description: This parameter is used to indicate total number of puncturing patterns contained within single instance of this extension. Value range: {000000b-111111b}. Type: unsigned integer. Field length: 8 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.2 symbolMask (puncturing pattern symbol mask) | Description: This parameter (also see clause 7.4.7.6.3 and 7.4.7.19.8) is a bitmask where each bit indicates the symbols associated with the puncturing pattern. A value of ‘1’ indicates that the symbol shall be considered for puncturing. A value of ‘0’ indicates the symbol need not be considered for puncturing. Value r... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.3 startPuncPrb (starting PRB to which one puncturing pattern applies) | Description: This parameter conveys the first PRB of the puncturing pattern. Value range: {00 0000 000b-11 1111 1111b}. Type: unsigned integer. Field length: 10 bits. 7.4.7.20.4 numPuncPrb (number of contiguous PRBs to which one puncturing pattern applies) Description: This parameter conveys the number of PRBs of the p... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.5 puncReMask (puncturing pattern RE mask) | Description: This parameter defines the Resource Element (RE) mask of the puncturing pattern within a PRB. Each bit in the puncReMask indicates the presence/absence of a puncturing RE within a PRB. MSB indicates the value for the RE of the lowest frequency in a PRB. Value range: {0000 0000 0001b-1111 1111 1111b}. Type:... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.6 rb (resource block indicator) | Description: refer to clause 7.4.5.2 Note: This shall not be applicable if rbgIncl flag is set to ‘1’ in this extension ETSI ETSI TS 103 859 V7.0.2 (2022-09) 143 |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.7 rbgIncl (rbg included flag) | Description: This parameter is used to indicate presence/absence of resource block group for the case of non- contiguous PRB allocation. If this flag is set to ‘0’, 2 fields following this parameter i.e. rbgSize and rbgMask are absent and vice versa. Value range: {0b=resource block group included; 1b=resource block gro... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.8 rbgSize (rbg size) | Description: refer to clause 7.4.7.6.1 |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.9 rbgMask (rbg bitmask) | Description: refer to clause 7.4.7.6.2 |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.4.7.20.9 Interaction with Other Extensions | Ext 20 is compatible with all other Extensions. Ext-20 is used to describe the puncturing information of other channels and their associated sections on top of the current section. Whereas, other extensions are used to describe the Beamforming and Scheduling information of the current section. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5 C-Plane Optimizations | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.1 C-Plane Optimization using Section Extension =6 | Section Extension =6 is used for non-contiguous PRB allocation in both time and frequency domains. This is realized by two bitmasks: symbolMask and rbgMask. The first allows to select an arbitrary subset of symbols within a slot. The second allows to select arbitrary subset of blocks of subcarriers (each block has 12*r... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.2 C-Plane Optimization using Section Extension =7 | Material to come. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.3 C-Plane Optimization using Section Extension =10 | In general, the O-DU uses unique eAxC ids to address each layer or spatial stream when sending C-plane and U-plane messages to the O-RU. In many situations, information contained in C-plane messages for the different spatial streams is the same or similar. For example, a SU MIMO allocation with 8 layers may have same v... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.4 C-Plane Optimization using Section Extension =11 | Section Extension =11 referes to flexible beamforming weight transmission. One way to transfer per-PRB beamforming weights is using Section Extension =1 and creating one section for each PRB. This introduces high overhead in the form of section headers and Section Extensions. The objective of Section Extension =11 is t... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.4.1 Interaction between Section Extension =11 and Section Extension =6 | Section Extension =6 is used for non-contiguous PRB allocation in both time and frequency domains. The main parameter in Section Extension =6 that is used to identify the PRB groups is rbgSize. On the other hand, numBundPrb is used in Section Extension =11 to identify the number of bundled PRBs that share the same beam... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.4.2 Interaction between Section Extension =11 and Section Extension =12 | Section Extension =12 is used for non-contiguous PRB allocation in both time and frequency domains. Section Extension =11 can be combined with Section Extension =12 in one section description in the same way as how Extension =11 may be combined with Section Extension =6. That is, description in clause 7.5.4.2 applies a... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.4.3 Interaction between Section Extension =11 and Section Extension =13 | Section Extension =13 is used for non-contiguous PRB allocation with frequency hopping. Section Extension =11 can be combined with Section Extension =12 in one section description in the same way as how Extension =11 may be combined with Section Extension =6. That is, description in clause 7.5.4.2 applies also to Secti... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.5 C-Plane Optimization using Section Extension =12 | The Section Extension =12 is useful for PRB allocation non-contiguous in time and frequency domains. The Section Extension =12 conveys priority, symbolMask and a variable size list of frequency ranges. For that is more space efficient than Section Extension =6 in scenarios where: PRB allocation is continuous in frequen... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.6 C-Plane Optimization using Section Extension =13 | The Section Extension =13 is useful for PRB allocation with intra-slot frequency hopping. The Section Extension =13 conveys a variable size list of pairs of parameters indicating a value to be used in place of startPrbc and a time instant (symbol number) starting from which the startPrbc shall be substituted. Size of S... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.7 Coupling via Frequency and Time with Priorities | This optimization uses the coupling mechanism described in 5.4.1.2.3 and allows the reduction of the number of section descriptions. The coupling mechanism with priorities allows to unambiguously describe beamforming configuration even if section descriptions overlap (i.e. refer to the same RE) provided they have diffe... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.7.1 Coupling via Frequency and Time with Priorities (Optimized) | This coupling method is an optimization over Coupling via Frequency and Time with Priorities to identify duplication of highest priority section description. When highest priority section descriptions are duplicated, it may cause O-RU to process the duplicated sections multiple times. Depending on the O-RU implementati... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.8 U-Plane Operation Without C-Plane | O-RU may support U-plane operation without C-plane. In general, this function can be used for channels with resource allocation known (at least approximately, see below) during eAxC activation (e.g. PRACH and SRS). If this function is enabled via M-Plane for given eAxC then for this eAxC C-plane is not used to provide ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.9 Modulation Compression with Section Extension 10 | Section Extension =10 is used for group configuration of multiple ports. Section Extension =4 and Section Extension =5 are used for modulation compression. Extension type 10 can be used together with extension type 4 or 5. When all parameter values of Section Extension 4 or 5 is same for all eAxC ids, append one single... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.5.11 Optimizations with ExtType=20 | This extension is like Coupling Via Frequency and Time with Priorities (see clause 7.4.1.2.3 and 7.5.7), but more efficient and more widely applicable. In that approach, if there is C-plane application layer packet fragmentation, each C-Plane message shall contain the highest priority section descriptions referring to ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.6 O-RUs per endpoint and per C-Plane message limits | This section is introduced to specify details of O-RU processing limits specified by per endpoint limits and per C-Plane limits. Whether one or both limits apply to the O-RU is based on the O-RUs processing architecture i.e. if the O-RU is endpoint processing based or has additional per C-Plane processing prior to endp... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.6.1 O-RU per endpoint processing limits | When O-RUs processing granularity is endpoint based i.e. processing resources in O-RU to handle CU-Plane messages are allocated per endpoint, certain limits may be imposed by the O-RU per endpoint e.g. endpoint-section-capacity, endpoint-beam-capacity, endpoint-prb-capacity. When such limits are imposed by the O-RU, th... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.6.2 O-RU C-Plane message limits | For O-RUs with per C-Plane message processing limits in addition to per endpoint processing limits, the O-RU can choose to advertise its limitations on a per C-Plane message basis. O-DU can choose to indicate that if it adheres to the associated limitations, otherwise the stated O-RU capacity may be compromised. The de... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8 U-plane Protocol | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1 General | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.1 U-plane Transport | Either eCPRI or IEEE 1914.3 is used as an encapsulation mechanism for the user-plane messages. Due to the nature of these messages (very strict delay constraints), it is assumed that message acknowledgements are not possible. Likewise, different data flows may be used for the User-Plane and Control-Plane messages. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.2 U-plane Data Compression | U-Plane IQ data, (both DL and UL) including user data, PRACH and control channels may be transmitted in compressed format. There are several envisioned compression methods including an “uncompressed” format. The method of compression is variable based on sectionId but is constant for every U-Plane data section referenc... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.3 Digital Power Scaling | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.3.1 Definition of IQ Power in dBFS | IQ power level in dBFS (dB full scale) is a logarithmic representation of the power level for an IQ sample carried over the digital interface. IQ power level in dBFS is proportional to logarithm of I²+Q²: IQ power level [dBFS] = 10·log10( I²+Q² ) - 10·log10(FS) = 10∙log10 (I2+Q2 ) - 10∙log10(FS0∙2-FS_Offset ) where -FS... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.3.2 Definition of Gain over Fronthaul Interface | The gain of an array defines the relation between the levels of a test signal seen at its input and output, also called digital power scaling. The gain of an array can be calculated from the gain of one element of the array while assuming all elements have same gain. Figure 8-1 depicts the gain relations between the di... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.3.2.1 DL Gain Guideline | The DL gain of a TX array carrier element shall be provided as part of the O-RU carrier set-up procedure. The configured (by the O-DU over the M-Plane) DL gain of a TX array carrier element (i.e. “TX array carrier element’’ refers to the TX array element serving the respective carrier configured on the respective TX ar... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.3.2.2 UL Gain Definition | The UL gain or scaling of an rx-array carrier element (i.e. ”rx-array carrier element’’ refers to the rx-array element serving the respective eAxC configured on the respective rx-array) is defined by mapping -152dBm at the assumed- lossless antenna port to the smallest power level an IQ sample can carry over the digita... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.1.3.3 TX Power Budget Guideline for Category A and Category B O-RUs | This clause describes a guideline for handling of power budget in a category A and category B O-RU. In general, care shall be taken to avoid exceeding the maximum rms power rating of a tx-array element. ETSI ETSI TS 103 859 V7.0.2 (2022-09) 164 In this clause, a,k is the maximum rms power rating (in W) of tx-array ele... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.2 Elementary Procedures | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.2.1 IQ Data Transfer procedure | This procedure (an alternative procedure IQ data transfer is described in clause 8.2.2) is used to transfer frequency domain IQ data samples between the O-DU and O-RU. Data is transmitted symbol by symbol as U-Plane messages. The data-associated control information is typically sent every slot (or for LTE, TTI) in a di... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3 Elements for the U-plane Protocol | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3.1 General | U-Plane messages are encapsulated using a two-layered header approach. The first layer consists of an eCPRI or IEEE 1914.3 common header, including fields used to indicate the message type, while the second layer is an application layer including necessary fields for control and synchronization. When the optional “litt... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3.2 DL/UL Data | A common frame format is used for U-Plane messages consisting of a transport layer and an application layer. The application layer is within the transport payload and consists of a common header for time reference, followed by information and parameters dependent and specific to the Section Type in use. Data from multi... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3.3 UL/DL Data Coding of Information Elements | See clause 5.1.3 for transport header information element details. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3.3.1 dataDirection (data direction (gNB Tx/Rx)) | See clause (7.4.4.1) |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3.3.2 payloadVersion (payload version) | See clause (7.4.4.2) |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3.3.3 filterIndex (filter index) | See clause (7.4.4.3) ETSI ETSI TS 103 859 V7.0.2 (2022-09) 170 |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 8.3.3.4 frameId (frame identifier) | See clause (7.4.4.4) frameId in U-plane message shall be set to the frameId value signaled in the corresponding C-plane message. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.