Electronic device and method for providing modulation compression information in fronthaul interface

Abstract

In an embodiment, a method performed by an apparatus of a distributed unit (DU) in a wireless communication system is provided. The method may include the following operations: identifying sub-blocks in a segment; generating a control plane (C-plane) message including segment extension information including modulation compression information corresponding to the sub-blocks; and transmitting the C-plane message to a radio unit (RU) over the fronthaul interface.

Description

Technical Field

[0001] The present disclosure relates to a fronthaul interface. More specifically, the present disclosure relates to an electronic device and a method for providing modulation compression information in a fronthaul interface. Background Art

[0002] As the transmission capacity in a wireless communication system increases, a functional split that separates the functions of a base station is being applied. According to such a functional split, a base station can be split into a distributed unit (DU) and a radio unit (RU). The fronthaul interface is defined for communication between the DU and the RU.

[0003] The above information is presented only as background information to assist in understanding the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above is applicable as prior art with respect to the present disclosure. Summary of the Invention

[0004] Technical Problem

[0005] Aspects of the present disclosure are at least to solve the above problems and / or disadvantages and at least to provide the advantages described below. Accordingly, one aspect of the present disclosure is to provide an electronic device and a method for providing modulation compression information in a fronthaul interface.

[0006] Additional aspects will be set forth in part in the following description, in part will be understood from the description, or may be learned by practice of the presented embodiments.

[0007] According to an aspect of the present disclosure, there is provided a method performed by a distributed unit (DU) in a wireless communication system. The method may include identifying sub-blocks in a section. The method may include generating a control plane (C-plane) message including section extension information, the section extension information including modulation compression information corresponding to the sub-blocks. The method may include sending the C-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag for indicating whether the constellation of the sub-block is shifted and scaling information to be applied to the sub-block. The section extension information may include information for indicating the number of one or more symbols of the sub-block and information for indicating the number of one or more physical resource blocks (PRBs) of the sub-block.

[0008] According to one aspect of the present disclosure, a method performed by a Radio Unit (RU) is provided. The method may include receiving, via a fronthaul interface, a Control Plane (C-plane) message including section extension information from a Distributed Unit (DU). The method may include: identifying modulation compression information corresponding to a sub-block in a section. The modulation compression information may include a flag for indicating whether the constellation of the sub-block is shifted and scaling information to be applied to the sub-block. The section extension information may include information for indicating the number of one or more symbols of the sub-block and information for indicating the number of one or more Physical Resource Blocks (PRBs) of the sub-block.

[0009] According to one aspect of the present disclosure, an electronic device of a Distributed Unit (DU) in a wireless communication system is provided. The electronic device includes 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 a sub-block in a section. The at least one processor may be configured to: generate a Control Plane (C-plane) message including section extension information, the section extension information including modulation compression information corresponding to the sub-block. The at least one processor may be configured to send the C-plane message to a Radio Unit (RU) via a fronthaul interface. The modulation compression information may include a flag for indicating whether the constellation of the sub-block is shifted and scaling information to be applied to the sub-block. The section extension information includes information for indicating the number of one or more symbols of the sub-block and information for indicating the number of one or more Physical Resource Blocks (PRBs) of the sub-block.

[0010] According to one aspect of the present disclosure, an electronic device of a Radio Unit (RU) in a wireless communication system is provided. The electronic device includes 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, via a fronthaul interface, a Control Plane (C-plane) message including section extension information from a Distributed Unit (DU). The at least one processor may be configured to identify modulation compression information corresponding to a sub-block in a section. The modulation compression information may include a flag for indicating whether the constellation of the sub-block is shifted and scaling information to be applied to the sub-block. The section extension information may include information for indicating the number of one or more symbols of the sub-block and information for indicating the number of one or more Physical Resource Blocks (PRBs) of the sub-block.

[0011] According to one aspect of the present disclosure, a method performed by a distributed unit (DU) is provided. The method includes generating a control plane (C-plane) message including section extension information for modulation compression. The method includes sending the C-plane message to a radio unit (RU) via a fronthaul interface. The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first physical resource block (PRB) information for indicating one or more PRBs in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scaling offset information for indicating a first scaling value to be applied to the first sub-block, and first re-masking information for indicating whether the first scaling value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0012] According to one aspect of the present disclosure, a method performed by a radio unit (RU) is provided. The method includes receiving, via a fronthaul interface, from a distributed unit, a control plane (C-plane) message including section extension information for modulation compression. The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first physical resource block (PRB) information for indicating one or more PRBs in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scaling offset information for indicating a first scaling value to be applied to the first sub-block, and first re-masking information for indicating whether the first scaling value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0013] According to one aspect of the present disclosure, there is provided an electronic device of a distributed unit (DU). The electronic device includes at least one transceiver for a fronthaul interface, at least one processor, and a memory configured to store program instructions. The instructions, when executed by the at least one processor, cause the electronic device to perform functions including: generating a control plane (C-plane) message including section extension information for modulation compression; and transmitting the C-plane message to a radio unit (RU) via the fronthaul interface. The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first physical resource block (PRB) information for indicating one or more PRBs in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scaling offset information for indicating a first scaling value to be applied to the first sub-block, and first re-masking information for indicating whether the first scaling value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0014] According to one aspect of the present disclosure, there is provided an electronic device of a radio unit (RU). The electronic device includes at least one transceiver for a fronthaul interface, at least one processor, and a memory configured to store program instructions. The instructions, when executed by the at least one processor, cause the electronic device to perform functions including: receiving, via the fronthaul interface, a control plane (C-plane) message including section extension information for modulation compression from a distributed unit (DU). The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first physical resource block (PRB) information for indicating one or more PRBs in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scaling offset information for indicating a first scaling value to be applied to the first sub-block, and first re-masking information for indicating whether the first scaling value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0015] According to an aspect of the present disclosure, there is provided a non-transitory computer-readable medium including a memory that stores a program including instructions. When the instructions are executed by one or more processors, the instructions cause a distributed unit (DU) to generate a control plane (C-plane) message including section extension information for modulation compression, and send the C-plane message to a radio unit (RU) through a fronthaul interface. The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first PRB information for indicating one or more physical resource blocks (PRBs) in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scale offset information for indicating a first scale value to be applied to the first sub-block, and first re-masking information for indicating whether the first scale value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0016] According to an aspect of the present disclosure, there is provided a non-transitory computer-readable medium including a memory that stores a program including instructions. When the instructions are executed by one or more processors, the instructions cause a radio unit (RU) to receive, through a fronthaul interface, a control plane (C-plane) message including section extension information for modulation compression from a distributed unit (DU). The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first PRB information for indicating one or more physical resource blocks (PRBs) in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scale offset information for indicating a first scale value to be applied to the first sub-block, and first re-masking information for indicating whether the first scale value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0017] From the following detailed description of various embodiments of the present disclosure disclosed in conjunction with the accompanying drawings, other aspects, advantages, and significant features of the present disclosure will become apparent to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A wireless communication system according to an embodiment of the present disclosure is shown.

[0019] Figure 2a A fronthaul interface according to an embodiment of the present disclosure is shown.

[0020] Figure 2b A fronthaul interface of an O-RAN (Open Radio Access Network) according to an embodiment of the present disclosure is shown.

[0021] Figure 3a Shows the functional configuration of a distributed unit (DU) according to an embodiment of the present disclosure.

[0022] Figure 3b Shows the functional configuration of a radio unit (RU) according to an embodiment of the present disclosure.

[0023] Figure 4 Shows an example of the functional split between a DU and an RU according to an embodiment of the present disclosure.

[0024] Figure 5a and Figure 5b Shows an example of modulation compression (MC) according to various embodiments of the present disclosure.

[0025] Figure 6 Shows an example of signaling between a DU and an RU for providing modulation compression information about sub - blocks of a section according to an embodiment of the present disclosure.

[0026] Figure 7a and Figure 7b Each shows an example of a first scheme for dividing a section according to various embodiments of the present disclosure.

[0027] Figure 8a and Figure 8b Each shows an example of a second scheme for dividing a section according to various embodiments of the present disclosure.

[0028] Figures 9a to 9b Each shows an example of a third scheme for dividing a section according to various embodiments of the present disclosure.

[0029] Figure 10 Shows an example of section segmentation for periodic resource allocation according to an embodiment of the present disclosure.

[0030] Figure 11 Shows an example of modulation compression for sub - blocks according to an embodiment of the present disclosure.

[0031] Figure 12 Shows an example of signaling between a DU and an RU for providing compression information using an identifier (ID) according to an embodiment of the present disclosure.

[0032] Throughout the drawings, it should be noted that the same reference numerals are used to depict the same or similar elements, features, and structures. Detailed Description

[0033] The following description with reference to the accompanying drawings helps to comprehensively understand various embodiments of the present disclosure defined by the claims and their equivalents. It includes various specific details to assist understanding, but these are only considered exemplary. Thus, those of ordinary skill in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and configurations may be omitted for clarity and conciseness.

[0034] The terms and words used in the following description and claims are not limited to their bibliographical meanings, but are used by the inventor to achieve a clear and consistent understanding of the present disclosure. Thus, it will be clear to those skilled in the art that the following description of the various embodiments of the present disclosure is for illustrative purposes only and not for limiting the present disclosure defined by the appended claims and their equivalents.

[0035] It should be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly indicates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more such surfaces.

[0036] The terms used in the present disclosure are only for describing specific embodiments and are not intended to limit the scope of other embodiments. Unless the context clearly indicates otherwise, singular expressions may include plural expressions. The terms used herein (including technical or scientific terms) may have the same meaning as commonly understood by those of ordinary skill in the art described in the present disclosure. Among the terms used in the present disclosure, terms defined in a general dictionary may be interpreted as having the same or similar meanings as those they have in the context of the related art, and should not be interpreted as ideal or overly formal meanings unless clearly defined in the present disclosure. In some cases, even if a term is defined in the present disclosure, it should not be interpreted as excluding embodiments of the present disclosure.

[0037] In various examples of the present disclosure described below, hardware methods will be described as examples. However, since various embodiments of the present disclosure may include technologies that utilize both hardware-based methods and software-based methods, they are not intended to exclude software-based methods.

[0038] As used in the following description, in the present disclosure, terms referring to signals (e.g., packets, messages, signals, information, signaling), terms referring to resources (e.g., segments, symbols, time slots, subframes, radio frames, subcarriers, resource elements (REs), resource blocks (RBs), bandwidth parts (BWPs), opportunities), terms referring to operating states (e.g., steps, operations, procedures), terms referring to data (e.g., packets, messages, user flows, information, bits, symbols, codewords), terms referring to channels, terms referring to network entities (distributed unit (DU), radio unit (RU), central unit (CU), control plane (CU-CP), user plane (CU-UP), open radio access network (O-RAN) DU (O-DU), O-RAN RU (O-RU), O-RAN CU (O-CU), O-RAN CU-UP (O-CU-UP), O-RAN CU-CP (O-CU-CP)), terms referring to components of a device or equipment, etc. are given only for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and thus other terms with the same or equivalent technical meanings may be used. In addition, as used herein, terms such as "~ module", "~ unit", "~ segment", "~ part", "~ body", etc. may refer to a structure or unit of at least one shape for processing a specific function.

[0039] In addition, throughout the present disclosure, expressions such as "above" or "below" may be used to determine whether a specific condition is satisfied or achieved, but it is merely a description for illustrative purposes and is not intended to exclude the meanings of "greater than or equal to" or "less than or equal to". A condition described as "greater than or equal to" may be replaced by an expression such as "above", a condition described as "less than or equal to" may be replaced by an expression such as "below", and a condition described as "greater than or equal to and below" may be replaced by "above and less than or equal to". In addition, hereinafter, "A" to "B" means at least one of the elements from A (including A) to B (including B). Hereinafter, "C" and / or "D" means including at least one of "C" or "D", i.e., {"C", "D", or "C" and "D"}.

[0040] The present disclosure uses terms used in some communication standards (e.g., the 3rd Generation Partnership Project (3GPP), the extensible radio access network (xRAN), the open radio access network (O-RAN), etc.) to describe various embodiments, but they are merely examples for explanation. Even in other communication systems, various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0041] Figure 1 A wireless communication system according to an embodiment of the present disclosure is shown.

[0042] Reference Figure 1 , the wireless communication system includes a base station 110 and a terminal 120 which are part of nodes using a wireless channel. Although Figure 1 only one base station is shown, the wireless communication system may also include other base stations that are the same as or similar to the base station 110.

[0043] The base station 110 is a network infrastructure that provides wireless access to the terminal 120. The base station 110 may have a coverage area defined based on the range within which signals can be transmitted. In addition to the term "base station", the base station 110 may be referred to as an "access point (AP)", "eNodeB (eNB)", "fifth generation node", "next generation node B (gNB)", "wireless point", "transmission / reception point (TRP)" or any other term having the same or equivalent meaning thereto.

[0044] The terminal 120, which is a device used by a user, performs communication with the base station 110 via a wireless channel. The link from the base station 110 to the terminal 120 is referred to as the downlink (DL), while the link from the terminal 120 to the base station 110 is referred to as the uplink (UL). In addition, although Figure 1 not shown herein, the terminal 120 and other terminals may perform communication with each other via a wireless channel. In this context, the link between the terminal 120 and another terminal (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used in combination with the PC5 interface. In some other embodiments, the terminal 120 may operate without any participation of the user. According to an embodiment of the present disclosure, the terminal 120, which may be a device that performs machine type communication (MTC), may not be carried by a user. According to another embodiment, the terminal 120 may be a narrowband (NB) Internet of Things (IoT) device.

[0045] The terminal 120 may be referred to as a "user equipment (UE)", "customer premise equipment (CPE)", "mobile station", "subscriber station", "remote terminal", "wireless terminal", "electronic device", "user device", or any other term having the same or equivalent technical meaning thereto.

[0046] 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., FR1 (Frequency Range 1) of NR). In addition, the base station 110 and the terminal 120 may transmit and receive wireless signals in a relatively high frequency band (e.g., FR2 (or FR2-1, FR2-2, FR2-3) of NR, FR3 of NR, or millimeter wave (mmWave) frequency bands (e.g., 28 GHz, 30 GHz, 38 GHz, 60 GHz)). To enhance the channel gain, the base station 110 and the terminal 120 may perform beamforming. In this context, beamforming may include transmit beamforming and receive beamforming. The base station 110 and the terminal 120 may assign directivity to transmitted or received signals. To this end, the base station 110 and the terminal 120 may select a serving beam through a beam search or beam management process. After the serving beam is selected, subsequent communication may be performed through a resource having a QCL relationship with the resource that has transmitted the serving beam.

[0047] If the large-scale characteristics of the channel carrying the symbol on the first antenna port can be inferred from the channel carrying the symbol on the second antenna port, the first antenna port and the second antenna port may be evaluated as being in the QCL relationship. For example, the large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler frequency shift, average gain, average delay, or spatial receiver parameters.

[0048] Although Figure 1 It is described that both the base station 110 and the terminal 120 perform beamforming, but embodiments of the present disclosure are not necessarily limited thereto. In some embodiments, the terminal may or may not perform beamforming. Similarly, 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.

[0049] In the present disclosure, a beam representing a spatial stream of a signal in a wireless channel may be formed by one or more antennas (or antenna elements), and the formation process thereof may be referred to as beamforming. Beamforming may include at least one of analog beamforming and digital beamforming (e.g., precoding). Reference signals transmitted based on beamforming may include, for example, a demodulation reference signal (DM-RS), a channel state information reference signal (CSI-RS), a synchronization signal / physical broadcast channel (SS / PBCH), or a sounding reference signal (SRS). In addition, for the configuration of each reference signal, IEs such as CSI-RS resources, SRS resources, etc. may be used, and such a configuration may include information associated with the beam. The information associated with the beam may refer to whether the corresponding configuration (e.g., CSI-RS resource) uses the same spatial domain filter as other configurations (e.g., another CSI-RS resource in the same CSI-RS resource set) or uses a different spatial domain filter, or which reference signal it is quasi-co-located (QCL), or if it is QCL, what type it is (e.g., QCL type A, B, C, or D).

[0050] According to the related art, in a communication system in which the cell radius of a base station is relatively large, each base station has been installed so that the corresponding base station includes the functions of a digital processing unit (or distributed unit (DU)) and a radio frequency (RF) processing unit (or wireless unit (RU)). However, with the use of high frequency bands in the 4th generation (4G) system and / or its subsequent communication systems (for example, the fifth generation (5G)), and the reduction in the cell coverage of base stations, the number of base stations covering a certain area has increased. This results in an increase in the initial installation cost for communication operators to install more base stations. In order to minimize the installation cost of the base station, a structure has been proposed in which the DU and RU of the base station are separated so that one or more RUs are connected to one DU via a wired network, and one or more RUs are geographically distributed to cover a specific area. In the following, reference will be made to Figures 2a to 2b Describe examples of deployment structures and extensions of base stations according to various embodiments of the present disclosure.

[0051] Figure 2a A fronthaul interface according to an embodiment of the present disclosure is shown.

[0052] refer to Figure 2a , fronthaul refers to the physical link between the wireless LAN and the base station, rather than the backhaul link between the base station and the core network. Figure 2aAn example of the fronthaul structure between a DU 210 and an RU 220 is shown, but this is only for convenience of description and the present disclosure is not limited thereto. In other words, the embodiments of the present disclosure can also be applied to the fronthaul structure between one DU and multiple RUs. For example, the embodiments of the present disclosure can be applied to the fronthaul structure between one DU and two RUs. In addition, the embodiments of the present disclosure can also be applied to the fronthaul structure between one DU and three RUs.

