Electronic device and method for indicating allocated resource region

Abstract

According to one embodiment, a method performed by a device of a distributed unit (DU) comprises an operation of generating a control plane (C-plane) message including section information and section extension information for indicating a resource region. The method comprises an operation of transmitting the C-plane message to a radio unit (RU). The C-plane message indicates an allocated resource region for each port among a plurality of ports for a group configuration, within the resource region.

Description

Electronic device and method for indicating resource allocation areas

[0001] The present disclosure relates to an electronic device and method for indicating a resource allocation area.

[0002] As transmission capacity increases in wireless communication systems, functional splitting, which functionally separates base stations, is being implemented. Through functional splitting, base stations can be divided into distributed units (DUs) and radio units (RUs). A fronthaul interface is defined for communication between DUs and RUs.

[0003] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above-described matters constitute prior art related to the present disclosure.

[0004] According to one embodiment, a method performed in a device of a distributed unit (DU) may include generating a control plane (C-plane) message including section information and section extension information for indicating a resource area. The method may include transmitting the control plane message to a radio unit (RU). The control plane message may indicate a resource allocation area for each port among a plurality of ports for group configuration within the resource area.

[0005] According to one embodiment, a method performed in a device of a radio unit (RU) may include receiving, from a distributed unit (DU), a control plane (C-plane) message including section information and section extension information for indicating a resource region. The method may include identifying, based on the control plane message, a resource allocation region for each port among a plurality of ports for group configuration within the resource region.

[0006] According to one embodiment, a device of a distributed unit (DU) may include a fronthaul transceiver, a memory storing instructions, and a processor. The instructions, when executed by the processor, may cause the device to generate a control plane (C-plane) message including section information and section extension information for indicating a resource region. The instructions, when executed by the processor, may cause the device to transmit the C-plane message to a radio unit (RU) via the fronthaul transceiver. The C-plane message may indicate a resource allocation region for each port among a plurality of ports for group configuration within the resource region.

[0007] According to one embodiment, a device of a radio unit (RU) may include a fronthaul transceiver, a radio frequency (RF) transceiver, a memory storing instructions, and a processor. The instructions, when executed by the processor, may cause the device to receive, from a distributed unit (DU), using the fronthaul transceiver, a control plane (C-plane) message including section information and section extension information for indicating a resource region. The instructions, when executed by the processor, may cause the device to identify, based on the control plane message, a resource allocation region for each port among a plurality of ports for group configuration within the resource region.

[0008] Figure 1 illustrates a wireless communication system.

[0009] Figure 2a illustrates a front-hole interface.

[0010] Figure 2b illustrates the fronthaul interface of an O(open)-RAN(radio access network).

[0011] Figure 3a illustrates the functional configuration of a distributed unit (DU).

[0012] Figure 3b illustrates the functional configuration of a RU (radio unit).

[0013] Figure 4 illustrates an example of function split between DU and RU.

[0014] Figure 5 shows an example of section information of a C-plane message.

[0015] Figures 6a and 6b illustrate examples of section extension information of a C-plane message, which includes information about group configuration for multiple ports.

[0016] Figure 7a illustrates an example of the operation of RU and DU in Class A.

[0017] Figure 7b illustrates an example of the operation of RU and DU in Class B.

[0018] Figure 8 illustrates an example of the operation of DU and RU for receiving an uplink signal.

[0019] Figure 9a illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0020] Figure 9b illustrates an example of section extension information for indicating resource allocation areas for each of a plurality of ports.

[0021] Figure 10a illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0022] Figure 10b illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0023] Figure 10c illustrates an example of section extension information for indicating resource allocation areas for each of a plurality of ports.

[0024] Figure 10d illustrates an example of section extension information for indicating a resource allocation area for each of a plurality of ports.

[0025] Figure 11a illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0026] Figure 11b illustrates an example of section extension information for indicating resource allocation areas for each of a plurality of ports.

[0027] Figure 12a illustrates an example of a technique for indicating at least one resource block.

[0028] Figure 12b illustrates an example of an indicator set according to a technique for indicating at least one resource block.

[0029] Figure 13 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0030] Figure 14 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0031] Figure 15 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0032] Figure 16 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0033] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0034] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0035] In the following description, terms referring to signals (e.g., signal, information, message, signaling), terms referring to resources (e.g., symbol, slot, subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), occasion), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, user stream, information, bit, symbol, codeword), terms referring to channels, terms referring to network entities, terms referring to components of devices, etc. are examples for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

[0036] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}.

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

[0038] Figure 1 illustrates a wireless communication system.

[0039] Referring to FIG. 1, FIG. 1 illustrates a base station (110) and a terminal (120) as some of the nodes utilizing a wireless channel in a wireless communication system. Although FIG. 1 illustrates only one base station, the wireless communication system may further include other base stations identical or similar to the base station (110).

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

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

[0042] The terminal (120) may be referred to as a terminal, or other terms such as 'user equipment (UE),' 'customer premises equipment (CPE),' 'mobile station,' 'subscriber station,' 'remote terminal,' 'wireless terminal,' 'electronic device,' or 'user device,' or other terms having equivalent technical meanings.

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

[0044] If large-scale characteristics of a channel carrying a symbol on a first antenna port can be inferred from a channel carrying a symbol on a second antenna port, the first antenna port and the second antenna port can be evaluated to have a QCL relationship. For example, the large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and a spatial receiver parameter.

[0045] Although both the base station (110) and the terminal (120) are described as performing beamforming in FIG. 1, the embodiments of the present disclosure are not necessarily limited thereto. In some embodiments, the terminal may or may not perform beamforming. Furthermore, the base station may or may not perform beamforming. That is, either only one of the base station and the terminal may perform beamforming, or neither the base station nor the terminal may perform beamforming.

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

[0047] In the past, in communication systems with relatively large cell radius of base stations, each base station was installed to include the functions of a digital processing unit (or distributed unit (DU)) and a radio frequency (RF) processing unit (or radio unit (RU)). However, as higher frequency bands are used in 4G (4th generation) and / or subsequent communication systems (e.g., 5G) and the cell coverage of base stations decreases, the number of base stations to cover a specific area has increased. The installation costs for operators to install base stations have also increased. In order to minimize the installation costs of base stations, a structure has been proposed in which the DU and RU of a base station are separated, one or more RUs are connected to one DU via a wired network, and one or more RUs are geographically distributed to cover a specific area. Hereinafter, the deployment structure and expanded examples of base stations according to various embodiments of the present disclosure are described through FIGS. 2A and 2B.

[0048] FIG. 2A illustrates a fronthaul interface. Unlike the backhaul between a base station and a core network, fronthaul refers to the connection between entities between a wireless LAN and a base station. FIG. 2A illustrates an example of a fronthaul structure between a DU (210) and one RU (220), but this is merely for convenience of explanation and the present disclosure is not limited thereto. In other words, embodiments of the present disclosure can also be applied to a fronthaul structure between one DU and multiple RUs. For example, embodiments of the present disclosure can be applied to a fronthaul structure between one DU and two RUs. Furthermore, embodiments of the present disclosure can also be applied to a fronthaul structure between one DU and three RUs.

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

[0050] As communications technology advances, mobile data traffic increases, significantly increasing the bandwidth requirements for the fronthaul between the digital unit and the radio unit. In deployments such as C-RAN (centralized / cloud radio access network), the DU performs functions for the packet data convergence protocol (PDCP), radio link control (RLC), media access control (MAC), and physical layer (PHY), while the RU can be implemented to perform additional functions for the PHY layer in addition to its radio frequency (RF) functions.

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

[0052] The RU (220) may be responsible for lower layer functions of a wireless network. For example, the RU (220) may perform a part of the PHY layer, an RF function. Here, a part of the PHY layer refers to functions of the PHY layer that are performed at a relatively lower level than the DU (210), and may include, for example, iFFT transformation (or FFT transformation), CP (cyclic prefix) insertion (CP removal), and digital beamforming. An example of such specific functional separation is described in detail in FIG. 4. The RU (220) may be referred to as an 'access unit (AU)', an 'access point (AP)', a 'transmission / reception point (TRP)', a 'remote radio head (RRH)', a 'radio unit (RU)', or other terms having an equivalent technical meaning thereto. In one embodiment, if RU (220) complies with the O-RAN standard, it may be referred to as O-RU (O-RAN RU). RU (220) may be represented as a second network entity for a base station (e.g., gNB) in embodiments of the present disclosure, if necessary.

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

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

[0055] Figure 2b illustrates the fronthaul interface of an open RAN (radio access network). A base station (110) according to a distributed deployment is exemplified as an eNB or gNB.

[0056] Referring to FIG. 2b, the base station (110) may include an O-DU (251) and O-RUs (253-1, ..., 253-n). Hereinafter, for convenience of explanation, the operation and function of the O-RU (253-1) may be understood as a description of each of the other O-RUs (e.g., O-RU (253-n)).

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

[0058] The O-DU (251) can communicate with the O-RU (253-1) through an LLS interface. The LLS interface corresponds to a fronthaul interface. The LLS interface refers to a logical interface between the O-DU (251) and the O-RU (253-1) that utilizes lower layer functional split (i.e., intra-PHY based functional split). 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.

[0059] In FIG. 2B, to explain the O-RAN, entities of the base station (110) are described as O-DU and O-RU. However, these names are not to be construed as limiting the embodiments of the present disclosure. In the embodiments described below, it is obvious that the operations of the DU (210) can be performed by the O-DU (251). The description of the DU (210) can be applied to the O-DU (251). Similarly, in the embodiments described below, it is obvious that the operations of the RU (220) can be performed by the O-RU (253-1). The description of the RU (220) can be applied to the O-DU (253-1).

[0060] Fig. 3a illustrates the functional configuration of a DU (distributed unit). The configuration illustrated in Fig. 3a can be understood as the configuration of the DU (210) of Fig. 2a (or the O-DU (250) of Fig. 2b) as part of a base station. Terms such as "...unit" and "...unit" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.

[0061] Referring to FIG. 3a, DU (210) includes a transceiver (310), memory (320), and processor (330).

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

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

[0064] The transceiver (310) can transmit and receive signals. For example, the transceiver (310) can transmit a management plane (M-plane) message. For example, the transceiver (310) can transmit a management plane (S-plane) message. For example, the transceiver (310) can transmit a control plane (C-plane) message. For example, the transceiver (310) can transmit a user plane (U-plane) message. For example, the transceiver (310) can receive a user plane message. Although only the transceiver (310) is illustrated in FIG. 3A, in other implementations, the DU (210) may include two or more transceivers.

[0065] The transceiver (310) transmits and receives signals as described above. Accordingly, all or part of the transceiver (310) may be referred to as a "communication unit," a "transmitter," a "receiver," or a "transmitter-receiver unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the transceiver (310) performs the processing described above.

[0066] Although not illustrated in FIG. 3A, the transceiver (310) may further include a backhaul transceiver for connection to the core network or other base stations. The backhaul transceiver provides an interface for communicating with other nodes within the network. That is, the backhaul transceiver converts a bit stream transmitted from the base station to other nodes, such as other access nodes, other base stations, upper nodes, the core network, etc., into a physical signal, and converts a physical signal received from other nodes into a bit stream.

[0067] The memory (320) stores data such as basic programs, application programs, and setting information for the operation of the DU (210). The memory (320) may be referred to as a storage unit. The memory (320) may be composed of volatile memory, nonvolatile memory, or a combination of volatile memory and nonvolatile memory. In addition, the memory (320) provides stored data upon request from the processor (330).

[0068] The processor (330) controls the overall operations of the DU (210). The processor (380) may be referred to as a control unit. For example, the processor (330) transmits and receives signals through the transceiver (310) (or through the backhaul communication unit). In addition, the processor (330) records and reads data from the memory (320). In addition, the processor (330) may perform the functions of the protocol stack required by the communication standard. Although only the processor (330) is illustrated in FIG. 3A, the DU (210) may include two or more processors according to other implementation examples.

[0069] The configuration of DU (210) illustrated in FIG. 3A is merely an example, and examples of DUs performing embodiments of the present disclosure are not limited to the configuration illustrated in FIG. 3A. In some embodiments, some configurations may be added, deleted, or changed.

[0070] Fig. 3b illustrates the functional configuration of a radio unit (RU). The configuration illustrated in Fig. 3b can be understood as a configuration of the RU (220) of Fig. 2b or the O-RU (253-1) of Fig. 2b as part of a base station. Terms such as "...unit" and "...unit" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.

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

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

