KR20240052619A - Electronic device and method for providing modulation compression information in fronthaul interface - Google Patents

Abstract

In embodiments, a method performed by a distributed unit (DU) in a wireless communication system may include identifying a subblock within one section. The method may include generating a control-plane (C-plane) message including section extension information including modulation compression information corresponding to the subblock. The method may include transmitting the C-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

Description

Electronic device and method for providing modulation compression information in a fronthaul interface {ELECTRONIC DEVICE AND METHOD FOR PROVIDING MODULATION COMPRESSION INFORMATION IN FRONTHAUL INTERFACE}

This disclosure relates to a fronthaul interface. More specifically, the present disclosure relates to an electronic device and method for providing modulation compression information in a fronthaul interface.

As transmission capacity increases in wireless communication systems, function split, which functionally separates base stations, is being applied. According to functional separation, the base station can be divided into a distributed unit (DU) and a radio unit (RU). A fronthaul interface is defined for communication between DUs and RUs.

In embodiments, a method performed by a distributed unit (DU) in a wireless communication system may include identifying a subblock within one section. The method may include generating a control-plane (C-plane) message including section extension information including modulation compression information corresponding to the subblock. The method may include transmitting the C-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

In embodiments, a method performed by a radio unit (RU) in a wireless communication system transmits a control-plane (C-plane) message including section extension information from a distributed unit (DU) through a fronthaul interface. It may include a receiving operation. The method may include an operation of identifying modulation compression information corresponding to a subblock within one section in the section extension information. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

In embodiments, an electronic device of a distributed unit (DU) in a wireless communication system may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to identify subblocks within one section. The at least one processor may be configured to generate a control-plane (C-plane) message including section extension information including modulation compression information corresponding to the subblock. The at least one processor may be configured to transmit the C-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

In embodiments, an electronic device of a radio unit (RU) in a wireless communication system may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to receive a control-plane (C-plane) message including section extension information from a distributed unit (DU) through a fronthaul interface. The at least one processor may be configured to identify modulation compression information corresponding to a subblock within one section in the section extension information. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

1 shows a wireless communication system according to embodiments.
2A shows a fronthaul interface according to embodiments.
FIG. 2B illustrates a fronthaul interface of an open (O)-radio access network (RAN) according to embodiments.
FIG. 3A shows the functional configuration of a distributed unit (DU) according to embodiments.
FIG. 3B shows the functional configuration of a radio unit (RU) according to embodiments.
Figure 4 shows an example of function split between DU and RU, according to embodiments.
5A-5B illustrate examples of modulation compression (MC), according to embodiments.
Figure 6 shows an example of signaling between DU and RU to provide modulation compression information for a subblock of a section, according to embodiments.
7A-7B show an example of a first way to divide a section, according to embodiments.
8A-8B show an example of a second method for dividing a section, according to embodiments.
9A-9B show an example of a third way to divide a section, according to embodiments.
Figure 10 shows an example of section division for periodic resource allocation, according to embodiments.
11 shows an example of modulation compression for a subblock, according to embodiments.
Figure 12 shows an example of signaling between DU and RU to provide compressed information using an identifier (ID), according to embodiments.

Terms used in the present disclosure are merely used to describe specific embodiments and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions, unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by a person of ordinary skill in the technical field described in this disclosure. Among the terms used in this disclosure, terms defined in general dictionaries may be interpreted to have the same or similar meaning as the meaning they have in the context of related technology, and unless clearly defined in this disclosure, have an ideal or excessively formal meaning. It is not interpreted as In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach method is explained as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, the various embodiments of the present disclosure do not exclude software-based approaches.

Terms referring to signals used in the following description (e.g., packet, message, signal, information, signaling), terms referring to resources (e.g., section, symbol, slot, subframe ( subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), opportunity), terms for computational states (e.g. phase ( step, operation, procedure), terms referring to data (e.g. packet, message, user stream, information, bit, symbol, codeword) , a term referring to a channel, a term referring to network entities (distributed unit (DU), radio unit (RU), central unit (CU), control plane (CU-CP), user plane (CU-UP) ), O-DU (O-RAN (open radio access network) DU), O-RU (O-RAN RU), O-CU (O-RAN CU), O-CU-UP (O-RAN CU-CP ), O-CU-CP (O-RAN CU-CP)), terms referring to device components, etc. are examples for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used. In addition, terms such as '... part', '... base', '... water', and '... body' used hereinafter mean at least one shape structure or a unit that processes a function. It can mean.

In addition, in the present disclosure, the expressions greater than or less than may be used to determine whether a specific condition is satisfied or fulfilled, but this is only a description for expressing an example, and the description of more or less may be used. It's not exclusion. Conditions written as ‘more than’ can be replaced with ‘more than’, conditions written as ‘less than’ can be replaced with ‘less than’, and conditions written as ‘more than and less than’ can be replaced with ‘greater than and less than’. In addition, hereinafter, 'A' to 'B' means at least one of the elements from A to (including A) and B (including B).

The present disclosure describes various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), extensible radio access network (xRAN), and open-radio access network (O-RAN)), This is only an example for explanation, and various embodiments of the present disclosure can be easily modified and applied to other communication systems.

1 shows a wireless communication system according to embodiments.

Referring to FIG. 1, FIG. 1 illustrates a base station 110 and a terminal 120 as some of the nodes that use a wireless channel in a wireless communication system. Although FIG. 1 shows only one base station, the wireless communication system may further include other base stations that are the same or similar to base station 110.

The base station 110 is a network infrastructure that provides wireless access to the terminal 120. The base station 110 has coverage defined based on the distance at which signals can be transmitted. In addition to the base station, the base station 110 includes 'access point (AP)', 'eNodeB (eNB)', '5G node (5th generation node)', and 'next generation nodeB'. , gNB)', 'wireless point', 'transmission/reception point (TRP)', or other terms with equivalent technical meaning.

