Apparatus and method for using time division duplex method in forward pass interface

Abstract

An apparatus of a radio unit (RU) may include a radio frequency (RF) switch selectively connected to an uplink path or a downlink path for time division duplex (TDD); at least one processor; and a memory including instructions. When executed individually or collectively by the at least one processor, the instructions may cause the apparatus to: receive a control plane message from a distributed unit (DU) within a downlink receive window; obtaining a segment for downlink scheduling based on data direction information and a segment type indicator of a generic header of the control plane message; and changing a path to which the RF switch is connected from an uplink path to a downlink path on the basis of the segmented command for increasing the symbol number and information for indicating the number of symbols.

Description

TECHNICAL FIELD

[0001] The following description relates to an apparatus and method for using a time division duplex method in a fronthaul interface. BACKGROUND

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

[0003] TECHNICAL SOLUTION

[0004] A radio unit (RU) can include a radio frequency (RF) switch that is selectively coupled to one of an uplink path and a downlink path for time division duplex (TDD). The RU can include at least one processor that includes processing circuitry. The RU can include at least one memory that includes instructions, including one or more storage mediums. The instructions, when executed by the at least one processor individually and collectively, can cause the RU to receive a control plane message from a distributed unit (DU) within a downlink reception window. The instructions, when executed by the at least one processor individually and collectively, can cause the RU to obtain a segment for downlink scheduling based on a segment type indicator of a generic header and data direction information in the control plane message. The instructions, when executed by the at least one processor individually and collectively, can cause the RU to change a path to which the RF switch is coupled from the uplink path to the downlink path based on a symbol number increment command of the segment and information indicating a number of symbols.

[0005] A method performed by a radio unit (RU) can include receiving a control plane message from a distributed unit (DU) within a downlink reception window. The method can include obtaining a segment for downlink scheduling based on a segment type indicator of a generic header and data direction information in the control plane message. The method can include changing a path to which a radio frequency (RF) switch is coupled from an uplink path to a downlink path based on a symbol number increment command of the segment and information indicating a number of symbols, the RF switch being selectively coupled to one of the uplink path and the downlink path for time division duplex (TDD).

[0006] A non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed individually or jointly by at least one processor of a radio unit (RU) including a radio frequency (RF) switch selectively coupled to one of an uplink path and a downlink path for time division duplexing (TDD), cause the RU to receive control plane messages from a distributed unit (DU) within a downlink receive window. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed individually and jointly by at least one processor, cause the RU to obtain segments for downlink scheduling based on segment type indicators and data direction information in a general header of the control plane messages. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed individually and jointly by at least one processor, cause the RU to change the path to which the RF switch is coupled from an uplink path to a downlink path based on information such as the number of segment symbol numbers incrementing commands and indicating symbol counts. Attached Figure Description

[0007] Figure 1 An example of a wireless communication system is shown.

[0008] Figure 2a An example of a network entity based on a distributed deployment is shown.

[0009] Figure 2b An example of an Open Radio Access Network (O-RAN) fronthaul interface is shown.

[0010] Figure 3a An example of the functional configuration of a distributed unit (DU) is shown.

[0011] Figure 3b An example of the functional configuration of a radio unit (RU) is shown.

[0012] Figure 4 An example of functional division between DU and RU is shown.

[0013] Figure 5 An example of the components included in a RU for supporting dynamic time division duplex (TDD) is shown.

[0014] Figure 6 An example of a method for generating a receive window for control plane messages associated with the timing of transmitting downlink signals is shown.

[0015] Figure 7a and Figure 7b An example of parameters included in a control plane message is shown.

[0016] Figure 8aAn example of the operational flow of a method for storing information about downlink symbols based on the segmentation type of control plane messages is shown.

[0017] Figure 8b An example of a memory for a RU that stores information about downlink symbols is shown.

[0018] Figure 9 An example of the operation flow of a method for controlling radio frequency (RF) switches based on information about downlink symbols is shown.

[0019] Figure 10 An example of a method for changing the coupling state of an RF switch based on control plane messages is shown.

[0020] Figure 11 An example of the operation flow of a method for changing the coupling state of an RF switch based on control plane messages is shown. Detailed Implementation

[0021] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of another embodiment. Singular expressions may include plural expressions unless the context clearly indicates otherwise. The terms used herein (including technical or scientific terms) may have the same meaning as commonly understood by one of ordinary skill in the art as described in this disclosure. Among the terms used in this disclosure, unless expressly defined herein, terms defined in a general dictionary may be interpreted as having the same or similar meaning as in the context of related art and are not to be interpreted as having an ideal or overly formal meaning. In some cases, even terms defined in this disclosure may not be construed as excluding embodiments of this disclosure.

[0022] In the various embodiments of this disclosure described below, hardware methods will be described as examples. However, since the various embodiments of this disclosure include techniques using both hardware and software, software-based methods are not excluded.

[0023] For ease of explanation, the following description exemplifies terms referring to signals (e.g., packets, messages, signals, information, signaling), terms referring to resources (e.g., segments, symbols, time slots, subframes, radio frames, subcarriers, resource elements (REs), resource blocks (RBs), bandwidth portions (BWPs), timing), terms used for calculating states (e.g., steps, operations, procedures), terms referring to data (e.g., packet messages, user streams, information, bits, symbols, codewords), terms referring to channels, terms referring to network entities (e.g., distributed units (DUs), radio units (RUs), central units (CUs), CU control planes (CPs), CU user planes (UPs), open radio access networks (O-RAN) DUs (O-DUs), O-RAN RUs (O-RUs), O-RAN CUs (O-CUs), O-RAN CU-UPs (O-CU-UPs), O-RAN CU-CPs (O-CU-CPs), and components of equipment, etc. Therefore, this disclosure is not limited to the terms described below, and other terms with equivalent technical meanings may be used. In addition, terms such as “…unit”, “…device”, “…object” and “…structure” used below may refer to at least one shape structure or a unit of processing function.

[0024] Furthermore, in this disclosure, the terms "greater than" or "less than" are used to determine whether a particular condition is met or satisfied, but this is merely a description of examples and does not exclude descriptions of "greater than or equal to" or "less than or equal to". A condition described as "greater than or equal to" can be replaced by "greater than", a condition described as "less than or equal to" can be replaced by "less than", and a condition described as "greater than or equal to and less than" can be replaced by "greater than and less than or equal to". Additionally, in the following, "a" to "B" refers to at least one of the elements from A (inclusive) to B (inclusive). In the following, "C" and / or "D" means including at least one of "C" or "D", i.e., {"C", "D", and "C" and "D"}.

[0025] Although this disclosure uses terminology used in some communication standards (e.g., the 3rd Generation Partnership Project (3GPP)) to describe various embodiments, these are merely examples for illustrative purposes. Various embodiments of this disclosure can be applied to other communication and broadcasting systems.

[0026] Figure 1 An example of a wireless communication system is shown.

[0027] refer to Figure 1 , Figure 1 Base station 110 and terminal 120 are shown as segments of nodes utilizing a wireless channel in a wireless communication system. Figure 1Only one base station is shown, but the wireless communication system may also include another base station that is the same as or similar to base station 110.

[0028] Base station 110 is a network infrastructure that provides wireless access to terminal 120. Base station 110 has coverage defined based on the distance at which signals can be transmitted. In addition to "base station", base station 110 may also be referred to as "access point (AP)", "eNodeB (eNB)", "fifth generation node", "next generation nodeB (gNB)", "wireless point", "transmit / receive point (TRP)" or other terms with equivalent technical meanings.

[0029] Terminal 120, used as a user device, communicates with base station 110 via a wireless channel. The link from base station 110 to terminal 120 is called the downlink (DL), and the link from terminal 120 to base station 110 is called the uplink (UL). Furthermore, although in Figure 1 Not shown, however, terminal 120 and another terminal can communicate with each other via a wireless channel. In this case, the link between terminal 120 and the other terminal (device-to-device link (D2D)) is called a side link, and the side link can be used interchangeably with the PC5 interface. In some other embodiments, terminal 120 can be operated without user intervention. According to embodiments, terminal 120, as a device performing machine-type communication (MTC), may not be carried by the user. Furthermore, according to embodiments, terminal 120 may be a narrowband (NB)-Internet of Things (IoT) device.

[0030] In addition to “terminal”, terminal 120 may also be referred to as “user equipment (UE)”, “customer premises equipment (CPE)”, “mobile station”, “subscriber station”, “remote terminal”, “wireless terminal”, “electronic device”, “user equipment” or other terms with equivalent technical meaning.

[0031] Base station 110 can perform beamforming with terminal 120. Base station 110 and terminal 120 can transmit and receive radio signals in relatively low frequency bands (e.g., NR frequency range 1 (FR 1)). Furthermore, base station 110 and terminal 120 can transmit and receive radio signals in relatively high frequency bands (e.g., FR 2 (or FR 2-1, FR 2-2, FR 2-3) or FR 3) and millimeter-wave frequency bands (e.g., 28 GHz, 30 GHz, 38 GHz, 60 GHz). Base station 110 and terminal 120 can perform beamforming to improve channel gain. In this document, beamforming can include transmit beamforming and receive beamforming. Base station 110 and terminal 120 can provide directionality to the transmitted or received signal. To this end, base station 110 and terminal 120 can select a serving beam through a beam search or beam management process. After selecting a serving beam, subsequent communication can be performed using resources that are in a QCL relationship with the resources of the transmit serving beam.

[0032] If the large-scale characteristics of the channel carrying symbols at the first antenna port can be inferred from the channel carrying symbols at the second antenna port, then the QCL relationship between the first and second antenna ports can be evaluated. For example, large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial receiver parameters.

[0033] although Figure 1 The description states that both base station 110 and terminal 120 perform beamforming, but embodiments of this disclosure are not limited to this. In some embodiments, the terminal may or may not perform beamforming. Furthermore, the base station may or may not perform beamforming. That is, only one of the base station and the terminal may perform beamforming, or both the base station and the terminal may not perform beamforming.

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

[0035] Traditionally, in communication systems with relatively large cell radii, each base station is installed to include functions of a digital processing unit (or distributed unit (DU)) and a radio frequency (RF) processing unit (or radio unit (RU)). However, with the use of high-frequency bands in fourth-generation (4G) and / or subsequent communication systems (e.g., 5G) and the smaller cell coverage of base stations, the number of base stations covering a specific area has increased. The installation cost burden for operators has also increased. To minimize the installation cost of base stations, a structure has been proposed where the DU and RU of a base station are separated, one or more RUs are connected to a DU via a wired network, and one or more RUs are deployed geographically to cover a specific area. In the following sections, through... Figure 2a and Figure 2b Deployment structures and extended examples of base stations according to various embodiments of this disclosure are described.

[0036] Figure 2b An example of a network entity arranged in a distributed manner is shown.

[0037] For example, network entities may include a digital unit (DU) 210 and a radio unit (RU) 220 (or a massive multiple-input multiple-output (MMU) unit). For example, network entities can be connected via fronthaul. Unlike backhaul between the base station and the core network, fronthaul refers to segments between entities (e.g., DU 210 and RU 220) between the wireless LAN and the base station. Figure 4An example of a fronthaul structure between a DU 210 and an RU 220 is shown, but this is for illustrative purposes only, and the present disclosure is not limited thereto. In other words, embodiments of the present disclosure can also be applied to a fronthaul structure between a DU and multiple RUs. For example, embodiments of the present disclosure can be applied to a fronthaul structure between a DU and two RUs. Furthermore, embodiments of the present disclosure can also be applied to a fronthaul structure between a DU and three RUs.

[0038] refer to Figure 4 Base station 110 may include DU 210 and RU 220. Fronthaul 215 between DU 210 and RU 220 can be operated via Fx interface. For operation of fronthaul 215, an interface such as Enhanced Common Public Radio Interface (eCPRI) or Radio over Ethernet (ROE) can be used.

[0039] With the development of communication technology and the increase in mobile data traffic, the bandwidth requirements for fronthaul between digital units and radio units have increased significantly. In deployments such as centralized / cloud radio access networks (C-RAN), DUs can be implemented to perform Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) functions, while RUs can be implemented to perform PHY layer functions in addition to radio frequency (RF) functions.