[0073] The RF transceiver (360) may include multiple transmission and reception paths. Furthermore, the RF transceiver (360) may include an antenna unit. The RF transceiver (360) may include at least one antenna array composed of multiple antenna elements. In terms of hardware, the RF transceiver (360) may be composed of digital circuits and analog circuits (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the RF transceiver (360) may include multiple RF chains. The RF transceiver (360) may perform beamforming. The RF transceiver (360) may apply beamforming weights to a signal to be transmitted and received in order to impart directionality according to the settings of the processor (380). According to one embodiment, the RF transceiver (360) may include a radio frequency (RF) block (or RF section).

[0074] According to one embodiment, the RF transceiver (360) can transmit and receive signals on a radio access network. For example, the RF transceiver (360) can transmit a downlink signal. The downlink signal can include a synchronization signal (SS), a reference signal (RS) (e.g., a cell-specific reference signal (CRS), a demodulation (DM)-RS), system information (e.g., a MIB, a SIB, remaining system information (RMSI), other system information (OSI)), a configuration message, control information, or downlink data. In addition, for example, the RF transceiver (360) can 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), or a power headroom report (PHR). Although only the RF transceiver (360) is illustrated in FIG. 3b, in other implementation examples, the RU (220) may include two or more RF transceivers.

[0075] According to embodiments, 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) to indicate the 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) to indicate the presence or absence of far-field interference.

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

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

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

[0079] The processor (380) controls the overall operations of the RU (220). The processor (380) may be referred to as a control unit. For example, the processor (380) transmits and receives signals through the RF transceiver (360) or the fronthaul transceiver (365). In addition, the processor (380) records and reads data in the memory (370). In addition, the processor (380) may perform functions of a protocol stack required by a communication standard. Although only the processor (380) is illustrated in FIG. 3B, the RU (220) may include two or more processors according to other implementation examples. The processor (380) may be a set of instructions or codes stored in the memory (370), or may be a storage space that stores instructions / codes or instructions / codes that are at least temporarily residing in the processor (380), or may be a part of the circuitry that constitutes the processor (380). Additionally, the processor (380) may include various modules for performing communication. The processor (380) may control the RU (220) to perform operations according to the embodiments described below.

[0080] The configuration of RU (220) illustrated in FIG. 3b is merely an example, and examples of RUs performing embodiments of the present disclosure are not limited to the configuration illustrated in FIG. 3b. In some embodiments, some configurations may be added, deleted, or changed.

[0081] Figure 4 illustrates an example of function split between DUs and RUs. As wireless communication technologies advance (e.g., the introduction of 5G (5th generation) communication systems (or NR (new radio) communication systems), the frequency bands used have increased further. As the cell radius of a base station has become significantly smaller, the number of RUs required for installation has also increased further. Furthermore, in 5G communication systems, the amount of data transmitted has increased by a factor of up to ten, significantly increasing the transmission capacity of the wired network transmitted to the fronthaul. Due to the factors described above, the installation cost of the wired network in the 5G communication system may increase significantly. Therefore, in order to lower the transmission capacity of the wired network and reduce the installation cost of the wired network, 'function split' can be utilized, which transfers some of the functions of the modem of the DU to the RU to lower the transmission capacity of the fronthaul.

[0082] To reduce the burden on the DU, the role of the RU, which is traditionally solely responsible for RF functions, can be expanded to include some physical layer functions. As the RU performs higher-layer functions, its throughput increases, which can increase transmission bandwidth in the fronthaul while reducing latency requirements due to response processing. However, as the RU performs higher-layer functions, virtualization gains decrease, and the RU's size, weight, and cost increase. Considering the trade-offs between the advantages and disadvantages described above, implementing an optimal functional separation is required.

[0083] Referring to Figure 4, the functional separation in the physical layer below the MAC layer is illustrated. For the downlink (DL) that transmits a signal to a terminal through a wireless network, the base station can sequentially perform channel encoding / scrambling, modulation, layer mapping, antenna mapping, RE mapping, digital beamforming (e.g., precoding), iFFT transform / CP insertion, and RF transform. For the uplink (UL) that receives a signal from a terminal through a wireless network, the base station can sequentially perform RF transform, FFT transform / CP removal, digital beamforming (pre-combining), RE demapping, channel estimation, layer demapping, demodulation, and decoding / descrambling. The separation of uplink and downlink functions can be defined in various types depending on the needs of vendors, discussions in standards, etc., according to the above-mentioned trade-offs.

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

[0085] In one embodiment, when a large amount of signal processing is expected, such as in the FR 1 MMU, functional separation at a relatively high layer (e.g., the fourth functional separation (420b)) may be required to reduce fronthaul capacity. In addition, functional separation at too high a layer (e.g., the sixth functional separation (430)) may complicate the control interface and cause a burden on the implementation of the RU due to the inclusion of a large number of PHY processing blocks within the RU. Therefore, appropriate functional separation may be required depending on the arrangement and implementation method of the DU and the RU.

[0086] In one embodiment, if the precoding of data received from the DU cannot be processed (i.e., if the precoding capability of the RU is limited), the third functional separation (420a) or a lower functional separation (e.g., the second functional separation (410)) may be applied. Conversely, if the DU has the capability to process the precoding of data received from the DU, the fourth functional separation (420b) or a higher functional separation (e.g., the sixth functional separation (430)) may be applied.

[0087] Hereinafter, embodiments in the present disclosure are described based on the third functional separation (420a) (which may be referred to as category A (CAT-A)) or the fourth functional separation (420b) (which may be referred to as category B (CAT-B)) for performing beamforming processing in an RU unless otherwise specified. The O-RAN standard distinguishes the types of O-RUs depending on whether the precoding function is located at the interface of the O-DU or the O-RU interface. An O-RU that does not perform precoding (i.e., has low complexity) may be referred to as a CAT-A O-RU. An O-RU that performs precoding may be referred to as a CAT-B O-RU.

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

[0089] Embodiments of the present disclosure exemplarily describe the standards of eCPRI and O-RAN as fronthaul interfaces when transmitting messages between a DU (e.g., DU (210) of FIG. 2a) and an RU (e.g., RU (220) of FIG. 2a). The Ethernet payload of the message may include an eCPRI header, an O-RAN header, and additional fields. Hereinafter, various embodiments of the present disclosure are described using standard terms of eCPRI or O-RAN, but other expressions having equivalent meanings to each term may be used instead in various embodiments of the present disclosure. Hereinafter, various embodiments of the present disclosure are described using standard terms of eCPRI or O-RAN, but are not limited thereto. For example, in various embodiments of the present disclosure, the CPRI standard may be used as the fronthaul interface.

[0090] The fronthaul transport protocol can use Ethernet and eCPRI, which are easy to share with networks. The Ethernet payload can include an eCPRI header and an O-RAN header. The eCPRI header can be located at the beginning of the Ethernet payload. The contents of the eCPRI header are as follows.

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

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

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

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

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

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

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

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

[0099] 1) DU_port ID: The DU_port ID is used to distinguish processing units (e.g., different baseband cards) in the O-DU. The O-DU is expected to allocate bits for the DU_port ID, and the O-RU is expected to append the same value to the UL U-plane message carrying the same sectionId data.

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

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

[0102] 4) RU_port ID: The RU_port ID specifies logical flows such as data layer or spatial streams, and signaling channels that require separate numerologies (e.g. PRACH) or special antenna allocation such as SRS.

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

[0104] The control plane may be configured to provide scheduling information and beamforming information via control messages. The control plane refers to real-time control between DUs and RUs. The user plane may include IQ sample data transmitted between DUs and RUs. The user plane may include user downlink data (IQ data or SSB / RS), uplink data (IQ data or SRS / RS), or PRACH data. A weight vector of the beamforming information described above may be multiplied by the user's data. The synchronization plane generally refers to traffic between DUs and RUs for a synchronization controller (e.g., IEEE grand master). The synchronization plane may be related to timing and synchronization. The management plane refers to non-real-time control between DUs and RUs. The management plane may be related to initial setup, non-realtime reset or reset, and non-realtime report.

[0105] Control plane messages, or C-plane messages, can be encapsulated based on a two-layer header approach. The first layer can consist of the eCPRI common header or the IEEE 1914.3 common header, which contains fields used to indicate the message type. The second layer is the application layer, which contains fields necessary for control and synchronization. Within the application layer, sections define the characteristics of U-plane data transmitted or received on a beam with a single pattern ID. The following section types are supported within the C-plane:

[0106] Section Type can indicate the purpose of control messages transmitted on the control plane. For example, the purposes of each Section Type are as follows.

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

[0108] 2) sectionType=1: Used for most DL / UL wireless channels. Here, "most" refers to channels that do not require time or frequency offsets, such as those required for mixed numerology channels.

[0109] 3) sectionType=2: reserved for further use

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

[0111] 5) sectionType=4: reserved for further use

[0112] 6) sectionType=5: UE scheduling information. Transmits UE scheduling information so that the RU can perform real-time BF weight calculations (O-RAN optional BF method).

[0113] 7) sectionType=6: Transmits UE-specific channel information. Periodically transmits UE channel information to enable the RU to perform real-time BF weight calculations (O-RAN optional BF method).

[0114] 8) sectionType=7: Used for LAA support

[0115] According to one embodiment, a control plane (C-plane) message (hereinafter, C-plane message) may include section information and / or section extension information. The section information may be configured based on one of a plurality of section types. The section extension information may be configured based on one of a plurality of section extension types. For example, the section information may include a beam identifier (ID) for one port and / or information about a resource region for the section. The section extension information may include information about a group configuration for a plurality of ports.

[0116] In Fig. 5, an example of section information of a C-plane message, which includes a beam identifier (ID) for one port and / or information about a resource area for a section, will be described. In Figs. 6a and 6b, an example of section extension information of a C-plane message, which includes information about a group configuration for multiple ports, will be described.

[0117] Figure 5 shows an example of section information of a C-plane message.

[0118] Referring to FIG. 5, section information (530) of a C-plane message (500) may include a beam identifier (ID) for one port and / or information about a resource area for the section. Section information (530) including a beam identifier (ID) for one port and / or information about a resource area for the section may be included in a C-plane message (500) configured based on one section type among a plurality of section types (e.g., section types 1, 3, and 5).

[0119] In FIG. 5, an example is described in which section information (530) including a beam identifier (ID) for one port and / or information on a resource area for a section is included in a C-plane message (500) configured based on section type 1, but is not limited thereto. For example, section information (530) including a beam identifier (ID) for one port and / or information on a resource area for a section may be included in a C-plane message configured based on one of a plurality of section types (e.g., section types 1 to 8).

[0120] Referring to FIG. 5, a C-plane message (500) may include transport header (e.g., eCPRI header or IEEE 1914.3) information (510), common header information (520), section information (530), and section extension information (540). The transport header may include 'ecpriVersion', 'ecpriReserved', 'ecpriConcatenation', 'ecpriMessage', 'ecpriPayload', 'ecpriRtcid / ecpriPcid', and 'ecpriSeqid', as described above.

[0121] Common header information (520) may include 'dataDirection' indicating the data transmission direction of the base station (e.g., gNB), 'payloadVersion' indicating the valid payload protocol version of IEs in the application layer, and 'filterindex' indicating the index for the channel filter between IQ data and the air interface to be used in both DL and UL.

[0122] The common header information (520) may include information indicating the location of a time resource to which a message is applicable. The location of the time resource may be indicated by a frame, a subframe, a slot, or a symbol. The common header information (520) may include 'frameId' indicating a frame number, 'subframeId' indicating a subframe number, 'slotId' indicating a slot number, and 'startSymblId' indicating a symbol number. A frame is determined based on a 256 modulo operation. A subframe has a unit of 1 ms included in a 10 ms frame. Slot numbers are numbered within a subframe, and the maximum size may be 1, 2, 4, 8, or 16 depending on the numerology.

[0123] The common header information (520) may include 'numberOfsections' indicating the number of data sections (hereinafter, 'sections') included in the C-plane message. The common header information (520) may include 'sectionType' determining the characteristics of the C-plane data. According to one embodiment, the 'sectionType' of the common header information (520) may indicate 1. However, the section type indicating 1 is only one embodiment, and does not mean that the section extension type information (540) according to the embodiments of the present disclosure cannot be applied to other section types (2, 3, 4, ...).

[0124] Section information (530) is layer-specific information and may include information about resources allocated in one slot (e.g., 14 symbols). In the C-plane and U-plane, a section may refer to an area to which resources are allocated. For example, one section may represent a resource area for N RBs in the frequency domain (e.g., N is 1 to 273 according to the current NR standard) and M symbols in the time domain (e.g., N is 1 to 14 according to the current NR standard) in a resource grid expressed as time-frequency resources.

