Method and apparatus for indicating antenna mapping information in wireless communication system

Abstract

The present disclosure relates to a method and an apparatus for indicating antenna mapping information in a wireless communication system. The method performed by a distributed unit (O-DU) of a base station in a wireless communication system, according to one embodiment of the present disclosure, comprises the steps of: receiving, from at least one radio unit (O-RU), a management message including capability information related to uplink antenna mapping of the at least one O-RU; generating, on the basis of the capability information, a control message including uplink antenna mapping information about the at least one O-RU; and transmitting the generated control message to the at least one O-RU, wherein the control message can include a section type format for scheduling information and a section extension format including at least one from among antenna group indication information, antenna diversity indication information, and antenna diversity number indication information related to antenna mapping.

Description

Method and apparatus for indicating antenna mapping information in a wireless communication system

[0001] The present disclosure relates to a method and apparatus for indicating antenna mapping information in a wireless communication system, and more specifically, to a method and apparatus for indicating antenna mapping information to be used for uplink beamforming.

[0002] Looking back at the evolution of wireless communication through successive generations, technologies have been developed primarily for human-oriented services, such as voice, multimedia, and data. Following the commercialization of 5G (5th Generation) communication systems, connected devices, which have been increasing explosively, are expected to be connected to communication networks. Examples of networked objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve into various form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. In the 6G (6th Generation) era, efforts are underway to develop improved 6G communication systems to connect hundreds of billions of devices and objects to provide diverse services. For this reason, 6G communication systems are being referred to as "beyond 5G" systems.

[0003] In the 6G communication system predicted to be realized around 2030, the maximum transmission speed is tera (i.e., 1,000 gigabit) bps (bit per second), and the wireless latency is 100 microseconds (μ sec). In other words, compared to the 5G communication system, the transmission speed in the 6G communication system is 50 times faster and the wireless latency is reduced to one-tenth.

[0004] To achieve such high data transmission speeds and ultra-low latency, 6G communication systems are being considered for implementation in the terahertz (THz) band (e.g., the 95 gigahertz (GHz) to 3 terahertz (3THz) band). Due to more severe path loss and atmospheric absorption phenomena compared to the millimeter wave (mmWave) band introduced in 5G, the importance of technologies capable of guaranteeing signal reach, or coverage, is expected to increase in the terahertz band. As key technologies to ensure coverage, new waveforms, beamforming, and multi-antenna transmission technologies such as massive Multiple-Input and Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, which are superior in terms of coverage compared to RF (Radio Frequency) devices, antennas, and OFDM (Orthogonal Frequency Division Multiplexing), must be developed. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) are being discussed to improve the coverage of terahertz band signals.

[0005] In addition, to improve frequency efficiency and system network, development is underway in 6G communication systems for full duplex technology, in which uplink and downlink simultaneously utilize the same frequency resources at the same time; network technology that integrates satellites and HAPS (High-Altitude Platform Stations); network structure innovation technology that supports mobile base stations and enables network operation optimization and automation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; AI-based communication technology that utilizes AI (Artificial Intelligence) from the design stage and internalizes end-to-end AI support functions to realize system optimization; and next-generation distributed computing technology that realizes services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high performance communication and computing resources (Mobile Edge Computing (MEC), cloud, etc.). In addition, attempts are continuing to further strengthen connectivity between devices, further optimize networks, promote the softwareization of network entities, and increase the openness of wireless communication through the design of new protocols to be used in 6G communication systems, the implementation of hardware-based security environments, the development of mechanisms for the safe utilization of data, and the development of technologies regarding privacy maintenance methods.

[0006] Due to the research and development of such 6G communication systems, it is expected that a new dimension of hyper-connected experience will become possible through the hyper-connectivity of 6G communication systems, which encompasses not only connections between objects but also connections between people and objects. Specifically, it is projected that 6G communication systems will enable the provision of services such as truly immersive eXtended Reality (XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response, which are provided through 6G communication systems with enhanced security and reliability, will be applied in various fields including industry, healthcare, automotive, and home appliances.

[0007] The present disclosure provides a method and apparatus for indicating antenna mapping information to be used for uplink beamforming.

[0008] A method performed by a distributed unit (O-DU) of a base station in a wireless communication system according to one embodiment of the present disclosure comprises: receiving a management message from at least one radio unit (O-RU) that includes capability information related to uplink antenna mapping of the at least one O-RU; generating a control message that includes uplink antenna mapping information for the at least one O-RU based on the capability information; and transmitting the generated control message to the at least one O-RU. The control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0009] A method performed by a radio unit (O-RU) of a base station in a wireless communication system according to one embodiment of the present disclosure comprises: transmitting a management message to a distributed unit (O-DU) that includes capability information related to uplink antenna mapping of the O-RU; receiving a control message from the O-DU that includes uplink antenna mapping information for at least one O-RU generated based on the capability information; and receiving an uplink beam based on the generated control message. The control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0010] According to one embodiment of the present disclosure, a distributed unit (O-DU) device of a base station in a wireless communication system comprises a fronthaul interface unit configured to transmit and receive signals to and from a radio unit (O-RU) and at least one control unit, wherein the control unit receives a management message from at least one radio unit (O-RU) that includes capability information related to uplink antenna mapping of the at least one O-RU, generates a control message that includes uplink antenna mapping information for the at least one O-RU based on the capability information, and controls the transmission of the generated control message to the at least one O-RU, wherein the control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0011] According to one embodiment of the present disclosure, a radio unit (O-RU) device of a base station in a wireless communication system comprises a transceiver, a fronthaul interface unit configured to transmit and receive signals with a distributed unit (O-DU), and at least one control unit. The control unit transmits a management message to the distributed unit (O-DU) that includes capability information related to uplink antenna mapping of the O-RU, receives from the distributed unit a control message that includes uplink antenna mapping information for at least one O-RU generated based on the capability information, and controls the receiving of an uplink beam based on the generated control message. The control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0012] According to one embodiment of the present disclosure, a method and apparatus for indicating antenna mapping information to be used for uplink beamforming can be provided.

[0013] Figure 1 is a diagram showing the fronthall interface of an O(open)-RAN(radio access network).

[0014] Figure 2 is a diagram showing an example of low layer function split through RU (radio unit) and DU (distributed unit).

[0015] Figure 3 is a diagram showing the format of a message transmitted between the O-RU and the O-DU.

[0016] FIG. 4 is a diagram illustrating the process of transmitting management messages, control messages, and data between an O-RU and an O-DU according to one embodiment of the present disclosure.

[0017] FIG. 5 is a flowchart illustrating a method performed by an O-DU according to one embodiment of the present disclosure.

[0018] FIG. 6 is a flowchart illustrating a method performed by an O-RU according to one embodiment of the present disclosure.

[0019] FIGS. 7 and FIGS. 8 are section extension formats for indicating antenna mapping information according to one embodiment of the present disclosure.

[0020] FIG. 9 is a drawing showing an M-plane setting according to one embodiment of the present disclosure.

[0021] FIG. 10 is a drawing for illustrating identification information for a supportable antenna group according to one embodiment of the present disclosure.

[0022] FIG. 11 is a diagram illustrating the transmission of a C-plane message and a U-plane message according to one embodiment of the present disclosure.

[0023] FIG. 12 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0024] FIG. 13 is a drawing showing antenna mapping according to one embodiment of the present disclosure.

[0025] FIGS. 14 and FIGS. 15 are section extension formats for indicating antenna mapping information according to another embodiment of the present disclosure.

[0026] FIG. 16 is a drawing showing an M-plane setting according to another embodiment of the present disclosure.

[0027] FIG. 17 is a drawing for explaining a method for setting the number of supportable antenna diversity according to one embodiment of the present disclosure.

[0028] FIG. 18 is a drawing for explaining identification information indicating the number and order of antenna diversity according to one embodiment of the present disclosure.

[0029] FIG. 19 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0030] FIG. 20 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0031] FIG. 21 is a drawing showing antenna mapping according to another embodiment of the present disclosure.

[0032] FIGS. 22 and FIGS. 23 are section extension formats for indicating antenna mapping information according to another embodiment of the present disclosure.

[0033] FIG. 24 is a drawing showing an M-plane setting according to another embodiment of the present disclosure.

[0034] FIG. 25 is a drawing for explaining a method for setting the number of supportable antenna diversity according to another embodiment of the present disclosure.

[0035] FIG. 26 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0036] FIG. 27 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0037] FIG. 28 is a drawing showing antenna mapping according to another embodiment of the present disclosure.

[0038] FIG. 29 is a drawing showing the configuration of an O-DU according to one embodiment of the present disclosure.

[0039] FIG. 30 is a drawing showing the configuration of an O-RU according to one embodiment of the present disclosure.

[0040] A method performed by a distributed unit (O-DU) of a base station in a wireless communication system according to one embodiment of the present disclosure comprises: receiving a management message from at least one radio unit (O-RU) that includes capability information related to uplink antenna mapping of the at least one O-RU; generating a control message that includes uplink antenna mapping information for the at least one O-RU based on the capability information; and transmitting the generated control message to the at least one O-RU. The control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0041] In one embodiment, the capability information includes identification information for a supportable antenna group, and the section expansion format may include antenna group indication information.

