Electronic device and method for providing modulation compression information through user plane

Abstract

According to an embodiment, a method performed by means of a distributed unit (DU) may include an operation of transmitting a control plane (C-plane) message including control information, and then generating a user plane (U-plane) message consisting of modulation compression information and segments, and including modulated and compressed data. The method may include the operation of sending a U-plane message to a radio unit (RU) over a fronthaul interface. The modulation compression information may include a flag for indicating whether the constellation has been shifted and scaling information for indicating a scaler value.

Description

Technical Field

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

[0002] As the transmission capacity in a wireless communication system increases, a functional division of a base station is being applied. According to the functional division, a base station can be divided into a distributed unit (DU) and a radio unit (RU). A fronthaul interface is defined for communication between the DU and the RU. Summary of the Invention

[0003] Technical Solution According to various embodiments, a method performed by a distributed unit (DU) may include, after transmitting a control plane (C-plane) message including control information, generating a user plane (U-plane) message including modulation compression information and modulated and compressed data configured as segments. The method may include transmitting the U-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

[0004] According to various embodiments, a method performed by a radio unit (RU) may include, after receiving a control plane (C-plane) message including control information, receiving, through a fronthaul interface, a user plane (U-plane) message including modulation compression information and modulated and compressed data configured as segments. The method may include identifying the modulation compression information and the modulated and compressed data based on the U-plane message. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

[0005] According to various embodiments, an electronic device performed by a distributed unit (DU) may include at least one transceiver including a fronthaul transceiver, and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to, after transmitting a control plane (C-plane) message including control information, generate a user plane (U-plane) message including modulation compression information and modulated and compressed data configured as segments. The at least one processor may be configured to transmit the U-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

[0006] According to various embodiments, an electronic device performed by a radio unit (RU) may include at least one transceiver including a fronthaul transceiver, and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to, after receiving a control plane (C-plane) message including control information, receive a user plane (U-plane) message including modulation compression information and modulated and compressed data configured to be segments through a fronthaul interface. The at least one processor may be configured to identify the modulation compression information and the modulated and compressed data based on the U-plane message. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 FIG. 6 shows a wireless communication system according to an embodiment.

[0008] Figure 2a FIG. 10 shows a fronthaul interface according to an embodiment.

[0009] Figure 2b FIG. 14 shows an open (O) radio access network (RAN) fronthaul interface according to an embodiment.

[0010] Figure 3a FIG. 18 shows a functional configuration of a distributed unit (DU) according to an embodiment.

[0011] Figure 3b FIG. 22 shows a functional configuration of a radio unit (RU) according to an embodiment.

[0012] Figure 4 FIG. 26 shows an example of a functional division between a DU and an RU according to an embodiment.

[0013] Figures 5a to 5b FIG. 30 shows an example of modulation compression (MC) according to an embodiment.

[0014] Figure 6 FIG. 34 shows an example of a U-plane message according to an embodiment.

[0015] Figure 7a And Figure 7b FIG. 40 shows an example of operations of a DU and an RU according to modulation compression applications according to an embodiment.

[0016] Figure 8 FIG. 44 shows an example of parameters including modulation compression information according to an embodiment.

[0017] Figure 9 FIG. 48 shows an example of configuring parameters including modulation compression information for each segment according to an embodiment.

[0018] Figure 10Shows an example of configuring parameters including modulation compression information for each RB according to an embodiment.

[0019] Figure 11 Shows an example of configuring parameters including modulation compression information for each RE according to an embodiment.

[0020] Figure 12 Shows an example of parameters including RE masking information according to an embodiment.

[0021] Figure 13a and 13b Shows an example of configuring parameters including RE masking information and parameters including modulation compression information as a parameter set in a U-plane message.

[0022] Figure 14 Shows an example of configuring parameters including RE masking information and modulation compression information as a parameter set in a U-plane message.

[0023] Figure 15 Shows an example of a U-plane message including parameters including RE masking information and modulation compression information according to an embodiment.

[0024] Figure 16 Shows an example of a U-plane message including parameters including RE masking information and modulation compression information according to an embodiment.

[0025] Figure 17 Shows an example of a U-plane message including a parameter indicating the format for sending modulation compression information according to an embodiment.

[0026] Figure 18 Shows an example of a U-plane message including a parameter indicating the format for sending modulation compression information according to an embodiment.

[0027] Figure 19 Shows an example of a U-plane message according to an embodiment, the U-plane message including a parameter indicating a method of configuring RE masking information in a section and a parameter indicating the number of re-masking for each PRB.

[0028] Figure 20 Shows an example of a U-plane message according to an embodiment, the U-plane message including a parameter indicating a method of configuring RE masking information in a section and a parameter indicating the number of re-masking for each PRB.

[0029] Figure 21 Shows an example of a U-plane message according to an embodiment, the U-plane message including a parameter indicating a method of configuring RE masking information in a section and a parameter indicating the number of re-masking for each PRB.

[0030] Figure 22 is a flowchart showing the operation of a DU according to an embodiment.

[0031] Figure 23 is a flowchart showing the operation of an RU according to an embodiment. Detailed Description

[0032] The terms used in this disclosure are only for describing specific embodiments and are not intended to limit the scope of another embodiment. Unless otherwise clearly specified in the context, 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 this disclosure. Among the terms used in this disclosure, terms defined in a general dictionary may be interpreted as having the same or similar meaning as the context meaning of the related art, and unless clearly defined in this disclosure, they are not interpreted as ideal or overly formal meanings. In some cases, even terms defined in this disclosure may not be interpreted as excluding embodiments of this disclosure.

[0033] In various embodiments of the disclosure described below, hardware methods will be described as examples. However, since various embodiments of the disclosure include technologies using both hardware and software, various embodiments of the disclosure do not exclude software-based methods.

[0034] For ease of explanation, in the following description, 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, processes), terms referring to data (e.g., packets, messages, user flows, information, bits, symbols, codewords), terms referring to channels, terms referring to network entities (e.g., distributed unit (DU), radio unit (RU), central unit (CU), CU-control plane (CP), CU-user plane (UP), open radio access network (O-RAN) DU (O-DU), O-RAN RU (O-RU), O-RAN CU (O-CU), O-RAN CU-CP (O-CU-CP), O-RAN CU-CP (O-CU-CP)) and terms referring to components of a device are used. Therefore, this disclosure is not limited to the terms to be described below, and another term with an equivalent technical meaning may be used. In addition, terms such as "... unit", "... device", "... object", and "... structure" may refer to at least one shaped structure or may refer to a unit with a processing function.

[0035] In addition, in the present disclosure, the terms "greater than" or "less than" may be used to determine whether a specific condition is satisfied or achieved, but this is only a description of an illustrative example and does not exclude the description 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 "greater than", a condition described as "less than or equal to" may be replaced by "less than", and a condition described as "greater than or equal to and less than" may be replaced by "greater than and less than or equal to". In addition, hereinafter, "A" to "B" means at least one element from A (including A) to B (including B).

[0036] Although the present disclosure describes various embodiments using terms used in some communication standards (e.g., the 3rd Generation Partnership Project (3GPP), the Scalable Radio Access Network (xRAN), the Open Radio Access Network (O-RAN)), these are only illustrative examples. The various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0037] Figure 1 A wireless communication system according to an embodiment is shown.

[0038] Reference Figure 1 , Figure 1 shows a base station 110 and a terminal 120 that are part of a node using a wireless channel in a wireless communication system. Figure 1 Only one base station is shown, but the wireless communication system may also include another base station that is the same as or similar to the base station 110.

[0039] The base station 110 is a network infrastructure that provides wireless access to the terminal 120. The base station 110 has a coverage area defined based on the distance at which signals can be transmitted. In addition to "base station", the base station 110 may also be referred to as "access point (AP)", "eNodeB (eNB)", "5th generation node", "next generation node B (gNB)", "radio point", "transmission / reception point (TRP)", or other terms having an equivalent technical meaning.

[0040] The terminal 120, which is a device used by a user, communicates with the base station 110 via a wireless channel. The link from the base station 110 to the terminal 120 is called the downlink (DL), and the link from the terminal 120 to the base station 110 is called the uplink (UL). In addition, although Figure 1Although not shown in the figure, the terminal 120 and another terminal can communicate with each other via a wireless channel. At this time, the link between the terminal 120 and the other terminal (device-to-device link (D2D)) is called a sidelink, and the sidelink can be used interchangeably with the PC5 interface. In some other embodiments, the terminal 120 can operate without user participation. According to an embodiment, the terminal 120, as a device for performing machine type communication (MTC), may not be carried by a user. In addition, according to an embodiment, the terminal 120 can be a narrowband (NB)-Internet of Things (IoT) device.

[0041] In addition to "terminal", the terminal 120 may also be referred to as a "user equipment (UE)", "client premise equipment (CPE)", "mobile station", "user station", "remote terminal", "wireless terminal", "electronic device", "user device", or other terms with equivalent technical meanings.

[0042] The base station 110 can perform beamforming with the terminal 120. The base station 110 and the terminal 120 can transmit and receive wireless signals in a relatively low frequency band (e.g., frequency range 1 (FR 1) of NR). In addition, the base station 110 and the terminal 120 can transmit and receive wireless signals in a relatively high frequency band (e.g., FR 2 (or FR 2-1, FR 2-2, FR 2-3) or FR 3) and millimeter wave (mmWave) frequency bands (e.g., 28 GHz, 30 GHz, 38 GHz, 60 GHz). The base station 110 and the terminal 120 can perform beamforming to improve the channel gain. Here, beamforming can include transmit beamforming and receive beamforming. The base station 110 and the terminal 120 can provide directivity to the transmitted signal or the received signal. To this end, the base station 110 and the terminal 120 can select a serving beam through a beam search or beam management process. After selecting the serving beam, subsequent communication can be performed through a resource having a QCL relationship with the resource of the transmitted serving beam.

[0043] 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, it can be evaluated that the first antenna port and the second antenna port are in a QCL relationship. For example, the large-scale characteristics can include at least one of delay spread, Doppler spread, Doppler frequency shift, average gain, average delay, and spatial receiver parameters.

[0044] Although Figure 1It 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. Additionally, the base station may or may not perform beamforming. That is, only one of the base station and the terminal may perform beamforming, or neither the base station nor the terminal may perform beamforming.

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

[0046] Traditionally, in a communication system with a relatively large base station cell radius, each base station is installed to include the functions of a digital processing unit (or distributed unit (DU)) and a radio frequency (RF) processing unit (or radio unit (RU)). However, with the use of high frequency bands in the fourth generation (4G) and / or subsequent communication systems (e.g., 5G) and the base station cell coverage range becoming smaller, the number of base stations covering a specific area has increased. The installation cost burden on the operator for installing base stations has also increased. To minimize the installation cost of base stations, a structure has been proposed in which the DU and RU of the base station are separated, one or more RUs are connected to one DU via a wired network, and one or more RUs are deployed to be geographically distributed to cover a specific area. Hereinafter, Figure 2a and Figure 2b describe the deployment structure and expansion examples of base stations according to various embodiments of the present disclosure.