[0125] The section information (530) may include 'sectionId' which means a section identifier. The section information (530) may include 'rb' which indicates whether every RB is used or every other RB is used, 'symInc' which indicates a symbol number increment command, 'startPrbc' which indicates a starting PRB number of a data section description, 'numPrbc' which indicates the number of consecutive PRBs per data section description, 'reMask' which defines an RE mask within a PRB, 'numSymbol' which defines the number of PRACH (physical random access channel) repetitions or the number of symbols to which section control is applied, 'ef' which indicates an extension flag, and 'beamId' which defines a beam pattern to be applied to U-plane data. For example, as the value of 'ef' is set to 1, section extension information (540) may be included in the C-plane message (500). The section extension information (540) may be selectively included in the C-plane message (500) depending on the value of 'ef'.

[0126] For example, section extension information (540) may include information on group configuration for multiple ports. Section extension information (540) may be configured based on at least one section extension type among multiple section extension types. As an example, section extension information (540) may be configured based on section extension type 10. An example of section extension information (540) of a C-plane message including information on group configuration for multiple ports will be described below in FIGS. 6A and 6B .

[0127] Figures 6a and 6b illustrate examples of section extension information of a C-plane message, which includes information about group configuration for multiple ports.

[0128] Referring to FIGS. 6A and 6B , section extension information (540) of a C-plane message may include information regarding group configuration for multiple ports. Section extension information (540) may be configured for group configuration for multiple ports. Section extension information (540) including information regarding group configuration for multiple ports may be configured based on one of a plurality of section extension types (e.g., section extension types 1 to 23).

[0129] In FIGS. 6A and 6B, an example is described in which section extension information (540) including information on group configuration for multiple ports is configured based on section extension type 10, but is not limited thereto. Section extension information (540) including information on group configuration for multiple ports may also be configured based on one (or at least one) of a plurality of section extension types (e.g., section extension types 1 to 23).

[0130] Referring to FIGS. 6A and 6B , the section extension information (540) may include 'extType', which provides an extension type that provides additional parameters. The section extension information (540) may include 'ef', which indicates whether there is another extension present or whether the current extension field is the last extension. The section extension information (540) may include 'extLen', which provides the length of the section extension in units of 32-bit (or 4-byte) words.

[0131] For example, the section extension information (540) may include 'beamGroupType' indicating the type of beam grouping. 'beamGroupType' may be composed of 2 bits. When 'beamGroupType' is set to '00' (or '00b', '0') or '01' (or '01b', '1'), the section extension information (540) may be composed as in Fig. 6a. When 'beamGroupType' is set to '10' (or '10b', '2'), the section extension information (540) may be composed as in Fig. 6b.

[0132] Referring to FIG. 6a, the section extension information (540) may include 'numPortc' indicating the number of eAxC ports indicated by the section extension.

[0133] For example, if 'beamGroupType' is set to '00' (or '00b', '0'), 'BeamID' included in section information (e.g., section information (530) of FIG. 5) (or section header) can be used as a common beam identifier for all ports according to 'numPortc' grouped into M-Plane.

[0134] For example, if 'beamGroupType' is set to '01' (or '01b', '1'), the beam identifiers of consecutive 'numPortc' following 'BeamID' included in the section information (e.g., section information (530) of FIG. 5) (or section header) can be applied to the ports according to 'numPortc'.

[0135] Referring to Fig. 6b, when 'beamGroupType' is set to '10' (or '10b', '2'), the section extension information (540) is a beam identifier for ports according to 'numPortc' (e.g., '2 nd port beamId' or '(numPortc+1)th port beamID' (or terminal identifier ('ueId')).

[0136] Referring to FIGS. 6A and 6B, when section extension information (540) is not used, section information (e.g., section information (530) of FIG. 5) included in a C-plane message (e.g., section information (530) of FIG. 5) can designate one endpoint (or port, terminal). DU (210) can receive one U-plane message using the C-plane message. In order to designate multiple endpoints (or multiple ports, multiple terminals) through a C-plane message including the same information, DU (210) must repeatedly transmit the same information to RU (220). To prevent repetitive operations, section extension information (540) can be transmitted. Section extension information (540) specifies the number of endpoints (or ports or terminals) to be added through 'numPortc', and section extension information (540) can indicate a beam identifier ('beamID') or terminal identifier ('ueID') corresponding to the endpoints (or ports or terminals) to be added.

[0137] A beam identifier and / or a terminal identifier to be applied to a plurality of end points (or, a plurality of ports, a plurality of terminals) may be indicated through section extension information (540). For a plurality of end points (or, a plurality of ports, a plurality of terminals), 'rb', 'symInc', 'startPrbc', 'numPrbc', 'reMask', and / or 'numSymbol' indicated by section information (e.g., section information (530) of FIG. 4)) may be set identically. Scheduling information transmitted to a terminal connected to the RU (220) may be transmitted through a PDCCH. Scheduling information for a PUSCH that can be processed by a base station (e.g., DU (210) and RU (220)) may be transmitted to the terminal.

[0138] In the case of terminals scheduled based on MU-MIMO (multiple user - multiple input multiple output), 'startPrbc' and 'numPrbc' of each terminal may be set differently. In this case, the C-plane message may not be optimized through the existing section extension information (540). The DU (210) may set 'startPrbc' and 'numPrbc' of each terminal differently by transmitting multiple C-plane messages including section information to the RU (220). However, the RU (220) must perform the MU-MIMO combining operation based on combining all of the multiple C-plane messages. However, if the C-plane message deviates from the Ethernet standard payload, packet segmentation may occur, making the combining operation impossible.

[0139] In addition, the C-plane message (500) may include basic information about the processing value of the DL PHY level signal that the RU (220) must transmit to the terminal and basic information about the processing value of the UL PHY level signal that the RU (220) must transmit to the DU (210). The RU (220) may transmit the I (in-phase) value and the Q (quadrature-phase) value of the uplink received from the terminal to the DU (210). Since the DU (210) operates based on at least some of the I values ​​and Q values ​​received from the RU (220), the transmission area of ​​the terminal and the operating area of ​​the RU (220) may not match.

[0140] When at least one function related to uplink performance improvement (ULPI) is performed in the RU (220), the RU (220) may not know the exact RB size of the uplink signal (e.g., PUSCH) of the terminal. In addition, the RU (220) may not be able to perform the MU-MIMO function through differential RB. In the following specification, examples of the operations of the DU (210) and the RU (220) for receiving an uplink signal when at least one function related to ULPI is performed in the RU (220) will be described. First, the operations of the DU (210) and the RU (220) for ULPI will be described later with reference to FIGS. 7A and 7B.

[0141] Figure 7a illustrates an example of the operation of RU and DU in Class A.

[0142] FIG. 7A illustrates an example (700) of a method in which an RU (220) processes a demodulation reference signal (DMRS) in class A and provides the processed information to a DU (210). For example, class A may represent an example of functional separation in which DMRS processing is performed in the RU (220). Class A may be referred to as uplink performance improvement (ULPI) class A or DMRS beamforming-equalizing (DMRS BF-EQ). For example, the DMRS processing may include extraction, channel estimation, and weight calculation for the uplink DMRS.

[0143] Referring to example (700), when using the above class A, the RU (220) can perform FFT (fast Fourier transform) (720), SRS extraction (sounding reference signal extraction) (721), SRS channel estimation (722), SRS beamforming weight calculation (723), DMRS extraction (724), DMRS channel estimation (725), DMRS weight calculation (726), beamforming (727), equalizing (728), and channel information-based BFW calculation (729). In example (700), operations (or functions) such as FFT (720), SRS extraction (721), SRS channel estimation (722), SRS BFW calculation (723), DMRS extraction (724), DMRS channel estimation (725), DMRS weight calculation (726), beamforming (727), equalizing (728), and channel information-based BFW calculation (729) are depicted, but the RU (220) may be implemented based on hardware, software, or a combination of hardware and software to perform the above operations.

[0144] Referring to example (700), RU (220) can perform FFT (720) on an uplink signal received through an uplink channel. For example, RU (220) can perform FFT (720) on the uplink signal received from terminal (120). RU (220) can determine a signal (y) associated with antenna elements based on FFT (720). rx ) can be obtained. For example, the uplink channel may include a physical uplink shared channel (PUSCH). For example, the uplink signal may include an SRS or a DMRS.

[0145] For example, RU (220) is a signal (y rx ) can perform SRS extraction (721). For example, RU (220) can perform SRS extraction (721) on SRS (y SRS ) can perform SRS channel estimation (722). RU (220) generates a channel estimation matrix (H) based on the SRS channel estimation (722). SRS ) can be obtained. RU (220) is a channel estimation matrix (H SRS ) can perform SRS BFW calculation (723). RU (220) generates a matrix (W) representing the concatenation of beamforming weight vectors (e.g., N) based on the SRS BFW calculation (723). SRS )(NxK) can be obtained. The above K can represent the number of antenna elements of the RU (220).

[0146] For example, RU (220) is a signal (y rx ) and matrix (W SRS ) can perform DMRS extraction (724). For example, RU (220) can perform DMRS extraction (y`) based on DMRS extraction (724). dmrs ) can be obtained. While performing DMRS extraction (724), the RU (220) may also perform dimension reduction. For example, the dimension reduction may be referred to as port reduction, pre-reduction, or pre-dimension reduction. Based on the dimension reduction, the order (or value) (e.g., K) of the dimension corresponding to the antenna elements of the RU (220) may be reduced. For example, the RU (220) may obtain the extracted DMRS (y` dmrs ), DMRS channel estimation (725) can be performed. RU (220) generates a channel estimation matrix (H) based on DMRS channel estimation (725). dmrs) can be obtained. RU (220) is a channel estimation matrix (H dmrs ) can perform DMRS weight calculation (726). RU (220) can perform a matrix (W`) representing the concatenation of beamforming weight vectors (L) based on DMRS weight calculation (726). dmrs )(LxK) and a matrix (W`) representing the normalization weight matrix of the IQ data within each layer. eq )(LxL) can be obtained.

[0147] For example, RU (220) can perform beamforming (727). For example, RU (220) can perform matrix (W SRS ) and matrix (W` dmrs )(LxK) based on the signal (y rx ) can perform beamforming (727). The RU (220) performs beamforming based on the beamforming (727) signal (y bf ) can be obtained. At this time, the matrix (W SRS ) can be obtained based on SRS BFW calculation (723), SRS BFW calculation (714), or channel information-based BFW calculation (729). For example, channel information-based BFW calculation (729) can be performed by RU (220). For example, SRS BFW calculation (714) can be performed by DU (210). For example, RU (220) can obtain matrix (W`) eq ), based on the signal (y bf ) can perform equalization (728). The RU (220) can perform equalization (728) on the signal (y eq ) can be obtained. For example, RU (22) can obtain a signal (y eq ) can be provided (or transmitted) to DU (210). Signal (y eq ) may be referenced as an uplink message. For example, the uplink message may be a calculated SINR (SINR yeq) may contain information about.

[0148] Referring to example (700), when using the above class A, DU (210) can perform layer demapping (711), demodulation and decoding (712), SRS channel estimation (713), and SRS BFW calculation (714). Although example (700) shows operations (or functions) such as layer demapping (711), demodulation and decoding (712), SRS channel estimation (713), and SRS BFW calculation (714), DU (210) can be implemented based on hardware, software, or a combination of hardware and software to perform the above operations.

[0149] Referring to example (700), DU (210) receives (or acquires) a signal (y) from RU (220). eq ) can perform layer demapping (711). DU (210) compares the result of layer demapping (711) with SINR (SINR yeq ) can perform demodulation and decoding (712). In addition, the DU (210) can perform the extracted SRS (y SRS ) can perform SRS channel estimation (713). The DU (210) can perform channel estimation matrix (H) based on the SRS channel estimation (713). SRS ) can be obtained. After this, DU (210) can perform scheduling through a scheduler.

[0150] Figure 7b illustrates an example of the operation of RU and DU in Class B.

[0151] FIG. 7B illustrates an example (750) of a method for providing information on how DMRS processing is performed in RU (220) and DU (210) in Class B. For example, Class B may represent an example of functional separation in which DMRS processing is performed in RU (220) and DU (210). Class B may be referred to as uplink performance improvement (ULPI) Class B or DMRS beamforming-nonequalizing (DMRS BF-NEQ). For example, the DMRS processing may include extraction, channel estimation, and weight calculation for uplink DMRS.

[0152] Referring to example (750), when using the above class B, the RU (220) can perform FFT (fast Fourier transform) (770), SRS extraction (sounding reference signal extraction) (771), SRS channel estimation (772), SRS beamforming weight calculation (773), DMRS extraction (774), DMRS channel estimation (775), DMRS weight calculation (776), beamforming (777), and channel information-based BFW calculation (778). In example (700), operations (or functions) such as FFT (770), SRS extraction (771), SRS channel estimation (772), SRS BFW calculation (773), DMRS extraction (774), DMRS channel estimation (775), DMRS weight calculation (776), beamforming (777), and channel information-based BFW calculation (778) are depicted, but the RU (220) may be implemented based on hardware, software, or a combination of hardware and software to perform the above operations.