[0042] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include at least one identification information indicating the number and order of antenna diversitys.

[0043] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include information indicating the number of antenna diversitys.

[0044] In one embodiment, the capability information includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and the section type format for the scheduling information may include the antenna diversity number indication information based on the duplicated UE identification information.

[0045] A method performed by a radio unit (O-RU) of a base station in a wireless communication system according to another embodiment of the present disclosure comprises: transmitting a management message to a distributed unit (O-DU) that includes capability information related to uplink antenna mapping of the O-RU; receiving a control message from the O-DU that includes uplink antenna mapping information for at least one O-RU generated based on the capability information; and receiving an uplink beam based on the generated control message. The control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0046] In one embodiment, the capability information includes identification information for a supportable antenna group, and the section expansion format may include antenna group indication information.

[0047] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include at least one identification information indicating the number and order of antenna diversitys.

[0048] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include information indicating the number of antenna diversitys.

[0049] In one embodiment, the capability information includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and the section type format for the scheduling information may include the antenna diversity number indication information based on the duplicated UE identification information.

[0050] According to another embodiment of the present disclosure, a distributed unit (O-DU) device of a base station in a wireless communication system comprises a fronthaul interface unit configured to transmit and receive signals to and from a radio unit (O-RU) and at least one control unit, wherein the control unit receives a management message from at least one radio unit (O-RU) that includes capability information related to uplink antenna mapping of the at least one O-RU, generates a control message that includes uplink antenna mapping information for the at least one O-RU based on the capability information, and controls the transmission of the generated control message to the at least one O-RU, wherein the control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0051] In one embodiment, the capability information includes identification information for a supportable antenna group, and the section expansion format may include antenna group indication information.

[0052] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include at least one identification information indicating the number and order of antenna diversitys.

[0053] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include information indicating the number of antenna diversitys.

[0054] In one embodiment, the capability information includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and the section type format for the scheduling information may include the antenna diversity number indication information based on the duplicated UE identification information.

[0055] According to another embodiment of the present disclosure, a radio unit (O-RU) device of a base station in a wireless communication system comprises a transceiver, a fronthaul interface unit configured to transmit and receive signals with a distributed unit (O-DU), and at least one control unit. The control unit transmits a management message to the distributed unit (O-DU) that includes capability information related to uplink antenna mapping of the O-RU, receives from the distributed unit a control message that includes uplink antenna mapping information for at least one O-RU generated based on the capability information, and controls the receiving of an uplink beam based on the generated control message. The control message may include a section type format for scheduling information and a section extension format that includes one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping.

[0056] In one embodiment, the capability information includes identification information for a supportable antenna group, and the section expansion format may include antenna group indication information.

[0057] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include at least one identification information indicating the number and order of antenna diversitys.

[0058] In one embodiment, the capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include information indicating the number of antenna diversitys.

[0059] In one embodiment, the capability information includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and the section type format for the scheduling information may include the antenna diversity number indication information based on the duplicated UE identification information.

[0060] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that identical components in the accompanying drawings are represented by the same reference numerals whenever possible. Furthermore, detailed descriptions of known functions and configurations that could obscure the essence of the present disclosure will be omitted.

[0061] In describing the embodiments in this specification, descriptions of technical details that are well known in the technical field to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary descriptions.

[0062] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0063] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, like reference numerals refer to like components.

[0064] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0065] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). Alternatively, in some embodiments, the functions mentioned in the blocks may occur out of order. For example, two blocks depicted consecutively may be executed substantially simultaneously, or the blocks may be executed in reverse order from time to time according to the corresponding function.

[0066] In this disclosure, the term “part” as used refers to a software or hardware component, such as an FPGA or ASIC, and the “part” performs certain roles. However, the “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to operate one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” Furthermore, the components and “parts” may be implemented to operate one or more CPUs within a device or secure multimedia card.

[0067] Hereinafter, in the present disclosure, an uplink (UL) refers to a wireless link through which a terminal transmits data or control signals to a base station, and a downlink (DL) refers to a wireless link through which a base station transmits data or control signals to a terminal. Additionally, the base station is an entity that performs resource allocation for terminals and may be at least one of an eNode B, Node B, BS (Base Station), gNB (generation Node B) wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions.

[0068] With the commercialization of 5th generation communication systems to meet the demand for wireless data traffic, it is expected that services with high data transmission rates will be provided to users through 5G systems, just like 4G systems, and that wireless communication services for various purposes, such as the Internet of Things and services requiring high reliability for specific purposes, will be provided.

[0069] The Open Radio Access Network Alliance (O-RAN Alliance), established by operators and equipment providers to support network systems that mix 4th and 5th generation communication systems, defined new network elements (NEs) and interface specifications based on existing 3GPP standards, leading to the emergence of the Open Radio Access Network (O-RAN) architecture. In the next-generation O-RAN architecture, specifications are being discussed to support new functions and operations for 6th generation communication systems.

[0070] O-RAN redefined the existing 3GPP NEs—RU (radio unit), DU (distributed unit), CU-CP (central unit-control plane), and CU-UP (central unit-user plane)—as O-RU, O-DU, O-CU-CP, and O-CU-UP, respectively (these can be collectively referred to as O-RAN base stations), and additionally standardized RIC (RAN Intelligent Controller) and NRT-RIC (non-real-time RAN Intelligent Controller). Each can be connected via Ethernet between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC. In addition, interface specifications for communication between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC, respectively, have become necessary, and currently, specifications such as E2-DU, E2-CU-CP, and E2-CU-UP can be used between O-DU, O-CU-CP, O-CU-UP and RIC. Unless otherwise noted, RU, DU, CU-CP, and CU-UP described in this specification may be used interchangeably with O-RU, O-DU, O-CU-CP, and O-CU-UP, respectively.

[0071] Figure 1 is a diagram showing the fronthall interface of an O(open)-RAN(radio access network).

[0072] Referring to FIG. 1, the base station (100) may include an O-DU (120) and one or more O-RUs (110-1, …, 110-n). A plurality of O-RUs (160) may be connected to one O-DU (150).

[0073] The O-DU (120) is a logical node containing functions of a base station (e.g., eNB, gNB) excluding those exclusively allocated to the O-RU (110). More specifically, the O-DU (120) is a logical node that provides RLC, MAC, and high-PHY functions. That is, the O-DU (120) can perform functions of the MAC layer and some of the functions of the PHY layer. Here, some of the functions of the PHY layer are those 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).

[0074] The O-DU (120) can control the operation of the O-RUs (110-1, …, 110-N). In this case, the O-DU (120) may be referred to as an LLS (lower layer split) CU (central unit). Additionally, the O-RU (110) may include a subset of the base station functions. Real-time aspects of control plane (C-plane) communication and user plane (U-plane) communication with the O-RU (110) can be controlled by the O-DU (120). The control plane transmits control signals between the O-RU (110) and the O-DU (120), and may indicate, for example, time information, frequency information, beamid, etc. The user plane may transmit demodulated values ​​in the frequency domain between the O-RU (110) and the O-DU (120).

[0075] O-RUs (110-1, …, 110-N) are logical nodes connected to O-DUs (120) that provide low-PHY functions and RF processing. That is, O-RUs (110-1, …, 110-N) can perform low-layer functions of a wireless network. For example, RUs (110) can perform some of the functions of the PHY layer, such as RF functions. Here, some of the functions of the PHY layer refer to functions of the PHY layer that are performed at a level relatively lower than that of the O-DU (120), and may include, for example, iFFT transformation (or FFT transformation), CP insertion (CP removal), and digital beamforming. Specific examples of functional separation are described in detail in FIG. 2.

[0076] O-RU(110-1, …, 110-N) may be referred to as an 'access unit (AU)', 'access point (AP)', 'transmission / reception point (TRP)', 'remote radio head (RRH)', 'radio unit (RU)', or other terms having an equivalent technical meaning.

[0077] O-DU (120) and O-RU (110-1, …, 110-N) can communicate through LLS interfaces (LLS-C, LLS-U). LLS interfaces (LLS-C, LLS-U) represent logical interfaces between O-DU (120) and O-RU (110) utilizing lower layer functional split (i.e., intra-PHY based functional split). In this case, LLS-C supports the C-plane through the LLS interface, and LLS-U supports the U-plane through the LLS interface. LLS interfaces (LLS-C, LLS-U) correspond to fronthall interfaces.

[0078] In FIG. 1, the base station (100) is illustrated to include an O-DU (120) and an O-RU (110-1, …, 110-N), but is not limited thereto, and the base station (100) may include additional components. For example, the base station (100) may further include a centralized unit (O-CU) configured to perform the functions of the upper layers of the access network (e.g., packet data convergence protocol (PDCP), radio resource control (RRC)). Various embodiments of the present disclosure may be applied to both base station deployments including an O-CU and deployments where the O-DU (120) is directly connected to the core network (i.e., implemented by integrating the O-CU and O-DU (120) into a single entity, such as a base station (e.g., an NG-RAN node)).