[0053] Referring Figure 2a , the base station 110 may include a DU 210 and an RU 220. The fronthaul 215 between the DU 210 and the RU 220 may operate through an F x interface. For the operation of the fronthaul 215, interfaces such as, for example, the enhanced common public radio interface (eCPRI) or radio over Ethernet (ROE) may be used.

[0054] With the further development of communication technologies, mobile data services have increased significantly, and thus the bandwidth requirements for the fronthaul between the digital unit and the radio unit have also increased significantly. In deployments such as a centralized / cloud radio access network (C-RAN), the DU may be implemented to perform the functions of the packet data convergence protocol (PDCP), radio link control (RLC), media access control (MAC), and physical (PHY), and the RU may be implemented to perform the functions of the PHY layer in addition to the radio frequency (RF) function.

[0055] The DU 210 may be used as the upper layer function of the wireless network. For example, the DU 210 may perform the functions of the MAC layer and / or part of the PHY layer. The part of the PHY layer that is performed at a higher level function in the PHY layer may include channel coding (or channel decoding), scrambling (or descrambling), modulation (or demodulation), or layer mapping (or layer demapping). When the DU 210 complies with the O-RAN standard, the DU 210 may be referred to as an O-DU (O-RAN DU). In the embodiments of the present disclosure, when needed, the DU 210 may be replaced by a first network entity of a base station (e.g., a gNB).

[0056] The RU 220 may be used as the lower layer function of the wireless network. For example, the RU 220 may perform a part of the PHY layer and / or the RF function. The part of the PHY layer that is performed at a relatively lower level than the DU 210 among the functions of the PHY layer may include, for example, iFFT transform (or FFT transform), CP insertion (CP removal), and digital beamforming. Referring Figure 4Examples of this specific functional split are described in more detail. RU 220 may be referred to as an "Access Unit (AU)", "Access Point (AP)", "Transmit / Receive Point (TRP)", "Remote Radio Head (RRH)", "Radio Unit (RU)", or any other term with an equivalent technical meaning. When RU 220 complies with the O-RAN standard, RU 220 may be referred to as an O-RU (O-RAN RU). In an embodiment of the present disclosure, when needed, RU 220 may be replaced and represented by a second network entity of a base station (e.g., gNB).

[0057] Although Figure 2a FIG. shows that the base station 110 includes a DU 210 and an RU 220, but the embodiments of the present disclosure are not limited thereto. The base station may be implemented using a distributed deployment of a centralized unit (CU) configured to perform functions of the upper layer of the access network (e.g., Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), etc.) and a distributed unit (DU) configured to perform functions of the lower layer. In this context, the distributed unit (DU) may include Figure 1 a digital unit (DU) and a radio unit (RU). Between the core network (e.g., 5G Core (5GC) or Next Generation Core (NGC) network) and the radio access network (RAN), the base station may be implemented with a deployment arranged in the order of CU, DU, and RU. The interface between the CU and the distributed unit (DU) may be referred to as the F1 interface.

[0058] The centralized unit (CU) may be connected to one or more DUs to perform functions at a higher layer than the DU. For example, the CU may perform functions of the Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layers, and the DU and RU may perform functions of the lower layer. The DU may execute some functions (high PHY) in the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers, and the RU may be responsible for the remaining functions (low PHY) of the PHY layer. Depending on the implementation of the distributed deployment of the base station, the digital unit (DU) may be included in the distributed unit (DU). Hereinafter, unless otherwise defined, the description will be for the operations of the digital unit (DU) and the RU, but it should be noted that various embodiments of the present disclosure may be applied to the deployment of a base station including a CU, and may also be applied to the deployment where the DU is directly connected to the core network (i.e., a base station implemented as integrating the CU and the DU into one entity (e.g., an NG-RAN node)).

[0059] Figure 2bShows a fronthaul interface of an Open Radio Access Network (O-RAN) according to an embodiment of the present disclosure, where an eNB or gNB is shown as a base station 110 according to a distributed deployment.

[0060] Referring Figure 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 by the description of each other O-RU (e.g., O-RU 253-n).

[0061] The O-DU 251 is a logical node including functions among those of a base station (e.g., eNB, gNB) according to Figure 4 to be described later, except for the functions assigned to the O-RU 253-1. The O-DU 251 may control the operations of the 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 including a subset of the functions among those of a base station (e.g., eNB, gNB) according to Figure 4 to be described later. The real-time aspects of the control plane (C-plane) communication and user plane (U-plane) communication with the O-RU 253-1 may be controlled by the O-DU251.

[0062] The O-DU 251 may communicate with the O-RU 253-1 via the LLS interface. The LLS interface corresponds to the fronthaul interface. The LLS interface means a logical interface between the O-DU 251 and the O-RU 253-1 using lower layer function split (i.e., frame-based PHY function split). The LLS-C between the O-DU 251 and the O-RU 253-1 provides the C-plane via the LLS interface. The LLS-U between the O-DU 251 and the O-RU253-1 provides the U-plane via the LLS interface.

[0063] In Figure 2b , the entities of the base station 110 are referred to as O-DU and O-RU to describe the O-RAN. However, such naming should not be construed as limiting the embodiments of the present disclosure thereto. In referring Figure 3a , Figure 3b , Figure 4 , Figure 5a , Figure 5b , Figure 6 , Figure 7a , Figure 7b , Figure 8a , Figure 8b , Figure 9a , Figure 9b and Figures 10 to 12In the described embodiments, the operations of the DU 210 can be performed by the O-DU 251. The description of the DU 210 can also be applied to the O-DU 251. Similarly, in the reference Figure 3a , Figure 3b , Figure 4 , Figure 5a , Figure 5b , Figure 6 , Figure 7a , Figure 7b , Figure 8a , Figure 8b , Figure 9a , Figure 9b and Figures 10 to 12 described embodiments, of course, the operations of the RU 220 can be performed by the O-RU 253-1. The description of the RU 220 can also be applied to the O-RU 253-1.

[0064] Figure 3a shows a functional configuration of a distributed unit (DU) according to an embodiment of the present disclosure.

[0065] Referring to Figure 3a , the shown configuration can be understood as the configuration of the DU 210 (or Figure 2a the O-DU 251) of Figure 2b as part of a base station. As used herein, terms such as "~ module", "~ unit", or "~ part" may refer to a unit for processing at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

[0066] Referring to Figure 3a , the DU 210 includes a transceiver 310, a memory 320, and a processor 330.

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

[0068] The transceiver 310 may perform functions for transmitting and receiving signals in a wireless communication environment. For example, the transceiver 310 may perform a function for converting between a baseband signal and a bit string according to the physical layer standard of the communication system. When transmitting data, the transceiver 310 generates complex symbols by encoding and modulating the transmitted bit string. When receiving data, the transceiver 310 recovers the received bit string by demodulating and decoding the baseband signal. The transceiver 310 may include multiple transmit / receive paths. The transceiver 310 may be connected to a core network or connected to other nodes (e.g., integrated access backhaul (IAB)).

[0069] The transceiver 310 may be configured to transmit and receive various signals. For example, the transceiver 310 may transmit management plane (M-plane) messages, synchronization plane (S-plane) messages, or control plane (C-plane) messages. Similarly, the transceiver 310 may transmit or receive user plane (U-plane) messages. Although only the transceiver 310 is shown in Figure 3a , the DU 210 may include two or more transceivers.

[0070] The transceiver 310 may be configured to transmit and receive signals as described above. Thus, all or at least a part of the transceiver 310 may also be referred to as a communication unit, a transmit unit, a receive unit, or a transmit / receive unit. In addition, throughout the following description, the transmission and / or reception performed via a wireless channel is used to mean that the foregoing processes are performed by the transceiver 310.

[0071] Although not shown in Figure 3a , the transceiver 310 may further include a backhaul transceiver for connecting to a core network or another base station. The backhaul transceiver provides an interface for performing communication with other nodes in the network. The backhaul transceiver converts the bit string transmitted from the base station to another node (such as another access node, another base station, a higher layer node, a core network, etc.) into a physical signal, and converts the physical signal received from another node into a bit string.

[0072] The memory 320 stores data such as basic programs, application programs, and setting information for the overall operation of the DU 210. The memory 320 may be referred to as a storage unit. The memory 320 may be configured with a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory. In addition, the memory 320 provides the stored data according to the request of the processor 330.

[0073] The processor 330 controls the overall operation of the DU 210. The processor 330 may be referred to as a controller. For example, the processor 330 transmits and receives signals via the transceiver 310 (or via the fronthaul communication unit). The processor 330 records data into the memory 320 and reads data from the memory 320. The processor 330 may execute the functions of the protocol stack required by the communication standard. Although only the processor 330 is shown in Figure 3a , according to another embodiment, the DU 210 may include two or more processors.

[0074] Figure 3a The configuration of the DU 210 shown is merely an example, and the configuration of the DU implementing the embodiments of the present disclosure is not limited to Figure 3a the configuration shown. In some embodiments, a part of the configuration may be added, deleted, or changed.

[0075] Figure 3b The functional configuration of a radio unit (RU) according to an embodiment of the present disclosure is shown.

[0076] Referring to Figure 3b , the configuration shown may be understood as the configuration of the RU 220 as part of a base station or Figure 2b the O-RU 253-1 of Figure 2b . As used herein, terms such as "~ module", "~ unit", or "~ part" may refer to a unit for processing at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

[0077] Referring to Figure 3b , the RU 220 may include an RF transceiver 360, a fronthaul transceiver 365, a memory 370, and a processor 380.

[0078] The RF transceiver 360 performs the function of transmitting and receiving signals through a wireless channel. For example, the RF transceiver 360 upconverts a baseband signal to an RF band signal to transmit the RF band signal through an antenna, and downconverts the RF band signal received through the antenna to a baseband signal. The RF transceiver 360 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0079] The RF transceiver 360 may include multiple transmit / receive paths. The RF transceiver 360 may also include an antenna unit. The RF transceiver 360 may include at least one antenna array configured with multiple antenna elements. In terms of hardware, the RF transceiver 360 may be configured with digital circuitry and analog circuitry (e.g., a radio frequency integrated circuit (RFIC)). The digital circuitry and the analog circuitry may be implemented in a single package. The RF transceiver 360 may include multiple RF chains. The RF transceiver 360 may perform beamforming. The RF transceiver 360 may apply beamforming weights to signals in order to give directivity according to the settings of the signals by the processor 380 for transmission and reception. The RF transceiver 360 may include a radio frequency (RF) block (or RF unit).

[0080] The RF transceiver 360 may send and receive signals over an access network. For example, the RF transceiver 360 may send downlink signals. The downlink signals may include synchronization signals (SS), reference signals (RS) (e.g., cell-specific reference signals (CRS), DM (demodulation)-RS), system information (e.g., MIB, SIB, RMSI (remaining system information), OSI (other system information)), configuration messages, control information, or downlink data. The RF transceiver 360 may receive uplink signals. The uplink signals may include random access-related signals (e.g., random access preambles: RAP) (or Msg1 (message 1), Msg3 (message 3)), reference signals (e.g., sounding reference signals (SRS), DM-RS), power headroom reports (PHR), etc. Although only the RF transceiver 360 is shown in Figure 3b According to an example of another embodiment, the RU 220 may include two or more RF transceivers.

[0081] The RF transceiver 360 may send RIM-RS. The RF transceiver 360 may send a first type of RIM-RS for notifying detection of far-field interference (e.g., RIM-RS type 1 of 3GPP). The RF transceiver 360 may send a second type of RIM-RS for notifying the presence or absence of far-field interference (e.g., RIM-RS type 2 of 3GPP).

[0082] The fronthaul transceiver 365 may send and receive signals. According to an embodiment, the fronthaul transceiver 365 may send and receive signals over a fronthaul interface. For example, the fronthaul transceiver 365 may receive management plane (M plane) messages, synchronization plane (S plane) messages, or control plane (C plane) messages. Similarly, the fronthaul transceiver 365 may send or receive user plane (U plane) messages. Although only the Figure 3bOnly the fronthaul transceiver 365 is shown, but according to an example of another embodiment, the RU 220 may include two or more fronthaul transceivers.

[0083] As described above, the RF transceiver 360 and the fronthaul transceiver 365 transmit and receive signals. Thus, all or at least a part of the RF transceiver 360 and the fronthaul transceiver 365 may be referred to as a "communication unit", "transmission unit", "reception unit", or "transceiver unit". In addition, throughout the following description, transmission and / or reception performed via a wireless channel may be used to mean that the foregoing processes are performed by the transceiver 310.

[0084] The memory 370 stores data such as basic programs, application programs, and setting information for the overall operation of the RU 220. The memory 370 may be referred to as a storage unit. The memory 370 may be configured with a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory. The memory 370 provides the stored data according to a request of the processor 380. The memory 370 may include a memory for storing conditions, instructions, or setting values related to an SRS transmission scheme.

[0085] The processor 380 controls the overall operation of the RU 220. The processor 380 may be referred to as a controller. For example, the processor 380 transmits and receives signals via the RF transceiver 360 or the fronthaul transceiver 365. The processor 380 writes data to the memory 370 and reads data from the memory 370. The processor 380 may execute functions of a protocol stack required by a communication standard. Although only the processor 380 is shown in Figure 3b According to another implementation example, the RU 220 may include two or more processors. The processor 380 may include a storage space for storing at least instructions / codes that temporarily reside in the processor 380, where the instructions / codes are instruction sets or codes stored in the memory 370, or may be a part of a circuit for configuring the processor 380. The processor 380 may include various communication modules for performing communication. The processor 380 may control the RU 220 to perform operations according to the following embodiments of the present disclosure.

[0086] Figure 3b The configuration of the RU 220 shown is only an example, and examples of the RU that implements the embodiments of the present disclosure are not limited to Figure 3b the configuration shown. In some configurations, certain ones in the configuration may be added, deleted, or changed.

[0087] Figure 4 An example of the functional split between the DU and the RU according to an embodiment of the present disclosure is shown.

[0088] Refer to Figure 4, with the latest development of wireless communication technologies (e.g., the introduction of 5G communication systems or NR (New Radio) communication systems), the frequency bands used have increased even more. In addition, as the cell radius of base stations becomes very small, the number of RUs that need to be installed further increases. In 5G communication systems, the data transmission volume has increased significantly by 10 times or more. Therefore, the data transmission capacity of the wired network sent to the fronthaul has increased significantly. Therefore, due to the above factors, the initial installation cost of the wired network in 5G communication systems may increase very significantly. Therefore, in order to reduce the transmission capacity of the wired network and reduce the installation cost of the wired network, "function split" can be used to reduce the transmission capacity of the fronthaul by transferring some functions of the DU's modem to the RU.

[0089] To reduce the burden on the DU, the role of the RU, which is only responsible for the existing RF functions, can be extended to some functions of the physical layer. The higher the functional layer that the RU executes, the more the throughput of the RU may increase to increase the transmission bandwidth at the fronthaul. At the same time, the lower the constraint on the latency requirement due to the response processing. The higher the functional layer that the RU executes, the smaller the virtualization gain obtained by the RU, and the more the size, weight, and cost of the RU increase. Therefore, considering the trade-off between the above advantages and disadvantages, it is necessary to achieve an optimal function split.

[0090] Reference Figure 4 , a function split in the physical layer below the MAC layer is shown. In the case of transmitting a signal from the base station to the terminal through the wireless network in the downlink (DL), the base station can sequentially perform channel coding / scrambling, modulation, layer mapping, antenna mapping, RE mapping, digital beamforming (e.g., precoding), iFFT transform / CP insertion, and RF conversion. In the case of receiving a signal from the terminal through the wireless network in the uplink (UL), the base station can sequentially perform RF conversion, FFT transform / CP removal, digital beamforming (e.g., pre-combination), RE demapping, channel estimation, layer demapping, demodulation, decoding / demodulation. According to the aforementioned trade-off, the function split of the uplink function and the downlink function can be defined in various types through requirements between suppliers, discussions on standards, etc.

[0091] In the first function split 405, the RU performs the RF function and the DU performs the PHY function. In the first function split, the PHY function in the RU is basically not implemented, and the first function split can be referred to as, for example, Option 8. In the second function split 410, the RU performs the iFFT transform / CP addition in the DL of the PHY function and the FFT transform / CP removal in the UL, and the DU performs the remaining PHY functions. For example, the second function split 410 can be referred to as Option 7-1. In the third function split 420a, the RU performs the iFFT transform / CP addition in the DL of the PHY function and the FFT transform / CP removal and digital beamforming in the UL, and the DU performs the remaining PHY functions. For example, the third function split 420a can be referred to as Option 7-2x Category A. In the fourth function split 420b, the RU performs up to digital beamforming in both the DL and UL, and the DU performs the upper-layer PHY functions after digital beamforming. For example, the fourth function split 420b can be referred to as Option 7-2x Category B. In the fifth function split 425, the RU performs up to RE mapping (or RE demapping) in both the DL and UL, and the DU performs the upper-layer PHY functions after RE mapping (or RE demapping). For example, the fifth function split 425 can be referred to as Option 7-2. In the sixth function split 430, the RU performs up to modulation (or demodulation) in both the DL and UL, and the DU performs the upper-layer PHY functions after modulation (or demodulation). For example, the sixth function split 430 can be referred to as Option 7-3. In the seventh function split 440, the RU performs up to encoding / scrambling (or decoding / descrambling) in both the DL and UL, and the DU performs the upper-layer PHY functions after modulation (or demodulation). For example, the seventh function split 440 can be referred to as Option 6.

[0092] In the case where a large amount of signal processing as in the FR1 MMU is expected, a relatively upper function split (e.g., the fourth function split 420b) may be required to reduce the fronthaul capacity. In addition, a function split that is too high (e.g., the sixth function split 430) may result in a more complex control interface and impose a significant burden on the implementation of the RU due to including multiple PHY processing blocks in the RU, and thus an appropriate function split may be required according to the deployment and implementation scenarios of the DU and RU.