[0153] Referring to example (750), RU (220) can perform FFT (770) on an uplink signal received through an uplink channel. For example, RU (220) can perform FFT (770) on the uplink signal received from terminal (120). RU (220) can determine a signal (y) associated with antenna elements based on FFT (770). rx ) can be obtained. For example, the uplink channel may include a physical uplink shared channel (PUSCH). For example, the uplink signal may include an SRS or a DMRS.

[0154] For example, RU (220) is a signal (y rx) can perform SRS extraction (771). For example, RU (220) can perform SRS extraction (771) on SRS (y SRS ) can perform SRS channel estimation (772). The RU (220) generates a channel estimation matrix (H) based on the SRS channel estimation (772). SRS ) can be obtained. RU (220) is a channel estimation matrix (H SRS ) can perform SRS BFW calculation (773). RU (220) generates a matrix (W) representing the concatenation of beamforming weight vectors (e.g., N) based on the SRS BFW calculation (773). SRS )(NxK) can be obtained. The above K can represent the number of antenna elements of the RU (220).

[0155] For example, RU (220) is a signal (y rx ) and matrix (W SRS ) can perform DMRS extraction (774). For example, RU (220) can perform DMRS extraction (y`) based on DMRS extraction (774). dmrs ) can be obtained. While performing DMRS extraction (774), the RU (220) may also perform dimension reduction. For example, the dimension reduction may be referred to as port reduction, pre-reduction, or pre-dimension reduction. Based on the dimension reduction, the order (or value) (e.g., K) of the dimension corresponding to the antenna elements of the RU (220) may be reduced. For example, the RU (220) may obtain the extracted DMRS (y` dmrs ), DMRS channel estimation (775) can be performed. RU (220) can perform channel estimation matrix (H) based on DMRS channel estimation (775). dmrs ) can be obtained. RU (220) is a channel estimation matrix (H dmrs) can perform DMRS weight calculation (776). RU (220) can perform a matrix (W`) representing the concatenation of beamforming weight vectors (L) based on DMRS weight calculation (776). dmrs )(LxK) can be obtained.

[0156] For example, RU (220) can perform beamforming (777). For example, RU (220) can perform matrix (W SRS ) and matrix (W` dmrs )(LxK) based on the signal (y rx ) can perform beamforming (777). The RU (220) performs beamforming based on the beamforming (777) signal (y bf ) can be obtained. At this time, the matrix (W SRS ) can be obtained based on SRS BFW calculation (773), SRS BFW calculation (769), or channel information-based BFW calculation (779). For example, channel information-based BFW calculation (779) can be performed by RU (220). For example, SRS BFW calculation (769) can be performed by DU (210). For example, RU (220) can obtain signal (y bf ) can be provided (or transmitted) to DU (210). Signal (y bf ) may be referenced as an uplink message. For example, the uplink message may be a calculated SINR (SINR yeq ) may contain information about.

[0157] Referring to example (750), when using the above class B, the DU (210) can perform DMRS extraction (761), DMRS channel estimation (762), DMRS weight calculation (763), combining (764), equalizing (765), layer demapping (766), demodulation and decoding (767), SRS channel estimation (768), and SRS BFW calculation (769). In example (750), operations (or functions) such as DMRS extraction (761), DMRS channel estimation (762), DMRS weight calculation (763), combining (764), equalizing (765), layer demapping (766), demodulation and decoding (767), SRS channel estimation (768), and SRS BFW calculation (769) are depicted, but the DU (210) may be implemented based on hardware, software, or a combination of hardware and software to perform the above operations.

[0158] For example, DU(210) is a signal (y bf ) can perform DMRS extraction (761). For example, DU (210) can perform DMRS extraction (y) based on DMRS extraction (761). dmrs ) can be obtained. For example, DU (210) can obtain the extracted DMRS (y dmrs ), DMRS channel estimation (762) can be performed. DU (210) can perform channel estimation matrix (H) based on DMRS channel estimation (762). dmrs ) can be obtained. DU (210) is a channel estimation matrix (H dmrs ) can perform DMRS weight calculation (763). DU (210) generates a matrix (W) representing a normalization weight matrix of IQ data based on DMRS weight calculation (763). eq )(LxL) and the matrix (W`) where spatial streams (M+N) are mapped to layers (L).comb )(Lx(M+N)) can be obtained. For example, DU(210) is a matrix (W` comb ) based on the signal (y bf ) can perform a combination (764). The DU (210) can obtain a signal ( ) of the non-equalized layer streams (M) based on the combination (764). For example, the DU (210) can obtain a signal ( ) of the matrix (W eq ), based on the signal (y comb ) can perform equalization (765). The DU (210) can perform equalization (765) on the signal (y eq ) and SINR (SINR yeq ) can be obtained. For example, DU (210) can obtain a signal (y eq ) can perform layer demapping (766). DU (210) compares the result of layer demapping (766) with SINR (SINR yeq ) can perform demodulation and decoding (767). In addition, the DU (210) can perform the extracted SRS (y SRS ) can perform SRS channel estimation (768). The DU (210) can perform channel estimation matrix (H) based on the SRS channel estimation (768). SRS ) can be obtained. After this, DU (210) can perform scheduling through a scheduler.

[0159] Figure 8 illustrates an example of the operation of DU and RU for receiving an uplink signal.

[0160] Referring to FIG. 8, the DU (210) and the RU (220) may be configured through class A and / or class B as illustrated in FIGS. 7a and 7b. For example, the RU (220) configured through class A and / or class B may perform channel estimation for uplink. The DU (210) and the RU (220) configured through class A and / or class B may receive uplink signals through operations 801 to 805.

[0161] In operation 801, DU (210) can transmit a C-plane message to RU (220). RU (220) can receive a C-plane message from DU (210).

[0162] According to one embodiment, the DU (210) may generate a C-plane message. The C-plane message may include section information for indicating a resource region (e.g., section information (530) of FIG. 5) and section extension information (e.g., section extension information (540) of FIGS. 5, 6A, and 6B). For example, the C-plane message may indicate a resource allocation region for each port among multiple ports for group configuration within the resource region. For example, at least one of the section information and the section extension information may indicate a resource allocation region for each port among multiple ports for group configuration within the resource region. For example, the section information may indicate a resource allocation region for each port among multiple ports for group configuration within the resource region. For example, the section extension information may indicate a resource allocation region for each port among multiple ports for group configuration within the resource region.

[0163] Section information may include information on the number of a plurality of resource blocks (e.g., PRBs (physical resource blocks)) constituting a resource area (e.g., 'numPrbc') and information for indicating a start resource block of the plurality of resource blocks (e.g., 'startPrbc').

[0164] According to one embodiment, a C-plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among a plurality of resource blocks. For example, the information for indicating at least one resource block may include an indicator configured based on the number of at least one resource block and the starting resource block of the at least one resource block. Specific examples of an indicator configured based on the number of at least one resource block and the starting resource block of the at least one resource block will be described later with reference to FIGS. 9A, 9B, and / or 14.

[0165] According to one embodiment, a C-plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among a plurality of resource blocks. The information for indicating at least one resource block may include information about the number of at least one resource block and information about a starting resource block of the at least one resource block. The C-plane message may further include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on the plurality of resource blocks. Specific examples of the information about the number of at least one resource block, the information about the starting resource block of the at least one resource block, and / or the information for indicating at least one resource group will be described later with reference to FIGS. 10A, 10B, 10C, 10D, and / or 15.

[0166] According to one embodiment, a C-plane message may include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on a plurality of resource blocks, and information for indicating resource blocks for each of the plurality of resource groups. Specific examples of the information for indicating at least one resource group constituting a resource allocation area for one port and the information for indicating resource blocks for each of the plurality of resource groups will be described later with reference to FIGS. 11A, 11B, and / or 16.

[0167] In operation 802, the RU (220) may transmit scheduling information to at least one terminal (800). For example, the scheduling information may be transmitted to at least one terminal (800) via downlink control information (DCI). At least one terminal (800) may identify a resource allocation region for an uplink signal based on the scheduling information.

[0168] In operation 803, at least one terminal (800) may transmit uplink signal(s) to the RU (220). For example, each of the at least one terminal (800) may transmit uplink signal(s) to the RU (220) based on a resource allocation region identified based on scheduling information. The RU (220) may receive uplink signal(s) from each of the at least one terminal (800). For example, each of the uplink signal(s) may include a demodulation-reference signal (DMRS). The DMRS may be used for channel estimation.

[0169] In operation 804, the RU (220) may perform channel estimation based on an uplink signal received from at least one terminal (800) through an uplink channel in operation 802.

[0170] According to one embodiment, the RU (220) may identify a resource allocation region allocated to at least one terminal (800) (or each of multiple ports) based on a C-plane message. For example, a resource region may be allocated to at least one terminal (800) (or multiple ports). Among the resource regions, a resource allocation region may be allocated for one terminal among at least one terminal (800) (or multiple ports). The RU (220) may perform channel estimation for the resource allocation region. The RU (220) may perform channel estimation for at least one resource allocation region included in the resource region.

[0171] At operation 805, the RU (220) may transmit a U-plane message to the DU (210). The U-plane message may include information about the uplink signal received by operation 803.

[0172] As described above, in order for the RU (220) to perform channel estimation for an uplink channel for at least one terminal (800), the RU (220) must receive information about a resource allocation region for each of at least one terminal (800) (or endpoint) from the DU (210). Therefore, in the following specification, a specific example in which information about a resource allocation region for each of at least one terminal (800) (or endpoint) is included in a C-plane message will be described.

[0173] Figure 9a illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0174] Referring to FIG. 9a, the C-plane message may include section information and section extension information for indicating a resource region. For example, the section information may include information for indicating the number of resource blocks constituting the resource region (e.g., 'numPrbc' in FIG. 5) and information for indicating the starting resource block of the resource blocks (e.g., 'startPrbc' in FIG. 5).

[0175] According to one embodiment, the C-plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among a plurality of resource blocks.

[0176] For example, a C-plane message may contain information about n ports. Although not illustrated, the C-plane message may contain 'numPortc'. 'numPortc' may indicate the number of ports added to one port. For example, if the value of 'numPortc' is 1, the C-plane message may contain information about 2 ports. For example, if the value of 'numPortc' is 3, the C-plane message may contain information about 4 ports.

[0177] For example, a C-plane message may include information about a first port (910-1) to information about an n-th port (910-n). Each of the information about the first port (910-1) to information about the n-th port (910-n) may include a beam identifier ('beamid') (or terminal identifier ('ueid')) assigned to the corresponding port and / or an indicator ('prbIndication') for indicating at least one resource block. The indicator ('prbIndication') for indicating at least one resource block may be configured based on the number of at least one resource block and a starting resource block of at least one resource block.

[0178] For example, information about the first port (910-1) is a beam identifier (920-1) assigned to the first port ('1 st port beamid'). Information about the first port (910-1) may include an indicator (930-1) ('1) for indicating at least one resource block for the first port. st port prbIndication'). The indicator (930-1) may be configured based on the number of at least one resource block for the first port and the starting resource block of the at least one resource block.

[0179] For example, information about the nth port (910-1) is the beam identifier (920-n) assigned to the nth port ((numPortc+1) th port beamid). Information about the nth port (910-n) may include an indicator (930-n) ('(numPortc+1)) for indicating at least one resource block for the nth port. th port prbIndication'). The indicator (930-n) may be configured based on the number of at least one resource block for the nth port and the starting resource block of the at least one resource block.

[0180] For example, the beam identifiers (920-1 to 920-n) (or terminal identifiers) included in each of the information about the first port (910-1) to the information about the n-th port (910-n) may be composed of 15 bits. The indicators (930-1 to 930-n) included in each of the information about the first port (910-1) to the information about the n-th port (910-n) may be composed of 8 bits.

[0181] According to one embodiment, at least some of the information about the first port (910-1) to the information about the n-th port (910-n) may be included in the section information. The remaining some of the information about the first port (910-1) to the information about the n-th port (910-n) may be included in the section extension information.

[0182] For example, the beam identifier (920-1) assigned to the first port may be included in the section information. The remaining information, excluding the beam identifier (920-1) assigned to the first port, among the information about the first port (910-1) to the information about the n-th port (910-n), may be included in the section extension information. An example in which the remaining information, excluding the beam identifier (920-1) assigned to the first port, among the information about the first port (910-1) to the information about the n-th port (910-n), is included in the section extension information will be described later in FIG. 9B.

[0183] For example, information about the first port (910-1) may be included in the section information. Information about the second port (910-2) to information about the nth port (910-n) may be included in the section extension information.

[0184] Specific examples of indicators (e.g., indicators (930-1) to (930-n)) configured based on the number of at least one resource block and the starting resource block of said at least one resource block will be described later in FIGS. 12A and 12B.