The terminal 120 is a device used by a user and communicates with the base station 110 through a wireless channel. The link from the base station 110 to the terminal 120 is called downlink (DL), and the link from the terminal 120 to the base station 110 is called uplink (UL). Additionally, although not shown in FIG. 1, the terminal 120 and another terminal may communicate with each other through a wireless channel. At this time, the link between the terminal 120 and other terminals (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used interchangeably with the PC5 interface. In some other embodiments, terminal 120 may operate without user involvement. According to one embodiment, the terminal 120 is a device that performs machine type communication (MTC) and may not be carried by the user. Additionally, according to one embodiment, the terminal 120 may be a narrowband (NB)-internet of things (IoT) device.

In addition to the terminal, the terminal 120 includes 'user equipment (UE)', 'customer premises equipment (CPE)', 'mobile station', and 'subscriber station'. , may be referred to as a ‘remote terminal’, a ‘wireless terminal’, an electronic device’, or a ‘user device’ or other terms with equivalent technical meaning. .

The base station 110 may perform beamforming with the terminal 120. The base station 110 and the terminal 120 may transmit and receive wireless signals in a relatively low frequency band (e.g., FR 1 (frequency range 1) of NR). In addition, the base station 110 and the terminal 120 use relatively high frequency bands (e.g., FR 2 (or, FR 2-1, FR 2-2, FR 2-3), FR 3 in NR), millimeter waves ( It is possible to transmit and receive wireless signals in mmWave bands (e.g., 28 GHz, 30 GHz, 38 GHz, 60 GHz). To improve channel gain, the base station 110 and the terminal 120 may perform beamforming. Here, beamforming may include transmission beamforming and reception beamforming. The base station 110 and the terminal 120 can provide directionality to a transmitted signal or a received signal. To this end, the base station 110 and the terminal 120 may select serving beams through a beam search or beam management procedure. After serving beams are selected, subsequent communication can be performed through a resource in a QCL relationship with the resource that transmitted the serving beams.

A first antenna port and a second antenna port are said to be in a QCL relationship if the large-scale characteristics of the channel carrying the symbols on the first antenna port can be inferred from the channel carrying the symbols on the second antenna port. can be evaluated. For example, a wide range of characteristics include delay spread, doppler spread, doppler shift, average gain, average delay, and spatial receiver parameters. It may include at least one of:

In FIG. 1, both the base station 110 and the terminal 120 are depicted as performing beamforming, but embodiments of the present disclosure are not necessarily limited thereto. In some embodiments, the terminal may or may not perform beamforming. Additionally, the base station may or may not perform beamforming. That is, only one of the base station and the terminal may perform beamforming, or neither the base station nor the terminal may perform beamforming.

In the present disclosure, a beam refers to the spatial flow of a signal in a wireless channel, and is formed by one or more antennas (or antenna elements), and this formation process may be referred to as beamforming. there is. Beamforming may include at least one of analog beamforming or digital beamforming (eg, precoding). Reference signals transmitted based on beamforming include, for example, demodulation-reference signal (DM-RS), channel state information-reference signal (CSI-RS), and synchronization signal/physical broadcast channel (SS/PBCH). , may include a sounding reference signal (SRS). Additionally, as a configuration for each reference signal, IE such as CSI-RS resource or SRS-resource may be used, and this configuration may include information associated with the beam. Information associated with a beam refers to whether its configuration (e.g., CSI-RS resource) uses the same spatial domain filter as another configuration (e.g., another CSI-RS resource within the same CSI-RS resource set) or a different This may mean whether a spatial domain filter is used, or which reference signal it is QCL (quasi-co-located) with, and if so, what type (e.g., QCL type A, B, C, D).

Conventionally, in a communication system in which the cell radius of the base station is relatively large, each base station has a digital processing unit (or distributed unit (DU)) and a radio frequency (RF) processing unit (RF processing unit, or RU). It was installed to include the functions of a radio unit). However, as higher frequency bands are used in ^4th generation (4G) and/or subsequent communication systems (e.g., 5G) and cell coverage of base stations becomes smaller, the number of base stations to cover a specific area has increased. The installation cost burden on operators to install base stations has also increased. In order to minimize the installation cost of the base station, the DU and RU of the base station are separated, one or more RUs are connected to one DU through a wired network, and one or more RUs are deployed geographically distributed to cover a specific area. A structure has been proposed. Hereinafter, the deployment structure and expansion examples of the base station according to various embodiments of the present disclosure are described through FIGS. 2A and 2B.

*Figure 2A shows a fronthaul interface according to embodiments. Fronthaul refers to the connection between entities between the wireless LAN and the base station, unlike backhaul between the base station and the core network. FIG. 2A shows an example of a fronthaul structure between a DU 210 and one RU 220, but this is only for convenience of explanation and the present disclosure is not limited thereto. In other words, the embodiment of the present disclosure can also be applied to the fronthaul structure between one DU and multiple RUs. For example, embodiments of the present disclosure can be applied to a fronthaul structure between one DU and two RUs. Additionally, embodiments of the present disclosure can also be applied to a fronthaul structure between one DU and three RUs.

Referring to FIG. 2A, the base station 110 may include a DU 210 and a RU 220. The fronthaul 215 between the DU 210 and the RU 220 may be operated through the F _x interface. For operation of the fronthaul 215, for example, an interface such as enhanced common public radio interface (eCPRI) or radio over ethernet (ROE) may be used.

As communication technology develops, mobile data traffic increases, and accordingly, the bandwidth requirement for the fronthaul between digital units and wireless units has increased significantly. In deployments such as C-RAN (centralized/cloud radio access network), DU performs functions for PDCP (packet data convergence protocol), RLC (radio link control), MAC (media access control), and PHY (physical). , the RU may be implemented to perform more functions for the PHY layer in addition to the radio frequency (RF) function.

The DU 210 may be responsible for upper layer functions of the wireless network. For example, the DU 210 may perform the functions of the MAC layer and part of the PHY layer. Here, part of the PHY layer is performed at a higher level among the functions of the PHY layer, for example, channel encoding (or channel decoding), scrambling (or descrambling), modulation (or demodulation), and layer mapping (layer mapping) (or layer demapping). According to one embodiment, if the DU 210 complies with the O-RAN standard, it may be referred to as an O-RAN DU (O-DU). DU 210 may be represented as a replacement for a first network entity for a base station (eg, gNB) in embodiments of the present disclosure, if necessary.

The RU 220 may be responsible for lower layer functions of the wireless network. For example, the RU 220 may perform part of the PHY layer and RF functions. Here, the part of the PHY layer is one that is performed at a relatively lower level than the DU 210 among the functions of the PHY layer, for example, iFFT conversion (or FFT conversion), CP insertion (CP removal), and digital beamforming. It can be included. An example of this specific functional separation is detailed in Figure 4. RU 220 is an 'access unit (AU)', 'access point (AP)', 'transmission/reception point (TRP)', 'remote radio head (RRH) )', 'radio unit (RU)', or other terms with equivalent technical meaning. According to one embodiment, if the RU 220 complies with the O-RAN standard, it may be referred to as an O-RAN RU (O-RU). The RU 220 may be replaced with a second network entity for a base station (eg, gNB) in embodiments of the present disclosure, if necessary.

Although FIG. 2A illustrates that the base station 110 includes a DU 210 and a RU 220, embodiments of the present disclosure are not limited thereto. The base station according to embodiments includes a centralized unit (CU) configured to perform the functions of the upper layers of the access network (e.g., packet data convergence protocol (PDCP), radio resource control (RRC)) and a lower layer. It can be implemented as a distributed deployment according to distributed units (DUs) configured to perform functions. At this time, the distributed unit (DU) may include the digital unit (DU) and radio unit (RU) of FIG. 1. Between the core (e.g. 5GC (5G core) or NGC (next generation core)) network and the radio network (RAN), base stations may be implemented in a structure in which CU, DU, and RU are arranged in that order. The interface between the CU and distributed unit (DU) may be referred to as the F1 interface.

A centralized unit (CU) is connected to one or more DUs and can be responsible for functions of a higher layer than the DU. For example, the CU may be responsible for the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, and the DU and RU may be responsible for the functions of the lower layer. DU performs RLC (radio link control), MAC (media access control), and some functions of the PHY (physical) layer (high PHY), and RU is responsible for the remaining functions of the PHY layer (low PHY). there is. Additionally, as an example, a digital unit (DU) may be included in a distributed unit (DU), depending on the distributed deployment implementation of the base station. Hereinafter, unless otherwise defined, the operations of a digital unit (DU) and RU are described, but various embodiments of the present disclosure are based on a base station arrangement including a CU or an arrangement where the DU is directly connected to the core network (i.e., CU and DU can be applied to both integrated and implemented as a single entity, a base station (e.g., NG-RAN node).

FIG. 2B shows a fronthaul interface of an open (O)-RAN (radio access network) according to embodiments. As a base station 110 according to distributed deployment, an eNB or gNB is exemplified.

Referring to FIG. 2B, the base station 110 may include an O-DU 251 and O-RUs 253-1, ..., 253-n. Hereinafter, for convenience of explanation, the operations and functions of the O-RU 253-1 may be understood as explanations for each of other O-RUs (eg, O-RU 253-n).

The O-DU 251 includes functions excluding functions exclusively assigned to the O-RU 253-1 among the functions of the base station (e.g., eNB, gNB) according to FIG. 4, which will be described later. It is a logical node that does. O-DU (251) can control the operation of O-RUs (253-1, ..., 253-n). The O-DU 251 may be referred to as a lower layer split (LLS) central unit (CU). The O-RU 253-1 is a logical node that includes a subset of the functions of a base station (e.g., eNB, gNB) according to FIG. 4, which will be described later. Real-time aspects of control plane (C-plane) communication and user plane (U-plane) communication with the O-RU 253-1 may be controlled by the O-DU 251.

The O-DU 251 can communicate with the O-RU 253-1 through an LLS interface. The LLS interface corresponds to the fronthaul interface. The LLS interface refers to a logical interface between the O-DU 251 and the O-RU 253-1 using lower layer functional split (i.e., intra-PHY-based functional split). LLS-C between O-DU (251) and O-RU (253-1) provides C-plane through the LLS interface. LLS-U between O-DU (251) and O-RU (253-1) provides U-plane through the LLS interface.

In FIG. 2B, to explain O-RAN, the entities of the base station 110 are referred to as O-DU and O-RU. However, these names should not be construed as limiting the embodiments of the present disclosure. In the embodiments described through FIGS. 3A to 12, it goes without saying that the operations of the DU 210 can be performed by the O-DU 251. The description of DU 210 may be applied to O-DU 251. Likewise, in the embodiments described through FIGS. 3A to 12, it goes without saying that the operations of the RU 220 may be performed by the O-RU 253-1. The description of RU 220 may be applied to O-DU 253-1.

FIG. 3A shows the functional configuration of a distributed unit (DU) according to embodiments. The configuration illustrated in FIG. 3A may be understood as the configuration of DU 210 in FIG. 2A (or O-DU 250 in FIG. 2B) as part of a base station. Terms such as '... unit' and '... unit' used hereinafter refer to a unit that processes at least one function or operation, which can be implemented through hardware, software, or a combination of hardware and software. there is.

Referring to FIG. 3A, the DU 210 includes a transceiver 310, a memory 320, and a processor 330.

The transceiver 310 may perform functions for transmitting and receiving signals in a wired communication environment. The transceiver 310 may include a wired interface for controlling direct connection between devices through a transmission medium (e.g., copper wire, optical fiber). For example, the transceiver 310 may transmit an electrical signal to another device through a copper wire or perform conversion between an electrical signal and an optical signal. The DU 210 may communicate with a radio unit (RU) through the transceiver 310. The DU 210 may be connected to a CU in a core network or distributed arrangement through the transceiver 310.

The transceiver 310 may perform functions for transmitting and receiving signals in a wireless communication environment. For example, the transceiver 310 may perform a conversion function between a baseband signal and a bit stream according to the physical layer standard of the system. For example, when transmitting data, the transceiver 310 generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the transceiver 310 restores the received bit stream by demodulating and decoding the baseband signal. Additionally, the transceiver 310 may include multiple transmission and reception paths. Additionally, according to one embodiment, the transceiver 310 may be connected to the core network or to other nodes (eg, integrated access backhaul (IAB)).

The transceiver 310 can transmit and receive signals. For example, the transceiver 310 may transmit a management plane (M-plane) message. For example, the transceiver 310 may transmit a synchronization plane (management plane, S-plane) message. For example, the transceiver 310 may transmit a control plane (C-plane) message. For example, the transceiver 310 may transmit a user plane (U-plane) message. For example, transceiver 310 may receive a user plane message. Although only the transceiver 310 is shown in FIG. 3A, according to another implementation example, the DU 210 may include two or more transceivers.

The transceiver 310 transmits and receives signals as described above. Accordingly, all or part of the transceiver 310 may be referred to as a 'communication unit', a 'transmission unit', a 'reception unit', or a 'transmission/reception unit'. Additionally, in the following description, transmission and reception performed through a wireless channel are used to mean that processing as described above is performed by the transceiver 310.

Although not shown in FIG. 3A, the transceiver 310 may further include a backhaul transceiver for connection to the core network or another base station. The backhaul transceiver provides an interface to communicate with other nodes in the network. In other words, the backhaul transceiver converts the bit string transmitted from the base station to other nodes (e.g., other access nodes, other base stations, upper nodes, core networks, etc.) into physical signals, and the physical signals received from other nodes into bit strings. Convert.

The memory 320 stores data such as basic programs, application programs, and setting information for operation of the DU (210). Memory 320 may be referred to as a storage unit. The memory 320 may be comprised of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. And, the memory 320 provides stored data according to the request of the processor 330.

The processor 330 controls the overall operations of the DU (210). The processor 380 may be referred to as a control unit. For example, the processor 330 transmits and receives signals through the transceiver 310 (or through the backhaul communication unit). Additionally, the processor 330 writes and reads data into the memory 320. Additionally, the processor 330 can perform protocol stack functions required by communication standards. Although only the processor 330 is shown in FIG. 3A, according to another implementation example, the DU 210 may include two or more processors.

The configuration of the DU 210 shown in FIG. 3A is only an example, and the example of the DU performing the embodiments of the present disclosure is not limited to the configuration shown in FIG. 3A. In some embodiments, some configurations may be added, deleted, or changed.

FIG. 3B shows the functional configuration of a radio unit (RU) according to embodiments. The configuration illustrated in FIG. 3B may be understood as a configuration of the RU 220 of FIG. 2B or the O-RU 253-1 of FIG. 2B as part of a base station. Terms such as '... unit' and '... unit' used hereinafter refer to a unit that processes at least one function or operation, which can be implemented through hardware, software, or a combination of hardware and software. there is.

Referring to FIG. 3B, the RU 220 includes an RF transceiver 360, a fronthaul transceiver 365, a memory 370, and a processor 380.

The RF transceiver 360 performs functions for transmitting and receiving signals through a wireless channel. For example, the RF transceiver 360 upconverts the baseband signal into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the RF transceiver 360 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

The RF transceiver 360 may include multiple transmission and reception paths. Furthermore, the RF transceiver 360 may include an antenna unit. The RF transceiver 360 may include at least one antenna array comprised of multiple antenna elements. In terms of hardware, the RF transceiver 360 may be composed of digital circuits and analog circuits (eg, radio frequency integrated circuit (RFIC)). Here, the digital circuit and analog circuit can be implemented in one package. Additionally, the RF transceiver 360 may include multiple RF chains. The RF transceiver 360 may perform beamforming. The RF transceiver 360 may apply a beamforming weight to the signal to be transmitted and received in order to give directionality according to the settings of the processor 380. According to one embodiment, the RF transceiver 360 may include a radio frequency (RF) block (or RF unit).

According to one embodiment, the RF transceiver 360 may transmit and receive signals on a radio access network. For example, the RF transceiver 360 may transmit a downlink signal. Downlink signals include synchronization signal (SS), reference signal (RS) (e.g., cell-specific reference signal (CRS), demodulation (DM)-RS), system information (e.g., MIB, SIB, It may include remaining system information (RMSI), other system information (OSI), configuration message, control information, or downlink data. Also, for example, the RF transceiver 360 may receive an uplink signal. Uplink signals include random access-related signals (e.g., random access preamble (RAP) (or Msg1 (message 1)), Msg3 (message 3)), reference signals (e.g., sounding reference signal (SRS), DM) -RS), or power headroom report (PHR), etc. Although only the RF transceiver 360 is shown in FIG. 3B, according to another implementation example, the RU 220 may include two or more RF transceivers.

According to embodiments, RF transceiver 460 may transmit RIM-RS. The RF transceiver 460 may transmit a first type of RIM-RS (eg, RIM-RS type 1 of 3GPP) to notify detection of remote interference. The RF transceiver 460 may transmit a second type of RIM-RS (e.g., RIM-RS type 2 of 3GPP) to indicate the presence or absence of remote interference.

The fronthaul transceiver 365 can transmit and receive signals. According to one embodiment, the fronthaul transceiver 365 may transmit and receive signals on the fronthaul interface. For example, the fronthaul transceiver 365 may receive a management plane (M-plane) message. For example, the fronthaul transceiver 365 may receive a synchronization plane (management plane, S-plane) message. For example, the fronthaul transceiver 365 may receive a control plane (C-plane) message. For example, the fronthaul transceiver 365 may transmit a user plane (U-plane) message. For example, fronthaul transceiver 365 may receive user plane messages. Although only the fronthaul transceiver 365 is shown in FIG. 3b, according to another implementation example, the RU 220 may include two or more fronthaul transceivers.

The RF transceiver 360 and the fronthaul transceiver 365 transmit and receive signals as described above. Accordingly, all or part of the RF transceiver 360 and the fronthaul transceiver 365 may be referred to as a 'communication unit', a 'transmission unit', a 'reception unit', or a 'transceiver unit'. Additionally, in the following description, transmission and reception performed through a wireless channel are used to mean that the processing as described above is performed by the RF transceiver 360. In the following description, transmission and reception performed through a wireless channel are used to mean that the processing as described above is performed by the RF transceiver 360.

The memory 370 stores data such as basic programs, application programs, and setting information for operation of the RU 220. Memory 370 may be referred to as a storage unit. The memory 370 may be comprised of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. And, the memory 370 provides stored data according to the request of the processor 380. According to one embodiment, memory 370 may include memory for conditions, commands, or setting values related to the SRS transmission method.

The processor 380 controls the overall operations of the RU (220). The processor 380 may be referred to as a control unit. For example, processor 380 transmits and receives signals through RF transceiver 360 or fronthaul transceiver 365. Additionally, the processor 380 writes and reads data into the memory 370. Additionally, the processor 380 can perform protocol stack functions required by communication standards. Although only the processor 380 is shown in FIG. 3B, according to another implementation example, the RU 220 may include two or more processors. The processor 380 is a set of instructions or code stored in the memory 370, which is a storage space that stores instructions/code or instructions/code that are at least temporarily residing in the processor 380, or the processor 380 It may be part of the circuitry that constitutes. Additionally, the processor 380 may include various modules for performing communication. The processor 380 may control the RU 220 to perform operations according to embodiments described later.

The configuration of the RU 220 shown in FIG. 3B is only an example, and the example of the RU that performs the embodiments of the present disclosure is not limited to the configuration shown in FIG. 3B. In some embodiments, some configurations may be added, deleted, or changed.

Figure 4 shows an example of function split between DU and RU, according to embodiments. As wireless communication technology develops (e.g., the introduction of the ^5th generation (5G) communication system (or the introduction of the new radio (NR) communication system), the frequency band used has further increased. As the cell radius of the base station becomes very small, The number of RUs required to be installed has further increased, and in the 5G communication system, the amount of data transmitted has increased significantly by more than 10 times, and the transmission capacity of the wired network transmitted through the fronthaul has increased significantly. Therefore, in the 5G communication system, the installation cost of the wired network can increase significantly. Therefore, in order to lower the transmission capacity of the wired network and reduce the installation cost of the wired network, some functions of the DU's modem are installed. 'Function split', which lowers the fronthaul transmission capacity by transferring it to the RU, can be used.

To reduce the burden on the DU, the role of the RU, which is responsible only for existing RF functions, can be expanded to include some functions of the physical layer. As the RU performs higher layer functions, the throughput of the RU increases, thereby increasing the transmission bandwidth in the fronthaul, and at the same time, the latency requirement constraints due to response processing can be lowered. Meanwhile, as the RU performs higher layer functions, the virtualization gain decreases, and the size, weight, and cost of the RU increase. Considering the trade-off of the advantages and disadvantages described above, it is necessary to implement optimal functional separation.

Referring to Figure 4, functional separations in the physical layer below the MAC layer are shown. In the case of downlink (DL), which transmits signals to the terminal through a wireless network, the base station sequentially performs channel encoding/scrambling, modulation, layer mapping, antenna mapping, RE mapping, digital beamforming (e.g. precoding), iFFT conversion/CP insertion, and RF conversion can be performed. In the case of uplink (UL), which receives signals from a terminal through a wireless network, the base station sequentially performs RF conversion, FFT conversion/CP removal, digital beamforming (pre-combining), and RE decoding. It can perform mapping, channel estimation, layer demapping, demodulation, and decoding/descrambling. Separation of uplink functions and downlink functions can be defined in various types depending on the need between vendors (vendors), discussions on specifications, etc. according to the trade-off described above.

In the first functional separation 405, the RU performs the RF function and the DU performs the PHY function. The first function separation is that the PHY function in the RU is not substantially implemented, and may be referred to as Option 8, for example. In the second functional separation 410, the RU performs iFFT conversion/CP insertion in the DL and FFT conversion/CP removal in the UL of the PHY functions, and the DU performs the remaining PHY functions. As an example, the second functional separation 410 may be referred to as Option 7-1. In the third function separation 420a, the RU performs iFFT conversion/CP insertion in the DL and FFT conversion/CP removal and digital beamforming in the UL of the PHY functions, and the DU performs the remaining PHY functions. As an example, the third functional separation 420a may be referred to as Option 7-2x Category A. In the fourth function separation 420b, the RU performs digital beamforming in both DL and UL, and the DU performs higher PHY functions after digital beamforming. As an example, the fourth functional separation 420b may be referred to as Option 7-2x Category B. In the fifth function separation 425, the RU performs RE mapping (or RE demapping) in both DL and UL, and the DU performs higher PHY functions after RE mapping (or RE demapping). As an example, the fifth function separation 425 may be referred to as Option 7-2. In the sixth function separation 430, the RU performs modulation (or demodulation) in both DL and UL, and the DU performs subsequent higher PHY functions until modulation (or demodulation). As an example, the sixth function separation 430 may be referred to as Option 7-3. In the seventh function separation 440, the RU performs encoding/scrambling (or decoding/descrambling) in both DL and UL, and the DU performs subsequent higher PHY functions up to modulation (or demodulation). As an example, the seventh function separation 440 may be referred to as Option 6.

According to one embodiment, when large-capacity signal processing is expected, such as FR 1 MMU, function separation at a relatively high layer (e.g., fourth function separation 420b) may be required to reduce fronthaul capacity. . In addition, separation of functions at too high a layer (e.g., the sixth function separation 430) may cause a burden on the implementation of the RU due to the complicated control interface and the inclusion of multiple PHY processing blocks within the RU. Appropriate separation of functions may be required depending on the arrangement and implementation method of the and RU.

According to one embodiment, when precoding of data received from the DU cannot be processed (i.e., when there is a limit to the precoding capability of the RU), the third function separation 420a or a lower function is performed. Separation (e.g., second functional separation 410) may be applied. Conversely, if there is a capability to process precoding of data received from the DU, the fourth functional separation 420b or a higher functional separation (e.g., the sixth functional separation 430) may be applied.

Hereinafter, in the present disclosure, unless otherwise specified, the embodiments include the third function separation 420a (which may be referred to as category A, CAT-A) or the fourth function separation 420a for performing beamforming processing in the RU. It is described based on functional separation 420b (which may be referred to as category B CAT-B). The O-RAN standard distinguishes between types of O-RUs depending on whether the precoding function is located on the interface of the O-DU or the O-RU interface. An O-RU in which precoding is not performed (i.e., low complexity) may be referred to as a CAT-A O-RU. The O-RU where precoding is performed may be referred to as a CAT-B O-RU.

Hereinafter, upper-PHY refers to physical layer processing processed in the DU of the fronthaul interface. For example, the upper-PHY may include FEC encoding/decoding, scrambling, and modulation/demodulation. Hereinafter, sub-PHY refers to physical layer processing processed in the RU of the fronthaul interface. For example, the sub-PHY may include FFT/iFFT, digital beamforming, physical random access channel (PRACH) extraction and filtering. However, the above-described criteria do not exclude embodiments with other functional separations. The functional configuration, signaling or operation of FIGS. 5A to 12 described later may be applied not only to the third functional separation 420a or fourth functional separation 420b but also to other functional separations.

Embodiments of the present disclosure, when transmitting messages between a DU (e.g., DU 210 in FIG. 2A) and RU (e.g., RU 220 in FIG. 2A), examples include specifications of eCPRI and O-RAN as fronthaul interfaces. It is described negatively. The Ethernet payload of the message may include an eCPRI header, an O-RAN header, and additional fields. Hereinafter, various embodiments of the present disclosure will be described using the standard terms of eCPRI or O-RAN, but other expressions having equivalent meaning to each term may be used instead of the various embodiments of the present disclosure.

Fronthaul's transport protocol can be Ethernet and eCPRI, which are easy to share with networks. The eCPRI header and O-RAN header may be included in the Ethernet payload. The eCPRI header can be located in front of the Ethernet payload. The contents of the eCPRI header are as follows.

1) ecpriVersion (4 bits): This parameter indicates the eCPRI protocol version.

2) ecpriReserved (3 bits): This parameter is reserved for future use of eCPRI.

3) ecpriConcatenation (1 bit): This parameter indicates when eCPRI concatenation is in use.