[0093] In the case where it is not possible to process the precoding of the data received from the DU (i.e., when the precoding capacity of the RU is limited), the third function split 420a or a lower function split thereof (e.g., the second function split 410) can be applied. In the case where the function split can process the precoding of the data received from the DU, the fourth function split 420b or a higher function split thereof (e.g., the sixth function split 430) can be applied.

[0094] In the following, in the present disclosure, unless otherwise defined, embodiments are described based on the third functional split 420a (which may be referred to as Category A or CAT-A) or the fourth functional split 420b (which may be referred to as Category B or CAT-B) for performing beamforming processes in RU. The O-RAN specification differentiates the type of O-RU based on whether the precoding function is located on the O-DU interface or the O-RU interface. An O-RU that does not perform precoding (i.e., has low complexity) may be referred to as a CAT-A O-RU. An O-RU that performs precoding may be referred to as a CAT-B O-RU.

[0095] In the following, the upper-layer PHY refers to the physical layer processing performed in the DU of the fronthaul interface. For example, the upper-layer PHY may include FEC encoding / decoding, scrambling, and modulation / demodulation. In the following, the lower-layer PHY refers to the physical layer processing performed in the RU of the fronthaul interface. For example, the lower-layer PHY may include FFT / iFFT, digital beamforming, or physical random access channel (PRACH) extraction and filtering. However, it should be noted that the above principles do not exclude embodiments implemented through other functional splits. The functional configurations, signaling, or operations described below may be described based on the third functional split 420a or the fourth functional split 420b, but they may also be applied to other functional splits.

[0096] Embodiments of the present disclosure describe the specifications of eCPRI and O-RAN as the fronthaul interface when sending messages between a DU (e.g., Figure 2a DU 210 in Figure 2a ) and an RU (e.g.,

[0097] RU220 in

[0098] ) as an example. The Ethernet payload of the message may include an eCPRI header, an O-RAN header, and additional fields. In the following, standard terms of eCPRI or O-RAN will be used to describe various embodiments of the present disclosure, but it should be noted that in various embodiments of the present disclosure, any other expression having the same or equivalent meaning as the corresponding term may be used instead.

[0099] ecpriVersion (4 bits): This parameter indicates the eCPRI protocol version.

[0100] ecpriConcatenation (1 bit): This parameter indicates when eCPRI concatenation is used.

[0101] ecpriMessage (1 byte): This parameter indicates the service type carried by the message type. For example, the parameter indicates an IQ (In-phase / Quadrature-phase) data message, a real-time control data message, or a transport network delay measurement message.

[0102] ecpriPayload (2 bytes): This parameter indicates the byte size of the payload part of the eCPRI message.

[0103] ecpriRtcid / ecpriPcid (2 bytes): This parameter is the eAxC (Extended Antenna Carrier) identifier (eAxCID), which identifies the specific data stream associated with each C-plane (ecpriRtcid) or U-plane (ecpriPcid) message.

[0104] ecpriSeqid (2 bytes): This parameter provides two levels of unique message identification and sequencing. The first octet of this parameter is the sequence ID used to identify the message sequence within the eAxC message stream, and this sequence ID is used to verify that all messages have been received and to rearrange out-of-order messages. The second octet of this parameter is the sub-sequence ID. This sub-sequence ID is used to verify the sequence and enable its rearrangement when wireless transmission level segmentation (eCPRI or IEEE-1914.3) occurs.

[0105] eAxC identifier (ID): This ID includes the band and sector identifier ("BandSector_ID"), the component carrier identifier ("CC_ID"), the spatial stream identifier ("RU_Port_ID"), and the distributed unit identifier ("DU_Port_ID"). The bit allocation of the eAxCID can be classified as follows.

[0106] DU_port ID: This ID is used to distinguish processing units in the O-DU (e.g., other baseband cards). It is expected that the O-DU will allocate bits for the DU_port ID, and the O-RU will append the same value to the UL U-plane messages carrying the same sectionId data.

[0107] BandSector_ID: This ID is the aggregated cell identifier (the band and sector classification supported by the O-RU).

[0108] CC_ID: This ID is used to distinguish the carrier components supported by the O-RU.

[0109] RU_portID: This ID specifies, for example, a logical stream such as a data layer or a spatial stream, and, for example, a signal channel requiring a special antenna allocation, such as a separate parameter set (eg, PRACH) or SRS.

[0110] The fronthaul application protocol may include a control plane (C-plane), a user plane (U-plane), a synchronization plane (S-plane), and a management plane (M-plane).

[0111] The control plane can be configured to provide scheduling information and beamforming information via control messages. The control plane means real-time control between DU and RU. The user plane may include IQ sample data transmitted between DU and RU. The user plane may include downlink data (IQ data or SSB / RS), uplink data (IQ data or SRS / RS) or PRACH data of the user. The weight vector of the above beamforming information can be multiplied with the user's data. The synchronization plane generally means the traffic between DU and RU for the synchronization controller (e.g., IEEE master controller). The synchronization plane may be related to timing and synchronization. The management plane means non-real-time control between DU and RU. The management plane may be related to initial setup, non-real-time reset or reset or non-real-time reporting.

[0112] The control plane messages (i.e., C-plane messages) can be encapsulated based on a two-layer header approaching scheme. The first layer can consist of an eCPRI common header or an IEEE 1914.3 common header, which includes fields for indicating the message type. The second layer is an application layer that includes fields necessary for control and synchronization. The segments in the application layer define the characteristics of the U-plane data sent or received in a beam with a mode ID. The segment types supported in the C-plane are as follows.

[0113] The section type may indicate the usage of the control message transmitted in the control plane. For example, the usage of each section type may be defined as follows.

[0114] sectionType=0: This is used to indicate resource blocks or symbols that are not used in DL or UL.

[0115] sectionType=1: This is used for most DL / UL radio channels, where the term "most" indicates channels that do not require time or frequency offsets, such as those required for hybrid neuron channels.

[0116] sectionType=2: This is reserved for further use.

[0117] sectionType = 3: This is for PRACH and hybrid parameter set channels, and channels that require time or frequency offsets different from the nominal SCS value.

[0118] sectionType = 4: This is reserved for further use.

[0119] sectionType = 5: This is UE scheduling information, transmitting UE scheduling information so that the RU can perform real-time BF weight calculation (O-RAN optional BF scheme).

[0120] sectionType = 6: This is for UE-specific channel information transmission, periodically transmitting UE channel information so that the RU can perform real-time BF weight calculation (O-RAN optional BF scheme).

[0121] sectionType = 7: This is used to support LAA

[0122] sectionType = 8: This is used for ACK / NACK feedback, providing ACK / NACK feedback for the section description of C-plane messages from the RU to the DU.

[0123] In the RAN, several types of compression methods can be used in each section to improve the data transmission efficiency between the DU and the RU. Compression techniques can include, for example, uncompressed techniques, block floating-point compression (BFPC) techniques, modulation compression (MC) techniques, etc. The IQ data frame of the O-RAN standard can include a user data compression header (e.g., udCompHdr). The user data compression header can be defined and transmitted with a specified bit width (e.g., 4-bit "udIqWidth") and compression method (e.g., 4-bit "udCompMeth"). For example, the compression method can be defined as shown in Table 1 below.

[0124] [Table 1]

[0125]

[0126]

[0127] Among the above compression techniques, the MC technique is a lossless method with no data loss and high compression efficiency. The MC technique relies on the characteristic that modulated data symbols can be represented by a very limited number of bits of the in-phase (I) component and the quadrature (Q) component. For example, since a QPSK (Quadrature Phase Shift Keying) modulation symbol has only two potential states for I and two potential states for Q, a QPSK modulation symbol can be represented as a single-bit I component and a single-bit Q component without losing information. Another example is that a symbol modulated with 64QAM can be represented by at most 3 bits of the I component and 3 bits of the Q component.

[0128] For the I component of the data in the U-plane message, 16 bits can be used. For the Q component of the data in the U-plane message, 16 bits can also be used. That is, 32 bits can be used for data transmission in the U-plane message. When QPSK modulation is used for modulation compression, the number of transmitted bits can be reduced from 32 bits to 2 bits. When 16QAM modulation is used for modulation compression, the number of transmitted bits can be reduced from 32 bits to 4 bits. When 64QAM modulation is used for modulation compression, the number of transmitted bits can be reduced from 32 bits to 6 bits.

[0129] To express the values of the I component and the Q component, the values of the I component and the Q component are allowed to be superimposed with multiple constellation sizes that can be expressed with a single word width, and the constellation can be "shifted" so that the two's complement can represent each constellation point. For example, the QPSK constellation points can be shifted by -1 / 2. The I component can be -1 or 0. The Q component can be -1 or 0. In addition, for example, the 16QAM constellation points can be shifted 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. In addition, for example, the 64QAM constellation points can be shifted 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.

[0130] The MC technique converts bit-level information into shifted constellation points (SCP). The DU (e.g., DU 210) can transmit a U-plane message including the conversion information according to the SCP to the RU (e.g., RU 220). The DU 210 can send a constellation shift flag (csf) to the RU 220 to indicate whether it is to be shifted. 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 below.

[0131] [Table 2]

[0132] udIqWidth shift value 1 1 / 2 2 1 / 4 3 1 / 8 4 1 / 16 5 1 / 32

[0133] Data compressed according to the MC technique does not indicate the actual power value. The DU 210 can transmit a modulation compression ratio value (modCompScaler) to the RU 220 so that the RU can set the power level for the modulation compressed data. The "modCompScaler" parameter indicates the scale factor to be applied to the unscaled constellation points during decompression. In the O-RAN specification, the "modCompScaler" parameter can be provided to the RU through section extension information (e.g., section extension type 4). The "modCompScaler" parameter can indicate an exponent component and a mantissa component through the following equation.

[0134] [Equation 1]

[0135]

[0136] where "mantissa" indicates the mantissa component of the indicated value, "exponent" indicates the exponent component of the indicated value, and modCompScaler[k] represents the (k + 1)-th bit of the "modCompScaler" parameter. For example, modCompScaler[0] indicates the first bit of the "modCompScaler" parameter, and modCompScaler

[14] represents the fifteenth bit of the "modCompScaler" parameter.

[0137] The most significant 4 bits among the 15 bits of the "modCompScaler" parameter indicate the exponent component, and the least significant 11 bits among the 15 bits of the "modCompScaler" parameter indicate the mantissa component. Therefore, the value indicated by the "modCompScaler" parameter can be obtained from the following equation.

[0138] [Equation 2]

[0139] modCompScaler = mantissa · 2 -exponent

[0140] where "mantissa" indicates the mantissa component of the indicated value, and "exponent" indicates the exponent component of the indicated value.

[0141] Section extension 4 of the O-RAN standard for transmitting the "modCompScaler" parameter is shown in Table 3 below.

[0142] [Table 3]

[0143]

[0144] DU 210 can send a modulation compression power scaling RE mask (mcScaleReMask) to RU 220. The "mcScaleReMask" parameter can indicate the position of the REs in a PRB and the same scaling and modulation type. Similar to the "modCompScaler" parameter, DU 210 can send a scaling value ("mcScaleOffset") for modulation compression to RU 220.

[0145] The "mcScaleOffset" parameter indicates the scale factor to be applied to the unshifted constellation points during decompression. In the O-RAN standard, the "mcScaleOffset" parameter can be provided to RU 220 through section extension information (e.g., section extension type 5). The "mcScaleOffset" parameter can indicate an exponent component and a mantissa component through the following equation.

[0146] [Equation 3]

[0147]

[0148] where "mantissa" indicates the mantissa component of the indicated value, "exponent" indicates the exponent component of the indicated value, and mcScaleOffset[k] indicates the (k + 1)-th bit of the "mcScaleOffset" parameter. For example, mcScaleOffset[0] indicates the first bit of the "mcScaleOffset" parameter, and mcScaleOffset

[14] indicates the fifteenth bit of the "mcScaleOffset" parameter.

[0149] 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 least significant 11 bits indicate the mantissa component. Therefore, the value indicated by the "mcScaleOffset" parameter is as follows in the following equation.

[0150] [Equation 4]

[0151] mcScaleOffset = mantissa · 2 -exponent

[0152] where "mantissa" indicates the mantissa component of the indicated value, and "exponent" indicates the exponent component of the indicated value.

[0153] Section extension 5 of the O-RAN standard for sending the "mcScaleOffset" parameter is shown in the following table. Table 4 indicates one scaling value, and Table 5 indicates two scaling values.

[0154] [Table 4]

[0155]

[0156] [Table 5]

[0157]

[0158] The section extension information in the above Tables 3 to 5 can be included in the C-plane message. RU 220 can recover the original signal desired by DU 210 based on the compressed data received through the U-plane message and the parameters received through the C-plane message. According to an embodiment, RU 220 can obtain the original signal from the compressed bits based on the "csf" parameter. According to an embodiment, RU220 can obtain the original signal from the compressed bits based on the "modCompScaler" parameter. According to an embodiment, RU 220 can obtain the original signal from the compressed bits based on the "mcscaleoffset" parameter and the "mcScaleReMask" parameter.

[0159] Figure 5a and Figure 5b each shows an example of modulation compression (MC) according to various embodiments of the present disclosure. Terms such as "…… module", "…… unit", etc. refer to a unit for processing at least one function or operation, which can be implemented by hardware or software or a combination thereof.

[0160] Referring Figure 5a , DU 510 can include a scheduler 511, a C-plane message generator 513, and a U-plane message generator 515. The scheduler 511 can schedule the U-plane message according to the above modulation compression technique. The C-plane message generator 513 can generate a C-plane message including control information according to the modulation compression technique. For example, the C-plane message generator 513 can generate a C-plane message including section extension 4 as shown in Table 3. In addition, for example, the C-plane message generator 513 can generate a C-plane message including section extension 5 as shown in Table 4 or Table 5. The U-plane message generator 515 can generate a U-plane message including an I component and a Q component according to the modulation compression technique.

[0161] The RU 520 may include a C-plane analyzer 521, a buffer 523, a U-plane analyzer 525, and a modulation decompression unit 527. The C-plane analyzer 521 may receive a C-plane message from the DU 510. The C-plane analyzer 521 may obtain parameters related to modulation compression from the segment extension information (e.g., segment extension 4, segment extension 5) included in the C-plane message. The C-plane analyzer 521 may obtain segment information from the C-plane message. The C-plane analyzer 521 may store the parameters related to modulation compression and the segment information in the buffer 523. The U-plane analyzer 525 may receive a U-plane message from the DU 510. The U-plane analyzer 525 may include an I component and a Q component included in the U-plane message. The modulation decompression unit 527 may obtain the parameters related to modulation compression and the segment information from the buffer 523. The modulation decompression unit 527 may obtain the I component and the Q component from the U-plane analyzer 525. The modulation decompression unit 527 may obtain the bit string of the I component and the bit string of the Q component based on the parameters related to modulation compression. For example, during decompression, the modulation decompression unit 527 may "unshift" the constellation according to the "csf" value and apply a scale factor to the constellation type indicated in the segment. The segment may have multiple modulation types. The modulation type may be inferred from the reMask bits. Each "1" bit in the reMask bits indicates a shift command ("csf") for the RE of the PRB and a scale factor (e.g., "modCompScaler" when using segment extension 4, or "mcScaleOffset" when using segment extension 5).

[0162] The RAN standard provides segment-based modulation compression. When compression techniques other than modulation compression are used in the data transmission of a specific time slot, the segment may be configured according to the beamId (or ueId) allocation of the data resources (e.g., RE / PRB / symbol). However, when modulation compression is applied, it may be required that all PRBs and symbols in the segment use the same "csf" and the same scale value (e.g., "modCompScaler" when using segment extension 4, and "mcScaleOffset" when using segment extension 5). In other words, since these segments are configured according to the "csf" and scale values of the data, relatively more segments may be configured in modulation compression compared to compression techniques other than modulation compression. For example, if the resource regions have the same beamId but different "csf" and different scale values, it may be necessary to divide the resource regions into different segments.

[0163] Reference Figure 5b, the resource grid 551 indicates the data allocation for each independent data type. The vertical axis of the resource grid 551 may represent the frequency domain (unit: PRB), and its 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, data 551h may be included in the area of the resource grid 551.