[0185] According to one embodiment, in FIG. 9A, information about the first port (910-1) to information about the n-th port (910-n) are illustrated as being configured sequentially, but this is for convenience of explanation and is not limited thereto. Information about the first port (910-1) to information about the n-th port (910-n) may be included in various forms (e.g., discontinuous forms) within the C-plane message. Depending on the embodiment, at least some or all of information about the first port (910-1) to information about the n-th port (910-n) may be explicitly or implicitly included within the C-plane message.

[0186] Figure 9b illustrates an example of section extension information for indicating resource allocation areas for each of a plurality of ports.

[0187] Referring to FIG. 9B, the section extension information may include at least some of the information illustrated in FIG. 9A. For example, the section extension information may include some of the information regarding the first port. The section extension information may include information regarding the second port (910-2) to information regarding the nth port (910-n).

[0188] For example, the section extension information may include an indicator (930-1) ('1) for indicating at least one resource block for the first port among the information (910-1) regarding the first port of FIG. 9a. st The section extension information may include all of the information about the second port (910-2) to the information about the nth port (910-n) of FIG. 9A.

[0189] Section extension information is the beam identifier (920-1) assigned to the first port among the information (910-1) regarding the first port of FIG. 9a ('1 stport beamid') may not be included. The beam identifier (920-1) assigned to the first port ('1 st port beamid') may be included in section information (e.g., section information (530) of FIG. 5). Since section extension information is indicated after the section information, the beam identifier (920-1) ('1) assigned to the first port among the information (910-1) regarding the first port st port beamid') may not be included.

[0190] According to one embodiment, the section extension information illustrated in FIG. 9b may be configured based on section extension type 10. An example of a C-plane message including section extension information configured based on section extension type 10 will be described below in FIG. 14.

[0191] Figure 10a illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0192] Figure 10b illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0193] Referring to FIGS. 10A and 10B , the C-plane message may include section information and section extension information for indicating a resource region. For example, the section information may include information for indicating the number of resource blocks constituting the resource region (e.g., 'numPrbc' in FIG. 5 ) and information for indicating a starting resource block of the resource blocks (e.g., 'startPrbc' in FIG. 5 ).

[0194] According to one embodiment, the C-plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among a plurality of resource blocks. The information for indicating at least one resource block may include information about the number of at least one resource block and information about a starting resource block of the at least one resource block. The C-plane message may further include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on the plurality of resource blocks.

[0195] For example, a C-plane message may contain information about n ports. Although not illustrated, the C-plane message may contain 'numPortc'. 'numPortc' may indicate the number of ports added to one port. For example, if the value of 'numPortc' is 1, the C-plane message may contain information about 2 ports. For example, if the value of 'numPortc' is 3, the C-plane message may contain information about 4 ports.

[0196] According to one embodiment, information about n ports included in a C-plane message may include 'RBGenable' indicating whether a resource allocation area is indicated based on multiple resource groups. If 'RBGenable' is set to a first value (e.g., '0'), a resource allocation area may not be indicated based on multiple resource groups. If 'RBGenable' is set to a second value (e.g., '1'), a resource allocation area may be indicated based on multiple resource groups.

[0197] For example, if the resource allocation area is continuous, the value of 'RBGenable' may be set to a first value (e.g., '0'). If the resource allocation area is discontinuous, the value of 'RBGenable' may be set to a second value (e.g., '1').

[0198] Referring to FIG. 10A, an example of information included in a C-plane message is illustrated when the value of information (1020-1, ... 1020-n) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups is the first value (e.g., '0'). In FIG. 10A, for convenience of explanation, an example is illustrated in which the value of information (1020-1, ... 1020-n) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups is set to the first value in all of the first to n-th ports, but the present invention is not limited thereto. In at least one port among the first to n-th ports, a resource allocation area may not be indicated based on multiple resource groups.

[0199] Referring to FIG. 10b, an example of information included in a C-plane message is illustrated when the value of information (1062-1, ... 1062-n) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups is a second value (e.g., '1'). For convenience of explanation in FIG. 10b, an example is illustrated in which the value of information (1062-1, ... 1062-n) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups is set to the second value in all of the first to n-th ports, but the present invention is not limited thereto. A resource allocation area may be indicated based on multiple resource groups only in at least one port among the first to n-th ports.

[0200] First, referring to FIG. 10A, for example, a C-plane message may include information about a first port (1010-1) to information about an n-th port (1010-n). Each of the information about the first port (1010-1) to information about the n-th port (1010-n) may include a beam identifier ('beamid') (or terminal identifier ('ueid')) assigned to the corresponding port, information for indicating the number of at least one resource block assigned to the corresponding port, and / or information for indicating a starting resource block of at least one resource block assigned to the corresponding port.

[0201] For example, information (1010-1) regarding the first port includes information (1020-1) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups, information (1021-1) (RBGUnit) for indicating a unit of multiple resource groups, and information (1022-1) ('1) for indicating a starting resource block of at least one resource block allocated to the first port. st port startPrbcPerPort'), information for indicating the number of at least one resource block allocated to the first port (1023-1)('1 st port numPrbcPerPort'), and / or the beam identifier (1024-1) assigned to the first port ('1st port beamid') (or terminal identifier).

[0202] For example, information (1010-n) about the nth port includes information (1020-n) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups, information (1021-n) ('RBGUnit') for indicating a unit of multiple resource groups, and information (1022-n) ('(numPortc+1)) for indicating a starting resource block of at least one resource block allocated to the nth port. thport startPrbcPerPort'), information to indicate the number of at least one resource block allocated to the nth port (1023-n)('(numPortc+1) th port numPrbcPerPort'), and / or beam identifier (1024-n) assigned to the nth port ('(numPortc+1) th port beamid') (or terminal identifier).

[0203] Information (1021-1 to 1021-n) ('RBGUnit') for indicating the units of multiple resource groups may not be used. Depending on the embodiment, information (1021-1 to 1021-n) ('RBGUnit') for indicating the units of multiple resource groups may not be included in information (1010-1 to 1010-n) regarding multiple ports.

[0204] For example, information (1022-1 to 1022-n) ('startPrbcPerPort') for indicating a start resource block of at least one resource block allocated to one port may be composed of 10 bits. Information (1023-1 to 1023-n) for indicating the number of at least one resource block allocated to one port may be composed of 8 bits. Beam identifiers (1024-1 to 1024-n) allocated to one port may be composed of 15 bits.

[0205] According to one embodiment, at least some of the information about the first port (1010-1) to the information about the n-th port (1010-n) may be included in the section information. The remaining some of the information about the first port (1010-1) to the information about the n-th port (1010-n) may be included in the section extension information.

[0206] For example, the beam identifier (1024-1) assigned to the first port may be included in the section information. The remaining information, excluding the beam identifier (1024-1) assigned to the first port, among the information about the first port (1010-1) to the information about the n-th port (1010-n), may be included in the section extension information. An example in which the remaining information, excluding the beam identifier (1024-1) assigned to the first port, among the information about the first port (1010-1) to the information about the n-th port (1010-n), is included in the section extension information will be described later in FIG. 10c.

[0207] For example, information about the first port (1010-1) may be included in the section information. Information about the second port (1010-2) to information about the nth port (1010-n) may be included in the section extension information.

[0208] Referring to FIG. 10b, for example, the C-plane message may include information about the first port (1060-1) to information about the n-th port (1060-n). Each of the information about the first port (1060-1) to information about the n-th port (1060-n) may include a beam identifier ('beamid') (or terminal identifier ('ueid')) assigned to the corresponding port, and information for indicating at least one resource group assigned to the corresponding port among a plurality of resource groups.

[0209] For example, information (1060-1) about the first port may include a beam identifier (1061-1) ('1st port beamid') (or terminal identifier) ​​assigned to the first port, information (1062-1) ('RBGenable') for indicating whether a resource allocation area is indicated based on a plurality of resource groups, information (1063-1) (RBGUnit) for indicating a unit of the plurality of resource groups, and / or information (1064-1) ('1') for indicating at least one resource group assigned to the first port. st It may contain 'prbBitmap'.

[0210] For example, information about the nth port (1060-n) is the beam identifier (1061-n) assigned to the nth port ('(numPortc+1) th port beamid')(or terminal identifier), information (1062-n)('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups, information (1063-n)(RBGUnit) for indicating a unit of multiple resource groups, and / or information (1064-n)('(numPortc+1)) for indicating at least one resource group allocated to the nth port th It may contain 'prbBitmap'.

[0211] For example, information (1063-1 to 1063-n) ('RBGUnit') for indicating a unit of multiple resource groups can indicate at least one of 2, 4, 8, and 16. Information (1064-1 to 1064-n) for indicating at least one resource group allocated to one port can indicate at least one resource group among multiple resource groups configured according to information (1063-1 to 1063-n) for indicating a unit of multiple resource groups based on a bitmap.

[0212] For example, when information (1063-1 to 1063-n) for indicating units of multiple resource groups indicates 4, the multiple resource groups can be configured in 4RB units based on the start resource block ('startPrbc' in FIG. 5) of the multiple resource blocks. When information (1064-1 to 1064-n) for indicating at least one resource group assigned to one port is set to '0101', information (1064-1 to 1064-n) for indicating at least one resource group assigned to one port can indicate two areas of [startPrbc, startPrbc+4] and [startPrbC+8, startPrbC+12].

[0213] For example, beam identifiers (1061-1 to 1061-n) assigned to one port may consist of 15 bits. Information (1063-1 to 1063-n) for indicating units of multiple resource groups may consist of 2 bits. Information (1064-1 to 1064-n) for indicating at least one resource group assigned to one port may consist of 20 bits.

[0214] According to one embodiment, at least some of the information about the first port (1060-1) to the information about the n-th port (1060-n) may be included in the section information. The remaining some of the information about the first port (1060-1) to the information about the n-th port (1060-n) may be included in the section extension information.

[0215] For example, the beam identifier (1061-1) assigned to the first port may be included in the section information. The remaining information, excluding the beam identifier (1061-1) assigned to the first port, among the information about the first port (1060-1) to the information about the n-th port (1060-n), may be included in the section extension information. An example in which the remaining information, excluding the beam identifier (1061-1) assigned to the first port, among the information about the first port (1060-1) to the information about the n-th port (1060-n), is included in the section extension information will be described later in FIG. 10d.

[0216] For example, information about the first port (1060-1) may be included in the section information. Information about the second port (1060-2) to information about the nth port (1060-n) may be included in the section extension information.

[0217] In FIGS. 10A and 10B, the case where the value of 'RBGenable' is the first value and the case where the value of 'RBGenable' is the second value are illustrated, but the present invention is not limited thereto. Whether a resource allocation area is indicated based on multiple resource groups for each of a plurality of ports can be independently set. For example, a resource allocation area may not be indicated based on multiple resource groups in the first port, and a resource allocation area may be indicated based on multiple resource groups in the n-th port. In this case, the C-plane message may include information (1010-1) for the first port of FIG. 10A and information (1060-n) for the n-th port of FIG. 10B.

[0218] According to one embodiment, among the information about the first port (1010-1, 1060-1), the beam identifier (1024-1, 1061-1) (or terminal identifier) ​​assigned to the first port may be included in the section information. The remaining information excluding the beam identifier (1024-1, 1061-1) (or terminal identifier) ​​assigned to the first port may be included in the section extension information.

[0219] Figure 10c illustrates an example of section extension information for indicating resource allocation areas for each of a plurality of ports.

[0220] Figure 10d illustrates an example of section extension information for indicating a resource allocation area for each of a plurality of ports.

[0221] Referring to FIG. 10c, the section extension information may include at least some of the information illustrated in FIG. 10a. For example, the section extension information may include some (1050) of the information (1010-1) regarding the first port of FIG. 10a. The section extension information may include information regarding the second port (1010-2) to information regarding the nth port (1010-n).