[0047] Figure 2a FIG. shows a fronthaul interface according to an embodiment. Different from the backhaul between the base station and the core network, the fronthaul refers to an entity between the base station and the radio access network. Figure 2aAn example of a fronthaul structure between a DU 210 and an RU 220 is shown, but this is only for illustrative purposes and the present disclosure is not limited thereto. In other words, embodiments of the present disclosure can also be applied to fronthaul structures between a single DU and multiple RUs. For example, embodiments of the present disclosure can be applied to a fronthaul structure between a single DU and two RUs. Additionally, embodiments of the present disclosure can also be applied to a fronthaul structure between a single DU and three RUs.

[0048] Reference 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 be operated via an Fx interface. For the operation of the fronthaul 215, an interface such as the enhanced common public radio interface (eCPRI) or radio over ethernet (ROE) may be used.

[0049] With the development of communication technologies, mobile data services have increased, and thus the bandwidth requirements for the fronthaul between the digital unit and the radio unit have increased significantly. In deployments such as centralized / cloud radio access networks (C-RANs), the DU may be implemented to perform the functions of 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 for the PHY layer in addition to radio frequency (RF) functions.

[0050] The DU 210 may be responsible for the higher layer functions of the wireless network. For example, the DU 210 may perform the functions of the MAC layer and part of the PHY layer. Herein, part of the PHY layer is a function performed at a higher level within the functions of the PHY layer, and may include, for example, channel coding (or channel decoding), scrambling (or descrambling), modulation (or demodulation), and layer mapping (or layer demapping). According to an embodiment, if the DU 210 complies with the O-RAN standard, it may be referred to as an O-RAN DU (O-DU). In embodiments of the present disclosure, as needed, the DU 210 may be replaced with a first network entity for the base station (e.g., a gNB) and represented as such an entity.

[0051] The RU 220 may be responsible for the lower layer functions of the wireless network. For example, the RU 220 may perform a part of the PHY layer, as well as RF functions. Herein, a part of the PHY layer is a function performed at a relatively lower level within the functions of the PHY layer than the DU 210, and may include, for example, iFFT conversion (or FFT conversion), CP insertion (CP removal), and digital beamforming. In Figure 4In it, examples of such a specific functional division are described in 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 other terms with equivalent technical meanings. According to an embodiment, if RU 220 complies with the O-RAN standard, it may be referred to as an O-RAN RU (O-RU). In an embodiment of the present disclosure, as needed, RU 220 may be replaced by a second network entity for a base station (e.g., gNB) and represented as that entity.

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

[0053] The centralized unit (CU) may be responsible for functions at a higher layer than the DU by connecting to one or more DUs. For example, the CU may be responsible for functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, and the DU and RU may be responsible for lower layer functions. The DU may perform some functions of the radio link control (RLC), media access control (MAC), and PHY layers (high PHY), and the RU may perform the remaining functions of the PHY layer (low PHY). In addition, as an example, the digital unit (DU) may be included in the distributed unit (DU) according to the implementation of the distributed deployment of the base station. Hereinafter, unless otherwise defined, the operations of the digital unit (DU) and the RU are described, but various embodiments of the present disclosure may be applied to a base station configuration including a CU, and may also be applied to a configuration in which the DU is directly connected to the core network (i.e., the CU and the DU are integrated into a base station (e.g., an NG-RAN node) as a single entity).

[0054] Figure 2b FIG. shows the fronthaul interface of an open (O) radio access network (RAN) according to an embodiment. As the base station 110 according to the distributed deployment, an eNB or a gNB is illustrated.

[0055] ReferenceFigure 2b For example, the base station 110 may include an O-DU 251 and O-RUs 253-1, ..., O-RUs 253-n. Hereinafter, for ease of explanation, the operations and functions of O-RU 253-1 may be understood as the description of each other O-RU (e.g., O-RU 253-n).

[0056] The O-DU 251 is a logical node that includes functions in the functions of a base station (e.g., eNB, gNB) according to, in addition to the functions specifically allocated to O-RU 253-1, Figure 4 which will be described later. The O-DU 251 may control the operations of O-RUs 253-1, ..., and 253-n. The O-DU 251 may be referred to as a Lower Layer Split (LLS) Central Unit (CU). The O-RU 253-1 is a logical node that includes a subset of the functions in the functions of a base station (e.g., eNB, gNB) according to Figure 4 which will 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-DU 251.

[0057] The O-DU 251 may communicate with the O-RU 253-1 through an LLS interface. The LLS interface corresponds to a fronthaul interface. The LLS interface refers to a logical interface between the O-DU 251 and the O-RU 253-1 that uses a lower layer function split (i.e., function split within the PHY). The LLS-C between the O-DU 251 and the O-RU 253-1 provides the C-plane through the LLS interface. The LLS-U between the O-DU 251 and the O-RU 253-1 provides the U-plane through the LLS interface.

[0058] In Figure 2b the entities of the base station 110 have been described as O-DU and O-RU to describe O-RAN. However, these names shall not be construed as limiting the embodiments of the present disclosure. In the embodiments described with reference to Figures 3a to 15 the operations of the DU 210 may also be performed by the O-DU 251. The description of the DU 210 may be applied to the O-DU 251. Similarly, in the embodiments described with reference to Figures 3a to 15 the operations of the RU 220 may also be performed by the O-RU 253-1. The description of the RU 220 may be applied to the O-RU 253-1.

[0059] Figure 3a shows a functional configuration of a Distributed Unit (DU) according to an embodiment. The configuration exemplified as part of a base station in Figure 3a may be understood as Figure 2a the DU 210 (or Figure 2bConfiguration of the O-DU 251). Hereinafter, the terms “… unit” and “… device” used below refer to a unit that processes at least one function or operation, which can be implemented by hardware, or software, or a combination of hardware and software.

[0060] Reference Figure 3a , the DU 210 includes a transceiver 310, a memory 320, and a processor 330.

[0061] The transceiver 310 can perform functions for transmitting and receiving signals in a wired communication environment. The transceiver 310 can include a wired interface for controlling device-to-device direct connections through a transmission medium (such as copper wire, optical fiber). For example, the transceiver 310 can send an electrical signal to another device through copper wire, or perform the conversion between an electrical signal and an optical signal. The DU 210 can communicate with a radio unit (RU) through the transceiver 310. The DU 210 can be connected to a distributed deployed core network or a CU through the transceiver 310.

[0062] The transceiver 310 can also perform functions for transmitting and receiving signals in a wireless communication environment. For example, the transceiver 310 can perform the conversion function between a baseband signal and a bit string according to the physical layer specification of the system. For example, when transmitting data, the transceiver 310 generates complex-valued symbols by encoding and modulating the transmitted bit string. In addition, when receiving data, the transceiver 310 recovers the received bit string by demodulating and decoding the baseband signal. In addition, the transceiver 310 can include multiple transmit / receive paths. In addition, according to an embodiment, the transceiver 310 can be connected to a core network or other nodes (such as integrated access backhaul (IAB)).

[0063] The transceiver 310 can send and receive signals. For example, the transceiver 310 can send management plane (M plane) messages. For example, the transceiver 310 can send synchronization plane (S plane) messages. For example, the transceiver 310 can send control plane (C plane) messages. For example, the transceiver 310 can send user plane (U plane) messages. For example, the transceiver 310 can receive U plane messages. Although Figure 3a only the transceiver 310 is shown, the DU 210 can include two or more transceivers according to another embodiment.

[0064] The transceiver 310 sends and receives signals as described above. Therefore, all or some of the transceiver 310 can be referred to as a “communication unit”, “transmission unit”, “reception unit” or “transmission / reception unit”. In addition, in the following description, the transmission and reception performed through a wireless channel are used to include the meaning of the processing performed by the transceiver 310 as described above.

[0065] AlthoughFigure 3a 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. In other words, the backhaul transceiver converts a bit string transmitted from the base station to another node (e.g., another access node, another base station, an upper layer node, and a core network) into a physical signal, and converts a physical signal received from another node into a bit string.

[0066] The memory 320 stores basic programs, application programs, and data such as configuration information for the 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 a request from the processor 330.

[0067] The processor 330 controls the overall operation of the DU 210. The processor 380 may be referred to as a control unit. For example, the processor 330 transmits and receives signals through the transceiver 310 (or through a backhaul communication unit). In addition, the processor 330 writes and reads data in the memory 320. In addition, the processor 330 may execute functions of a protocol stack required by a communication standard. Although Figure 3a only the processor 330 is shown in Figure 3a , the DU 210 may include two or more processors according to another embodiment.

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

[0069] Figure 3b FIG. Figure 3b shows a functional configuration of a radio unit (RU) according to an embodiment. Figure 3b The configuration exemplified in Figure 3b as part of a base station may be understood as Figure 2a the configuration of the RU 220 or Figure 2b the O-RU 253-1 in Figure 2b . Hereinafter, the terms “... unit” and “...er” used hereinafter refer to a unit that processes at least one function or operation, which may be implemented by hardware, or software, or a combination of hardware and software.

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

[0071] 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 into an RF band signal and then transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the RF transceiver 360 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC.

[0072] The RF transceiver 360 may include multiple transmit / receive paths. In addition, the RF transceiver 360 may include an antenna unit. The RF transceiver 360 may include at least one antenna array composed of multiple antenna elements. In terms of hardware, the RF transceiver 360 may be composed of a digital circuit and an analog circuit (e.g., a radio frequency integrated circuit (RFIC)). Herein, the digital circuit and the analog circuit may be implemented in a single package. In addition, the RF transceiver 360 may include multiple RF chains. The RF transceiver 360 may perform beamforming. To provide directivity for the signals to be transmitted and received according to the settings of the processor 380, the RF transceiver 360 may apply beamforming weights to the signals. According to an embodiment, the RF transceiver 360 may include a radio frequency (RF) block (or RF unit).

[0073] According to an embodiment, the RF transceiver 360 may transmit and receive signals on a wireless access network. For example, the RF transceiver 360 may transmit a downlink signal. The downlink signal may include a synchronization signal (SS), a reference signal (RS) (e.g., a cell-specific reference signal (CRS), a demodulation (DM)-RS), system information (e.g., an MIB, an SIB, remaining system information (RMSI), other system information (OSI)), a configuration message, control information, or downlink data. In addition, for example, the RF transceiver 360 may receive an uplink signal. The uplink signal may include a random access-related signal (e.g., a random access preamble (RAP)) (or message 1 (Msg1), message 3 (Msg3)), a reference signal (e.g., a sounding reference signal (SRS), a DM-RS), or a power headroom report (PHR). Although Figure 3b only the RF transceiver 360 is shown, the RU 220 may include two or more RF transceivers according to another embodiment.

[0074] According to an embodiment, the RF transceiver 460 may transmit a RIM-RS. The RF transceiver 460 may transmit a first type of RIM-RS (e.g., the RIM-LS type 1 of 3GPP) to notify the detection of remote interference. The RF transceiver 460 may transmit a second type of RIM-RS (e.g., the RIM-RS type 2 of 3GPP) for notifying the presence or absence of remote interference.

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

[0076] As described above, the RF transceiver 360 and the fronthaul transceiver 365 transmit and receive signals. Therefore, all or some of the RF transceiver 360 and the fronthaul transceiver 365 can be referred to as a "communication unit", "transmission unit", "reception unit", or "transmission / reception unit". In addition, in the following description, the transmission and reception performed over a wireless channel are used to mean including the processing performed by the RF transceiver 360 as described above. In the following description, the transmission and reception performed over a wireless channel are used to include the processing performed by the RF transceiver 360 as described above.