[0079] Below, for the convenience of explanation, the operation and function of one O-RU (110) will be described. However, this description is not limited to this and can be understood as a description of each of the other O-RUs (e.g., O-RU(110-1, …, 110-n)).

[0080] Figure 2 is a diagram showing an example of low layer function split through RU (radio unit) and DU (distributed unit).

[0081] With the advancement of wireless communication technology (e.g., 5G communication systems or NR (new radio) communication systems), the frequency bands in use are increasing. Furthermore, the introduction of small cells has reduced the cell size of base stations, necessitating a large number of RUs. Additionally, as wireless communication systems develop and the volume of transmitted data increases, the transmission capacity of the wired network transmitted through the front haul (FH), the interface between the RU and the DU, has also increased significantly. Consequently, to reduce the installation costs of the wired network, a "function split" can be utilized to lower the transmission capacity of the front haul by having the RU perform some of the DU's functions. More specifically, to reduce the burden on the DU, the role of the RU, which previously handled only RF functions, can be expanded to include some functions of the physical layer.

[0082] Referring to FIG. 2, in the physical layer for the downlink in a 4G or 5G communication system, DL data is received at the MAC layer (236), channel coding and scrambling are performed on the received data (234), modulation is performed on the scrambling data (232), and layer mapping of the modulation symbols is performed (230). The modulation symbols mapped to each layer are mapped to each antenna port (228), and after being mapped to the corresponding resource element (RE, a unit of resource allocation consisting of one subcarrier and one symbol) (226), digital beamforming (which can be combined with precoding) is performed (224), and an Inverse Fast Fourier Transform (IFFT) is performed to transform the signal into a time domain signal, after which a Cyclic Prefix (CP) is added (222) and the signal is carried on the carrier frequency in RF (220) and transmitted to the terminal through the antenna.

[0083] Additionally, in the physical layer for the UL in a 4G or 5G communication system, a signal of the carrier frequency received through the antenna is converted from RF (240) to a baseband signal, the converted signal is transformed into a frequency domain signal (242) through CP removal and FFT, the applied digital beamforming is applied in reverse to combine the UL signal (244), the signal is demapped (246) from the RE where the UL signal was mapped to perform channel estimation (248), layer demapping (250) is performed to demodulate the aligned modulation symbols (252), and the bit sequence obtained from the demodulation result is descrambled and decoded to obtain information bits (254). Afterwards, the obtained information bits are transmitted to the MAC layer (256).

[0084] At this time, there are various options for the sublayer function division, and as examples, Option 6 (212), Option 7-3 (210), Option 7-2 (208), Option 7-2x Category B (202), Option 7-2x Category A (200), Option 7-1 (206), and Option 8 (204) are illustrated in FIG. 2. At this time, it can be understood that the function located to the right of an option is performed in the DU, and the function located to the left is performed in the RU. For example, the CPRI of an LTE system corresponds to Option 8, and in the case of DL, the signal in which all processes of the physical layer shown in FIG. 3 have been performed in the DU is transmitted to the RU via FH, and in the RU, only the process of converting the received signal into an analog signal and transmitting it to the terminal is performed. However, as the more functions performed in the DU, the greater the required fronthall bandwidth, the option 7-2x category B (202) and option 7-2x category A (200) may be supported in O-RAN.

[0085] Specifically, Category A (200) of Option 7-2x is a capability category of O-RU (110) that cannot process the precoding of data received by O-RU (110) from O-DU (120), and Category B (202) of Option 7-2x corresponds to a capability category of O-RU (110) that can process the precoding of data received by O-RU (110) from O-DU (120). O-DU (120) must support Category A O-RU (110) for eight transmission streams or fewer. That is, O-DU (120) can be said to support precoding up to eight transmission streams. At this time, when option 7-2x category B (202) is applied, the O-DU (120) transmits information about the modulation symbol and beamforming information, including layer mapping, to the O-RU (110), and the O-RU (110) applies beamforming to the modulation symbol, converts it into an analog signal, and transmits it to the terminal through the antenna.

[0086] There are four types of information that must be transmitted from the O-DU (120) to the O-RU (110) of option 7-2x. Information transmitted in the M-plane (management plane) is transmitted in a non-real-time manner in both directions between the DL and UL, and is information for initial setup or reset between the O-DU (120) and the O-RU (110). Information transmitted in the S-plane (synchronization-plane) is transmitted in real-time, and is information for synchronization or timing between the O-DU (120) and the O-RU (110). Information transmitted in the C-plane (control-plane) is transmitted in real-time in the direction of the DL, and is information for the O-DU (120) to control the transmission of I / Q data from the O-RU (110). Information transmitted from the U-plane (user-plane) is transmitted in real-time in both directions between the DL and UL, and includes DL frequency domain I / Q data (including SSB (synchronization signal block) and reference signals), and in the U-plane, UL frequency domain I / Q data (including reference signals such as sounding reference signals) and frequency domain I / Q data for the PRACH (physical random access channel). In this disclosure, such information or data may be used interchangeably with messages.

[0087] Figure 3 is a diagram showing the format of a message transmitted between the O-RU and the O-DU.

[0088] The O-RU and O-DU are connected via Ethernet. Referring to FIG. 3, the Ethernet message may include a Destination MAC address (310), a Source MAC Address (320), a VLAN (virtual LAN) Tag (330), a Type / Length (340), and a Payload (350). Furthermore, it may include a Preamble, a Frame Check Sequence (FCS), and an Inter Frame Gap (IFG).

[0089] The Destination MAC address (310) indicates the public address of the O-RU (110) or MMU (massive MIMO unit) in the case of DL, and the public address of a specific port of the channel card of the O-DU (120) in the case of UL (which can perform operations such as converting data formats according to the operation of the MAC (medium access control) layer responsible for scheduling, the operation of the high-PHY (upper physical layer), and the interface between the O-RU (110) and the O-DU (120)). The Source MAC Address (320) indicates the public address of the O-RU (110) or MMU in the case of UL, and the public address of a specific port of the channel card of the O-DU (120) in the case of DL.

[0090] The VLAN Tag (330) is 4 bytes and allows C, U, or S-plane messages to be mapped to different VLAN tags for management. The TPID (Tag protocol identifier) ​​included in the VLAN Tag can be set to a value of 0x8100, for example, 16 bits, to identify a frame as an IEEE 802.1Q tag frame. This field is located in the same position as the Ethertype / Length field in untagged frames, so it is used to distinguish untagged frames from regular frames.

[0091] The TCI (Tag control information) included in the VLAN Tag (330) can include, for example, the following three fields in 16 bits. The PCP (Priority code point) is 3 bits and represents the priority of the frame. The DEI (Drop eligible indicator) is 1 bit and is used separately from or in combination with the PCP to distinguish frames that should be dropped when traffic becomes congested. The VID (VLAN identifier) ​​is 12 bits and is a field indicating which frame belongs to which VLAN. All values ​​other than the reserved values ​​0x000 and 0xFFF are used as VLAN identifiers, and up to 4,094 VLANs are allowed. For example, the reserved value 0x000 indicates that the frame does not belong to any VLAN, in which case 802.1Q can specify only the priority and refer to it as the priority tag.

[0092] Type / Length (Ethertype) (340) is for eCPRI and can be set to a fixed value, for example, 0xAEFE.

[0093] The payload (350) may include a message according to each plane format including an eCPRI header. More specifically, the payload (350) includes a message in a format according to each plane, for example, the C-plane format including an eCPRI (enhanced CPRI) header and an O-RAN header is 330. Additionally, the payload (350) may include information in a format according to a U-plane or other plane.

[0094] The O-DU (120) can transmit a control plane signal to the O-RU (110) to indicate the beamforming method to be applied at the O-RU (110). The beamforming methods that can be applied include real-time weight beamforming (RTBF) and channel information based beamforming (CIBF). To instruct the O-RU (110) to perform uplink beamforming (uplink BF) operations, the O-DU (120) transmits a C-plane message containing a section type format or a section type format and a section extension format. For example, to instruct the O-RU (110) to perform CIBF, the O-DU (120) can transmit an indicator for the channel to be used for uplink beamforming operations by using Section Type 5 (ST 5) to indicate the UeId for the SRS (sound reference signal) channel. At this time, to simultaneously indicate multiple channels for uplink beamforming operation, Section Extension Type 10 (SE 10) may be added, or SE16 may be added to indicate additional antenna port mapping information.

[0095] However, the current O-RAN standard supports a maximum of 64 antenna ports, making it difficult to apply to systems that support more than that number. For example, since 6G communication systems consider 256 antenna ports, the current O-RAN standard may be difficult to apply to 6G communication systems. Additionally, while 8 bytes of information are currently used to support 64 antenna ports, the burden on the fronthaul increases if the data size exceeds this limit (e.g., 32 bytes). Furthermore, although there may be 2^64 possible cases to support the mapping of 64 antenna ports under the current O-RAN standard, it is practically difficult for the O-RU to support all of them; therefore, a method is required to convey an antenna port mapping method that the O-RU can support. The current O-RAN standard does not define an optional capability negotiation process for SE16, which poses difficulties in application. Accordingly, the present disclosure describes a method and apparatus for indicating antenna mapping information.