[0222] For example, section extension information includes information (1020-1) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups among the information (1010-1) regarding the first port of FIG. 10a, information (1021-1) (RBGUnit) for indicating a unit of multiple resource groups, and information (1022-1) ('1) for indicating a starting resource block of at least one resource block allocated to the first port. st port startPrbcPerPort'), and / or information (1023-1) ('1) for indicating the number of at least one resource block allocated to the first port st The section extension information may include information about the second port (1010-2) to information about the nth port (1010-n) of FIG. 10A.

[0223] Section extension information is the beam identifier (1024-1) ('1) assigned to the first port among the information (1010-1) regarding the first port of FIG. 10a. st port beamid') may not be included. The beam identifier (1024-1) assigned to the first port ('1 st port beamid') may be included in section information (e.g., section information (530) of FIG. 5). Since section extension information is indicated after the section information, the beam identifier (1024-1) ('1) assigned to the first port among the information about the first port (1010-1) st port beamid') may not be included.

[0224] Referring to FIG. 10d, the section extension information may include at least some of the information illustrated in FIG. 10b. For example, the section extension information may include some (1080) of the information (1060-1) regarding the first port of FIG. 10b. The section extension information may include information (1060-2) regarding the second port to information (1060-n) regarding the nth port.

[0225] For example, section extension information may include information (1062-1) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups, information (1063-1) (RBGUnit) for indicating a unit of multiple resource groups, and / or information (1064-1) ('1) for indicating at least one resource group allocated to the first port, among the information (1060-1) regarding the first port of FIG. 10b. st prbBitmap'). The section extension information may include all of the information about the second port (1060-2) to the information about the nth port (1060-n) of FIG. 10b.

[0226] Section extension information is the beam identifier (1061-1) assigned to the first port among the information (1060-1) regarding the first port of FIG. 10b ('1 st port beamid') may not be included. The beam identifier (1061-1) assigned to the first port ('1 st port beamid') may be included in section information (e.g., section information (530) of FIG. 5). Since section extension information is indicated after the section information, the beam identifier (1061-1) ('1) assigned to the first port among the information (1060-1) regarding the first port st port beamid') may not be included.

[0227] In FIGS. 10C and 10D, the case where the value of 'RBGenable' is the first value and the case where the value of 'RBGenable' is the second value are illustrated, but the present invention is not limited thereto. Whether a resource allocation area is indicated based on multiple resource groups for each of a plurality of ports can be independently set. For example, a resource allocation area may not be indicated based on multiple resource groups in the first port, and a resource allocation area may be indicated based on multiple resource groups in the n-th port. In this case, the C-plane message may include some of the information (1050) for the first port in FIG. 10C and information (1060-n) for the n-th port in FIG. 10D.

[0228] According to one embodiment, the section extension information illustrated in FIG. 10c and / or FIG. 10d may be configured based on section extension type 10. An example of a C-plane message including section extension information configured based on section extension type 10 will be described below in FIG. 15.

[0229] Figure 11a illustrates an example of information for indicating a resource allocation area for each of a plurality of ports.

[0230] Referring to FIG. 11a, the C-plane message may include section information and section extension information for indicating a resource region. For example, the section information may include information for indicating the number of resource blocks constituting the resource region (e.g., 'numPrbc' in FIG. 5) and information for indicating the starting resource block of the resource blocks (e.g., 'startPrbc' in FIG. 5).

[0231] According to one embodiment, a C-plane message may include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on a plurality of resource blocks, and information for indicating resource blocks for each of the plurality of resource groups.

[0232] For example, a C-plane message may contain information about n ports. Although not illustrated, the C-plane message may contain 'numPortc'. 'numPortc' may indicate the number of ports added to one port. For example, if the value of 'numPortc' is 1, the C-plane message may contain information about 2 ports. For example, if the value of 'numPortc' is 3, the C-plane message may contain information about 4 ports.

[0233] For example, a C-plane message may include information about a first port (1010-1) to information about an n-th port (1010-n). Each of the information about the first port (1010-1) to information about the n-th port (1010-n) may include a beam identifier ('beamid') (or a terminal identifier ('ueid')) assigned to the corresponding port and / or information ('GroupBitmap') for indicating at least one resource group assigned to the corresponding port. The C-plane message may further include information (1120) ('numPRBGroup') for indicating the number of a plurality of resource groups. The C-plane message may further include indicators (1130-1 to 1130-n) for indicating resource blocks for each of the plurality of resource groups.

[0234] For example, information about the first port (1110-1) may include a beam identifier (1140-1) ('1st port beamid') (or terminal identifier) ​​assigned to the first port and / or information (1150-1) ('1st port beamid') for indicating at least one resource group assigned to the first port. st It can contain a GroupBitmap').

[0235] For example, information about the nth port (1110-n) is the beam identifier (1140-n) assigned to the nth port ('(numPortc+1) th port beamid')(or terminal identifier) ​​and / or information for indicating at least one resource group assigned to the nth port (1150-n)('(numPortc+1) th It can contain a GroupBitmap').

[0236] For example, an indicator (1130-1) for indicating at least one resource block for a first resource group may be configured based on the number of at least one resource block for the first resource group and a starting resource block of the at least one resource block. For example, an indicator (1130-n) for indicating at least one resource block for an n-th resource group may be configured based on the number of at least one resource block for the n-th resource group and a starting resource block of the at least one resource block.

[0237] Specific examples of indicators (e.g., indicators (1130-1) to (1130-n)) for indicating at least one resource block for one resource group will be described later in FIGS. 12a and 12b.

[0238] For example, beam identifiers (1140-1 to 1140-n) assigned to one port may be composed of 15 bits. Information (1150-1 to 1150-n) for indicating at least one resource group assigned to one port may be composed of 8 bits. Information (1120) for indicating the number of multiple resource groups may be composed of 3 bits. Indicators (1130-1 to 1130-n) configured based on the number of at least one resource block for one resource group and the starting resource block of the at least one resource block may be composed of 16 bits.

[0239] According to one embodiment, at least some of the information illustrated in FIG. 11a may be included in the section information. The remaining part of the information illustrated in FIG. 11a may be included in the section extension information.

[0240] For example, the beam identifier (1140-1) assigned to the first port may be included in the section information. Among the information illustrated in FIG. 11a, the remaining information except for the beam identifier (1140-1) assigned to the first port may be included in the section extension information. An example in which the remaining information except for the beam identifier (1140-1) assigned to the first port among the information (1110-1) regarding the first port to the information (1110-n) regarding the n-th port is included in the section extension information will be described later in FIG. 11b.

[0241] For example, information about the first port (1110-1) may be included in the section information. Information about the second port (1110-2) to information about the nth port (1110-n) may be included in the section extension information.

[0242] According to one embodiment, the information illustrated in FIG. 11a (e.g., information (1110-1 to 1110-n), information (1120), and indicators (1130-1 to 1130-n)) is illustrated as consisting of a single field, but this is for convenience of explanation and is not limited thereto. The information illustrated in FIG. 11a may be included in a C-plane message in various forms. Depending on the embodiment, at least some or all of the information illustrated in FIG. 11a may be explicitly or implicitly included in the C-plane message.

[0243] Figure 11b illustrates an example of section extension information for indicating resource allocation areas for each of a plurality of ports.

[0244] Referring to FIG. 11A, the section extension information may include at least some of the information illustrated in FIG. 11A. For example, the section extension information may include some of the information (1110-1) regarding the first port of FIG. 11A. The section extension information may include information (1110-2) regarding the second port of FIG. 11A to information (1110-n) regarding the nth port.

[0245] For example, section extension information may include information (1150-1) ('1) for indicating at least one resource group assigned to port 1 among the information (1110-1) regarding the first port of FIG. 11a. st GroupBitmap'). The section extension information may include all of the information about the second port (1110-2) to the information about the nth port (1110-n) of FIG. 11a.

[0246] Section extension information is the beam identifier (1140-1) assigned to the first port among the information (1110-1) regarding the first port of FIG. 11a. st port beamid') may not be included. The beam identifier (1140-1) assigned to the first port ('1st port beamid') may be included in section information (e.g., section information (530) of FIG. 5). Since section extension information is indicated after the section information, the beam identifier (1140-1) ('1) assigned to the first port among the information (1110-1) regarding the first port of FIG. 11a st port beamid') may not be included.

[0247] According to one embodiment, the section extension information illustrated in FIG. 11b may be configured based on section extension type 10. An example of a C-plane message including section extension information configured based on section extension type 10 will be described below in FIG. 16.

[0248] Figure 12a illustrates an example of a technique for indicating at least one resource block.

[0249] Figure 12b illustrates an example of an indicator set according to a technique for indicating at least one resource block.

[0250] Referring to FIGS. 12A and 12B, a resource allocation area (1210) can be configured within a resource area (1200). The resource allocation area (1210) can be set within the resource area (1200).

[0251] The resource area (1200) can be configured based on the starting resource block (1211) of the resource area (1200) and the number (1212) of resource blocks in the resource area (1200). The resource allocation area (1210) can be configured based on the starting resource block (S) of the resource allocation area (1210) and the number (L) of resource blocks in the resource allocation area (1210).

[0252] When the starting resource block (1211) and the number of resource blocks (1212) are determined, the resource allocation area (1210) within the resource area (1200) can be indicated through one indicator ('prbindication') using the following mathematical formula.

[0253]

[0254] Referring to mathematical expression 1, 'prbindication' is a value indicating the location of the resource allocation area (1210) based on the starting resource block (1211). 'numPrbC' is the number of resource blocks (1212). L is the number of resource blocks in the resource allocation area (1210). S is the starting resource block of the resource allocation area (1210). is a floor function (or floor operation) for x. Although not shown in mathematical expression 1, 'startPrbC' is the start resource block (1211) of the resource area (1200).

[0255] When 'numPrbC' is 14 and 'startPrbC' is 0, 'prbindication' can be set as shown in Fig. 12b based on mathematical expression 1. Fig. 12b shows the value of 'prbindication' according to the start resource block (S) of the resource allocation area (1210) and the number (L) of resource blocks of the resource allocation area (1210).

[0256] For example, when the starting resource block (S) is 5 and the number of resource blocks (L) is 8, the value of 'prbindication' is '103'. When the DU (210) transmits 'prbindication' set to '103' to the RU (220), the RU (220) can identify that the starting resource block (S) is 5 and the number of resource blocks (L) is 8. As described above, when 'prbindication' is transmitted, the number of transmitted bits can be reduced. 'prbindication' can be used to indicate at least one resource block allocated to one port in FIG. 9A. 'prbindication' can be used to indicate at least one resource block constituting one resource group in FIG. 11A. Since the number of resource blocks (1212) of the starting resource block (1211) and the resource area (1200) can be transmitted through the section information (530) of FIG. 5, at least one resource block allocated to one port (or at least one resource block constituting one resource group) can be indicated through 'prbindication'.

[0257] Figure 13 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0258] Referring to FIG. 13, a C-plane message (1300) may be used to indicate at least one resource block to be allocated to each of a plurality of ports. For example, the C-plane message (1300) may correspond to at least a portion of the C-plane message (500) illustrated in FIG. 5.

[0259] For example, section information (1330) of a C-plane message (1300) may include a beam identifier (ID) for a port and / or information about a resource area for a section. Section information (1330) including information about a beam identifier (ID) for a port and / or information about a resource area for a section may be included in a C-plane message (1300) configured based on one section type among a plurality of section types (e.g., section types 1 to 8). For example, section information (1330) including information about a beam identifier (ID) for a port and / or information about a resource area for a section may be included in a C-plane message (1300) configured based on one section type among section types 1, 3, and 5. Section information (1330) may be configured based on one section type among section types 1, 3, and 5.

[0260] In FIG. 13, an example is described in which section information (1330) including a beam identifier (ID) for one port and / or information on a resource area for a section is included in a C-plane message (1300) configured based on section type 1, but is not limited thereto. For example, section information (530) including a beam identifier (ID) for one port and / or information on a resource area for a section may be included in a C-plane message configured based on one of a plurality of section types (e.g., section types 1 to 8).

[0261] A C-plane message (1300) may include transport header information (1310), common header information (1320), section information (1330), and section extension information (1340). The transport header information (1310) may correspond to the transport header information (510) of FIG. 5. The common header information (1320) may correspond to the common header information (1320) of FIG. 5. The section information (1330) may correspond to the section information (1330) of FIG. 5.

[0262] For example, a resource area for a section may be composed of multiple resource blocks. Section information (1330) may include information (1331) ('startPrbc') indicating a start resource block of the multiple resource blocks. Section information (1330) may include information (1332) ('numPrbc') indicating the number of the multiple resource blocks. Section information (1330) may include a beam identifier (or terminal identifier) ​​(1335) ('beamId') assigned to the first port.

[0263] According to one embodiment, the C-plane message (1300) may indicate at least one resource block to be allocated to each of the multiple ports. The section extension information (1340) may indicate at least one resource block to be allocated to each of the multiple ports.

[0264] For example, section extension information (1340) may be configured based on section extension type A. Section extension type A may be configured with at least one of a plurality of section extension types. For example, section extension type A may include section extension type 1 to section extension type 23. For example, section extension type may include section extension type 10. For example, section extension type A may be configured with a combination of section extension type 10 and another section extension type. For example, section extension type A may be distinguished from section extension type 1 to section extension type 23.

[0265] The following FIGS. 14 to 16 illustrate examples of C-plane messages for indicating at least one resource block allocated to each of a plurality of ports. FIGS. 14 to 16 illustrate examples in which at least one resource block allocated to each of a plurality of ports is indicated through section extension information of the C-plane message, but the present invention is not limited thereto. The at least one resource block allocated to each of a plurality of ports may also be indicated by section information of the C-plane message.