[0164] The resource grid 553 indicates the data allocation without using modulation compression. The data transmitted separately by the DU (e.g., the data for each beamID or the data for each ueId) may have a unique modulation type. However, when the modulation compression technique is not applied, the DU may define a certain area specified by the PRB interval and the symbol interval as a section, and the DU may send the data in this section to the RU. For example, three sections (e.g., section #0, section #1, and section #2) may be included in the resource grid 553. Section #1 may include the resource areas of data 551b, data 551c, and data 551d. Section #2 may include the resource areas of data 551e, data 551f, data 551g, and data 551h.

[0165] The resource grid 555 indicates the 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 (e.g., symbol #4). Data 551c and data 551d may be divided into different RB areas in the same symbol. If the same modulation compression is applied to each section, it is necessary to allocate data 551c and data 551d to different sections. Different from the resource grid 553, it may be requested that data 551d be included in a section different from the section including data 551c. In addition, since the modulation type can be distinguished for each symbol used for modulation compression, this section may be time-division. For example, independent modulation compression may be applied to each of data 551e, data 551f, data 551g, and data 551h. In the case where the same modulation compression is applied to each section, it is necessary to allocate data 551e, data 551f, data 551g, and data 551h to different sections.

[0166] Although not shown in Figure 5b , in addition to the separation in the RB unit, there may also be another case where each RE is separated using section extension 4 during modulation compression.

[0167] As referenced in Figure 5bAs described above, data transmission using modulation compression may require more segments compared to data transmission without using modulation compression. However, the more segments are distinguished, the more the amount of fronthaul transmission increases. Therefore, due to the increased overhead for defining segments and the redundant transmission of (multiple) parameters other than modulation compression, inefficiency of the RU may occur.

[0168] To reduce the above problems, embodiments of the present disclosure propose control information that is used to provide modulation compression information (e.g., "csf" and a scaling value) for data allocated in a partial area of a segment. A number of areas can be configured within a segment, and modulation compression information can be allocated to each area. The DU (e.g., DU 210) may send a C-plane message of a segment including modulation compression information of each area to the RU (e.g., RU 220). For ease of description of embodiments of the present disclosure, in a segment, an area distinguished for modulation compression is referred to as a modulation compression (MC) chunk, but instead of an MC chunk, terms such as a data chunk, a data bundle, a segment bundle and a segment group, a sub-block, a data sub-block, an MC sub-block, a segment sub-block, an MC area, a segment sub-area, a pattern, a symbol pattern, a symbol PRB pattern, a partial area of a segment, or a term having a technical meaning equivalent thereto may be used.

[0169] Figure 6 An example of signaling between a DU (e.g., DU 210) and an RU (e.g., RU 220) to provide modulation compression information about a sub-block of a segment according to an embodiment of the present disclosure is shown. The sub-block of the segment is a unit to which modulation compression is applied and may be referred to as an "MC chunk".

[0170] Reference Figure 6 , in operation 601, the DU 210 may send an M-plane message to the RU 220. According to an embodiment, the DU 210 may provide modulation compression to an MC chunk in units of sub-blocks (i.e., including an M-plane message notifying information capable of providing modulation compression specific to the MC chunk) (hereinafter referred to as modulation compression based on an MC chunk). For example, a segment extension type for providing modulation compression based on an MC chunk may be defined. The M-plane message may indicate a segment extension type supported by the DU 210. The supported segment extension type may indicate segment extension information for modulation compression based on an MC chunk. The DU 210 may provide at least one parameter for modulation compression based on an MC chunk (described below with reference to Figure 7a , Figure 7b , Figure 8a , Figure 8b and Figure 9a and Figure 9b to the RU 220 through the M-plane message. Although Figure 6An example of the DU 210 sending an M-plane message to the RU 220 is described, but embodiments of the present disclosure are not limited thereto. In some embodiments, the RU 220 may send an M-plane message to the DU 210. The M-plane message may include at least one of information about the segment extension types that the RU 220 can support or information indicating applicable parameters in the RU 220.

[0171] In operation 603, the DU 210 may perform scheduling based on MC chunks. The DU 210 may divide a segment into one or more MC chunks. The DU 210 may divide a segment into multiple MC chunks. For example, the DU 210 may divide a segment into 4 MC chunks. The DU 210 may determine one or more parameters for indicating each MC chunk. For example, the DU 210 may determine a parameter indicating the number of MC chunks. The DU 210 may determine a parameter indicating the number of one or more symbols of each MC chunk. The DU 210 may determine a parameter indicating the number of one or more PRBs of each MC chunk. The DU 210 may determine the interval between the PRBs of the MC chunks or a parameter indicating the interval between symbols.

[0172] In operation 605, the DU 210 may send a C-plane message including compressed information about the MC chunks to the RU 220. The C-plane message may include segment information. The segment information may indicate the resource area of the segment. The C-plane message may include segment extension information. The segment extension information may include information indicating the resource area of the MC chunks (hereinafter referred to as "resource area information"). The segment extension information may include compressed information about the MC chunks.

[0173] The resource area information may include at least one of parameters according to the scheduling result of the MC chunks (for example, the number of MC chunks, the number of one or more symbols of each MC chunk, the number of one or more PRBs of each MC chunk, the interval between the PRBs of the MC chunks, or the interval between symbols).

[0174] The compression information may include at least one of parameters related to modulation compression of data on a resource region to be applied to an MC block (e.g., "csf" parameter, "mcScaleReMask" parameter, "modCompScaler" parameter, or "mcScaleOffset" parameter). The "csf" parameter is a flag indicating whether the constellation of the MC block is shifted. The "mcScaleReMask" parameter is a bitmap of REs (hereinafter referred to as mask information) in the PRB of the MC block, where each bit setting of mcScaleReMask indicates whether "mcScaleOffset" and "csf" are applicable to the RE (resource element) sent through the U-plane message. The "modCompScaler" parameter or the "mcScaleOffset" parameter indicates the scaling value of the MC block.

[0175] At operation 607, the DU 210 may send a U-plane message to the RU 220. The DU 210 may perform modulation compression of data based on the modulation compression technique according to operations 601 to 605. The DU 210 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 region occupied by the MC block. The RU 220 may obtain parameters related to modulation compression based on the modulation compression information of the MC block of the section extension information received from the DU 210. Based on the parameters related to modulation compression, a bitstream of the I component and a bitstream of the Q component may be obtained. For example, during decompression, the RU 220 may "de-shift" the constellation according to the "csf" value and apply a scaling value to the constellation type indicated in the section.

[0176] Although the U-plane message for the downlink signal is described only as an example in Figure 6 , the embodiments of the present disclosure are not limited thereto. In some embodiments, the modulation compression using MC blocks according to the embodiments of the present disclosure may also be applied to the U-plane message of the uplink signal.

[0177] Several regions (i.e., MC blocks) may be defined within one section. The DU 210 may allocate modulation compression information for each MC block. The modulation compression information may include a constellation shift flag (e.g., "csf"). In addition, according to an embodiment, the modulation compression information may include scaling information (e.g., "mcScaleReMask" parameter, "modCompScaler" parameter, or "mcScaleOffset" parameter as a scaling value). In addition, the modulation compression information may include a constellation shift flag and scaling information. Since each MC block has its own constellation shift flag and scaling information, the control information may be configured differently for each method specifying the MC block.

[0178] In the following, reference is made to Figure 7a and Figure 7b for a method of specifying an MC chunk by a scheme that first differentiates by symbol units and then by PRB units.

[0179] Figure 7a and Figure 7b each show an example of a first scheme for partitioning a section according to various embodiments of the present disclosure.

[0180] Referring to Figure 7a and FIG. 7B, a single section can be partitioned into one or more MC chunks. The first scheme may refer to a method of first partitioning a section into symbol bundles (i.e., symbol chunks) when configuring an MC chunk and then partitioning the frequency domain of the symbol chunks into PRB bundles (i.e., PRB chunks).

[0181] Referring to Figure 7a a section 700 can be specified by a resource area defined by a "numPrbc" parameter 710 and a "numSymbol" parameter 720. The "numPrbc" parameter 710 represents the number of PRBs. The "numSymbol" parameter 720 represents the number of symbols. The section 700 can be partitioned into multiple MC chunks. In the following, for the description of MC chunks, parameters for specifying MC chunks can be used. At least one or all of the following-described parameters can be used to specify (or classify) MC chunks. The following parameters can be exemplified. The parentheses next to the parameter name indicate an example of the number of bits.

[0182] startMcSymbolId(4b): The starting symbol index of a symbol chunk having the same symbol range (may not exist).

[0183] numMcSymbol(4b): The number of symbols of a symbol chunk having the same symbol range. The sum of numMcSymbol should be the same as numSymbol of the section. "0" represents numSymbol.

[0184] mcSymbPeriod(2b): Symbol chunk period. This parameter can indicate whether, for symbol chunks with the same symbol range, each symbol, every other symbol (i.e., symbol interval of one symbol), every 2 symbols (i.e., symbol interval of two symbols), or every 4 symbols (i.e., symbol interval of four symbols) is used. It indicates 0 = each symbol, 1 = every other symbol, 2 = every 2 symbols, and 3 = every 4 symbols (may not exist when each symbol is always used). [It indicates whether each symbol, every other symbol, every 2 symbols, or every 4 symbols is used for symbol chunks with the same symbol range. 0 = each symbol, 1 = every other symbol, 2 = every 2 symbols, 3 = every 4 symbols (can be absent when each symbol is always used).]

[0185] numMcPrbChunks(4b): Number of PRB chunks on symbol chunk #i with numMcSymbol(i) (may not exist).

[0186] startMcPrbc(10b): Starting PRB index of the PRB chunks in the PRB chunk (may not exist).

[0187] numMcPrbc(8b): Number of PRBs in the PRB chunk on the symbol chunk. The sum of numMcPrbc should be the same as numPrbc of the section. "0" represents numPrbc.

[0188] mcPrbPeriod(2b): PRB chunk period. This parameter can indicate whether, for PRB chunks, each RB, every other RB (i.e., PRB interval of one PRB), every 2 RBs (i.e., PRB interval of two PRBs), or every 4 RBs (i.e., PRB interval of four PRBs) is used. It indicates 0 = each RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs (may not exist when each RB is always used). [It indicates whether each RB, every other RB, every 2 RBs, or every 4 RBs is used for PRB chunks. 0 = each RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs. (Can be absent when each RB is always used.)]

[0189] mcRemaskOnOff(1b): This indicates whether mcScaleRemask exists in the section extension or MC chunk. Through this field, the format of the section extension type of the C-plane message described later can be changed (it can be omitted if each RE of the MC chunk shares the same csf and modCompScaler). [This indicates whether mcScaleRemask exists in the section extension or MC chunk. (The format of the section extension type can be changed through this field) (It can be absent when all REs in the MC chunk share the same CSF and modCompScaler.)]

[0190] numMcRemask(4b): This indicates the number of mcScaleRemask in the section extension or MC chunk. (It can be omitted if all REs in the MC chunk share the same CSF and the same modCompScaler) [This indicates the number of mcScaleRemask in the section extension or MC chunk (It can be absent when all REs in the MC chunk share the same CSF and modCompScaler.)]

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

[0192] periodFlag(1b): This indicates whether mcSymbolPeriod and mcPrbPeriod are used for each section extension or MC chunk (this parameter can be absent)

[0193] Sector 700 can be divided into multiple MC chunks. According to the first scheme, it can be first divided into symbol units. The "numSymbol" parameter 720 can be divided into numMcSymbol(0) 721 and numMcSymbol(1) 723. numMcSymbol(0) 721 represents the number of one or more symbols of symbol chunk #0. numMcSymbol(1) 723 represents the number of one or more symbols of symbol chunk #1. The "numSymbol" parameter 720 indicates the sum of the number of one or more symbols of symbol chunk #0 and the number of one or more symbols of symbol chunk #1. After sector 700 is divided into symbol units, the frequency domain of each 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 domains (hereinafter referred to as PRB chunks). The frequency domain corresponding to numMcSymbol(0) 721 can be divided into PRB chunk #0 731 of numMcPrbc(0,0), PRB chunk #1 732 of numMcPrbc(0,1), and PRB chunk #2 733 of numMcPrbc(0,2). The frequency domain corresponding to numMcSymbol(1) 723 can be divided into two domains. 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).

[0194] For example, when using all the above parameters, the symbol index value of a symbol chunk #i and the PRB index value of a PRB chunk #j can be obtained through Equation 5 and Equation 6.

[0195] [Equation 5]

[0196] Symbol index(l) = startMcSymbolId + 1*(2^mcSymbPer iod), l = 0, … numMcSymbol(i) - 1.

[0197] [Equation 6]

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

[0199] For example, if startMcSymbolId or startMcPrbc is not used among the parameters, the symbol index value of a symbol chunk #i and the PRB index value of a PRB chunk #j can be obtained through the following equation.

[0200] [Equation 7]

[0201] Symbol index(l) = first symbol index in symbol chunk#i + 1*(2^mcSymbPeriod), l = 0,...numMcSymbol(i)-1.

[0202] The first symbol index is the first empty symbol index after the previous symbol chunk.

[0203] [Equation 8]

[0204] PRB index(k) = first PRB index in PRB chunk#j + k*(2^mcPrbPeriod), k = 0,...numMcPrbc(j)-1.

[0205] The first PRB index is the first empty PRB index after the previous PRB chunk within the symbol chunk.

[0206] "numMcPRBChunks" indicates the number of PRB chunks in each symbol chunk. For example, "numMcPRBChunks" indicates the number of at least one PRB chunk in each symbol chunk. "numMcPRBChunks" indicates the total number of MC chunks within the section extension. For example, "numMcPRBChunks" indicates the number of all MC chunks included in the section extension.

[0207] According to an embodiment of the present disclosure, both "mcRemaskOnOff" and "numMcRemask" may exist together in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk). According to another embodiment, only one of "mcRemaskOnOff" and "numMcRemask" may exist in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk). According to another embodiment, "mcRemaskOnOff" and "numMcRemask" may be omitted in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk).

[0208] Both "mcRemaskOnOff" and "numMcRemask" can be included in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, both "mcRemaskOnOff" and "numMcRemask" can be included in each section extension. For example, both "mcRemaskOnOff" and "numMcRemask" are included in each MC chunk (e.g., symbol chunk or PRB chunk).

[0209] At least one of "mcRemaskOnOff" or "numMcRemask" can be included in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, at least one of "mcRemaskOnOff" or "numMcRemask" is included in each section extension. For example, at least one of "mcRemaskOnOff" and "numMcRemask" is included in each MC chunk (e.g., symbol chunk or PRB chunk).

[0210] "mcRemaskOnOff" and "numMcRemask" can be omitted in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, "mcRemaskOnOff" and "numMcRemask" are included in a field different from the section extension (or MC chunk (e.g., symbol chunk or PRB chunk)).

[0211] If resources are periodically allocated in the time domain within a section, parameters for symbol chunks (e.g., the "mcSymbolPeriod" parameter) can be defined. Additionally, according to an embodiment, if resources are allocated at regular intervals in the frequency domain within a section, parameters for PRB chunks (e.g., the "mcPrbPeriod" parameter) can be defined. In the above embodiments, according to an embodiment, the periodFlag value may or may not exist in each section extension or MC chunk (symbol chunk or PRB chunk). Also, in the above embodiments, one flag parameter has been described, but according to another embodiment, the flag parameters for each of mcSymbolPeriod and mcPrbPeriod can exist separately.

[0212] DU 210 can generate section extension information including at least one of the above parameters to indicate the MC chunks divided according to the first scheme. DU 210 can send a C-plane message including the section extension information to RU 220.

[0213] DU 210 can configure a section with one MC chunk without using "mcScaleReMask". For example, to indicate one MC chunk, the section extension information can be configured as shown in the following table.

[0214] [Table 6]

[0215]

[0216] "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 (i.e., the symbols within the symbol chunk). When there is only one MC chunk in the section, "numMcSymbol" can be the same as "numSymbol". "numMcPrbChunks" indicates the number of one or more PRB chunks within the symbol chunk. The number of one or more PRB chunks can be 1. "numMcPrbc" indicates the number of PRBs in a PRB chunk. When there is only one MC chunk in the section, "numMcPrbc" can be the same as "numPrbc". "csf" indicates whether the constellation of the MC chunk is shifted, and "modCompScaler" indicates the scaling value of the MC chunk. According to the calculations of Equations 1 to 2 above, the scaling value can be obtained from the 15 bits of the "modCompScaler" field. According to an embodiment, DU 210 can configure a section with two MC chunks without using "mcScaleReMask". For example, to indicate two MC chunks, the section extension information can be configured as shown in the following table.

[0217] [Table 7]

[0218]

[0219] "extType" indicates the type of section extension information. "extLen" indicates the length of the section extension information. "numMcSymbol" indicates the number of symbols in an MC chunk (i.e., the number of symbols in a symbol chunk). For example, the number of symbol chunks can be 1. "numMcSymbol" can be the same as "numSymbol". Thus, the section extension information can include a "numMcSymbol" field. "numMcPrbChunks" indicates the number of one or more PRB chunks in a symbol chunk. For example, the number of one or more PRB chunks can be 2. N+3 octets of "numMcPrbc" indicates the number of PRBs in the first PRB chunk. The symbol chunk and the first PRB chunk can indicate an MC chunk. N+4 octets of "csf" indicates whether the constellation for an MC chunk is shifted, and N+4 octets and N+5 octets of "modCompScaler" indicate the scaling value for an MC chunk. According to the calculations such as Equation 1 to Equation 2 above, the scaling value can be derived from the 15 bits of the "modCompScaler" field. N+6 octets of "numMcPrbc" indicates the number of PRBs in the second PRB chunk. The symbol chunk and the second PRB chunk can indicate another MC chunk. N+7 octets of "csf" indicates whether the constellation for another MC chunk is shifted, and N+7 octets and N+8 octets of "modCompScaler" indicate the scaling value for another MC chunk. According to the calculations of Equation 1 to Equation 2 above, the scaling value can be derived from the 15 bits of the "modCompScaler" field. According to an embodiment, DU 210 can use "mcScaleReMask" and configure a section with one MC chunk. For example, to indicate one MC chunk, the section extension information can be configured as shown in the following table.

[0220] [Table 8]

[0221]

[0222] "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 (i.e., the symbols within the symbol chunk). "numMcPrbChunks" indicates the number of one or more PRB chunks within the symbol chunk. For example, the number of one or more PRB chunks can be 1. Thus, "numMcPrbc" can be the same as "numPrbc". "mcScaleReMask" is a bitmap of REs in the PRB (hereinafter referred to as "mask information"), and each bit setting of mcScaleReMask can indicate whether "mcScaleOffset" and "csf" are applicable to the REs (resource elements) sent via the U-plane message (e.g., "0" = not applicable, "1" = applicable). "csf" indicates whether the constellation is shifted, and "mcScaleOffset" indicates the scale value. According to the calculations of Equation 3 to Equation 4 above, the scale value can be derived from the 15 bits of the "mcScaleOffset" field. According to an embodiment, DU 210 can use "mcScaleReMask" and configure a section with two MC chunks. For example, to indicate two MC chunks, the section extension information can be configured as shown in the following table.