[0096] FIG. 4 is a diagram illustrating the process of transmitting management messages, control messages, and data between an O-RU and an O-DU according to one embodiment of the present disclosure.

[0097] Referring to FIG. 4, the O-RU (401) and O-DU (402) communicate via a fronthall interface (FH interface).

[0098] Referring to FIG. 4, in step 410, the O-RU (401) transmits an M-plane message to the O-DU (402). The M-plane message may contain information for initial setup or reset between the O-DU (402) and the O-RU (401). For example, the M-plane message may include O-RU initial setup, setup for providing management functions, and setup for C-plane messages and U-plane messages. In one embodiment, the M-plane message may include capability information of the O-RU (401). In one embodiment, the capability information of the O-RU (401) may include antenna information that the O-RU (401) can support. The M-plane message conveying this capability information may be transmitted during the initial setup process between the O-DU (402) and the O-RU (401), or it may be transmitted upon the occurrence of a specific event.

[0099] In step 420, the O-DU (402) can update scheduling information based on antenna information supported by the O-RU (401) included in the M-plane message received from the O-RU (401). For example, the scheduling strategy can be updated based on antenna information supported by the O-RU (401).

[0100] In step 430, the O-DU (402) may transmit an M-plane message to the O-RU (401). In one embodiment, the M-plane message may transmit an option preferred by the O-DU (402) to the O-RU (401) based on antenna information that the O-RU (401) can support. However, step 430 may be performed optionally and may not be performed.

[0101] In step 440, the O-DU (402) transmits a C-plane message containing scheduling information to the O-RU (401). The C-plane message may include a section type format for indicating antenna mapping information, or a section type format and a section extension format.

[0102] In step 450, the O-RU (401) can transmit a U-plane message to the O-DU (402). In one embodiment, the U-plane message may include received I / Q data based on antenna mapping information indicated in the C-plane message.

[0103] FIG. 5 is a flowchart illustrating a method performed by an O-DU according to one embodiment of the present disclosure.

[0104] Referring to FIG. 5, in step 510, the O-DU (distributed unit) of the base station receives a management message from at least one O-RU (radio unit) containing capability information related to the uplink antenna mapping of at least one O-RU. In one embodiment, the management message may include an M-plane message.

[0105] In one embodiment, capability information may indicate identification information for a supportable antenna group, information regarding the number of supportable antenna diversitys, and whether duplicated UE (user equipment) identification information is supported. The information included in the capability information will be described in detail below.

[0106] In step 520, the O-DU may generate a control message containing uplink antenna mapping information for at least one O-RU based on the capability information. The control message may include a C-plane message. In one embodiment, the control message may include a section type format for scheduling information and a section extension format containing one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

[0107] In one embodiment, the section type for scheduling information may include Section Type 5 (ST 5) of the O-RAN specification. However, this is merely an example and is not limited thereto, and the section type for scheduling information may include other Section Types of the O-RAN specification. The section type format for scheduling information may include antenna diversity count indication information based on duplicate UE identification information.

[0108] In one embodiment, the section extension format may include one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping, depending on the capability information received in step 510. Additionally, the section extension format may be used in conjunction with Section Extension Type 10 (SE 10) of the O-RAN specification. SE 10 is a section extension format regarding the group configuration of multiple ports (e.g., layer or Tx / Rx path). C-plane section information for multiple ports may include identical information, except for the beam ID or UE ID. If multiple ports share common section information at a single O-RU, they can be merged into a single C-plane section information through a single representative port using SE 10. In this case, M-Plane can perform port grouping by pre-configuring the representative port. Accordingly, SE 10 can group multiple ports using the representative port and efficiently merge C-Plane section information. In one embodiment, the section extension format may vary in form depending on whether it is used with SE 10. The section extension format will be described in detail below.

[0109] In step 530, the O-DU transmits the generated control message to at least one O-RU.

[0110] FIG. 6 is a flowchart illustrating a method performed by an O-RU according to one embodiment of the present disclosure.

[0111] In Fig. 6, the content that overlaps with that explained in Fig. 5 will be briefly explained.

[0112] Referring to FIG. 6, in step 610, the base station's O-RU (radio unit) can transmit a management message containing capability information related to the O-RU's uplink antenna mapping to the O-DU (distributed unit). In one embodiment, the management message may include an M-plane message.

[0113] In one embodiment, capability information may indicate identification information for a supportable antenna group, information regarding the number of supportable antenna diversitys, and whether duplicated UE (user equipment) identification information is supported. The information included in the capability information will be described in detail below.

[0114] In step 620, the O-RU may receive a control message containing uplink antenna mapping information for at least one O-RU generated based on the capability information. The control message may include a C-plane message. In one embodiment, the control message may include a section type format for scheduling information and a section extension format containing one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

[0115] In one embodiment, the section type for scheduling information may include Section Type 5 of the O-RAN specification. However, this is merely an example and is not limited thereto, and the section type for scheduling information may include other Section Types of the O-RAN specification. The section type format for scheduling information may include antenna diversity count indication information based on redundant UE identification information. In one embodiment, the section extension format may include one or more of antenna group indication information, antenna diversity indication information, or antenna diversity count indication information related to antenna mapping according to the capability information transmitted in step 610. The section extension format will be described in detail below.

[0116] In step 630, the O-RU can receive an uplink beam based on the control message it has generated.

[0117] FIGS. 7 and FIGS. 8 are section extension formats for indicating antenna mapping information according to one embodiment of the present disclosure.

[0118] FIG. 7 illustrates a section extension format when used alone, and FIG. 8 illustrates a section extension format when used with SE 10.

[0119] First, referring to FIG. 7, a section expansion format for indicating antenna mapping information according to one embodiment may include the following fields. The ef field indicates whether another section expansion format is subsequently included, and the extType field indicates the type of section expansion. For example, the extType field may indicate a section expansion message format according to one embodiment as extType = XX. The extLen field may indicate the length of the section expansion message format. The last field of the section expansion format may include padding bytes added to ensure data alignment.

[0120] In one embodiment, the antGroupID field included in the section expansion format includes antenna group indication information. The antenna group indication information may indicate information about the antenna group to be used for uplink beamforming in the corresponding layer.

[0121] The section extension format of FIG. 7 is a section extension format used alone and can indicate a single antenna group to be used in a layer indicated or identified by other information. More specifically, when identification information for a supported antenna group is set through an M-plane message, one of them can be indicated through a section extension format (e.g., extType XX) included in a C-plane message. The identification information for a supported antenna group set through an M-plane message will be described in detail with reference to FIG. 9.

[0122] Referring to FIG. 8, a section expansion format for indicating antenna mapping information according to one embodiment may include an ef field, an extType field, and an extLen field. The section expansion format of FIG. 8 is a section expansion format used with SE 10 and includes one or more antGroupID fields. Each antGroupID field may indicate information about an antenna group to be used for uplink beamforming in a corresponding layer. As described above, when identification information for a supported antenna group is set through an M-plane message, one of them may be indicated through a section expansion format (e.g., extType XX) included in a C-plane message.

[0123] In one embodiment, the section extension format used with SE 10 may include numPortC + 1 antGroupID field. Here, numPortC is a value included in SE 10 and represents the number of eAxC ports indicated by SE 10. numPortC may indicate up to 64 eAxC ports. However, it is not limited thereto, and the maximum value of numPortC may vary according to O-RAN specifications. The value of the extLen field may vary depending on the number of antGroupID fields.

[0124] FIG. 9 is a drawing showing an M-plane setting according to one embodiment of the present disclosure.

[0125] Referring to FIG. 9, capability information transmitted via an M-Plane message is illustrated. supported-section-types is configuration information for section types supported by the O-RU and may include a section-type indicating the section types supported by the O-RU and supported-section-extensions indicating section extensions supported by the O-RU that can be used with the section types. In one embodiment, supported-antenna-group-id is identification information for a supported antenna group and may include an antenna-group-id indicating an antenna group ID and an antenna-mask indicating the antennas supported by the antenna-group-id. As described above, since numPortC can indicate up to 64 eAxC ports, antenna-mask can also indicate up to 64. This will be explained in more detail in FIG. 10.

[0126] FIG. 10 is a drawing for illustrating identification information for a supportable antenna group according to one embodiment of the present disclosure.

[0127] Referring to FIG. 10, the O-RU can support 8 antennas (e.g., antennas 0-7) and 6 antenna groups formed by combining the 8 antennas. Each antenna group is assigned an ant-group-id (e.g., 0-5) and may include one or more different antennas. For example, ant-group id 0 may include all antennas 0-7, and ant-group id 3 may include antennas 0, 1, 3, and 7.