[0040] DU 210 can be responsible for the upper-layer functions of the wireless network. For example, DU 210 can perform a portion of the functions of the MAC layer and the PHY layer. In this document, "a portion of the PHY layer" refers to functions performed at a higher level within the PHY layer and may include, for example, channel coding (or channel decoding), scrambling (or descrambling), modulation (or demodulation), and layer mapping (or layer demapping). According to embodiments, if DU 210 conforms to the O-RAN standard, it can be referred to as an O-RAN DU (O-DU). As needed, in embodiments of this disclosure, DU 210 can be replaced with and represented as the first network entity of a base station (e.g., a gNB).

[0041] RU 220 can be responsible for lower-layer functions of the wireless network. For example, RU 220 can perform a portion of the PHY layer and RF functions. In this document, "a portion of the PHY layer" refers to functions performed at a relatively lower level than DU 210 within the PHY layer and may include, for example, iFFT conversion (or FFT conversion), cyclic prefix (CP) insertion (or CP removal), and digital beamforming. RU 220 may be referred to as an Access Unit (AU), Access Point (AP), Transmit / Receive Point (TRP), Remote Radio Head (RRH), Radio Unit (RU), or other terms with equivalent technical meanings. According to embodiments, if RU 220 conforms to the O-RAN standard, it may be referred to as an O-RAN RU (O-RU). As needed, in embodiments of this disclosure, RU 220 may be replaced with and represented as a second network entity of a base station (e.g., gNB).

[0042] although Figure 2b Base station 110 is described as including DU 210 and RU 220, but embodiments of this disclosure are not limited thereto. Base stations according to embodiments can be implemented in a distributed deployment based on centralized units (CUs) configured to perform functions of the upper layers of the access network (e.g., Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC)) and distributed units (DUs) configured to perform functions of the lower layers. For example, digital unit (DU) 210 can be implemented separately as a centralized unit (CU) and a distributed unit (DU). Between the core network (e.g., 5G core (5GC) or next-generation core (NGC)) and the radio access network (RAN), the base station can be implemented in a structure in which centralized units (CUs), distributed units (DUs), and radio units (RUs) are arranged sequentially. The interface between the centralized unit (CU) and the distributed unit (DU) can be referred to as the F1 interface.

[0043] A centralized unit (CU) can be connected to one or more distributed units (DUs) to handle functions at higher levels than the DUs. For example, a CU can handle functions at the Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layers, while DUs and RUs can handle lower-level functions. A DU can perform some functions at the Radio Link Control (RLC), Media Access Control (MAC), and PHY layers (high PHY), while an RU can perform the remaining functions at the PHY layer (low PHY). Furthermore, as an example, depending on the implementation of a distributed deployment of the base station, a digital unit (DU) can be included within a distributed unit (DU). Hereinafter, unless otherwise defined, it is described as the operation of digital units (DUs) and RUs; however, various embodiments of this disclosure can be applied to base station arrangements that include CUs or arrangements where DUs are directly connected to the core network (i.e., CUs and DUs are integrated into a base station as a single entity (e.g., an NG-RAN node)).

[0044] Figure 3a An example of an Open Radio Access Network (O-RAN) fronthaul interface is shown. Figure 3a In this context, the eNB or gNB is exemplified as base station 110 based on a distributed deployment.

[0045] refer to Figure 2a Base station 110 may include O-DU 251 and O-RU 253-1, ..., and 253-n. In the following text, for ease of explanation, the operation and function of O-RU 253-1 can be understood as a description of each of the other O-RUs (e.g., O-RU 253-n).

[0046] O-DU 251 is included according to what will be described later. Figure 2b The O-DU 251 is a logical node that controls the functions of a base station (e.g., eNB, gNB) other than those specifically allocated to the O-RU 253-1. The O-DU 251 can control the operation of O-RU 253-1, ..., and 253-n. The O-DU 251 can be referred to as a Lower Layer Segmentation (LLS) Central Unit (CU). The O-RU 253-1 includes functions as described later. Figure 3a Logical nodes that are a subset of the functions of a base station (e.g., eNB, gNB). Real-time aspects of communication with the control plane (C-plane) and user plane (U-plane) of the O-RU 253-1 can be controlled by the O-DU 251.

[0047] The O-DU 251 can communicate with the O-RU 253-1 via the LLS interface. The LLS interface corresponds to the fronthaul interface. The LLS interface refers to the logical interface between the O-DU 251 and O-RU 253-1 using lower-level function partitioning (i.e., function partitioning within the PHY). The LLS-C between the O-DU 251 and O-RU 253-1 provides the C-plane through the LLS interface. The LLS-U between the O-DU 251 and O-RU 253-1 provides the U-plane through the LLS interface.

[0048] exist Figure 3a In this document, the entities of base station 110 have been described as O-DU and O-RU to describe O-RAN. However, these designations are not to be construed as limiting the embodiments of this disclosure. In the embodiments described later, the operation of DU 210 may also be performed by O-DU 251. The description of DU 210 can be applied to O-DU 251. Similarly, in the embodiments described later, the operation of RU 220 may also be performed by O-RU 253-1. The description of RU 220 can be applied to O-RU 253-1.

[0049] Figure 3a An example of the functional configuration of a distributed unit (DU) is shown.