4) ecpriMessage (1 byte): This parameter indicates the type of service carried by the message type. For example, the parameter represents an IQ data message, a real-time control data message, or a transport network delay measurement message.

5) ecpriPayload (2 bytes): This parameter indicates the byte size of the payload portion of the eCPRI message.

6) ecpriRtcid/ecpriPcid (2 bytes): This parameter is the extended antenna-carrier (eAxC) identifier (eAxC ID) and identifies the specific data flow associated with each C-plane (ecpriRtcid) or U-plane (ecpriPcid) message. do.

7) ecpriSeqid (2 bytes): This parameter provides unique message identification and ordering at two levels. The first octet of this parameter is the sequence ID, which is used to identify the order of messages within the eAxC message stream, and the sequence ID is used to ensure that all messages have been received and to reorder out-of-order messages. The second octet of this parameter is the subsequence ID. The subsequence ID is used to determine order and implement reordering when radio-transport-level (eCPRI or IEEE-1914.3) fragmentation occurs.

The eAxC identifier (ID) is a band and sector identifier ('BandSector_ID'), a component carrier identifier ('CC_ID'), a spatial stream identifier ('RU_Port_ID'), and a distributed unit identifier ('DU_Port_ID'). Includes. Bit allocation of eAxC ID can be divided as follows.

1) DU_port ID: To distinguish processing units in O-DU, DU_port ID is used (e.g. different baseband cards). It is expected that the O-DU allocates bits for the DU_port ID and the O-RU attaches the same value to the UL U-plane message carrying the same sectionId data.

2) BandSector_ID: Aggregated cell identifier (band and sector distinction supported by O-RU).

3) CC_ID: CC_ID distinguishes carrier components supported by O-RU.

4) RU_port ID: RU_port ID specifies logical flows such as data layer or spatial stream, and signal channels that require separate numerologies (e.g. PRACH) or special antenna allocation such as SRS. do.

The fronthaul application protocol is the control plane (C-plane), user plane (U-plane), synchronization plane (S-plane), and management plane (M). -plane) may be included.

The control plane may be configured to provide scheduling information and beamforming information through control messages. The control plane means real-time control between DU and RU. The user plane may contain IQ sample data transmitted between DU and RU. The user plane may include the user's downlink data (IQ data or SSB/RS), uplink data (IQ data or SRS/RS), or PRACH data. The weight vector of the above-described beamforming information may be multiplied by the user's data. Synchronization plane generally refers to the traffic between DU and RU to a synchronization controller (e.g. IEEE Grand Master). The synchronization plane may be related to timing and synchronization. The management plane refers to non-real-time control between DU and RU. The management plane may be related to initial setup, non-realtime reset or reset, and non-realtime report.

Messages in the control plane, i.e. C-plane messages, can be encapsulated based on a two-layer header approach. The first layer may consist of the eCPRI common header or IEEE 1914.3 common header, which contains fields used to indicate the message type. The second layer is the application layer, which contains fields required for control and synchronization. Within the application layer, a section defines the characteristics of U-plane data transmitted or received on a beam with one pattern ID. The section types supported within C-plane are as follows.

Section Type may indicate the purpose of the control message transmitted in the control plane. For example, the purpose of each Section Type is as follows.

1) sectionType=0: Used to indicate unused resource blocks or symbols in DL or UL.

2) sectionType=1: Used for most DL/UL wireless channels. Here, 'most' refers to channels that do not require time or frequency offset, such as is required for mixed numerology channels.

3) sectionType=2: reserved for further use

4) sectionType=3: PRACH and mixed-numerology channel. Channels that require time or frequency offset or differ from the nominal SCS value(s)

5) sectionType=4: reserved for further use

6) sectionType=5: UE scheduling information. Delivers UE scheduling information so that RU can calculate BF weight in real time (O-RAN optional BF method)

7) sectionType=6: UE-specific channel information transmission. Periodically transmit UE channel information so that RU can calculate BF weight in real time (O-RAN optional BF method)

8) sectionType=7: Used for LAA support

In O-RAN, various types of compression techniques can be used within each section to increase data transmission efficiency between DUs and RUs. The compression techniques include, for example, a no-compression technique, a block floating point compression (BFPC) technique, and a modulation compression (MC) technique. The IQ data frame of the O-RAN standard may include a user data compression header (e.g., udCompHdr). The user data compression header is defined and transmitted by bit width (e.g., 4-bit 'udIqWidth') and compression method (e.g., 4-bit 'udCompMeth'). For example, the compression method can be defined as in the table below.

udCompMeth compression method udIqWidth meaning 0000b no compression bitwidth of each uncompressed I and Q value 0001b Block floating point (BFP) bitwidth of each I and Q mantissa value 0010b Block scaling bitwidth of each I and Q scaled value 0011b μ-law bitwidth of each compressed I and Q value 0100b Modulation compression bitwidth of each compressed I and Q value 0101b BFP +selective RE sending bitwidth of each compressed I and Q value 0110b Mod-compr + selective RE sending bitwidth of each compressed I and Q value 0111b-1111b Reserved for further methods depends on the specific compression method

Among the above-described compression techniques, the MC technique is a non-lossy method, with no data loss and high compression efficiency. The MC technique relies on the characteristic that a modulated data symbol can be represented by a very limited number of bits of the I (in-phase) component and Q (quadrature) component bits. For example, a quadrature phase shift keying (QPSK) modulated symbol has only two potential states of I and two potential states of Q, so the QPSK modulated symbol has I It can be expressed without loss of information with a single bit for the component and a single bit for the Q component. For another example, a symbol modulated using 64 QAM can be expressed with a maximum of 3 bits for the I component and 3 bits for the Q component.

For the I component of data in a U-plane message, 16 bits can be used. For the Q component of data in a U-plane message, 16 bits can be used. That is, 32 bits in the U-plane message can be used to transmit data. For modulation compression, if QPSK modulation is used, the number of bits transmitted can be reduced from 32 bits to 2 bits. For modulation compression, if 16 QAM modulation is used, the number of bits transmitted can be reduced from 32 bits to 4 bits. For modulation compression, if 64 QAM modulation is used, the number of bits transmitted can be reduced from 32 bits to 6 bits.

To represent the values of the I and Q components, which can allow for the overlap of multiple constellation sizes that can be expressed in a single word-width, the constellations are two's complements. -complement)) can be 'moved' to represent each constellation point. For example, QPSK constellation points can move by -1/2. The I component can be -1 or 0. The Q component can be -1 or 0. Also, for example, 16 QAM constellation points can move by -1/4. The I component can be -1, -1/2, 0, 1/2. The Q component can be -1, 1/2, 0, or 1/2. Also, for example, 64 QAM constellation points can move by -1/8. The I component can be -1, -3/4, -1/2, -1/4, 0, 1/4, 1/2, or 3/4. The Q component can be -1, -3/4, -1/2, -1/4, 0, 1/4, 1/2, or 3/4.

The MC technique converts bit-level information into SCP (shifted constellation point). The DU (eg, DU 210) may transmit a U-plane message containing converted information according to the SCP to the RU (eg, RU 220). The DU 210 may transmit a constellation shift flag (CSF) to the RU 220 to indicate whether there is a shift. For example, when the 'csf' value is '1', the movement value of each constellation point in a specific bit width can be defined as shown in Table 2.

udIqWidth Shift value One 1/2 2 1/4 3 1/8 4 1/16 5 1/32

Data compressed according to the MC technique does not represent actual power values. The DU 210 may transmit a modulation compression scaler value (modCompScaler) to the RU 220 so that the RU can set a power level to the modulation compressed data. The 'modCompScaler' parameter indicates the scale factor to apply to unshifted constellation points during decompression. In the O-RAN standard, the 'modCompScaler' parameter can be provided to the RU through section extension information (e.g. Section Extension Type 4). The 'modCompScaler' parameter can indicate the exponent component and mantissa component through the following equation.

'mantissa' indicates the mantissa component of the indicated value. 'exponent' represents the exponential component of the indicated value. modCompScaler[k] represents the k+1th bit of the 'modCompScaler' parameter. For example, modCompScaler[0] represents the first bit of the 'modCompScaler' parameter. modCompScaler[14] represents the 15th bit of the 'modCompScaler' parameter.

Among the 15 bits of the 'modCompScaler' parameter, the most significant 4-bits indicate the exponent component, and among the 15 bits of the 'modCompScaler' parameter, the lowest 11-bits indicate the mantissa component. Therefore, the value indicated by the 'modCompScaler' parameter is the same as the equation below.

'mantissa' indicates the mantissa component of the indicated value. 'exponent' represents the exponential component of the indicated value.

Section Extension 4 of the O-RAN standard that transmits the 'modCompScaler' parameter is shown in the table below.

The DU 210 may transmit a modulation compression power scale RE mask (mcScaleReMask) to the RU 220. The 'mcScaleReMask' parameter may indicate the position of the RE, with the same scaling and modulation type, within the PRB. Similar to the 'modCompScaler' parameter, the DU 210 may transmit a scaling value for modulation compression (mcScaleOffset) to the RU 220. The 'mcScaleOffset' parameter indicates the scale factor to apply to unshifted constellation points during decompression. In the O-RAN standard, the 'mcScaleOffset' parameter may be provided to the RU 220 through section extension information (e.g., Section Extension Type 5). The 'mcScaleOffset' parameter can indicate the exponent component and mantissa component through the equation below.

'mantissa' indicates the mantissa component of the indicated value. 'exponent' represents the exponential component of the indicated value. mcScaleOffset[k] represents the k+1th bit of the 'mcScaleOffset' parameter. For example, mcScaleOffset[0] represents the first bit of the 'mcScaleOffset' parameter. mcScaleOffset[14] represents the 15th bit of the 'mcScaleOffset' parameter.

Among the 15 bits of the 'mcScaleOffset' parameter, the most significant 4 bits indicate the exponent component, and among the 15 bits of the 'mcScaleOffset' parameter, the lowest 11 bits indicate the mantissa component. Therefore, the value indicated by the 'mcScaleOffset' parameter is the same as the equation below.

'mantissa' indicates the mantissa component of the indicated value. 'exponent' represents the exponential component of the indicated value.

Section Extension 5 of the O-RAN standard that transmits the 'mcScaleOffset' parameter is shown in the tables below. Table 4 shows one scaler value, and Table 5 shows two scaler values.

The section expansion information in Tables 3 to 5 described above may be included in the C-plane message. The RU 220 can restore the original signal intended by the DU 210 based on compressed data received through the U-plane message and parameters received through the C-plane message. According to one embodiment, the RU 220 may obtain the original signal from compressed bits based on the 'csf' parameter. According to one embodiment, the RU 220 may obtain the original signal from compressed bits based on the 'modCompScaler' parameter. According to one embodiment, the RU 220 may obtain the original signal from compressed bits based on the 'mcscaleoffset' parameter and the 'mcScaleReMask' parameter.

5A-5B illustrate examples of modulation compression (MC), according to embodiments. Terms such as '... unit' and '... unit' used hereinafter refer to a unit that processes at least one function or operation, which can be implemented through hardware, software, or a combination of hardware and software. there is.

Referring to FIG. 5A, the DU 510 may include a scheduling unit 511, a C-plane message generation unit 513, and a U-plane message generation unit 515. The scheduling unit 511 may perform scheduling on U-plane messages according to the modulation compression technique described above. The C-plane message generator 513 may generate a C-plane message including control information according to the modulation compression technique. For example, the C-plane message generator 513 may generate a C-plane message including Section Extension 4 as shown in Table 3. Additionally, for example, the C-plane message generator 513 may generate a C-plane message including Section Extension 5 as shown in Table 4 or Table 5. The U-plane message generator 515 may generate a U-plane message including an I component and a Q component according to the modulation compression technique.

The RU 520 may include a C-plane analysis unit 521, a buffer 523, a U-plane analysis unit 525, and a modulation decompression unit 527. The C-plane analysis unit 521 may receive a C-plane message from the DU 510. The C-plane analysis unit 521 may obtain parameter(s) related to modulation compression from section extension information (e.g., Section Extension 4, Section Extension 5) included in the C-plane message. The C-plane analysis unit 521 can obtain section information from the C-plane message. The C-plane analysis unit 521 may store the parameter(s) related to the modulation compression and the section information in the buffer 523. The U-plane analysis unit 525 may receive a U-plane message from the DU 510. The U-plane analysis unit 525 may include the I component and Q component included in the U-plane message. The modulation decompression unit 527 may obtain the parameter(s) related to the modulation compression and the section information from the buffer 523. The modulation decompression unit 527 may obtain the I component and the Q component from the U-plane analysis unit 525. The modulation decompression unit 527 may obtain a bit stream for the I component and a bit stream for the Q component based on the parameters related to the modulation compression. For example, when decompressing, the modulation decompression unit 527 may 'unshift' the constellation according to the 'csf' value and apply a scale factor for the constellation type indicated in the section. . One section can have multiple modulation types. The modulation type can be inferred from the reMask bits. Each '1' bit in the reMask bits corresponds to the shift command ('csf') and scale factor (e.g. 'modCompScaler' when using section extension 4, 'mcScaleOffset' when using section extension 5), for REs in the PRB. ).

The O-RAN standard provides section-based modulation compression. If a compression technique rather than modulation compression is used when transmitting data in a specific slot, the section can be configured according to beamId (or ueId) allocation of data resources (e.g. RE/PRB/symbol). However, when modulation compression is applied, all PRBs and symbols within a section will use the same 'csf' and the same scaler value (e.g. 'modCompScaler' when using section extension 4, 'mcScaleOffset' when using section extension 5). may be required. In other words, since sections are configured according to the 'csf' and scaler values of the data, relatively more sections can be configured in modulation compression compared to compression techniques other than modulation compression. For example, if resource areas have the same beamId, but different 'csf' and different scaler values, the resource areas may be required to be separated into different sections.

Referring to Figure 5b, the resource grid 551 represents data allocation for each independent data type. The vertical axis of the resource grid 551 may represent the frequency domain (unit: PRB), and the horizontal axis may represent the time domain (unit: symbol). For example, data 551a, data 551b, data 551c, data 551d, data 551e, data 551f, data 551g, and data 551h in the area of resource grid 551. ) may be included.