[0128] The antennas included in the antenna group can be indicated by an antenna-mask, and the antenna-mask can be indicated by a bitmap equal to the number of antennas. In this case, the bit corresponding to the antenna included in the antenna group can be indicated as 1, and the bit corresponding to the antenna not included can be indicated as 0.

[0129] As described above, when the O-RU sets identification information for a supported antenna group to the O-DU using capability information included in an M-plane message, the O-DU can indicate an antenna group to be used for uplink beamforming using a section expansion format according to one embodiment included in a C-plane message. For example, if the O-RU informs the O-DU via an M-plane message of an antenna-group-id indicating six antenna group IDs and an antenna-mask indicating the antenna supported by each antenna-group-id, as shown in FIG. 10, the O-DU can instruct the O-RU to select one of the antenna-group-ids and use it for uplink beamforming.

[0130] FIG. 11 is a diagram illustrating the transmission of a C-plane message and a U-plane message according to one embodiment of the present disclosure.

[0131] Referring to FIG. 11, the process of indicating an antenna group using a section expansion format when used alone, that is, the section expansion format described in FIG. 7, is illustrated. More specifically, the O-DU transmits three C-plane messages to the O-RU, each containing an ST 5 format and an SE XX format according to one embodiment. By transmitting the three C-plane messages, the O-DU can indicate a 3Rx antenna mapping.

[0132] O-DU first instructs that beamforming be performed on UE-A using the antennas included in antGroupId 0, using ST 5 indicating UE-A and SE XX indicating antGroupId=0. Then, O-DU instructs that beamforming be performed on UE-B using the antennas included in antGroupId 2, using ST 5 indicating UE-B and SE XX indicating antGroupId=2, and instructs that beamforming be performed on UE-B using the antennas included in antGroupId 4, using ST 5 indicating UE-B and SE XX indicating antGroupId=4.

[0133] The O-RU can receive uplink data through 3Rx, that is, 3 reception paths, as indicated by 3 C-plane messages, and transmit the I / Q data received through each reception path to the O-DU via U-plane messages. In this case, the O-RU is assigned one antGroupId for UE-A and receives uplink data through one reception path, but is assigned two antGroupIds for UE-B and receives uplink data through two reception paths. That is, the O-RU can receive uplink data for UE-B through two antenna diversitys.

[0134] In one embodiment, the order of the three C-plane messages may be changed by the Ethernet protocol. However, since antGroupId clearly designates a specific antenna, uplink data can be received even if the order of the C-planes is changed.

[0135] FIG. 12 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0136] Referring to FIG. 12, the process of indicating an antenna group using a section expansion format used with SE 10, namely the section expansion format described in FIG. 8, is illustrated. More specifically, the O-DU transmits a C-plane message to the O-RU containing the ST 5 format, the SE 10 format, and the SE XX format according to one embodiment. Here, ST 5 indicates UE-A, SE 10 indicates two UE-Bs, and SE XX indicates antGroupId=0, 2, 4. By using the SE 10 format, the O-DU can indicate 3Rx antenna mapping with a single C-plane message.

[0137] The three UE IDs indicated by ST 5 and SE 10, namely UE-A, UE-B, and UE-B, correspond sequentially to antGroupId 0, 2, and 4 included in SE XX. That is, the O-DU can instruct to perform beamforming for UE-A using the antennas included in antGroupId 0, and to perform beamforming for UE-B using the antennas included in antGroupId 2 and 4.

[0138] The O-RU can receive uplink data through 3 Rx, that is, 3 receive paths, indicated by a single C-plane message, and transmit the I / Q data received through each receive path to the O-DU through a U-plane message. In this case, for UE-A, the O-RU is assigned one antGroupId and receives uplink data through one receive path. For UE-B, by indicating two UE-Bs in SE 10, it can receive uplink data through 2 Rx, that is, 2 receive paths. In other words, the O-RU can receive uplink data for UE-B through two antenna diversitys.

[0139] FIGS. 11 and FIGS. 12 differ in whether SE 10 is used, but both indicate 3Rx antenna mapping, indicating antGroupId 0 for UE-A and antGroupIds 2 and 4 for UE-B. Refer to FIG. 13 for a more detailed explanation.

[0140] FIG. 13 is a drawing showing antenna mapping according to one embodiment of the present disclosure.

[0141] Referring to FIG. 13, which is a diagram for explaining antenna mapping according to the method illustrated in FIG. 11 and 12, illustrates antenna mapping when receiving uplink data using 3Rx. In FIG. 13, layer 1 is the layer corresponding to UE-A in FIG. 11 and 12, and layer 2 is the layer corresponding to UE-B in FIG. 11 and 12. In FIG. 11 and 12, UE-A receives the uplink using 1Rx corresponding to layer 1. At this time, for UE-A, antGroupId 0 is indicated, and uplink data is received using antennas (or antenna ports) included in antGroupId 0. In FIG. 11 and 12, UE-B is 1 of layer 2 st Rx and 2 nd Uplink is received using 2Rx corresponding to Rx. At this time, for UE-B, antGroupId 2 and 4 are specified, and uplink data is received using antennas (or antenna ports) included in antGroupId 2 and 4.

[0142] According to one embodiment, even when performing antenna mapping as shown in FIG. 13, the method by which the O-DU instructs the O-RU to provide antenna mapping information may differ depending on whether SE 10 is used.

[0143] FIGS. 14 and FIGS. 15 are section extension formats for indicating antenna mapping information according to another embodiment of the present disclosure.

[0144] FIG. 14 illustrates a section extension format when used alone, and FIG. 15 illustrates a section extension format when used with SE 10.

[0145] First, referring to FIG. 14, a section expansion format for indicating antenna mapping information according to one embodiment may include the following fields. The ef field indicates whether another section expansion format is subsequently included, and the extType field indicates the type of section expansion. For example, the extType field may indicate the section expansion message format according to one embodiment as extType = YY. The extLen field may indicate the length of the section expansion message format. Additional padding bytes may be added to the last field of the section expansion format to align the data.

[0146] In one embodiment, the antDiversityId field included in the section extension format includes antenna diversity instruction information. The antenna diversity instruction information may include at least one identification information indicating the number and order of antenna diversity. The antenna diversity instruction information may indicate information related to the antenna to be used for uplink beamforming in the corresponding layer.

[0147] The section extension format of FIG. 14 is a section extension format used alone and can indicate information related to antennas to be used in a layer indicated or identified by other information. More specifically, when information regarding the number of supported antenna diversitys is set through an M-plane message, at least one identification information indicating the number and order of antenna diversitys can be indicated through a section extension format (e.g., extType YY) included in a C-plane message. The at least one identification information indicating the number and order of supported antenna diversitys set through the M-plane message will be described in detail with reference to FIG. 17 and FIG. 18.

[0148] Referring to FIG. 15, a section extension format for indicating antenna mapping information according to one embodiment may include an ef field, an extType field, and an extLen field. The section extension format of FIG. 15 is a section extension format used with SE 10 and includes one or more antDiversityId fields. Each antDiversityId field may indicate at least one identification information indicating the number and order of antenna diversity. As described above, once information regarding the number of supported antenna diversity is set through an M-plane message, the number and order of antenna diversity can be indicated through a section extension format (e.g., extType YY) included in a C-plane message.

[0149] In one embodiment, the section extension format used with SE 10 may include numPortC + 1 antDiversityId field. Here, numPortC is a value included in SE 10 and represents the number of eAxC ports indicated by SE 10. numPortC may indicate up to 64 eAxC ports. However, it is not limited thereto, and the maximum value of numPortC may vary according to O-RAN specifications. The value of the extLen field may vary depending on the number of antDiversityId fields.

[0150] FIG. 16 is a drawing showing an M-plane setting according to another embodiment of the present disclosure.

[0151] Referring to FIG. 16, capability information transmitted via an M-Plane message is illustrated. supported-section-types is configuration information for section types supported by the O-RU, and may include a section-type indicating a section type supported by the O-RU and supported-section-extensions indicating a section extension supported by the O-RU that can be used with the section type.

[0152] In one embodiment, the supported-seYY-bitmap may include information about the number of supported antenna diversitys.

[0153] FIG. 17 is a drawing for explaining a method for setting the number of supportable antenna diversity according to one embodiment of the present disclosure.

[0154] Referring to FIG. 17, the O-RU can set the number of diversity supported by the bitmap. The bitmap can be configured such that the number of bits increases as the number of Rx increases, with 1Rx as the LSB (list significant bit). For example, if the entire system supports 16Rx, the supported-seYY-bitmap can be configured as a 16-bit bitmap, and if the O-RU supports 2Rx and 1Rx as in FIG. 17, the supported-seYY-bitmap can be indicated as 00000000 00000011.

[0155] FIG. 18 is a drawing for explaining identification information indicating the number and order of antenna diversity according to one embodiment of the present disclosure.