[0266] Figure 14 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0267] Referring to FIG. 14, a C-plane message (1400) may include transport header information (1410), common header information (1420), section information (1430), and section extension information (1440). The transport header information (1410) may correspond to the transport header information (1310) of FIG. 13. The common header information (1420) may correspond to the common header information (1420) of FIG. 13. The section information (1430) may correspond to the section information (1430) of FIG. 13. The section extension information (1440) may be configured based on section extension type 10.

[0268] For example, a resource area for a section may be composed of multiple resource blocks. Section information (1430) may include information (1431) ('startPrbc') indicating a start resource block of the multiple resource blocks. Section information (1430) may include information (1432) ('numPrbc') indicating the number of the multiple resource blocks. Section information (1430) may include a beam identifier (or terminal identifier) ​​(1450-1) ('beamId') assigned to the first port.

[0269] For example, section extension information (1440) may include information (1444) indicating the type of beam grouping ('beamGroupType'). To indicate at least one resource block allocated to each of a plurality of ports, the value of 'beamGroupType' may be set to '11' (or '11b', '2').

[0270] For example, a C-plane message (1400) may include information about n ports. It may include information (1443) ('numPortc') indicating the number of ports added to one port. For example, if the value of 'numPortc' is 1, the C-plane message (1400) may include information about 2 ports. For example, if the value of 'numPortc' is 3, the C-plane message (1400) may include information about 4 ports.

[0271] According to one embodiment, the C-plane message (1400) may include information as shown in FIG. 9a to indicate at least one resource block to be allocated to each of the multiple ports.

[0272] The C-plane message (1400) may include information about the first port (1441-1) to information about the n-th port (1441-n). For example, among the information about the first port (1441-1), a beam identifier (or terminal identifier) ​​(1450-1) assigned to the first port may be included in the section information (1430). Among the information about the first port (1441-1), an indicator (1460-1) for indicating at least one resource block assigned to the first port may be included in the section extension information (1440). Information about the second port (1441-2) to information about the n-th port (1441-n) may be included in the section extension information (1440).

[0273] For example, each of the information for the second port (1441-2) to the information for the nth port (1441-n) may include a beam identifier (1450-2 to 1450-n) assigned to the corresponding port and an indicator (1460-2 to 1460-n) for indicating at least one resource block assigned to the corresponding port.

[0274] For example, the indicators (1460-1 to 1460-n) can indicate at least one resource block allocated to the corresponding port based on FIGS. 12A and 12B . Since information (1431) ('startPrbc') indicating a start resource block and information (1432) ('numPrbc') indicating the number of multiple resource blocks are included in the section information (1430), at least one resource block (or resource allocation area) allocated to the corresponding port can be indicated through the indicators (1460-1 to 1460-n).

[0275] For example, section extension information (1440) may include information for zero padding (1442).

[0276] According to one embodiment, if duplicate assignment of endpoints for the same terminal identifier (or beam identifier) ​​is allowed, PUSCH scheduling operation according to a communication standard (e.g., 3GPP) specified through a C-plane message (1400) may be supported.

[0277] Figure 15 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0278] Referring to FIG. 15, a C-plane message (1500) may include transport header information (1510), common header information (1520), section information (1530), and section extension information (1540). The transport header information (1510) may correspond to the transport header information (1310) of FIG. 13. The common header information (1520) may correspond to the common header information (1520) of FIG. 13. The section information (1530) may correspond to the section information (1530) of FIG. 13. The section extension information (1540) may be configured based on section extension type 10.

[0279] For example, a resource area for a section may be composed of multiple resource blocks. Section information (1530) may include information (1531) ('startPrbc') indicating a start resource block of the multiple resource blocks. Section information (1530) may include information (1532) ('numPrbc') indicating the number of the multiple resource blocks. Section information (1530) may include a beam identifier (or terminal identifier) ​​(1550-1) ('beamId') assigned to the first port.

[0280] For example, section extension information (1540) may include information (1544) indicating the type of beam grouping ('beamGroupType'). To indicate at least one resource block allocated to each of a plurality of ports, the value of 'beamGroupType' may be set to '11' (or '11b', '2').

[0281] For example, a C-plane message (1500) may include information about n ports. It may include information (1543) ('numPortc') indicating the number of ports added to one port. For example, if the value of 'numPortc' is 1, the C-plane message (1500) may include information about 2 ports. For example, if the value of 'numPortc' is 3, the C-plane message (1500) may include information about 4 ports.

[0282] According to one embodiment, the C-plane message (1500) may include information as shown in FIGS. 10A and 10B to indicate at least one resource block to be allocated to each of the multiple ports.

[0283] The C-plane message (1500) may include information about the first port (1541-1) to information about the n-th port (1541-n). For example, among the information about the first port (1541-1), a beam identifier (or terminal identifier) ​​(1550-1) assigned to the first port may be included in the section information (1530). Among the information about the first port (1541-1), information (1562) for indicating a start resource block of at least one resource block assigned to the first port ('1) st port startPrbcPerPort') and information (1563) for indicating the number of at least one resource block allocated to the first port ('1 st The section extension information (1540) may include information about the second port (1541-2) to information about the n-th port (1541-n). Information about the second port (1541-2) to information about the n-th port (1541-n) may be included in the section extension information (1540). For example, within the section extension information (1540), each of the information about the second port (1441-2) to information about the n-th port (1541-n) may include a beam identifier (1550-2 to 1550-n) assigned to the corresponding port.

[0284] For example, information included in each of the information for the first port (1541-1) to the information for the nth port (1541-n) may be configured differently depending on information (1561, 1571, ..., 1581, 1591) ('RBGenable') for indicating whether a resource allocation area is indicated based on multiple resource groups.

[0285] For example, if the resource allocation area is contiguous, the value of 'RBGenable' may be set to a first value (e.g., '0'). If the resource allocation area is discontinuous, the value of 'RBGenable' may be set to a second value (e.g., '1').

[0286] For example, if the value of 'RBGenable' is the first value (e.g., '0'), a resource allocation area may not be indicated based on multiple resource groups on the corresponding port. If the value of 'RBGenable' is the second value (e.g., '1'), a resource allocation area may be indicated based on multiple resource groups on the corresponding port. FIG. 15 illustrates an example in which the value of 'RBGenable' is set to the first value (e.g., '0') in the information for the first port (1541-1) and the information for the n-th port (1541-n), and in which the value of 'RBGenable' is set to the second value (e.g., '1') in the information for the second port (1541-2) and the information for the (n-1)-th port (1541-(n-1)).

[0287] The information (1541-(n-1)) for the (n-1)th port may have a structure identical to or similar to the structure of the information (1541-1) for the first port, since the value of 'RBGenable' is set to the first value (e.g., '0'). For example, the beam identifier (or terminal identifier) ​​(1550-(n-1)) assigned to the (n-1)th port, the information (1541-(n-1)) for the (n-1)th port may include information (1582) ('numPortc') for indicating the start resource block of at least one resource block assigned to the (n-1)th port. th port startPrbcPerPort') and information (1583) to indicate the number of at least one resource block allocated to the first port ('numPortc th port numPrbcPerPort').

[0288] Since the value of 'RBGenable' is set to the second value (e.g., '1'), the structure of the information (1541-n) for the n-th port can be configured to be identical or similar to the structure of the information (1541-2) for the second port. For example, the information (1541-2) for the second port may include a beam identifier (or terminal identifier) ​​(1550-2) assigned to the second port, information (1573) (RBGUnit) for indicating a unit of a plurality of resource groups, and / or information (1572) ('2') for indicating at least one resource group assigned to the second port. nd prbBitmap'). For example, information (1541-n) for the nth port may include a beam identifier (or terminal identifier) ​​(1550-n) assigned to the nth port, information (1593) (RBGUnit) for indicating a unit of multiple resource groups, and / or information (1592) ('(numPortc+1)) for indicating at least one resource group assigned to the nth port. th It may contain 'prbBitmap'.

[0289] For example, information (1572, 1592) for indicating at least a resource group assigned to one port can indicate at least one resource group among a plurality of resource groups configured according to information (1573, 1573) for indicating a unit of a plurality of resource groups based on a bitmap.

[0290] For example, section extension information (1540) may include information for zero padding (1542).

[0291] According to one embodiment, PUSCH scheduling operation according to a communication standard (e.g., 3GPP) specified through a C-plane message (1500) may be supported.

[0292] Figure 16 illustrates an example of a C-plane message for indicating at least one resource block to be allocated to each of a plurality of ports.

[0293] Referring to FIG. 16, a C-plane message (1600) may include transport header information (1610), common header information (1620), section information (1630), and section extension information (1640). The transport header information (1610) may correspond to the transport header information (1310) of FIG. 13. The common header information (1620) may correspond to the common header information (1620) of FIG. 13. The section information (1630) may correspond to the section information (1630) of FIG. 13. The section extension information (1640) may be configured based on section extension type 10.

[0294] For example, a resource area for a section may be composed of multiple resource blocks. Section information (1630) may include information (1631) ('startPrbc') indicating a start resource block of the multiple resource blocks. Section information (1630) may include information (1632) ('numPrbc') indicating the number of the multiple resource blocks. Section information (1630) may include a beam identifier (or terminal identifier) ​​(1650-1) ('beamId') assigned to the first port.

[0295] For example, section extension information (1640) may include information (1644) indicating the type of beam grouping ('beamGroupType'). To indicate at least one resource block allocated to each of a plurality of ports, the value of 'beamGroupType' may be set to '11' (or '11b', '2').

[0296] For example, a C-plane message (1600) may include information about n ports. It may include information (1643) ('numPortc') indicating the number of ports added to one port. For example, if the value of 'numPortc' is 1, the C-plane message (1600) may include information about 2 ports. For example, if the value of 'numPortc' is 3, the C-plane message (1600) may include information about 4 ports.

[0297] According to one embodiment, the C-plane message (1600) may include information as shown in FIG. 11a to indicate at least one resource block to be allocated to each of the multiple ports.

[0298] The C-plane message (1600) may include information about the first port (1641-1) to information about the n-th port (1641-n). For example, among the information about the first port (1641-1), a beam identifier (or terminal identifier) ​​(1650-1) assigned to the first port may be included in the section information (1630). Among the information about the first port (1641-1), information (1660-1) for indicating at least one resource group assigned to the first port ('1) st GroupBitmap') may be included in the section extension information (1640). Information about the second port (1641-2) to information about the n-th port (1641-n) may be included in the section extension information (1640). For example, within the section extension information (1640), each of the information about the second port (1441-2) to information about the n-th port (1641-n) may include a beam identifier (1650-2 to 1650-n) assigned to the corresponding port and information (1660-2 to 1660-n) for indicating at least one resource group assigned to the corresponding port.

[0299] For example, section extension information (1640) may further include information (1645) ('numPRBGroup') on the number of multiple groups and indicators (1651-1 to 1651-n) for indicating at least one resource block for one resource group. The indicators (1651-1 to 1651-n) may indicate at least one resource block for the group based on FIGS. 12A and 12B . Since information (1631) ('startPrbc') indicating a start resource block and information (1632) ('numPrbc') indicating the number of multiple resource blocks are included in the section information (1630), at least one resource block for the group (or constituting the group) may be indicated through the indicators (1651-1 to 1651-n).

[0300] For example, section extension information (1640) may include information for zero padding (1642).

[0301] According to one embodiment, PUSCH scheduling operation according to a communication standard (e.g., 3GPP) specified through a C-plane message (1600) may be supported.

[0302] According to one embodiment, a method performed in a device of a distributed unit (DU) may include generating a control plane (C-plane) message including section information and section extension information for indicating a resource area. The method may include transmitting the control plane message to a radio unit (RU). The control plane message may indicate a resource allocation area for each port among a plurality of ports for group configuration within the resource area.

[0303] According to one embodiment, the section information may include information for indicating the number of a plurality of resource blocks constituting the resource area and information for indicating a starting resource block of the plurality of resource blocks.

[0304] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include an indicator configured based on the number of the at least one resource block and the starting resource block of the at least one resource block.

[0305] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include information for indicating the number of the at least one resource block and information about a starting resource block of the at least one resource block.

[0306] According to one embodiment, the control plane message may include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on the plurality of resource blocks.

[0307] According to one embodiment, the control plane message may include information for indicating resource blocks for each of the plurality of resource groups.

[0308] According to one embodiment, a method performed in a device of a radio unit (RU) may include receiving, from a distributed unit (DU), a control plane (C-plane) message including section information and section extension information for indicating a resource region. The method may include identifying, based on the control plane message, a resource allocation region for each port among a plurality of ports for group configuration within the resource region.