[0223] [Table 9]

[0224]

[0225] "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 (i.e., the symbols within the symbol chunk). For example, the number of symbol chunks can be 2. Thus, the section extension information can include two "numMcSymbol" fields. In the two "numMcSymbol" fields, the first "numMcSymbol" field indicates the number of one or more symbols in the first symbol chunk. In 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 can include information on the MC chunks for each "numMcSymbol" field.

[0226] The "numMcPrbChunks" of the first "numMcSymbol" field indicates the number of one or more PRB chunks within the first symbol chunk. For example, the number of one or more PRB chunks in the first symbol chunk can be 1. The N+3 octet "numMcPrbc" indicates the number of PRBs in the first symbol chunk and the corresponding PRB chunk. The first symbol chunk and the PRB chunk can indicate one MC chunk. The N+4 octet to N+5 octet "mcScaleReMask" is a bitmap of the REs in the PRBs of an MC chunk, and each bit setting of mcScaleReMask can indicate whether "mcScaleOffset" and "csf" are applicable to the REs sent via the U-plane message (e.g., "0" = not applicable, "1" = applicable). The N+5 octet "csf" indicates whether the constellation for an MC chunk is shifted, and the N+5 octet and N+6 octet "mcScaleOffset" indicate the scale value for an MC chunk. According to the calculations of Equation 3 to Equation 4 above, the scale value can be derived from the 15 bits of the "mcScaleOffset" field.

[0227] The "numMcPrbChunks" of the second "numMcSymbol" field indicates the number of one or more PRB chunks within the second symbol chunk. For example, the number of one or more PRB chunks in the second symbol chunk can be 1. The N+3 octet "numMcPrbc" indicates the number of PRBs in the second symbol chunk and the corresponding PRB chunk. The second symbol chunk and the PRB chunk can point to another MC chunk. The N+10 octet to N+11 octet "mcScaleReMask" is a bitmap of the REs in the PRBs of an MC chunk, and each bit setting of mcScaleReMask can indicate whether "mcScaleOffset" and "csf" are applicable to the REs sent via the U-plane message (e.g., "0" = not applicable, "1" = applicable). The N+11 octet "csf" indicates whether the constellation for an MC chunk is shifted, and the N+11 octet to N+12 octet "mcScaleOffset" indicate the scale value for an MC chunk. According to the calculations such as Equation 3 to Equation 4 above, the scale value can be derived from the 15 bits of the "mcScaleOffset" field. According to an embodiment, the DU 210 can use "mcScaleReMask" and configure section 750 with four MC chunks having a period. Two symbol chunks can be configured in one section, and two PRB chunks can be configured in each symbol chunk. The "periodFlag" parameter can be used for each symbol chunk. In order to according to Figure 7bThe indicated section segmentation is used to indicate MC chunks, and the section extension information can be configured as shown in the following table.

[0228] [Table 10]

[0229]

[0230] In Figure 7b the shown example, section 750 can be configured with 7 symbols and 10 PRBs, where A = 4, B = 3, C = 5, and D = 5. According to the above table and Figure 7b , the first MC chunk 751 can be specified by 4 symbols (A = 4) and 5 PRBs (C = 5). Since "mcSymbPeriod" is 1, the interval between two of the four symbols can be one symbol. Since "mcPrbPeriod" is zero, the interval between the PRBs among the 5 PRBs can be zero. The first MC chunk 751 can occupy five consecutive PRBs. For example, the first MC chunk 751 can occupy PRB#0, PRB#1, PRB#2, PRB#3, and PRB#4.

[0231] According to the above table and Figure 7b , the second MC chunk 752 can be specified by 4 symbols (A = 4) and 5 PRBs (D = 5). Since "mcSymbPeriod" is 1, the interval between two of the four symbols can be one symbol. Since "mcPrbPeriod" is zero, the interval between the PRBs among the 5 PRBs can be zero. The second MC chunk 752 can occupy five consecutive PRBs. For example, the second MC chunk 752 can occupy PRB#5, PRB#6, PRB#7, PRB#8, and PRB#9.

[0232] According to the above table and Figure 7b , the third MC chunk 753 can be specified by 3 symbols (B = 3) and 5 PRBs (C = 5). Since "mcSymbPeriod" is 1, the interval between two of the three symbols can be one symbol. Since "mcPrbPeriod" is 1, the interval between the PRBs among the 5 PRBs can be one PRB. For example, the third MC chunk 753 can occupy PRB#0, PRB#2, PRB#4, PRB#6, and PRB#8.

[0233] According to the above table and Figure 7b, the fourth MC chunk 754 can be specified by 3 symbols (B = 3) and 5 PRBs (D = 5). Since "mcSymbPeriod" is 1, the interval between two of the three symbols can be one symbol. Since "mcPrbPeriod" is 1, the interval between the PRBs among the 5 PRBs can be one PRB. The fourth MC chunk 754 can start from the empty PRB region. For example, the fourth MC chunk 754 can occupy PRB #1, PRB #3, PRB #5, PRB #7, and PRB #9.

[0234] Formats in which some regions corresponding to zero padding in Tables 6 to 10 (for example, octet N + 7 in Table 9, octets N + 3, N + 5, N + 9, N + 17, N + 19, N + 23, N + 25 in Table 10) are reduced so that all parameters are continuously set can also be understood as embodiments of the present disclosure.

[0235] Figure 8a and Figure 8b Each shows an example of a second scheme for segmenting according to various embodiments of the present disclosure. A segment can be divided into one or more MC chunks. The second scheme can mean a method of first dividing a segment into PRB bundles (i.e., PRB chunks) and then dividing the time domain of the PRB chunks into symbol bundles (i.e., symbol chunks) when configuring MC chunks.

[0236] Refer to Figure 8a , the segment 800 can be specified by a resource region defined by the "numPrbc" parameter 810 and the "numSymbol" parameter 820. The "numPrbc" parameter 810 indicates the number of PRBs. The "numSymbol" parameter 820 indicates the number of symbols. The segment 800 can be divided into multiple MC chunks. Hereinafter, for describing MC chunks, parameters for specifying MC chunks can be used first. At least one or all of the following parameters can be used to specify (or classify) MC chunks. The following parameters can be exemplified. The parentheses next to the parameter name indicate an example of the number of bits.

[0237] startMcPrbc(10b): The starting PRB index of the PRB chunk (may not exist).

[0238] numMcPrbc(8b): The number of PRBs of the PRB chunk having the same PRB range. The sum of numMcPrbc should be the same as numPrbc of the segment. "0" represents numPrbc.

[0239] mcPrbPeriod(2b): PRB group period. This parameter indicates whether, for a PRB group, every RB, every other RB (i.e., the PRB interval of one PRB), every 2 RBs (i.e., the PRB interval of two PRBs), or every 4 RBs (i.e., the PRB interval of 4 PRBs) is used. This parameter indicates 0 = every RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs. (May not exist when every RB is always used.) [It indicates whether every RB, every other RB, every 2 RBs, or every 4 RBs is used for the PRB group. 0 = every RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs. (May not exist when every RB is always used.)]

[0240] numMcSymbolChunks(4b): The number of symbol chunks of PRB group #i with numMcPrbc(i) (may not exist).

[0241] startMcSymbolId(4b): The starting symbol index of symbol chunks with the same symbol range (may not exist).

[0242] numMcSymbol(4b): The number of symbols of symbol chunks on the PRB group with numMcPrb. The sum of numMcSymbol should be the same as numSymbol of the section. "0" represents numSymbol.

[0243] mcSymbPeriod(2b): This parameter may indicate whether, for symbol chunks with the same symbol range, every symbol, every other symbol (i.e., the symbol interval of one symbol), every 2 symbols (i.e., the symbol interval of two symbols), or every 4 symbols (i.e., the symbol interval of 4 symbols) is used. This parameter indicates 0 = all symbols, 1 = all other symbols, 2 = every 2 symbols, 3 = every 4 symbols (may not exist when every symbol is always used). [It indicates whether every symbol, every other symbol, every 2 symbols, or every 4 symbols is used for symbol chunks with the same symbol range. 0 = every symbol, 1 = every other symbol, 2 = every 2 symbols, 3 = every 4 symbols. (May not exist when every symbol is always used.)]

[0244] mcRemaskOnOff(1b): This indicates whether mcScaleRemask exists in the section extension or MC chunk. The format of the section extension type of the C-plane message described below can be changed through this field (can be omitted) [This indicates the existence of mcScaleRemask in the section extension or MC chunk (the format of the section extension type can be changed through this field). (May not exist)]

[0245] numMcRemask(4b): This indicates the number of mcScaleRemask in the section extension or MC chunk. (May be omitted if all REs in the MC chunk share the same CSF and the same modCompScaler) [This indicates the number of mcScaleRemask in the section extension or MC chunk (when all REs in the MC chunk share the same CSF and modCompScaler, it may not exist.)]

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

[0247] periodFlag(1b): This indicates whether the mcSymbolPeriod and mcPrbPeriod for each section are used for each section extension or MC chunk. (May not exist)

[0248] Sector 800 can be divided into multiple MC chunks. According to the second scheme, sector 800 can first 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 represents the number of one or more PRBs of PRB chunk #0. numMcSymbol(1) 812 represents the number of one or more PRBs of PRB chunk #1. numMcSymbol(2) 813 represents the number of one or more PRBs of PRB chunk #2. The "numPrbc" parameter 810 indicates the sum of the number of one or more PRBs of PRB chunk #0, the number of one or more PRBs of PRB chunk #1, and the number of one or more PRBs of PRB chunk #2. After sector 800 is divided into PRB units, the time domain of each PRB chunk can be divided into symbol units. The "numSymbol" parameter 820 can be divided. The time domain corresponding to numMcPrbc(0) 811 can be divided into two domains (hereinafter referred to as "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 a symbol chunk #2 833 of numMcSymbol(1,0). The time domain corresponding to numMcPrbc(2) 813 can be divided into two domains. 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).

[0249] For example, when using all the above parameters, the PRB index value of PRB chunk #i and the symbol index value of a symbol chunk #i can be obtained through the following equation.

[0250] [Equation 9]

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

[0252] [Equation 10]

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

[0254] When neither the startMcSymbolId parameter nor the startMcPrbc parameter is used, the PRB index value of PRB chunk #i and the symbol index value of a symbol chunk #i can be determined by the following equations.

[0255] [Equation 11]

[0256] PRB index(k) = first PRB index in PRB chunk#j + k * (2^mcPrbPeriod), k = 0, ... numMcPrbc(i) - 1

[0257] The first PRB index is the first available PRB index after the previous PRB chunk within the symbol chunk.

[0258] [Equation 12]

[0259] Symbol index(l) = first symbol index in symbol chunk#i + 1 * (2^mcSymbPeriod), l = 0, ... numMcSymbol(j) - 1

[0260] The first symbol index is the first available symbol index after the previous symbol chunk.

[0261] "numMcSymbolChunks" indicates the number of PRB chunks in each symbol chunk. For example, "numMcSymbolChunks" indicates the number of at least one symbol chunk in each symbol chunk. "numMcSymbolChunks" indicates the total number of MC chunks within the section extension. For example, "numMcSymbolChunks" indicates the number of all MC chunks included in the section extension.

[0262] According to an embodiment, both “mcRemaskOnOff” and “numMcRemask” may coexist in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk). According to an embodiment, only one of “mcRemaskOnOff” and “numMcRemask” may exist in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk). According to an embodiment, “mcRemaskOnOff” and “numMcRemask” may be omitted in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk).

[0263] Both “mcRemaskOnOff” and “numMcRemask” may be included in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, both “mcRemaskOnOff” and “numMcRemask” are included in each section extension. For example, both “mcRemaskOnOff” and “numMcRemask” are included in each MC chunk (e.g., symbol chunk or PRB chunk).

[0264] At least one of “mcRemaskOnOff” or “numMcRemask” may be included in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, at least one of “mcRemaskOnOff” or “numMcRemask” is included in each section extension. For example, at least one of “mcRemaskOnOff” and “numMcRemask” is included in each MC chunk (e.g., symbol chunk or PRB chunk).

[0265] “mcRemaskOnOff” and “numMcRemask” may be omitted in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, “mcRemaskOnOff” and “numMcRemask” are included in a field different from the section extension (or MC chunk (e.g., symbol chunk or PRB chunk)).

[0266] When resources are periodically allocated in the time domain within a section, parameters for symbol chunking (e.g., the "mcSymbolPeriod" parameter) can be defined. When resources are allocated at regular intervals in the frequency domain within a section, parameters for PRB chunking (e.g., the "mcPrbPeriod" parameter) can be defined. In the above embodiments, according to each embodiment, a "periodFlag" value may or may not exist in each section extension or MC chunk (symbol chunk or PRB chunk). Although in the above embodiments, one flag parameter has been described, according to another embodiment, flag parameters for each of "mcSymbolPeriod" or "mcPrbPeriod" may exist separately.

[0267] The DU 210 can generate section extension information including at least one of the above parameters to indicate the MC chunks divided according to the second scheme. The DU 210 can send a C-plane message including the section extension information to the RU 220.

[0268] The DU 210 can configure a section with one MC chunk without using "mcScaleReMask". For example, to indicate one MC chunk, the section extension information can be configured as shown in the following table.

[0269] [Table 11]

[0270]

[0271] "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 (i.e., the number of PRBs in the PRB chunk). For example, when there is only one MC chunk in the section, "numMcPrbc" can 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 can be 1. "numMcSymbol" indicates the number of symbols within one symbol chunk. For example, when there is only one MC chunk in a section, "numMcSymbol" can be the same as "numSymbol". "csf" indicates whether the constellation is shifted, and "modCompScaler" indicates a scaling value. According to the calculations such as Equation 1 to Equation 2 above, the scaling value can be derived from the 15 bits of the "modCompScaler" field.

[0272] According to an embodiment, DU 210 may configure a section having two MC chunks without using "mcScaleReMask". For example, to indicate two MC chunks, the section extension information may be configured as shown in the following table.

[0273] [Table 12]

[0274]

[0275] "extType" indicates the type of section extension information. "extLen" indicates the length of the section extension information. "numMcPrbc" indicates the number of PRBs of an MC chunk, that is, the number of PRBs within a PRB chunk. For example, the number of PRB chunks may be 1. "numMcPrbc" may be the same as "numPrbc". Thus, the section extension information may include one "numMcPrbc" field. "numMcSymbolChunks" indicates the number of one or more symbol chunks within a PRB chunk. For example, the number of one or more symbol chunks may be 2. The N+3 octet "numMcSymbol" indicates the number of symbols within the first symbol chunk. The PRB chunk and the first symbol chunk may indicate one MC chunk. The N+4 octet "csf" indicates whether the constellation for one MC chunk is shifted, and the N+4 octet and N+5 octet "modCompScaler" indicate the scaling value for one MC chunk. According to the calculations such as Equation 1 to Equation 2 above, the scaling value may be derived from the 15 bits of the "modCompScaler" field. The N+6 octet "numMcSymbol" indicates the number of symbols within the second symbol chunk. The PRB chunk and the second symbol chunk may indicate another MC chunk. The N+7 octet "csf" indicates whether the constellation for another MC chunk is shifted, and the N+7 octet and N+8 octet "modCompScaler" indicate the scaling value for another MC chunk. According to the calculations such as Equation 1 to Equation 2 above, the scaling value may be derived from the 15 bits of the "modCompScaler" field.

[0276] According to an embodiment, DU 210 may use "mcScaleReMask" and configure a section having one MC chunk. For example, to indicate one MC chunk, the section extension information may be configured as shown in the following table.

[0277] [Table 13]

[0278]

[0279] "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, i.e., the number of PRBs within the PRB chunk. "numMcSymbolChunks" indicates the number of one or more symbol chunks within the PRB chunk. For example, the number of one or more symbol chunks can be 1. Thus, "numMcSymbol" can be the same as "numSymbol". "mcScaleReMask" is a bitmap of the REs in the PRB (hereinafter referred to as "mask information"), and each bit setting of mcScaleReMask can indicate whether "mcScaleOffset" and "csf" are applicable to the REs (resource elements) sent through the U-plane message (e.g., "0" = not applicable, "1" = applicable). "csf" indicates whether the constellation is shifted, and "mcScaleOffset" indicates the scale value. According to the calculation as in Equation 3 to Equation 4 above, the scale value can be derived from the 15 bits of the "mcScaleOffset" field. According to an embodiment, DU 210 can use "mcScaleReMask" and configure a section with two MC chunks. For example, to indicate two MC chunks, the section extension information can be configured as shown in the following table.

[0280] [Table 14]

[0281]

[0282] DU 210 can use "mcScaleReMask" and configure a section with two MC chunks. For example, to indicate two MC chunks, the section extension information can be configured as shown in the following table.

[0283] "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, i.e., the number of PRBs within the PRB chunk. For example, the number of PRB chunks can be 2. Thus, the section extension information can include two "numMcPrbc" fields. The first "numMcPrbc" field among the two "numMcPrbc" fields indicates the number of one or more PRBs in the first PRB chunk. The second "numMcPrbc" field among the two "numMcPrbc" fields indicates the number of one or more PRBs in the second PRB chunk. The section extension information can include the information of the MC chunk for each "numMcPrbc" field.