[0050] Figure 3a The configuration illustrated as part of the base station can be understood as Figure 3a DU 210 (or Figure 3a The configuration of O-DU 251. In the following text, the terms "...unit" and "...device" as used below refer to a unit that performs at least one function or operation, which can be implemented by hardware or software, or a combination of hardware and software.

[0051] refer to Figure 3b The DU 210 includes a transceiver 310, a memory 320, and a processor 330.

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

[0053] Transceiver 310 can also perform functions for transmitting and receiving signals in a wireless communication environment. For example, transceiver 310 can perform conversion functions between baseband signals and bit strings according to the physical layer specifications of the system. For example, when transmitting data, transceiver 310 generates complex-valued symbols by encoding and modulating the transmitted bit string. Furthermore, when receiving data, transceiver 310 recovers the received bit string by demodulating and decoding the baseband signal. Additionally, transceiver 310 may include multiple transmit / receive paths. Furthermore, according to embodiments, transceiver 310 can be connected to a core network or other nodes (e.g., integrated access backhaul (IAB)).

[0054] Transceiver 310 can send and receive signals. For example, transceiver 310 can send management plane (M-plane) messages. For example, transceiver 310 can send synchronization plane (S-plane) messages. For example, transceiver 310 can send control plane (C-plane) messages. For example, transceiver 310 can send user plane (U-plane) messages. For example, transceiver 310 can receive U-plane messages. Although in Figure 3b Only transceiver 310 is shown in the figure, but according to another implementation, DU 210 may include two or more transceivers.

[0055] As described above, transceiver 310 transmits and receives signals. Therefore, all or some of transceiver 310 may be referred to as a "communication unit," "transmitting unit," "receiving unit," or "transmitting / receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to include the meaning of the processing performed by transceiver 310 as described above.

[0056] Despite Figure 2a Not shown, but transceiver 310 may also include a backhaul transceiver for connecting to the core network or another base station. The backhaul transceiver provides an interface for performing communication with other nodes in the network. In other words, the backhaul transceiver converts bit strings sent from the base station to another node (such as another access node, another base station, an uplink node, and the core network) into physical signals, and converts physical signals received from another node into bit strings.

[0057] Memory 320 stores basic programs, application programs, and data such as configuration information for the operation of DU 210. Memory 320 may be referred to as a storage unit. Memory 320 may be configured with volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Furthermore, memory 320 provides stored data according to requests from processor 330.

[0058] Processor 330 controls the overall operation of DU 210. Processor 380 can be referred to as a control unit. For example, processor 330 sends and receives signals via transceiver 310 (or via a return communication unit). Furthermore, processor 330 writes and reads data from memory 320. Additionally, processor 330 can perform the functions of the protocol stack required in the communication standard. Although in Figure 2b Only processor 330 is shown in the figure, but according to another implementation, DU 210 may include two or more processors.

[0059] For example, processor 330 may include various processing circuitry and / or multiple processors. For example, the term "processor" as used herein (including the claims) may include various processing circuitry comprising at least one processor, and one or more of the at least one processor may be configured to individually and / or jointly perform the various functions described below. As used below, when "processor," "at least one processor," and "one or more processors" are described as being configured to perform various functions, these terms are not limited thereto and cover situations where one processor performs a portion of the referenced functions and another processor (or multiple processors) performs another portion of the referenced functions, and situations where one processor is capable of performing all of the referenced functions. Additionally, at least one processor may include, for example, a combination of processors performing various enumerated / disclosed functions in a distributed manner. At least one processor may execute program instructions to implement or perform various functions.

[0060] Figure 3b The configuration of DU 210 shown is merely an example, and examples of DUs performing embodiments of this disclosure are not limited to. Figure 3b The configuration is shown in the figure. In some embodiments, some configurations can be added, deleted, or changed.

[0061] Figure 3b An example of the functional configuration of a radio unit (RU) is shown.

[0062] Figure 3b The configuration illustrated as part of the base station can be understood as Figure 3b RU 220 or Figure 3b The configuration of the O-RU 253-1. In the following text, the terms "...unit" and "...device" as used refer to a unit that performs at least one function or operation, which can be implemented by hardware or software, or a combination of hardware and software.

[0063] refer to Figure 4 The RU 220 includes an RF transceiver 360, a fronthaul transceiver 365, a memory 370, and a processor 380.

[0064] The RF transceiver 360 performs functions for transmitting and receiving signals via a wireless channel. For example, the RF transceiver 360 up-converts a baseband signal to an RF band signal and then transmits it through an antenna, and down-converts the RF band signal received through the antenna back to a baseband signal. The RF transceiver 360 may include, for example, a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, or an ADC.

[0065] RF transceiver 360 may include multiple transmit / receive paths. Furthermore, RF transceiver 360 may include antenna elements. RF transceiver 360 may include at least one antenna array composed of multiple antenna elements. In terms of hardware, RF transceiver 360 may consist of digital circuitry and analog circuitry (e.g., radio frequency integrated circuits (RFICs)). Hereinafter, the digital and analog circuitry may be implemented as a single packet. Furthermore, RF transceiver 360 may include multiple RF chains. RF transceiver 360 may perform beamforming. To provide directionality to the signals to be transmitted and received according to the settings of processor 380, RF transceiver 360 may apply beamforming weights to the signals. According to embodiments, RF transceiver 360 may include a radio frequency (RF) block (or RF unit).

[0066] According to an embodiment, the RF transceiver 360 can transmit and receive signals on a radio access network. For example, the RF transceiver 360 can transmit downlink signals. Downlink signals may include synchronization signals (SS), reference signals (RS) (e.g., cell-specific reference signals (CRS), demodulation (DM)-RS), system information (e.g., MIB, SIB, residual system information (RMSI), other system information (OSI)), configuration messages, control information, or downlink data. Furthermore, for example, the RF transceiver 360 can receive uplink signals. Uplink signals may include random access associated signals (e.g., random access preamble (RAP)) (or message 1 (Msg1), message 3 (Msg3)), reference signals (e.g., probe reference signals (SRS), DM-RS), or power headroom reports (PHR). Although in Figure 4 Only RF transceiver 360 is shown in the figure, but according to another implementation, RU 220 may include two or more RF transceivers.

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

[0068] As described above, RF transceiver 360 and fronthaul transceiver 365 transmit and receive signals. Therefore, all or some of RF transceiver 360 and fronthaul transceiver 365 may be referred to as a "communication unit," "transmitting unit," "receiving unit," or "transmit / receive unit." Furthermore, in the following description, "transmission and reception performed via a wireless channel" is used to include the meaning of the processing described above performed by RF transceiver 360.

[0069] Memory 370 stores basic programs, application programs, and data such as configuration information for the operation of RU 220. Memory 370 may be referred to as a storage unit. Memory 370 may be configured with volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Furthermore, memory 370 provides stored data upon request from processor 380. According to embodiments, memory 370 may include memory for conditions, commands, or setting values ​​related to the SRS transmission scheme.

[0070] Processor 380 controls the overall operation of RU 220. Processor 380 can be referred to as a control unit. For example, processor 380 transmits and receives signals via RF transceiver 360 or fronthaul transceiver 365. Furthermore, processor 380 writes and reads data from memory 370. Additionally, processor 380 can perform the functions of the protocol stack required by communication standards. Although in Figure 2a Only processor 380 is shown, but according to another implementation, RU 220 may include two or more processors. Processor 380, as an instruction set or code stored in memory 370, may be instructions / code that reside at least temporarily in processor 380, or storage space storing instructions / code, or part of the circuitry constituting processor 380. Furthermore, processor 380 may include various modules for performing communications. Processor 380 can control RU 220 to perform operations according to embodiments described later.

[0071] For example, processor 380 may include various processing circuitry and / or multiple processors. For example, the term "processor" as used herein (including the claims) may include various processing circuitry comprising at least one processor, and one or more of the at least one processor may be configured to individually and / or collectively perform the various functions described below. As used below, when "processor," "at least one processor," and "one or more processors" are described as being configured to perform various functions, these terms are not limited thereto and cover situations where one processor performs a portion of the referenced functions and another processor (or multiple processors) performs another portion of the referenced functions, and situations where one processor is capable of performing all of the referenced functions. Additionally, at least one processor may include, for example, a combination of processors performing various enumerated / disclosed functions in a distributed manner. At least one processor may execute program instructions to implement or perform various functions.

[0072] Figure 5 The configuration of RU 220 shown is merely an example, and examples of RUs performing embodiments of this disclosure are not limited to this. Figure 5 The configuration is shown in the figure. In some embodiments, some configurations can be added, deleted, or changed.

[0073] Figure 2a An example of functional division between DU and RU according to an embodiment is shown.

[0074] With advancements in wireless communication technologies (e.g., the introduction of fifth-generation (5G) communication systems (or new radio (NR) communication systems)), the frequency bands used have increased further. As base station cell radii become very small, the number of RUs (Real Estate Units) requiring installation has increased further. Furthermore, in 5G communication systems, with the amount of data transmitted increasing significantly by more than tenfold, the transmission capacity of wired networks to the fronthaul has increased significantly. Due to these factors, the installation cost of wired networks in 5G communication systems can increase significantly. Therefore, to reduce the transmission capacity of wired networks and lower their installation costs, a "functional partitioning" approach can be used to reduce fronthaul transmission capacity by transferring some functions of the DU's modem to the RU.

[0075] To reduce the burden on the DU, the role of the RU, which is currently only responsible for existing RF functions, can be expanded to include some physical layer functions. When the RU performs higher-level functions, its throughput increases, which can increase the transmission bandwidth in the fronthaul while reducing latency requirements due to response processing. On the other hand, when the RU performs higher-level functions, virtualization gain decreases and the size, weight, and cost of the RU increase. Considering the trade-offs mentioned above, optimal function partitioning is required.

[0076] refer to Figure 5 This illustrates the functional division in the physical layer below the MAC layer. When transmitting signals to the terminal's downlink (DL) via a wireless network, the base station can sequentially perform channel coding / scrambling, modulation, layer mapping, antenna mapping, RE mapping, digital beamforming (e.g., precoding), iFFT conversion / CP insertion, and RF conversion. When receiving signals from the terminal's uplink (UL) via a wireless network, the base station can sequentially perform RF conversion, FFT conversion / CP removal, digital beamforming (pre-combining), RE demapping, channel estimation, layer demapping, demodulation, and decoding / descrambling. Based on these trade-offs, the division of uplink and downlink functions can be defined in various ways depending on inter-vendor needs, standards discussions, etc.

[0077] In the first functional partition 405, the RU performs the RF function, and the DU performs the PHY function. This first functional partition essentially prevents the PHY function from being implemented within the RU, and as an example, it can be referred to as Option 8. In the second functional partition 410, the RU performs iFFT transformation / CP insertion in the DL of the PHY function and FFT transformation / CP removal in the UL, while the DU performs the remaining PHY function. As an example, the second functional partition 410 can be referred to as Option 7-1. In the third functional partition 420a, the RU performs iFFT transformation / CP insertion in the DL of the PHY function and FFT transformation / CP removal and digital beamforming in the UL, while the DU performs the remaining PHY function. As an example, the third functional partition 420a can be referred to as Option 7-2x Category A. In the fourth functional partition 420b, the RU performs digital beamforming in both the DL and UL, and the DU performs the upper-layer PHY function after digital beamforming. As an example, the fourth functional partition 420b can be referred to as Option 7-2x Category B. In the fifth functional segment 425, the RU performs RE mapping (or RE demapping) in both DL and UL, and the DU performs upper-layer PHY functions after RE mapping (or RE demapping). As an example, the fifth functional segment 425 can be referred to as Option 7-2. In the sixth functional segment 430, the RU performs up to modulation (or demodulation) in both DL and UL, and the DU performs upper-layer PHY functions after modulation (or demodulation). As an example, the sixth functional segment 430 can be referred to as Option 7-3. In the seventh functional segment 440, the RU performs up to encoding / scrambling (or decoding / descrambling) in both DL and UL, and the DU performs upper-layer PHY functions after modulation (or demodulation). As an example, the seventh functional segment 440 can be referred to as Option 6.

[0078] According to embodiments, in cases where a large amount of signal processing is anticipated, such as in an FR 1 MMU, functional partitioning at relatively higher levels (e.g., fourth functional partition 420b) may be required to reduce fronthaul capacity. Furthermore, in functional partitioning at excessively higher levels (e.g., sixth functional partition 430), the implementation of the RU may become burdensome due to the increased complexity of the control interface and the inclusion of multiple PHY processing blocks within the RU; therefore, appropriate functional partitioning may be required depending on the arrangement and implementation method of the DU and RU.

[0079] According to an embodiment, when precoding of data received from the DU cannot be processed (i.e., when there is a limitation on the precoding capability of the RU), a third functional segmentation 420a or a lower functional segmentation (e.g., a second functional segmentation 410) can be applied. Conversely, when the ability to process precoding of data received from the DU is available, a fourth functional segmentation 420b or a higher functional segmentation (e.g., a sixth functional segmentation 430) can be applied.

[0080] In the following description, unless otherwise stated, embodiments of this disclosure are based on either a third functional segment 420a (which may be referred to as Category A (CAT-A)) or a fourth functional segment 420b (which may be referred to as Category B (CAT-B)) for performing beamforming processing in the RU. In the O-RAN standard, the type of O-RU is distinguished based on whether the precoding function resides at the interface of the O-DU or the interface of the O-RU. An O-RU where precoding is not performed (i.e., low complexity) may be referred to as a CAT-A O-RU. An O-RU where precoding is performed may be referred to as a CAT-B O-RU.

[0081] In the following text, "upper PHY" refers to physical layer processing handled in the DU of the fronthaul interface. For example, upper PHY may include FEC encoding / decoding, scrambling, and modulation / demodulation. In the following text, "lower PHY" refers to physical layer processing handled in the RU of the fronthaul interface. For example, lower PHY may include FFT / iFFT, digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. However, the above criteria do not preclude embodiments through other functional partitioning.

[0082] Embodiments of this disclosure exemplarily describe when in DU (e.g., Figure 3b DU 210) and RU (e.g., Figure 5The standard eCPRI and O-RAN are used as fronthaul interfaces when sending messages between RU 220. The Ethernet payload of the message may include an eCPRI header, an O-RAN header, and additional fields. In the following, the standard terminology of eCPRI or O-RAN is used to describe various embodiments of this disclosure; however, other expressions having equivalent meanings to each term may be used instead in various embodiments of this disclosure.

[0083] Ethernet and eCPRI, which are easily shared with the network, can be used as the transport protocols for the fronthaul. The eCPRI header and O-RAN header can be included in the Ethernet payload. The eCPRI header can be placed before the Ethernet payload. The eCPRI header contains the following:

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

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

[0086] 3) ecpriConcatenation (1 bit): This parameter indicates when to use eCPRI concatenation.

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

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

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

[0090] 7) ecpriSeqid (2 bytes): This parameter provides unique message identification and ordering at two levels. The first octet is a sequence ID used to identify the message order within the eAxC message stream, ensuring all messages are received and reordering out-of-order messages. The second octet is a subsequence ID. The subsequence ID is used to verify the order and implement reordering in the event of radio transmission level (eCPRI or IEEE-1914.3) fragmentation.

[0091] The eAxC identifier (ID) includes the band and sector identifier (“BandSector_ID”), component carrier identifier (“CC_ID”), spatial stream identifier (“RU_Port_ID”), and distributed cell identifier (“DU_Port_ID”). The bit allocation of the eAxC ID can be distinguished as follows.

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

[0093] 2) BandSector_ID: Aggregate cell identifier (identifier of frequency bands and sectors supported by O-RU).

[0094] 3) CC_ID: CC_ID identifies the carrier components supported by the O-RU.

[0095] 4) RU_port ID: RU_port ID specifies logical flows such as data layer or space streams, as well as logical flows of signal channels such as separate parameter sets (e.g., PRACH) or SRS that require specific antenna assignments.

[0096] The application protocol of the fronthaul can include the control plane (C plane), user plane (U plane), synchronization plane (S plane), and management plane (M plane).

[0097] The control plane can be configured to provide scheduling and beamforming information via control messages. The control plane signifies real-time control between the DU and RU. The user plane can include IQ sample data transmitted between the DU and RU. The user plane can include the user's downlink data (IQ data or SSB / RS), uplink data (IQ data or SRS / RS), or PRACH data. The weight vector of the aforementioned beamforming information can be multiplied by the user's data. The synchronization plane typically signifies the flow between the DU and RU of a synchronization controller (e.g., an IEEE grand master). The synchronization plane can be associated with timing and synchronization. The management plane signifies non-real-time control between the DU and RU. The management plane can be associated with initial setup, non-real-time reset or resetting, and non-real-time reporting.

[0098] Messages in the control plane (i.e., control plane messages) can be encapsulated using a two-layer header approach. The first layer can be configured with the eCPRI general header or the IEEE 1914.3 general header, which includes fields indicating the message type. The second layer is the application layer, which includes fields required for control and synchronization. In the application layer, segments define the characteristics of U-plane data transmitted or received on a beam with a mode ID. The segment types supported in the C-plane are as follows.

[0099] Segment types can indicate the purpose of control messages sent in the control plane. For example, the purpose of a segment type is as follows.

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

[0101] 2) sectionType=1: Used for most DL / UL wireless channels. In this document, "most" refers to channels that do not require time or frequency offset, such as those required for hybrid parameter set channels.

[0102] 3) sectionType=2: Reserved for further use

[0103] 4) sectionType=3: PRACH and hybrid parameter set channels. Channels that require time or frequency offsets or differ from the nominal SCS value.

[0104] 5) sectionType=4: Reserved for further use

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

[0106] 7) sectionType=6: Transmits UE-specific channel information. Periodically transmits UE channel information, enabling the RU to perform real-time BF weight calculation (optional BF method for O-RAN).

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

[0108] Open Radio Access Network (ORAN) is an organization that redefines the standard fronthaul interface between DU and RU based on various functional partitioned architectures and provides a standard interface in partitioned architectures where Ethernet is applied (e.g., 7-2x functional partitioned architecture).

[0109] In the following, this disclosure presents an apparatus and method for dynamically controlling paths in an RU 220 to support dynamic TDD configuration. The paths may include downlink paths and uplink paths for TDD.

[0110] TDD can refer to a scheme for time-based allocation of signal resources for transmitting and receiving signals, including data, between base station 110 and user equipment 120. For example, TDD can be included in a resource allocation scheme for uplink (UL) and downlink (DL) transmissions. For example, the resource allocation scheme can include both frequency division duplex (FDD) and TDD. For example, the signal can include OFDM signals (or OFDM symbols) used in an orthogonal frequency division multiplexing (OFDM) modulation scheme.

[0111] For example, TDD can represent a scheme in which resources for DL ​​transmission and resources for UL transmission are allocated over time. In contrast, FDD can represent a scheme in which resources for DL ​​transmission and resources for UL transmission are allocated according to frequency. For example, referring to the above description, in the FDD scheme, the frequency bands for DL ​​transmission and UL transmission are separated from each other, while in the TDD scheme, the DL transmission interval and the UL transmission interval can be separated in time within the same frequency band. To support TDD, the RU220 of base station 110 needs to accurately distinguish the DL data transmission interval and the UL data transmission interval in time using the DL / UL control signal (or differentiation signal) for TDD (hereinafter, the control signal).

[0112] In an LTE wireless communication system, an example of a TDD configuration mode can be defined as shown in the table below.

[0113] [Table 1]

[0114]