[0077] The memory 370 stores basic programs, application programs, and data such as configuration information for the operation of the RU 220. The memory 370 can be referred to as a storage unit. The memory 370 can be configured with volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. In addition, the memory 370 provides the stored data according to a request from the processor 380. According to an embodiment, the memory 370 can include a memory for conditions, commands, or setting values related to an SRS transmission scheme.

[0078] The processor 380 controls the overall operation of the RU 320. The processor 380 can be referred to as a control unit. For example, the processor 380 transmits and receives signals through the RF transceiver 360 or the fronthaul transceiver 365. In addition, the processor 380 writes and reads data in the memory 370. In addition, the processor 380 can perform the functions of a protocol stack required by a communication standard. Although Figure 3b only the processor 380 is shown, the RU 220 can include two or more processors according to another embodiment. The processor 380 as an instruction set or code stored in the memory 370 can be instructions / codes that at least temporarily reside in the processor 380, or a storage space for storing instructions / codes, or a part of the circuit constituting the processor 380. In addition, the processor 380 can include various modules for performing communication. The processor 380 can control the RU 220 to perform operations according to embodiments to be described later.

[0079] Figure 3b The configuration of the RU 220 shown in FIG. 1 is only an example, and examples of the RU for performing the embodiments of the present disclosure are not limited to Figure 3b In some embodiments, some configurations may be added, deleted or changed.

[0080] Figure 4 An example of functional division between DU and RU according to an embodiment is shown. With the development of wireless communication technology (for example, the introduction of the 5th generation (5G) communication system (or new radio (NR) communication system)), the frequency band used has further increased. As the cell radius of the base station becomes very small, the number of RUs that need to be installed has further increased. In addition, in the 5G communication system, as the amount of data transmitted has significantly increased by more than 10 times, the transmission capacity of the wired network transmitted to the fronthaul has increased significantly. Due to the above factors, the installation cost of the wired network in the 5G communication system may increase significantly. Therefore, in order to reduce the transmission capacity of the wired network and reduce the installation cost of the wired network, a "functional division" can be used to reduce the transmission capacity of the fronthaul by transferring some functions of the DU's modem to the RU.

[0081] In order 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 include some functions of the physical layer. As the RU performs higher-layer functions, the throughput of the RU increases, which can increase the transmission bandwidth in the fronthaul while reducing the latency requirement constraints due to response processing. On the other hand, as the RU performs higher-layer functions, the virtualization gain decreases and the size, weight, and cost of the RU increase. Considering the trade-offs of the above advantages and disadvantages, it is necessary to achieve the optimal functional division.

[0082] refer to Figure 4 , showing the functional division in the physical layer below the MAC layer. In the case where the downlink (DL) sends a signal to the terminal through the wireless network, the base station can sequentially perform channel coding / scrambling, modulation, layer mapping, antenna mapping, RE mapping, digital beamforming (e.g., precoding), iFFT conversion / CP insertion, and RF conversion. In the case where the uplink (UL) receives a signal from the terminal through the wireless network, the base station can sequentially perform RF conversion, FFT conversion / CP removal, digital beamforming (pre-combination), RE demapping, channel estimation, layer demapping, demodulation, decoding / descrambling. Based on the above trade-offs, the division of uplink functions and downlink functions can be defined in various types by requirements between vendors, discussions on standards, etc.

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

[0084] According to an embodiment, in the case where a large amount of signal processing is expected, such as in an FR 1 MMU, it may be necessary to perform functional splitting at a relatively high layer (e.g., the fourth functional split 420b) to reduce the fronthaul capacity. In addition, in the functional splitting at too high a layer (e.g., the sixth functional split 430), since the control interface becomes complex and multiple PHY processing blocks are included in the RU, this may impose a burden on the implementation of the RU. Therefore, it may be necessary to perform appropriate functional splitting according to the layout and implementation method of the DU and the RU.

[0085] According to an embodiment, in the case where the precoding of the data received from the DU cannot be processed (i.e., in the case where there are limitations in the precoding capabilities of the RU), the third functional split 420a or a lower functional split (e.g., the second functional split 410) can be applied. On the contrary, in the case where there is the ability to process the precoding of the data received from the DU, the fourth functional split 420b or a higher functional split (e.g., the sixth functional split 430) can be applied.

[0086] In the following, in the present disclosure, unless otherwise specified, embodiments are described based on the third functional partition 420a (which may be referred to as Category A (CAT-A)) or the fourth functional partition 420b (which may be referred to as Category B (CAT-B)) for performing beamforming processing at the RU. The O-RAN standard differentiates the types of O-RUs according to whether the precoding function is located at the O-DU interface or the O-RU interface. An O-RU that does not perform precoding (i.e., 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.

[0087] 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, modulation / demodulation. In the following, the lower-layer PHY refers to the physical layer processing performed by the RU of the fronthaul interface. For example, the lower-layer PHY may include FFT / iFFT, digital beamforming, and physical random access channel (PRACH) extraction and filtering. However, the above standards do not exclude embodiments through other functional partitions. The functional configurations, signaling, or operations of the embodiments described below can be applied not only to the third functional partition 420a or the fourth functional partition 420b, but also to other functional partitions.

[0088] Embodiments of the present disclosure are exemplarily described when transmitting messages between a DU (e.g., Figure 2a DU 210) and an RU (e.g., Figure 2a RU 220) as the fronthaul interface, the standards of eCPRI and O-RAN. The Ethernet payload of the message may include an eCPRI header, an O-RAN header, and additional fields. In the following, the standard terms of eCPRI or O-RAN are used to describe various embodiments of the present disclosure, but in various embodiments of the present disclosure, other expressions having equivalent meanings to each term may be used as alternatives.

[0089] Ethernet and eCPRI, which are easy to share with the network, can be used as the transmission protocol for the fronthaul. The eCPRI header and the O-RAN header may be included in the Ethernet payload. The eCPRI header may be located in front of the Ethernet payload. The eCPRI header has the following content.

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

[0091] 2) ecpriReserved (3 bits): This parameter is reserved for further use of eCPRI.

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

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

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

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

[0096] 7) ecpriSeqid (2 bytes): This parameter provides unique message identification and sequencing at two levels. The first octet of this parameter is the sequence ID used to identify the message order in the eAxC message stream, and the sequence ID is used to ensure that all messages are received and out-of-order messages are reordered. The second octet of this parameter is the subsequence ID. The subsequence ID is used to verify sequencing and enable reordering when fragmentation occurs at the radio transmission level (eCPRI or IEEE-1914.3).

[0097] The eAxC identifier (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 eAxC ID can be distinguished as follows.

[0098] 1) DU_port ID: The DU_port ID is used to distinguish processing units in the O-DU (e.g., different 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 UL U-plane messages carrying the same sectionId data.

[0099] 2) BandSector_ID: The aggregated cell identifier (the identification of the band and sector supported by the O-RU).

[0100] 3) CC_ID: The CC_ID identifies the carrier component supported by the O-RU.

[0101] 4) RU_port ID: The RU_port ID designates a logical flow such as a data layer or a spatial stream, and a signal channel such as a logical flow of an independent parameter set (e.g., PRACH) or an SRS that requires specific antenna allocation.

[0102] The application protocols for fronthaul can include a control plane (C plane), a user plane (U plane), a synchronization plane (S plane), and a management plane (M plane).

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

[0104] The messages in the control plane, i.e., C plane messages, can be encapsulated based on a two-layer header method. The first layer can be configured with an eCPRI common header or an IEEE 1914.3 common header including a field for indicating the message type. The second layer is the application layer including the fields required for control and synchronization. In the application layer, a section defines the characteristics of the U plane data transmitted or received on a beam with a pattern ID. The following are the section types supported within the C plane.

[0105] The section type can indicate the purpose of the control message transmitted in the control plane. For example, the purposes of the section type are as follows.

[0106] 1) sectionType = 0: Used to indicate resource blocks or symbols not used in the DL or UL.

[0107] 2) sectionType = 1: For most DL / UL radio channels. In this article, "most" refers to channels that do not require time or frequency offsets, such as those required for hybrid parameter set channels.

[0108] 3) sectionType = 2: Reserved for further use 4) sectionType = 3: PRACH and hybrid parameter set channels. Channels that require time or frequency offsets or are different from the nominal SCS value.

[0109] 5) sectionType = 4: Reserved for further use 6) sectionType = 5: UE scheduling information. The UE scheduling information is sent so that the RU can perform real-time BF weight calculation (O-RAN optional BF method) 7) sectionType = 6: Send UE-specific channel information. The UE channel information is sent periodically so that the RU can perform real-time BF weight calculation (O-RAN optional BF method) 8) sectionType = 7: For LAA support In O-RAN, various compression techniques can be used in each section to improve the data transmission efficiency between the DU and the RU. Compression techniques include, for example, uncompressed technique, block floating-point compression (BFPC) technique, and modulation compression (MC) technique. The IQ data frame of the O-RAN standard can include a user data compression header (e.g., udCompHdr). The user data compression header is defined and transmitted by the bit width (e.g., 4-bit "udIqWidth") and the compression method (e.g., 4-bit "udCompMeth"). For example, the compression method can be defined as shown in the following table.

[0110] [Table 1]

[0111] Among the above compression techniques, the MC technique is a lossless method, which has no data loss and high compression efficiency. The MC technique relies on the characteristic that modulation 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 the quadrature phase shift keying (QPSK) modulation symbol has only two possible states for I and two possible states for Q, the QPSK modulation symbol can be represented by a single bit of the I component and a single bit of the Q component without information loss. Another example is that a symbol using 64 QAM modulation can be represented by at most 3 bits of the I component and 3 bits of the Q component.

[0112] 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 be used. That is to say, 32 bits can be used to transmit data in the U-plane message. If QPSK modulation is used for modulation compression, the number of bits transmitted can be reduced from 32 bits to 2 bits. If 16 QAM modulation is used for modulation compression, the number of bits transmitted can be reduced from 32 bits to 4 bits. If 64 QAM modulation is used for modulation compression, the number of bits transmitted can be reduced from 32 bits to 6 bits.

[0113] To represent the values of the I and Q components that can be represented by a single word width, enabling multiple constellation sizes to overlap, the constellation can be "shifted" so that each constellation point is represented in two's complement. For example, the QPSK constellation can be shifted by -1 / 2. The I component can be -1 or 0. The Q component can be -1 or 0. Additionally, for example, the 16 QAM constellation 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. Additionally, for example, the 64 QAM constellation 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.

[0114] The MC technique converts bit-level information into shifted constellation points (SCPs). The DU (e.g., DU 210) can send a U-plane message including information converted according to the SCPs to the RU (e.g., RU 220). The DU 210 can send a constellation shift flag ("csf") to the RU 220 to indicate whether to shift. For example, when the value of the "csf" is "1", the shift value of each constellation point in a specific bit width can be defined as shown in Table 2.

[0115] [Table 2]

[0116] The compressed data according to the MC technique does not represent the actual power values. To enable the RU to set the power level in the modulated and compressed data, the DU 210 can send a modulation compression scaler value ("modCompScaler") to the RU 220. The "modCompScaler" parameter indicates the scaling factor to be applied to the unshifted constellation points during decompression. In the O-RAN standard, the "modCompScaler" parameter can be provided to the RU through section extension information (e.g., SectionExtension Type 4). The "modCompScaler" parameter can indicate the exponent component and the mantissa component through the following equation.