[0284] The "numMcSymbolChunks" of the first "numMcPrbc" field indicates the number of one or more symbol chunks within the first PRB chunk. For example, the number of one or more symbol chunks within the first PRB chunk can be 1. The "numMcSymbol" of N+3 octets indicates the number of symbols in the first PRB chunk and the corresponding symbol chunks. The first PRB chunk and the symbol chunks can indicate an MC chunk. The "mcScaleReMask" from N+4 octets to N+5 octets is a bitmap of the REs in the PRBs of an MC chunk, and each bit setting of mcScaleReMask can indicate whether "mcScaleOffset" and "csf" are applicable to the REs sent through the U-plane message (e.g., "0" = not applicable, "1" = applicable). The "csf" of N+5 octets indicates whether the constellation for an MC chunk is shifted, and the "mcScaleOffset" from N+5 octets to N+6 octets indicates the scale value of an MC chunk. According to the calculations such as Equation 3 to Equation 4 above, the scale value can be derived from the 15 bits of the "mcScaleOffset" field.

[0285] The "numMcSymbolChunks" of the second "numMcPrbc" field indicates the number of one or more symbol chunks within the second PRB chunk. For example, the number of one or more symbol chunks within the second PRB chunk can be 1. The "numMcSymbol" of N+3 octets indicates the number of PRBs in the second PRB chunk and the corresponding symbol chunks. The second PRB chunk and the symbol chunks can indicate another MC chunk. The "mcScaleReMask" from N+10 octets to N+11 octets is a bitmap of the REs in the PRBs of an MC chunk, and each bit setting of mcScaleReMask can indicate whether "mcScaleOffset" and "csf" are applicable to the REs sent through the U-plane message (e.g., "0" = not applicable, "1" = applicable). The "csf" in N+11 octets indicates whether the constellation for an MC chunk is shifted, and the "mcScaleOffset" from N+11 octets to N+12 octets indicates the scale value of an MC chunk. According to the calculations such as Equation 3 to Equation 4 above, the scale value can be derived from the 15 bits of the "mcScaleOffset" field.

[0286] DU 210 can use "mcScaleReMask" and configure section 850 with four MC chunks having a period. Two PRB chunks can be configured in one section, and two symbol chunks can be configured in each PRB chunk. The "periodFlag" parameter for each PRB chunk can be used. For example, in order to indicate the MC chunks according to the Figure 8b section segmentation shown, the section extension information can be configured as shown in the following table.

[0287] [Table 15]

[0288]

[0289] In Figure 8b the example shown, section 850 can be configured with 7 PRBs and 10 symbols, where A = 4, B = 3, C = 5, D = 5.

[0290] According to the above table and Figure 8b , the first MC chunk 851 can be specified by 4 PRBs (A = 4) and 5 symbols (C = 5). Since "mcPrbPeriod" is 1, the interval between the PRBs among the 4 PRBs can be 1. For example, the first MC chunk 851 can occupy PRB #0, PRB #2, PRB #4, and PRB #6. Since "mcSymbPeriod" is 0, the interval between two symbols among the five symbols can be 0. That is, the first MC chunk 851 can occupy 5 consecutive symbols. For example, the first MC chunk 851 can occupy symbol #0, symbol #1, symbol #2, symbol #3, and symbol #4.

[0291] According to the above table and Figure 8b , the second MC chunk 852 can be specified by 4 PRBs (A = 4) and 5 symbols (D = 5). Since "mcPrbPeriod" is 1, the interval between the PRBs among the 4 PRBs can be 1. For example, the second MC chunk 852 can occupy PRB #0, PRB #2, PRB #4, and PRB #6. Since "mcSymbPeriod" is 0, the interval between two symbols among the five symbols can be 0. The second MC chunk 852 can occupy five consecutive symbols. For example, the second MC chunk 852 can occupy symbol #5, symbol #6, symbol #7, symbol #8, and symbol #9.

[0292] According to the above table and Figure 8b, the third MC chunk 853 can be specified by 3 PRBs (B = 3) and 5 symbols (C = 5). Since "mcPrbPeriod" is 1, the interval between the PRBs among the three PRBs can be 1. For example, the third MC chunk 853 can occupy PRB #1, PRB #3, and PRB #5. Since "mcSymbPeriod" is 1, the interval between two of the five symbols can be 1. The third MC chunk 853 can occupy 5 symbols. For example, the third MC chunk 853 can occupy symbol #0, symbol #2, symbol #4, symbol #6, and symbol #8.

[0293] According to the above table and Figure 8b , the fourth MC chunk 854 can be specified by 3 PRBs (B = 3) and 5 symbols (D = 5). Since "mcPrbPeriod" is 1, the interval between the PRBs among the three PRBs can be 1. For example, the fourth MC chunk 854 can occupy PRB #1, PRB #3, and PRB #5. Since "mcSymbPeriod" is 1, the interval between two of the five symbols can be 1. The fourth MC chunk 854 can occupy 5 symbols. For example, the fourth MC chunk 854 can occupy symbol #1, symbol #3, symbol #5, symbol #7, and symbol #8.

[0294] Reducing the format of some regions of the octets corresponding to the zero-padding in Tables 11 to 15 (for example, octet N + 7 in Table 14, octets N + 8, N + 13, N + 20, N + 25 in Table 15) can also be understood as an embodiment of the present disclosure.

[0295] Figure 9a and Figure 9b Each shows an example of a third scheme for dividing sections according to various embodiments of the present disclosure.

[0296] Referring to Figure 9a and FIG. 9B, a section can be divided into one or more MC chunks. Different from the first and second schemes, the third scheme is a method of configuring MC chunks in units of arbitrary PRB chunks and symbol chunks.

[0297] Referring to Figure 9a, section 900 can be specified by a resource area defined by parameter 910 and parameter 920. The "numPrbc" parameter 910 indicates the number of PRBs. The "numSymbol" parameter 920 indicates the number of symbols. Section 900 can be divided into multiple MC chunks. Hereinafter, in order to describe MC chunks, parameters for specifying MC chunks may be used first. At least one or all of the following parameters described can be used to specify (or classify) MC chunks. The following parameters can be used as examples, where the parentheses next to the parameter name indicate an example of the number of bits.

[0298] numMcChunks(4b): The number of MC chunks.

[0299] startMcPrbc(10b): The starting PRB of the chunk.

[0300] numMcPrbc(8b): The number of PRBs of the chunk. "0" indicates numPrbc.

[0301] mcPrbPeriod(2b): The PRB chunk period. This parameter indicates whether, for the PRB chunk, every RB, every other RB (i.e., the PRB interval of one PRB), every 2 RBs (i.e., the PRB interval of two PRBs), or every 4 RBs (i.e., the PRB interval of 4 RBs) is used. It indicates 0 = every RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs. (May not exist when always using every RB.) [It indicates whether every RB, every other RB, every 2 RBs, or every 4 RBs is used for the PRB chunk. 0 = every RB, 1 = every other RB, 2 = every 2 RBs, 3 = every 4 RBs. (May not exist when always using every RB.)]

[0302] startMcSymbol(4b): The starting symbol index of the MC chunk.

[0303] numMcSymbol(4b): The number of symbols of the MC chunk. "0" indicates numSymbol

[0304] mcSymbPeriod(2b): This parameter can indicate whether, for symbol chunks with the same symbol range, each symbol, every other symbol (i.e., symbol interval of one symbol), every 2 symbols (i.e., symbol interval of two symbols), or every 4 symbols (i.e., symbol interval of 4 symbols) is used. It indicates 0 = all symbols, 1 = all other symbols, 2 = every 2 symbols, 3 = every 4 symbols (may not exist when always using each symbol). [It indicates whether each symbol, every other symbol, every 2 symbols, or every 4 symbols is used for symbol chunks with the same symbol range. 0 = each symbol, 1 = every other symbol, 2 = every 2 symbols, 3 = every 4 symbols. (May not exist when always using each symbol.)]

[0305] mcRemaskOnOff(1b): This indicates whether mcScaleRemask exists in the section extension or MC chunk. The format of the section extension type of the C-plane message described below can be changed through this field (may be omitted) [This indicates the existence of mcScaleRemask in the section extension or MC chunk (the format of the section extension type can be changed through this field) (may not exist)]

[0306] numMcRemask(4b): This indicates the number of mcScaleRemask in the section extension or MC chunk. (May be omitted if all REs in the MC chunk share the same CSF and the same modCompScaler) [This indicates the number of mcScaleRemask in the section extension or MC chunk (may not exist when all REs in the MC chunk share the same CSF and modCompScaler.)]

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

[0308] periodFlag(1b): This indicates whether mcSymbolPeriod and mcPrbPeriod are used for each section extension or MC chunk (may not exist).

[0309] "numMcPRBChunks" indicates the number of PRB chunks in each symbol chunk. For example, "numMcPRBChunks" indicates the number of at least one PRB chunk in each symbol chunk. "numMcPRBChunks" indicates the total number of MC chunks within the section extension. For example, "numMcPRBChunks" indicates the number of all MC chunks included in the section extension.

[0310] According to an embodiment, both “mcRemaskOnOff” and “numMcRemask” may be present together in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk). According to an embodiment, only one of “mcRemaskOnOff” and “numMcRemask” may be present in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk). According to an embodiment, “mcRemaskOnOff” and “numMcRemask” may be omitted in each section extension and / or MC chunk (e.g., symbol chunk or PRB chunk).

[0311] According to an embodiment, both “mcRemaskOnOff” and “numMcRemask” may be included in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, both “mcRemaskOnOff” and “numMcRemask” are included in each section extension. For example, both “mcRemaskOnOff” and “numMcRemask” are included in each MC chunk (e.g., symbol chunk or PRB chunk).

[0312] According to an embodiment, at least one of “mcRemaskOnOff” or “numMcRemask” may be included in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, at least one of “mcRemaskOnOff” or “numMcRemask” is included in each section extension. For example, at least one of “mcRemaskOnOff” and “numMcRemask” is included in each MC chunk (e.g., symbol chunk or PRB chunk).

[0313] According to an embodiment, “mcRemaskOnOff” and “numMcRemask” may be omitted in each section extension (or MC chunk (e.g., symbol chunk or PRB chunk)). For example, “mcRemaskOnOff” and “numMcRemask” are included in a field different from the section extension (or MC chunk (e.g., symbol chunk or PRB chunk)).

[0314] When resources are periodically allocated in the time domain within a section, parameters for symbol chunking (e.g., the "mcSymbolPeriod" parameter) can be defined. When resources are allocated at regular intervals in the frequency domain within a section, parameters for PRB chunking (e.g., the "mcPrbPeriod" parameter) can be defined. In the above embodiments, according to the embodiments, a periodFlag value may or may not exist in each section extension or MC chunk (symbol chunk or PRB chunk). A flag parameter has been described in the above embodiments, but according to another embodiment, the flag parameters for each of mcSymbolPeriod or mcPrbPeriod may exist separately.

[0315] A 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. 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 may be specified by numMcSymbol(2) and numMcPrbc(2). The fourth MC chunk 934 may be specified by numMcSymbol(3) and numMcPrbc(3).

[0316] The DU 210 may generate section extension information including at least one of the above parameters to indicate the MC chunks divided according to the first scheme. The DU 210 may send a C-plane message including the section extension information to the RU 220.

[0317] According to an embodiment, the DU 210 may configure Figure 9b section 950 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 three MC chunks, the section extension information may be configured as shown in the following table.

[0318] [Table 16]

[0319]

[0320] The first MC chunk 931 can be specified by numMcSymbol(0) and numMcPrbc(0). The starting symbol of one or more symbols of numMcSymbol(0) can be indicated by startMcSymbol(0). The starting PRB of one or more PRBs of numMcPrbc(0) can be indicated by startMcPrbc(0). The "modCompScaler" from byte N+6 to byte N+7 indicates the scaling value of the first MC chunk 931. According to the calculations such as the above Equation 1 to Equation 2, the scaling value can be obtained from the 15 bits of the "modCompScaler" field. The second MC chunk 932 can be specified by numMcSymbol(1) and numMcPrbc(1). The starting symbol of one or more symbols of numMcSymbol(1) can be indicated by startMcSymbol(1). The starting PRB of one or more PRBs of numMcPrbc(1) can be indicated by startMcPrbc(1). The "modCompScaler" from byte N+12 to byte N+13 indicates the scaling value of the second MC chunk 932. According to the calculations such as the above Equation 1 to Equation 2, the scaling value can be obtained from the 15 bits of the "modCompScaler" field.

[0321] The third MC chunk 933 can be specified by numMcSymbol(2) and numMcPrbc(2). The starting symbol of one or more symbols of numMcSymbol(2) can be indicated by startMcSymbol(2). The starting PRB of one or more PRBs of numMcPrbc(2) can be indicated by startMcPrbc(2). The "modCompScaler" from byte N+13 to byte N+14 indicates the scaling value of the third MC chunk 933. According to the calculations such as the above Equation 1 to Equation 2, the scaling value can be obtained from the 15 bits of the "modCompScaler" field.

[0322] According to an embodiment, the DU 210 can use "mcScaleReMask" and configure the Figure 9b section 950 with three MC chunks. For example, in order to indicate three MC chunks, the section extension information can be configured as shown in the following table.

[0323] [Table 17]

[0324]

[0325] The first MC block 931 can be specified by numMcSymbol(0) and numMcPrbc(0). The starting symbol of one or more symbols of numMcSymbol(0) can be indicated by startMcSymbol(0). The starting PRB of one or more PRBs of numMcPrbc(0) can be indicated by startMcPrbc(0). "mcScaleReMask" from byte N+6 to byte N+7 indicates the mask information of the first MC block 931. "csf" in byte N+7 indicates whether the constellation is shifted for the first MC block 931, and "mcScaleOffset" from byte N+7 to byte N+9 indicates the scale value of the first MC block 931. According to the calculations such as Equation 3 to Equation 4 above, the scale value can be obtained from the 15 bits of the "mcScaleOffset" field. The second MC block 932 can be specified by numMcSymbol(1) and numMcPrbc(1). The starting symbol of one or more symbols of numMcSymbol(1) can be indicated by startMcSymbol(1). The starting PRB of one or more PRBs of numMcPrbc(1) can be indicated by startMcPrbc(1). "mcScaleReMask" from byte N+14 to byte N+15 indicates the mask information of the second MC block 932. "csf" in byte N+15 indicates whether the constellation is shifted for the second MC block 932, and "mcScaleOffset" from byte N+15 to byte N+17 indicates the scale value of the second MC block 932. According to the calculations of Equation 3 to Equation 4, the scale value can be obtained from the 15 bits of the "mcScaleOffset" field.

[0326] The third MC block 933 can be specified by numMcSymbol(2) and numMcPrbc(2). The starting symbol of one or more symbols of numMcSymbol(2) can be indicated by startMcSymbol(2). The starting PRB of one or more PRBs of numMcPrbc(2) can be indicated by startMcPrbc(2). "mcScaleReMask" from byte N+22 to byte N+23 indicates the mask information of the third MC block 933. "csf" in byte N+23 indicates whether the constellation is shifted for the third MC block 933, and "mcScaleOffset" from byte N+23 to byte N+24 indicates the scale value of the third MC block 933. According to the calculations such as Equation 3 to Equation 4 above, the scale value can be obtained from the 15 bits of the "mcScaleOffset" field.

[0327] Figure 10 An example of segment segmentation for periodic resource allocation according to an embodiment of the present disclosure is shown. Figure 10 The case of applying periodic resource allocation in segment segmentation using the third scheme is described.

[0328] Reference Figure 10 , the section 1000 can be specified by a resource area defined by the "numPrbc" parameter and the "numSymbol" parameter 1020. For example, the "numPrbc" parameter can indicate 6. The section 1000 can be configured with six PRBs 1011, 1012, 1013, 1014, 1015, and 1016. The section 1000 can include six symbols 1021, 1022, 1023, 1024, 1025, and 1026.

[0329] According to an embodiment, the DU 210 uses "mcScaleReMask", "mcPrbPeriod", and "mcSymbolPeriod" to configure three MC chunks 1031, 1033, and 1035 within a section 1000. The DU 210 can generate section extension information including Figure 9a at least one of the parameters described in to indicate each MC chunk divided according to the third scheme. The DU210 can send a C-plane message including the section extension information to the RU 220.

[0330] To indicate three MC chunks, the section extension information can be configured as shown in the following table. The periodFlag parameter can be omitted.

[0331] [Table 18]

[0332]

[0333] "extType" indicates the type of the section extension information. "extLen" indicates the length of the section extension information. "numMcChunks" indicates the number of MC chunks. For example, "numMcChunks" can be 3. The MC chunks can include a first MC chunk 1031, a second MC chunk 1033, and a third MC chunk 1035.

[0334] The first MC block 1031 can be specified by numMcSymbol(0) and numMcPrbc(0). The starting symbol of one or more symbols of numMcSymbol(0) can be indicated by startMcSymbol(0). The starting PRB of one or more PRBs of numMcPrbc(0) can be indicated by startMcPrbc(0). Since "mcSymbPeriod" is 1, the interval between two symbols in the first MC block 1031 can be one symbol. Since "mcPrbPeriod" is 1, the interval between PRBs in the first MC block 1031 can be one PRB.

[0335] The second MC block 1033 can be specified by numMcSymbol(2) and numMcPrbc(2). The starting symbol of one or more symbols of numMcSymbol(2) can be indicated by startMcSymbol(2). The starting PRB of one or more PRBs of numMcPrbc(1) can be indicated by startMcPrbc(1). Since "mcSymbPeriod" is 1, the interval between two symbols in the second MC block 1033 can be one symbol. Since "mcPrbPeriod" is 1, the interval between PRBs in the second MC block 1033 can be one PRB.