[0115] D can represent a subframe used for DL ​​(Downlink), U can represent a subframe used for UL (Uplink), and S can represent a special subframe. For example, D can indicate that all 14 symbols in a subframe used for DL ​​are used for DL ​​data transmission. Similarly, U can indicate that all 14 symbols in a subframe used for UL are used for UL data transmission. Furthermore, S can indicate that the symbols in a special subframe are configured with downlink symbols, protection symbols, and uplink symbols. The ratio of downlink symbols, protection symbols, and uplink symbols in S can be indicated by the special subframe configuration.

[0116] Referring to the table above, in LTE wireless communication systems, the TDD configuration can be statically selected based on the requirements of service providers, etc. In NR wireless communication systems, unlike LTE, the TDD configuration mode can be set relatively freely. For example, in NR wireless communication systems, a TDD configuration mode can be set for each symbol in a time slot. In other words, unlike LTE where all 14 symbols in a subframe are set as either symbols for uplink transmission (hereinafter referred to as uplink symbols) or symbols for downlink transmission (hereinafter referred to as downlink symbols), in NR, a TDD configuration mode can be set for each of the 14 symbols in a time slot. Examples of TDD configuration modes can be defined in NR wireless communication systems, as shown in the table below.

[0117] [Table 2]

[0118]

[0119] D can represent a downlink symbol, U can represent an uplink symbol, and F can represent a flexible symbol. For example, a flexible symbol can indicate that either an uplink symbol or a downlink symbol can be assigned. In NR wireless communication systems, TDD configuration can operate statically, semi-statically based on cell traffic, or dynamically over time.

[0120] As described above, in a TDD configuration that is flexibly designed for each symbol and operates semi-statically or dynamically, the method of generating a signal (i.e., a control signal) that statically controls TDD and then controlling the RF switch based on it may be unsuitable. Therefore, the apparatus and method according to embodiments of this disclosure provide an apparatus and method for dynamically controlling paths in the RU 220. The apparatus and method according to embodiments of this disclosure can dynamically identify whether a particular symbol is a resource for downlink transmission or a resource for uplink transmission based on parameters of control plane messages obtained from the DU 210. The apparatus and method according to embodiments of this disclosure can control RF switches selectively coupled to one of the downlink and uplink paths based on a particular symbol. Therefore, the apparatus and method according to embodiments of this disclosure can dynamically support TDD.

[0121] Figure 2a An example of the components included in a RU for supporting dynamic time division duplex (TDD) is shown.

[0122] Figure 5 The RU 220 may include Figure 3a The RU 220. For example, Figure 5 The RU 220 may include Figure 5 At least some of the components included in the RU 220. Figure 6The DU 210 may include Figure 7a DU 210. For example, Figure 7b The DU 210 may include Figure 8a to Figure 10 At least some of the components included in DU 210.

[0123] refer to Figure 6 The RU 220 can be connected to the DU 210. For example, the RU 220 can be connected to the DU 210 via a fronthaul interface. The fronthaul interface can be used to send and receive data between the RU 220 and the DU 210. The data can include uplink and downlink data.

[0124] refer to Figure 6 RU 220 may include multiple components for supporting dynamic TDD. For example, RU 220 may include a downlink signal processing unit 510, a digital-to-analog converter (DAC) 520, a power amplifier (PA) 530, an RF switch 540, an antenna 550, a low-noise amplifier (LNA) 560, an analog-to-digital converter (ADC) 570, an uplink signal processing unit 580, and a TDD control signal generation module 500. For example, multiple components may be controlled by a processor 380 of RU 220. DAC 520, PA 530, RF switch 540, LNA 560, and ADC 570 may be referred to as an RF processing unit or RF unit.

[0125] For example, downlink signal processing unit 510, DAC 520, and PA 530 may be included in the downlink path. Alternatively, for example, uplink signal processing unit 580, ADC 570, and LNA 560 may be included in the uplink path. For example, the uplink and downlink paths may be controlled by RF switch 540. RF switch 540 may be referred to as a switch, a switch for selecting a TDD path, a TDD switch, or a path selection element. When the path coupled to RF switch 540 is an uplink path, RU 220 can provide the uplink signal to DU 210 by processing the uplink signal obtained through antenna 550. Alternatively, when the path coupled to RF switch 540 is a downlink path, RU 220 can transmit a downlink signal based on information obtained from DU 210 through antenna 550 by generating and processing the downlink signal. For example, uplink and downlink signals can be sent and received from user equipment 120, which receives services from base station 110 including DU 210 and RU 220.

[0126] For example, RU 220 can generate control signals for TDD based on a static TDD configuration (such as an LTE wireless communication system). For example, RU 220 can obtain configuration values ​​corresponding to the TDD configurations in Table 1 above, and generate control signals through the TDD control signal generation module 500 based on the configuration values. RU 220 can use the generated control signals to change the path to which RF switch 540 is coupled. For example, if the control signal indicates a downlink path, RF switch 540 can be coupled to the downlink path. Alternatively, for example, if the control signal indicates an uplink path, RF switch 540 can be coupled to the uplink path. In the above example, an example of RF switch 540 changing the coupling path according to the uplink transmission interval and the downlink transmission interval is described, but embodiments of this disclosure are not limited thereto. For example, during a protection period, RF switch 540 can be coupled to either the downlink path or the uplink path based on the control signal.

[0127] According to an embodiment, RU 220 can generate control signals for supporting dynamic TDD through TDD control signal generation module 500. For example, TDD control signal generation module 500 may include synchronization unit 501, control plane message processing unit 503, control signal generation unit 505, and control signal delay unit 507. RU 220 can generate control signals for supporting dynamic TDD based on control plane messages obtained from DU 210 through TDD control signal generation module 500. Therefore, RU 220 can dynamically control RF switch 540 through control signals. Each of synchronization unit 501, control plane message processing unit 503, control signal generation unit 505, and control signal delay unit 507 can be implemented based on hardware, software, or a combination of hardware and software.

[0128] According to an embodiment, synchronization unit 501 can generate information about the synchronization receiving window based on the synchronization plane message, subcarrier spacing (SCS) information, and parameters of the receiving window obtained from DU 210. For example, RU 220 can generate information about the synchronization receiving window based on the synchronization plane message, SCS information, and parameters through synchronization unit 501.

[0129] For example, the synchronization plane message may include the frame number synchronized with absolute time, as well as information indicating the start frame of the frame (e.g., frame tick). For example, RU 220 can generate a frame structure synchronized with absolute time using the synchronization plane message and the subcarrier spacing (SCS) information supported by RU 220. For example, absolute time may represent the time synchronized between base station 110 and user equipment 120.

[0130] For example, SCS information can indicate one of the multiple SCSs that RU 220 can support for TDD. For instance, in LTE, RU 220 can provide a fixed SCS of 15 kHz. Furthermore, for example, in NR, RU 220 can provide multiple SCSs including 15, 30, 60, 120, and 240 kHz. For example, RU 220 can provide 15, 30, and 60 kHz SCSs for data in the Frequency Range 1 (FR1) band and 15 and 30 kHz SCSs for the synchronization signal block. For example, RU 220 can provide 60 and 120 kHz SCSs for data in the FR2 band and 120 and 240 kHz SCSs for the synchronization signal block. In this example, RU 220 can operate multiple SCSs for a resource area defined by the time and frequency domains. Thus, multiple SCSs operating on a resource area can be referred to as a hybrid parameter set. In the following description, for ease of explanation, the RU 220 is described as providing a single SCS of 15 kHz or 30 kHz in FR1 and a single SCS of 120 kHz in FR2; however, embodiments of this disclosure are not limited thereto. For example, the RU 220 according to embodiments of this disclosure can be applied even when using a mixed parameter set.

[0131] For example, parameters of the receive window can include candidates for the receive window. For example, candidates can be determined based on time information included in the general header of the downlink control plane message. For example, candidates can be referred to as canonical values. For example, candidates can be values ​​configured in RU 220. For example, DU 210 can perform downlink transmissions based on the receive window considered in management plane messages. For example, management plane messages including candidates can be sent from RU 220 to DU 210. For example, time information can include at least one of a start symbol identifier or a time offset. For example, the receive window can be determined based on a maximum and minimum time interval defined for the time information. For example, the maximum time interval can include the T2a_max_cp_dl parameter. For example, the minimum time interval can include the T2a_min_cp_dl parameter. For example, a receive window can be identified for each symbol.

[0132] Referring to the above, the RU 220 can generate information about the synchronization receive window based on synchronization plane messages, SCS information, and receive window parameters. The synchronization receive window can represent a receive window related to absolute time synchronization. Specific details related to this will be discussed later. Figure 5 As described in the text.

[0133] According to an embodiment, the control plane message processing unit 503 can obtain parameters (or information) included in the control plane message. For example, RU 220 can identify parameters based on the control plane message obtained from DU 210 by the control plane message processing unit 503. In this case, RU 220 can identify segments for downlink scheduling of the control plane message based on the data direction and segment type indicator of the control plane message by the control plane message processing unit 503. The segment can be referred to as a segment type. For example, parameters may include time identifiers, symbol number increment commands, and symbol counts included in the control plane message. For example, time identifiers may include frame ID, subframe ID, and slot ID. Specific details related to this will be discussed below. Figure 6 and Figure 6 As described in the text.

[0134] According to an embodiment, the control signal generation unit 505 can generate control signals based on information and parameters regarding the synchronization receive window. For example, RU 220 can generate control signals based on information and parameters regarding the synchronization receive window through the control signal generation unit 505. For example, RU 220 can identify parameters of control plane messages obtained in the synchronization receive window and identify one or more downlink symbols for downlink transmission based on the parameters. For example, RU 220 can store (or write) information about one or more downlink symbols in memory 370. For example, RU 220 can identify one or more downlink symbols based on identifying (or reading) information about one or more downlink symbols stored in memory 370. RU 220 can generate control signals for changing the path coupled to RF switch 540 with respect to the identified one or more downlink symbols. For example, control signals can be generated for each of the one or more downlink symbols (i.e., for each downlink symbol). In other words, control signals can be used to change the path coupled to RF switch 540 for each downlink symbol. Alternatively, for example, where one or more downlink symbols are multiple subsequent downlink symbols, the control signal can be used to change the path coupled to RF switch 540 with respect to the time length corresponding to the multiple subsequent downlink symbols. For example, RU 220 can use the downlink path coupled based on the control signal to transmit downlink signals from one or more identified downlink symbols via antenna 550. Specific content related to this will be discussed later. Figure 7a As described in the text.

[0135] According to an embodiment, the control signal delay unit 507 can delay the timing at which a control signal can be applied to each component included in the RU 220. For example, by delaying the timing of the control signal generated by the control signal generation module 500, the RU 220 can synchronously apply the timing of the control signal in its components. For example, when using a downlink path, the RU 220 can provide a control signal delayed for a first time length to the DAC 520 via the control signal delay unit 507. In this case, the RU 220 can provide a control signal delayed for a second time length, longer than the first time length, to the PA 530 via the control signal delay unit 507. The duration including the first and second time lengths can be determined based on the processing time within each component included in the RU 220. However, embodiments of this disclosure are not limited thereto. For example, the RU 220 according to an embodiment of this disclosure may not include the control signal delay unit 507. Therefore, the RU 220 can perform downlink transmission (or uplink reception) by generating a control signal at the start of each symbol based on absolute time and providing it to each component without delaying the control signal.

[0136] Figure 7b An example of a method for generating a receive window for control plane messages associated with the timing of transmitting downlink signals is shown.

[0137] Figure 7a The method can be derived from Figure 7b The RU 220 is executed. For example, the receive window can represent a receive window synchronized with absolute time. Figure 7b Example 601 of frames 611 and 613 synchronized with absolute time and example 603 of time slots 631 and 633 in frames 611 and 613 are shown.

[0138] Referring to Example 601, RU 220 can generate a frame structure including frames 611 and 613 based on the synchronization plane message obtained from DU 210. For example, RU 220 can generate a frame structure including synchronization frames 611 and 613 based on the synchronization frame number and frame tick included in the synchronization plane message. In this case, the frame structure can be formed based on the SCS indicated by the SCS information.

