Electronic device and method for indicating unscheduled layer in fronthaul interface

Abstract

In an embodiment, an electronic device of a radio unit (RU) may include: at least one fronthaul transceiver; at least one radio frequency (RF) transceiver; and at least one processor coupled to the at least one fronthaul transceiver and the at least one RF transceiver. The at least one processor may be configured to: receive a control plane (C-plane) message from a distributed unit (DU) over a fronthaul interface, the C-plane message including information about a resource region and user equipment (UE) identification information corresponding to a value for indicating non-scheduling; calculating a beamforming weight based on the C-plane message; and performing beamforming based on the beamforming weight.

Description

Technical Field

[0001] The present disclosure relates to a fronthaul interface and more particularly to an electronic device and method for indicating a non-scheduled layer in a fronthaul interface. Background Art

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

[0003] The above information may be provided as related art to assist in understanding the present disclosure. No statement or determination is made as to whether any of the above information might be applicable as prior art related to the present disclosure. Summary of the invention

[0004] Technical Solution

[0005] In an embodiment, an electronic device of a radio unit (RU) is provided. The electronic device may include at least one fronthaul transceiver, at least one radio frequency (RF) transceiver, and at least one processor coupled to at least one fronthaul transceiver and at least one RF transceiver. The at least one processor may be configured to receive a control plane (C-plane) message from a distributed unit (DU) via a fronthaul interface, the C-plane message including information about a resource region and user equipment (UE) identification information corresponding to a non-scheduled value for indicating a layer. The at least one processor may be configured to calculate beamforming weights based on the C-plane message. The at least one processor may be configured to perform beamforming based on the beamforming weights.

[0006] In an embodiment, an electronic device of a distributed unit (DU) is provided. The electronic device may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to: identify non-scheduling for a layer in a resource region. The at least one processor may be configured to generate a control plane (C-plane) message, the C-plane message including information about the resource region and user equipment (UE) identification information corresponding to a value for indicating non-scheduling of the layer. The at least one processor may be configured to send the generated C-plane message to a radio unit (RU). The C-plane message may be associated with a beamforming weight in the RU.

[0007] In an embodiment, a method performed by a radio unit (RU) is provided. The method may include receiving a control plane (C-plane) message from a distributed unit (DU) via a fronthaul interface, the C-plane message including information about a resource region and user equipment (UE) identification information corresponding to a non-scheduled value for indicating a layer. The method may include calculating beamforming weights based on the C-plane message. The method may include performing beamforming based on the beamforming weights.

[0008] In an embodiment, a method performed by a distributed unit (DU) is provided. The method may include: identifying non-scheduling for a layer in a resource region. The method may include generating a control plane (C-plane) message, the C-plane message including information about the resource region and user equipment (UE) identification information corresponding to a value for indicating non-scheduling of the layer. The method may include sending the generated C-plane message to a radio unit (RU). The C-plane message may be associated with a beamforming weight in the RU.