Resource grid 553 represents data allocation without modulation compression. Data individually transmitted through DU (e.g., data for each beamID (or data for each ueId) may have a unique modulation type. However, if the modulation compression technique is not applied, the DU has a certain area specified by the PRB interval and symbol interval. is defined as a section, and the DU may transmit data for the section to the RU, for example, three sections (e.g., section #0, section #1, section #2) in the resource grid 553. ) may be included. Section #1 may include a resource area of data 551b, a resource area of data 551c, and section #2 may include a resource area of data 551e. It may include an area, a resource area of data 551f, a resource area of data 551g, and a resource area of data 551h.

Resource grid 555 represents data allocation using modulation compression. A unique modulation type may be applied to each individual data. For example, data 551c and data 551d are frequency-divided in a specific symbol (eg, symbol #4). That is, data 551c and data 551d may be divided into different RB areas within the same symbol. If the same modulation compression is applied to each section, data 551c and data 551d are required to be assigned to different sections. That is, unlike the resource grid 553, the data 551d may be required to be included in a section different from the section containing the data 551c. Additionally, because modulation types can be distinguished for each symbol for modulation compression, sections can be time-divided. For example, independent modulation compression may be applied to each of data 551e, data 551f, data 551g, and data 551h. If the same modulation compression is applied to each section, data 551e, data 551f, data 551g, and data 551h are required to be assigned to different sections.

Although not shown in FIG. 5b, in addition to separation in RB units, separation by RE may also occur when using Section extension 4 during modulation compression.

As described through FIG. 5B, compared to data transmission without modulation compression, data transmission with modulation compression may require more sections. However, as the number of sections increases, the amount of fronthaul transmission may increase. The overhead for defining a section increases, and parameter(s) other than modulation compression are transmitted redundantly, which may result in inefficiency in the RU.

To reduce the problems described above, embodiments of the present disclosure propose control information for providing modulation compression information (eg, 'csf' and scaler value) for data allocated within some areas of a section. Multiple areas may be configured within one section, and modulation compression information may be assigned to each area. The DU (eg, DU 210) may transmit a C-plane message for the section, including modulation compression information for each region, to the RU (eg, RU 220). To describe embodiments of the present disclosure, within the one section, an area distinguished for modulation compression is referred to as an MC (modulation compression) chunk, but in addition to the MC chunk, there are data chunks, data bundles, section bundles, and sections. It may be replaced with group, subblock, data subblock, MC subblock, section subblock, MC area, section subarea, section partial area, or a term with equivalent technical meaning.

6 shows an example of signaling between a DU (e.g., DU 210) and a RU (e.g., RU 220) to provide modulation compression information for a subblock of a section, according to embodiments. do. The subblock of the section is a unit to which modulation compression is applied and may be referred to as an MC chunk.

Referring to FIG. 6, in operation 601, the DU 210 may transmit an M-plane message to the RU 220. According to one embodiment, the DU 210 is an M-plane that includes information to indicate that modulation compression in subblock units, that is, modulation compression specific to MC chunks (hereinafter referred to as MC chunk-based modulation compression) can be provided. Messages can be sent. For example, a section extension type may be defined to provide MC chunk-based modulation compression. The M-plane message may indicate a section extension type that can be supported by the DU 210. The supportable section extension type may indicate section extension information for MC chunk-based modulation compression. Additionally, according to one embodiment, the DU 210 sends at least one parameter for the MC chunk-based modulation compression (described later with reference to FIGS. 7A to 9B) to the RU 220 through the M-plane message. can be provided to. In FIG. 6, an example in which the DU 210 transmits an M-plane message to the RU 220 is described, but embodiments of the present disclosure are not limited to this. In some embodiments, RU 220 may transmit an M-plane message to DU 210. Here, the M-plane message may include at least one of information indicating a section extension type supportable by the RU 220 or a parameter applicable to the RU 220.

In operation 603, DU 210 may perform MC chunk-based scheduling. DU 210 may divide one section into one or more MC chunks. DU 210 may divide one section into multiple MC chunks. For example, DU 210 may divide one section into four MC chunks. DU 210 may determine one or more parameters to represent each MC chunk. For example, DU 210 may determine a parameter indicating the number of MC chunks. Additionally, for example, DU 210 may determine a parameter indicating the number of one or more symbols in each MC chunk. Additionally, for example, DU 210 may determine a parameter indicating the number of one or more PRBs in each MC chunk. Additionally, for example, the DU 210 may determine a parameter indicating the inter-PRB interval or inter-symbol interval of the MC chunk.

In operation 605, the DU 210 may transmit a C-plane message containing compression information for the MC chunk to the RU 220. The C-plane message may include section information. Section information may point to a resource area for the section. The C-plane message may include section extension information. The section extension information may include information indicating a resource area for the MC chunk (hereinafter referred to as resource area information). The section extension information may include compression information for the MC chunk.

According to one embodiment, the resource area information includes parameters according to the scheduling result of the MC chunk (e.g., number of MC chunks, number of one or more symbols of each MC chunk, number of one or more PRBs of each MC chunk, MC It may include at least one of the interval between PRBs of the chunk or the interval between symbols.

According to one embodiment, the compression information includes parameters related to modulation compression to be applied to data on the resource area of the MC chunk (e.g., 'csf' parameter, 'mcScaleReMask' parameter, 'modCompScaler' parameter, or 'mcScaleOffset' parameter ) may include at least one of The 'csf' parameter is a flag that indicates whether the constellation for the MC chunk is shifted. The 'mcScaleReMask' parameter is a bitmap (hereinafter referred to as masking information) for REs in the PRB for the MC chunk, and each bit setting of mcScaleReMask is 'mcScaleOffset' and 'csf' sent as a U-Plane message. Indicates whether it is applicable to the RE (resource element). The 'modCompScaler' parameter or the 'mcScaleOffset' parameter represents the scale value for the MC chunk.

In operation 607, the DU 210 may transmit a U-plane message to the RU 220. The DU 210 may perform modulation compression on data based on the modulation compression technique according to operations 601 to 605. DU 210 can generate a U-plane message including I component and Q component according to the modulation compression technique. The U-plane message may include data to be transmitted on the area occupied by the MC chunk. The RU 220 may obtain parameters related to modulation compression based on the modulation compression information for the MC chunk of the section extension information received from the DU 210. Based on the parameters related to the modulation compression, a bit string for the I component and a bit string for the Q component can be obtained. For example, when decompressing, the RU 220 may 'unshift' the constellation according to the 'csf' value and apply the scale value for the constellation type indicated in the section.

In FIG. 6, only the U-plane message for the downlink is described as an example, but embodiments of the present disclosure are not limited thereto. In some embodiments, modulation compression using an MC chunk according to embodiments of the present disclosure may also be applied to a U-plane message for an uplink signal.

Multiple areas (i.e. MC chunks) may be defined within one section. The DU 210 according to embodiments may allocate modulation compression information to each MC chunk. According to one embodiment, the modulation compression information may include a constellation shift flag (eg, 'csf'). Additionally, according to one embodiment, the modulation compression information may include scale information (e.g., a scaler value, 'mcScaleReMask' parameter, 'modCompScaler' parameter, or 'mcScaleOffset' parameter). Additionally, according to one embodiment, the modulation compression information may include a constellation shift flag and scale information. Because each MC chunk has its own constellation movement flag and scale information, control information may be configured differently depending on how the MC chunk is specified.

Hereinafter, in FIGS. 7A and 7B, the method in which MC chunks are specified is described by first distinguishing in symbol units and later in PRB units.

7A-7B show an example of a first way to divide a section, according to embodiments. One section can be divided into one or more MC chunks. In the first method, when configuring MC chunks, the section is first divided into bundles of symbols (i.e., symbol chunks), and then the frequency domain of the symbol chunks is divided into bundles of PRBs (i.e., PRB chunks ( This refers to a method in which the PRB is divided into chunks))).

Referring to FIG. 7A, the section 700 may be specified as a resource area defined by the 'numPrbc' parameter 710 and the 'numSymbol' parameter 720. The 'numPrbc' parameter 710 represents the number of PRBs. The 'numSymbol' parameter 720 represents the number of symbols. Section 700 may be divided into multiple MC chunks. Hereinafter, to describe the MC chunk, parameters for specifying the MC chunk may first be used. At least some or all of the parameters described below may be used to specify (or distinguish) an MC chunk. The following parameters can be exemplified. The parentheses next to the parameter name indicate an example number of bits.

startMcSymbolId(4b): Start symbol index for symbol chunks with the same symbol range (may be omitted). [start symbol index for a symbol chunk having the same symbol range. (can be absent)]

numMcSymbol(4b): Number of symbols for symbol chunks with the same symbol range. The sum of numMcSymbol must be equal to the numSymbol of the section. '0' may mean numSymbol. [number of symbols for a symbol chunk having the same symbol range. The sum of numMcSymbol should be the same as numSymbol of section. '0' means numSymbol.]

mcSymbPeriod(2b): Symbol chunk period. The above parameters can be set to every symbol, for symbol chunks with the same symbol range, every other symbol (i.e. symbol spacing is one symbol), every 2 symbols (i.e. symbol spacing is two symbols), or every 4 symbols (i.e. , can indicate whether a symbol spacing of 4 symbols is used. 0 = all symbols, 1 = all other symbols, 2 = every 2 symbols, 3 = every 4 symbols (maybe absent if all symbols are always used). [It indicates if every symbol, every other symbol, every 2 symbols, or every 4 symbols is used for a symbol chunk having the same same symbol range. 0 = every symbol, 1 = every other symbol, 2 = every 2 symbols, 3 = every 4 symbols. (can be absent when always every symbol is used.)]

numMcPrbChunks(4b): Number of PRB chunks of symbol chunk #i that numMcSymbol(i) has (may be omitted). [number of PRB chunks on a symbol chunk #i with numMcSymbol(i) (can be absent)]

startMcPrbc(10b): The starting PRB index for the PRB chunk of the PRB chunk (may be omitted). [start PRB index for a PRB chunk in a PRB chunk. (can be absent)]

numMcPrbc(8b): Number of PRBs for the PRB chunk of the symbol chunk. The sum of numMcPrbc must be equal to the numPrbc of the section. '0' means numPrbc. [number of PRBs for a PRB chunk on a symbol chunk. The sum of numMcPrbc should be the same as numPrbc of section. '0' means numPrbc.]

mcPrbPeriod(2b): PRB chunk period. The above parameters can be set for PRB chunks every RB, every other RB (i.e. PRB interval is one PRB), every 2RB (i.e. PRB interval is two PRBs), or every 4RB (i.e. PRB interval is four PRBs). s) can indicate whether it is used or not. 0 = every RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs (maybe none if all RBs are always used). [It indicates if every RBs, every other RBs, every 2 RBs, or every 4 RBs is used for a PRB chunk. 0 = every RBs, 1 = every other RBs, 2 = every 2 RBs, 3 = every 4 RBs. (can be absent when always every RB is used.)]

mcRemaskOnOff(1b): Indicates whether a section expansion or MC chunk has mcScaleRemask. Through this field, the format of the section extension type of the C-plane message, which will be described later, can be changed (if all REs in the MC chunk share the same csf and modCompScaler, it can be omitted). [This indicates there are mcScaleRemask in this section extension or MC chunk (can change format of section extension type with this field) (can be absent when all REs in a MC chunk shares the same CSF and modCompScaler.)]

numMcRemask(4b): Indicates the number of mcScaleRemask within a section extension or MC chunk. (If all REs in a MC chunk share the same CSF and modCompScaler, it can be omitted) [This indicates the number of mcScaleRemask in this section extension or MC chunk (can be absent when all REs in a MC chunk shares the same CSF and modCompScaler.)]

mcScaleReMask(12b): Indicates the RE mask of each RE of the PRB to which the corresponding csf/scaler is applied. [This indicates RE mask of each RE in a PRB which appling the corresponding csf/scaler]

periodFlag(1b): Indicates whether to use mcSymbolPeriod and mcPrbPeriod per section extension or MC chunk (can be omitted). [It indicates if mcSymbolPeriod and mcPrbPeriod are used or not for each section extension or MC chunk. (can be absent)]

Section 700 may be divided into multiple MC chunks. When using the first method, first, it can be divided into symbol units. The 'numSymbol' parameter 720 can be divided into numMcSymbol(0) 721 and numMcSymbol(1) 723. numMcSymbol(0) (721) means the number of one or more symbols in symbol chunk #0. numMcSymbol(1) (723) means the number of symbols in one or more symbol chunk #1. That is, the 'numSymbol' parameter 720 represents the sum of the number of one or more symbols in symbol chunk #0 and the number of one or more symbols in symbol chunk #1. After the section 700 is divided into symbol units, the frequency domain per symbol chunk can be divided into PRB units. The 'numPrbc' parameter 710 can be divided. The frequency domain corresponding to numMcSymbol(0) 721 can be divided into three regions (hereinafter referred to as PRB chunks). The frequency domain corresponding to numMcSymbol(0)(721) is PRB chunk #0(731) of numMcPrbc(0,0), PRB chunk #1(732) of numMcPrbc(0,1), and numMcPrbc(0,2). It can be divided into PRB chunk #2 (733). The frequency domain corresponding to numMcSymbol(1) 723 can be divided into two regions. The frequency domain corresponding to numMcSymbol(1) (723) can be divided into PRB chunk #3 (734) of numMcPrbc (1,0) and PRB chunk #4 (735) of numMcPrbc (1,1).

For example, if all of the above-described parameters are used, the symbol index value of one symbol chunk #i and the PRB index value of PRB chunk #j can be determined as in the following equation.

<Equation 5>

Symbol index(l) = startMcSymbolId + l*(2^mcSymbPeriod), l = 0, … numMcSymbol(i)-1.

<Equation 6>

PRB index(k) = startMcPrbc + k*(2^mcPrbPeriod), k = 0, … numMcPrbc(j)-1.

For example, if startMcSymbolId is not used or startMcPrbc is not used among the parameters, the symbol index value of one symbol chunk #i and the PRB index value of one PRB chunk #j can be determined as in the equation below.

<Equation 7>

Symbol index(l) = first symbol index in symbol chunk #i + l*(2^mcSymbPeriod), l = 0, … numMcSymbol(i)-1. The first symbol index is the first empty symbol index since the previous symbol chunk.

<Equation 8>

PRB index(k) = first PRB index in PRB chunk #j + k*(2^mcPrbPeriod), k = 0, … numMcPrbc(j)-1. The first PRB index is the first PRB index within the symbol chunk that is empty since the previous PRB chunk.

According to one embodiment, numMcPrbChunks may indicate the number of PRB chunks in each symbol chunk. For example, numMcPrbChunks may indicate the number of at least one PRB chunk included in each symbol chunk. According to one embodiment, numMcPrbChunks may indicate the total number of MC chunks in a section extension. For example, numMcPrbChunks may indicate the number of all MC chunks included in the section extension.

According to one embodiment, mcRemaskOnOff and numMcRemask may exist together within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk). According to one embodiment, only one mcRemaskOnOff and numMcRemask may exist within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk). According to one embodiment, mcRemaskOnOff and numMcRemask may not exist within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk).

According to one embodiment, mcRemaskOnOff and numMcRemask may be included together within each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, mcRemaskOnOff and numMcRemask can both be included in each section extension. For example, mcRemaskOnOff and numMcRemask may both be included in an MC chunk (e.g. symbol chunk or PRB chunk).

According to one embodiment, at least one of mcRemaskOnOff and numMcRemask may be included within each section extension (or MC chunk (eg, symbol chunk or PRB chunk)). For example, at least one of mcRemaskOnOff and numMcRemask may both be included in each section extension. For example, at least one of mcRemaskOnOff and numMcRemask may be included in an MC chunk (e.g., symbol chunk or PRB chunk).

According to one embodiment, both mcRemaskOnOff and numMcRemask may not be included within a section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, mcRemaskOnOff and numMcRemask may be included in fields that are distinct from section extensions (or MC chunks (e.g. symbol chunks or PRB chunks)).

According to one embodiment, if resources are periodically allocated in the time domain within one section, a parameter (eg, 'mcSymbolPeriod' parameter) for a symbol chunk may be defined. Additionally, according to one embodiment, if resources are allocated at regular intervals in the frequency domain within one section, a parameter (e.g., 'mcPrbPeriod' parameter) for the PRB chunk may be defined. In the above embodiments, the periodFlag value may or may not exist in each section extension or MC chunk (symbol chunk or PRB chunk) depending on the embodiment. Meanwhile, in the above-described embodiments, one flag parameter is described, but according to another embodiment, separate flag parameters for mcSymbolPeriod and mcPrbPeriod may exist.