[0156] Referring to FIG. 18, an antDiversityId that can be indicated in SE YY format is illustrated. The antDiversityId value is assigned 0 to 1Rx and has sequentially larger values ​​as the number of Rx, i.e., reception paths increases, and a number of values ​​equal to the number of Rx are sequentially assigned to each Rx to indicate the diversity order. For example, since 1Rx has one reception path, one value, i.e., 0, is assigned, and since 2Rx has two reception paths, two values ​​are assigned, but 1 and 2 are assigned sequentially increasing following the 0 assigned to 1Rx. In the same way, since 3Rx has three reception paths, three values ​​are assigned, but 3, 4, and 5 are assigned sequentially increasing following the largest value, 2, assigned to the previous 2Rx. In this way, an antDiversityId can be assigned to indicate the number and order of antenna diversity up to 16Rx. This method of assigning antDiversityId may be pre-configured for the O-RU and O-DU.

[0157] Although FIG. 18 illustrates assigning 0 to 1Rx, this is merely an example and is not limited thereto. AntDiversityId can be assigned in various ways, such as assigning the largest value to 1Rx or assigning values ​​that decrease sequentially.

[0158] FIG. 19 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0159] Referring to FIG. 19, the process of indicating an antenna group using a section expansion format when used alone, that is, the section expansion format described in FIG. 14, is illustrated. More specifically, the O-DU transmits three C-plane messages to the O-RU, each containing an ST 5 format and an SE YY format according to one embodiment. By transmitting the three C-plane messages, the O-DU can indicate a 3Rx antenna mapping.

[0160] O-DU first instructs that beamforming be performed on UE-A using the antennas indicated by antDiversityId 0, using ST 5 indicating UE-A and SE YY indicating antDiversityId=0. Then, O-DU instructs that beamforming be performed on UE-B using the antennas indicated by antDiversityId 2, using ST 5 indicating UE-B and SE YY indicating antDiversityId=2, and instructs that beamforming be performed on UE-B using the antennas indicated by antDiversityId 4, using ST 5 indicating UE-B and SE YY indicating antDiversityId=4.

[0161] The O-RU can receive uplink data through 3Rx, that is, 3 reception paths, as indicated by 3 C-plane messages, and transmit the I / Q data received through each reception path to the O-DU via U-plane messages. In this case, the O-RU receives uplink data through one reception path with one antDiversityId assigned to UE-A, but receives uplink data through two reception paths with two antDiversityIds assigned to UE-B. That is, the O-RU can receive uplink data from UE-B through two antenna diversitys.

[0162] In one embodiment, the order of the three C-plane messages may be changed by the Ethernet protocol. However, since antDiversityId clearly designates a specific antenna, uplink data can be received even if the order of the C-planes is changed.

[0163] FIG. 20 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0164] Referring to FIG. 20, the process of indicating an antenna group using a section expansion format used with SE 10, namely the section expansion format described in FIG. 15, is illustrated. More specifically, the O-DU transmits a C-plane message to the O-RU containing the ST 5 format, the SE 10 format, and the SE YY format according to one embodiment. Here, ST 5 indicates UE-A, SE 10 indicates two UE-Bs, and SE YY indicates antDiversityId=0, 2, 4. By using the SE 10 format, the O-DU can indicate 3Rx antenna mapping with a single C-plane message.

[0165] The three UE Ids indicated by ST 5 and SE 10, namely UE-A, UE-B, and UE-B, correspond sequentially to antDiversityId 0, 2, and 4 included in SE YY. That is, O-DU can instruct to perform beamforming for UE-A using the antennas indicated by antDiversityId 0, and to perform beamforming for UE-B using the antennas indicated by antDiversityId 2 and 4.

[0166] The O-RU can receive uplink data through 3 Rx, that is, 3 receive paths, indicated by a single C-plane message, and transmit the I / Q data received through each receive path to the O-DU via a U-plane message. In this case, for UE-A, the O-RU is assigned one antDiversityId and receives uplink data through one receive path. For UE-B, by indicating two UE-Bs in SE 10, it can receive uplink data through 2 Rx, that is, 2 receive paths. In other words, the O-RU can receive uplink data for UE-B through two antenna diversitys.

[0167] FIGS. 19 and FIGS. 20 differ in whether SE 10 is used, but both indicate 3Rx antenna mapping, indicating antDiversityId 0 for UE-A and antDiversityId 2 and 4 for UE-B. Refer to FIG. 21 for a more detailed explanation.

[0168] FIG. 21 is a drawing showing antenna mapping according to another embodiment of the present disclosure.

[0169] Referring to FIG. 21, which is a diagram illustrating antenna mapping according to the method illustrated in FIG. 19 and FIG. 20, it illustrates antenna mapping when receiving uplink data using 3Rx. FIG. 21(a) and FIG. 21(b) differ in the antenna mapping relationship for layer 2. When the number and order of multiple antenna diversitys are indicated through antDiversityId, even though it is possible to indicate which layer antDiversityId is mapped to, it is difficult to know which antenna antDiversityId is mapped to. For example, in FIG. 21(a), layer 2's 1 st Rx is mapped to the top 4 antennas out of the 8 antennas, and layer 2's 2 nd Rx is mapped to the bottom 4 antennas out of the 8 antennas. In comparison, in Fig. 21(b), layer 2's 1 st Rx is mapped to the 4 odd-numbered antennas from the top out of the 8 antennas, and layer 2's 2 nd Rx is mapped to the four even-numbered antennas from the top out of the eight antennas. As such, the method of specifying the number and order of multiple antenna diversitys via the antDiversityId included in the C-plane message can specify a layer, but it cannot specify the antennas mapped to that layer. However, the mapping relationship between each layer and antenna may be configured internally within the O-RU. Therefore, uplink data can be received even if the antDiversityId does not specify a particular antenna.

[0170] In FIG. 21, layer 1 is the layer corresponding to UE-A in FIG. 19 and 20, and layer 2 is the layer corresponding to UE-B in FIG. 19 and 20. In FIG. 19 and 20, UE-A receives the uplink using 1Rx corresponding to layer 1. At this time, for UE-A, antDiversityId 0 is indicated, and uplink data is received using the antennas (or antenna ports) indicated by antDiversityId 0. In FIG. 19 and 20, UE-B is 1 of layer 2 st Rx and 2 nd Uplink is received using 2Rx corresponding to Rx. At this time, for UE-B, antDiversityId 2 and 4 are indicated, and uplink data is received using antennas included in antDiversityId 2 and 4.

[0171] According to one embodiment, even when performing antenna mapping as shown in FIG. 21, the method by which the O-DU instructs the O-RU to provide antenna mapping information may differ depending on whether SE 10 is used.

[0172] FIGS. 22 and FIGS. 23 are section extension formats for indicating antenna mapping information according to another embodiment of the present disclosure.

[0173] FIG. 22 illustrates a section extension format when used alone, and FIG. 23 illustrates a section extension format when used with SE 10.

[0174] First, referring to FIG. 22, a section expansion format for indicating antenna mapping information according to one embodiment may include the following fields. The ef field indicates whether another section expansion format is subsequently included, and the extType field indicates the type of section expansion. For example, the extType field may indicate the section expansion message format according to one embodiment as extType = ZZ. The extLen field may indicate the length of the section expansion message format. Additional padding bytes may be added to the last field of the section expansion format to align the data.

[0175] In one embodiment, the numDiversity field included in the section expansion format includes information regarding antenna diversity count indication information. The antenna diversity count indication information may indicate information related to the number of Rx, i.e., the number of receiving paths, to be used for uplink beamforming in the corresponding layer.

[0176] The section extension format of FIG. 22 is a section extension format used alone and can indicate the number of antenna diversity to be used in a layer indicated or identified by other information. More specifically, when information regarding the number of supported antenna diversity is set through an M-plane message, the number of antenna diversity can be indicated through a section extension format (e.g., extType YY) included in a C-plane message. Information regarding the number of supported antenna diversity set through an M-plane message will be explained in detail with reference to FIG. 25.

[0177] Referring to FIG. 23, a section extension format for indicating antenna mapping information according to one embodiment may include an ef field, an extType field, and an extLen field. The section extension format of FIG. 15 is a section extension format used with SE 10 and includes one or more numDiversity fields. Each numDiversity field may indicate the number of antenna diversitys. As described above, once information regarding the number of supported antenna diversitys is set through an M-plane message, the number of antenna diversitys may be indicated through a section extension format (e.g., extType YY) included in a C-plane message.

[0178] In one embodiment, the section extension format used with SE 10 may include numPortC + 1 numDiversity field. Here, numPortC is a value included in SE 10 and represents the number of eAxC ports indicated by SE 10. numPortC may indicate up to 64 eAxC ports. However, it is not limited thereto, and the maximum value of numPortC may vary according to O-RAN specifications. The value of the extLen field may vary depending on the number of numDiversity fields.

[0179] FIG. 24 is a drawing showing an M-plane setting according to another embodiment of the present disclosure.

[0180] Referring to FIG. 24, capability information transmitted via an M-Plane message is illustrated. supported-section-types is configuration information for section types supported by the O-RU, and may include a section-type indicating a section type supported by the O-RU and supported-section-extensions indicating a section extension supported by the O-RU that can be used with the section type.