[0336] The third MC block 933 can be specified by numMcSymbol(2) and numMcPrbc(2). The starting symbol of one or more symbols of numMcSymbol(2) can be indicated by startMcSymbol(2). The starting PRB of one or more PRBs of numMcPrbc(2) can be indicated by startMcPrbc(2). Here, since "mcSymbPeriod" is 1, the interval between two symbols in the first MC block 1031 can be one symbol. Since "mcPrbPeriod" is 0, PRBs can be continuously allocated in the first MC block 1031.

[0337] Reducing the formatting of some regions of the octets corresponding to the zero-padding in Tables 16 to 18 (e.g., octets N + 9, N + 17 in Table 17, octets N + 6, N + 10, N + 19, N + 24 in Table 18) can also be understood as an embodiment of the present disclosure.

[0338] Although reference has been made to Figure 5a 、 Figure 5b 、 Figure 6 、 Figure 7a 、 Figure 7b 、 Figure 8a, Figure 8b , Figure 9a , Figure 9b and Figure 10 describe various examples of segment extension information according to a resource partitioning scheme, but embodiments of the present invention are not limited thereto. In addition to the specified scheme, a segment segmentation scheme using a format pattern can be utilized. According to an embodiment, its mode parameter value can indicate a specific format of the segment extension information. For example, when the mode parameter value is 0, segment extension information having the format of Table 6 or Table 7 can be used. Further, for example, when the mode parameter value is 1, segment extension information having the format of Table 2 or Table 3 can be used. Further, for example, when the mode parameter value is 2, segment extension information having the format of Table 3 or Table 4 can be used.

[0339] When the mode parameter indicates 0, the segment extension information shown in the following table can be used.

[0340] [Table 19]

[0341]

[0342] In the segment extension information having the format of Table 7, a field indicating the mode parameter can be added to the N+2 octet region. For the description of other parameters, reference can be made to Table 7 above and its description. When the mode parameter indicates 1, the segment extension information shown in the following table can be used.

[0343] [Table 20]

[0344]

[0345] In the segment extension information having the format of Table 9, a field indicating the mode parameter can be added to the N+2 octet region. For the description of other parameters, reference can be made to Table 9 above and its description. In Table 9, the "numMcPrbChunk" parameter can be omitted. According to an additional embodiment, a format in which some regions of the octets corresponding to zero-padding in Tables 19 to 20 (for example, octet N+8) are reduced and all parameters are arranged continuously can also be understood as an embodiment of the present disclosure. Through this arrangement, at least some of the parameters in Tables 19 to 20 can be omitted or the positions of at least some of the parameters can be changed.

[0346] According to an additional embodiment, the octets corresponding to zero-padding in Tables 11 to 15 (for example, octet N+7 in Table 14, octets N+8, N+13, N+20, N+25 in Table 15) can also be understood as an embodiment of the present disclosure.

[0347] Figure 11 Shows an example of modulation compression for sub-blocks according to an embodiment of the present disclosure.

[0348] Reference Figure 11 ,DU 210 may include an M-plane message generator 1111, an MC-chunk-based scheduler 1113, a C-plane message generator 1115, and a U-plane message generator 1117. The M-plane message generator 1111 may generate an M-plane message including at least one parameter required for a modulation compression scheme configured in units of MC-chunks. The M-plane message generator 1111 may send at least one parameter to the RU 220. According to an embodiment, the M-plane message generator 1111 may generate an M-plane message including information for indicating whether the DU 210 supports new section extension information (e.g., one of the formats of Tables 6 to 20). In addition, according to an embodiment, the M-plane message generator 1111 may generate an M-plane message including Reference Figure 7a , Figure 7b , Figure 8a , Figure 8b , Figure 9a and Figure 9b at least one parameter among the parameters described. Thereafter, the DU 210 may send the M-plane message to the RU 220.

[0349] The MC-chunk-based scheduler 1113 may perform scheduling on the C-plane message and the U-plane message according to the above modulation compression technique. The C-plane message generator 1115 may generate a C-plane message including section extension information according to the modulation compression technique described in Reference Figure 6 , Figure 7a , Figure 7b , Figure 8a , Figure 8b , Figure 9a , Figure 9b and Figure 10 . The C-plane message generator 1115 may generate section extension information specific to an MC-chunk constituting a partial area within a section. The section extension information may include resource area information for the MC-chunk (e.g., the number of symbols, the number of PRBs) and modulation compression information to be applied to the data occupied by the MC-chunk. For example, the C-plane message generator 1115 may generate a C-plane message including section extension information having 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.

[0350] The RU 220 may include an M-plane message generator 1121, a C-plane analyzer 1123, a buffer 1125, a U-plane analyzer 1127, and a modulation / demodulation unit 1129. The M-plane message generator 1121 may generate an M-plane message including at least one parameter required for modulation compression technology configured in MC chunks. The M-plane message generator 1121 may send at least one parameter to the DU 210. According to an embodiment, the M-plane message generator 1121 may generate an M-plane message including information for indicating whether the RU 220 supports new segment extension information (e.g., the format of any one of Tables 6 to 20). In addition, according to an embodiment, the M-plane message generator 1121 may generate an M-plane message including at least one parameter among the parameters described with reference to Figure 7a , Figure 7b , Figure 8a , Figure 8b , Figure 9a and Figure 9b . Thereafter, the RU 220 may send the M-plane message to the DU 210.

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

[0352] Figure 12 Shows an example of signaling between a DU (e.g., DU 210) and an RU (e.g., RU 220) according to an embodiment of the present disclosure for providing compression information using an identifier (ID).

[0353] Reference Figure 12 , compression information can be specified for each sub-block within a section. A sub-block is the unit to which modulation compression is applied and can be referred to as an MC chunk.

[0354] ID-based section extension information can be used. In this case, the ID can be associated with the MC chunks and the modulation compression information for the MC chunks in the above embodiments. By using the ID, the overhead caused by the repeated compression information in the data of the U-plane message can be reduced. Multiple MC chunks can be configured within a section. Compression information (e.g., constellation shift flag and scale value) can be assigned to each MC chunk. After the region information about the MC chunks (e.g., the number of symbols of the MC chunk and the number of PRBs of the MC chunk) and the modulation compression information about the MC chunks are sent once through the initial C-plane message, subsequent indication of the region information and modulation compression information on the MC chunks can be performed only by using the ID. The section extension information including the ID can be newly defined.

[0355] Reference Figure 12 , in operation 1201, the DU 210 can send a C-plane message including the compression information based on the MC chunk and the ID to the RU 220. For example, the C-plane message can be sent in time slot A-X. The compression information based on the MC chunk means the compression information specific to the MC chunk. The section extension information of the C-plane message can include at least one parameter indicating the MC chunk (e.g., the number of symbols of the MC chunk, the number of PRBs of the MC chunk). The section extension information of the C-plane message can include the 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 can include the ID associated with the compression information. According to an embodiment, the ID can be associated with the compression information. In addition, according to an embodiment, the ID can be associated with the compression information and the MC chunk.

[0356] The RU 220 can receive the ID value from the DU 210 and store the modulation compression information (e.g., constellation shift flag and scale value) corresponding to the ID in a storage device (e.g., buffer 1125, memory 370).

[0357] In operation 1203, the DU 210 can send a U-plane message including data to the RU 220. The U-plane message can be coupled with the C-plane message of operation 1201. For example, the C-plane message can be sent in time slot A. The data can be sent on the scheduling region (e.g., MC chunk) of the C-plane message. The RU 220 can decompress the data based on the compression information of operation 1201. Although not shown in Figure 12 , the RU 220 can send the data obtained by decompression to a terminal (e.g., terminal 120).

[0358] In operation 1211, the DU 210 may send a C-plane message including an ID to the RU 220. For example, the C-plane message may be sent in time slot B-X. The DU 210 may transfer only the ID value to the RU 220, thereby providing modulation compression information to the RU 220. The RU 220 may receive the ID value from the DU 210 and identify the modulation compression information (e.g., constellation shift flag and scale value) corresponding to the ID stored in a storage device (e.g., buffer 1125 or memory 370).

[0359] In operation 1213, the DU 210 may send a U-plane message including data to the RU 220. The U-plane message may be coupled with the C-plane message of operation 1211. For example, the C-plane message may be sent in time slot B. The data may be sent on the scheduling region (e.g., MC chunk) of the C-plane message. The RU 220 may decompress the data based on the modulation compression information (e.g., constellation shift flag and scale value) corresponding to the ID.

[0360] In operation 1221, the DU 210 may send a C-plane message including an ID to the RU 220. For example, the C-plane message may be sent in time slot C-X. The RU 220 may receive the ID value from the DU 210 and identify the modulation compression information (e.g., constellation shift flag and scale value) corresponding to the ID stored in a storage device (e.g., buffer 1125 or memory 370).

[0361] In operation 1223, the DU 210 may send a U-plane message including data to the RU 220. The U-plane message may be coupled with the C-plane message of operation 1221. For example, the C-plane message may be sent in time slot C. The data may be sent on the scheduling region (e.g., MC chunk) of the C-plane message. The RU 220 may decompress the data based on the modulation compression information (e.g., constellation shift flag and scale value) corresponding to the ID.

[0362] According to an embodiment of the present disclosure, in addition to the modulation compression information, Figure 12 the ID described in may also specify various information. For example, at least one of the following parameters of the ID may be included in the section extension information.

[0363] mcInfoId: This parameter is configured with any N bits and specifies the csf and scale information. For example, the scale information may include a "modCompScaler" parameter or a "mcScaleOffset" parameter.

[0364] mcRemaskId: This parameter is configured with any M bits and specifies the remasking information. For example, the remasking information may include a "mcScaleRemask" parameter.

[0365] mcId: This parameter is configured with any P bits and specifies the CSF, scale value, and re-masking information.

[0366] chunkandmcinfoId: This parameter is configured with any Q bits and specifies the resource region information and modulation compression information (e.g., CSF and scale information) of the MC chunk. For example, the scale information may include a "modCompScaler" parameter or a "mcScaleOffset" parameter.

[0367] According to the example, each ID may exist in its entirety, only partially, or may be omitted. In addition, the bit widths of each ID (e.g., N, M, P, Q) may be predetermined based on the O-RAN standard or may be predetermined through the negotiation process of the M-plane message. The RU may require a storage device (e.g., a memory or a buffer) for storing the above IDs and the compression information or masking information corresponding to the IDs. In addition, in addition to the above IDs, additional IDs for specifying at least one of the parameters described in Figure 6 , Figure 7a , Figure 7b , Figure 8a , Figure 8b , Figure 9a , Figure 9b and Figure 10 may be used. In addition, the ID parameters with additional definitions may replace the IDs described above.

[0368] Providing modulation compression information for some resource regions specific to a section can reduce the fronthaul transmission volume between the DU and the RU. In addition, since no additional section allocation is required, the burden of packet processing in each of the DU and the RU can be reduced. In addition, when operating the modulation compression technology and other compression technologies in a dynamic manner, no section segmentation occurs, thus achieving an effective scheduling for configuring the section.

[0369] The effects that can be obtained in the present disclosure are not limited to those mentioned above, and those skilled in the art will clearly understand other effects not mentioned herein from the foregoing and the following description.

[0370] According to an embodiment of the present disclosure, a method performed by a distributed unit (DU) may include identifying sub-blocks in a section. The method may include: generating a control plane (C-plane) message including section extension information, where the section extension information includes modulation compression information corresponding to the sub-blocks. The method may include sending the C-plane message to a radio unit (RU) via a fronthaul interface. The modulation compression information may include a flag for indicating whether the constellation of the sub-block is shifted and scaling information to be applied to the sub-block. The section extension information may include information for indicating the number of one or more symbols of the sub-block and information for indicating the number of one or more physical resource blocks (PRBs) of the sub-block.

[0371] According to an embodiment, the one section may include a plurality of sub-blocks. The section extension information may include modulation compression information of additional sub-blocks different from the sub-block, information for indicating the number of one or more symbols of the additional sub-block, and information for indicating the number of one or more physical resource blocks (PRBs) of the additional sub-block.

[0372] According to an embodiment, a sub-block may include at least one of a first parameter for indicating a period between symbols or a second parameter for indicating an interval between PRBs. Within the one section, the one or more symbols may be allocated 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.

[0373] According to an embodiment, the section extension information may include identification information linked to the modulation compression information. The method may include sending another C-plane message including the identification information to the RU. The method may include sending a user plane (U-plane) message coupled to the another C-plane message to the RU. The data of the U-plane message may be compressed based on the modulation compression information corresponding to the identification information.

[0374] According to an embodiment, the scaling information may include 15 bits for indicating a scaling value. Alternatively, the scaling information may include 15 bits for indicating a scaling value and 12 bits for indicating whether the scaling value is applied to each resource element (RE) in the PRB.

[0375] According to an embodiment of the present disclosure, a method performed by a radio unit (RU) may include receiving, via a fronthaul interface, a control plane (C-plane) message including section extension information from a distributed unit (DU). The method may include: identifying modulation compression information corresponding to sub-blocks in a section. The modulation compression information may include a flag for indicating whether the constellation of the sub-block is shifted and scaling information to be applied to the sub-block. The section extension information may include information for indicating the number of one or more symbols of the sub-block and information for indicating the number of one or more physical resource blocks (PRBs) of the sub-block.

[0376] According to an embodiment, the one section may include a plurality of sub - blocks. The section extension information may include modulation compression information of additional sub - blocks different from the sub - blocks, information indicating the number of one or more symbols of the additional sub - blocks, and information indicating the number of one or more physical resource blocks (PRBs) of the additional sub - blocks.

[0377] According to an embodiment, the sub - block may include at least one of a first parameter indicating the period between symbols or a second parameter indicating the interval between PRBs. Within the one section, the one or more symbols may be allocated 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.

[0378] According to an embodiment, the section extension information may include identification information linked to the modulation compression information. The method may include receiving, from the RU, another C - plane message including the identification information. The method may include receiving, from the RU, a U - plane message coupled to the another C - plane message. The data of the U - plane message may be decompressed based on the modulation compression information corresponding to the identification information.

[0379] According to an embodiment, the ratio information may include 15 bits for indicating a ratio value. Alternatively, the ratio information may include 15 bits for indicating a ratio value and 12 bits for indicating whether the ratio value is applied to each resource element (RE) in the PRB.

[0380] According to an embodiment of the present disclosure, an electronic device of a distributed unit (DU) 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 sub - blocks in a section; generate a control plane (C - plane) message including section extension information, the section extension information including modulation compression information corresponding to the sub - blocks; and transmit the C - plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag for indicating whether the constellation of the sub - block is shifted and ratio information to be applied to the sub - block. The section extension information may include information indicating the number of one or more symbols of the sub - block and information indicating the number of one or more physical resource blocks (PRBs) of the sub - block.

[0381] According to an embodiment, the one section may include a plurality of sub - blocks. The section extension information may include modulation compression information of additional sub - blocks different from the sub - blocks, information indicating the number of one or more symbols of the additional sub - blocks, and information indicating the number of one or more physical resource blocks (PRBs) of the additional sub - blocks.

[0382] According to an embodiment, a sub-block 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 assigned to be separated by the interval indicated by the second parameter.

[0383] According to an embodiment, section extension information may include identification information linked to modulation compression information. The at least one processor may also be configured to: send another C-plane message including the identification information to the RU; and send a U-plane message coupled with the another 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.

[0384] According to an embodiment, the ratio information may include 15 bits for indicating a ratio value. Alternatively, the ratio information may include 15 bits for indicating a ratio value and 12 bits for indicating whether the ratio value is applied to each resource element (RE) in the PRB.

[0385] According to an embodiment of the present disclosure, an electronic device of a radio unit (RU) 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; and identify modulation compression information corresponding to a sub-block in one section. The modulation compression information may include a flag indicating whether the constellation of the sub-block is shifted and ratio information to be applied to the sub-block. The section extension information may include information indicating the number of one or more symbols of the sub-block and information indicating the number of one or more physical resource blocks (PRBs) of the sub-block.

[0386] According to an embodiment, the one section may include a plurality of sub-blocks. The section extension information may include modulation compression information of additional sub-blocks different from the sub-block, information indicating the number of one or more symbols of the additional sub-block, and information indicating the number of one or more physical resource blocks (PRBs) of the additional sub-block.

[0387] According to an embodiment, a sub-block 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 assigned to be separated by the interval indicated by the second parameter.

[0388] According to an embodiment, the section extension information may include identification information linked to modulation compression information. The at least one processor may also be configured to: receive another C-plane message including the identification information from the RU; and receive a U-plane message coupled to the another C-plane message from the RU. The data of the U-plane message may be decompressed based on the modulation compression information corresponding to the identification information.

[0389] According to an embodiment, the ratio information may include 15 bits for indicating a ratio value. Alternatively, the ratio information may include 15 bits for indicating a ratio value and 12 bits for indicating whether the ratio value is applied to each resource element (RE) in a physical resource block (PRB).

[0390] According to an embodiment, the C-plane message may include modulation compression information.

[0391] According to an embodiment, the processor is configured to receive a U-plane message from the DU, and the U-plane message may include data associated with the C-plane message.

[0392] According to an embodiment, the processor is configured to decompress the data included in the U-plane message based on the modulation compression information and send the decompressed data to the terminal.

[0393] According to an embodiment of the present disclosure, a method performed by a distributed unit (DU) is provided. The method includes generating a control plane (C-plane) message including section extension information for modulation compression. The method includes sending the C-plane message to a radio unit (RU) via a fronthaul interface. The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first PRB information for indicating one or more physical resource blocks (PRBs) in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first ratio offset information for indicating a first ratio value to be applied to the first sub-block, and first re-masking information for indicating whether the first ratio value is applied to each resource element (RE) in the PRB in the first sub-block.