The DU 210 may generate section extension information including at least one of the parameters in order to indicate an MC chunk divided according to the first method. The DU 210 may transmit a C-plane message including the section extension information to the RU 220.

According to one embodiment, the DU 210 may configure a section with one MC chunk without using 'mcScaleReMask'. For example, to indicate the one MC chunk, section extension information may be structured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcSymbol' indicates the number of symbols in the MC chunk, that is, the number of symbols in the symbol chunk. For example, if there is only one MC chunk in the section, 'numMcSymbol' may be equal to 'numSymbol'. 'numMcPrbChunks' indicates the number of one or more PRB chunks within the symbol chunk. For example, the number of the one or more PRB chunks may be 1. 'numMcPrbc' indicates the number of PRBs in one PRB chunk. For example, if there is only one MC chunk in the section, 'numMcPrbc' may be the same as 'numPrbc'. 'csf' indicates whether the constellation for the MC chunk is shifted, and 'modCompScaler' indicates the scale value for the MC chunk. The scale value can be derived by calculating Equation 1 to Equation 2 from the 15-bits of the 'modCompScaler' field. According to one embodiment, DU 210 may configure a section with two MC chunks without using 'mcScaleReMask'. For example, to indicate the two MC chunks, section extension information may be structured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcSymbol' indicates the number of symbols in the MC chunks, that is, the number of symbols in the symbol chunk. For example, the number of symbol chunks may be one. 'numMcSymbol' may be the same as 'numSymbol'. Accordingly, the section extension information may include one 'numMcSymbol' field. 'numMcPrbChunks' indicates the number of one or more PRB chunks within the symbol chunk. For example, the number of the one or more PRB chunks may be 2. 'numMcPrbc' of N+3 octets indicates the number of PRBs in the first PRB chunk. The symbol chunk and the first PRB chunk may point to one MC chunk. 'csf' of N+4 octets indicates whether the constellation for the one MC chunk is shifted, and 'modCompScaler' of N+4 octets and N+5 octets indicates the scale value for the one MC chunk. The scale value can be derived by calculating Equation 1 to Equation 2 from the 15-bits of the 'modCompScaler' field. 'numMcPrbc' of N+6 octets indicates the number of PRBs in the second PRB chunk. The symbol chunk and the second PRB chunk may point to another MC chunk. 'csf' of N+7 octets indicates whether the constellation is shifted for the other MC chunk, and 'modCompScaler' of N+7 octets and N+8 octets indicates the scale value for the other MC chunk. indicates. The scale value can be derived from the 15-bits of the 'modCompScaler' field according to the calculation of Equation 1 to Equation 2. According to one embodiment, the DU 210 uses 'mcScaleReMask' and one You can configure sections with MC chunks. For example, to indicate the one MC chunk, section extension information may be structured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcSymbol' indicates the number of symbols in the MC chunk, that is, the number of symbols in the symbol chunk. 'numMcPrbChunks' indicates the number of one or more PRB chunks within the symbol chunk. For example, the number of the one or more PRB chunks may be 1. Therefore, 'numMcPrbc' may be the same as 'numPrbc'. 'mcScaleReMask' is a bitmap (hereinafter referred to as masking information) for REs in the PRB, and each bit setting of mcScaleReMask is 'mcScaleOffset' and 'csf' is a RE (resource element) sent in a U-Plane message. Can indicate whether it is applicable (e.g., '0'=not applicable, '1'=applicable). 'csf' indicates whether the constellation is shifted, and 'mcScaleOffset' indicates the scale value. The scale value can be derived by calculating Equation 3 to Equation 4 from the 15-bits of the 'mcScaleOffset' field.

According to one embodiment, DU 210 may use 'mcScaleReMask' and configure a section with two MC chunks. For example, to indicate the two MC chunks, section extension information may be structured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcSymbol' indicates the number of symbols in the MC chunk, that is, the number of symbols in the symbol chunk. For example, the number of symbol chunks may be 2. Accordingly, the section extension information may include two 'numMcSymbol' fields. Among the two 'numMcSymbol' fields, the first 'numMcSymbol' field indicates the number of one or more symbols in the first symbol chunk. Among the two 'numMcSymbol' fields, the second 'numMcSymbol' field indicates the number of one or more symbols in the second symbol chunk. The section extension information may include information for MC chunks for each 'numMcSymbol' field. 'numMcPrbChunks' for the first 'numMcSymbol' field indicates the number of one or more PRB chunks within the first symbol chunk. For example, the number of the one or more PRB chunks within the first symbol chunk may be 1. 'numMcPrbc' of N+3 octets indicates the number of PRBs in the first symbol chunk and the corresponding PRB chunk. The first symbol chunk and the PRB chunk may point to one MC chunk. 'mcScaleReMask' of N+4 octets to N+5 octets is a bitmap for REs in the PRB of the one MC chunk, and each bit setting of mcScaleReMask is 'mcScaleOffset' and 'csf' are U- It can indicate whether it is applicable to the RE sent as a Plane message (e.g., '0'=not applicable, '1'=applicable). 'csf' of N+5 octets indicates whether the constellation for the one MC chunk is shifted, and 'mcScaleOffset' of N+5 octets to N+6 octets indicates the scale value for the one MC chunk. The scale value can be derived by calculating Equation 3 to Equation 4 from the 15-bits of the 'mcScaleOffset' field. 'numMcPrbChunks' for the second 'numMcSymbol' field indicates the number of one or more PRB chunks within the second symbol chunk. For example, the number of the one or more PRB chunks within the second symbol chunk may be 1. 'numMcPrbc' of N+3 octets indicates the number of PRBs in the second symbol chunk and the corresponding PRB chunk. The second symbol chunk and the PRB chunk may point to another MC chunk. 'mcScaleReMask' of N+10 octets to N+11 octets is a bitmap for REs in the PRB of the one MC chunk, and each bit setting of mcScaleReMask is 'mcScaleOffset' and 'csf' are U- It can indicate whether it is applicable to the RE sent as a Plane message (e.g., '0'=not applicable, '1'=applicable). 'csf' of N+11 octets indicates whether the constellation for the one MC chunk is shifted, and 'mcScaleOffset' of N+11 to N+12 octets indicates the scale value for the one MC chunk. The scale value can be derived by calculating Equation 3 to Equation 4 from the 15-bits of the 'mcScaleOffset' field.

According to one embodiment, the DU 210 may use 'mcScaleReMask' and configure the section 750 with 4 MC chunks with a period. Two symbol chunks may be configured within one section, and two PRB chunks may be configured within each symbol chunk. The 'period flag' parameter for each symbol chunk can be used. For example, to indicate MC chunks according to the section division shown in FIG. 7B, section extension information may be configured as in the table below.

In the example shown in FIG. 7B, section 750 may consist of 7 symbols and 10 PRBs. Here, A=4, B=3, C=5, D=5. Based on the table and FIG. 7b, the first MC chunk 751 can be specified with 4 symbols (A=4) and 5 PRBs (C=5). Here, since 'mcSymbPeriod' is 1, the interval between two symbols among the four symbols can be one symbol. Since 'mcPrbPeriod' is 0, the interval between PRBs among the five PRBs may be 0. That is, the first MC chunk 751 may occupy five consecutive PRBs. As an example, the first MC chunk 751 may occupy PRB #0, PRB #1, PRB #2, PRB #3, and PRB #4. According to the table above and FIG. 7b, the second MC Chunk 752 may be specified with 4 symbols (A=4) and 5 PRBs (D=5). Here, since 'mcSymbPeriod' is 1, the interval between two symbols among the four symbols can be one symbol. Since 'mcPrbPeriod' is 0, the interval between PRBs among the five PRBs may be 0. That is, the second MC chunk 752 may occupy five consecutive PRBs. As an example, the second MC chunk 752 may occupy PRB #5, PRB #6, PRB #7, PRB #8, and PRB #9.

Based on the table and FIG. 7b, the third MC chunk 753 can be specified as 3 symbols (B=3) and 5 PRBs (C=5). Here, since 'mcSymbPeriod' is 1, the interval between two symbols among the three symbols can be one symbol. Since 'mcPrbPeriod' is 1, the interval between PRBs among the five PRBs may be one PRB. As an example, the third MC chunk 753 may occupy PRB #0, PRB #2, PRB #4, PRB #6, and PRB #8.

Based on the table and FIG. 7b, the fourth MC chunk 754 can be specified as 3 symbols (B=3) and 5 PRBs (D=5). Here, since 'mcSymbPeriod' is 1, the interval between two symbols among the three symbols can be one symbol. Since 'mcPrbPeriod' is 1, the interval between PRBs among the five PRBs may be one PRB. The fourth MC chunk 754 may start from an empty PRB area. As an example, the fourth MC chunk 754 may occupy PRB #1, PRB #3, PRB #5, PRB #7, and PRB #9.

According to an additional embodiment, octets corresponding to zero padding in Tables 6 to 10 (e.g., octets N+7 in Table 9, octets N+3, N+5, N+9, N+17 in Table 10, A format in which some areas (N+19, N+23, N+25) are reduced and all parameters are arranged sequentially can also be understood as an embodiment of the present disclosure.

8A-8B show an example of a second method for dividing a section, according to embodiments. One section can be divided into one or more MC chunks. In the second method, when configuring MC chunks, the section is first divided into bundles of PRBs (i.e., PRB chunks), and then the time domain of the PRB chunks is divided into bundles of symbols (i.e., symbol chunks ( It refers to the way it is divided into symbol chunk))).

Referring to FIG. 8A, the section 800 may be specified as a resource area defined by the 'numPrbc' parameter 810 and the 'numSymbol' parameter 820. The 'numPrbc' parameter 810 indicates the number of PRBs. The 'numSymbol' parameter 820 represents the number of symbols. Section 800 may be divided into multiple MC chunks. Hereinafter, to describe the MC chunk, parameters for specifying the MC chunk may first be used. At least some or all of the parameters described below may be used to specify (or distinguish) an MC chunk. The following parameters can be exemplified. The parentheses next to the parameter name indicate an example number of bits.

startMcPrbc(10b): Starting PRB index for the PRB chunk (can be omitted). [start PRB index for a PRB chunk. (can be absent)]

numMcPrbc(8b): Number of PRBs for PRB chunks with the same PRB range. The sum of numMcPrbc must equal the numPrbc of the section. '0' may mean numPrbc. [number of PRBs for a PRB chunk having the same PRB range. The sum of numMcPrbc should be the same as numPrbc of section. '0' means numPrbc.]

mcPrbPeriod(2b): PRB chunk period. The above parameters can be set for PRB chunks every RB, every other RB (i.e. PRB interval is one PRB), every 2RB (i.e. PRB interval is two PRBs), or every 4RB (i.e. PRB interval is four PRBs). s) can indicate whether it is used or not. 0 = every RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs (maybe none if all RBs are always used). [It indicates if every RBs, every other RBs, every 2 RBs, or every 4 RBs is used for a PRB chunk. 0 = every RBs, 1 = every other RBs, 2 = every 2 RBs, 3 = every 4 RBs. (can be absent when always every RB is used.)]

numMcSymbolChunks(4b): Number of symbol chunks in PRB chunk #i with numMcPrbc(i) (may be omitted). [number of symbol chunks on a PRB chunk #i with numMcPrbc(i) (can be absent)]

startMcSymbolId(4b): Start symbol index for a symbol chunk having the same symbol range (may be omitted). (can be absent)]

numMcSymbol(4b): Number of symbols for the symbol chunk in the PRB chunk with numMcPrb. The sum of numMcSymbol must be equal to the numSymbol of the section. '0' may mean numSymbol. [number of symbols for a symbol chunk on a PRB chunk with numMcPrb. The sum of numMcSymbol should be the same as numSymbol of section. '0' means numSymbol.]

mcSymbPeriod(2b): The above parameter can be set to every symbol, every other symbol (i.e. symbol spacing is one symbol), every two symbols (i.e. symbol spacing is two symbols), or for symbol chunks with the same symbol range. It can indicate whether every 4 symbols are used (i.e., a symbol interval of 4 symbols). 0 = all symbols, 1 = all other symbols, 2 = every 2 symbols, 3 = every 4 symbols (maybe absent if all symbols are always used). [It indicates if every symbol, every other symbol, every 2 symbols, or every 4 symbols is used for a symbol chunk having the same same symbol range. 0 = every symbol, 1 = every other symbol, 2 = every 2 symbols, 3 = every 4 symbols. (can be absent when always every symbol is used.)]

mcRemaskOnOff(1b): Indicates whether a section expansion or MC chunk has mcScaleRemask. Through the above field, the format of the section extension type of the C-plane message, which will be described later, can be changed (can be omitted). [This indicates there are mcScaleRemask in this section extension or MC chunk (can change format of section extension type with this field) (can be absent)]

numMcRemask(4b): Indicates the number of mcScaleRemask within a section extension or MC chunk. (If all REs in a MC chunk share the same CSF and modCompScaler, it can be omitted) [This indicates the number of mcScaleRemask in this section extension or MC chunk (can be absent when all REs in a MC chunk shares the same CSF and modCompScaler.)]

mcScaleReMask(12b): Indicates the RE mask of each RE of the PRB to which the corresponding csf/scaler is applied. [This indicates RE mask of each RE in a PRB which applies the corresponding csf/scaler.]

periodFlag(1b): Indicates whether to use mcSymbolPeriod and mcPrbPeriod per section extension or MC chunk (can be omitted). [It indicates if mcSymbolPeriod and mcPrbPeriod are used or not for each section extension or MC chunk. (can be absent)]

Section 800 may be divided into multiple MC chunks. When using the second method, first, it can be divided into PRB units. The 'numPrbc' parameter 810 can be divided into numMcPrbc(0) (811), numMcPrbc(1) (812), and numMcPrbc(2) (813). numMcPrbc(0) (811) means the number of one or more PRBs in PRB chunk #0. numMcSymbol(1) (812) means the number of one or more PRBs in PRB chunk #1. numMcSymbol(2) (813) means the number of one or more PRBs in PRB chunk #2. That is, the 'numPrbc' parameter 810 represents the sum of the number of one or more PRBs in PRB chunk #0, the number of one or more PRBs in PRB chunk #1, and the number of one or more PRBs in PRB chunk #2. After the section 800 is divided into PRB units, the time region per PRB chunk can be divided into symbol units. The 'numSymbol' parameter 820 can be split. The time domain corresponding to numMcPrbc(0) 811 may be divided into two regions (hereinafter, symbol chunks). The time domain corresponding to numMcPrbc(0) (811) can be divided into symbol chunk #0 (831) of numMcSymbol (0,0) and symbol chunk #1 (832) of numMcSymbol (0,1). The time domain corresponding to numMcPrbc(1) (812) may not be divided. The time domain corresponding to numMcPrbc(1) 812 may include symbol chunk #2 833 of one numMcSymbol(1,0). The time domain corresponding to numMcPrbc(2) (813) can be divided into two regions. The time domain corresponding to numMcPrbc(0) (811) can be divided into symbol chunk #3 (834) of numMcSymbol (2,0) and symbol chunk #4 (835) of numMcSymbol (2,1).

For example, if all of the above-described parameters are used, the PRB index value of PRB chunk #i and the symbol index value of one symbol chunk #i can be determined as in the following equation.

<Equation 9>

PRB index(k) = startMcPrbc + k*(2^mcPrbPeriod), k = 0, … numMcPrbc(i)-1.

<Equation 10>

Symbol index(l) = startMcSymbolId + l*(2^mcSymbPeriod), l = 0, … numMcSymbol(j)-1.