[0139] Referring to Example 603, each of slots 631 and 633 in the frame structure may include SCS-based symbols. Figure 7aIn Example 603, for ease of explanation, a 30 kHz SCS is assumed. However, embodiments of this disclosure are not limited to this. For example, in the case of a 30 kHz SCS, slot 631 (e.g., slot #19) may have a length of 0.5 ms, and each of the 14 symbols included in slot 631 may have a length of approximately 36 μs. Slot 633 (e.g., slot #0) may also have a structure substantially the same as that of slot 631.

[0140] Referring to Example 603, RU 220 may transmit downlink signals to User Equipment 120 in the first symbol 621 (e.g., symbol #0) of time slot 633. In this case, the first symbol 621 may represent the absolute time of transmitting the downlink signal. RU 220 may receive downlink control plane messages for the downlink signal in a receive window 645 identified based on a minimum time interval 643 and a maximum time interval 641 starting from the start point 640 of the first symbol 621. For example, the downlink control plane messages may include segments (e.g., segment type 1 or segment type 5) for scheduling resources to transmit the downlink signal. The minimum time interval 643 may be determined based on RU 220 receiving the downlink control plane messages and the processing time required to generate (or process) the downlink signal based on the downlink control plane messages. The minimum time interval 643 and the maximum time interval 641 may be configured in RU 220. For example, RU 220 may send management plane messages to DU 210 including information about the minimum time interval 643 and the maximum time interval 641. For example, management plane messages can indicate the minimum and maximum time intervals for each symbol. For instance, management plane messages can indicate the minimum time interval 643 and maximum time interval 641 for the first symbol 621, and the maximum and maximum time intervals for the second symbol 622 (e.g., symbol #1), respectively. As described above, the minimum and maximum time intervals for each symbol can be referred to as the canonical values ​​(or delay management parameters) of the receive window. RU 220 can identify the receive window 645 for the first symbol 621 and the receive window 655 for the second symbol 622 based on the canonical values. In this case, receive window 645 and receive window 655 can represent receive windows synchronized with absolute time according to the synchronization plane message.

[0141] Figure 8a and Figure 8a An example of parameters included in a control plane message is shown.

[0142] Figure 8aExamples of parameters for a general header 700 included in a control plane message are shown. For example, the general header 700 in a control plane message may include data direction information 701, time identifiers 703, 705, and 707, a start symbol identifier 709, a segment number 711, and a segment type indicator 713. However, embodiments of this disclosure are not limited thereto.

[0143] For example, data direction information 701 can indicate whether a control plane message is for uplink control plane (e.g., an uplink control plane message) or for downlink control plane (e.g., a downlink control plane message). For example, when the value of data direction information 701 is 0, the control plane message can be an uplink control plane message. Alternatively, when the value of data direction information 701 is 1, the control plane message can be a downlink control plane message.

[0144] For example, time identifiers 703, 705, and 707 may include timing information for control plane messages. For example, time identifiers 703, 705, and 707 may include frame ID 703, subframe ID 705, and slot ID 707. For example, time identifiers 703, 705, and 707 may be used to identify the reception window for control plane messages. For example, if a control plane message is received from a reception window identified by a specification value according to the time indicated by time identifiers 703, 705, and 707, RU 220 can identify that the control plane message was received at the appropriate time.

[0145] For example, the start symbol identifier 709 can indicate the index of the start symbol of a control plane message. For example, the start symbol identifier 709 can be used to indicate a specific symbol in slot ID 707.

[0146] For example, the segment number 711 can be used to indicate the number of segments included in a control plane message. In this case, the segment type indicator 713 can indicate the segments of the control plane message. For example, segments can include segment types 0 to 7. The segment type of the control plane message can be associated with scheduling information. For example, the segment type used for scheduling can include segment type 1, segment type 3, and segment type 5. Segment type 1 and segment type 5 can provide general downlink / uplink channel allocation information. Segment type 3 can provide allocation information for the Physical Random Access Channel (PRACH). The segment type used for downlink scheduling can be segment type 1 and segment type 5. In other words, DU 210 can send control plane messages including segment type 1 or segment type 5 to RU 220 within a downlink transmission interval.

[0147] According to an embodiment, DL and UL allocations can be temporally partitioned in a TDD system supported by RU 220. The smallest unit of DL and UL allocation can be a symbol. For example, a downlink control plane message including segment type 1 or segment type 5 providing downlink allocation information can be separate from an uplink control plane message including segment type 1, segment type 3, or segment type 5 providing uplink allocation information, and they do not overlap temporally. In other words, an uplink message including segment type 1, segment type 3, or segment type 5 cannot be allocated to the symbol to which a downlink message including segment type 1 or segment type 5 is allocated. Conversely, a downlink message including segment type 1 or segment type 5 cannot be allocated to the symbol to which an uplink message including segment type 1, segment type 3, or segment type 5 is allocated. Therefore, in the device and method according to embodiments of the present disclosure, when the downlink control plane message includes a segmentation type for downlink scheduling (e.g., segmentation type 1 or segmentation type 5) (e.g., when the value of data direction information 701 is 1), RU220 can generate a control signal for changing the path of RF switch 540 based on the segmentation type for downlink scheduling.

[0148] Figure 5 An example of segment 720 of a downlink control plane message is shown. For example, segment 720 may represent a portion of segment type 1 or segment type 5.

[0149] refer to Figure 8a The downlink control plane message segment 720 may include a symbol number increment command 721 and information 723 indicating the number of symbols. For example, the symbol number increment command 721 may be used to indicate the symbols associated with segment 720. For example, if the value of the symbol number increment command 721 is 0, the symbol number may be maintained. For example, if the value of the symbol number increment command 721 is 0, the symbol represented by the start symbol identifier 709 (e.g., symbol #0) may be used for segment 720. For example, if the value of the symbol number increment command 721 is 1, the next symbol after the symbol indicated by the start symbol identifier 709 (e.g., symbol #0) (e.g., symbol #1) may be used for segment 720. For example, information 723 may be used to indicate the number of symbols including the symbol identified by the symbol number increment command 721. For example, the symbols indicated by information 723 may be assigned to segment 720.

[0150] refer to Figure 8b and 7bA control plane message may include one or more segments. For example, a control plane message may include one segment 720. Alternatively, for example, a control plane message may include multiple segments 720. For example, RU 220 may identify that the control plane message includes a segment type for downlink scheduling based on the data direction information 701 of the general header 700 and the segment type indicator 713. Based on the time identifiers 703, 705, and 707 in the control plane message, the symbol number increment command 721 in the segment, and the information 723 indicating the number of symbols, RU 220 may identify the downlink symbols in which downlink transmissions are scheduled. The identified information about the downlink symbols may be stored in the memory 370 of RU 220. Specific details related to this will be discussed below. Figure 8b As described in the text.

[0151] Figure 8b An example of the operational flow of a method for storing information about downlink symbols based on the segmentation type of control plane messages is shown.

[0152] Figure 8b At least some of the methods can be derived from Figure 5 The RU 220 executes the operation. For example, at least some of the methods can be controlled by the processor 380 of the RU 220. In the following embodiments, each operation can be executed sequentially, but not necessarily sequentially. For example, the order of each operation can be changed, and at least two operations can be executed in parallel.

[0153] In operation 800, RU 220 can receive synchronization plane messages. For example, RU 220 can receive synchronization plane messages from DU 210. For example, the synchronization plane message may include the number of the frame synchronized with absolute time and information indicating the start frame of the frame (e.g., frame tick). For example, absolute time may represent the time synchronized between base station 110 and user equipment 120.

[0154] According to an embodiment, RU 220 can obtain SCS information. For example, RU 220 can obtain SCS information from DU 210. For example, the SCS information can indicate one of the multiple SCSs that RU 220 can support for TDD. For example, an SCS may include 15 kHz, 30 kHz, or 120 kHz.

[0155] In operation 805, RU 220 can send management plane messages. For example, RU 220 can send management plane messages to DU 210. For example, management plane messages can include candidates for the receive window of downlink control plane messages. For example, candidates can be determined based on time information included in the general header of the downlink control plane messages. For example, candidates can be referred to as canonical values. For example, candidates can be values ​​configured in RU 220. For example, DU 210 can perform downlink transmissions based on the receive window considered in the management plane messages. For example, time information can include at least one of a start symbol identifier or a time offset. For example, the receive window can be determined based on a maximum time interval and a minimum time interval defined for the time information. For example, the maximum time interval can include the T2a_max_cp_dl parameter. For example, the minimum time interval can include the T2a_min_cp_dl parameter. For example, the receive window can be identified for each symbol. Figure 9 The present invention illustrates an example of a method including operations 800 and 805, but embodiments thereof are not limited thereto. For example, operations 800 and 805 may be omitted.

[0156] In operation 810, RU 220 can receive control plane messages. For example, RU 220 can receive control plane messages from DU 210. For example, RU 220 can obtain a general header from the control plane message. For example, the general header may include data direction information, a time identifier, a start symbol identifier, a number of segments, and a segment type indicator. However, embodiments of this disclosure are not limited thereto. The data direction information may be referred to as a data direction or a downlink indicator. Based on the data direction information in the general header, RU 220 can identify that the control plane message is a control plane message for downlink (hereinafter, a downlink control plane message). Furthermore, RU 220 can identify that the downlink control plane message includes a segment type for downlink scheduling based on the segment type indicator in the general header. For example, the segment type indicator may be referred to as a segment type or a segment type field.

[0157] In operation 815, RU 220 can identify whether control plane messages are received within the downlink receive window. For example, RU 220 can identify the downlink receive window for control plane messages based on the time identifier of the general header. For example, RU 220 can obtain candidates for synchronization receive windows based on synchronization plane messages, SCS information, and parameters of the downlink receive window. RU 220 can obtain the downlink receive windows among the candidates corresponding to the time identifiers. RU 220 can identify whether control plane messages are received within the downlink receive window. For example, it can identify whether the start and end points of receiving control plane messages are included within the downlink receive window.

[0158] In operation 815, if a control plane message is received within the downlink receive window, RU 220 can perform operation 820. Alternatively, in operation 815, if a control plane message is received outside the downlink receive window, RU 220 can perform operation 810. For example, when RU 220 performs operation 810 again, it can receive another control plane message following that control plane message.

[0159] In operation 820, RU 220 can obtain segments of control plane messages. For example, RU 220 can identify segments based on segment type indicators in the general header of the control plane message. For example, the segment type indicator can indicate at least one of segment type 1 and segment type 5. For example, RU 220 can obtain segments based on those indicated by the segment type indicator. For example, RU 220 can obtain segments after identifying the segment type indicator.

[0160] For example, a segment may include a symbol number increment command and information indicating the number of symbols. For example, the symbol number increment command can be used to indicate symbols associated with the segment. For example, if the value of the symbol number increment command is 0, the symbol number can be maintained. For example, if the value of the symbol number increment command is 0, the symbol indicated by the start symbol identifier in the general header (e.g., symbol #0) can be used for the segment. For example, if the value of the symbol number increment command is 1, the next symbol after the symbol indicated by the start symbol identifier (e.g., symbol #0) (e.g., symbol #1) can be used for the segment. For example, information indicating the number of symbols can be used to indicate the number of symbols including the symbol identified by the symbol number increment command. For example, the symbol indicated by the information indicating the number of symbols can be assigned to the segment. For example, the number of symbols can indicate a value greater than or equal to 1. Accordingly, information indicating the number of symbols can be used to indicate one or more downlink symbols.

[0161] In operation 825, RU 220 can obtain one or more downlink symbols based on segments. For example, RU 220 can obtain one or more downlink symbols based on a start symbol identifier, a symbol number increment command, and information indicating the number of symbols. The example describes obtaining one or more downlink symbols based on segments included in a control plane message, but embodiments of this disclosure are not limited thereto. For example, RU 220 can obtain one or more downlink symbols based on that segment and another segment of a control plane message. For example, another segment following that segment may include segment type 1 or segment type 5.

[0162] To explain the method of obtaining one or more downlink symbols based on the symbol number increment command and the symbol quantity, it is assumed that the starting symbol identifier indicates symbol #0. For example, in the case where the symbol number increment command for a segment type is 0 and the symbol quantity is 1, RU 220 can obtain (or identify) symbol #0 as the symbol of that segment. Alternatively, for example, in the case where the symbol number increment command for a segment is 1 and the symbol quantity is 4, RU 220 can obtain symbols #1 through #4 as the symbols of that segment.

[0163] In operation 830, RU 220 can store information indicating one or more downlink symbols. For example, RU 220 can store information indicating one or more downlink symbols in memory 370. Storing information in memory 370 can be referred to as writing to memory 370.

[0164] For example, RU 220 can store information including indices within a time slot, encompassing one or more downlink symbols, in memory 370. In this case, memory 370 may include a storage area for storing information. For example, the memory area may include a memory area for two time slots. For example, the memory area may include 28 bits (= 14 symbols). 2). For example, the index of one or more downlink symbols can indicate which downlink symbols have been allocated for downlink transmission. In other words, the index (or information) of one or more downlink symbols can be used to indicate whether downlink control plane messages have been allocated. Specific details related to this will be discussed below. Figure 9 As described in the text.

[0165] In operation 835, RU 220 can identify whether another segment has been obtained. For example, after storing the information obtained from the segment based on the control plane message in memory 370, RU 220 can identify whether another segment of the control plane message is included.

[0166] In operation 835, if another segment is acquired, RU 220 can perform operation 825. For example, RU 220 can acquire one or more other downlink symbols of the other segment based on the other segment and store information about the one or more other downlink symbols in memory 370. Alternatively, in operation 835, if the other segment is not acquired, RU 220 can perform operation 810. For example, when RU 220 performs operation 810 again, it can receive another control plane message following the control plane message.

[0167] Figure 5 An example of a memory for a RU that stores information about downlink symbols is shown.

[0168] exist Figure 9 Example 850 shows a method for storing information about downlink symbols obtained by RU 220 in memory 370. Figure 8a The RU 220 may include Figure 10 RU 220.

[0169] Referring to Example 850, the memory 370 of RU 220 may include a first memory region 860 and a second memory region 870. The first memory region 860 and the second memory region 870 may be referred to as memory regions. For example, the first memory region 860 may include 14 bits, and the second memory region 870 may include 14 bits. For example, the 14 bits of the first memory region 860 may have address values ​​from 0 to 13. For example, the 14 bits of the second memory region 870 may have address values ​​from 14 to 27. However, embodiments of this disclosure are not limited thereto.

[0170] Referring to Example 850, a first memory region 860 may be used for a first time slot (e.g., time slot #N-1), and a second memory region 870 may be used for a second time slot (e.g., time slot #N). For example, a first bit 861 of the first memory region 860 may correspond to symbol #0 of the first time slot, and a second bit 862 of the first memory region 860 may correspond to symbol #1 following symbol #0 of the first time slot. Symbol #1 may follow symbol #0. Furthermore, for example, a first bit 871 of the second memory region 870 may correspond to symbol #0 of the second time slot. Referring to Example 850, the first memory region 860 and the second memory region 870 may include 28 bits. This is because a control plane message can be provided for at most one time slot. In other words, information about the downlink symbols allocated for a control plane message can be stored in a portion of Example 850 (e.g., the first memory region 860). When RU 220 identifies (or reads) information in a portion of the region and generates control signals for downlink symbols, additional information about other downlink symbols allocated for another control plane message can be stored in the remaining region of example 850 (e.g., second memory region 870). According to an embodiment, RU 220 can generate control signals for each symbol and clear (or refresh) the bits in the memory region corresponding to the generated symbol. However, embodiments of this disclosure are not limited thereto. For example, RU 220 can generate control signals for subsequent downlink symbols.

[0171] Figure 10 An example of the operation flow of a method for controlling radio frequency (RF) switches based on information about downlink symbols is shown.

[0172] Figure 10At least some of the methods can be derived from Figure 11 The RU 220 executes the operation. For example, at least some of the methods can be controlled by the processor 380 of the RU 220. In the following embodiments, each operation can be executed sequentially, but not necessarily sequentially. For example, the order of each operation can be changed, and at least two operations can be executed in parallel.

[0173] In operation 900, RU 220 can detect the last symbol including the end point of the downlink receive window. For example, RU 220 can detect the last symbol including the end point of the downlink receive window based on control plane message identification. However, embodiments of this disclosure are not limited thereto. For example, RU 220 can detect the absolute time corresponding to the end point of the receive window.

[0174] In operation 905, RU 220 can generate control signals based on information indicating downlink symbols stored in memory 370. Figure 11 The memory 370 can be based on Figure 5 The method stores the state of information indicating one or more downlink symbols. For example, RU 220 can generate control signals based on the information in memory 370. In other words, RU 220 can generate control signals for each symbol.

[0175] In operation 910, RU 220 can couple RF switch 540 to a downlink path based on a control signal. For example, the control signal can be used to change the path to which RF switch 540 is coupled to a downlink path for the transmission of downlink signals. For example, RF switch 540 can be decoupled from the uplink path and coupled to the downlink path based on a control signal.

[0176] In operation 915, RU 220 can transmit downlink signals in downlink symbols. For example, RU 220 can generate downlink signals by activating a downlink path based on a control signal controlling RF switch 540. RU 220 can transmit the generated downlink signals in downlink symbols. For example, downlink symbols can be used to transmit downlink signals to user equipment 120 connected to RU 220.

[0177] Alternatively, RU 220 can generate another control signal based on information stored in memory 370 that does not indicate a downlink symbol (or other information that indicates an uplink symbol). RU 220 can then change the path to which RF switch 540 is coupled to an uplink path based on this other control signal. For example, RU 220 can change it to an uplink path based on this other control signal. RU 220 can then transmit an uplink signal within the uplink symbol indicated by memory 370.

[0178] According to an embodiment, RU 220 can generate a control signal (or another control signal) based on information in memory 370, and send a downlink signal (or an uplink signal), then clear memory 370. Thereafter, RU 220 can read bits in memory 370 following the bit indicating a downlink symbol, and then send a downlink signal or an uplink signal based on that bit. Downlink signals can be sent from each of one or more downlink symbols stored in memory 370. Uplink signals can be sent outside of one or more downlink symbols. That is, RU 220 can repeatedly read memory 370 to generate and send a downlink signal or an uplink signal for each symbol. For example, it can repeatedly read memory regions of memory 370 (e.g., a first memory region 860 and a second memory region 870). RU 220 can read and clear each bit (i.e., symbol cell) of the memory region.

[0179] Figure 9 An example of a method for changing the coupling state of an RF switch based on control plane messages is shown.

[0180] Figure 11 Example 1000 of a method for generating control signals for changing the coupling state of RF switch 540 based on control plane messages is shown. The coupling state may include a state where RF switch 540 is coupled to an uplink path for uplink transmission in TDD and a state where RF switch 540 is coupled to a downlink path for downlink transmission in TDD. For example, control signals may be used to couple RF switch 540 to a downlink path. Control plane messages may represent downlink control plane messages for scheduling (or downlink scheduling) of downlink transmissions.

[0181] Referring to Example 1000, Example 1001 shows uplink and downlink symbols configured according to TDD configuration based on absolute time, Example 1003 shows the timing of sending downlink control messages including control plane messages, and Example 1005 shows the timing of generating control signals for coupling with the downlink path.

[0182] Referring to Example 1001, starting from reference point 1010-1, five downlink symbols, five uplink symbols following the five downlink symbols, and four downlink symbols following the five uplink symbols can be configured for TDD. In Example 1001, for ease of explanation, an example of 14 symbols included in a time slot (time slot #N) is described, but embodiments of this disclosure are not limited thereto. Example 1003 shows the timing of transmitting link control messages and Example 1005 shows the timing of generating control signals for coupling with the downlink path.

[0183] According to an embodiment, downlink transmission can be performed using downlink symbol 1011, which is the initial symbol after reference time 1010-1. In this case, RU 220 can receive control plane messages for scheduling downlink symbol 1011 at timing 1031 before reference time 1010-1.

[0184] For example, the receive window 1025-1 for the interval in which control plane messages are received can be identified based on the minimum time interval 1023-1 and the maximum time interval 1021-1. For example, information regarding the minimum time interval 1023-1 and the maximum time interval 1021-1 can be configured in RU 220. Synchronization of the absolute time for the minimum time interval 1023-1 and the maximum time interval 1021-1 can be performed based on synchronization plane messages. In this case, synchronization can be performed based on SCS information. The receive window 1025-1 can be a receive window configured for downlink symbol 1011. In Example 1000, only the receive window for downlink symbol 1011 is shown, but embodiments of this disclosure are not limited thereto. For example, RU 220 can identify a receive window for each symbol.

[0185] For example, RU 220 can identify the receive window 1025-1 configured for downlink symbol 1011, and identify that a control plane message has been received within the receive window 1025-1. Identifying that a control plane message has been received within the receive window 1025-1 can be performed based on the time identifier and start symbol identifier within the general header of the control plane message.

[0186] For example, RU 220 can obtain the segments for downlink scheduling of control plane messages based on data direction information and segment type identifiers within the general header of the control plane message. For example, the data direction information can indicate a value representing downlink transmission (e.g., 1). For example, the segment type identifier can include at least one of segment type 1 and segment type 5.

[0187] For example, RU 220 can obtain the first and second segments of the control plane message received at timing 1031. In this case, each of the first and second segments can be one of segment type 1 and segment type 5. In example 1000, assume that the start symbol identifier in the general header of the control plane message indicates downlink symbol 1011 (i.e., symbol #0). In this case, assume that the symbol number increment command for the first segment is 0, the number of symbols for the first segment is 1, the symbol number increment command for the second segment is 1, and the number of symbols for the second segment is 4.

[0188] For example, RU 220 can identify that downlink symbol 1011 has been assigned to the control plane message based on the parameters of the first segment of the control plane message. For example, since the symbol number increment command is 0 and the symbol quantity is 1, RU 220 can identify that downlink symbol 1011 has been assigned and store the information about downlink symbol 1011 in memory 370. In this case, the information about downlink symbol 1011 can be stored in a first region of memory 370 corresponding to the index of downlink symbol 1011. The length of the first region can be 1 bit.

[0189] Furthermore, for example, RU 220 can identify that downlink symbol 1012 has been assigned to the control plane message based on parameters of the second segment of the control plane message. For example, since the symbol number increment command is 1 and the number of symbols is 4, RU 220 can identify that downlink symbol 1012 (e.g., symbols #1 to #4) has been assigned and store the information about downlink symbol 1012 in memory 370. In this case, the information about downlink symbol 1012 can be stored in a second region of memory 370 corresponding to the index of downlink symbol 1012. The length of the second region can be 4 bits.

[0190] For example, RU 220 can generate control signals for coupling the downlink path and RF switch 540 based on the detection of a symbol including the end point 1051 of the receive window 1025-1. For example, RU 220 can begin reading memory 370 in response to the detection of end point 1051. For example, RU 220 can read a first region of memory 370 and generate control signals to couple RF switch 540 to the downlink path for the path coupled to downlink symbol 1011. Furthermore, for example, RU 220 can read a second region of memory 370 and generate control signals to couple RF switch 540 to the downlink path for each of the downlink symbols 1012 that are coupled to it. However, embodiments of this disclosure are not limited thereto. For example, RU 220 can read the second region and generate control signals to couple RF switch 540 to the downlink path for the path coupled to subsequent downlink symbols 1012.

[0191] As described above, RU 220 can transmit downlink signals from downlink symbol 1011 and downlink symbol 1012 based on control signals used to couple downlink path and RF switch 540.

[0192] According to an embodiment, downlink transmission can be performed on downlink symbols 1013 (e.g., symbols #10 to #13) after reference time 1010-2. In this case, RU 220 can receive another control plane message for scheduling downlink symbols 1013 at timing 1033 before reference time 1010-2.

[0193] For example, the receive window 1025-2 for the interval in which another control plane message is received can be identified based on the minimum time interval 1023-2 and the maximum time interval 1021-2. The receive window 1025-2 can be the receive window configured for downlink symbol 1014 in downlink symbol 1013.

[0194] For example, RU 220 can identify the receive window 1025-2 configured for downlink symbol 1014, and identify that another control plane message has been received within the receive window 1025-2. Identifying that another control plane message has been received within the receive window 1025-2 can be performed based on the time identifier and start symbol identifier within the general header of the other control plane message.

[0195] For example, RU 220 can obtain the segment type for downlink scheduling of another control plane message based on data direction information and segment type identifier within the general header of that other control plane message. For example, the data direction information can indicate a value representing downlink transmission (e.g., 1). For example, the segment type identifier can include at least one of segment type 1 and segment type 5.

[0196] For example, RU 220 can obtain a third segment of another control plane message received at timing 1033. In this case, the third segment can be either segment type 1 or segment type 5. In example 1000, it is assumed that the start symbol identifier in the general header of the other control plane message indicates downlink symbol 1014 (i.e., symbol #10). In this case, it is assumed that the symbol number increment command for the third segment is 0 and the number of symbols in the third segment is 4.

[0197] For example, RU 220 can identify that downlink symbol 1013 has been assigned to another control plane message based on parameters of the third segment of that message. For instance, since the symbol number increment command is 0 and the symbol count is 4, RU 220 can identify that downlink symbol 1013 has been assigned and store information about downlink symbol 1013 in memory 370. In this case, information about downlink symbol 1013 can be stored in a third region of memory 370 corresponding to the index of downlink symbol 1013. The length of the third region can be 4 bits.

[0198] For example, RU 220 can generate control signals for coupling the downlink path and RF switch 540 based on the detection of a symbol including the end point 1053 of the receive window 1025-2. For example, RU 220 can begin reading memory 370 in response to the detection of end point 1053. For example, RU 220 can read a third region of memory 370 and generate control signals to couple RF switch 540 to the downlink path for each of the downlink symbols 1013 that are coupled to it. However, embodiments of this disclosure are not limited thereto. For example, RU 220 can read the third region and generate control signals to couple RF switch 540 to the downlink path for the subsequent downlink symbols 1013 that are coupled to it.

[0199] As described above, RU 220 can transmit downlink signals in downlink symbol 1013 based on control signals used to couple downlink path and RF switch 540.

[0200] Despite ​Not shown, but RU 220 can receive uplink control plane messages for scheduling uplink symbol 1015. For example, the uplink control plane message can be obtained between timing 1031 and timing 1033. RU 220 can store information indicating that no downlink symbol has been allocated in memory 370 based on the uplink control plane message. In other words, RU 220 can store information indicating that an uplink symbol has been allocated in memory 370. For example, information indicating that an uplink symbol has been allocated can be stored in a memory area between the second and third areas. RU 220 can generate another control signal for coupling the uplink path and RF switch 540 based on the information indicating that an uplink symbol has been allocated. Based on the other control signal, RU 220 can transmit uplink signals in the uplink symbol (or receive uplink signals from the user equipment).

[0201] ​ An example of the operation flow of a method for changing the coupling state of an RF switch based on control plane messages is shown.

[0202] ​ At least some of the methods can be derived from ​ The method is executed by RU 220. For example, at least some of the methods can be controlled by processor 380 of RU 220. In the following embodiments, each operation can be executed sequentially, but not necessarily sequentially. For example, the order of each operation can be changed, and at least two operations can be executed in parallel.

[0203] In operation 1110, RU 220 can receive control plane messages within the downlink receive window. For example, RU 220 can obtain control plane messages from DU 210 within the downlink receive window.

[0204] For example, RU 220 can obtain a general header from a control plane message. This general header may include data direction information, a time identifier, a start symbol identifier, a segment count, and a segment type indicator. However, embodiments of this disclosure are not limited thereto. Based on the data direction information in the general header, RU 220 can identify that the control plane message is a control plane message for downlink (hereinafter, downlink control plane message). Furthermore, RU 220 can identify that the downlink control plane message includes segments for downlink scheduling based on the segment type indicator in the general header.

[0205] According to an embodiment, RU 220 can receive synchronization plane messages. For example, RU 220 can receive synchronization plane messages from DU 210. For example, the synchronization plane message may include the number of a frame synchronized with absolute time and information indicating the start frame of the frame (e.g., frame tick). For example, absolute time may represent the time synchronized between base station 110 and user equipment 120.

[0206] According to an embodiment, RU 220 can obtain SCS information. For example, RU 220 can obtain SCS information from DU 210. For example, the SCS information can indicate one of the multiple SCSs that RU 220 can support for TDD. For example, an SCS may include 15 kHz, 30 kHz, or 120 kHz.

[0207] According to an embodiment, RU 220 can send management plane messages. For example, RU 220 can send management plane messages to DU 210. For example, the management plane message can include candidates for the receive window of the downlink control plane message. For example, the candidates can be determined based on the time information of the general header included in the downlink control plane message. For example, the candidates can be referred to as canonical values. For example, the candidates can be values ​​configured in RU 220. For example, DU 210 can perform downlink transmissions based on the receive window considered in the management plane message. For example, the time information can include at least one of a start symbol identifier or a time offset. For example, the receive window can be determined based on a maximum time interval and a minimum time interval defined for the time information. For example, the maximum time interval can include the T2a_max_cp_dl parameter. For example, the minimum time interval can include the T2a_min_cp_dl parameter. For example, the receive window can be identified for each symbol.

[0208] For example, RU 220 can identify the downlink receive window for control plane messages based on the time identifier in the general header. For example, RU 220 can obtain candidates for the synchronization receive window based on the synchronization plane message, SCS information, and parameters of the downlink receive window. RU 220 can obtain the downlink receive window corresponding to the time identifier among the candidates. RU 220 can determine whether control plane messages are received within the downlink receive window. For example, it can determine whether the start and end points of receiving control plane messages are included within the downlink receive window.

[0209] According to an embodiment, if a control plane message is received outside the downlink receive window, RU 220 can receive another control plane message following that control plane message.

[0210] In Operation 1120, RU 220 can obtain segments for downlink scheduling based on the data direction information and segment type indicator in the general header of the control plane message.

[0211] For example, RU 220 can identify segments based on segment type indicators in the general header of control plane messages. For example, the segment type indicator can indicate at least one of segment type 1 and segment type 5. For example, RU 220 can obtain segments based on the segment type indicator.

[0212] For example, a segment may include a symbol number increment command and information indicating the number of symbols. For example, the symbol number increment command can be used to indicate symbols associated with the segment. For example, if the value of the symbol number increment command is 0, the symbol number can be maintained. For example, if the value of the symbol number increment command is 0, the symbol indicated by the start symbol identifier in the general header (e.g., symbol #0) can be used for the segment. For example, if the value of the symbol number increment command is 1, the next symbol after the symbol indicated by the start symbol identifier (e.g., symbol #0) (e.g., symbol #1) can be used for the segment. For example, information indicating the number of symbols can be used to indicate the number of symbols including the symbol identified by the symbol number increment command. For example, the symbol indicated by the information indicating the number of symbols can be assigned to the segment. For example, the number of symbols can indicate a value greater than or equal to 1. Accordingly, information indicating the number of symbols can be used to indicate one or more downlink symbols.

[0213] According to an embodiment, RU 220 can obtain one or more downlink symbols based on segments. For example, RU 220 can obtain one or more downlink symbols based on a start symbol identifier, a symbol number increment command, and information indicating the number of symbols. In the example, the case of obtaining one or more downlink symbols based on segments included in a control plane message is described, but embodiments of this disclosure are not limited thereto. For example, RU 220 can obtain one or more downlink symbols based on the segment and another segment of a control plane message. For example, another segment following the first segment may include segment type 1 or segment type 5.

[0214] According to an embodiment, RU 220 can store information indicating one or more downlink symbols. For example, RU 220 can store information indicating one or more downlink symbols in memory 370. Storing information in memory 370 can be referred to as writing to memory 370.

[0215] For example, RU 220 can store information including indices within a time slot, encompassing one or more downlink symbols, in memory 370. In this case, memory 370 may include a storage area for storing information. For example, the memory area may include a memory area for two time slots. For example, the memory area may include 28 bits (= 14 symbols). 2). For example, the allocation of one or more downlink symbols for downlink transmission can be indicated by the index of one or more downlink symbols. In other words, the index (or information) of one or more downlink symbols can be used to indicate whether downlink control plane messages have been allocated.

[0216] In operation 1130, RU 220 can change the path coupled to RF switch 540 from an uplink path to a downlink path based on information about the number of segmented symbol numbers incrementing commands and indication symbols.

[0217] According to an embodiment, RU 220 can detect the last symbol including the end point of the downlink receive window. For example, RU 220 can detect the last symbol including the end point of the downlink receive window based on control plane message identification. However, embodiments of this disclosure are not limited thereto. For example, RU 220 can detect the absolute time corresponding to the end point of the receive window.

[0218] According to an embodiment, RU 220 can generate control signals based on information indicating downlink symbols stored in memory 370. ​ The memory 370 can be in a state of storing information indicating one or more downlink symbols. For example, RU 220 can generate control signals based on the information in the memory 370. In other words, RU 220 can generate a control signal for each symbol. However, embodiments of this disclosure are not limited thereto. For example, RU 220 can generate control signals for subsequent downlink symbols.

[0219] According to an embodiment, RU 220 can couple RF switch 540 to a downlink path based on a control signal. For example, the control signal can be used to change the path to which RF switch 540 is coupled to a downlink path for the transmission of downlink signals. For example, RF switch 540 can disconnect from the uplink path and couple to a downlink path based on a control signal.

[0220] According to an embodiment, RU 220 can transmit downlink signals in a downlink symbol. For example, RU 220 can generate downlink signals by activating a downlink path based on a control signal controlling RF switch 540. RU 220 can transmit the generated downlink signals in a downlink symbol. For example, the downlink symbol can be used to transmit downlink signals to user equipment 120 connected to RU 220.

[0221] According to an embodiment, RU 220 can generate another control signal based on information stored in memory 370 that does not indicate a downlink symbol (or other information that indicates an uplink symbol). RU 220 can change the path to which RF switch 540 is coupled to an uplink path based on this other control signal. For example, RU 220 can change it to an uplink path based on this other control signal. RU 220 can transmit an uplink signal in the uplink symbol indicated by memory 370.

[0222] According to an embodiment, RU 220 can generate a control signal (or another control signal) based on information in memory 370, and send a downlink signal (or an uplink signal), then clear memory 370. Thereafter, RU 220 can read bits in memory 370 following the bit indicating a downlink symbol, and then send a downlink signal or an uplink signal based on that bit. Downlink signals can be sent from each of one or more downlink symbols stored in memory 370. Uplink signals can be sent outside of one or more downlink symbols. That is, RU 220 can repeatedly read memory 370 to generate and send a downlink signal or an uplink signal for each symbol. For example, it can repeatedly read memory regions of memory 370 (e.g., a first memory region 860 and a second memory region 870). RU 220 can read and clear each bit (i.e., symbol cell) of the memory region.

[0223] Despite ​ Not shown, but RU 220 can identify whether another segment of the control plane message has been obtained. For example, after storing information obtained based on a segment of the control plane message in memory 370, RU 220 can identify whether another segment of the control plane message is included. For example, RU 220 can obtain one or more other downlink symbols of the other segment based on the other segment, and store information about the one or more other downlink symbols in memory 370. Thereafter, RU 220 can perform downlink transmission based on the information about the one or more other downlink symbols.

[0224] The apparatus and method according to embodiments of this disclosure provide an apparatus and method for dynamically controlling paths in RU 220. The apparatus and method according to embodiments of this disclosure can dynamically identify whether a specific symbol is a resource for downlink transmission or a resource for uplink transmission based on parameters of control plane messages obtained from DU 210. The apparatus and method according to embodiments of this disclosure can control RF switches selectively coupled to one of the downlink path and the uplink path based on specific symbols. Therefore, the apparatus and method according to embodiments of this disclosure can dynamically support TDD.

[0225] As described above, a radio unit (RU) may include a radio frequency (RF) switch selectively coupled to one of an uplink path and a downlink path for time division duplexing (TDD). The RU may include at least one processor comprising processing circuitry. The RU may include at least one memory containing instructions, including one or more storage media. When executed individually and jointly by at least one processor, the instructions enable the RU to receive control plane messages from a distributed unit (DU) within a downlink receive window. When executed individually and jointly by at least one processor, the instructions enable the RU to obtain segments for downlink scheduling based on segment type indicators and data direction information in the general header of the control plane messages. When executed individually and jointly by at least one processor, the instructions enable the RU to change the path coupled to the RF switch from an uplink path to a downlink path based on information such as segment symbol number increment commands and indicator symbol counts.

[0226] According to an embodiment, when executed individually and jointly by at least one processor, the instruction enables the RU to receive a synchronization plane message from the DU, including information indicating frames for downlink transmission of the RU. When executed individually and jointly by at least one processor, the instruction enables the RU to generate a synchronization frame structure based on the synchronization plane message. The frame structure can be used to transmit downlink signals to the user equipment.

[0227] According to an embodiment, when executed individually and jointly by at least one processor, this instruction enables the RU to obtain the downlink receive window of the control plane message based on the time identifier and start symbol identifier information of the general header and the parameters of the downlink receive window. The time identifier may include frame ID, subframe ID, and slot ID.

[0228] According to an embodiment, when executed individually and jointly by at least one processor, the instruction enables the RU to identify whether a control plane message has been received within an interval of the downlink receive window. When executed individually and jointly by at least one processor, the instruction enables the RU to obtain segments of the control plane message in response to its reception within the interval. When executed individually and jointly by at least one processor, the instruction enables the RU to obtain another control plane message in response to at least a portion of the control plane message being received outside the interval.

[0229] According to an embodiment, data direction information can indicate the downlink. The segment type indicator can indicate segment type 1 or segment type 5.

[0230] According to an embodiment, when executed individually and jointly by at least one processor, this instruction enables the RU to obtain an additional segment for downlink scheduling based on data direction information and a segment type indicator. The additional segment in the control plane message can follow the segmentation.

[0231] According to an embodiment, when executed individually and jointly by at least one processor, this instruction enables the RU to obtain one or more downlink symbols allocated in a segment based on the symbols indicated by the start symbol identification information in the general header, as well as the symbol quantity and symbol number increment command for those symbols. When executed individually and jointly by at least one processor, this instruction also enables the RU to store information indicating one or more downlink symbols in memory.

[0232] According to an embodiment, when the symbol number increment command indicates 0, one or more downlink symbols may include that symbol. When the symbol number increment command indicates 1, one or more downlink symbols may include another symbol following that symbol.

[0233] According to an embodiment, one or more downlink symbols can be scheduled based on the number of symbols.

[0234] According to an embodiment, the memory may include a memory region with two time slots. Information indicating one or more downlink symbols may be stored in the memory region at a location corresponding to one or more downlink symbols.

[0235] According to an embodiment, when executed individually and jointly by at least one processor, the instruction can cause the RU to detect the last symbol, including the end point of the downlink receive window. When executed individually and jointly by at least one processor, the instruction can cause the RU, in response to detecting the last symbol, to generate a control signal corresponding to one or more downlink symbols based on information stored in memory indicating one or more downlink symbols. When executed individually or jointly by at least one processor, the instruction can cause the RU to couple an RF switch to the downlink path based on the control signal. When executed individually and jointly by at least one processor, the instruction can cause the RU to transmit downlink signals to the user equipment on one or more downlink symbols via the downlink path coupled to the RF switch.

[0236] According to an embodiment, the control signal may be generated before a specified time interval starting from the initial symbol in one or more downlink symbols. The specified time interval may be identified based on the processing delay used to generate the control signal.

[0237] According to an embodiment, when executed individually and jointly by at least one processor, this instruction enables the RU to receive uplink control plane messages from the DU within another downlink receive window following the downlink receive window. When executed individually and jointly by at least one processor, this instruction enables the RU to change the path to which the RF switch is coupled from a downlink path to an uplink path based on the uplink control plane messages.

[0238] According to an embodiment, when executed individually and jointly by at least one processor, this instruction enables the RU to receive another control plane message from the DU within a subsequent downlink receive window. When executed individually and jointly by at least one processor, this instruction enables the RU to obtain another segment for downlink scheduling based on the segment type indicator and data direction information in the general header of the other control plane message. When executed individually and jointly by at least one processor, this instruction enables the RU to change the path to which the RF switch is coupled from an uplink path to a downlink path based on the symbol number increment command and the information indicating the number of symbols in the other segment. The resources indicated by the control plane message and the other control plane message can be used for downlink signals transmitted on symbols in a time slot.

[0239] According to an embodiment, one of the multiple subcarrier spacings (SCS) supported by the RU can be used in a resource indicated by a control plane message.

[0240] As described above, a method performed by a radio unit (RU) may include receiving control plane messages from a distributed unit (DU) within a downlink receive window. The method may include obtaining segments for downlink scheduling based on segment type indicators and data direction information in the general header of the control plane messages. The method may include changing the path to which a radio frequency (RF) switch, selectively coupled to one of an uplink path and a downlink path for time division duplexing (TDD), is coupled from the uplink path to the downlink path, based on segment symbol number increment commands and information indicating the number of symbols.

[0241] According to an embodiment, the method may include obtaining the downlink receive window of the control plane message based on the time identifier and start symbol identifier information in the general header and the parameters of the downlink receive window. The time identifier may include the frame ID, subframe ID, and slot ID.

[0242] According to an embodiment, data direction information can indicate the downlink. The segment type indicator can indicate segment type 1 or segment type 5.

[0243] According to an embodiment, the method may include obtaining one or more downlink symbols allocated in a segment based on a symbol indicated by start symbol identification information in a general header, and a symbol quantity and symbol number increment command for that symbol. The method may also include storing information indicating one or more downlink symbols in the memory of the RU.

[0244] According to an embodiment, the memory may include a memory region with two time slots. Information indicating one or more downlink symbols may be stored in the memory region at a location corresponding to one or more downlink symbols.

[0245] As described above, a non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed individually or jointly by at least one processor of a radio unit (RU) including a radio frequency (RF) switch selectively coupled to one of an uplink path and a downlink path for time division duplexing (TDD), cause the RU to receive control plane messages from a distributed unit (DU) within a downlink receive window. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed individually and jointly by at least one processor, cause the RU to obtain segments for downlink scheduling based on segment type indicators and data direction information in a general header of the control plane messages. The non-transitory computer-readable storage medium may store one or more programs including instructions that, when executed individually and jointly by at least one processor, cause the RU to change the path to which the RF switch is coupled from an uplink path to a downlink path based on information such as the number of segment symbol increment commands and indicator symbols.

[0246] The methods described in the embodiments of the claims or specification of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0247] When implemented as software, a computer-readable storage medium may be provided for storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions to cause the electronic device to perform a method according to the embodiments described in the claims or specification of this disclosure. One or more programs may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., an optical disc read-only memory (CD-ROM)) or via an app store (e.g., the Play Store). TM Online distribution (e.g., downloading or uploading) or direct distribution between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium, such as the memory of a manufacturer's server, an app store's server, or a relay server.

[0248] Such programs (software modules, software) can be stored in random access memory, including non-volatile memory such as flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical storage devices (e.g., optical disc ROM (CD-ROM), digital versatile disc (DVD), or other formats), or magnetic tape cartridges. Alternatively, it can be stored in a memory configured with some or all of these. Furthermore, multiple configuration memories may be included.

[0249] Furthermore, the program can be stored in an attachable storage device that can be accessed via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WAN), or storage area network (SAN), or a combination thereof. Such a storage device can be connected to a device executing embodiments of this disclosure via an external port. Additionally, a separate storage device on the communication network can also be connected to a device executing embodiments of this disclosure.

[0250] In the specific embodiments described above, the components included in this disclosure are represented in a singular or plural form according to the presented embodiments. However, the singular or plural representation may be appropriately chosen for ease of explanation, and this disclosure is not limited to singular or plural components; even components expressed in a plural form may be configured in a singular form, or vice versa.

[0251] According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, the integrated component may still perform one or more functions of each of the multiple components in the same or similar manner as the corresponding components in the multiple components before integration. According to various embodiments, operations performed by a module, program, or other component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order or omitted, or one or more other operations may be added.

[0252] Furthermore, specific embodiments have been described in detail in this disclosure, and of course, various modifications can be made without departing from the scope of this disclosure.

Claims

1. A radio unit (RU), comprising: Radio frequency (RF) switches selectively couple to one of the uplink and downlink paths used for time division duplexing (TDD); At least one processor, including processing circuitry; as well as At least one memory, including instructions, including one or more storage media, Wherein, the instructions, when executed individually or jointly by the at least one processor, cause the RU to: Receive control plane messages from the distributed unit (DU) within the downlink receive window; Based on the segmentation type indicator and data direction information in the general header of the control plane message, segments for downlink scheduling are obtained; and Based on the information of the segmented symbol number increment command and the number of indicator symbols, the path to which the RF switch is coupled is changed from the uplink path to the downlink path.

2. The RU as claimed in claim 1, wherein, The instructions, when executed individually and jointly by the at least one processor, cause the RU to: Receive from the DU a synchronization plane message including information indicating frames for downlink transmission of the RU; and The synchronization frame structure is generated based on the synchronization plane message. The frame structure is used to send downlink signals to the user equipment.

3. The RU as claimed in claim 1, wherein, The instructions, when executed individually and jointly by the at least one processor, cause the RU to: Based on the time identifier and start symbol identifier information of the general header and the parameters of the downlink receive window of the control plane message, the downlink receive window is obtained, and The time identifier includes frame ID, subframe ID, and time slot ID.

4. The RU as described in claim 3, wherein, The instructions, when executed individually and jointly by the at least one processor, cause the RU to: Identify whether the control plane message was received within the interval of the downlink receive window; In response to the control plane message being received within the interval, a segment of the control plane message is obtained; and In response to at least a portion of the control plane messages being received outside the interval, another control plane message is obtained.

5. The RU as described in claim 1, in, The data direction information indicates the downlink, and The segmentation type indicator indicates segmentation type 1 or segmentation type 5.

6. The RU as claimed in claim 1, wherein, The instructions, when executed individually or jointly by the at least one processor, cause the RU to: Based on the data direction information and the segment type indicator, another segment is obtained for downlink scheduling, and The other segment in the control plane message follows the first segment.

7. The RU as claimed in claim 1, wherein, The instructions, when executed individually or jointly by the at least one processor, cause the RU to: Based on the symbols indicated by the start symbol identification information in the general header, the number of symbols, and the symbol number increment command, one or more downlink symbols allocated in the segment are obtained; and Information indicating the one or more downlink symbols is stored in the memory.

8. The RU as described in claim 7, in, When the symbol number increment command indicates 0, the one or more downlink symbols include the symbol, and Wherein, when the symbol number increment command indicates 1, the one or more downlink symbols include another symbol following the symbol.

9. The RU as described in claim 7, in, The one or more downlink symbols are scheduled based on the number of symbols.

10. The RU as described in claim 7, in, The memory comprises a memory region with two time slots, and The information indicating the one or more downlink symbols is stored in the memory region at a location corresponding to the one or more downlink symbols.

11. The RU as claimed in claim 7, wherein, The instructions, when executed individually and jointly by the at least one processor, cause the RU to: The detection includes the last symbol at the end point of the downlink receive window; In response to the detection of the last symbol, a control signal corresponding to the one or more downlink symbols is generated based on the information stored in the memory indicating the one or more downlink symbols; The RF switch is coupled to the downlink path based on the control signal; and Downlink signals are transmitted to the user equipment on one or more downlink symbols via the downlink path coupled to the RF switch.

12. The RU as described in claim 11, in, The control signal is generated before a specified time interval starting from the initial symbol in the one or more downlink symbols, and The specified time interval is identified based on the processing delay used to generate the control signal.

13. The RU as claimed in claim 1, wherein, The instructions, when executed individually or jointly by the at least one processor, cause the RU to: Uplink control plane messages are received from the DU in another downlink receive window following the downlink receive window; and Based on the uplink control plane message, the path to which the RF switch is coupled is changed from the downlink path to the uplink path; Receive another control plane message from the DU within the other downlink receive window; Based on the segment type indicator and data direction information in the general header of the other control plane message, another segment is obtained for downlink scheduling; and Based on the information of the symbol number increment command and the number of indicator symbols in the other segment, the path to which the RF switch is coupled is changed from the uplink path to the downlink path. The resources indicated by the control plane message and the other control plane message are used for downlink signals transmitted on symbols in the time slot.

14. A method performed by a radio unit (RU), comprising: Receive control plane messages from the distributed unit (DU) within the downlink receive window; Based on the segmentation type indicator and data direction information in the general header of the control plane message, segments for downlink scheduling are obtained; as well as Based on information about the number of symbols incrementing in the segment and the number of indicator symbols, the path to which a radio frequency (RF) switch selectively coupled to one of the uplink and downlink paths for time division duplex (TDD) is coupled is changed from the uplink path to the downlink path.

15. A non-transitory computer-readable storage medium storing one or more programs comprising instructions that, when executed individually or jointly by at least one processor of a radio unit (RU) including a radio frequency (RF) switch selectively coupled to one of an uplink path and a downlink path for time division duplexing (TDD), cause the RU to: Receive control plane messages from the distributed unit (DU) within the downlink receive window; Based on the segmentation type indicator and data direction information in the general header of the control plane message, segments for downlink scheduling are obtained; and Based on the information of the segmented symbol number increment command and the number of indicator symbols, the path to which the RF switch is coupled is changed from the uplink path to the downlink path.

Images