[0117] [Equation 1]

[0118] "Mantissa" represents the mantissa component of the indicated value. "Exponential" represents the exponential component of the indicated value. modCompScaler[k] indicates the (k + 1)-th bit of the "modCompScaler" parameter. For example, modCompScaler[0] indicates the first bit of the "modCompScaler" parameter. modCompScaler

[14] indicates the 15th bit of the "modCompScaler" parameter.

[0119] The 4 most significant bits among the 15 bits of the "modCompScaler" parameter represent the exponential component, and the 11 least significant bits among the 15 bits of the "modCompScaler" parameter represent the mantissa component. Therefore, the value indicated by the "modCompScaler" parameter is as shown in the following equation.

[0120] [Equation 2]

[0121] "Mantissa" represents the mantissa component of the indicated value. "Exponent" represents the exponential component of the indicated value.

[0122] The section extension 4 for transmitting the "modCompScaler" parameter in the O-RAN standard is as shown in the following table.

[0123] [Table 3]

[0124] The DU 210 can transmit the modulation compression power scaling RE mask (mcScaleReMask) to the RU 220. The "mcScaleReMask" parameter can indicate the position of the RE together with the same scaling and modulation type within the PRB. Similar to the "modCompScaler" parameter, the DU 210 can transmit the scaling value (mcScaleOffset) for modulation compression to the RU220.

[0125] The "mcScaleOffset" parameter indicates the scaling factor applied to the unshifted constellation points during decompression. In the O-RAN standard, the "mcScaleOffset" parameter can be provided to the RU 220 through section extension information (e.g., Section Extension Type 4). The "mcScaleOffset" parameter can indicate the exponential component and the mantissa component through the following equation.

[0126] [Equation 3]

[0127] "Mantissa" represents the mantissa component of the indicated value. "Exponent" represents the exponent component of the indicated value. mcScaleOffset[k] represents the (k + 1)-th bit of the "mcScaleOffset" parameter. For example, mcScaleOffset[0] represents the first bit of the "mcScaleOffset" parameter. mcScaleOffset

[14] represents the 15th bit of the "mcScaleOffset" parameter.

[0128] The 4 most significant bits out of the 15 bits of the "mcScaleOffset" parameter represent the exponent component, and the 11 least significant bits out of the 15 bits of the "mcScaleOffset" parameter represent the mantissa component. Thus, the value indicated by the "mcScaleOffset" parameter is as shown in the following equation.

[0129] [Equation 4]

[0130] "Mantissa" represents the mantissa component of the indicated value. "Exponent" represents the exponent component of the indicated value.

[0131] The section extension 5 for passing the "mcScaleOffset" parameter in the O-RAN standard is as shown in the following table. Table 4 indicates one scaler value, and Table 5 indicates two scaler values.

[0132] [Table 4]

[0133] [Table 5]

[0134] The section extension information of the above Tables 3 to 5 may be included in the C-plane message. The RU 220 may recover the original signal expected by the 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, the RU 220 may obtain the original signal from the compressed bits based on the "csf" parameter. According to an embodiment, the RU 220 may obtain the original signal from the compressed bits based on the "modCompScaler" parameter. According to an embodiment, the RU 220 may obtain the original signal from the compressed bits based on the "mcscaleoffset" parameter and the "mcScaleReMask" parameter.

[0135] Figures 5a to 5bShows an example of modulation compression (MC) according to an embodiment. Terms such as “… unit” and “… er” may refer to a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

[0136] Referring Figure 5a , the DU 510 may include a scheduling unit 511, a C-plane message generation unit 513, and a U-plane message generation unit 515. The scheduling unit 511 may perform scheduling on the U-plane message according to the above modulation compression technique. The C-plane message generation unit 513 may generate a C-plane message including control information according to the above modulation compression technique. For example, the C-plane message generation unit 513 may generate a C-plane message including segment extension 4 as shown in Table 3. In addition, for example, the C-plane message generation unit 513 may generate a C-plane message including segment extension 5 as shown in Table 4 or Table 5. The U-plane message generation unit 515 may generate a U-plane message including an I component and a Q component according to the above modulation compression technique.

[0137] The RU 520 may include a C-plane analysis unit 521, a buffer 523, a U-plane analysis unit 525, and a modulation decompression unit 527. The C-plane analysis unit 521 may receive a C-plane message from the DU 510. The C-plane analysis unit 521 may obtain 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 analysis unit 521 may obtain segment information from the C-plane message. The C-plane analysis unit 521 may store the parameters related to modulation compression and the segment information in the buffer 523. The U-plane analysis unit 525 may receive a U-plane message from the DU 510. The U-plane analysis unit 525 may include the I component and the 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 analysis unit 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 diagram according to the “csf” value and apply a scaling factor to the constellation diagram type shown in the segment. The segment has several 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 RE of the PRB and a scaling factor (e.g., “modCompScaler” when using segment extension 4, “mcScaleOffset” when using segment extension 5).

[0138] The O-RAN standard provides section-based modulation compression. If compression techniques other than modulation compression are used when transmitting data in a specific time slot, the section can be configured based on the beamId (or ueId) allocation of data resources (e.g., RE / PRB / symbol). However, applying modulation compression may require all PRBs and symbols in the section to use the same "csf" and the same scaler value (e.g., "modCompScaler" when using section extension 4, "mcScaleOffset" when using section extension 5). In other words, since the section is configured based on the "csf" and scaler value of the data, relatively more sections can be configured in modulation compression compared to compression techniques other than modulation compression. For example, if the resource region has the same beamId but different "csf" and different scaler values, the resource region may need to be divided into different sections.

[0139] Reference Figure 5b , the resource grid 551 indicates the data allocation according to the independent data type. The vertical axis of the resource grid 551 can indicate the frequency domain (unit: PRB), and the horizontal axis can indicate the time domain (unit: symbol). For example, data 551a, data 551b, data 551c, data 551d, data 551e, data 551f, data 551g, and data 551h can be included in the region of the resource grid 551.