For example, if startMcSymbolId is not used or startMcPrbc is not used among the parameters, the PRB index value of PRB chunk #i and the symbol index value of one symbol chunk #i can be determined as in the following equation.

<Equation 11>

PRB index(k) = first PRB index in PRB chunk #j + k*(2^mcPrbPeriod), k = 0, … numMcPrbc(i)-1. The first PRB index is the first PRB index within the symbol chunk that is empty since the previous PRB chunk.

<Equation 12>

Symbol index(l) = first symbol index in symbol chunk #i + l*(2^mcSymbPeriod), l = 0, … numMcSymbol(j)-1. The first symbol index is the first empty symbol index since the previous symbol chunk.

According to one embodiment, numMcSymbolChunks may indicate the number of symbol chunks in each PRB chunk. For example, numMcSymbolChunks may indicate the number of at least one symbol chunk included in each PRB chunk. According to one embodiment, numMcSymbolChunks may indicate the total number of MC chunks within a section extension. For example, numMcSymbolChunks may indicate the number of all MC chunks included in the section extension.

According to one embodiment, mcRemaskOnOff and numMcRemask may exist together within each section extension and/or MC chunk (symbol chunk or PRB chunk). According to one embodiment, only one mcRemaskOnOff and numMcRemask may exist within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk). According to one embodiment, mcRemaskOnOff and numMcRemask may not exist within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk).

According to one embodiment, mcRemaskOnOff and numMcRemask may be included together within each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, mcRemaskOnOff and numMcRemask can both be included in each section extension. For example, mcRemaskOnOff and numMcRemask may both be included in an MC chunk (e.g. symbol chunk or PRB chunk).

According to one embodiment, at least one of mcRemaskOnOff and numMcRemask may be included within each section extension (or MC chunk (eg, symbol chunk or PRB chunk)). For example, at least one of mcRemaskOnOff and numMcRemask may both be included in each section extension. For example, at least one of mcRemaskOnOff and numMcRemask may be included in an MC chunk (e.g., symbol chunk or PRB chunk).

According to one embodiment, both mcRemaskOnOff and numMcRemask may not be included within a section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, mcRemaskOnOff and numMcRemask may be included in fields that are distinct from section extensions (or MC chunks (e.g. symbol chunks or PRB chunks)).

According to one embodiment, if resources are periodically allocated in the time domain within one section, a parameter (eg, 'mcSymbolPeriod' parameter) for a symbol chunk may be defined. Additionally, according to one embodiment, if resources are allocated at regular intervals in the frequency domain within one section, a parameter (e.g., 'mcPrbPeriod' parameter) for the PRB chunk may be defined. In the above embodiments, the periodFlag value may or may not exist in each section extension or MC chunk (symbol chunk or PRB chunk) depending on the embodiment. Meanwhile, in the above-described embodiments, one flag parameter is described, but according to another embodiment, separate flag parameters for mcSymbolPeriod and mcPrbPeriod may exist.

The DU 210 may generate section extension information including at least one of the parameters in order to indicate an MC chunk divided according to the second method. The DU 210 may transmit a C-plane message including the section extension information to the RU 220.

According to one embodiment, the DU 210 may configure a section with one MC chunk without using 'mcScaleReMask'. For example, to indicate the one MC chunk, section extension information may be structured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcPrbc' indicates the number of PRBs in the MC chunk, that is, the number of PRBs in the PRB chunk. For example, if there is only one MC chunk in the section, 'numMcPrbc' may be the same as 'numPrbc'. 'numMcSymbolChunks' indicates the number of one or more symbol chunks in the PRB chunk. For example, the number of one or more symbol chunks may be 1. 'numMcSymbol' represents the number of symbols in one symbol chunk. For example, if there is only one MC chunk in the section, 'numMcSymbol' may be equal to 'numSymbol'. 'csf' indicates whether the constellation is shifted, and 'modCompScaler' indicates the scale value. The scale value can be derived from the 15-bits of the 'modCompScaler' field according to calculations of Equation 1 to Equation 2. According to one embodiment, the DU 210 does not use 'mcScaleReMask' and uses 2 You can configure a section with MC chunks. For example, to indicate the two MC chunks, section extension information may be structured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcPrbc' indicates the number of PRBs in the MC chunk, that is, the number of PRBs in the PRB chunk. For example, the number of PRB chunks may be one. 'numMcPrbc' may be the same as 'numPrbc'. Accordingly, the section extension information may include one 'numMcPrbc' field. 'numMcSymbolChunks' indicates the number of one or more symbol chunks in the PRB chunk. For example, the number of one or more symbol chunks may be 2. 'numMcSymbol' of N+3 octets indicates the number of symbols in the first symbol chunk. The PRB chunk and the first symbol chunk may point to one MC chunk. 'csf' of N+4 octets indicates whether the constellation for the one MC chunk is shifted, and 'modCompScaler' of N+4 octets and N+5 octets indicates the scale value for the one MC chunk. The scale value can be derived from the 15-bits of the 'modCompScaler' field according to calculations of Equation 1 to Equation 2. 'numMcSymbol' of N+6 octets indicates the number of symbols in the second symbol chunk. The PRB chunk and the second symbol chunk may point to another MC chunk. 'csf' of N+7 octets indicates whether the constellation is shifted for the other MC chunk, and 'modCompScaler' of N+7 octets and N+8 octets indicates the scale value for the other MC chunk. indicates. The scale value can be derived from the 15-bits of the 'modCompScaler' field according to the calculation of Equation 1 to Equation 2. According to one embodiment, the DU 210 uses 'mcScaleReMask' and one You can configure sections with MC chunks. For example, to indicate the one MC chunk, section extension information may be configured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcPrbc' indicates the number of PRBs in the MC chunk, that is, the number of PRBs in the PRB chunk. 'numMcSymbolChunks' indicates the number of one or more symbol chunks in the PRB chunk. For example, the number of one or more symbol chunks may be 1. Therefore, 'numMcSymbol' may be the same as 'numSymbol'. 'mcScaleReMask' is a bitmap (hereinafter referred to as masking information) for REs in the PRB, and each bit setting of mcScaleReMask is 'mcScaleOffset' and 'csf' is a RE (resource element) sent in a U-Plane message. Can indicate whether it is applicable (e.g., '0'=not applicable, '1'=applicable). 'csf' indicates whether the constellation is shifted, and 'mcScaleOffset' indicates the scale value. The scale value can be derived by calculating Equation 3 to Equation 4 from the 15-bits of the 'mcScaleOffset' field. According to one embodiment, DU 210 may use 'mcScaleReMask' and configure a section with two MC chunks. For example, to indicate the two MC chunks, section extension information may be structured as shown in the table below.

According to one embodiment, DU 210 may use 'mcScaleReMask' and configure a section with two MC chunks. For example, to indicate the two MC chunks, section extension information may be structured as shown in the table below.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcPrbc' indicates the number of PRBs in the MC chunk, that is, the number of PRBs in the PRB chunk. For example, the number of PRB chunks may be 2. Accordingly, the section extension information may include two 'numMcPrbc' fields. Among the two 'numMcPrbc' fields, the first 'numMcPrbc' field indicates the number of one or more PRBs in the first PRB chunk. Among the two 'numMcPrbc' fields, the second 'numMcPrbc' field indicates the number of one or more PRBs in the second PRB chunk. The section extension information may include information for MC chunks for each 'numMcPrbc' field.

'numMcSymbolChunks' for the first 'numMcPrbc' field indicates the number of one or more symbol chunks within the first PRB chunk. For example, the number of the one or more symbol chunks within the first PRB chunk may be 1. 'numMcSymbol' of N+3 octets indicates the number of symbols in the first PRB chunk and the corresponding symbol chunk. The first PRB chunk and the symbol chunk may point to one MC chunk. 'mcScaleReMask' of N+4 octets to N+5 octets is a bitmap for REs in the PRB of the one MC chunk, and each bit setting of mcScaleReMask is 'mcScaleOffset' and 'csf' are U- It can indicate whether it is applicable to the RE sent as a Plane message (e.g., '0'=not applicable, '1'=applicable). 'csf' of N+5 octets indicates whether the constellation for the one MC chunk is shifted, and 'mcScaleOffset' of N+5 octets to N+6 octets indicates the scale value for the one MC chunk. The scale value can be derived by calculating Equation 3 to Equation 4 from the 15-bits of the 'mcScaleOffset' field.

'numMcSymbolChunks' for the second 'numMcPrbc' field indicates the number of one or more symbol chunks in the second PRB chunk. For example, the number of the one or more symbol chunks in the second PRB chunk may be 1. 'numMcSymbol' of N+3 octets indicates the number of PRBs in the second PRB chunk and the corresponding symbol chunk. The second PRB chunk and the symbol chunk may point to another MC chunk. 'mcScaleReMask' of N+10 octets to N+11 octets is a bitmap for REs in the PRB of the one MC chunk, and each bit setting of mcScaleReMask is 'mcScaleOffset' and 'csf' are U- It can indicate whether it is applicable to the RE sent as a Plane message (e.g., '0'=not applicable, '1'=applicable). 'csf' of N+11 octets indicates whether the constellation for the one MC chunk is shifted, and 'mcScaleOffset' of N+11 to N+12 octets indicates the scale value for the one MC chunk. The scale value can be derived by calculating Equation 3 to Equation 4 from the 15-bits of the 'mcScaleOffset' field.

According to one embodiment, the DU 210 may use 'mcScaleReMask' and configure the section 850 with 4 MC chunks with a period. Two PRB chunks may be configured within one section, and two symbol chunks may be configured within each PRB chunk. The 'period flag' parameter for each PRB chunk can be used. For example, to indicate MC chunks according to the section division shown in FIG. 8B, section extension information may be configured as in the table below.

In the example shown in Figure 8B, section 850 may consist of 7 PRBs and 10 symbols. Here, A=4, B=3, C=5, D=5. Based on the table and FIG. 8B, the first MC chunk 851 can be specified by 4 PRBs (A=4) and 5 (C=5) symbols. Here, since 'mcPrbPeriod' is 1, the interval between PRBs among the four PRBs may be 1. As an example, the first MC chunk 851 may occupy PRB #0, PRB #2, PRB #4, and PRB #6. Since 'mcSymbPeriod' is 0, the interval between two symbols among the five symbols may be 0. That is, the first MC chunk 851 may occupy five consecutive symbols. As an example, the first MC chunk 851 may occupy symbol #0, symbol #1, symbol #2, symbol #3, and symbol #4.

Based on the above table and FIG. 8B, the second MC chunk 852 can be specified with 4 PRBs (A=4) and 5 (D=5) symbols. Here, since 'mcPrbPeriod' is 1, the interval between PRBs among the four PRBs may be 1. As an example, the second MC chunk 852 may occupy PRB #0, PRB #2, PRB #4, and PRB #6. Since 'mcSymbPeriod' is 0, the interval between two symbols among the five symbols may be 0. That is, the second MC chunk 852 may occupy five consecutive symbols. As an example, the second MC chunk 852 may occupy symbol #5, symbol #6, symbol #7, symbol #8, and symbol #9.

Based on the table and FIG. 8B, the third MC chunk 853 can be specified with three PRBs (B=3) and five (C=5) symbols. Here, since 'mcPrbPeriod' is 1, the interval between PRBs among the three PRBs may be 1. As an example, the third MC chunk 853 may occupy PRB #1, PRB #3, and PRB #5. Since 'mcSymbPeriod' is 1, the interval between two symbols among the five symbols may be 1. That is, the third MC chunk 853 can occupy 5 symbols. As an example, the third MC chunk 853 may occupy symbol #0, symbol #2, symbol #4, symbol #6, and symbol #8.

Based on the table and FIG. 8B, the fourth MC chunk 854 can be specified with 3 PRBs (B=3) and 5 (D=5) symbols. Here, since 'mcPrbPeriod' is 1, the interval between PRBs among the three PRBs may be 1. As an example, the fourth MC chunk 854 may occupy PRB #1, PRB #3, and PRB #5. Since 'mcSymbPeriod' is 1, the interval between two symbols among the five symbols may be 1. That is, the fourth MC chunk 854 can occupy 5 symbols. As an example, the fourth MC chunk 854 may occupy symbol #1, symbol #3, symbol #5, symbol #7, and symbol #8.

According to an additional embodiment, octets corresponding to zero padding in Tables 11 to 15 (e.g., octets N+7 in Table 14, octets N+8, N+13, N+20, N+25 in Table 15) A format in which some areas of is reduced and all parameters are arranged sequentially can also be understood as an embodiment of the present disclosure.

9A-9B show an example of a third way to divide a section, according to embodiments. One section can be divided into one or more MC chunks. The third method refers to a method in which MC chunks are configured in units of arbitrary PRB chunks and symbol chunks, unlike the first method and the second method.

Referring to FIG. 9A, the section 900 may be specified as a resource area defined by the 'numPrbc' parameter 910 and the 'numSymbol' parameter 920. The 'numPrbc' parameter 910 indicates the number of PRBs. The 'numSymbol' parameter 920 represents the number of symbols. Section 900 may be divided into multiple MC chunks. Hereinafter, to describe the MC chunk, parameters for specifying the MC chunk may first be used. At least some or all of the parameters described below may be used to specify (or distinguish) an MC chunk. The following parameters can be exemplified. The parentheses next to the parameter name indicate an example number of bits.

numMcChunks(4b): Number of MC chunks [number of MC chunks]

startMcPrbc(10b): Start PRB for a chunk [start PRB for a chunk]

numMcPrbc(8b): Number of PRBs for the chunk. '0' represents numPrbc. [number of PRBs for a chunk, ‘0’ means numPrbc]

mcPrbPeriod(2b): PRB chunk period. The above parameters can be set for PRB chunks every RB, every other RB (i.e. PRB interval is one PRB), every 2RB (i.e. PRB interval is two PRBs), or every 4RB (i.e. PRB interval is four PRBs). s) can indicate whether it is used or not. 0 = every RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs (maybe none if all RBs are always used). It indicates if every RBs, every other RBs, every 2 RBs, or every 4 RBs is used for a PRB chunk. 0 = every RBs, 1 = every other RBs, 2 = every 2 RBs, 3 = every 4 RBs. (can be absent when always every RB is used.)

startMcSymbol(4b): Start symbol index for MC chunk. [start symbol index for a MC chunk]

numMcSymbol(4b): Number of symbols for MC chunk. ‘0’ represents numSymbol [number of symbols for a MC chunk, ‘0’ means numSymbol]

mcSymbPeriod(2b): The above parameter can be set to every symbol, every other symbol (i.e. symbol spacing is one symbol), every two symbols (i.e. symbol spacing is two symbols), or for symbol chunks with the same symbol range. It can indicate whether every 4 symbols are used (i.e., a symbol interval of 4 symbols). 0 = all symbols, 1 = all other symbols, 2 = every 2 symbols, 3 = every 4 symbols (maybe absent if all symbols are always used). [It indicates if every symbol, every other symbol, every 2 symbols, or every 4 symbols is used for a symbol chunk having the same same symbol range. 0 = every symbol, 1 = every other symbol, 2 = every 2 symbols, 3 = every 4 symbols. (can be absent when always every symbol is used.)]

mcRemaskOnOff(1b): Indicates whether a section expansion or MC chunk has mcScaleRemask. Through the above field, the format of the section extension type of the C-plane message, which will be described later, can be changed (can be omitted). This indicates there are mcScaleRemask in this section extension or MC chunk (format of section extension type with this field) (can be absent)

numMcRemask(4b): Indicates the number of mcScaleRemask within a section extension or MC chunk. (If all REs in a MC chunk share the same CSF and modCompScaler, it can be omitted) [This indicates the number of mcScaleRemask in this section extension or MC chunk (can be absent when all REs in a MC chunk shares the same CSF and modCompScaler.)]