[0009] In an embodiment, a method performed by a radio unit (RU) is provided. The method may include receiving a control plane (C-plane) message from a distributed unit (DU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about a resource region described by the segment and UE identification information. The segment extension information may include information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The method may include identifying that the resource region is not allocated for the designated port based on the UE identification information of the designated port set to 0x7FFF in the C-plane message.

[0010] In an embodiment, a method performed by a distributed unit (DU) is provided. The method may include setting the UE identification information of a designated port that is not scheduled to 0x7FFF. The method may include sending a control plane (C-plane) message to a radio unit (RU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about the resource area described by the segment and UE identification information. The segment extension information may include information about the beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The UE identification information of the designated port in the C-plane message may indicate that the resource area is not allocated for the designated port.

[0011] In an embodiment, an electronic device of a radio unit (RU) is provided. The electronic device may include: a memory including instructions; at least one transceiver, the at least one transceiver being configured to send or receive signals on a fronthaul interface; and at least one processor. The instructions, when executed by the at least one processor, may cause the RU to receive a control plane (C-plane) message from a distributed unit (DU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about a resource region described by a segment and UE identification information. The segment extension information may include information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The instructions may cause the RU, when executed by the at least one processor, to identify that the resource region is not allocated for the designated port based on the UE identification information of the designated port set to 0x7FFF in the C-plane message.

[0012] In an embodiment, an electronic device of a distributed unit (DU) is provided. The electronic device may include: a memory including instructions; at least one transceiver, the at least one transceiver being configured to send a signal or receive a signal on a fronthaul interface; and at least one processor. When the instructions are executed by the at least one processor, the DU may set the UE identification information of the unscheduled designated port to 0x7FFF. When the instructions are executed by the at least one processor, the DU may send a control plane (C-plane) message to a radio unit (RU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about a resource region described by a segment and UE identification information, and the segment extension information may include information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The UE identification information of the designated port in the C-plane message may indicate that the resource region is not allocated for the designated port.

[0013] In an embodiment, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium may include a memory storing a program including instructions. The instructions, when executed by a processor of a radio unit (RU), may cause the RU to: receive a control plane (C-plane) message from a distributed unit (DU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information; and identify that the resource region is not allocated for the designated port based on the UE identification information of the designated port set to 0x7FFF in the C-plane message. The segment information may include information about the resource region described by the segment and UE identification information. The segment extension information may include information about the beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port.

[0014] In an embodiment, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium may include a memory storing a program including instructions. The instructions, when executed by a processor of a distributed unit (DU), may cause the DU to: set the UE identification information of a designated port that is not scheduled to 0x7FFF, and send a control plane (C-plane) message to a radio unit (RU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about a resource area described by a segment and UE identification information. The segment extension information may include information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The UE identification information of the designated port in the C-plane message may indicate that the resource area is not allocated for the designated port. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 2a A fronthaul interface according to an embodiment is shown.

[0017] Figure 2b A fronthaul interface of an open (O) radio access network (RAN) according to an embodiment is shown.

[0018] Figure 3a Components of a distributed unit (DU) according to an embodiment are shown.

[0019] Figure 3b Components of a radio unit (RU) according to an embodiment are shown.

[0020] Figure 4 An example of functional division between DU and RU according to an embodiment is shown.

[0021] Figure 5a An example of a downlink (DL) message according to an embodiment is shown.

[0022] Figure 5b An example of an uplink (UL) message according to an embodiment is shown.

[0023] Figure 6 An example of resource allocation for each layer according to an embodiment is shown.

[0024] Figure 7a and Figure 7b An example of beamforming using indication of a non-scheduled layer according to an embodiment is shown.

[0025] Figure 8 An example of beamforming weights for each resource zone according to an embodiment is shown.

[0026] Fig. 9 A functional configuration of a DU and a functional configuration of an RU for beamforming using an indication of a non-scheduled layer according to an embodiment are shown.

[0027] Fig.10 An operation flow for indicating a DU of a non-scheduled layer according to an embodiment is shown.

[0028] Fig.11 An operation flow for indicating an RU of a non-scheduled layer according to an embodiment is shown.

[0029] Fig.12a and Figure 12b An example of a C-plane message for indicating a non-scheduled layer according to an embodiment is shown. Specific embodiments

[0030] The terms used in the present disclosure are only used to describe specific embodiments, and may not be intended to limit the scope of another embodiment. Singular expressions may include plural expressions, unless there are clear different meanings in the context. The terms used herein (including technical or scientific terms) may have the same meanings as those generally understood by those of ordinary skill in the art described in the present disclosure. The terms defined in the general dictionary of the terms used in the present disclosure may be interpreted with the same or similar meanings as the contextual meanings of the relevant technology, and unless clearly defined in the present disclosure, should not be interpreted with ideal or overly formal meanings. In some cases, even the terms defined in the present disclosure cannot be interpreted as excluding embodiments of the present disclosure.

[0031] In various embodiments of the present disclosure described below, a hardware method is described as an example. However, since various embodiments of the present disclosure include techniques using both hardware and software, various embodiments of the present disclosure do not exclude software-based methods.

[0032] For the convenience of description, the terms used in the following description 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 for operation 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 (distributed unit (DU), radio unit (RU), central unit (CU), control plane (CU-CP), user plane (CU-UP), open radio access network (O-RAN) DU (O-DU), O-RAN RU (O-RU), O-RAN CU (O-CU), O-RAN CU-CP (O-CU-UP), O-RAN CU-CP (O-CU-CP)), terms referring to components of devices, etc. are exemplified. Therefore, the present disclosure is not limited to the terms described below, and another term having an equivalent technical meaning may be used. In addition, terms such as “unit”, “member”, “material”, “body”, etc. used below may indicate at least one shape structure, or may indicate a unit of a processing function.

[0033] In addition, in the present disclosure, in order to determine whether a specific condition is met or achieved, the expression greater than or less than may be used, but this is only a description for expressing an example and does not exclude the description of greater than or equal to or less than or equal to. The condition described as "greater than or equal to" may be replaced by "greater than", the condition described as "less than or equal to" may be replaced by "less than", and the 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 of the elements from A (including A) to B (including B).

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

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

[0036] refer to Figure 1 , the wireless communication system includes a base station 110 and a terminal 120 as a part of a node using a wireless channel. 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 .

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

[0038] The terminal 120 is a device used by a user, which communicates with the base station 110 through a wireless channel. The link from the base station 110 to the terminal 120 is called a downlink (DL), and the link from the terminal 120 to the base station 110 is called an uplink (UL). Figure 1 Not shown, but the terminal 120 and other terminals can communicate with each other through a wireless channel. In this context, the link between the terminal 120 and other terminals (device to device, D2D) is called a side link, which can be mixed with the PC5 interface. In some other embodiments, the terminal 120 can operate without any participation of the user. According to an embodiment of the present disclosure, the terminal 120 may be a device that performs machine type communication (MTC) and may not be carried by the user. According to another embodiment, the terminal 120 may be a narrowband (NB) Internet of Things (IoT) device.

[0039] Terminal 120 may be referred to as “user equipment (UE)”, “customer premises equipment (CPE)”, “mobile station”, “user station”, “remote terminal”, “wireless terminal”, “electronic device”, “user device” or any other term with the same or equivalent technical meaning.

[0040] The base station 110 may perform beamforming with the terminal 120. The base station 110 and the terminal 120 may send and receive wireless signals in a relatively low frequency band, for example, FR1 (frequency range 1) of NR. In addition, the base station 110 and the terminal 120 may send and receive wireless signals in a relatively high frequency band, for example, FR2 (or FR2-1, FR2-2, FR2-3) of NR, FR3 of NR, or a millimeter wave (mmWave) band (for example, 28 GHz, 30 GHz, 38 GHz, 60 GHz) of NR. In order to enhance the channel gain, the base station 110 and the terminal 120 may perform beamforming. In this context, beamforming may include transmit beamforming and receive beamforming. The base station 110 and the terminal 120 may assign directivity to a transmit signal or a receive signal. To this end, the base station 110 and the terminal 120 may select a service beam through a beam search or a beam management process. After selecting the service beam, subsequent communication may be performed through a resource having a QCL relationship with a resource to which the service beam has been transmitted.

[0041] The first antenna port and the second antenna port may be evaluated as having such a QCL relationship if a large-scale characteristic of a channel carrying symbols on the first antenna port can be inferred from a channel carrying symbols on the second antenna port. For example, the large-scale characteristic may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, or spatial receiver parameters.

[0042] although Figure 1 It is described that both the base station 110 and the terminal 120 perform beamforming, but the embodiments of the present disclosure are not limited thereto. In some embodiments, the terminal may or may not perform beamforming. Similarly, the base station may or may not perform beamforming. That is, only one of the base station and the terminal may perform beamforming, or both the base station and the terminal may not perform beamforming.

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

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

[0045] Figure 2a The fronthaul interface according to an embodiment of the present disclosure is shown. The fronthaul refers to the physical link between the wireless LAN and the base station, rather than the backhaul of the link between the base station and the core network. Figure 2a An example of a forward transport structure between a DU 210 and one RU 220 is shown, but it is only for ease of description, and the present disclosure is not limited thereto. That is, the embodiments of the present disclosure may also be applied to a forward transport structure between one DU and multiple RUs. For example, the embodiments of the present disclosure may be applied to a forward transport structure between one DU and two RUs. In addition, the embodiments of the present disclosure may also be applied to a forward transport structure between one DU and three RUs.

[0046] refer to Figure 2a , the base station 110 may include a DU 210 and a RU 220. The fronthaul 215 between the DU 210 and the RU 220 may be performed via the F x Interface Operation. For the operation of the fronthaul 215, an interface such as, for example, enhanced Common Public Radio Interface (eCPRI) or Radio over Ethernet (ROE) may be used.

[0047] With the further development of communication technology, mobile data traffic has increased significantly, and therefore, the bandwidth requirements required for the fronthaul between the digital unit and the wireless unit have also increased significantly. In deployments such as centralized / cloud radio access networks (C-RAN), the DU may be implemented to perform functions for packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and physical (PHY), and the RU may be implemented to perform functions of the PHY layer in addition to radio frequency (RF) functions.

[0048] DU 210 may be used as an upper layer function of a wireless network. For example, DU 210 may perform the functions of a portion of a MAC layer and / or a PHY layer. The portion of the PHY layer performed at a higher level of the functions of the PHY layer may include channel coding (or channel decoding), scrambling (or descrambling), modulation (or demodulation), or layer mapping (or layer demapping). In the case where DU 210 complies with the O-RAN standard, DU 210 may be referred to as O-DU (O-RAN DU). In an embodiment of the present disclosure, DU 210 may be represented as being replaced by a first network entity of a base station (e.g., gNB) in a required scenario.

[0049] The RU 220 may serve as a lower layer of the functions of the wireless network. For example, the RU 220 may perform a portion of the PHY layer and / or the RF functions. The portion of the PHY layer that is performed at a relatively lower level than the DU 210 in the functions of the PHY layer may include, for example, iFFT transformation (or FFT transformation), CP insertion (CP removal), and digital beamforming. Figure 4 An example of this specific functional split is described in more detail. RU 220 may be referred to as an "access unit (AU)", "access point (AP)", "transmit / receive point (TRP)", "remote radio head (RRH)", "radio unit (RU)" or any other term having a technically equivalent meaning thereto. In the case where RU 220 complies with the O-RAN standard, RU 220 may be referred to as an O-RU (O-RANRU). In an embodiment of the present disclosure, RU 220 may be represented as being replaced by a second network entity of a base station (e.g., gNB) where necessary.

[0050] although Figure 2a The base station 110 is shown to include a DU 210 and a RU 220, but the embodiments of the present disclosure are not limited thereto. The base station can implement distributed deployment according to a centralized unit (CU) configured to perform upper layer functions of the access network (e.g., packet data convergence protocol (PDCP), radio resource control (RRC), etc.) and a distributed unit (DU) configured to perform lower layer functions. In this context, the distributed unit (DU) may include Figure 1 The digital unit (DU) and the radio unit (RU) of the 5G core (5GC) and the next generation core (NGC) network. Between the core network (e.g., 5G core (5GC) or next generation core (NGC) network) and the radio access network (RAN), the base station can be implemented with a deployment arranged in the order of CU, DU, and RU. The interface between the CU and the distributed unit (DU) can be referred to as the F1 interface.

[0051] A centralized unit (CU) may be connected to one or more DUs to act as upper layer functions in addition to the DU. For example, the CU may act as the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, and the DU and RU may act as lower layer functions. The DU may perform some functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers (high PHY), and the RU may be responsible for the remaining functions of the PHY layer (low PHY). Depending on the implementation of the distributed deployment of the base station, the digital unit (DU) may be included in the distributed unit (DU). In the following, unless otherwise defined, the operation of the digital unit (DU) and the RU will be described, but it should be noted that the various embodiments of the present disclosure may be applied to the deployment of a base station including a CU or a deployment in which the DU is directly connected to the core network (i.e., implemented as incorporated into a base station (e.g., an NG-RAN node), where the CU and the DU constitute one entity).

[0052] Figure 2b A fronthaul interface of an open radio access network (O-RAN) according to an embodiment of the present disclosure is shown, wherein an eNB or a gNB is shown as a base station 110 according to a distributed deployment.

[0053] refer to Figure 2b , the base station 110 may include an O-DU 251 and O-RUs (253-1, . . . , 253-n). Hereinafter, for ease of explanation, the operation and function of the O-RU 253-1 may be understood by explaining each of the other O-RUs (e.g., O-RU 253-n).

[0054] The O-DU 251 is composed of the following components except for Figure 4The O-DU 251 is a logical node for functions other than those specifically assigned to the O-RU 253-1 in the functions of a base station (e.g., eNB, gNB). The O-DU 251 may control the operation of the O-RU (253-1, . . . , 253-n). The O-DU 251 may be referred to as a lower layer segmentation (LLS) central unit (CU). The O-RU 253-1 is a block diagram including a plurality of blocks of the O-RU 253-1 and a plurality of blocks of the O-RU 253-1. Figure 4 A logical node that is a subset of the functionality of a base station (e.g., eNB, gNB). The real-time aspects of control plane (C-plane) communication and user plane (U-plane) communication with O-RU253-1 can be controlled by O-DU 251.

[0055] The O-DU 251 can communicate with the O-RU 253-1 via the LLS interface. The LLS interface corresponds to the fronthaul interface. The LLS interface refers to the logical interface between the O-DU 251 and the O-RU 253-1 using the lower layer functional split (i.e., based on the functional 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.

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

[0057] Figure 3a FIG. 2 shows a functional configuration of a distributed unit (DU) according to an embodiment of the present disclosure. The configuration shown can be understood as Figure 2a DU 210 (or Figure 2b The configuration of the O-DU 251) is a part of the base station. As used herein, terms such as "module", "unit", or "component" may mean a unit for processing at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

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

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

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

[0061] The transceiver 310 may be configured to send and receive various signals. For example, the transceiver 310 may send a management plane (M-plane) message, a synchronization plane (S-plane) message, or a control plane (C-plane) message. Similarly, the transceiver 310 may send or receive a user plane (U-plane) message. Figure 3a Only the transceiver 310 is shown in FIG. 2 , but the DU 210 may include two or more transceivers.

[0062] The transceiver 310 may be configured to transmit and receive signals as described above. Thus, all or at least a portion of the transceiver 310 may also be referred to as a communication unit, a transmitting unit, a receiving unit, or a transmitting / receiving unit. In addition, throughout the following description, transmission and / or reception performed via a wireless channel is used as a meaning including that the aforementioned process is performed by the transceiver 310.

[0063] Despite Figure 3a Although not shown in the figure, the transceiver 310 may also include a backhaul transceiver for connecting to the core network or another base station. The backhaul transceiver provides an interface for performing communication with other nodes in the network. The backhaul transceiver converts a bit string sent from the base station to another node (e.g., another access node, another base station, a high-level node, a core network, etc.) into a physical signal, and converts a physical signal received from another node into a bit string.

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

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

[0066] Figure 3a The configuration of the DU 210 shown in FIG. 2 is only an example, and the configuration of the DU for performing the embodiments of the present disclosure is not limited to Figure 3a In some embodiments, a portion of the configuration may be added, deleted, or changed.

[0067] Figure 3b FIG. 1 shows a functional configuration of a radio unit (RU) according to an embodiment of the present disclosure. The configuration shown can be understood as Figure 2b RU 220 or Figure 2bThe configuration of the O-RU 253-1 is a part of the base station. As used herein, terms such as "module", "unit", or "component" may mean a unit for processing at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

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

[0069] The RF transceiver 360 performs functions for transmitting and receiving signals through a wireless channel. For example, the RF transceiver 360 up-converts a baseband signal into an RF band signal to transmit the RF band signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. The RF transceiver 360 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like.

[0070] The RF transceiver 360 may include multiple transmit / receive paths. The RF transceiver 360 may also include an antenna unit. The RF transceiver 360 may include at least one antenna array configured with multiple antenna elements. In terms of hardware, the RF transceiver 360 may be configured with digital circuits and analog circuits (e.g., radio frequency integrated circuits (RFIC)). The digital circuits and analog circuits may be implemented in a single package. The RF transceiver 360 may include multiple RF chains. The RF transceiver 360 may perform beamforming. The RF transceiver 360 may apply beamforming weights to the signal so that the signal is given directionality for transmission and reception according to the setting of the processor 380. The RF transceiver 360 may include a radio frequency (RF) block (or RF unit).

[0071] In an embodiment, the RF transceiver 360 may send and receive signals through a wireless access network. For example, the RF transceiver 360 may send a downlink signal. The downlink signal may include a synchronization signal (SS), a reference signal (RS) (e.g., a cell-specific reference signal (CRS), DM (demodulation)-RS), system information (e.g., MIB, SIB, RMSI (remaining system information), OSI (other system information)), a configuration message, control information, or downlink data. 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 Msg1 (message 1), Msg3 (message 3)), a reference signal (e.g., a sounding reference signal (SRS), DM-RS), a power headroom report (PHR), etc. Although in Figure 3bOnly the RF transceiver 360 is shown in FIG. 2 , but according to another example of implementation, the RU 220 may include two or more RF transceivers.

[0072] 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., RIM-RS type 1 of 3GPP) for notifying detection of far-field interference. The RF transceiver 460 may transmit a second type of RIM-RS (e.g., RIM-RS type 2 of 3GPP) for notifying the presence or absence of far-field interference.

[0073] The fronthaul transceiver 365 can send and receive signals. According to an embodiment, the fronthaul transceiver 365 can send and receive signals on the fronthaul interface. For example, the fronthaul transceiver 365 can receive management plane (M-plane) messages, synchronization plane (S-plane) messages, or control plane (C-plane) messages. Similarly, the fronthaul transceiver 365 can send or receive user plane (U-plane) messages. Although in Figure 3b Only the fronthaul transceiver 365 is shown in FIG. 2 , but according to another example of an implementation, the RU 220 may include two or more fronthaul transceivers.

[0074] As described above, the RF transceiver 360 and the fronthaul transceiver 365 transmit and receive signals. In this way, all or at least a part of the RF transceiver 360 and the fronthaul transceiver 365 may be referred to as a "communication unit", "transmitting unit", "receiving unit" or "transceiver unit". In addition, throughout the following description, transmission and / or reception performed via a wireless channel may be used as a meaning including that the aforementioned process is performed by the transceiver 310.

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

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

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

[0078] Figure 4 An example of functional splitting between DU and RU according to an embodiment of the present disclosure is shown. With the recent development of wireless communication technology (e.g., the introduction of 5G communication system or NR (New Radio) communication system), the frequency bands used have been further increasing. In addition, as the cell radius of the base station becomes very small, the number of RUs that need to be installed further increases. In the 5G communication system, the amount of data transmission has greatly increased by more than 10 times, and therefore, the data transmission capacity of the wired network transmitted to the fronthaul has increased significantly. Therefore, due to the above factors, the initial installation cost of the wired network in the 5G communication system may increase very significantly. In this way, in order to reduce the transmission capacity of the wired network and reduce the installation cost of the wired network, by transferring some functions of the DU's modem to the RU, "functional splitting" can be used to reduce the transmission capacity of the fronthaul.

[0079] In order to reduce the burden on DU, the role of RU, which is only responsible for existing RF functions, can be extended to a certain function of the physical layer. The higher the layer of the function performed by RU, the more the throughput of RU can be increased, thereby increasing the transmission bandwidth at the fronthaul, and at the same time, the lower the constraint on delay requirements due to response processing. The higher the layer of the function performed by RU, the smaller the virtualization gain obtained by RU, and the more the size, weight and cost of RU increase. Therefore, considering the trade-off between the above advantages and disadvantages, it is necessary to achieve optimal functional segmentation.

[0080] 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 transform / 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 transform / CP removal, digital beamforming (e.g., precombination), RE demapping, channel estimation, layer demapping, demodulation, decoding / descrambling. Based on the aforementioned trade-offs, the functional division of uplink functions and downlink functions can be defined in various types by needs between vendors, discussions on standards, etc.

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

[0082] In an embodiment, in the case where a large amount of signal processing is expected in the FR 1MMU, a functional split at a relatively high layer (e.g., the fourth functional split 420b) may be required to reduce the fronthaul capacity. In addition, since multiple PHY processing blocks are included in the RU, a functional split at an overly high layer (e.g., the sixth functional split 430) may result in a more complex control interface and impose a great burden on the implementation of the RU, and therefore, appropriate functional splitting may be required according to the deployment and implementation scheme of the DU and RU.

[0083] In an embodiment, in the case where it is impossible to process precoding of data received from the DU (i.e., when the precoding capability of the RU is limited), the third functional partition 420a or a lower functional partition (e.g., the second functional partition 410) may be applied. In the case where the functional partition can process precoding of data received from the DU, the fourth functional partition 420b or a higher functional partition (e.g., the sixth functional partition 430) may be applied.

[0084] Hereinafter, in the present disclosure, embodiments are described based on the third functional partition 420a (which may be referred to as Category A or CAT-A) or the fourth functional partition 420b (which may be referred to as Category B or CAT-B) for performing beamforming procedures in the RU, unless otherwise defined. The O-RAN specification distinguishes the types of O-RUs based on whether the precoding function is on the O-DU interface or on the O-RU interface. An O-RU in which precoding is not performed (i.e., with low complexity) may be referred to as a CAT-A O-RU. An O-RU in which precoding is performed may be referred to as a CAT-B O-RU.

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

[0086] When in DU (e.g. Figure 2a DU 210) and RU (e.g. Figure 2aWhen sending messages between RU 220 in the example, the embodiments of the present disclosure describe the specifications of eCPRI and O-RAN as a fronthaul interface as an example. 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 will be used to describe various embodiments of the present disclosure, but it should be noted that in various embodiments of the present disclosure, any other expression having the same or equivalent meaning as the corresponding term may be used instead.

[0087] For the transmission protocol of the fronthaul, Ethernet and eCPRI, which are easy to share with the network, can be used. The eCPRI header and O-RAN header can be included in the Ethernet payload. The eCPRI header can be at the front end of the Ethernet payload. The content of the eCPRI header is as follows.

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

[0089] ecpriReserved (3 bits): This parameter is reserved for further use by eCPRI.

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

[0091] ecpriMessage (1 byte): This parameter indicates the service type carried by the message type, for example, an IQ (in-phase / quadrature-phase) data message, a real-time control data message, or a transmission network delay measurement message.

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

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

[0094] ecpriSeqid (2 bytes): This parameter provides unique message identification and sequencing in two levels. The first octet of this parameter is the sequence ID used to identify the sequence of messages within the eAxC message stream, and the sequence ID is used to verify that all messages have been received and for reordering out-of-order messages. The second octet of this parameter is the subsequence ID. When a radio transmission level segment (eCPRI or IEEE-1914.3) occurs, the subsequence ID is used to verify the sequence and enable its reordering.

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

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

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

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

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

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

[0101] The control plane can be configured to provide scheduling information and beamforming information via control messages. The control plane refers to real-time control between the DU and the RU. The user plane may include IQ sample data transmitted between the DU and the RU. The user plane may include the user's downlink data (IQ data or SSB / RS), uplink data (IQ data or SRS / RS) or PRACH data. The weight vector of the aforementioned beamforming information can be multiplied by the user data. The synchronization plane generally refers to the service between the DU and the RU for the synchronization controller (e.g., IEEE ancestor). The synchronization plane may 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 may be related to initial setup, non-real-time reset, or reset, or non-real-time reporting.

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

[0103] Section Type may indicate the use of control messages sent in the control plane. For example, the use of each section type may be defined as follows.

[0104] sectionType=0: This is used to indicate unused resource blocks or symbols in DL or UL.

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

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

[0107] sectionType=3: This is for PRACH and mixed parameter set channels, and the channel requires a time or frequency offset or is different from the nominal SCS value.

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

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

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

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

[0112] C-plane messages may be exchanged between DUs (e.g., DU 210, O-DU 251) and RUs (e.g., RU 220, O-RU 253-1). The main purpose of C-plane messages is to send data-related control information (e.g., scheduling and beamforming commands) required for user data processing if they are not provided through the M-plane. This message may be sent separately for DL-related commands and UL-related commands. In the following, Figure 5a The C-plane messages for the downlink are shown in Figure 5b C-plane messages for uplink are shown in FIG.

[0113] Figure 5a An example of a downlink (DL) message according to an embodiment is shown. Figure 2a According to an embodiment, the DU 210 may include an O-DU 251. Figure 2a According to an embodiment, the RU 220 may include an O-RU 253-1.

[0114] refer to Figure 5a In operation 501, DU 210 may send a C-plane message to RU 220. RU 220 may receive the C-plane message from DU 210. The C-plane message may be sent via a fronthaul interface. The C-plane message may be configured in units of symbols. For example, each C-plane message may include scheduling information for a downlink signal in one or more symbols. For example, the C-plane message may include scheduling for a downlink signal from symbol #M to symbol #N (i.e., symbol #M, symbol #M+1, ..., symbol #N-1, symbol #N). The scheduling information may be referred to as a segment. A DL C-plane message describing multiple symbols needs to arrive at RU 220 from the end of the DL U-plane receive window for the indicated start symbol (e.g., startSymbolId) before a specific time period.

[0115] The C-plane message may be associated with one or more layers. The layer may be associated with the eAxC between the DU 210 and the RU 220. According to an embodiment, the C-plane message may be associated with one layer. The C-plane message may include scheduling information about a downlink data flow corresponding to the layer. According to another embodiment, the C-plane message may be associated with multiple layers. The C-plane message may include scheduling information about downlink data flows corresponding to different layers.

[0116] In operation 503, DU 210 may send a U-plane message for symbol #M to RU 220. DU 210 may send a U-plane message for each layer in symbol #M to RU 220. RU 220 may receive the U-plane message for symbol #M from DU 210. The U-plane message may be transmitted over a fronthaul interface. In symbol #M, the U-plane message may include IQ samples of downlink data to be sent from an upper node to a UE through a radio access network. RU 220 may send a U-plane message associated with a layer corresponding to the antenna to the UE through an antenna.

[0117] In operation 505, DU 210 may send a U-plane message for symbol #M+1 to RU 220. DU 210 may send a U-plane message for each layer to RU 220 in symbol #M+1. RU 220 may receive a U-plane message for symbol #M+1 from DU 210. The U-plane message may be transmitted over a fronthaul interface. In symbol #M+1, the U-plane message may include IQ samples of downlink data to be sent from an upper node to a UE through a wireless access network. RU 220 may send a U-plane message associated with a layer corresponding to the antenna to the UE through an antenna. Although not in Figure 5a , but according to an embodiment, DU 210 may transmit a U-plane message for each of symbols #M+2, ..., and #N-1 to RU 220. In other words, through operations 503 to 507, DU 210 may transmit a U-plane message including a downlink signal scheduled based on a C-plane message to RU 220.

[0118] In operation 507, DU 210 may send a U-plane message for symbol #N to RU 220. DU 210 may send a U-plane message for each layer in symbol #N to RU 220. RU 220 may receive the U-plane message for symbol #N from DU 210. The U-plane message may be transmitted over a fronthaul interface. In symbol #N, the U-plane message may include IQ samples of downlink data to be sent from an upper node to a UE through a radio access network. RU 220 may send a U-plane message associated with a layer corresponding to the antenna to the UE through an antenna.

[0119] Figure 5b An example of an uplink (UL) message according to an embodiment is shown. Figure 2a According to an embodiment, the DU 210 may include an O-DU 251. Figure 2a According to an embodiment, the RU 220 may include an O-RU 253-1.

[0120] refer to Figure 5bIn operation 551, DU 210 may send a C-plane message to RU 220. RU 220 may receive the C-plane message from DU 210. The C-plane message may be transmitted over a fronthaul interface. The C-plane message may be configured in units of symbols. For example, each C-plane message may include scheduling information for an uplink signal in one or more symbols. For example, the C-plane message may include scheduling for an uplink signal from symbol #M to symbol #N (i.e., symbol #M, symbol #M+1, ..., symbol #N-1, symbol #N). The scheduling information may be referred to as a segment. The UL C-plane message describing multiple symbols needs to arrive at RU 220 in a specific time period before the sample of the uplink signal that first arrives at the antenna of RU 220 in the symbol (e.g., startSymbolId).

[0121] The C-plane message may be associated with one or more layers. The layer may be associated with the eAxC between the DU 210 and the RU 220. According to an embodiment, the C-plane message may be associated with one layer. The C-plane message may include scheduling information about an uplink data flow corresponding to the layer. According to another embodiment, the C-plane message may be associated with multiple layers. The C-plane message may include scheduling information about uplink data flows corresponding to different layers.

[0122] In operation 553, RU 220 may send a U-plane message for symbol #M to DU 210. RU 220 may receive a UL signal in symbol #M. RU 220 may receive a UL signal associated with a layer corresponding to the antenna through an antenna. RU 220 may generate IQ sample data for the UL signal received in symbol #M. RU 220 may send a U-plane message for each layer to DU 210 in symbol #M. DU 210 may receive a U-plane message for symbol #M from RU 220. The U-plane message may be transmitted through a fronthaul interface. The U-plane message may include IQ sample data of an uplink signal in symbol #M.

[0123] In operation 555, RU 220 may send a U-plane message for symbol #M+1 to DU 210. RU 220 may receive a UL signal in symbol #M+1. RU 220 may receive a UL signal associated with a layer corresponding to the antenna through an antenna. RU 220 may generate IQ sample data for the UL signal received in symbol #M+1. RU 220 may send a U-plane message for each layer to DU 210 in symbol #M+1. DU 210 may receive a U-plane message for symbol #M from RU 220. The U-plane message may be transmitted through a fronthaul interface. The U-plane message may include IQ sample data of an uplink signal in symbol #M. Although in Figure 5b , but according to an embodiment, RU 220 may transmit a U-plane message for each of symbols #M+2, ..., and #N-1 to DU 210. In other words, through operations 553 to 557, RU 220 may transmit a U-plane message including a UL signal to DU 210, the U-plane message being received in the scheduling section based on the C-plane message.

[0124] In operation 557, RU 220 may send a U-plane message for symbol #N to DU 210. RU 220 may receive a UL signal in symbol #N. RU 220 may receive a UL signal associated with a layer corresponding to the antenna through an antenna. RU 220 may generate IQ sample data for the UL signal received in symbol #N. RU 220 may send a U-plane message for each layer to DU 210 in symbol #N. DU 210 may receive a U-plane message for symbol #N from RU 220. The U-plane message may be transmitted through a fronthaul interface. The U-plane message may include IQ sample data of an uplink signal in symbol #N.

[0125] Figure 6 An example of resource allocation for each layer according to an embodiment is shown. Resources may be allocated across multiple layers and multiple resource blocks (RBs) within a symbol. A DU (e.g., DU 210, O-DU 251) may perform resource allocation. The scheduler of DU 210 may allocate resources for downlink transmission of a RU (e.g., RU 220, O-RU 253-1) or uplink transmission of a UE (e.g., terminal 120). DU 210 may indicate a resource region allocated via a C-plane message. IQ samples corresponding to downlink transmission or uplink transmission may be provided from DU 210 to RU 220 via a U-plane message. The U-plane message may include IQ sample data (hereinafter referred to as U-plane data) for each layer in RU 220.

[0126] refer to Figure 6 , the horizontal axis of graph 600 indicates the frequency domain. The vertical axis of resource graph 600 indicates the layer. Resource allocation may be performed in RB units. U-plane messages may be sent to resource blocks ("PRBs"), and data for each PRB may start at a byte boundary. If the end of the data in the PRB does not fall within a byte boundary due to the bit width of the IQ, zero bits may be added until the byte boundary is reached. In the following, resource allocation in RB units is assumed in each layer.

[0127] Resource allocation may be performed for each layer within a specific region of a frequency region. The specific region of a frequency region may be indicated by the segment information of a C-plane message. For example, U-plane data of layer #0 may be allocated to RB#0 601 and RB#1 603. U-plane data of layer #1 may be allocated to RB#0 601 and RB#1 603. U-plane data of layer #2 may be allocated to RB#0 601, RB#1 603, and RB#2 605. U-plane data of layer #3 may be allocated to RB#0 601, RB#1 603, and RB#2 605. U-plane data of layer #4 may be allocated to RB#0 601. U-plane data of layer #5 may be allocated to RB#0 601, RB#1 603, RB#2 605, and RB#3 607.

[0128] Meanwhile, there is an unscheduled area (hereinafter referred to as a non-scheduled area) during a specific period of the frequency region. For example, RB#2 605 and RB#3 607 of layer #0 correspond to the non-scheduled area. RB#2 605 and RB#3 607 of layer #1 correspond to the non-scheduled area. RB#3 607 of layer #2 corresponds to the non-scheduled area. RB#3 607 of layer #3 corresponds to the non-scheduled area. RB#1 603, RB#2 605, and RB#3 607 of layer #4 correspond to the non-scheduled area.

[0129] DU (e.g., DU 210 and O-DU 251) can provide channel information for each UE. In a specific resource (e.g., a time slot), an RU (e.g., RU 220, O-RU 253-1) can calculate beamforming weights for co-scheduled UEs based on channel information. An identifier associated with each data segment (e.g., a user identifier (ueId) of a C-plane message) can be used for beamforming. If a beamforming method based on channel information is used for at least one layer (or spatial stream), DU 210 should use the same beamforming method for all layers (or spatial streams) of a specific time-frequency resource element. For example, segment type 5 of a C-plane message can be used for scheduling information for a beamforming method based on channel information. One or more identifiers (e.g., ueId) can be associated with a segment of a C-plane message. DU 210 can provide scheduling information for each layer to RU 220 through the corresponding ueId.

[0130] Figure 7a to Figure 7b An example of beamforming using an indication of a non-scheduled layer according to an embodiment is shown. The beamforming may include beamforming based on channel information. The DU 210 may provide the scheduling information of each layer to the RU (e.g., RU 220, O-RU 253-1) through the corresponding UEID. Figure 7a In Figure 7B, assuming Figure 6The resource allocation shown in the example uses ueId to explain the scheduling information.

[0131] refer to Figure 7a , the horizontal axis of the graph 700 indicates the frequency domain. The vertical axis of the resource graph 700 indicates the layer. The ueId may be allocated in a segment unit. For example, the segment 710 may include RB#0 601, RB#1 603, RB#2 605, and RB#3 607.

[0132] According to an embodiment, a group configuration for multiple ports can be used to indicate a segment. For example, the segment extension 10 (SE 10) of the O-RAN standard can be used for a C-plane message. In addition to the beam ID or UEID, the C-plane segment information of multiple ports (ie, layers or Tx / Rx paths) can be the same. If multiple ports share common segment information within RU 220, the C-plane segments to be transmitted through the corresponding ports can be merged into one C-plane segment through the representative port by using SE 10. For example, in order to merge C-plane segments, segment extension information as shown in the following table can be added to the C-plane message.

[0133] [Table 1]

[0134]

[0135] "ef" may indicate the presence or absence of a segment extension. For example, if "ef" is 1, it indicates c (segment extension information) of the segment extension field, and if "ef" is 0, it indicates that there is no segment extension field. "extType" indicates the type of the segment extension field, and "extLen" indicates the length in bytes within the segment extension field. "numPortc" may indicate the number of ports (e.g., eAxC ports) indicated by the segment extension field (or the number of layers, the number of transmit / receive paths). For example, "numPortc" may indicate up to 64 ports by 6 bits. "beamGroupType" may indicate the type of beam grouping. If "beamGroupType" is "00b", the beam ID of the segment header may be used as a common beam ID for all ports. If "beamGroupType" is "01b", the continuous "numPortc" beam IDs or ueIds after the beam ID or ueId of the segment header may be applied to the port according to "numPortc". If "beamGroupType" is "10b", continuous or discontinuous "numPortc" beam IDs or ueIds after the beam ID or ueId of the section header can be applied to the port according to "numPortc". If "beamGroupType" is "10b", the following table can be referred to.

[0136] [Table 2]

[0137]

[0138] The segment extension field may also include as many beamIDs (or ueIds) as "numPortc". The distinction between single-user and multi-user may be made based on whether there is overlap during scheduling within a specified frequency region (e.g., one or more RBs). For example, the C-plane message to which Table 2 is added may provide resource allocations for multiple UEs within the same segment. In other words, the C-plane message may correspond to multi-user scheduling. Figure 6 The resource allocation is performed for six layers within the same segment, so it corresponds to MU-MIMO.

[0139] In chart 700, "numPortc" may be 5. Scheduling information for a total of six ports may be provided through a C-plane message. For example, a C-plane message may include a message format according to segment type 5 and segment extension 10 of the O-RAN standard. Each port may refer to a layer of MU-MIMO. DU 210 may assign a ueId to each layer of MU-MIMO. For example, in segment 710, the ueId of layer #0 may be set to 1. In segment 710, the ueId of layer #1 may be set to 2. In segment 710, the ueId of layer #2 may be set to 10. In segment 710, the ueId of layer #3 may be set to 11. In segment 710, the ueId of layer #4 may be set to 24. In segment 710, the ueId of layer #5 may be set to 30. In this case, a ueId may also be assigned to an area without actual U-plane data (e.g., RB #2 605 of layer #0).

[0140] RU 220 may receive a C-plane message. RU 220 may identify segment 710. RU 220 may identify a UEID corresponding to segment 710. RU 220 may calculate a beamforming weight for the UEID. For example, if K layers are co-scheduled for MU-MIMO, the beamforming matrix W may be applied to the frequency domain IQ data of the K layers. However, although the regions scheduled for each layer are different, beamforming performed assuming that the same frequency region is allocated to each layer may result in degradation of beamforming performance.

[0141] In some frequency regions, at least one layer may not be scheduled. For example, scheduling of all layers is performed in RB#0 601, but layer #2 of UE#2, layer #3 of UE#2, and layer #5 of UE#4 are performed in RB#2 605. In this case, DU 210 may provide scheduling information to RU 220. However, if DU 210 does not provide information to RU 220 on non-scheduled layers (e.g., layer #0, layer #1, layer #4) in a specific frequency region (e.g., RB#2 605), even if a specific region is scheduled, RU 220 cannot know whether the specific region is not scheduled or RU 220 has not received the information. If it is assumed that the MU-MIMO beamforming of 6 layers in RB#2 605 is the same as RB#1, the beamforming weights are calculated based on both the non-scheduled layers and the scheduled layers.

[0142] The beamforming weights of 6 layers can be calculated across RB#0 601, RB#1 603, RB#2 605 and RB#3 607. Although the RBs of some layers are not scheduled, they are included as elements for calculating the beamforming weights, and thus the derived beamforming weights may be unsuitable for the actual scheduling results. In addition, the beamforming gain may be reduced because the beamforming is calculated for a larger number of layers than the actually scheduled layers. In order to solve the above problems, by indicating unscheduled layers (hereinafter referred to as non-scheduled layers) in MU-MIMO beamforming, an electronic device and method according to an embodiment of the present disclosure propose a method for improving the accuracy of beamforming weights and improving beamforming gain.

[0143] According to an embodiment, the DU 210 may transmit information indicating a non-scheduled layer in beamforming of MU-MIMO to the RU 220. According to an embodiment, a specific value of the ueId of the C-plane message of the segment type 5 of the O-RAN standard may be used to indicate a non-scheduled layer. In the scheduling information of the C-plane message of the segment type 5, the ueId may indicate a layer. The ueId may indicate a non-scheduled layer instead of indicating a scheduled layer for MU-MIMO within a segment. For example, the ueId may be 16 bits. If the value of the ueId is 0x7FFF (= 2 15-1)("111111111111111b"), the UEId may indicate a non-scheduled layer. DU 210 may identify the unscheduled layer as a non-scheduled layer and set the UEId for the non-scheduled layer to 0x7FFF. RU 220 may identify the layer corresponding to the UEId set to 0x7FFF. The identification may indicate that RU 220 interprets the UEId set to 0x7FFF as the corresponding port is not scheduled. RU 220 may perform beamforming based on identifying that U-plane data of the identified layer does not exist. Even if a U-plane message in the corresponding layer is received from DU 210, RU 220 may ignore the U-plane data.

[0144] refer to Figure 7b , the horizontal axis of the graph 750 indicates the frequency domain. The vertical axis of the resource graph 700 indicates the layer. The ueId may be allocated in the layer and RB unit. For RB#2 605 and RB#3 607 of layer #0, ueId=0x7FFF may be allocated. For RB#2 605 and RB#3 607 of layer #1, ueId=0x7FFF may be allocated. For RB#3 607 of layer #2, ueId=0x7FFF may be allocated. For RB#3 607 of layer #3, ueId=0x7FFF may be allocated. For RB#1 603, RB#2 605, and RB#3 607 of layer #4, ueId=0x7FFF may be allocated.

[0145] According to an embodiment, DU 210 may indicate a non-scheduled layer to RU 220 through segment extension information of a C-plane message. For example, DU 210 may send a C-plane message for layer #0 to layer #5 to RU 220. The C-plane message may include scheduling information for RB #2 605. The segment extension information of the C-plane message may include "numPortc=5" and may include 5 UEIDs. The UEID and 5 additional UEIDs included in the segment area of ​​the C-plane message may indicate layer #0, layer #1, layer #2, layer #3, layer #4, and layer #5, respectively. Each non-scheduled layer may have a predefined value. The value of the UEID of layer #0 may be "0x7FFF". The value of the UEID of layer #1 may be "0x7FFF". The value of the UEID of layer #4 may be "0x7FFF". Each actually scheduled layer may have a unique UEID value. The value of the UEID of layer #2 may be "0x000A". The value of ueId of layer #3 may be "0x000B". The value of ueId of layer #5 may be "0x001E".

[0146] According to another embodiment, DU 210 may indicate a non-scheduled layer to RU 220 by transmission of a C-plane message for each layer. For example, DU 210 may send a C-plane message for layer #0 to RU 220. Information (e.g., eAxCID) of a header of the C-plane message may indicate layer #0. The segments of the C-plane message may indicate RB #2 605 and RB #3 607, and the ueId of the C-plane message may be set to 0x7FFF. In this way, a non-scheduled region for each of layer #1, layer #2, layer #3, and layer #4 may be indicated.

[0147] RU 220 may calculate beamforming weights based on the joint scheduling layer of MU-MIMO. The beamforming weights may include a beamforming matrix and may be applied to IQ data in the frequency domain. RU 220 may identify a non-scheduled layer. RU 220 may calculate beamforming weights based on at least one layer different from the non-scheduled layer. For example, in RB#0 601, RU 220 may calculate beamforming weights 761 based on 6 UEIDs. In RB#0 601, MU-MIMO beamforming for 6 layers may be performed.

[0148] In RB#1 603, RU 220 may calculate beamforming weights 763 based on 5 UEIDs. In RB#1 603, layer #4 may be indicated as a non-scheduled layer. Here, the beamforming weight of layer #4 is not set to "0". This means that before calculating the beamforming weight, the UEID of layer #4 is excluded from the array elements used to calculate the beamforming weight. Therefore, the weight of layer #4 is not calculated. In addition, RU 220 may calculate beamforming weights 763 for 5 layers. In RB#1 603, MU-MIMO beamforming for 5 layers may be performed.

[0149] In RB#2 605, RU 220 may calculate beamforming weights 765 based on 3 UEIDs. In RB#2 605, layer #0, layer #1, and layer #4 may be indicated as non-scheduled layers. Here, the beamforming weight of layer #4 is not set to "0". This means that before calculating the beamforming weight, the UEID of layer #4 is excluded from the array elements used to calculate the beamforming weight. Therefore, the beamforming weight of each of layer #0, layer #1, and layer #4 is not calculated. In addition, RU 220 may calculate beamforming weights 765 for 3 layers. In RB#1 603, MU-MIMO beamforming for 3 layers may be performed.

[0150] In RB#3 607, RU 220 may calculate beamforming weight 767 based on ueId of layer#5. RU 220 may calculate beamforming weight by assuming a single user except for MU-MIMO beamforming.

[0151] exist Figure 7b , 0x7FFF(=2 15 -1) is shown as a predefined value of ueId to indicate a non-scheduled layer, but the embodiments of the present disclosure are not limited thereto. For example, the value indicating the non-scheduled layer may be defined as another value (e.g., 0x0FF (=255)). Figure 7b In the embodiment, the value indicating the non-scheduled layer is described as being predetermined, but the embodiments of the present disclosure are not limited thereto. For example, the value indicating the non-scheduled layer may be defined based on the M-plane parameter.

[0152] Figure 8 An example of beamforming weights for each resource region according to an embodiment is shown. Figure 8 In order to describe the applied beamforming weights, it is assumed that Figure 6 The resource allocation and Figure 7b ueId.

[0153] refer to Figure 8 , chart 800 indicates beamforming weights for each RB. The beamforming weights may include a beamforming matrix. The beamforming matrix may be calculated based on channel information according to a specified reference (e.g., minimum mean square error (MMSE), zero forcing (ZF)). The beamforming matrix may include factors for each layer. For example, in RB#0 601, RU 220 may obtain beamforming weights 761 (W RB0 ). By receiving the matrix [h 1 h 2 h 10 h 11 h 24 h 30 ] to calculate the beamforming weight 761 (W RB0 ). Each channel information corresponds to the scheduled ueId.

[0154] In the non-scheduled layer as an RB in which the non-scheduled layer exists, the beamforming weight may be calculated in a different manner. According to an embodiment of the present disclosure, the beamforming weight calculation method according to the indication of the non-scheduled layer is that the non-scheduled layer is not considered as an array element of the beamforming matrix. For example, in RB#1603, RU 220 may obtain beamforming weight 763. By receiving the matrix [h 1 h 2 h 10 h 11 h 30 ] to calculate the beamforming weights 763 (W RB1 ). Since layer #4 is not scheduled, h, which is the channel information of layer #4,24 is not provided as input to the calculation of the beamforming weight 763. In addition, for example, in RB#2 605, RU 220 may obtain the beamforming weight 765. By receiving the matrix [h 1 h 2 h 10 h 11 h 30 ] to calculate the beamforming weights 763 (W RB1 ). Each channel information corresponds to the scheduled UEId. Since layer #0, layer #1, and layer #4 are not scheduled, h as the channel information of layer #0, layer #1, and layer #4 1 、h 2 and h 24 Not provided as input to the calculation of beamforming weights 763.

[0155] In the case where the number of layers scheduled by the non-scheduled layer is 1, the C-plane message may formally indicate MU-MIMO beamforming, but the actually calculated beamforming weight may indicate SU-MIMO beamforming. For example, in RB#3 607, RU 220 may obtain beamforming weight 767. Beamforming weight 763 (W RB3 ) can be calculated as h 30 , which is the channel of the scheduled ueId. Since layer #0, layer #1, layer #2, layer #3 and layer #4 are not scheduled, only h 30 (which is the channel information scheduled in layer #5 among the layers configured for MU-MIMO beamforming (e.g., layer #0, layer #1, layer #2, layer #3, layer #4, and layer #5)) is provided as input to the calculation of the beamforming weight 763.

[0156] Since different scheduling results are used for each RB, the beamforming weight can be calculated differently for each RB. Figure 8 In the example, as mentioned for each RB, the channel information corresponding to the non-scheduled layer is not used as input for beamforming weight calculation. Since the non-scheduled layer intentionally schedules only C-plane ueIds without U-plane data allocation due to interference after scheduling, the non-scheduled layer is different from the nulling layer in which the beamforming weights are calculated only in the layer to which U-plane data is allocated. In addition, the beamforming weights are not allocated to unnecessary layers, so the beamforming gain may increase.

[0157] Fig. 9 FIG. 4 shows a functional configuration of a DU using an indication of a non-scheduled layer and a functional configuration of an RU for beamforming according to an embodiment. Figure 2aAccording to an embodiment, the DU 210 may include an O-DU 251. Figure 2a According to an embodiment, the RU 220 may include an O-RU 253-1.

[0158] refer to Fig. 9 , DU 210 may include a scheduler 901, a modem 903, a C-plane processing unit 910a, and a U-plane processing unit 920a. The scheduler 901 may perform resource allocation. Resource allocation refers to U-plane data, which is the scheduling of signals to be transmitted on the radio access network. Resource allocation may be performed in layers and RB units. The ueId of a C-plane message with a segment type 5 of the O-RAN standard may represent the ueId assigned to the layer. According to an embodiment, the scheduler 901 may perform resource allocation based on the ueId. The result of resource allocation may be distinguished by the ueId. According to an embodiment, a specific value of the ueId in a specific RB area may be used to indicate an unscheduled layer. For example, a ueId indicating 0x7FFF may indicate an unscheduled layer.

[0159] The modem 903 may perform modulation and demodulation on a signal to be sent on the wireless access network. The modem 903 may receive a scheduling signal from the scheduler 901. The modem 903 may generate IQ sample data corresponding to the scheduling signal. The signal may be provided to the RU 220 on the fronthaul interface in the form of a U-plane message. The modem 903 may provide the IQ sample data to the U-plane processing unit 920a.

[0160] The C-plane processing unit 910a may generate a C-plane message. The C-plane processing unit 910a may generate a C-plane message based on the scheduling result received from the scheduler 901. According to an embodiment, the C-plane processing unit 910a may generate a C-plane message including a ueId for indicating an unscheduled layer. The C-plane processing unit 910a may send the C-plane message to the RU 220. The C-plane processing unit 910a may send the C-plane message to the C-plane processing unit 910b of the RU 220. The C-plane message may be provided on the fronthaul interface between the DU 210 and the RU 220.

[0161] The U-plane processing unit 920a may generate a U-plane message. The U-plane processing unit 920a may obtain IQ sample data from the modem 903. The U-plane processing unit 920a may generate a U-plane message including the IQ sample data. The U-plane processing unit 920a may send the U-plane message to the RU 220. The U-plane processing unit 920a may send the U-plane message to the U-plane processing unit 920b of the RU 220. The U-plane message may be provided on the fronthaul interface between the DU 210 and the RU 220.

[0162] The RU 220 may include a C-plane processing unit 910 b , a U-plane processing unit 920 b , a beamforming weight generation unit 930 , and a beamforming unit 940 .

[0163] The C-plane processing unit 910b may receive a C-plane message from the DU 210. The C-plane processing unit 910b may receive a C-plane message from the C-plane processing unit 910a of the DU 210. The C-plane processing unit 910b may process the received C-plane message. According to an embodiment, the C-plane processing unit 910b may identify scheduling information of the C-plane message. The C-plane processing unit 910b may identify whether each layer is scheduled at a designated frequency region (e.g., RB). The C-plane processing unit 910b may provide a scheduling result to the beamforming weight generation unit 930. The C-plane processing unit 910b may provide a ueId and information about the ueId to the beamforming weight generation unit 930.

[0164] The U-plane processing unit 920b may receive a U-plane message from the DU 210. The U-plane processing unit 920b may receive a U-plane message from the U-plane processing unit 920a of the DU 210. The U-plane processing unit 910b may process the received U-plane message. The U-plane processing unit 920b may provide IQ sample data of the U-plane message to the beamforming weight generation unit 930.

[0165] The beamforming weight generation unit 930 may calculate the beamforming weight. The beamforming weight may be calculated by the RU 220 based on the channel estimation. According to an embodiment, the beamforming weight generation unit 930 may be configured not to generate beamforming weights for non-scheduled layers. The beamforming weight generation unit 930 may identify the scheduled layer. The beamforming weight generation unit 930 may identify the non-scheduled layer. According to an embodiment, the beamforming weight generation unit 930 may identify the non-scheduled layer based on the value of ueId. If ueId indicates a value dedicated to non-scheduled (e.g., 0x7FFF or 0x00 FF (=2 8 -1)("000000011111111")), the beamforming weight generation unit 930 can recognize that the corresponding layer is not scheduled within the segment of the C-plane. Even if multiple layers for MU-MIMO are formed by the C-plane, the beamforming weight generation unit 930 can calculate the beamforming weight only for at least one scheduled layer instead of calculating the beamforming weight for multiple layers. In other words, the non-scheduled layer is not included as an array element of the beamforming weight matrix.

[0166] The beamforming unit 940 may perform beamforming. The beamforming unit 940 may apply beamforming weights. The beamforming weights may be applied to frequency domain IQ data of one or more layers. The beamforming weights may be applied to IQ sample data of a U-plane message. The RU 220 may transmit a downlink signal to which the beamforming weights are applied through the beamforming unit 940. For example, the RU 220 may transmit a downlink signal to a UE (e.g., terminal 120).

[0167] exist Fig. 9 , DL U-plane data processing is described as an example, but the embodiments of the present invention are not limited thereto. The embodiments of the present disclosure may also be applied to UL U-plane data processing. According to an embodiment, the U-plane processing unit 920a of the DU 210 may receive a U-plane message from the U-plane processing unit 920b of the RU 220. The U-plane message may include IQ sample data for an uplink signal.

[0168] Fig.10 FIG. 4 shows an operation flow of a DU for indicating a non-scheduled layer according to an embodiment. Figure 2a According to an embodiment, the DU 210 may include an O-DU 251.

[0169] refer to Fig.10 In operation 1001, the DU 210 may identify a non-scheduled layer in a resource region. The resource region is a time-frequency resource and may refer to an RB region corresponding to a symbol. The resource region may be referred to as a data segment. The DU 210 may identify an unscheduled layer in the RB region as a non-scheduled layer.

[0170] In operation 1003, DU 210 may generate a C-plane message including information about a resource region and UE identification information corresponding to a value indicating non-scheduling for a layer. The information about the resource region may include segment information indicating an RB region corresponding to a symbol. The C-plane message may indicate a resource region by the position of a starting PRB (e.g., startPrbc) and the number of consecutive PRBs (e.g., numPrbc). The UE identification information may be used for beamforming based on channel information. For scheduling of MU-MIMO beamforming, each layer may correspond to UE identification information. The UE identification information may include a ueId parameter for providing a label of a UE to which the segment content is applied. For example, the ueId parameter may be configured with 15 bits. According to an embodiment, the UE identification information may indicate a predefined value for indicating non-scheduling of a layer or a preconfigured value (e.g., an M-plane parameter) for indicating non-scheduling of a layer. For example, if the value of the ueId parameter is 0x7FFF, non-scheduling of the layer corresponding to the ueId parameter may be indicated. RU 220 may interpret the ueId set to 0x7FFF as indicating that the corresponding port is not scheduled. RU 220 may recognize that the resource region of the corresponding port of the ueId set to 0x7FFF is not allocated. For another example, if the last 8 bits of the bits of the ueId parameter indicate 255, non-scheduling of the layer corresponding to the ueId parameter may be indicated.

[0171] According to an embodiment, a C-plane message may be sent for each layer. The C-plane message may include scheduling information for the corresponding layer. For example, the C-plane message may have a message format of segment type 5 of the O-RAN standard. Channel information associated with UE identification information may be used to calculate the beamforming weight of the layer. A C-plane message different from a C-plane message including scheduling information may be associated with an unscheduled layer. The ueId parameter included in the segment information of the C-plane message of segment type 5 may indicate non-scheduling. The C-plane message may indicate a non-scheduling area.

[0172] According to another embodiment, the C-plane message may include scheduling information for multiple layers. For example, the C-plane message may have a message format of segment type 5 of the O-RAN standard. In addition, the C-plane message may include segment extension information for group configuration of multiple ports (e.g., SE 10 with the O-RAN standard). The C-plane message may include UE identification information for each of the multiple layers in the same resource area. In this case, the ueId parameter of the UE identification information associated with the unscheduled layer may indicate non-scheduling. For example, if the unscheduled layer as a non-scheduled layer is the first layer, the ueId of the segment information of the C-plane message may indicate non-scheduling. In addition, for example, if the unscheduled layer as a non-scheduled layer is not the first layer, the ueId corresponding to the sequence of the non-scheduled layer may indicate non-scheduling in the segment extension information of the C-plane message.

[0173] In operation 1005, the DU 210 may send a C-plane message. The DU 210 may send the C-plane message to the RU 220 through a fronthaul interface. The C-plane information may be used to calculate beamforming weights so as to perform beamforming in the RU 220.

[0174] although Fig.10 Although not shown in the figure, a U-plane message for a transmission signal in a region scheduled by a C-plane message may be sent on a fronthaul interface. For example, in the case of downlink transmission, the DU 210 may send a U-plane message corresponding to another layer other than the non-scheduled layer to the RU 220 within a resource region of the C-plane. In addition, for example, in the case of uplink transmission, the DU 210 may receive a U-plane message corresponding to another layer other than the non-scheduled layer from the RU 220 within a resource region of the C-plane.

[0175] The indication of the non-scheduled layer can be used to calculate the beamforming weight to be applied to the signal transmitted on the radio access network in the RU 220. Since the indicated non-scheduled layer is excluded from the calculation of the beamforming weight value, a beamforming weight value suitable for actual scheduling can be obtained. In addition, since the allocation of unnecessary layers is not considered, the beamforming gain can be increased.

[0176] Fig.11 FIG. 4 shows an operation flow of an RU for indicating a non-scheduled layer according to an embodiment. Figure 2a According to an embodiment, the RU 220 may include an O-RU 253.

[0177] refer to Fig.11In operation 1101, RU 220 may receive a C-plane message including information about a resource region and UE identification information corresponding to a value for indicating non-scheduling for a layer. The information about the resource region may include segment information indicating an RB region corresponding to a symbol. The C-plane message may indicate a resource region by the position of a starting PRB (e.g., startPrbc) and the number of consecutive PRBs (e.g., numPrbc). The UE identification information may be used for beamforming based on channel information. For scheduling of MU-MIMO beamforming, each layer may correspond to UE identification information. The UE identification information may include a ueId parameter for providing a label of a UE to which the segment content is applied. For example, the ueId parameter may be configured with 15 bits. According to an embodiment, the UE identification information may indicate a predefined value for indicating non-scheduling of a layer or a preconfigured value (e.g., an M-plane parameter) for indicating non-scheduling of a layer. For example, if the value of the ueId parameter is 0x7FFF, non-scheduling of a layer corresponding to the ueId parameter may be indicated. For another example, if the last 8 bits of the ueId parameter indicate 255, it may indicate non-scheduling of the layer corresponding to the ueId parameter.

[0178] In operation 1103, RU 220 may calculate beamforming weights based on the C-plane message. RU 220 may identify a non-scheduled layer based on the C-plane message. RU 220 may identify at least one layer to be scheduled based on the C-plane message or another C-plane message. RU 220 may calculate beamforming weights for at least one layer scheduled by excluding the non-scheduled layer. In other words, the indicated non-scheduled layer is not used as an input for calculating the beamforming weights.

[0179] According to an embodiment, a C-plane message may be sent for each layer. In order to calculate the beamforming weight of the layer, channel information associated with the UE identification information corresponding to the layer may be used. For example, the C-plane message may include a message format having a segment type 5 of the O-RAN standard. A C-plane message for at least one layer may indicate the scheduling of the corresponding layer in the segment. A C-plane message for a non-scheduled layer may indicate non-scheduling in the segment. The ueId parameter included in the segment information of the C-plane message of the non-scheduled layer may indicate non-scheduling. The segment of the C-plane message may be a non-scheduled area.

[0180] According to another embodiment, the C-plane message may include scheduling information for multiple layers. For example, the C-plane message may include a message format with a segment type 5 of the O-RAN standard. In addition, the C-plane message may include segment extension information for group configuration of multiple ports (e.g., SE 10 with the O-RAN standard). The C-plane message may include UE identification information for each of the multiple layers in the same resource area. In this case, the ueId parameter of the UE identification information associated with the unscheduled layer may indicate non-scheduling.

[0181] RU 220 may calculate beamforming weights based on the scheduled layers (excluding non-scheduled layers) within a specific resource region. Beamforming weights refer to an array for at least one scheduled layer. The array may include weight values ​​to be applied to the IQ data in each layer. The size of the array corresponds to the number of at least one scheduled layer. Therefore, if the UE identification information of a layer indicates the layer as a non-scheduled layer, even if the C-plane message indicates 6 layers, the beamforming weight W may include weight values ​​for each of the 5 layers.

[0182] RU 220 may calculate beamforming weights based on channel information. For example, RU 220 may calculate beamforming weights based on periodically provided channel information (e.g., channel information of a C-plane message of segment type 6). In addition, for example, RU 220 may calculate beamforming weights based on channel information and scheduling information (e.g., segment information of a C-plane message of segment type 5). RU 220 may calculate beamforming weights based on channel information of a scheduled layer. In this case, if the value of ueId indicates non-scheduling, RU 220 may ignore the channel information of the layer corresponding to ueId. If the value of ueId does not indicate non-scheduling, RU 220 may calculate beamforming weights based on the channel information of the layer corresponding to ueId.

[0183] In operation 1105, RU 220 may perform beamforming. RU 220 may perform beamforming based on the calculated beamforming weights. RU 220 may send a downlink signal through beamforming. The downlink signal may be sent on the scheduled radio resource through a C-plane message. The IQ sample data of the downlink signal may be provided to RU 220 through a U-plane message of each layer. RU 220 may receive a U-plane message from DU 210. A weight value corresponding to a specific layer may be applied to the IQ sample data of the U-plane message corresponding to the specific layer. Here, the specific layer may be associated with a UEID. According to an embodiment, if the UEID indicates non-scheduling, the RU 220 may not receive, or may ignore or discard the U-plane message corresponding to the layer of the UEID.

[0184] exist Fig.11 In the embodiment, the beamforming of RU 220 is described assuming downlink transmission, but the embodiments of the present disclosure are not limited thereto. The indication of the non-scheduled layer can also be applied to the beamforming of the UL signal. Based on the indication of the non-scheduled layer, the beamforming matrix of the UE for joint scheduling of MU-MIMO can be calculated.

[0185] Fig.12a and Figure 12b An example of a C-plane message for indicating a non-scheduled layer according to an embodiment is shown. The C-plane message may have a message format according to a segment type 5 of the O-RAN standard. Fig.12a In the embodiment of the present invention, a C-plane message 1200 for indicating a non-scheduled layer is described without using the SE 10 with the O-RAN standard. Figure 12b In the embodiment of the present invention, a C-plane message for indicating a non-scheduling layer is described in the case of using SE 10 with the O-RAN standard.

[0186] refer to Fig.12a , the C-plane message 1200 may include a transport header (e.g., an eCPRI header or IEEE 1914.3 information). As described above, the transport header may include "ecpriVersion", "ecpriReserved", "ecpriConcatenation", "ecpriMessage", "ecpriPayload", "ecpriRtcid / ecpriPcid", and "ecpriSeqid".

[0187] The C-plane message 1200 may include common header information. The common header information may include "data direction" indicating the data transmission direction of the base station (e.g., gNB) to be used in both DL and UL, "payloadVersion" indicating the valid 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.

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

[0189] The common header information may include "numberOfsection" indicating the number of data sections included in the C-plane message 1200. The common header information may include "section type" that determines the characteristics of the U-plane data. The common header information is the number of samples (e.g., T s =1 / 30.72 megahertz (MHz)), and may include a "time offset" that defines the offset from the start of the time slot to the start of the cyclic prefix (CP). Common header information may include a Fast Fourier Transform (FFT) / Inverse FFT (iFFT) size and a "frameStructure" that defines the SCS. Common header information is the number of samples (e.g., T s =1 / 30.72 megahertz (MHz)) and may include "cpLength" that defines the CP length.

[0190] The C-plane message 1200 may include segment information. The segment information may include a "sectionId" referring to a segment identifier. If the C-plane and the U-plane are coupled via "sectionId", the "sectionId" identifies the individual data segments described by the data segment description within the C-plane message 1200. The purpose of "sectionId" is to map the U-plane data segment to the corresponding C-plane message 1200 (and segment type) associated with the data. The segment information includes "rb" indicating whether to use each RB or each other RB, "symInc" indicating a symbol number increment command, "startPrbc" indicating the starting PRB number of the data segment description, "numPrbc" indicating the number of consecutive PRBs described per data segment, "reMask" defining the RE mask within the PRB, "numSymbol" defining the number of physical random access channel (PRACH) repetitions or the number of symbols, "ef" indicating an extension flag, and "ueId" defining the beam pattern to be applied to the U-plane data.

[0191] In the beamforming method based on channel information, DU 210 can provide channel information for each UE periodically (less frequently than each time slot) by using segment type 6 C-plane messages. Next, on a slot-by-slot basis, DU 210 can provide scheduling information by using segment type 5 C-plane messages that should be used with the channel information. RU 220 can calculate appropriate beamforming weights for co-scheduled UEs and specific time slots. RU220 can use the latest possible channel information for ueId for beamforming operations based on channel information. In other words, at the end of the reception window of the C-plane message of segment type 5, RU 220 can use channel information about the "ueId" available to RU 220.

[0192] Assuming that Figure 6 601, RB#1 603, and RB#2 605, and is not scheduled in RB#3 607. Therefore, the C-plane message may include two sections of layer #2. The first section of layer #2 (e.g., sectionId=xx) may include RB#0 601, RB#1 603, and RB#2 605. To indicate RB#0 601, RB#1 603, and RB#2 605, startPRBc may indicate 0 and numPrbc may indicate 3. The second section of layer #2 (e.g., sectionId=xx+1) may include RB#3 607. To indicate RB#3 607, startPRBc may indicate 3 and numPrbc may indicate 1. Here, since the first section is a scheduling region, the value of ueId may be assigned as 11. For example, ueId[14:0] may indicate "11". However, since the second segment is an unscheduled area, the ueId value may be set to a value for indicating a non-scheduled layer. According to an embodiment, DU 210 may set the ueId value to a value defined for a non-scheduled layer. For example, ueId[14:0] may indicate "0x7FFF". As another example, ueId[14:0] may indicate "255". According to an embodiment, in order to indicate a non-scheduled layer, DU 210 may set a certain area of ​​the bits of ueId (e.g., the lowest signal bit (LSB) 8 bits) to a specific value. For ueId, DU 210 may use a certain bit instead of using all 15 bits. For example, ueId[7:0] may indicate "255".

[0193] refer to Figure 12b, the C-plane message 1250 may include a transport header (e.g., an eCPRI header or IEEE 1914.3 information). The C-plane message 1250 may include common header information. The C-plane message 1250 may include segment information. For each of the fields of the transport header information, common header information, and segment information of the C-plane message 1250, reference may be made to Fig.12a Description of C-plane message 1200 in.

[0194] The C-plane message 1250 may include section extension information. The section extension information may have a format according to SE 10. For example, the section extension information may have a format as shown in Table 2. Figure 6 RB#1603 in the resource allocation shown. For common resource allocation of layers in RB#1 603, a C-plane message 1250 including segment extension information according to SE 10 may be provided to RU 220. Scheduling information for the first layer (e.g., layer #0) of the six layers in RB#1 603 may be indicated by the segment information of the C-plane message 1250. Scheduling information for the remaining layers (e.g., layer #1, layer #2, layer #3, layer #4, and layer #5) may be indicated by the segment extension information of the C-plane message 1250. According to SE 10, the remaining layers may be allocated to the second port ueId, the third port ueId, the fourth port ueId, the fifth port ueId, and the sixth port ueId, respectively.

[0195] In RB#1 603, UE#3 is not scheduled. In other words, RB#1 603 of layer #4 is a non-scheduled area. In order to indicate the non-scheduled area in RB#1 603, the ueId may be set to a specified value. According to an embodiment, DU 210 may set the value of the ueId as a value defined for the non-scheduled layer. For example, ueId[14:0] may indicate "0x7FFF". As another example, ueId[14:0] may indicate "255". According to another embodiment, in order to indicate the non-scheduled layer, DU 210 may set a certain area of ​​the bits of the ueId (e.g., the lowest signal bit (LSB) 8 bits) to a specific value. For the ueId, DU 210 may use some bits instead of all 15 bits. For example, ueId[7:0] may indicate "255".

[0196] In an embodiment, the electronic device of the radio unit (RU) may include at least one fronthaul transceiver, at least one radio frequency (RF) transceiver, and at least one processor coupled to the at least one fronthaul transceiver and the at least one RF transceiver. The at least one processor may be configured to receive a control plane (C-plane) message from a distributed unit (DU) via a fronthaul interface, the C-plane message including information about a resource region and user equipment (UE) identification information corresponding to a non-scheduled value for indicating a layer. The at least one processor may be configured to calculate beamforming weights based on the C-plane message. The at least one processor may be configured to perform beamforming based on the beamforming weights.

[0197] According to an embodiment, the beamforming weights may be an array for at least one layer scheduled in a resource region. The array may include weight values ​​to be applied to in-phase and quadrature-phase (IQ) data in each layer. The size of the array may correspond to the number of at least one layer. The at least one layer may not include a layer in which non-scheduled is indicated.

[0198] According to an embodiment, the beamforming weights may be calculated based on channel information received from the DU.

[0199] According to an embodiment, the C-plane message may include segment extension information for group configuration of multiple ports. The segment extension information may include UE identification information for each additional layer. The additional layer includes a layer indicated as non-scheduled, and the UE identification information of the layer may be included in the segment extension information.

[0200] According to an embodiment, the UE identification information may include a ueId parameter for providing a label of the UE to which the segment content is applied. The ueId parameter may be 15 bits, and the value used to indicate non-scheduled may be 0x7FFF, 0x00FF, or a value set by the M plane.

[0201] In an embodiment, the electronic device of the distributed unit (DU) may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to identify non-scheduling for a layer in a resource region. The at least one processor may be configured to generate a control plane (C-plane) message, the C-plane message including information about the resource region and user equipment (UE) identification information corresponding to a value for indicating non-scheduling of the layer. The at least one processor may be configured to send the generated C-plane message to a radio unit (RU). The C-plane message may be associated with a beamforming weight in the RU.

[0202] According to an embodiment, the beamforming weights may be an array for at least one layer scheduled in a resource region. The array may include weight values ​​to be applied to in-phase and quadrature-phase (IQ) data in each layer. The size of the array may correspond to the number of at least one layer. The at least one layer may not include a layer in which non-scheduled is indicated.

[0203] According to an embodiment, at least one processor may be configured to send channel information to the RU. The channel information may be used for beamforming weights.

[0204] According to an embodiment, the C-plane message may include segment extension information for group configuration of multiple ports. The segment extension information may include UE identification information for each additional layer. The additional layer includes a layer indicated as non-scheduled, and the UE identification information of the layer may be included in the segment extension information.

[0205] According to an embodiment, the UE identification information may include a ueId parameter for providing a label of the UE to which the segment content is applied. The ueId parameter may be 15 bits, and the value used to indicate non-scheduled may be 0x7FFF, 0x00 FF, or a value set by the M plane.

[0206] In an embodiment, a method performed by a radio unit (RU) may include receiving a control plane (C-plane) message from a distributed unit (DU) through a fronthaul interface, the C-plane message including information about a resource region and user equipment (UE) identification information corresponding to a non-scheduled value for indicating a layer. The method may include calculating beamforming weights based on the C-plane message. The method may include performing beamforming based on the beamforming weights.

[0207] According to an embodiment, the beamforming weights may be an array of at least one layer for scheduling in a resource region. The array may include weight values ​​to be applied to in-phase and quadrature-phase (IQ) data in each layer. The size of the array may correspond to the number of at least one layer. The at least one layer may not include a layer in which non-scheduled is indicated.

[0208] According to an embodiment, the beamforming weights may be calculated based on channel information received from the DU.

[0209] According to an embodiment, the C-plane message may include segment extension information for group configuration of multiple ports. The segment extension information may include UE identification information for each additional layer. The additional layer includes a layer indicated as non-scheduled, and the UE identification information of the layer may be included in the segment extension information.

[0210] According to an embodiment, the UE identification information may include a ueId parameter for providing a label of the UE to which the segment content is applied. The ueId parameter may be 15 bits, and the value used to indicate non-scheduled may be 0x7FFF, 0x00 FF, or a value set by the M plane.

[0211] In an embodiment, a method performed by a distributed unit (DU) may include: identifying non-scheduling for a layer in a resource region. The method may include generating a control plane (C-plane) message, the C-plane message including information about the resource region and user equipment (UE) identification information corresponding to a value for indicating non-scheduling of the layer. The method may include sending the generated C-plane message to a radio unit (RU). The C-plane message may be associated with a beamforming weight in the RU.

[0212] According to an embodiment, the beamforming weights may be an array of at least one layer for scheduling in a resource region. The array may include weight values ​​to be applied to in-phase and quadrature-phase (IQ) data in each layer. The size of the array may correspond to the number of at least one layer. The at least one layer may not include a layer in which non-scheduled is indicated.

[0213] According to an embodiment, the method may include sending channel information to the RU. The channel information may be used for beamforming weights.

[0214] According to an embodiment, the C-plane message may include segment extension information for group configuration of multiple ports. The segment extension information may include UE identification information for each additional layer. The additional layer includes a layer indicated as non-scheduled, and the UE identification information of the layer may be included in the segment extension information.

[0215] According to an embodiment, the UE identification information may include a ueId parameter for providing a label of the UE to which the segment content is applied. The ueId parameter may be 15 bits, and the value used to indicate non-scheduled may be 0x7FFF, 0x00FF, or a value set by the M plane.

[0216] In an embodiment, a method performed by a radio unit (RU) is provided. The method may include receiving a control plane (C-plane) message from a distributed unit (DU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about the resource area described by the segment and UE identification information. The segment extension information may include information about the beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The method may include identifying that a resource area is not allocated for a designated port based on the UE identification information of the designated port set to 0x7FFF in the C-plane message.

[0217] According to an embodiment, multiple ports may share the segment information in the RU. The multiple ports may include one or more ports and a representative port indicated by the segment extension information. The information about the beam group type may be "10b". The UE identification information per port may include the UE identification information of each port in the one or more ports.

[0218] According to an embodiment, the UE identification information of the designated port may be included in the segment information or the segment extension information. The segment information may correspond to segment type 5. The segment extension information may correspond to segment extension 10. The UE identification information of the designated port may be indicated by 15 bits.

[0219] According to an embodiment, the information about the resource region may include information about the starting physical resource block (PRB) of the segment description and information about the number of consecutive PRBs described in the segment. The UE identification information of the designated port set to 0x7FFF may indicate that the layer corresponding to the designated port is not scheduled within the PRB described in the segment.

[0220] According to an embodiment, the method may further include obtaining beamforming weights. The UE identification set of the segment information and the segment extension information may be associated with a UE and a layer of the UE co-scheduled in a multi-user (MU) multiple-input multiple-output (MIMO) scheduling. The beamforming weights may be obtained based on channel information of at least a portion of the UE identification set. The beamforming weights may be obtained based on non-scheduling of a resource region of a specified port.

[0221] In an embodiment, a method performed by a distributed unit (DU) is provided. The method may include setting the UE identification information of a designated port that is not scheduled to 0x7FFF. The method may include sending a control plane (C-plane) message to a radio unit (RU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about the resource area described by the segment and UE identification information. The segment extension information may include information about the beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The UE identification information of the designated port in the C-plane message may indicate that the resource area is not allocated for the designated port.

[0222] According to an embodiment, multiple ports may share the segment information in the RU. The multiple ports may include one or more ports and a representative port indicated by the segment extension information. The information about the beam group type may be "10b". The UE identification information per port may include the UE identification information of each port in the one or more ports.

[0223] According to an embodiment, the UE identification information of the designated port may be included in the segment information or the segment extension information. The segment information may correspond to segment type 5. The segment extension information may correspond to segment extension 10. The UE identification information of the designated port may be indicated by 15 bits.

[0224] According to an embodiment, the information about the resource region may include information about the starting physical resource block (PRB) of the segment description and information about the number of consecutive PRBs described in the segment. The UE identification information of the designated port set to 0x7FFF may indicate that the layer corresponding to the designated port is not scheduled within the PRB described in the segment.

[0225] According to an embodiment, a UE identification set of segment information and segment extension information may be associated with a UE and a layer of a UE co-scheduled in a multi-user (MU) multiple-input multiple-output (MIMO) scheduling. Channel information of at least a portion of the UE identification set may be used to calculate beamforming weights. The beamforming weights may be calculated based on non-scheduling of a resource region of a specified port.

[0226] In an embodiment, an electronic device of a radio unit (RU) is provided. The electronic device may include: a memory including instructions; at least one transceiver configured to send or receive signals on a fronthaul interface; and at least one processor. When the instruction is executed by the at least one processor, the RU may receive a control plane (C-plane) message from a distributed unit (DU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about a resource area described by the segment and UE identification information. The segment extension information may include information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. When the instruction is executed by the at least one processor, the RU may identify that the resource area is not allocated for the designated port based on the UE identification information of the designated port set to 0x7FFF in the C-plane message.

[0227] In an embodiment, an electronic device of a distributed unit (DU) is provided. The electronic device may include: a memory including instructions; at least one transceiver configured to send or receive signals on a fronthaul interface; and at least one processor. When the instruction is executed by the at least one processor, the DU may set the UE identification information of the unscheduled designated port to 0x7FFF. When the instruction is executed by the at least one processor, the DU may send a control plane (C-plane) message to a radio unit (RU), and the C-plane message includes segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about the resource area described by the segment and UE identification information, and the segment extension information may include information about the beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The UE identification information of the designated port in the C-plane message may indicate that the resource area is not allocated for the designated port.

[0228] In an embodiment, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium may include a memory storing a program including instructions. These instructions, when executed by a processor of a radio unit (RU), may cause the RU to receive a control plane (C-plane) message from a distributed unit (DU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information; and based on the UE identification information of the designated port set to 0x7FFF in the C-plane message to identify that the resource region is not allocated for the designated port. The segment information may include information about the resource region described by the segment and UE identification information. The segment extension information may include information about the beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port.

[0229] In an embodiment, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium may include a memory storing a program including instructions. These instructions, when executed by a processor of a distributed unit (DU), may cause the DU to set the UE identification information of a designated port that is not scheduled to 0x7FFF, and send a control plane (C-plane) message to a radio unit (RU), the C-plane message including segment extension information for group configuration of multiple ports and segment information for user equipment (UE) scheduling information. The segment information may include information about the resource area described by the segment and UE identification information. The segment extension information may include information about the beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port. The UE identification information of the designated port in the C-plane message may indicate that the resource area is not allocated for the designated port.

[0230] The electronic device and method according to the embodiments of the present disclosure may improve the beamforming performance in the RU by indicating unscheduled layers on the fronthaul interface.

[0231] Effects obtained by the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned herein will be clearly understood by ordinary technicians in the field to which the present disclosure belongs based on the following description.

[0232] The methods according to the embodiments described in the claims or specifications of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0233] In the case of being implemented as software, a computer-readable storage medium for storing one or more programs (software modules) may 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 that cause the electronic device to execute the method according to the claims or embodiments described in the specification of the present disclosure.

[0234] Such a program (software module, software) may be stored in a random access memory, a non-volatile memory including flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage device, a compact disk-ROM (CD-ROM), a digital versatile disk (DVD), another type of optical storage device, or a magnetic cartridge. Alternatively, it may be stored in a memory consisting of a combination of some or all of them. Furthermore, a plurality of memories of each configuration may be included.

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

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

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

Claims

1. A method performed by a radio unit RU, the method include: receiving a control plane C-plane message from a distributed unit DU, the C-plane message including segment extension information for group configuration of a plurality of ports and segment information for user equipment UE scheduling information, wherein the segment information includes information about a resource region described by the segment and UE identification information, and the segment extension information includes information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port; and Based on the UE identification information of the designated port set to 0x7FFF in the C-plane message, it is identified that the resource region is not allocated for the designated port.

2. The method according to claim 1, in, The multiple ports share the segment information in the RU, wherein the plurality of ports include the one or more ports indicated by the section extension information and a representative port, wherein the information about the beam group type is "10b", and The UE identification information of each port includes UE identification information of each port of the one or more ports.

3. The method according to claim 1, in, The UE identification information of the designated port is included in the section information or the section extension information, Wherein, the segment information corresponds to segment type 5, wherein the section extension information corresponds to section extension 10, and The UE identification information of the designated port is indicated by 15 bits.

4. The method according to claim 1, in, The information about the resource region includes information about the starting physical resource block (PRB) described by the section and information about the number of consecutive PRBs described by the section; and The UE identification information of the designated port set to 0x7FFF indicates that no layer corresponding to the designated port is scheduled within the PRB described in the segment.

5. The method according to claim 1, further comprising: include: Get the beamforming weights, The segment information and the UE identification set of the segment extension information are associated with the UE and the layer of the UE co-scheduled in multi-user MU multiple-input multiple-output MIMO scheduling, The beamforming weight is obtained based on channel information of at least a part of the UE identity set, and The beamforming weight is obtained based on non-scheduling of the resource area of ​​the designated port.

6. A method performed by a distributed unit DU, the method include: Set the UE identification information of the unscheduled designated port to 0x7FFF, and Sending a control plane C-plane message to a radio unit RU, wherein the C-plane message includes segment extension information for group configuration of multiple ports and segment information for user equipment UE scheduling information, The segment information includes information about a resource region described by the segment and UE identification information, and the segment extension information includes information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port, and The UE identification information of the designated port in the C-plane message indicates that the resource region is not allocated for the designated port.

7. The method according to claim 6, in, The plurality of ports share the segment information, wherein the plurality of ports include the one or more ports indicated by the section extension information and a representative port, The information about the beam group type is "10b", The UE identification information of each port includes the UE identification information of each port of the one or more ports, The UE identification information of the designated port is included in the section information or the section extension information. Wherein, the segment information corresponds to segment type 5, wherein the section extension information corresponds to section extension 10, and The UE identification information of the designated port is indicated by 15 bits.

8. The method according to claim 6, in, The information about the resource region includes information about a starting physical resource block (PRB) described by the segment and information about the number of consecutive PRBs described by the segment, and The UE identification information of the designated port set to 0x7FFF indicates that no layer corresponding to the designated port is scheduled within the PRB described in the segment.

9. The method according to claim 6, in, The segment information and the UE identification set of the segment extension information are associated with a UE and a layer of the UE co-scheduled in multi-user MU multiple-input multiple-output MIMO scheduling, Wherein, at least a portion of the channel information in the UE identification set is used to calculate the beamforming weight, and The beamforming weight is calculated based on non-scheduling of the resource area of ​​the designated port.

10. An electronic device of a wireless unit RU, the electronic device include: a memory including instructions; at least one transceiver configured to transmit or receive signals on a fronthaul interface; as well as at least one processor, Wherein, when the instruction is executed by the at least one processor, the RU: receiving a control plane C-plane message from a distributed unit DU, the C-plane message including segment extension information for group configuration of a plurality of ports and segment information for user equipment UE scheduling information, wherein the segment information includes information about a resource region described by the segment and UE identification information, and the segment extension information includes information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port; and Based on the UE identification information of the designated port set to 0x7FFF in the C-plane message, it is identified that the resource region is not allocated for the designated port.

11. The electronic device according to claim 10, in, The instructions, when executed by the at least one processor, cause the RU to perform operations according to claims 2 to 5.

12. An electronic device of a distributed unit DU, the electronic device include: a memory including instructions; at least one transceiver configured to transmit or receive signals on a fronthaul interface; as well as at least one processor, Wherein, when the instructions are executed by the at least one processor, the DU: Set the UE identification information of the unscheduled designated port to 0x7FFF, and Sending a control plane C-plane message to a radio unit RU, wherein the C-plane message includes segment extension information for group configuration of multiple ports and segment information for user equipment UE scheduling information, The segment information includes information about a resource region described by the segment and UE identification information, and the segment extension information includes information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port, and The UE identification information of the designated port in the C-plane message indicates that the resource region is not allocated for the designated port.

13. The electronic device according to claim 12, in, The instructions, when executed by the at least one processor, cause the DU to perform operations according to claims 6 to 9.

14. A non-transitory computer-readable medium comprising a memory storing a program comprising instructions, and in, When the instructions are executed by a processor of a radio unit RU, the RU: receiving a control plane C-plane message from a distributed unit DU, the C-plane message including segment extension information for group configuration of a plurality of ports and segment information for user equipment UE scheduling information, wherein the segment information includes information about a resource region described by the segment and UE identification information, and the segment extension information includes information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port; and Based on the UE identification information of the designated port set to 0x7FFF in the C-plane message, it is identified that the resource region is not allocated for the designated port.

15. A non-transitory computer-readable medium, the non-transitory computer-readable medium comprising a memory storing a program comprising instructions, in, When the instructions are executed by a processor of a distributed unit DU, the DU: Set the UE identification information of the unscheduled designated port to 0x7FFF, and Sending a control plane C-plane message to a radio unit RU, wherein the C-plane message includes segment extension information for group configuration of multiple ports and segment information for user equipment UE scheduling information, The segment information includes information about a resource region described by the segment and UE identification information, and the segment extension information includes information about a beam group type, information about the number of one or more ports indicated by the segment extension information, and UE identification information per port, and The UE identification information of the designated port in the C-plane message indicates that the resource region is not allocated for the designated port.

Images