[0309] According to one embodiment, the section information may include information for indicating the number of a plurality of resource blocks constituting the resource area and information for indicating a starting resource block of the plurality of resource blocks.

[0310] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include an indicator configured based on the number of the at least one resource block and the starting resource block of the at least one resource block.

[0311] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include information for indicating the number of the at least one resource block and information about a starting resource block of the at least one resource block.

[0312] According to one embodiment, the control plane message may include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on the plurality of resource blocks.

[0313] According to one embodiment, the control plane message may include information for indicating resource blocks for each of the plurality of resource groups.

[0314] According to one embodiment, a device of a distributed unit (DU) may include a fronthaul transceiver, a memory storing one or more instructions and including a storage medium, and at least one processor including a processing circuit. The one or more instructions, when individually or collectively executed by the at least one processor, may cause the device to generate a control plane (C-plane) message including section information and section extension information for indicating a resource region. The one or more instructions, when individually or collectively executed by the at least one processor, may cause the device to transmit the C-plane message to a radio unit (RU) via the fronthaul transceiver. The C-plane message may indicate a resource allocation region for each port among a plurality of ports for group configuration within the resource region.

[0315] According to one embodiment, the section information may include information for indicating the number of a plurality of resource blocks constituting the resource area and information for indicating a starting resource block of the plurality of resource blocks.

[0316] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include an indicator configured based on the number of the at least one resource block and the starting resource block of the at least one resource block.

[0317] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include information for indicating the number of the at least one resource block and information about a starting resource block of the at least one resource block.

[0318] According to one embodiment, the control plane message may include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on the plurality of resource blocks.

[0319] According to one embodiment, the control plane message may include information for indicating resource blocks for each of the plurality of resource groups.

[0320] According to one embodiment, a device of a radio unit (RU) may include a fronthaul transceiver, a radio frequency (RF) transceiver, a memory storing one or more instructions and including a storage medium, and at least one processor including a processing circuit. The one or more instructions, when individually or collectively executed by the at least one processor, may cause the device to receive, from a distributed unit (DU), using the fronthaul transceiver, a control plane (C-plane) message including section information and section extension information for indicating a resource region. The one or more instructions, when individually or collectively executed by the at least one processor, may cause the device to identify, within the resource region, a resource allocation region for each port among a plurality of ports for group configuration, based on the control plane message.

[0321] According to one embodiment, the section information may include information for indicating the number of a plurality of resource blocks constituting the resource area and information for indicating a starting resource block of the plurality of resource blocks.

[0322] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include an indicator configured based on the number of the at least one resource block and the starting resource block of the at least one resource block.

[0323] According to one embodiment, the control plane message may include information for indicating at least one resource block constituting a resource allocation area for one port among the plurality of resource blocks. The information for indicating the at least one resource block may include information for indicating the number of the at least one resource block and information about a starting resource block of the at least one resource block.

[0324] According to one embodiment, the control plane message may include information for indicating at least one resource group constituting a resource allocation area for one port among a plurality of resource groups configured based on the plurality of resource blocks.

[0325] According to one embodiment, the control plane message may include information for indicating resource blocks for each of the plurality of resource groups.

[0326] According to one embodiment, a method performed by a distributed unit (DU) may include generating a control plane (C-plane) message including section information and section extension information for indicating a resource region, and transmitting the control plane message to a radio unit (RU). The section extension information may include resource information for each of a plurality of user equipment (UEs) associated with a radio unit (RU) connected to the DU. The resource information may include first information and second information. The first information may indicate a starting resource block among resource blocks consecutively allocated to the corresponding UE within the resource region. The first information and the second information may be used to indicate the resource blocks consecutively allocated to the corresponding UE.

[0327] For example, the above section extension information can be used for DMRS-BF-EQ (demodulation reference signal-beamforming-equalizing) or DMRS-BF-NEQ (DMRS beamforming-nonequalizing).

[0328] For example, in the RU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include DMRS extraction and DMRS channel estimation. In the DU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include layer demapping and decoding.

[0329] For example, the second information may include information for identifying the number of resource blocks sequentially allocated to the corresponding UE.

[0330] For example, the section extension information may further include a value related to an ID (identifier) ​​for the corresponding UE.

[0331] According to one embodiment, a method performed by a radio unit (RU) may include receiving, from a distributed unit (DU), a control plane (C-plane) message including section information and section extension information for indicating a resource region. The section extension information may include resource information for each of a plurality of user equipment (UEs) associated with a radio unit (RU) connected to the DU. The resource information may include first information and second information. The first information may indicate a starting resource block among resource blocks consecutively allocated to the corresponding UE within the resource region. The first information and the second information may be used to indicate the resource blocks consecutively allocated to the corresponding UE. The method may include performing uplink communication based on the resource information allocated for each UE.

[0332] For example, the above section extension information can be used for DMRS-BF-EQ (demodulation reference signal-beamforming-equalizing) or DMRS-BF-NEQ (DMRS beamforming-nonequalizing).

[0333] For example, in the RU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include DMRS extraction and DMRS channel estimation. In the DU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include layer demapping and decoding.

[0334] For example, the second information may include information for identifying the number of resource blocks sequentially allocated to the corresponding UE.

[0335] For example, the section extension information may further include a value related to an ID (identifier) ​​for the corresponding UE.

[0336] According to one embodiment, an apparatus for performing functions of a distributed unit (DU) may include at least one fronthaul transceiver including communication circuitry, at least one processor including processing circuitry, and one or more storage media, and a memory for storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the apparatus to generate a control plane (C-plane) message including section information and section extension information for indicating a resource region, and transmit the C-plane message to a radio unit (RU). The section extension information may include resource information for each of a plurality of user equipment (UEs) associated with a radio unit (RU) connected to the DU. The resource information may include first information and second information. The first information may indicate a starting resource block among resource blocks consecutively allocated to a corresponding UE within the resource region. The first information and the second information may be used to indicate the resource blocks sequentially allocated to the corresponding UE.

[0337] For example, the above section extension information can be used for DMRS-BF-EQ (demodulation reference signal-beamforming-equalizing) or DMRS-BF-NEQ (DMRS beamforming-nonequalizing).

[0338] For example, in the RU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include DMRS extraction and DMRS channel estimation. In the DU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include layer demapping and decoding.

[0339] For example, the second information may include information for identifying the number of resource blocks sequentially allocated to the corresponding UE.

[0340] For example, the section extension information may further include a value related to an ID (identifier) ​​for the corresponding UE.

[0341] According to one embodiment, an apparatus for performing functions of a radio unit (RU) may include at least one fronthaul transceiver including communication circuitry, at least one processor including processing circuitry, and one or more storage media, and a memory for storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the apparatus to receive, from a distributed unit (DU), a control plane (C-plane) message including section information and section extension information for indicating a resource region. The section extension information may include resource information for each of a plurality of user equipment (UEs) associated with a radio unit (RU) connected to the DU. The resource information may include first information and second information. The first information may indicate a starting resource block among resource blocks consecutively allocated to a corresponding UE within the resource region. The first information and the second information may be used to indicate the resource blocks consecutively allocated to the corresponding UE. The above instructions, when individually or collectively executed by the at least one processor, may cause the device to perform uplink communication based on the resource information allocated for each UE.

[0342] For example, the above section extension information can be used for DMRS-BF-EQ (demodulation reference signal-beamforming-equalizing) or DMRS-BF-NEQ (DMRS beamforming-nonequalizing).

[0343] For example, in the RU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include DMRS extraction and DMRS channel estimation. In the DU, operations for the DMRS-BF-EQ or the DMRS-BF-NEQ may include layer demapping and decoding.

[0344] For example, the second information may include information for identifying the number of resource blocks sequentially allocated to the corresponding UE.

[0345] For example, the section extension information may further include a value related to an ID (identifier) ​​for the corresponding UE.

[0346] According to one embodiment, in section extension type 10, when 'beamGroupType' is set to '11b', startPrbc and numPrbc can be indicated for each endpoint through the control plane message described above. When the DU indicates MU-MIMO scheduling information to the RU through the control plane message described above, cases where startPrbc and numPrbc for each terminal are different can also be supported.

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

[0348] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure. The one or more programs may be provided as a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0349] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0350] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

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

[0352] According to embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0353] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible within the scope of the present disclosure.

Claims

1. In a method performed by DU (distributed unit), An operation of generating a control plane (C-plane) message containing section information and section extension information for indicating a resource area; and Including an operation of transmitting the above control plane message to a RU (radio unit), The above section extension information includes resource information for each of a plurality of user equipment (UEs) associated with a RU (radio unit) connected to the DU, The above resource information includes first information and second information, The above first information indicates a starting resource block among resource blocks sequentially allocated to the UE within the resource area, The above first information and the above second information are used to indicate the resource blocks sequentially allocated to the corresponding UE. method.

2. In the first paragraph, the section extension information is used for DMRS-BF-EQ (demodulation reference signal-beamforming-equalizing) or DMRS-BF-NEQ (DMRS beamforming-nonequalizing). method.

3. In the second paragraph, the operations for the DMRS-BF-EQ or the DMRS-BF-NEQ in the RU include DMRS extraction and DMRS channel estimation, In the above DU, the operations for the DMRS-BF-EQ or the DMRS-BF-NEQ include layer demapping and decoding. method.

4. In the first paragraph, the second information includes information for identifying the number of resource blocks sequentially allocated to the corresponding UE. method.

5. In the first paragraph, the section extension information further includes a value related to an ID (identifier) ​​for the corresponding UE. method. In a method performed by 6.RU (radio unit), An operation of receiving a control plane (C-plane) message containing section information and section extension information for indicating a resource area from a distributed unit (DU). The above section extension information includes resource information for each of a plurality of user equipment (UEs) associated with a RU (radio unit) connected to the DU, The above resource information includes first information and second information, The above first information indicates a starting resource block among resource blocks sequentially allocated to the UE within the resource area, The above first information and the above second information are used to indicate the resource blocks sequentially allocated to the corresponding UE, An operation for performing uplink communication based on the resource information allocated for each UE, method.

7. In the 6th paragraph, the section extension information is used for DMRS-BF-EQ (demodulation reference signal-beamforming-equalizing) or DMRS-BF-NEQ (DMRS beamforming-nonequalizing). method.

8. In the 7th paragraph, the operations for the DMRS-BF-EQ or the DMRS-BF-NEQ in the RU include DMRS extraction and DMRS channel estimation, In the above DU, the operations for the DMRS-BF-EQ or the DMRS-BF-NEQ include layer demapping and decoding. method.

9. In the 6th paragraph, the second information includes information for identifying the number of resource blocks sequentially allocated to the corresponding UE. method.

10. In the 6th paragraph, the section extension information further includes a value related to an ID (identifier) ​​for the corresponding UE. method.

11. In a device for performing the functions of DU (distributed unit), At least one fronthaul transceiver comprising communication circuitry; At least one processor comprising a processing circuit; and comprising one or more storage media, and including a memory storing instructions; The above instructions, when individually or collectively executed by the at least one processor, Generate a control plane (C-plane) message containing section information and section extension information for indicating a resource area, Causing the device to transmit the above control plane message to the RU (radio unit), The above section extension information includes resource information for each of a plurality of user equipment (UEs) associated with a RU (radio unit) connected to the DU, The above resource information includes first information and second information, The above first information indicates a starting resource block among resource blocks sequentially allocated to the UE within the resource area, The above first information and the above second information are used to indicate the resource blocks sequentially allocated to the corresponding UE. device.

12. In the 11th paragraph, the section extension information is used for DMRS-BF-EQ (demodulation reference signal-beamforming-equalizing) or DMRS-BF-NEQ (DMRS beamforming-nonequalizing). device.

13. In the 12th paragraph, the operations for the DMRS-BF-EQ or the DMRS-BF-NEQ in the RU include DMRS extraction and DMRS channel estimation, In the above DU, the operations for the DMRS-BF-EQ or the DMRS-BF-NEQ include layer demapping and decoding. device.

14. In the 11th paragraph, the second information includes information for identifying the number of resource blocks sequentially allocated to the corresponding UE. device. In a device for performing the functions of 15.RU (radio unit), At least one fronthaul transceiver comprising communication circuitry; At least one processor comprising a processing circuit; and comprising one or more storage media, and including a memory storing instructions; The above instructions, when individually or collectively executed by the at least one processor, Receive a control plane (C-plane) message containing section information and section extension information for indicating a resource area from a distributed unit (DU), The above section extension information includes resource information for each of a plurality of user equipment (UEs) associated with a RU (radio unit) connected to the DU, The above resource information includes first information and second information, The above first information indicates a starting resource block among resource blocks sequentially allocated to the UE within the resource area, The above first information and the above second information are used to indicate the resource blocks sequentially allocated to the corresponding UE, Causing the device to perform uplink communication based on the resource information allocated for each UE. device.

Images