mcScaleReMask(12b): Indicates the RE mask of each RE of the PRB to which the corresponding csf/scaler is applied. This indicates RE mask of each RE in a PRB which appling the corresponding csf/scaler.

periodFlag(1b): Indicates whether to use mcSymbolPeriod and mcPrbPeriod per section extension or MC chunk (can be omitted). It indicates if mcSymbolPeriod and mcPrbPeriod are used or not for each section extension or MC chunk. (can be absent)

According to one embodiment, mcRemaskOnOff and numMcRemask may exist together within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk). According to one embodiment, only one mcRemaskOnOff and numMcRemask may exist within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk). According to one embodiment, mcRemaskOnOff and numMcRemask may not exist within each section extension and/or MC chunk (e.g., symbol chunk or PRB chunk).

According to one embodiment, mcRemaskOnOff and numMcRemask may be included together within each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, mcRemaskOnOff and numMcRemask can both be included in each section extension. For example, mcRemaskOnOff and numMcRemask may both be included in an MC chunk (e.g. symbol chunk or PRB chunk).

According to one embodiment, at least one of mcRemaskOnOff and numMcRemask may be included within each section extension (or MC chunk (eg, symbol chunk or PRB chunk)). For example, at least one of mcRemaskOnOff and numMcRemask may both be included in each section extension. For example, at least one of mcRemaskOnOff and numMcRemask may be included in an MC chunk (e.g., symbol chunk or PRB chunk).

According to one embodiment, both mcRemaskOnOff and numMcRemask may not be included within a section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, mcRemaskOnOff and numMcRemask may be included in fields that are distinct from section extensions (or MC chunks (e.g. symbol chunks or PRB chunks)).

According to one embodiment, if resources are periodically allocated in the time domain within one section, a parameter (eg, 'mcSymbolPeriod' parameter) for a symbol chunk may be defined. Additionally, according to one embodiment, if resources are allocated at regular intervals in the frequency domain within one section, a parameter (e.g., 'mcPrbPeriod' parameter) for the PRB chunk may be defined. In the above embodiments, the periodFlag value may or may not exist in each section extension or MC chunk (symbol chunk or PRB chunk) depending on the embodiment. Meanwhile, in the above-described embodiments, one flag parameter is described, but according to another embodiment, separate flag parameters for mcSymbolPeriod and mcPrbPeriod may exist.

According to one embodiment, the plurality of MC chunks may include a first MC chunk (931), a second MC chunk (932), a third MC chunk (933), and a fourth MC chunk (934). For example, the first MC chunk 931 may be specified by numMcSymbol(0) and numMcPrbc(0). The second MC chunk 932 may be specified by numMcSymbol(1) and numMcPrbc(1). The third MC chunk 933 can be specified by numMcSymbol(2) and numMcPrbc(2). The fourth MC chunk 934 can be specified by numMcSymbol(3) and numMcPrbc(3).

The DU 210 may generate section extension information including at least one of the parameters in order to indicate an MC chunk divided according to the first method. The DU 210 may transmit a C-plane message including the section extension information to the RU 220.

According to one embodiment, DU 210 may configure section 950 of FIG. 9B with three MC chunks without using 'mcScaleReMask'. Section 950 may include a first MC chunk (931), a second MC chunk (932), and a third MC chunk (933). For example, to indicate the three MC chunks, section extension information may be structured as shown in the table below.

For example, the first MC chunk 931 may be specified by numMcSymbol(0) and numMcPrbc(0). The start symbol of one or more symbols of numMcSymbol(0) may be indicated by startMcSymbol(0). The start PRB of one or more PRBs of numMcPrbc(0) may be indicated by startMcPrbc(0). 'modCompScaler' of octets N+6 to N+7 represents the scale value for the first MC chunk (931). The scale value can be derived by calculating Equation 1 to Equation 2 from the 15-bits of the 'modCompScaler' field. For example, the second MC chunk 932 may be specified by numMcSymbol(1) and numMcPrbc(1). The start symbol of one or more symbols of numMcSymbol(1) may be indicated by startMcSymbol(1). The start PRB of one or more PRBs of numMcPrbc(1) may be indicated by startMcPrbc(1). 'modCompScaler' in octets N+12 to N+13 represents the scale value for the second MC chunk (932). The scale value can be derived by calculating Equation 1 to Equation 2 from the 15-bits of the 'modCompScaler' field. For example, the third MC chunk 933 may be specified by numMcSymbol(2) and numMcPrbc(2). The start symbol of one or more symbols of numMcSymbol(2) may be indicated by startMcSymbol(2). The start PRB of one or more PRBs of numMcPrbc(2) may be indicated by startMcPrbc(2). 'modCompScaler' in octets N+13 to N+14 represents the scale value for the third MC chunk (933). The scale value can be derived by calculating Equation 1 to Equation 2 from the 15-bits of the 'modCompScaler' field.

According to one embodiment, DU 210 may use 'mcScaleReMask' and configure section 950 of FIG. 9B with three MC chunks. For example, to indicate the three MC chunks, section extension information may be structured as shown in the table below.

For example, the first MC chunk 931 may be specified by numMcSymbol(0) and numMcPrbc(0). The start symbol of one or more symbols of numMcSymbol(0) may be indicated by startMcSymbol(0). The start PRB of one or more PRBs of numMcPrbc(0) may be indicated by startMcPrbc(0). 'mcScaleReMask' of octets N+6 to N+7 indicates masking information for the first MC chunk (931). 'csf' of octet N+7 indicates whether the constellation is shifted for the first MC chunk (931), and 'mcScaleOffset' of octets N+7 to N+9 is the scale value for the first MC chunk (931) represents. The scale value can be derived from the 15-bits of the 'mcScaleOffset' field according to the calculation of Equation 3 to Equation 4. For example, the second MC chunk 932 has numMcSymbol(1) and numMcPrbc(1 ) can be specified by. The start symbol of one or more symbols of numMcSymbol(1) may be indicated by startMcSymbol(1). The start PRB of one or more PRBs of numMcPrbc(1) may be indicated by startMcPrbc(1). 'mcScaleReMask' of octets N+14 to N+15 represents masking information for the second MC chunk (932). 'csf' of octet N+15 indicates whether the constellation is shifted for the second MC chunk (932), and 'mcScaleOffset' of octets N+15 to N+17 is the scale value for the second MC chunk (932). represents. The scale value can be derived from the 15-bits of the 'mcScaleOffset' field according to the calculation of Equation 3 to Equation 4. For example, the third MC chunk 933 has numMcSymbol(2) and numMcPrbc(2). ) can be specified by. The start symbol of one or more symbols of numMcSymbol(2) may be indicated by startMcSymbol(2). The start PRB of one or more PRBs of numMcPrbc(2) may be indicated by startMcPrbc(2). 'mcScaleReMask' of octets N+22 to N+23 represents masking information for the third MC chunk (933). 'csf' of octet N+23 indicates whether the constellation is shifted for the 3rd MC chunk (933), and 'mcScaleOffset' of octets N+23 to N+24 is the scale value for the 3rd MC chunk (933) represents. The scale value can be derived from the 15-bits of the 'mcScaleOffset' field according to calculations of Equation 3 to Equation 4.

Figure 10 shows an example of section division for periodic resource allocation, according to embodiments. In Figure 10, a situation in which periodic resource allocation is applied in section division using the third method is described.

Referring to FIG. 10, the section 1000 may be specified as a resource area defined by the 'numPrbc' parameter and the 'numSymbol' parameter 1020. For example, the 'numPrbc' parameter could point to 6. Section 1000 may be composed of six PRBs (1011, 1012, 1013, 1014, 1015, 1016). Section 1000 may include six symbols 1021, 1022, 1023, 1024, 1025, and 1026.

According to one embodiment, DU 210 uses 'mcScaleReMask', 'mcPrbPeriod', and 'mcSymbolPeriod' to configure three MC chunks (1031, 1033, 1035) within one section (1000). You can (configure). The DU 210 may generate section extension information including at least one of the parameters described in FIG. 9A to indicate each MC chunk divided according to the third method. The DU 210 may transmit a C-plane message including the section extension information to the RU 220.

For example, to indicate the three MC chunks, section extension information may be structured as shown in the table below. At this time, as an example, periodFlag may be omitted.

'extType' indicates the type of section extension information. 'extLen' indicates the length of the section extension information. 'numMcChunks' can indicate the number of MC chunks. For example, 'numMcChunks' could be 3. The MC chunks may include a first MC chunk (1031), a second MC chunk (1033), and a third MC chunk (1035). For example, the first MC chunk (1031) is numMcSymbol(0) and numMcPrbc(0). The start symbol of one or more symbols of numMcSymbol(0) may be indicated by startMcSymbol(0). The start PRB of one or more PRBs of numMcPrbc(0) may be indicated by startMcPrbc(0). Here, since 'mcSymbPeriod' is 1, the interval between two symbols in the first MC chunk (1031) may be one symbol. Since 'mcPrbPeriod' is 1, the interval between PRBs in the first MC chunk (1031) can be one PRB.

For example, the second MC chunk 1033 may be specified by numMcSymbol(2) and numMcPrbc(2). The start symbol of one or more symbols of numMcSymbol(2) may be indicated by startMcSymbol(2). The start PRB of one or more PRBs of numMcPrbc(1) may be indicated by startMcPrbc(1). Here, since 'mcSymbPeriod' is 1, the interval between two symbols in the second MC chunk (1033) can be one symbol. Since 'mcPrbPeriod' is 1, the interval between PRBs in the second MC chunk (1033) can be one PRB.

For example, the third MC chunk 1035 may be specified by numMcSymbol(2) and numMcPrbc(2). The start symbol of one or more symbols of numMcSymbol(2) may be indicated by startMcSymbol(2). The start PRB of one or more PRBs of numMcPrbc(2) may be indicated by startMcPrbc(2). Here, since 'mcSymbPeriod' is 1, the interval between two symbols in the first MC chunk (1031) may be one symbol. Since 'mcPrbPeriod' is 0, PRBs can be allocated consecutively in the first MC chunk (1031).

According to an additional embodiment, octets corresponding to zero padding in Tables 16 to 18 (e.g., octets N+9, N+17 in Table 17, octets N+6, N+10, N+19 in Table 18, A format in which some areas of (N+24) are reduced and all parameters are arranged sequentially can also be understood as an embodiment of the present disclosure.

5A to 10 , various examples of section extension information according to resource partitioning methods are described, but embodiments of the present disclosure are not limited thereto. In addition to the specified method, a section division method using a format mode can be used. According to one embodiment, the mode parameter value may indicate a specific format of section extension information. For example, when the mode parameter value is 0, section extension information having the format of Table 6 or Table 7 can be used. Additionally, for example, when the mode parameter value is 1, section expansion information having the format of Table 2 or Table 3 can be used. Additionally, for example, when the mode parameter value is 2, section expansion information having the format of Table 3 or Table 4 can be used.

For example, when the mode parameter indicates 0, section extension information such as the table below can be used.

In section extension information having the format of Table 7, a field indicating a mode parameter may be added to the N+2 octet area. For descriptions of other parameters, Table 7 and the description for Table 7 may be referred to. As another example, when the mode parameter indicates 1, section expansion information such as the table below may be used.

In section extension information having the format of Table 9, a field indicating a mode parameter may be added to the N+2 octet area. For descriptions of other parameters, Table 9 and the description for Table 9 may be referred to. In Table 9, the 'numMcPrbChunk' parameter may be omitted. According to an additional embodiment, some areas of the octet (e.g., octet N+8) corresponding to zero padding in Tables 19 and 20 are reduced, and the parameters are all continuous. The format arranged as can also be understood as an embodiment of the present disclosure. Through this, at least some of the parameters in Tables 19 and 20 may be omitted, or the positions of at least some of the parameters may be changed. According to an additional embodiment, octets corresponding to zero padding in Tables 11 to 15 (e.g., octets N+7 in Table 14, octets N+8, N+13, N+20, N+25 in Table 15) A format in which some areas of is reduced and all parameters are arranged sequentially can also be understood as an embodiment of the present disclosure.

11 shows an example of modulation compression for a subblock, according to embodiments.

Referring to FIG. 11 and FIG. 5A, the DU 210 includes an M-plane message generator 1111, an MC chunk-based scheduling unit 1113, a C-plane message generator 1115, and a U-plane message generator. It may include a message generator 1117. The M-plane message generator 1111 may generate an M-plane message containing at least one parameter required for a modulation compression technique configured in MC chunk units. The M-plane message generator 1111 may transmit the at least one parameter to the RU 220. According to one embodiment, the M-plane message generator 1111 includes information indicating whether the DU 210 supports new section extension information (e.g., one of the formats of Tables 6 to 20). M-plane messages can be created. Additionally, according to one embodiment, the M-plane message generator 1111 may generate an M-plane message including at least one of the parameters described in FIGS. 7A to 9B. Afterwards, the DU 210 may transmit an M-plane message to the RU 220.

The MC chunk-based scheduling unit 1113 can perform scheduling for C-plane messages and U-plane messages according to the modulation compression technique described above. The C-plane message generator 1115 may generate a C-plane message including section extension information according to the modulation compression technique described with reference to FIGS. 6 to 10. According to one embodiment, the C-plane message generator 1115 may generate section extension information specific to an MC chunk constituting a partial area within one section. The section extension information may include resource area information (e.g., number of symbols, number of PRBs) for the MC chunk and modulation compression information to be applied to data occupied by the MC chunk. For example, the C-plane message generator 1115 may generate a C-plane message including section extension information with a format for indicating one or more MC chunks, as shown in Tables 6 to 20. The U-plane message generator 1117 may generate a U-plane message including an I component and a Q component according to the modulation compression technique. The U-plane message may include data to be transmitted on the area occupied by the MC chunk.

The RU (220) may include an M-plane message generation unit 1121, a C-plane analysis unit 1123, a buffer 1125, a U-plane analysis unit 1127, and a modulation decompression unit 1129. there is. The M-plane message generator 1121 may generate an M-plane message including at least one parameter required for a modulation compression technique configured in MC chunk units. The M-plane message generator 1121 may transmit the at least one parameter to the DU 210. According to one embodiment, the M-plane message generator 1121 includes information indicating whether the RU 220 supports new section extension information (e.g., one of the formats of Tables 6 to 20). M-plane messages can be created. Additionally, according to one embodiment, the M-plane message generator 1121 may generate an M-plane message including at least one of the parameters described in FIGS. 7A to 9B. Afterwards, the RU 220 may transmit an M-plane message to the DU 210.

The C-plane analysis unit 1123 may receive a C-plane message from the DU 210. The C-plane analysis unit 1123 may obtain parameter(s) related to modulation compression from section extension information (e.g., Tables 6 to 20) included in the C-plane message. The C-plane analysis unit 1123 may obtain parameter(s) related to modulation compression for each MC chunk within one section. The C-plane analysis unit 1123 can obtain section information from the C-plane message. The C-plane analysis unit 1123 can identify the time-frequency resource area occupied by each MC chunk from the section extension information of the C-plane message. The C-plane analysis unit 1123 may include modulation compression information ('modCompScaler', 'mcScaleReMask', 'mcScaleOffset') for data to be applied to the time-frequency resource area. The C-plane analysis unit 1123 may store the parameter(s) related to the modulation compression and the section information in the buffer 1125. The U-plane analysis unit 1127 may receive a U-plane message from the DU 210. The U-plane analysis unit 1127 may include the I component and Q component included in the U-plane message. The modulation decompression unit 1129 may obtain the parameter(s) related to the modulation compression and the section information from the buffer 1125. The modulation decompression unit 1129 may obtain the I component and Q component from the U-plane analysis unit 1127. The modulation decompression unit 1129 may obtain a bit stream for the I component and a bit stream for the Q component based on the parameters related to the modulation compression. For example, when decompressing, the modulation decompression unit 1129 may 'unshift' the constellation according to the 'csf' value and apply a scale factor for the constellation type indicated in the section. . One section has one or two modulation types. The modulation type can be inferred from the reMask bits. Each '1' bit in the reMask bits represents a shift command ('csf') and a scale factor (e.g. 'modCompScaler', or 'mcScaleOffset' when using 'mcScaleReMask') for the REs of the PRB.

Figure 12 shows an example of signaling between a DU (eg, DU 210) and a RU (eg, RU 220) to provide compressed information using an identifier (ID), according to embodiments. The compressed information may be specified for each subblock within one section. The subblock is a unit to which modulation compression is applied and may be referred to as an MC chunk.

According to one embodiment, ID-based section extension information may be used. Here, the ID may be associated with the MC chunk and modulation compression information for the MC chunk in the above-described embodiments. Through the ID, overhead due to repeated compression information in the data of the U-plane message can be reduced. Multiple MC chunks may be configured within one section. Compression information (e.g., constellation shift flag and scaler value) may be assigned to each MC chunk. After the area information for the MC chunk (e.g., the number of symbols of the MC chunk and the number of PRBs of the MC chunk) and the modulation compression information for the MC chunk are transmitted once through the first C-plane message, thereafter, the MC chunk Indication of area information or modulation compression information can be performed using only ID. Section extension information including the ID may be newly defined.

Referring to FIG. 12, in operation 1201, the DU 210 may transmit a C-plane message including MC chunk-based compression information and ID to the RU 220. As an example, the C-plane message may be transmitted in slots A-X. The MC chunk-based compression information refers to compression information specific to the MC chunk. The section extension information of the C-plane message may include at least one parameter for indicating an MC chunk (e.g., the number of symbols in the MC chunk, the number of PRBs in the MC chunk). The section extension information of the C-plane message may include compression information specific to the MC chunk (e.g., 'csf' parameter, 'modCompScaler' parameter, or 'mcScaleOffset' parameter). The section extension information of the C-plane message may include an ID associated with the compressed information. According to one embodiment, the ID may be associated with compressed information. Additionally, according to one embodiment, the ID may be associated with the compressed information and the MC chunk.

According to one embodiment, the RU 220 receives the ID value from the DU 210 and stores modulation compression information (e.g., modulation compression information) corresponding to the ID in a storage space (e.g., buffer 1125, memory 370). constellation shift flag and scaler value) can be stored.