[0140] The resource grid 553 indicates the data allocation without using modulation compression. The data transmitted separately by the DU 510 (e.g., data according to beamID (or ueId)) can have a unique modulation type. However, if the modulation compression technique is not applied, the DU 510 will define a certain region of the PRB section and the symbol section as a section, and the DU 510 can send the data on this section to the RU 520. For example, three sections (e.g., section #0, section #1, and section #2) can be included in the resource grid 553. Section #1 can include the resource regions of data 551b, data 551c, and data 551d. Section #2 can include the resource regions of data 551e, data 551f, data 551g, and data 551h.

[0141] The resource grid 555 indicates data allocation using modulation compression. A unique modulation type can be applied to each individual data. For example, data 551c and data 551d are frequency-divided into a specific symbol (e.g., symbol #4). That is, data 551c and data 551d can be divided into different RB regions within the same symbol. If the same modulation compression is applied to each section, data 551c and data 551d need to be allocated to different sections. That is, different from the resource grid 553, data 551d may need to be included in a section different from the section including data 551c. In addition, since the modulation type can be distinguished for each symbol for modulation compression, time division can be performed on this section. For example, independent modulation compression can be applied to each of data 551e, data 551f, data 551g, and data 551h. If the same modulation compression is applied to each section, data 551e, data 551f, data 551g, and data 551h need to be allocated to different sections.

[0142] Although Figure 5b not shown in the figure, in addition to separation by RB units, when modulation compression is performed using section extension 4, separation by RE can also occur.

[0143] As Figure 5b shown, compared with data transmission without using modulation compression, data transmission using modulation compression may require more sections. However, as the number of segments increases, the fronthaul transmission volume can also increase. Since the overhead for defining this section increases and parameters other than modulation compression are repeatedly transmitted, the efficiency of the RU may decrease.

[0144] To reduce the above problems, according to an embodiment of the present disclosure, modulation compression information (e.g., "csf" and scaler values) for data allocated within some regions of a section can be provided through a U-plane message. Several regions can be configured within a section, and modulation compression information can be allocated to each region. The DU (e.g., DU 510) can send a U-plane message including the modulation compression information for each region of this section to the RU (e.g., RU520). To illustrate the embodiments of the present disclosure, the region used for modulation compression within a section is referred to as a modulation compression (MC) block, and terms belonging to or having equivalent technical meanings such as data block, sub-block, data sub-block, MC sub-block, section sub-block, MC region, section sub-region, and section partial region can also be used instead.

[0145] Figure 6Shows an example of a U-plane message according to an embodiment. The RU may load the IQ sampling data of the data section into one U-plane packet through a C-plane message including section extension information for providing U-plane merging. For example, each section type of the data section may be 1, 3, or 5.

[0146] Reference Figure 6 , the U-plane message 600 according to U-plane merging may include a transport header, an application layer header, section header information 610, and individual PRB information 620. Descriptions of the transport header and the application layer header can be referred to in Figure 9 .

[0147] The section header information 610 may include "sectionId" indicating the section identifier, "rb" indicating whether to use each RB or each other RB, "symInc" referring to the symbol number increment command, "startPrbu" indicating the starting PRB number of the U-plane section, and "numPrbu" indicating the number of consecutive PRBs of each data section. The values of the parameters of the section header information 610 (such as rb, startPrbu, and numPrbu) ensure that the data sections never overlap. To describe a section within a C-plane message, multiple U-plane data sections related to that section are required to define the PRBs to which the included IQ data can be applied. Generally, the data sections in the U-plane may include the PRBs corresponding to the section description of the C-plane message.

[0148] The section header information 610 may include "udCompHdr" indicating the compression method and IQ bit width of the user data for the data section. The compression method may be uncompressed, block floating point (BFP), block scaling, μ-law, modulation compression, "BFP and selective RE transmission", or "modulation compression and selective RE transmission". The section header information 610 may include "udCompLen", which specifies the total number of octets including the padding within the PRB field up to the end of the current section. The compression method may be set by the M-plane or specified in the "udCompHdr" of the data section including the PRB. The section header information 610 may include a "reserved" field, which is the bits reserved for further use.

[0149] The individual PRB information 620 may include a "udCompParam" field to indicate parameters applied to the compression method for the PRB. The individual PRB information 620 may include in-phase sampling (iSample) and quadrature sampling (qSample) for each RE of the PRB. According to an embodiment, a section may be configured with at least one PRB. The U-plane message 600 may include individual PRB information for each of the at least one PRB. For example, the individual PRB information 620 may include PRB information for a first PRB that configures a section. Although not shown, the PRB information regarding a second PRB that configures a section may be configured to follow the individual PRB information 620.

[0150] Figure 7a and Figure 7b An example of the operations of the DU and RU according to the application of modulation compression according to an embodiment is shown. Different from the above embodiments, embodiments for supporting information transmission for MC processing, which save RU resources and prevent section separation, may be described below. In Figure 5a , the RU 520 should include a separate memory (e.g., buffer 523) for modulation decompression, and a matching process between the compressed data and the modulation compression information and a device for the matching process are required. Therefore, the use of resources may increase. In Figure 7a and Figure 7b , embodiments for transmitting modulation compression information by adding modulation compression information to the U-plane message (or U-plane packet) of the corresponding section to reduce resource use and prevent section separation as much as possible may be described. Referring to Figure 7a , the DU 710 may include an M-plane message processing unit 711, a scheduling unit 713, a C-plane message generation unit 715, and a U-plane message generation unit 717.

[0151] According to an embodiment, the M-plane message processing unit 711 may generate an M-plane message including information on whether the format of the U-plane message is supported. For example, the M-plane message processing unit 711 may generate an M-plane message that includes information indicating that the U-plane message to be sent includes modulation compression information. For example, the DU 710 may determine (or identify) the compression technique of the data to be sent through the U-plane message. The DU 710 may generate an M-plane message including information indicating that the U-plane message to be sent includes modulation compression information by using the M-plane message processing unit 711. The M-plane message processing unit 711 may receive an M-plane message from the RU 720. The DU 710 may execute a negotiation protocol by exchanging management information with the RU 720 by using the M-plane message processing unit 721.

[0152] The scheduling unit 713 can perform scheduling on the U-plane message according to the modulation compression technology described above.

[0153] The C-plane message generation unit 715 can generate a C-plane message including control information. For example, the C-plane message may not include a section extension 4 such as Table 3. For example, the C-plane message may not include modulation compression information.

[0154] The U-plane message generation unit 717 can generate a U-plane message including the I and Q components according to the modulation compression technology. For example, the U-plane message can not only include the I and Q components according to the modulation compression technology, but also include modulation compression information according to the modulation compression technology.

[0155] The RU 720 can include an M-plane message processing unit 721, a C-plane message analysis unit 723, and a U-plane message analysis unit 725.

[0156] The M-plane message processing unit 721 can receive an M-plane message from the DU 710. For example, the M-plane message processing unit 721 can obtain information on whether the format of the U-plane message included in the M-plane message is supported. For example, the M-plane message processing unit 721 can obtain information indicating that the U-plane message to be received includes modulation compression information. The M-plane message processing unit 721 can generate an M-plane message. The M-plane message processing unit 721 can send the generated M-plane message to the DU 710. The RU 720 can perform a negotiation protocol by exchanging management information with the DU 710 using the M-plane message processing unit 721.

[0157] The C-plane message analysis unit 723 can receive a C-plane message from the DU 710. The C-plane message analysis unit 723 can obtain section information from the C-plane message.

[0158] The U-plane message analysis unit 725 can receive a U-plane message from the DU 710. The U-plane message analysis unit 725 can obtain the I and Q components included in the U-plane message. The U-plane message analysis unit 725 can obtain the modulation compression information included in the U-plane message. For example, the modulation compression information can include parameters related to modulation compression.

[0159] According to an embodiment, the U-plane message analysis unit 725 can perform all or some of the functions of the modulation decompression unit 527 in FIG. 5. The U-plane message analysis unit 725 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, during decompression, the U-plane message analysis unit 725 can "unshift" the constellation diagram according to the value of "csf" and apply a scaling factor for the type of constellation diagram shown in the section.

[0160] Reference Figure 7b In operation 751, the DU 710 may exchange M-plane messages with the RU 720. The DU 710 may determine the compression technique for the data to be sent via the U-plane message. For example, the DU 710 may generate an M-plane message that includes information indicating that the U-plane message to be sent includes modulation compression information, and send the generated M-plane message to the RU 720.

[0161] In operation 753, the DU 710 may perform scheduling. For example, the DU 710 may perform scheduling of the data to be sent to the RU 720. The DU 710 may obtain scheduling information.

[0162] In operation 755, the DU 710 may send a C-plane message to the RU 720 based on the scheduling information. For example, the DU 710 may generate a C-plane message based on the scheduling information. The C-plane message may be configured with at least one C-plane message. Different from FIG. 5, the C-plane message may not include modulation compression information.

[0163] According to an embodiment, the DU 710 may send a C-plane message to the RU 720 via a first time slot. The RU 720 may receive the C-plane message from the DU 710 via the first time slot. The RU 720 may parse the C-plane message. The RU 720 may obtain the information (e.g., control information) included in the C-plane message based on the parsing of the C-plane message.

[0164] In operation 757, the DU 710 may send a U-plane message to the RU 720. For example, the DU 710 may generate a U-plane message including an I component and a Q component according to the modulation compression technique. For example, the U-plane message may include an I component and a Q component according to the modulation compression technique, and modulation compression information according to the modulation compression technique. The DU 710 may send a U-plane message including an I component and a Q component according to the modulation compression technique and modulation compression information according to the modulation compression technique to the RU 720.

[0165] According to an embodiment, the DU 710 may send a C-plane message to the RU 720 and then send the U-plane message to the RU 720 via a second time slot. For example, the second time slot may be a time slot set after the first time slot. For example, the U-plane message may include modulation compression information corresponding to each section. The RU 720 may receive the U-plane message via the second time slot. The RU 720 may parse the U-plane message. The RU 720 may obtain the compressed data and modulation compression information based on the parsing of the U-plane message. The RU 720 may recover the compressed data based on the compressed data and modulation compression information.

[0166] For example, in a case where modulation compression information is included in a U-plane message, fewer segments can be configured than in a case where modulation compression information is included in a C-plane message. In addition, a separate memory (or buffer) and a matching process between compressed data and modulation compression information can be omitted. Therefore, resources of the RU 720 can be saved.

[0167] Figure 8 An example of parameters including modulation compression information according to an embodiment is shown.

[0168] Figure 9 An example of configuring parameters including modulation compression information for each segment according to an embodiment is shown.

[0169] Figure 10 An example of configuring parameters including modulation compression information for each RB according to an embodiment is shown.

[0170] Figure 11 An example of configuring parameters including modulation compression information for each RE according to an embodiment is shown.

[0171] Referring Figure 8 , the modCompParam 800 can be configured in the U-plane message. The modCompParam 800 can include modulation compression information. For example, the modCompParam 800 can be configured for each segment of the U-plane (or U-plane message). For example, the modCompParam 800 can be configured for each RE within the segment. For example, the modCompParam 800 can be configured for each RB (or PRB) within the segment.

[0172] According to an embodiment, the modCompParam 800 can include a set of csf 810 and a modCompScaler 820. The csf810 can be configured with 1 bit. The modCompScaler 820 can be configured with 15 bits. For example, the csf 810 can refer to a parameter for indicating whether data converted to shifted constellation points (SCPs) is shifted in the segment or in a part of the segment. For example, the modCompScaler 820 can refer to a parameter indicating a modulation compression scaling value (or scaler value) so that the RU 720 can set a power level for the modulated and compressed data.

[0173] Referring Figures 9 to 11 , the U-plane messages 900, 1000, or 1100 can be configured with a transport layer and an application layer.

[0174] The application layer may be required within the transport payload. The application layer may be configured with a common header for time reference. This may be followed by information and parameters that depend on and are specific to the type of section used. Data from several sections of the same value may be sorted in order within the payload.

[0175] To minimize the packet rate through the interface, messages should be filled with subsequent sections as much as possible. If the section type has no difference from the format and value of the U-plane application header or the format of the U-plane section header, data in sections of another section type may be mixed in a single U-plane message of a given eAxC.

[0176] Reference Figure 9 , the U-plane message 900 may include transport header (e.g., eCPRI header or IEEE 1914.3) information, common header information 910, section header information 921 and 922, and individual PRB information 931 and 932.

[0177] The transport header may include "ecpriVersion", "ecpriReserved", "ecpriConcatenation", "ecpriMessage", "ecpriPayload", "ecpriRtcid / ecpriPcid", and "ecpriSeqid" as described above.

[0178] The common header information 910 may include "dataDirection" indicating the data transmission direction of the base station (e.g., gNB), "payloadVersion" indicating the payload protocol version of the IE in the application layer, and "filterindex" indicating the index of the channel filter between the IQ data and the air interface to be used in both DL and UL.

[0179] The common header information 910 may include information indicating the location of the time resource to which the message can be applied. The location of the time resource may be indicated by frame, subframe, time slot, or symbol. The common header information 910 may include "frameId" indicating the frame number, "subframeId" indicating the subframe number, "slotId" indicating the time slot number, and "SymbolId" indicating the symbol number. The frame is determined based on 256 modulo operation. The subframe has a unit of 1 ms included in a 10 ms frame. The time slot numbers within the subframe are numbered and, depending on the parameter set, the maximum size may be 1, 2, 4, 8, or 16.

[0180] The section header information 921 and 922 may include Figure 6The section header information 610. modCompParam 811 and 812, as parameters including modulation compression information, may be included in the section header information 921 and 922 of each section. For example, modCompParam 811 and 812 may correspond to Figure 8 the modCompParam 800. According to an embodiment, modCompParam 811 and 812 may not be included in the U-plane message 900.

[0181] modCompParam 811 and 812, as parameters including modulation compression information, may be configured for each section. The section header information 921 may include modCompParam 811. The section header information 922 may include modCompParam 812.

[0182] Reference Figure 10 , the U-plane message 1000 may include transmission header (e.g., eCPRI header or IEEE 1914.3) information, common header information 1010, section header information 1020, and individual PRB information 1031 and 1032.

[0183] The common header information 1010 may correspond to Figure 9 the common header information 910. The section header information 1020 may correspond to Figure 6 the section header information 610.

[0184] The individual PRB information 1031 and 1032 may include the individual PRB information 521 and 522 of FIG. 5. modCompParam 821 and 822, as parameters including modulation compression information, may be included in the individual PRB information 1031 and 1032 of each PRB. For example, modCompParam 821 and 822 may correspond to Figure 8 the modCompParam 800.

[0185] modCompParam 821 and 822, as parameters including modulation compression information, may be configured for each RB. The first PRB information 1031 may include modCompParam 821. The second PRB information 1032 may include modCompParam 822.

[0186] Reference Figure 11 , the U-plane message 1100 may include transmission header information, common header information 1110, section header information 1120, and individual PRB information 1130.

[0187] The common header information 1110 may correspond to Figure 9The common header information 910. The section header information 1120 can correspond to Figure 6 the section header information 610.

[0188] The individual PRB information 1130 can include individual RE information. The modCompParam 831 and 832, as parameters including modulation compression information, can be included in the individual PRB information 1130 of each PRB. For example, the modCompParam 831 and 832 can correspond to Figure 8 the modCompParam 800. The modCompParam 831 and 832, as parameters including modulation compression information, can be configured for each RE. The individual PRB information 1130 can include the modCompParam831 and 832. Although only the modCompParam 831 and 832 are shown for ease of illustration, the modCompParam can be configured according to 12 REs.

[0189] For example, the modCompParam 831 can be after the first in-phase sampling (iSample) and the first quadrature sampling (qSample). The modCompParam 831 can include the modulation compression information about the first iSample and the first qSample.

[0190] For example, the modCompParam 832 can be after the second in-phase sampling (iSample) and the second quadrature sampling (qSample). The modCompParam 832 can include the modulation compression information about the second iSample and the second qSample.

[0191] Refer to Figures 9 to 11 , the M-plane parameters can be configured to support the U-plane messages 900, 1000, or 1100. The negotiation protocol between the DU and the RU for supporting the U-plane messages 900, 1000, or 1100 can be set.

[0192] For example, at least one M-plane parameter can be configured to check whether the DU and the RU support the U-plane messages 900, 1000, or 1100. The transmission and negotiation protocol for exchanging at least one M-plane parameter between the DU and the RU can be configured. The transmission and negotiation protocol for exchanging at least one M-plane parameter can be performed according to Figure 7b the operation 751.

[0193] Figure 12 An example of a parameter including RE mask information according to an embodiment is shown.

[0194] Figure 13a and13b An example is shown in which parameters including RE mask information and parameters including modulation compression information are configured as a parameter set in a U-plane message.

[0195] Figure 14 An example is shown in which parameters including RE mask information and modulation compression information are configured as a parameter set in a U-plane message.

[0196] Reference Figures 12 to 14 , modulation compression information for each section of the U-plane message may be included, or modulation compression and / or RE mask information for each RB of the U-plane message may be included. In Figures 12 to 14 , modulation compression information for each section or each RB may be configured as a parameter set in the U-plane message. RE mask information for each section or each RB may be configured as a parameter set in the U-plane message.

[0197] According to an embodiment, the modulation compression information of the U-plane message may be configured as Figure 8 the modCompParam 800 of . The modCompParam 800 may include csf and modCompScaler.

[0198] Reference Figure 12 , the RE mask information of the U-plane message may be configured with modCompRemask 1200. The modCompRemask 1200 may be configured with 12 bits. The modCompRemask 1200 may include information about the RE mask to which the modCompParam800 is applied. According to an embodiment, multiple modCompRemask 1200 may be included in one section. For example, the sum of all remasks may be 0xfff. For example, all bits of the modCompRemask 1200 may be set to "1".

[0199] Reference Figure 13a and Figure 13b , several modCompParam 800 may be transmitted as a parameter set. Several modCompParam 800 may be configured as modCompParam 1320. When several modCompParam 800 are transmitted as a parameter set, several modCompRemask 1200 may also be transmitted as a parameter set. Several modCompRemask 1200 may be configured as modCompRemask 1310.

[0200] For example, modCompRemask 1310 may include RE mask information. modCompRemask 1310 may include first RE mask information, second RE mask information, and third mask information for one section (or one RB). The first RE mask information may refer to the RE mask information of the first area (or the first block) within one section (or one RB). The first RE mask information may be referred to as the 0th scaled modCompRemask. The second RE mask information may refer to the RE mask information of the second area (or the second block) within one section (or one RB). The second RE mask information may be referred to as the 1st scaled modCompRemask. The third RE mask information may refer to the RE mask information of the third area (or the third block) within one section (or one RB). The third RE mask information may be referred to as the 2nd scaled modCompRemask.

[0201] For example, modCompParam 1320 may include modulation compression information. modCompParam 1320 may include first modulation compression information 1321, second modulation compression information 1322, and third modulation compression information 1325 within one section (or one RB, or one RE). The first modulation compression information 1321 of the first area (or the first block) within one section (or one RB) may be referred to as the 0th modCompParam. The second modulation compression information 1322 of the second area (or the second block) within one section (or one RB) may be referred to as the 1st modCompParam. The third modulation compression information 1323 on the third area (or the third block) within one section (or one RB) may be referred to as the 2nd modCompParam.

[0202] Reference Figure 14 , a number of modCompParam 800 and a number of modCompRemask 1200 may be configured as a parameter set. A number of modCompParam 800 and a number of modCompRemask 1200 may be configured as a parameter set 1400. For example, a number of modCompParam 800 and a number of modCompRemask 1200 may be alternately transmitted with Param1400 as a parameter set.

[0203] For example, the parameter set 1400 may include a parameter subset 1410 and a parameter subset 1420. For example, the parameter set 1400 may include first RE mask information, second RE mask information, first modulation compression information, and second modulation compression information within a section. The parameter subset 1410 may include the first RE mask information and the first modulation compression information. The parameter subset 1420 may include the second RE mask information and the second modulation compression information.

[0204] Figure 15 An example of a U-plane message including parameters including RE mask information and modulation compression information according to an embodiment is shown.

[0205] Figure 16 An example of a U-plane message including parameters including RE mask information and modulation compression information according to an embodiment is shown.

[0206] Reference Figure 15 , in the U-plane message 1500, a number of modCompParam and a number of modCompRemask can be configured as a parameter set for each section. For example, the U-plane message 1500 may include a parameter 1510. The parameter 1510 may include first RE mask information 1511 regarding a first region (or first block) within an interval, second RE mask information 1512 regarding a second region (or second block), first modulation compression information 1513 regarding the first region, and second modulation compression information 1514 regarding the second region. The first RE mask information 1511 may be referred to as the 0-scaled modCompRemask. The second RE mask information 1512 may be referred to as the 1-scaled modCompRemask. The first modulation compression information 1513 may be referred to as modCompParam. The second modulation compression information 1514 may be referred to as modCompParam. The previous modCompParam may be the first modulation compression information 1513. The subsequent modCompParam may be the second modulation compression information 1514.

[0207] Reference Figure 16 , in the U-plane message 1600, a number of modCompParam and a number of modCompRemask for each RB can be configured as a parameter set. For example, the U-plane message 1600 may include a parameter 1610. The parameter 1610 may include first RE mask information 1611 regarding a first region within a first RB, second RE mask information 1612 regarding a second region within the first RB, first modulation compression information 1613 regarding the first region, and second modulation compression information 1614 regarding the second region.

[0208] The first RE mask information 1611 of the first region may be referred to as the modCompRemask of the 0th scaling. The second RE mask information 1612 of the second region may be referred to as the modCompRemask of the 1st scaling.

[0209] The first modulation compression information 1613 may be referred to as modCompParam. The second modulation compression information 1614 may be referred to as modCompParam. The previous modCompParam may be the first modulation compression information 1613 regarding the first region. The subsequent modCompParam may be the second modulation compression information 1614 regarding the second region.

[0210] For example, the U-plane message 1600 may include a parameter 1620. The parameter 1620 may include the RE mask information and the modulation compression information for each of the first region and the second region within the second RB.

[0211] According to an embodiment, the parameters 1610 and 1620 may not be included in the U-plane message 1600. Although not shown, according to an embodiment, the modulation compression information may be configured for each RE within the U-plane message.

[0212] Reference Figure 15 and Figure 16 , M-plane parameters may be configured to support the U-plane message 1500 or 1600. A negotiation protocol between the DU and the RU for supporting the U-plane message 1500 or 1600 may be set.

[0213] For example, at least one M-plane parameter for checking whether the DU and the RU support the U-plane message 1500 or 1600 may be configured. A transmission and negotiation protocol for exchanging at least one M-plane parameter between the DU and the RU may be set. The transmission and negotiation protocol for exchanging at least one M-plane parameter may be performed according to Figure 7b operation 751 thereof.

[0214] Figure 15 and Figure 16 show an example of the modCompRemask and the modCompParam being transmitted together, but not limited thereto. The modCompRemask and the modCompParam may also be transmitted alternately.

[0215] According to an embodiment, parameters indicating a format for transmitting modulation compression information may be set according to the above embodiments. For example, modCompMode may be configured to indicate a format for transmitting modulation compression information. According to the value of modCompMode, the format for transmitting modulation compression information may be changed. For example, modCompMode may be set to 8 bits. For example, when the value of modCompMode is set to "0", the format for transmitting modulation compression information may be set to transmit modCompParam for each section. For example, when the value of modCompMode is set to "1", the format for transmitting modulation compression information may be set to transmit modCompParam for each RB. For example, when the value of modCompMode is set to "2", the format for transmitting modulation compression information may be set to transmit modCompParam for each RE. For example, in the value of modCompMode, a value for which the format for transmitting modulation compression information is not set may be set to "reserved".

[0216] Reference may be made to Figure 17 and Figure 18 for examples of configuring modCompMode in the U-plane message.

[0217] Figure 17 FIG. shows an example of a U-plane message including a parameter indicating a format for transmitting modulation compression information according to an embodiment.

[0218] Referring to Figure 17 , modCompMode 1710, as a parameter indicating a format for transmitting modulation compression information, may be included in the common header information 1701 of the U-plane message 1700.

[0219] For example, the value of modCompMode 1710 may be set to "0". Based on the value of modCompMode 1710 being set to "0", modCompParam 1721 and 1722 for each section may be transmitted. modCompParam 1721 may include modulation compression information for the first section. modCompParam 1722 may include modulation compression information for the second section.

[0220] Figure 18 FIG. shows an example of a U-plane message including a parameter indicating a format for transmitting modulation compression information according to an embodiment.

[0221] Referring to Figure 18, the modCompMode 1811 and 1812, as parameters indicating the format for sending modulation compression information, can be included in each section. For example, modCompMode 1811 can be included in the section header information 1801 of the first section of the U-plane message 1800. modCompMode 1812 can be included in the section header information 1802 of the second section of the U-plane message 1800.

[0222] For example, the value of modCompMode 1811 can be set to "0". Based on the value of modCompMode 1811 being set to "0", the modCompParam 1821 including the modulation compression information of the first section can be included in the section header information 1801.

[0223] For example, the value of modCompMode 1812 can be set to "1". Based on the value of modCompMode 1812 being set to "1", the modCompParam 1822 including the modulation compression information of the first PRB in the second section can be included in the first PRB information 1803, and the modCompParam 1823 including the modulation compression information of the second PRB in the second section can be included in the second PRB information 1804.

[0224] Reference Figure 17 and Figure 18 , M-plane parameters can be configured to support the U-plane message 1700 or 1800. The negotiation protocol between the DU and the RU for supporting the U-plane message 1700 or 1800 can be set. According to Figure 7b operation 751, the transmission and negotiation protocol for exchanging at least one M-plane parameter can be executed.

[0225] For example, at least one M-plane parameter for checking whether the DU and the RU support the U-plane message 1700 or 1800 can be configured. The transmission and negotiation protocol for exchanging at least one M-plane parameter can be set between the DU and the RU.

[0226] According to an embodiment, a compression technique for sending modulation compression information through the U-plane message can be defined. The compression technique (e.g., 4-bit "udCompMeth") can be defined as shown in the following table.

[0227] [Table 6]

[0228] Referring to Table 6, when using compression technology based on mod-compr and modulation compression information (i.e., MC information), the value of "udCompMeth" can be set to "0111b". According to an embodiment, when using compression technology based on mod-compr and modulation compression information (i.e., MC information), the value of "udCompMeth" can be set to one of the values set as reserved fields.

[0229] According to an embodiment, mcReMaskMode indicating a method of configuring (or existing) RE mask information within a section can be set. numMcReMask indicating the number of re-masks for each PRB can be set. mcReMaskMode and numMcReMask can be defined as shown in the following table.

[0230] [Table 7]

[0231] Referring to Table 7, mcReMaskMode can be set to 2 bits. When the value of mcReMaskMode is set to "00" (or "00b"), no re-mask can be set. When the value of mcReMaskMode is set to "01" (or "01b"), mcReMask can be set in each section. When the value of mcReMaskMode is set to "10" (or "10b"), mcReMask and an optional re-mask can be set in each RB. When the value of mcReMaskMode is set to "10", an existing selective RE transmission method can be applied. For example, when the sum of the re-masks is not 0xfff, the REs at the positions specified as "0" in the re-mask can be deleted from the U-plane message. For example, numMcReMask can be set to 4 bits.

[0232] According to an embodiment, mcReMaskMode and numMcReMask can be transmitted through an M-plane message. For example, in the static compression mode, mcReMaskMode and numMcReMask can be transmitted through an M-plane message.

[0233] According to an embodiment, in the dynamic compression mode, mcReMaskMode and numMcReMask can be transmitted through the reserved fields of udCompHdr in the section within the U-plane message.

[0234] According to an embodiment, in Table 6, when udCompMeth is set to "0111b", udCompParam may include a plurality of modCompParam corresponding to numMcReMask. Hereinafter, in the dynamic compression mode, an example of configuring modCompParam in the U-plane message according to the value of mcReMaskMode will be described.

[0235] Figure 19 An example of a U-plane message according to an embodiment is shown, which includes a parameter indicating a method of configuring RE mask information in a section and a parameter indicating the number of re-masks for each PRB.

[0236] Figure 20 An example of a U-plane message according to an embodiment is shown, which includes a parameter indicating a method of configuring RE mask information in a section and a parameter indicating the number of re-masks for each PRB.

[0237] Figure 21 An example of a U-plane message according to an embodiment is shown, which includes a parameter indicating a method of configuring RE mask information in a section and a parameter indicating the number of re-masks for each PRB.

[0238] Reference Figure 19 , Region 1900 may be part of the U-plane message. Region 1900 may include section header information 1910 and PRB information 1920. The section header information 1910 may include mcReMaskMode and numMcReMask. mcReMaskJode is a parameter indicating a method of configuring RE mask information within a section, and numMcReMask is a parameter indicating the number of re-masks for a PRB.

[0239] For example, the value of mcReMaskMode may be set to "0" (or "00b"). The value of numMcReMask may be set to "1". Based on the value of mcReMaskMode being set to "0", the value of numMcReMask may be set to "1". For example, when the value of mcReMaskMode is set to "0" (or "00b"), the value of numMcReMask may always be set to "1".

[0240] For example, when the value of mcReMaskMode is set to "0" and the value of numMcReMask is set to "1", udCompParam (or modCompParam) including modulation compression information of the PRB may be included in the PRB information 1920.

[0241] Reference Figure 20, Region 2000 can be part of a U-plane message. Region 2000 can include section header information 2010 and PRB information 2020. The section header information 2010 can include mcReMaskMode and numMcReMask. mcReMaskMode is a parameter indicating the method of configuring RE mask information within a section, and numMcReMask is a parameter indicating the number of re-masks in a PRB.

[0242] For example, the value of mcReMaskMode can be set to "1" (or "01b"). The value of numMcReMask can be set to "2". Based on the value of mcReMaskMode being set to "1", the value of numMcReMask can be set to "2".

[0243] For example, when the value of mcReMaskMode is set to "1" (or "01b") and the value of numMcReMask is set to "2", modCompRemask can be included in the section header information 2010. When the value of mcReMaskMode is set to "1" and the value of numMcReMask is set to "2", udCompParam2030 including the modulation compression information of the PRB can be included in the PRB information 2020. udCompParam 2030 can include a plurality (e.g., two) of modCompParam corresponding to the value of numMcReMask.

[0244] Reference Figure 21 , Region 2100 can be part of a U-plane message. Region 2100 can include section header information 2110 and PRB information 2120. The section header information 2110 can include mcReMaskMode and numMcReMask. mcReMaskJode is a parameter indicating the method of configuring RE mask information within a section, and numMcReMask is a parameter indicating the number of re-masks in a PRB.

[0245] For example, the value of mcReMaskMode can be set to "2" (or "10b"). The value of numMcReMask can be set to "2". Based on the value of mcReMaskMode being set to "2", the value of numMcReMask can be set to "2".

[0246] For example, when the value of mcReMaskMode is set to "2" (or "10b") and the value of numMcReMask is set to "2", udCompParam 2130 can be included in the PRB information 2120. udCompParam 2130 can include modCompRemask and modCompParam.

[0247] Reference Figures 19 to 21 , the M-plane parameters for supporting regions 1900, 2000, or 2100 as part of the U-plane message can be configured. The negotiation protocol between the DU and the RU for supporting the U-plane message including the above regions 1900, 2000, or 2100 can be set. The transmission and negotiation protocol for exchanging at least one M-plane parameter can be performed according to Figure 7b operation 751.

[0248] For example, it can be configured to check whether the DU and the RU support at least one M-plane parameter of the U-plane message including the above regions 1900, 2000, or 2100. The transmission and negotiation protocol for exchanging at least one M-plane parameter between the DU and the RU can be established.

[0249] Figure 22 is a flowchart showing the operations of the DU according to an embodiment.

[0250] Reference Figure 22 , in operation 2210, the DU (e.g., Figure 7a and Figure 7b DU 710) (or the processor of the DU) can generate a user plane (U-plane) message. For example, after the control plane (C-plane) message including control information is sent, the DU can generate a U-plane message, which is configured with modulation compression information and sections and includes modulated and compressed data.

[0251] For example, the DU can exchange management plane (M-plane) messages with the RU (e.g., Figure 7a and Figure 7b RU 720). The DU can exchange M-plane messages with the RU to check whether the specified format of the U-plane message is supported in the RU. For example, the DU can send an M-plane message including the format information of the U-plane message to the RU before sending the C-plane message.

[0252] The DU can configure at least one M-plane parameter to check whether the RU supports the specified format of the U-plane message. Based on the transmission protocol and negotiation protocol for exchanging at least one M-plane parameter, the DU can identify that the RU supports the specified format of the U-plane message.

[0253] For example, the DU may send a C-plane message to the RU. The C-plane message may include section information. In an embodiment of the present disclosure, since modulation compression information is included in the U-plane message, the C-plane message may not include section extension information for modulation compression. For example, the C-plane message may not include section extension 4. Additionally, as an example, the C-plane message may not include section extension 5.

[0254] For example, the U-plane message may include modulation compression information and modulated and compressed data. The modulated and compressed data may be configured in units of sections. The DU may modulate and compress the data based on modulation compression techniques. According to an embodiment, the U-plane message may include at least one section. Based on the U-plane message being configured to have at least one section, per-region modulation compression information may be configured within each of the at least one section or within one section. The modulation compression information may include a flag (e.g., "csf") for indicating whether the constellation moves and scaling information (e.g., "modCompScaler") for indicating a scaler value.

[0255] According to an embodiment, the U-plane message may include section header information of the section. The section header information may include modulation compression information. The modulation compression information may be included within the section header information.

[0256] According to an embodiment, the U-plane message may include PRB information configured based on sections. The PRB information may include modulation compression information. For example, the modulation compression information may include a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

[0257] According to an embodiment, the U-plane message may include RE mask information of at least one region set within the section. For example, the section may be divided into at least one region based on the RE mask information. The modulation compression information may include a flag for each of the at least one region and scaling information for each of the at least one region.

[0258] According to an embodiment, the U-plane message may include section header information of the section and PRB information configured based on sections. The section header information may include information for indicating a specified format in which RE mask information for setting at least one region within the section is configured within the U-plane. Based on the specified format, the RE mask information for at least one region may be included within the U-plane. For example, the RE mask information may be included in one of the section header information and the PRB information. For example, based on a first format, the RE mask information may be included in the section header information. Based on a second format, the RE mask information may be included in the PRB information.

[0259] In operation 2220, the DU may send a U-plane message to the RU via the fronthaul interface. For example, the DU may send a U-plane message configured according to the above embodiments to the RU. For example, the DU may send a U-plane message including modulation compression information and modulated and compressed data to the RU.

[0260] Figure 23 is a flowchart showing the operation of the RU according to an embodiment.

[0261] Refer to Figure 23 , in operation 2310, the RU (e.g., Figure 7a and Figure 7b the RU 720 of) (or the processor of the RU) may receive a user plane (U-plane) message from the DU (e.g., Figure 7a and Figure 7b the DU 710 of).

[0262] The RU may exchange M-plane messages with the DU to check whether a specified format of the U-plane message is supported in the DU. For example, before receiving a control plane (C-plane) message, the RU may receive a management plane (M-plane) message including format information of the U-plane message from the DU.

[0263] The RU may identify that the DU supports the specified format of the U-plane information based on the transport protocol and negotiation protocol for exchanging at least one M-plane parameter to check whether the specified format of the U-plane message is supported.

[0264] For example, the RU may receive a control plane (C-plane) message from the DU. The C-plane message may include section information. In an embodiment of the present disclosure, since the modulation compression information is included in the U-plane message, the C-plane message may not include section extension information for modulation compression. For example, the C-plane message may not include section extension 4. Additionally, as an example, the C-plane message may not include section extension 5.

[0265] In operation 2320, the RU may identify the modulation compression information and the modulated and compressed data included in the received U-plane message. For example, the RU may identify the modulation compression information and the modulated and compressed data based on the U-plane message received from the DU.

[0266] For example, a U-plane message may include modulation compression information and modulated and compressed data. The modulated and compressed data may be configured in units of segments. The DU may modulate and compress the data based on modulation compression techniques. According to an embodiment, the U-plane message may include at least one segment. Based on the U-plane message being configured with at least one segment, per-region modulation compression information may be configured within each of the at least one segment or within one segment. The modulation compression information may include a flag (e.g., "csf") for indicating whether a constellation moves and scaling information (e.g., "modCompScaler") for indicating a scaler value.

[0267] According to an embodiment, the U-plane message may include segment header information of a segment. The segment header information may include modulation compression information. The modulation compression information may be included within the segment header information.

[0268] According to an embodiment, the U-plane message may include PRB information configured based on a segment. The PRB information may include modulation compression information. For example, the modulation compression information may include a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

[0269] According to an embodiment, the U-plane message may include RE mask information for at least one region set within a segment. For example, the segment may be divided into at least one region based on the RE mask information. The modulation compression information may include a flag for each of the at least one region and scaling information for each of the at least one region.

[0270] According to an embodiment, the U-plane message may include segment header information of a segment and PRB information configured based on the segment. The segment header information may include information for indicating a specified format in which RE mask information for at least one region set within the segment is configured within the U-plane. Based on the specified format, the RE mask information for at least one region may be included within the U-plane. For example, the RE mask information may be included in one of the segment header information and the PRB information. For example, based on a first format, the RE mask information may be included in the segment header information. Based on a second format, the RE mask information may be included in the PRB information.

[0271] According to an embodiment, a method performed by a distributed unit (DU) may include, after transmitting a control plane (C-plane) message including control information, generating a user plane (U-plane) message including modulation compression information and modulated and compressed data configured as segments. The method may include transmitting the U-plane message to a radio unit (RU) via a fronthaul interface. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

[0272] According to an embodiment, the U-plane message may include section header information of a section. The section header information may include modulation compression information.

[0273] According to an embodiment, the U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information. The modulation compression information may include a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

[0274] According to an embodiment, the U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information. The modulation compression information may include a flag for each of a plurality of resource elements (REs) and scaling information for each of the plurality of REs.

[0275] According to an embodiment, the U-plane message may include resource element (RE) mask information for at least one area set within a section. The modulation compression information may include a flag for each of the at least one area and scaling information for each of the at least one area.

[0276] According to an embodiment, the U-plane message may include section header information of a section and physical resource block (PRB) information configured based on the section. The section header information may include information indicating a specified format, and the specified format is resource element (RE) mask information for at least one area set within a section configured within the U-plane. The RE mask information may include one of the section header information and the PRB information.

[0277] According to an embodiment, the method may include sending, via a fronthaul interface, a management plane (M-plane) message including format information of the U-plane message to the RU.

[0278] According to an embodiment, a method performed by a radio unit (RU) may include, after receiving a control plane (C-plane) message including control information, receiving, via a fronthaul interface, a user plane (U-plane) message including modulation compression information and modulated and compressed data configured as a section from a distributed unit (DU). The method may include identifying the modulation compression information and the modulated and compressed data based on the U-plane message. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

[0279] According to an embodiment, the U-plane message may include section header information of a section. The section header information may include modulation compression information.

[0280] According to an embodiment, the U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information. The modulation compression information may include a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

[0281] According to an embodiment, the U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information. The modulation compression information may include a flag for each of a plurality of resource elements (REs) and scaling information for each of the plurality of REs.

[0282] According to an embodiment, the U-plane message may further include resource element (RE) mask information for at least one area set within a section. The modulation compression information may include a flag for each of the at least one area and scaling information for each of the at least one type of area.

[0283] According to an embodiment, the U-plane message may include section header information of a section and physical resource block (PRB) information configured based on the section. The section header information may include information indicating a specified format, and the specified format is resource element (RE) mask information for at least one area set within a section configured within the U-plane. The RE mask information may include one of the section header information and the PRB information.

[0284] According to an embodiment, the method may include receiving, through a fronthaul interface, a management plane (M-plane) message including format information of a U-plane message from a radio unit (RU).

[0285] According to an embodiment, an electronic device executed by a distributed unit (DU) may include at least one transceiver including a fronthaul transceiver, and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to generate a user plane (U-plane) message including modulation compression information and modulated and compressed data configured as a section after transmitting a control plane (C-plane) message including control information. The at least one processor may be configured to transmit the U-plane message to a radio unit (RU) through a fronthaul interface. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

[0286] According to an embodiment, the U-plane message may include section header information of a section. The section header information may include modulation compression information.

[0287] According to an embodiment, the U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information. The modulation compression information may include a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

[0288] According to an embodiment, the U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information. The modulation compression information may include a flag for each of a plurality of resource elements (REs) and scaling information for each of the plurality of REs.

[0289] According to an embodiment, the U-plane message may further include resource element (RE) mask information for at least one area provided within a section. The modulation compression information may include a flag for each of the at least one area and scaling information for each of the at least one type of area.

[0290] According to an embodiment, the U-plane message may include section header information of a section and physical resource block (PRB) information configured based on the section. The section header information may include information indicating a specified format, and the specified format is resource element (RE) mask information for at least one area provided within a section configured within the U-plane. The RE mask information may include one of the section header information and the PRB information.

[0291] According to an embodiment, at least one processor may be configured to send a management plane (M-plane) message including format information of the U-plane message to an RU via a fronthaul interface.

[0292] According to an embodiment, an electronic device executed by a radio unit (RU) may include at least one transceiver and at least one processor coupled to the transceiver, and the at least one transceiver includes a fronthaul transceiver. The at least one processor may be configured to, after receiving a control plane (C-plane) message including control information, receive a user plane (U-plane) message including modulation compression information and modulated and compressed data configured as a section from a distributed unit (DU) via the fronthaul interface. The at least one processor may be configured to identify the modulation compression information and the modulated and compressed data based on the U-plane message. The modulation compression information may include a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

[0293] According to an embodiment, the U-plane message may include section header information of the section. The section header information may include modulation compression information.

[0294] According to an embodiment, a U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information, and the modulation compression information may include a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

[0295] According to an embodiment, a U-plane message may include physical resource block (PRB) information configured based on a section. The PRB information may include modulation compression information. The modulation compression information may include a flag for each of a plurality of resource elements (REs) and scaling information for each of the plurality of REs.

[0296] According to an embodiment, the U-plane message may further include resource element (RE) mask information for at least one area set within a section. The modulation compression information may include a flag for each of the at least one area and scaling information for each of the at least one type of area.

[0297] According to an embodiment, a U-plane message may include section header information of a section and physical resource block (PRB) information configured based on the section. The section header information may include information indicating a specified format, and the specified format is resource element (RE) mask information for at least one area set within a section configured within the U-plane. The RE mask information may include one of the section header information and the PRB information.

[0298] According to an embodiment, at least one processor may be configured to receive, via a fronthaul interface, a management plane (M-plane) message including format information of a U-plane message from a radio unit (RU).

[0299] According to an embodiment, a non-transitory computer-readable storage medium may include a memory storing a program including instructions. When executed by a processor, the instructions may cause a distributed unit (DU) to execute one of the above methods executed by the DU, or cause a radio unit (RU) to execute one of the above methods executed by the RU.

[0300] According to the above embodiments, modulation compression information can be sent via U-plane messages. When modulation compression is used, since the modulation compression information is sent via U-plane messages, the number of sections set in the U-plane messages can be reduced. When modulation compression is used, since the modulation compression information is sent via U-plane messages, the number of sections set in the U-plane messages can be set to be similar to the number of sections set according to a compression technique different from modulation compression. Since the modulation compression information is sent via U-plane messages, there is no need to configure additional sections in the U-plane messages. Since the modulation compression information is sent via U-plane messages, the DU does not need to configure section extensions for additional modulation compression. The DU can reduce the resources for processing U-plane messages based on sending the modulation compression information via U-plane messages.

[0301] According to the above embodiments, when a compression technique different from modulation compression is used in a dynamic manner, segmentation may not occur. Therefore, the scheduling operation for configuring sections can be simplified. When the modulation compression of the U-plane is released, the RU may not refer to the information of the C-plane. Therefore, according to the above embodiments, the resources for storing the C-plane information in the RU can be saved, and the matching process between the C-plane information and the U-plane data can be omitted.

[0302] The method according to the embodiments described in the claims or the specification of the present disclosure can be implemented in the form of hardware, software, or a combination of hardware and software.

[0303] In the case of being implemented as software, a computer-readable storage medium for storing one or more programs (software modules) can be provided. One or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. One or more programs include instructions for causing the electronic device to execute the method according to the embodiments described in the claims or the specification of the present disclosure.

[0304] Such a program (software module, software) can be stored in a random access memory, a non-volatile memory including a flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage device, a CD-ROM, an optical storage device (such as a digital versatile disc (DVD) or other formats), or a magnetic tape. Alternatively, it can be stored in a memory configured with a combination of some or all of them. In addition, multiple configured memories can be included.

[0305] In addition, the program can be stored in a connectable storage device, which can be accessed through a communication network, such as the Internet, intranet, local area network (LAN), wide area network (WAN), or storage area network (SAN), or a combination thereof. Such a storage device can be connected to the device implementing the embodiments of the present disclosure through an external port. In addition, a separate storage device on the communication network can also be connected to the device implementing the embodiments of the present disclosure.

[0306] In the above specific embodiments of the present disclosure, according to the presented specific embodiments, the components included in the present disclosure are represented in singular or plural. However, for ease of description, the singular or plural expression is appropriately selected according to the presented situation, and the present disclosure is not limited to singular or plural components. Even components represented in plural can be configured as singular, or components represented in singular can be configured as plural.

[0307] Meanwhile, specific embodiments have been described in the detailed description of the present disclosure. Of course, various modifications can be made without departing from the scope of the present disclosure.

Claims

1. A method performed by a distributed unit DU, the method comprising: After sending a control plane C plane message including control information, generating a user plane U plane message including modulation compression information and modulated and compressed data configured as a section, and Sending the U plane message to a radio unit RU via a fronthaul interface, Wherein the modulation compression information includes a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

2. The method according to claim 1, wherein, The U plane message further includes section header information of the section, and Wherein the section header information includes the modulation compression information.

3. The method according to any one of claims 1 to 2, wherein The U plane message further includes physical resource block PRB information configured based on the section, Wherein the PRB information includes the modulation compression information, and Wherein the modulation compression information includes a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

4. The method according to any one of claims 1 to 3, wherein, The U plane message further includes physical resource block PRB information configured based on the section, Wherein the PRB information includes the modulation compression information, and Wherein the modulation compression information includes a flag for each of a plurality of resource elements RE and scaling information for each of the plurality of RE.

5. The method according to any one of claims 1 to 4, wherein The U plane message further includes resource element RE mask information for at least one area set within the section, and Wherein the modulation compression information includes a flag for each of the at least one area and scaling information for each of the at least one area.

6. The method according to any one of claims 1 to 5, wherein The U plane message further includes section header information of the section and physical resource block PRB information configured based on the section, and Wherein the section header information includes information indicating a specified format for configuring resource element RE mask information for at least one area set within the section within the U plane, and Wherein the RE mask information includes one of the section header information and the PRB information.

7. The method according to any one of claims 1 to 6, the method further comprising: Sending a management plane M plane message including format information of the U plane message to the RU via the fronthaul interface.

8. A method performed by a radio unit RU, the method comprising: After receiving a control plane C plane message including control information, receiving, via a fronthaul interface, from a distributed unit DU a user plane U plane message including modulation compression information and modulated and compressed data configured as a section, and Identifying the modulation compression information and the modulated and compressed data based on the U plane message, Wherein the modulation compression information includes a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

9. The method according to claim 8, wherein The U plane message further includes section header information of the section, and Wherein the section header information includes the modulation compression information.

10. The method according to any one of claims 8 to 9, wherein, The U plane message further includes physical resource block PRB information configured based on the section, Wherein, the PRB information includes the modulation compression information, and wherein, the modulation compression information includes a flag for each of at least one PRB included in the PRB information and scaling information for each of the at least one PRB.

11. An electronic device executed by a distributed unit DU, comprising: at least one transceiver, the at least one transceiver including a fronthaul transceiver; at least one processor, the at least one processor being coupled to the at least one transceiver, wherein, the at least one processor is configured to: after sending a control plane C-plane message including control information, generate a user plane U-plane message including modulation compression information and modulated and compressed data configured as segments, and send the U-plane message to a radio unit RU through a fronthaul interface, wherein, the modulation compression information includes a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

12. The electronic device according to claim 11, wherein, The at least one processor is configured to perform any one of the methods recited in claims 2 to 7.

13. An electronic device executed by a radio unit RU, the electronic device comprising: at least one transceiver, the at least one transceiver including a fronthaul transceiver; at least one processor, the at least one processor being coupled to the at least one transceiver, wherein, the at least one processor is configured to: after receiving a control plane C-plane message including control information, receive, through a fronthaul interface, from a distributed unit DU a user plane U-plane message including modulation compression information and modulated and compressed data configured as segments, and identify the modulation compression information and the modulated and compressed data based on the U-plane message, wherein, the modulation compression information includes a flag for indicating whether a constellation moves and scaling information for indicating a scaler value.

14. The electronic device according to claim 13, wherein, The at least one processor is configured to perform any one of the methods recited in claims 9 or 10.

15. A non-transitory computer-readable storage medium including a memory storing a program, the program including instructions, wherein, When executed by a processor, the instructions cause the distributed unit DU to perform any one of the methods of claims 1 to 7, or cause the radio unit RU to perform any one of the methods of claims 8 to 10.

Images