[0394] According to an embodiment, the section extension information for modulation compression further includes second symbol information for indicating one or more symbols of a second sub-block among the one or more sub-blocks, second PRB information for indicating one or more PRBs in the second sub-block, a second flag for indicating whether the constellation of the second sub-block is shifted, second ratio offset information for indicating a second ratio value to be applied to the second sub-block, and second re-masking information for indicating whether the second ratio value is applied to each resource element (RE) in the PRB in the second sub-block.

[0395] According to an embodiment, the first PRB information includes information indicating a starting PRB of one or more PRBs of the first sub-block, and information indicating the number of one or more PRBs of the first sub-block.

[0396] According to an embodiment, the first symbol information indicates the position of each symbol among one or more symbols of the first sub-block.

[0397] According to an embodiment, the information indicating the number of one or more sub-blocks for modulation compression is indicated by four bits in the section extension information. The first flag is indicated by one bit in the section extension information. The first scale offset information is indicated by fifteen bits in the section extension information. The first re-masking information is indicated by twelve bits in the section information.

[0398] According to an embodiment of the present disclosure, a method performed by a radio unit (RU) is provided. The method includes receiving, via a fronthaul interface, a control plane (C-plane) message from a distributed unit, the C-plane message including section extension information for modulation compression. The section extension information for modulation compression includes information indicating the number of one or more sub-blocks for modulation compression, first symbol information indicating one or more symbols of a first sub-block among the one or more sub-blocks, first PRB information indicating one or more physical resource blocks (PRBs) in the first sub-block, a first flag indicating whether the constellation of the first sub-block is shifted, first scale offset information indicating a first scale value to be applied to the first sub-block, and first re-masking information indicating whether the first scale value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0399] According to an embodiment, the section extension information for modulation compression further includes second symbol information indicating one or more symbols of a second sub-block among the one or more sub-blocks, second PRB information indicating one or more PRBs in the second sub-block, a second flag indicating whether the constellation of the second sub-block is shifted, second scale offset information indicating a second scale value to be applied to the second sub-block, and second re-masking information indicating whether the second scale value is applied to each resource element (RE) in the PRBs of the second sub-block.

[0400] According to an embodiment, the first PRB information includes information indicating a starting PRB of one or more PRBs of the first sub-block, and information indicating the number of one or more PRBs of the first sub-block.

[0401] According to an embodiment, the first symbol information indicates the position of each symbol among one or more symbols of the first sub-block.

[0402] According to an embodiment, information indicating the number of one or more sub - blocks for modulation compression is indicated by four bits in the section extension information. The first flag is indicated by one bit in the section extension information. The first scale offset information is indicated by fifteen bits in the section extension information. The first re - masking information is indicated by twelve bits in the section information.

[0403] According to an embodiment of the present disclosure, an electronic device of a distributed unit (DU) is provided. The electronic device includes at least one transceiver for a fronthaul interface, at least one processor, and a memory configured to store program instructions. The instructions, when executed by the at least one processor, cause the electronic device to perform functions including: generating a control plane (C - plane) message including section extension information for modulation compression; and transmitting the C - plane message to a radio unit (RU) through the fronthaul interface. The section extension information for modulation compression includes information indicating the number of one or more sub - blocks for modulation compression, first symbol information indicating one or more symbols of a first sub - block among the one or more sub - blocks, first PRB information indicating one or more physical resource blocks (PRBs) in the first sub - block, a first flag indicating whether the constellation of the first sub - block is shifted, first scale offset information indicating a first scale value to be applied to the first sub - block, and first re - masking information indicating whether the first scale value is applied to each resource element (RE) in the PRBs of the first sub - block.

[0404] According to an embodiment, the section extension information for modulation compression further includes second symbol information indicating one or more symbols of a second sub - block among the one or more sub - blocks, second PRB information indicating one or more PRBs in the second sub - block, a second flag indicating whether the constellation of the second sub - block is shifted, second scale offset information indicating a second scale value to be applied to the second sub - block, and second re - masking information indicating whether the second scale value is applied to each resource element (RE) in the PRBs of the second sub - block.

[0405] According to an embodiment, the first PRB information includes information indicating the starting PRB of one or more PRBs of the first sub - block and information indicating the number of one or more PRBs of the first sub - block.

[0406] According to an embodiment, the first symbol information indicates the position of each of one or more symbols of the first sub - block.

[0407] According to an embodiment, information for indicating the number of one or more sub-blocks for modulation compression is indicated by four bits in the section extension information. The first flag is indicated by one bit in the section extension information. The first scale offset information is indicated by fifteen bits in the section extension information. The first re-masking information is indicated by twelve bits in the section information.

[0408] According to an embodiment of the present disclosure, an electronic device of a radio unit (RU) is provided. The electronic device includes at least one transceiver for a fronthaul interface, at least one processor, and a memory configured to store program instructions. The instructions, when executed by the at least one processor, cause the electronic device to perform functions including: receiving, via the fronthaul interface, a control plane (C-plane) message from a distributed unit (DU) including section extension information for modulation compression. The section extension information for modulation compression includes information for indicating the number of one or more sub-blocks for modulation compression, first symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, first PRB information for indicating one or more physical resource blocks (PRBs) in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scale offset information for indicating a first scale value to be applied to the first sub-block, and first re-masking information for indicating whether the first scale value is applied to each resource element (RE) in the PRBs of the first sub-block.

[0409] According to an embodiment, the section extension information for modulation compression further includes second symbol information for indicating one or more symbols of a second sub-block among the one or more sub-blocks, second PRB information for indicating one or more PRBs in the second sub-block, a second flag for indicating whether the constellation of the second sub-block is shifted, second scale offset information for indicating a second scale value to be applied to the second sub-block, and second re-masking information for indicating whether the second scale value is applied to each resource element (RE) in the PRBs of the second sub-block.

[0410] According to an embodiment, the first PRB information includes information for indicating a start PRB of one or more PRBs of the first sub-block and information for indicating the number of one or more PRBs of the first sub-block.

[0411] According to an embodiment, the first symbol information indicates the position of each of the one or more symbols of the first sub-block.

[0412] According to an embodiment, information indicating the number of one or more sub - blocks for modulation compression is indicated by four bits in the section extension information. The first flag is indicated by one bit in the section extension information. The first scaling offset information is indicated by fifteen bits in the section extension information. The first remasking information is indicated by twelve bits in the section information.

[0413] According to an embodiment of the present disclosure, a non - transitory computer - readable medium including a memory is provided, the memory storing a program including instructions. When the instructions are executed by one or more processors, the instructions cause a distributed unit (DU) to generate a control plane (C - plane) message including section extension information for modulation compression and transmit the C - plane message to a radio unit (RU) through a fronthaul interface. The section extension information for modulation compression includes information indicating the number of one or more sub - blocks for modulation compression, first symbol information indicating one or more symbols of a first sub - block among the one or more sub - blocks, first PRB information indicating one or more physical resource blocks (PRBs) in the first sub - block, a first flag indicating whether the constellation of the first sub - block is shifted, first scaling offset information indicating a first scaling value to be applied to the first sub - block, and first remasking information indicating whether the first scaling value is applied to each resource element (RE) in the PRBs of the first sub - block.

[0414] According to an embodiment of the present disclosure, a non - transitory computer - readable medium including a memory is provided, the memory storing a program including instructions. When the instructions are executed by one or more processors, the instructions cause a radio unit (RU) to receive, through a fronthaul interface, a control plane (C - plane) message including section extension information for modulation compression from a distributed unit (DU). The section extension information for modulation compression includes information indicating the number of one or more sub - blocks for modulation compression, first symbol information indicating one or more symbols of a first sub - block among the one or more sub - blocks, first PRB information indicating one or more physical resource blocks (PRBs) in the first sub - block, a first flag indicating whether the constellation of the first sub - block is shifted, first scaling offset information indicating a first scaling value to be applied to the first sub - block, and first remasking information indicating whether the first scaling value is applied to each resource element (RE) in the PRBs of the first sub - block.

[0415] Various embodiments of the present disclosure may be implemented as software including one or more instructions stored in a machine-readable storage medium. For example, at least one command among the stored one or more instructions may be called by a processor of a machine from the storage medium, and the machine may be operated to perform at least one function according to the at least one called instruction. The one or more instructions include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory" means that the storage medium is tangible and does not include signals (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and temporarily stored in the storage medium. O-RAN enables the configuration of a virtualized intelligent network with standardized open interfaces. For network virtualization, operations according to embodiments may be implemented in the form of a recording medium (e.g., a memory).

[0416] According to an embodiment, a method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product is distributed in the form of a device-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or is distributed online (e.g., downloaded or uploaded) through an application store (e.g., PlayStore TM ) or is directly distributed between two user devices (e.g., smart phones). In the case of online distribution, at least a part of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium such as a memory of a server of a manufacturer, an application store server, or a relay server.

[0417] According to various embodiments, each of the above-described components (e.g., a module or a program) may include a single entity or multiple entities, and some of the multiple entities may be separately provided in other components. According to various embodiments, one or more of the foregoing corresponding components or operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., a module or a program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as the corresponding components among the multiple components before integration. According to various embodiments, operations performed by a module, a program, or other components are performed sequentially, in parallel, iteratively, or heuristically, or one or more operations are performed in a different order, or are omitted, or one or more other actions may be added.

[0418] A method according to various embodiments described in the claims and / or the specification of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0419] When implemented by software, a computer-readable storage medium storing one or more programs (software modules) can be provided. One or more programs stored in such a computer-readable storage medium are configured to be run by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute the methods according to the embodiments described in the claims or the specification of the present disclosure.

[0420] Such programs (e.g., software modules, software) can be stored in random access memory, non-volatile memory (including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, compact disc-ROM (CD-ROM), digital versatile disc (DVD)), other types of optical storage devices, or magnetic tape cartridges. Alternatively, it can be stored in a memory configured with a combination of some or all of these components. In addition, the corresponding component memories can be provided in multiple quantities.

[0421] In addition, the program can be stored in an attachable storage device that can be accessed via a communication network such as, for example, the Internet, intranet, local area network (LAN), wide area network (WAN), or storage area network (SAN), or a communication network configured with a combination thereof. Such a storage device can be accessed through an external port by a device implementing the embodiments of the present disclosure. In addition, a separate storage device on the communication network can be accessed by a device implementing the embodiments of the present disclosure.

[0422] In the above specific embodiments of the present disclosure, the components included according to the presented specific embodiments can be expressed in singular or plural forms. However, for convenience of description, such singular or plural expressions can be selected to better suit the presented situation, and the present disclosure is not limited to singular or plural components. Thus, any component expressed in plural form can be configured by a single component, or any component expressed in singular form can be configured by a plurality of components.

[0423] Although the present disclosure has been shown and described with reference to various embodiments of the present disclosure, those skilled in the art will understand that various changes can be made in form and detail without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a Distributed Unit (DU), the method comprising: Generating a C-plane message including section extension information for modulation compression, where the C-plane is the control plane; And Sending the C-plane message to a Radio Unit (RU) via a fronthaul interface, Wherein the section extension information for the modulation compression includes: Information for indicating the number of one or more sub-blocks for the modulation compression; First symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, First PRB information for indicating one or more Physical Resource Blocks (PRBs) in the first sub-block, A first flag for indicating whether the constellation of the first sub-block is shifted, First scale offset information for indicating a first scale value to be applied to the first sub-block, and First re-masking information for indicating whether the first scale value is applied to each Resource Element (RE) in the PRBs of the first sub-block.

2. The method according to claim 1, Among them, The section extension information for the modulation compression further includes: Second symbol information for indicating one or more symbols of a second sub-block among the one or more sub-blocks, Second PRB information for indicating one or more PRBs in the second block, A second flag for indicating whether the constellation of the second sub-block is shifted, Second scale offset information for indicating a second scale value to be applied to the second sub-block, and Second re-masking information for indicating whether the second scale value is applied to each Resource Element (RE) in the PRBs of the second sub-block.

3. The method according to claim 1, wherein, The first PRB information includes: Information for indicating the starting PRB of one or more PRBs of the first sub-block, and Information for indicating the number of one or more PRBs of the first sub-block.

4. The method according to claim 1, wherein, The first symbol information indicates the position of each symbol among the one or more symbols of the first sub-block.

5. The method according to claim 1, Among them, The information for indicating the number of one or more sub-blocks for the modulation compression is indicated by four bits in the section extension information, Wherein, the first flag is indicated by one bit in the section extension information, Wherein, the first scale offset information is indicated by fifteen bits in the section extension information, and Wherein, the first re-masking information is indicated by twelve bits in the section information.

6. A method performed by a Radio Unit (RU), the method comprising: Receiving a C-plane message from a Distributed Unit via a fronthaul interface, the C-plane message including section extension information for modulation compression, where the C-plane is the control plane, Wherein, the section extension information for the modulation compression includes: Information for indicating the number of one or more sub-blocks for the modulation compression; First symbol information for indicating one or more symbols of a first sub-block among the one or more sub-blocks, First PRB information for indicating one or more Physical Resource Blocks (PRBs) in the first sub-block, A first flag for indicating whether the constellation of the first sub-block is shifted, first scaling offset information for indicating a first scaling value to be applied to the first sub-block, and first re-masking information for indicating whether the first scaling value is applied to each resource element (RE) in the physical resource blocks (PRBs) of the first sub-block.

7. The method according to claim 6, Among them, The section extension information for the modulation compression further includes: second symbol information for indicating one or more symbols of a second sub-block in the one or more sub-blocks, second PRB information for indicating one or more PRBs in the second block, a second flag for indicating whether the constellation of the second sub-block is shifted, second scaling offset information for indicating a second scaling value to be applied to the second sub-block, and second re-masking information for indicating whether the second scaling value is applied to each resource element (RE) in the PRBs of the second sub-block.

8. The method according to claim 6, wherein The first PRB information includes: information for indicating a starting PRB of one or more PRBs of the first sub-block, and information for indicating the number of one or more PRBs of the first sub-block.

9. The method according to claim 6, wherein The first symbol information indicates the position of each of the one or more symbols of the first sub-block.

10. The method according to claim 6, Among them, The information for indicating the number of one or more sub-blocks for the modulation compression is indicated by four bits in the section extension information, wherein, the first flag is indicated by one bit in the section extension information, wherein, the first scaling offset information is indicated by fifteen bits in the section extension information, and wherein, the first re-masking information is indicated by twelve bits in the section information.

11. An electronic device of a distributed unit (DU), the electronic device comprising: at least one transceiver for a fronthaul interface; at least one processor; and a memory storing instructions, wherein, when the instructions are run by the at least one processor, the electronic device performs functions, the functions including: generating a C-plane message including section extension information for modulation compression, the C-plane being the control plane; and sending the C-plane message to a radio unit (RU) through the fronthaul interface, wherein, the section extension information for the modulation compression includes: information for indicating the number of one or more sub-blocks for the modulation compression; first symbol information for indicating one or more symbols of a first sub-block in the one or more sub-blocks, first PRB information for indicating one or more physical resource blocks (PRBs) in the first sub-block, a first flag for indicating whether the constellation of the first sub-block is shifted, first scaling offset information for indicating a first scaling value to be applied to the first sub-block, and first re-masking information for indicating whether the first scaling value is applied to each resource element (RE) in the PRBs of the first sub-block.

12. An electronic device of a radio unit (RU), the electronic device comprising: At least one transceiver for the fronthaul interface; At least one processor; And A memory that stores instructions, Wherein, when the instructions are run by the at least one processor, the electronic device is caused to perform functions, and the functions include: Receiving a C-plane message from a distributed unit DU through the fronthaul interface, the C-plane message including section extension information for modulation compression, and the C-plane being the control plane, Wherein, the section extension information for the modulation compression includes: Information indicating the number of one or more sub-blocks for the modulation compression; First symbol information indicating one or more symbols of a first sub-block among the one or more sub-blocks, First PRB information indicating one or more physical resource blocks PRBs in the first sub-block, A first flag indicating whether the constellation of the first sub-block is shifted, First scale offset information indicating a first scale value to be applied to the first sub-block, and First re-masking information indicating whether the first scale value is applied to each resource element RE in the PRBs of the first sub-block.

13. A non-transitory computer-readable medium, the non-transitory computer-readable medium including a memory configured to store program instructions, wherein, When the program instructions are run by one or more processors, the distributed unit DU is caused to perform functions, and the functions include: Generating a C-plane message including section extension information for modulation compression, and the C-plane being the control plane; and Sending the C-plane message to a radio unit RU through the fronthaul interface, Wherein, the section extension information for the modulation compression includes: Information indicating the number of one or more sub-blocks for the modulation compression; First symbol information indicating one or more symbols of a first sub-block among the one or more sub-blocks, First PRB information indicating one or more physical resource blocks PRBs in the first sub-block, A first flag indicating whether the constellation of the first sub-block is shifted, First scale offset information indicating a first scale value to be applied to the first sub-block, and First re-masking information indicating whether the first scale value is applied to each resource element RE in the PRBs of the first sub-block.

14. A non-transitory computer-readable medium, the non-transitory computer-readable medium including a memory configured to store program instructions, wherein, When the program instructions are run by one or more processors, the radio unit RU is caused to perform functions, and the functions include: Receiving a C-plane message from a distributed unit DU through the fronthaul interface, the C-plane message including section extension information for modulation compression, and the C-plane being the control plane, Wherein, the section extension information for the modulation compression includes: Information indicating the number of one or more sub-blocks for the modulation compression; First symbol information indicating one or more symbols of a first sub-block among the one or more sub-blocks, First PRB information indicating one or more physical resource blocks PRBs in the first sub-block, A first flag indicating whether the constellation of the first sub-block is shifted, First scale offset information indicating a first scale value to be applied to the first sub-block, and First re-masking information for indicating whether the first ratio value is applied to each resource element RE in the PRB of the first sub-block.

Images