In operation 1203, the DU 210 may transmit a U-plane message containing data to the RU 220. The U-plane message may be coupled with the C-plane message of operation 1201. As an example, the C-plane message may be transmitted in slot A. The data may be transmitted on the scheduling area (eg, MC chunk) of the C-plane message. The RU 220 may perform decompression of the data based on the compression information in operation 1201. Although not shown in FIG. 12, the RU 220 may transmit the data obtained through the decompression to a terminal (eg, the terminal 120).

Thereafter, in operation 1211, the DU 210 may transmit a C-plane message including the ID to the RU 220. As an example, the C-plane message may be transmitted in slot B-X. The DU 210 can provide modulation compression information to the RU 220 by transmitting only the ID value to the RU 220. The RU 220 receives the ID value from the DU 210 and modulation compression information (e.g., constellation shift flag and scaler) corresponding to the ID stored in a storage space (e.g., buffer 1125, memory 370). value) can be identified.

In operation 1213, the DU 210 may transmit a U-plane message containing data to the RU 220. The U-plane message may be coupled with the C-plane message of operation 1211. As an example, the C-plane message may be transmitted in slot B. The data may be transmitted on the scheduling area (eg, MC chunk) of the C-plane message. The RU 220 may perform decompression on the data based on modulation compression information (eg, constellation shift flag and scaler value) corresponding to the ID.

Thereafter, in operation 1221, the DU 210 may transmit a C-plane message including the ID to the RU 220. As an example, the C-plane message may be transmitted in slot C-X. The RU 220 receives the ID value from the DU 210 and modulation compression information (e.g., constellation shift flag and scaler) corresponding to the ID stored in a storage space (e.g., buffer 1125, memory 370). value) can be identified.

In operation 1223, the DU 210 may transmit a U-plane message containing data to the RU 220. The U-plane message may be coupled with the C-plane message of operation 1221. As an example, the C-plane message may be transmitted in slot C. The data may be transmitted on the scheduling area (eg, MC chunk) of the C-plane message. The RU 220 may perform decompression on the data based on modulation compression information (eg, constellation shift flag and scaler value) corresponding to the ID.

According to one embodiment, the ID depicted in FIG. 12 may designate various information as well as modulation compression information. For example, for the ID, at least one of the following parameters may be included in the section extension information.

1) mcInfoId: Consists of random N bits and specifies csf and scaler information. As an example, scalar information may include a 'modCompScaler' parameter, or a 'mcScaleOffset' parameter.

2) mcRemaskId: Consists of random M bits and specifies remask information. As an example, remask information may include the 'mcScaleRemask' parameter.

3) mcId: Consists of random P bits and specifies csf, scaler, and remask information.

4) chunkandmcinfoId: Consists of random Q bits and specifies the resource area information and modulation compression information (e.g. csf and scaler information) of the MC chunk. As an example, scalar information may include a 'modCompScaler' parameter, or a 'mcScaleOffset' parameter.

Depending on the example, each ID may be present in all, only in part, or not at all. Additionally, the bitwidth (e.g., N, M, P, Q) of each ID may be predetermined according to the O-RAN standard or may be determined in advance through a negotiation process of an M-plane message. The RU may require a storage device (e.g., memory, buffer) to store the above-described ID and compressed information or masking information corresponding to the ID. Additionally, in addition to the IDs described above, an ID for specifying at least one of the parameters described through FIGS. 6 to 10 may be used. Additionally, ID parameters of other definitions may replace the IDs described above.

By providing specific modulation compression information to some resource areas of a section, the amount of fronthaul transmission between DU and RU can be reduced. In addition, since additional section allocation is not required, the packet processing burden can be reduced in each DU and RU. Additionally, when the modulation compression technique and other compression techniques are operated in a dynamic manner, section fragmentation does not occur, so efficient scheduling for configuring sections can be achieved.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

In embodiments, a method performed by a distributed unit (DU) in a wireless communication system may include identifying a subblock within one section. The method may include generating a control-plane (C-plane) message including section extension information including modulation compression information corresponding to the subblock. The method may include transmitting the C-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

According to one embodiment, the one section may include a plurality of subblocks. The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. It may contain information indicating the number.

According to one embodiment, the subblock may include at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs. Within the one section, the one or more symbols may be assigned to be separated by the period indicated by the first parameter. Within the one section, the one or more PRBs may be allocated to be separated by the interval indicated by the second parameter.

According to one embodiment, the section extension information may include identification information linked to the modulation compression information. The method may include transmitting another C-plane message including the identification information to the RU. The method may include transmitting a U-plane message coupled with the other C-plane message to the RU. Data of the U-plane message may be compressed based on the modulation compression information corresponding to the identification information.

According to one embodiment, the scale information may include 15 bits to indicate a scale value. Alternatively, the scale information may include 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.

In embodiments, a method performed by a radio unit (RU) in a wireless communication system transmits a control-plane (C-plane) message including section extension information from a distributed unit (DU) through a fronthaul interface. It may include a receiving operation. The method may include an operation of identifying modulation compression information corresponding to a subblock within one section in the section extension information. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

According to one embodiment, the one section may include a plurality of subblocks. The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. It may contain information indicating the number.

According to one embodiment, the subblock may include at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs. Within the one section, the one or more symbols may be assigned to be separated by the period indicated by the first parameter. Within the one section, the one or more PRBs may be allocated to be separated by the interval indicated by the second parameter.

According to one embodiment, the section extension information may include identification information linked to the modulation compression information. The method may include receiving another C-plane message including the identification information from the DU. The method may include receiving a U-plane message coupled with the other C-plane message from the DU. Data of the U-plane message may be decompressed based on the modulation compression information corresponding to the identification information.

According to one embodiment, the scale information may include 15 bits to indicate a scale value. Alternatively, the scale information may include 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.

In embodiments, an electronic device of a distributed unit (DU) in a wireless communication system may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to identify subblocks within one section. The at least one processor may be configured to generate a control-plane (C-plane) message including section extension information including modulation compression information corresponding to the subblock. The at least one processor may be configured to transmit the C-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

According to one embodiment, the one section may include a plurality of subblocks. The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. It may contain information indicating the number.

According to one embodiment, the subblock may include at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs. Within the one section, the one or more symbols may be assigned to be separated by the period indicated by the first parameter. Within the one section, the one or more PRBs may be allocated to be separated by the interval indicated by the second parameter.

According to one embodiment, the section extension information may include identification information linked to the modulation compression information. The at least one processor may be configured to transmit another C-plane message including the identification information to the RU. The at least one processor may be configured to transmit a U-plane message coupled with the other C-plane message to the RU. Data of the U-plane message may be compressed based on the modulation compression information corresponding to the identification information.

According to one embodiment, the scale information may include 15 bits to indicate a scale value. Alternatively, the scale information may include 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.

In embodiments, an electronic device of a radio unit (RU) in a wireless communication system may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to receive a control-plane (C-plane) message including section extension information from a distributed unit (DU) through a fronthaul interface. The at least one processor may be configured to identify modulation compression information corresponding to a subblock within one section in the section extension information. The modulation compression information may include a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock. The section extension information may include information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock.

According to one embodiment, the one section may include a plurality of subblocks. The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. It may contain information indicating the number.

According to one embodiment, the subblock may include at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs. Within the one section, the one or more symbols may be assigned to be separated by the period indicated by the first parameter. Within the one section, the one or more PRBs may be allocated to be separated by the interval indicated by the second parameter.

According to one embodiment, the section extension information may include identification information linked to the modulation compression information. The at least one processor may be configured to receive another C-plane message including the identification information from the DU. The at least one processor may be additionally configured to receive a U-plane message coupled with the other C-plane message from the DU. Data of the U-plane message may be decompressed based on the modulation compression information corresponding to the identification information.

According to one embodiment, the scale information may include 15 bits to indicate a scale value. Alternatively, the scale information may include 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.

Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) may include random access memory, non-volatile memory, including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.

In addition, the program may be distributed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communications network may be connected to the device performing embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present disclosure.

*

Claims (20)

In a method performed by a distributed unit (DU) in a wireless communication system,
An operation to identify a subblock within one section,
Generating a control-plane (C-plane) message including section extension information including modulation compression information corresponding to the subblock;
Including transmitting the C-plane message to a radio unit (RU) through a fronthaul interface,
The modulation compression information includes a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock,
The section extension information includes information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock,
method.
In claim 1,
The one section includes a plurality of subblocks,
The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. Further including information indicating the number,
method.
In claim 1,
The subblock includes at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs,
Within the one section, the one or more symbols are assigned to be separated by the period indicated by the first parameter,
Within the one section, the one or more PRBs are allocated to be separated by the interval indicated by the second parameter,
method.
In claim 1,
The section expansion information further includes identification information linked to the modulation compression information,
The above method is:
An operation of transmitting another C-plane message including the identification information to the RU;
Further comprising transmitting a U-plane message coupled with the other C-plane message to the RU,
The data of the U-plane message is compressed based on the modulation compression information corresponding to the identification information,
method.
In claim 1,
The scale information includes 15 bits to indicate a scale value, or
The scale information includes 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.
method.
In a method performed by a radio unit (RU) in a wireless communication system,
An operation of receiving a control-plane (C-plane) message including section extension information from a distributed unit (DU) on a fronthaul interface;
In the section expansion information, identifying modulation compression information corresponding to a subblock within one section,
The modulation compression information includes a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock,
The section extension information includes information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock,
method.
In claim 6,
The one section includes a plurality of subblocks,
The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. Further including information indicating the number,
method.
In claim 6,
The subblock includes at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs,
Within the one section, the one or more symbols are assigned to be separated by the period indicated by the first parameter,
Within the one section, the one or more PRBs are allocated to be separated by the interval indicated by the second parameter,
method.
In claim 6,
The section expansion information further includes identification information linked to the modulation compression information,
The above method is:
An operation of receiving another C-plane message including the identification information from the DU;
Further comprising the operation of receiving a U-plane message coupled with the other C-plane message from the DU,
The data of the U-plane message is decompressed based on the modulation compression information corresponding to the identification information,
method.
In claim 6,
The scale information includes 15 bits to indicate a scale value, or
The scale information includes 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.
method.
In the electronic device of a distributed unit (DU) in a wireless communication system,
at least one transceiver,
Comprising at least one processor coupled to the at least one transceiver,
The at least one processor,
Identify subblocks within a section,
Generating a control-plane (C-plane) message including section extension information including modulation compression information corresponding to the subblock,
Configured to transmit the C-plane message to a radio unit (RU) through a fronthaul interface,
The modulation compression information includes a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock,
The section extension information includes information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock,
Electronic devices.
In claim 11,
The one section includes a plurality of subblocks,
The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. Further including information indicating the number,
Electronic devices.
In claim 11,
The subblock includes at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs,
Within the one section, the one or more symbols are assigned to be separated by the period indicated by the first parameter,
Within the one section, the one or more PRBs are allocated to be separated by the interval indicated by the second parameter,
Electronic devices.
In claim 11,
The section expansion information further includes identification information linked to the modulation compression information,
The at least one processor,
Sending another C-plane message containing the identification information to the RU,
Additionally configured to transmit a U-plane message coupled with the other C-plane message to the RU,
The data of the U-plane message is compressed based on the modulation compression information corresponding to the identification information,
Electronic devices.
In claim 11,
The scale information includes 15 bits to indicate a scale value, or
The scale information includes 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.
Electronic devices.
In the electronic device of a radio unit (RU) in a wireless communication system,
at least one transceiver,
Comprising at least one processor coupled to the at least one transceiver,
The at least one processor,
The fronthaul interface receives a control-plane (C-plane) message containing section extension information from a distributed unit (DU),
In the section expansion information, it is configured to identify modulation compression information corresponding to a subblock within one section,
The modulation compression information includes a flag indicating whether the constellation for the subblock is moved and scale information to be applied to the subblock,
The section extension information includes information indicating the number of one or more symbols of the subblock and information indicating the number of one or more physical resource blocks (PRBs) of the subblock,
Electronic devices.
In claim 16,
The one section includes a plurality of subblocks,
The section extension information includes modulation compression information for the subblock and another subblock among the plurality of subblocks, information indicating the number of one or more symbols of the other subblock, and one or more PRBs of the other subblock. Further including information indicating the number,
Electronic devices.
In claim 16,
The subblock includes at least one of a first parameter indicating a period between symbols or a second parameter indicating an interval between PRBs,
Within the one section, the one or more symbols are assigned to be separated by the period indicated by the first parameter,
Within the one section, the one or more PRBs are allocated to be separated by the interval indicated by the second parameter,
Electronic devices.
In claim 16,
The section expansion information further includes identification information linked to the modulation compression information,
The at least one processor,
Receiving another C-plane message containing the identification information from the DU,
Additionally configured to receive a U-plane message coupled with the other C-plane message from the DU,
The data of the U-plane message is decompressed based on the modulation compression information corresponding to the identification information,
Electronic devices.
In claim 16,
The scale information includes 15 bits to indicate a scale value, or
The scale information includes 15 bits to indicate a scale value and 12 bits to indicate whether the scale value is applied to each RE (resource element) in the PRB.
Electronic devices.