[0181] In one embodiment, supported-seZZ-bitmap may include information regarding the number of supported antenna diversitys. Additionally, support-duplicated-ueid-wo-seZZ may indicate whether duplicated UE (user equipment) identification information is supported. If SE 10 is used and support-duplicated-ueid-wo-seZZ indicates that duplicated UE identification information is supported, the number of duplicate UE IDs in SE 10 can be determined as the number of antenna diversitys transmitted to numDiversity. In this case, the number of antenna diversitys may be indicated using only the section type for scheduling information (e.g., ST 5) and SE 10, without the section extension format for indicating antenna mapping information illustrated in FIGS. 22 and 23.

[0182] FIG. 25 is a drawing for explaining a method for setting the number of supportable antenna diversity according to another embodiment of the present disclosure.

[0183] Referring to FIG. 25, the O-RU can set the number of diversity supported by the bitmap. The bitmap can be configured such that the number of bit places increases as the number of Rx increases, with 1Rx as the LSB (list significant bit). For example, if the entire system supports 16Rx, the supported-seZZ-bitmap can be configured as a 16-bit bitmap, and if the O-RU supports 2Rx and 1Rx as in FIG. 25, the supported-seZZ-bitmap can be indicated as 00000000 00000011.

[0184] FIG. 26 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0185] Referring to FIG. 26, the process of indicating the number of antenna diversity using a section expansion format when used alone, that is, the section expansion format described in FIG. 22, is illustrated. More specifically, the O-DU transmits three C-plane messages to the O-RU, each containing an ST 5 format and an SE ZZ format according to one embodiment. By transmitting the three C-plane messages, the O-DU can indicate 3Rx antenna mapping.

[0186] The O-DU first instructs that beamforming be performed on UE-A using the antennas indicated by numDiversity 1, using ST 5 indicating UE-A and SE ZZ indicating numDiversity=1. Then, the O-DU instructs that beamforming be performed on UE-B using the antennas indicated by numDiversity 2, using ST 5 indicating UE-B and SE ZZ indicating numDiversity=2, and once again instructs that beamforming be performed on UE-B using the antennas indicated by numDiversity 2, using ST 5 indicating UE-B and SE ZZ indicating numDiversity=2. g

[0187] The O-RU receives uplink data through 3Rx, i.e., 3 reception paths, as indicated by 3 C-plane messages, and can transmit the I / Q data received through each reception path to the O-DU via U-plane messages. In this case, the O-RU is assigned one numDiversity for UE-A to receive uplink data through one reception path, but is assigned two numDiversities for UE-B to receive uplink data through two reception paths. That is, the O-RU can receive uplink data for UE-B through two antenna diversitys. However, in the case of SE ZZ, only the number of diversitys is indicated, and information regarding which layer to use, such as the diversity order, is not transmitted. In one embodiment, the diversity order can be determined according to the order included in the eAxC Id list. For example, information transmitted to the layer having the eAxC ID with a faster index in the eAxC Id list can be mapped to the faster Rx within the layer. In this case, uplink data can be received even if the order of C-plane messages is changed by the Ethernet protocol.

[0188] FIG. 27 is a diagram illustrating the transmission of C-plane messages and U-plane messages according to another embodiment of the present disclosure.

[0189] Referring to FIG. 27, the process of indicating the number of antenna diversity using a section expansion format used with SE 10, that is, the section expansion format described in FIG. 23, is illustrated. More specifically, the O-DU transmits a C-plane message to the O-RU that includes the ST 5 format, the SE 10 format, and the SE ZZ format according to one embodiment. Here, ST 5 indicates UE-A, SE 10 indicates two UE-Bs, and SE ZZ indicates numDiversity=1, 2, 2. By using the SE 10 format, the O-DU can indicate 3Rx antenna mapping with one C-plane message.

[0190] The three UE IDs indicated by ST 5 and SE 10, namely UE-A, UE-B, and UE-B, correspond sequentially to numDiversity 1, 2, and 2 included in SE ZZ. That is, O-DU can instruct to perform beamforming for UE-A using the antennas indicated by numDiversity 0, and to perform beamforming for UE-B using the antennas indicated by numDiversity 2 and 2. At this time, as explained above, SE ZZ only indicates the number of diversity values ​​and does not convey information regarding which layer to use, such as the diversity order. In one embodiment, the diversity order can be determined according to the order included in the eAxC ID list.

[0191] The O-RU can receive uplink data through 3 Rx, that is, 3 reception paths, indicated by a single C-plane message, and transmit the I / Q data received through each reception path to the O-DU via a U-plane message. In this case, for UE-A, the O-RU is assigned one numDiversity and receives uplink data through one reception path. For UE-B, by indicating 2 UE-Bs in SE 10, it can receive uplink data through 2 Rx, that is, 2 reception paths. In other words, the O-RU can receive uplink data for UE-B through 2 antenna diversitys.

[0192] FIGS. 26 and FIGS. 27 differ in whether SE 10 is used, but both indicate 3Rx antenna mapping, and indicate numDiversity 1 for UE-A and numDiversity 2 for UE-B. Refer to FIG. 28 for a more detailed explanation.

[0193] Furthermore, in one embodiment, when SE 10 is used and support-duplicated-ueid-wo-seZZ indicates that duplicate UE identification information is supported, the number of duplicate UE IDs in SE 10 can be determined as the number of antenna diversity transmitted to numDiversity. In this case, the number of antenna diversity may be indicated with only the section type for scheduling information (e.g., ST 5) and SE 10 without SE ZZ.

[0194] FIG. 28 is a drawing showing antenna mapping according to another embodiment of the present disclosure.

[0195] Referring to FIG. 28, which is a diagram illustrating antenna mapping according to the method illustrated in FIG. 26 and FIG. 27, it illustrates antenna mapping when receiving uplink data using 3Rx. FIG. 28(a) and FIG. 28(b) differ in the antenna mapping relationship for layer 2. When the number of multiple antenna diversitys is indicated via numDiversity, only the number of diversitys is known, and information regarding which layer to use, such as the diversity order, is not conveyed. In one embodiment, the diversity order can be determined according to the order included in the eAxC ID list. For example, information transmitted to the layer having the eAxC ID with a faster index in the eAxC ID list can be mapped to the faster Rx within the layer. However, even in this case, it is difficult to know which Rx is mapped to which antenna. For example, in FIG. 21(a), layer 2's 1 st Rx is mapped to the top 4 antennas out of the 8 antennas, and layer 2's 2 nd Rx is mapped to the bottom 4 antennas out of the 8 antennas. In comparison, in Fig. 21(b), layer 2's 1 st Rx is mapped to the 4 odd-numbered antennas from the top out of the 8 antennas, and layer 2's 2 nd Rx is mapped to the 4 even-numbered antennas from the top out of the 8 antennas. Even though numDiversity=2 indicates that the number of diversity elements in layer 2 is 2, the RU indicates that a specific terminal is layer 2's 1 st Whether assigned to Rx, layer 2's 2 ndIt is not possible to know if it is assigned to Rx. Furthermore, it is difficult to determine which antenna is mapped to the corresponding layer. However, the mapping relationship between each layer and antenna may be configured internally by the O-RU. Therefore, uplink data can be received even if numDiversity does not indicate a specific antenna.

[0196] In FIG. 28, layer 1 corresponds to the layer corresponding to UE-A in FIG. 26 and 27, and layer 2 corresponds to the layer corresponding to UE-B in FIG. 26 and 27. In FIG. 26 and 27, UE-A receives the uplink using 1Rx corresponding to layer 1. At this time, for UE-A, numDiversity 0 is indicated, and uplink data is received using the antennas (or antenna ports) indicated by numDiversity 0. In FIG. 26 and 27, UE-B is 1 of layer 2 st Rx and 2 nd Receive the uplink using 2Rx corresponding to Rx.

[0197] According to one embodiment, even when performing antenna mapping as shown in FIG. 21, the method by which the O-DU instructs the O-RU to provide antenna mapping information may differ depending on whether SE 10 is used.

[0198] FIG. 29 is a drawing showing the configuration of an O-RU according to one embodiment of the present disclosure.

[0199] Referring to FIG. 29, the base station's O-RU (110) includes a transceiver (2910), a connection unit (2920), a storage unit (2930), and a control unit (2940). However, the components of the base station's O-RU (110) are not limited to these, and the O-RU (110) may include more or fewer components than those shown. In addition, the transceiver (2910), the connection unit (2920), the storage unit (2930), and the control unit (2940) may be implemented in the form of a single chip.

[0200] The transceiver (2910) can transmit and receive signals with a terminal. Here, the signal may include control information and data. To this end, the transceiver (2910) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (2910), and the components of the transceiver (2910) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (2910) may receive a signal through a wireless channel and output it to a control unit (2940), and transmit the signal output from the control unit (2940) through a wireless channel. Furthermore, the transceiver (2910) may separately provide an RF transceiver for an LTE system and an RF transceiver for an NR system, or perform physical layer processing for LTE and NR with a single transceiver. Furthermore, the transmitting and receiving unit (2910) may include communication circuitry.

[0201] The connection unit (2920) is a device that connects the base station's O-RU (110) and O-DU (120), and can perform physical layer processing for message transmission and reception, as well as the operation of transmitting messages to the base station's O-DU (120) and receiving messages from the O-DU (120). The connection unit (2920) may include a fronthole interface unit.

[0202] The storage unit (2930) can store programs and data necessary for the operation of the O-RU (110). Additionally, the storage unit (2930) can store control information or data included in signals transmitted and received by the O-RU (110). The storage unit (2930) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple storage units (2930).

[0203] The control unit (2940) can control a series of processes to enable the O-RU (110) of the base station to operate according to the embodiment of the present disclosure described above. For example, the control unit (2940) can transmit and receive LTE or NR signals to and from a terminal according to C-plane messages and U-plane messages received from the O-DU (120) of the base station through the fronthall interface unit (2920). The control unit (2940) may include at least one processor. The control unit (2940) may be multiple, and the control unit (2940) can perform component control operations of the O-RU (110) of the base station by executing a program stored in the storage unit (2930).

[0204] In one embodiment, the control unit (2940) receives a management message from at least one O-RU (radio unit) containing capability information related to uplink antenna mapping of at least one O-RU, generates a control message containing uplink antenna mapping information for at least one O-RU based on the capability information, and controls the transmission of the generated control message to at least one O-RU. The control message may include a section type format for scheduling information and a section extension format including one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

[0205] In one embodiment, capability information includes identification information for a supported antenna group, and the section extension format may include antenna group indication information.

[0206] In one embodiment, capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include at least one identification information indicating the number and order of antenna diversitys.

[0207] In one embodiment, capability information includes information on the number of supported antenna diversitys, and the section extension format may include antenna diversity number indication information.

[0208] In one embodiment, capability information includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and the section type format for scheduling information may include antenna diversity number indication information based on duplicated UE identification information.

[0209] FIG. 30 is a drawing showing the configuration of an O-DU according to one embodiment of the present disclosure.

[0210] Referring to FIG. 30, the base station's O-DU (120) includes a connection unit (3010), a storage unit (3020), and a control unit (3030). However, the components of the base station's O-DU (120) are not limited to these, and the O-DU (120) may include more or fewer components than those shown. In addition, the fronthole interface unit (3010), the storage unit (3020), and the control unit (3030) may be implemented in the form of a single chip.

[0211] The connection unit (3010) is a device that connects the base station's O-RU (110) and O-DU (120), and can perform physical layer processing for message transmission and reception, as well as the operation of transmitting messages to the base station's O-RU (110) and receiving messages from the O-RU (110). The connection unit (3010) may include a fronthole interface unit.

[0212] The storage unit (3020) can store programs and data necessary for the operation of the O-RU (110). Additionally, the storage unit (3020) can store control information or data included in signals transmitted and received by the O-RU (110). The storage unit (3020) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple storage units (3020).

[0213] The control unit (3030) can control a series of processes to enable the O-DU (120) of the base station to operate according to the embodiment of the present disclosure described above. For example, the control unit (3030) can generate C-plane messages and U-plane messages to be transmitted to the O-RU (110) of the base station and transmit the messages to the O-RU (110) of the base station through the fronthole interface unit (3010). There may be multiple control units (3030), and the control unit (3030) can perform component control operations of the O-DU (120) of the base station by executing a program stored in the storage unit (3020).

[0214] In one embodiment, the control unit (3030) transmits a management message containing capability information related to the uplink antenna mapping of an O-RU to a distributed unit (O-DU), receives a control message from the O-DU containing uplink antenna mapping information for at least one O-RU generated based on the capability information, controls the receiving of an uplink beam based on the generated control message, and the control message may include a section type format for scheduling information and a section extension format including one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

[0215] In one embodiment, capability information includes identification information for a supported antenna group, and the section extension format may include antenna group indication information.

[0216] In one embodiment, capability information includes information regarding the number of supported antenna diversitys, and the section expansion format may include at least one identification information indicating the number and order of antenna diversitys.

[0217] In one embodiment, capability information includes information on the number of supported antenna diversitys, and the section extension format may include antenna diversity number indication information.

[0218] In one embodiment, capability information includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and the section type format for scheduling information may include antenna diversity number indication information based on duplicated UE identification information.

[0219] Meanwhile, the order of description in the drawings illustrating the method proposed in this disclosure does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel. Alternatively, the drawings illustrating the method proposed in this disclosure may omit some components and include only some components to the extent that the essence of this disclosure is not compromised.

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

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

[0222] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0223] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or 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 through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0224] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0225] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. In a wireless communication system, a method performed by an O-DU (distributed unit) of a base station, A step of receiving a management message from at least one O-RU (radio unit) that includes capability information related to the uplink antenna mapping of said at least one O-RU; Based on the above capability information, a step of generating a control message including uplink antenna mapping information for at least one O-RU; and The method includes the step of transmitting the control message generated above to at least one O-RU, The above control message is, A method characterized by including a section type format for scheduling information and a section extension format including one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

2. In Paragraph 1, The above ability information is, Includes identification information for supported antenna groups, and The above section extension format is, A method characterized by including the above antenna group instruction information.

3. In Paragraph 1, The above ability information is, Includes information on the number of supported antenna diversity, The above section extension format is, A method characterized by including at least one identification information indicating the number and order of antenna diversity and at least one of the antenna diversity number indication information.

4. In Paragraph 1, The above ability information is, It includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and The section type format for the above scheduling information is, A method characterized by including antenna diversity count indication information based on duplicate UE identification information.

5. In a wireless communication system, a method performed by the O-RU (radio unit) of a base station, A step of transmitting a management message containing capability information related to the uplink antenna mapping of the above O-RU to the O-DU (distributed unit); A step of receiving a control message from the above O-DU, the control message including uplink antenna mapping information for at least one O-RU generated based on the capability information; and The method includes the step of receiving an uplink beam based on the control message generated above, and The above control message is, A method characterized by including a section type format for scheduling information and a section extension format including one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

6. In Paragraph 5, The above ability information is, Includes identification information for supported antenna groups, and The above section extension format is, A method characterized by including the above antenna group instruction information.

7. In Paragraph 5, The above ability information is, Includes information on the number of supported antenna diversity, The above section extension format is, A method characterized by including at least one identification information indicating the number and order of antenna diversity and at least one of the antenna diversity number indication information.

8. In Paragraph 5, The above ability information is, It includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and The section type format for the above scheduling information is, A method characterized by including antenna diversity count indication information based on duplicate UE identification information.

9. In a distributed unit (O-DU) device of a base station in a wireless communication system, A fronthaul interface unit configured to transmit and receive signals with an O-RU (radio unit); and It includes at least one control unit, and The above control unit is, Receiving a management message from at least one O-RU (radio unit) that includes capability information related to the uplink antenna mapping of said at least one O-RU, and Based on the above capability information, a control message is generated that includes uplink antenna mapping information for at least one O-RU, and Control to transmit the control message generated above to at least one O-RU, and The above control message is, A device characterized by including a section type format for scheduling information and a section extension format including one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

10. In Paragraph 9, The above ability information is, Includes identification information for supported antenna groups, and The above section extension format is, A device characterized by including the above antenna group instruction information.

11. In Paragraph 9, The above ability information is, Includes information on the number of supported antenna diversity, The above section extension format is, A device characterized by including at least one identification information indicating the number and order of antenna diversity and at least one of the antenna diversity number indicating information.

12. In the O-RU (radio unit) device of a base station in a wireless communication system, Transmitter / receiver; A fronthaul interface unit configured to transmit and receive signals with an O-DU (distributed unit); and It includes at least one control unit, and The above control unit is, A management message containing capability information related to the uplink antenna mapping of the above O-RU is transmitted to the O-DU (distributed unit), and Receive a control message from the above O-DU that includes uplink antenna mapping information for at least one O-RU generated based on the capability information, and Control to receive the uplink beam based on the control message generated above, and The above control message is, A method characterized by including a section type format for scheduling information and a section extension format including one or more of antenna group instruction information, antenna diversity instruction information, or antenna diversity count instruction information related to antenna mapping.

13. In Paragraph 12, The above ability information is, Includes identification information for supported antenna groups, and The above section extension format is, A device characterized by including the above antenna group instruction information.

14. In Paragraph 12, The above ability information is, Includes information on the number of supported antenna diversity, The above section extension format is, A device characterized by including at least one identification information indicating the number and order of antenna diversity and at least one of the antenna diversity number indicating information.

15. In Paragraph 12, The above ability information is, It includes information regarding the number of supported antenna diversity and information indicating whether duplicated UE (user equipment) identification information is supported, and The section type format for the above scheduling information is, A device characterized by including antenna diversity count indication information based on duplicate UE identification information.

Images