Device and method for identifying random access signal in fronthaul interface
By enabling the RU to detect and report random access preambles to the DU within the wireless communication system, the method addresses the challenge of increased complexity and latency in identifying random access signals, improving communication efficiency and reducing call connection delays.
Patent Information
- Application Number
- PCT/KR2024/095747
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-06
- Filing Date
- 2024-04-16
- Publication Date
- 2024-11-07
AI Technical Summary
In wireless communication systems, the increasing transmission capacity and function split between base stations' distributed units (DUs) and radio units (RUs) lead to challenges in efficiently identifying random access signals across the fronthaul interface, particularly due to the increased complexity and latency in processing random access preambles, which affects call connection delays.
The proposed solution involves a method and apparatus where the radio unit (RU) detects random access preambles using extended type information and transmits detection results to the distributed unit (DU), reducing the processing time and resource usage of the fronthaul interface by providing the DU with information about detected preambles, thereby speeding up the random access procedure.
This approach reduces the processing time of the DU and shortens call connection delays by allowing the RU to perform preamble detection and report results efficiently, thereby enhancing the overall communication system's performance and reducing fronthaul interface capacity requirements.
Smart Images

Figure KR2024095747_07112024_PF_FP_ABST
Abstract
Description
Device and method for identifying random access signals within a fronthaul interface
[0001] The present disclosure relates to a device and method for identifying a random access signal within a fronthaul interface.
[0002] As transmission capacity increases in wireless communication systems, functional splitting, which functionally separates base stations, is being implemented. Through functional splitting, base stations can be divided into distributed units (DUs) and radio units (RUs). A fronthaul interface is defined for communication between the DUs and RUs.
[0003] In embodiments, a radio unit (RU) may include a transceiver. The RU may include a processor. The RU may include a memory. Instructions stored in the memory, when executed by the processor, may cause the RU to obtain, from a distributed unit (DU), a control plane message including extension type information for detection of a random access preamble. Instructions stored in the memory, when executed by the processor, may cause the RU to transmit, to the DU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The above extended type information may include indication information for detection random access preambles and information on the maximum number of reporting random access preambles.
[0004] In embodiments, a distributed unit (DU) may include a transceiver. The DU may include a processor. The DU may include a memory. Instructions stored in the memory, when executed by the processor, may cause the DU to transmit a control plane message including extension type information for detection of a random access preamble to a radio unit (RU). Instructions stored in the memory, when executed by the processor, may cause the DU to obtain an uplink message including information about random access preambles from the RU. The random access preambles may be detected based on the extension type information. The above extended type information may include indication information for detection random access preambles and information on the maximum number of reporting random access preambles.
[0005] In embodiments, a method performed by a radio unit (RU) may include obtaining, from a distributed unit (DU), a control plane message including extension type information for detection of a random access preamble. The method may include transmitting, to the DU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The extension type information may include indication information about detection random access preambles and information about a maximum number of reporting random access preambles.
[0006] In embodiments, a non-transitory computer-readable storage medium may store one or more programs, including instructions that, when executed by at least one processor of a device for a radio unit (RU) including a transceiver, cause the device to obtain, from a distributed unit (DU), a control plane message including extension type information for detection of a random access preamble. The non-transitory computer-readable storage medium may store one or more programs, including instructions that, when executed by the at least one processor, cause the device to transmit, to the DU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The extension type information may include indication information about detection random access preambles and information about a maximum number of reporting random access preambles.
[0007] Figure 1 illustrates an example of a wireless communication system.
[0008] Figure 2a illustrates an example of a fronthaul interface.
[0009] Figure 2b illustrates an example of a fronthaul interface of an open-radio access network (O-RAN).
[0010] Figure 3a illustrates an example of the functional configuration of a DU (distributed unit).
[0011] Figure 3b illustrates an example of the functional configuration of a RU (radio unit).
[0012] Figure 4 illustrates an example of function split between DU and RU.
[0013] FIG. 5a illustrates an example of how a DU detects a random access signal based on a specified functional separation.
[0014] Figure 5b illustrates an example of how an RU detects a random access signal based on a specified functional separation.
[0015] Figure 6a illustrates an example of an extension type for detection of a random access preamble.
[0016] Figure 6b illustrates an example of an extension type for detection of a random access preamble.
[0017] Figure 7 illustrates an example of an extension type for detection of a random access preamble.
[0018] Figures 8a and 8b illustrate examples of control plane messages including detection results of random access preambles.
[0019] Figures 9a to 9d illustrate examples of user plane messages including detection results of a random access preamble.
[0020] Figure 10a illustrates an example of a transmission window for an uplink message.
[0021] Figure 10b illustrates an example of a signal flow for transmitting an uplink message.
[0022] FIG. 11 illustrates an example of an operational flow for a method of reporting detection results based on extended type information for detection of a random access preamble.
[0023] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.
[0024] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.
[0025] In the following description, terms referring to signals (e.g., packet, message, signal, information, signaling), terms referring to resources (e.g., section, symbol, slot, subframe, radio frame, subcarrier, RE (resource element), RB (resource block), BWP (bandwidth part), occasion), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, message, user stream, information, bit, symbol, codeword), terms referring to channels, terms referring to network entities (distributed unit (DU), radio unit (RU), central unit (CU), CU-CP (control plane), CU-UP (user plane), O-DU (O-RAN (open radio access network) DU), O-RU (O-RAN RU), O-CU (O-RAN Terms such as CU), O-CU-UP (O-RAN CU-CP), O-CU-CP (O-RAN CU-CP)), and components of the device are provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used. In addition, terms such as '...part', '...machine', '...object', and '...body' used below may mean at least one shape structure or a unit that processes a function.
[0026] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}.
[0027] Although this disclosure describes embodiments using terminology used in certain communication standards (e.g., 3rd Generation Partnership Project (3GPP)), this is merely an example for illustrative purposes. Embodiments of this disclosure can also be applied to other communication and broadcasting systems.
[0028] Figure 1 illustrates an example of a wireless communication system.
[0029] Referring to FIG. 1, FIG. 1 illustrates a base station (110) and a terminal (120) as some of the nodes utilizing a wireless channel in a wireless communication system. Although FIG. 1 illustrates only one base station, the wireless communication system may further include other base stations identical or similar to the base station (110).
[0030] The base station (110) is a network infrastructure that provides wireless access to the terminal (120). The base station (110) has coverage defined based on the distance at which a signal can be transmitted. In addition to the base station, the base station (110) may be referred to as an 'access point (AP)', 'eNodeB (eNB)', '5th generation node', 'next generation nodeB (gNB)', 'wireless point', 'transmission / reception point (TRP)', or other terms having equivalent technical meanings.
[0031] The terminal (120) is a device used by a user and communicates with the base station (110) via a wireless channel. The link from the base station (110) to the terminal (120) is referred to as a downlink (DL), and the link from the terminal (120) to the base station (110) is referred to as an uplink (UL). In addition, although not shown in FIG. 1, the terminal (120) and another terminal may communicate with each other via a wireless channel. In this case, the link between the terminal (120) and another terminal (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used interchangeably with the PC5 interface. In some other embodiments, the terminal (120) may be operated without the involvement of a user. In one embodiment, the terminal (120) is a device that performs machine type communication (MTC) and may not be carried by the user. Additionally, according to one embodiment, the terminal (120) may be an NB (narrowband)-IoT (internet of things) device.
[0032] The terminal (120) may be referred to as a terminal, or other terms such as 'user equipment (UE),' 'customer premises equipment (CPE),' 'mobile station,' 'subscriber station,' 'remote terminal,' 'wireless terminal,' 'electronic device,' or 'user device,' or other terms having equivalent technical meanings.
[0033] The base station (110) and the terminal (120) can perform beamforming. The base station (110) and the terminal (120) can transmit and receive wireless signals in a relatively low frequency band (e.g., FR 1 (frequency range 1) of NR). In addition, the base station (110) and the terminal (120) can transmit and receive wireless signals in a relatively high frequency band (e.g., FR 2 (or, FR 2-1, FR 2-2, FR 2-3), FR 3 of NR), millimeter wave (mmWave) band (e.g., 28 GHz, 30 GHz, 38 GHz, 60 GHz)). To improve channel gain, the base station (110) and the terminal (120) can perform beamforming. Here, the beamforming can include transmission beamforming and reception beamforming. The base station (110) and the terminal (120) can impart directionality to the transmitted or received signal. To this end, the base station (110) and the terminal (120) can select serving beams through a beam search or beam management procedure. After the serving beams are selected, subsequent communication can be performed through resources that have a QCL relationship with the resource that transmitted the serving beams.
[0034] If large-scale characteristics of a channel carrying a symbol on a first antenna port can be inferred from a channel carrying a symbol on a second antenna port, the first antenna port and the second antenna port can be evaluated to have a QCL relationship. For example, the large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and a spatial receiver parameter.
[0035] Although both the base station (110) and the terminal (120) are described as performing beamforming in FIG. 1, the embodiments of the present disclosure are not necessarily limited thereto. In some embodiments, the terminal may or may not perform beamforming. Furthermore, the base station may or may not perform beamforming. That is, either only one of the base station and the terminal may perform beamforming, or neither the base station nor the terminal may perform beamforming.
[0036] In the present disclosure, a beam refers to a spatial flow of a signal in a wireless channel, and is formed by one or more antennas (or antenna elements), and this forming process may be referred to as beamforming. Beamforming may include at least one of analog beamforming and digital beamforming (e.g., precoding). Reference signals transmitted based on beamforming may include, for example, a demodulation-reference signal (DM-RS), a channel state information-reference signal (CSI-RS), a synchronization signal / physical broadcast channel (SS / PBCH), and a sounding reference signal (SRS). In addition, as a configuration for each reference signal, an IE such as a CSI-RS resource or an SRS-resource may be used, and this configuration may include information associated with the beam. Information associated with a beam may mean whether the configuration (e.g., a CSI-RS resource) uses the same spatial domain filter as another configuration (e.g., another CSI-RS resource within the same CSI-RS resource set) or a different spatial domain filter, or whether it is quasi-co-located (QCL) with a reference signal, and if so, what type it is (e.g., QCL type A, B, C, D).
[0037] In the past, in communication systems with relatively large cell radius of base stations, each base station was installed to include the functions of a digital processing unit (or DU (distributed unit)) and an RF (radio frequency) processing unit (or RU (radio unit)). However, in 4G (4 th As higher frequency bands are used in the 5G generation and / or subsequent communication systems (e.g., 5G) and the cell coverage of base stations becomes smaller, the number of base stations to cover a specific area has increased. The installation cost burden on operators to install base stations has also increased. In order to minimize the installation cost of base stations, a structure has been proposed in which the DU and RU of the base station are separated, one or more RUs are connected to one DU through a wired network, and one or more RUs are geographically distributed to cover a specific area. Hereinafter, the deployment structure and expansion examples of base stations according to various embodiments of the present disclosure are described through FIGS. 2A and 2B.
[0038] Figure 2a illustrates an example of a fronthaul interface. Unlike backhaul between a base station and the core network, fronthaul refers to the connection between entities within a wireless LAN and a base station.
[0039] Although FIG. 2A illustrates an example of a fronthaul structure between a DU (210) and one RU (220), this is merely for convenience of explanation and the present disclosure is not limited thereto. In other words, embodiments of the present disclosure can also be applied to a fronthaul structure between one DU and multiple RUs. For example, embodiments of the present disclosure can be applied to a fronthaul structure between one DU and two RUs. Furthermore, embodiments of the present disclosure can also be applied to a fronthaul structure between one DU and three RUs.
[0040] Referring to FIG. 2A, the base station (110) may include a DU (210) and a RU (220). The fronthaul (215) between the DU (210) and the RU (220) is F x It can be operated through an interface. For operation of the fronthaul (215), interfaces such as eCPRI (enhanced common public radio interface) and ROE (radio over ethernet) can be used, for example.
[0041] As communications technology advances, mobile data traffic increases, significantly increasing the bandwidth requirements for the fronthaul between the digital unit and the radio unit. In deployments such as C-RAN (centralized / cloud radio access network), the DU performs functions for the packet data convergence protocol (PDCP), radio link control (RLC), media access control (MAC), and physical layer (PHY), while the RU can be implemented to perform additional functions for the PHY layer in addition to its radio frequency (RF) functions.
[0042] The DU (210) may be responsible for upper layer functions of a wireless network. For example, the DU (210) may perform functions of the MAC layer and a part of the PHY layer. Here, a part of the PHY layer refers to functions performed at a higher level among the functions of the PHY layer, and may include, for example, channel encoding (or channel decoding), scrambling (or descrambling), modulation (or demodulation), and layer mapping (or layer demapping). According to an embodiment, if the DU (210) complies with the O-RAN standard, it may be referred to as an O-DU (O-RAN DU). The DU (210) may be replaced with a first network entity for a base station (e.g., gNB) in embodiments of the present disclosure, if necessary.
[0043] The RU (220) may be responsible for lower layer functions of a wireless network. For example, the RU (220) may perform a part of the PHY layer, an RF function. Here, a part of the PHY layer refers to functions of the PHY layer that are performed at a relatively lower level than the DU (210), and may include, for example, iFFT transformation (or FFT transformation), CP insertion (CP removal), and digital beamforming. The RU (220) may be referred to as an 'access unit (AU)', an 'access point (AP)', a 'transmission / reception point (TRP)', a 'remote radio head (RRH)', a 'radio unit (RU)', or other terms having an equivalent technical meaning thereto. According to an embodiment, when the RU (220) complies with the O-RAN standard, it may be referred to as an O-RU (O-RAN RU). RU (220) may be replaced with a second network entity for a base station (e.g., gNB) in embodiments of the present disclosure as needed.
[0044] Although the base station (110) is described in FIG. 2A as including a DU (210) and a RU (220), the embodiments of the present disclosure are not limited thereto. The base station according to the embodiments may be implemented in a distributed deployment according to a centralized unit (CU) configured to perform functions of upper layers of an access network (e.g., packet data convergence protocol (PDCP), radio resource control (RRC)) and a distributed unit (DU) configured to perform functions of lower layers. For example, the digital unit (DU) (210) may be implemented by separating into a centralized unit (CU) (or a control unit (CU)) and a distributed unit (DU). Between the core (e.g., 5GC (5G core) or NGC (next generation core)) network and the radio network (RAN), the base station can be implemented in a structure in which the CU (centralized unit), DU (distributed unit), and RU (radio unit) are arranged in that order. The interface between the CU (centralized unit) and the DU (distributed unit) can be referred to as the F1 interface.
[0045] A centralized unit (CU) can be connected to one or more DUs and can be responsible for functions at a higher layer than the DU. For example, the CU can be responsible for functions at the RRC (radio resource control) and PDCP (packet data convergence protocol) layers, while the DU and RU can be responsible for functions at lower layers. The DU can perform some functions (high PHY) of the RLC (radio link control), MAC (media access control), and PHY (physical) layers, while the RU can be responsible for the remaining functions (low PHY) of the PHY layer. In addition, for example, a digital unit (DU) can be included in a distributed unit (DU) depending on the implementation of a distributed deployment of the base station. Hereinafter, unless otherwise defined, the operations of DU (digital unit) and RU are described, but various embodiments of the present disclosure can be applied to both a base station arrangement including a CU and an arrangement in which a DU is directly connected to a core network (i.e., a base station in which the CU and DU are integrated into a single entity (e.g., an NG-RAN node)).
[0046] Figure 2b illustrates an example of a fronthaul interface of an open-radio access network (O-RAN). In Figure 2b, an eNB or gNB is exemplified as a base station (110) according to a distributed deployment.
[0047] Referring to FIG. 2b, the base station (110) may include an O-DU (251) and O-RUs (253-1, ..., 253-n). Hereinafter, for convenience of explanation, the operation and function of the O-RU (253-1) may be understood as a description of each of the other O-RUs (e.g., O-RU (253-n)).
[0048] The O-DU (251) is a logical node that includes functions, excluding functions exclusively assigned to the O-RU (253-1), among the functions of a base station (e.g., eNB, gNB) according to FIG. 4 described below. The O-DU (251) can control the operation of the O-RUs (253-1, ..., 253-n). The O-DU (251) may be referred to as an LLS (lower layer split) CU (central unit). The O-RU (253-1) is a logical node that includes a subset of the functions of a base station (e.g., eNB, gNB) according to FIG. 4 described below. Real-time aspects of control plane (C-plane) communication and user plane (U-plane) communication with the O-RU (253-1) can be controlled by the O-DU (251).
[0049] The O-DU (251) can communicate with the O-RU (253-1) through an LLS interface. The LLS interface corresponds to a fronthaul interface. The LLS interface refers to a logical interface between the O-DU (251) and the O-RU (253-1) that utilizes lower layer functional split (i.e., intra-PHY based functional split). The LLS-C between the O-DU (251) and the O-RU (253-1) provides the C-plane through the LLS interface. The LLS-U between the O-DU (251) and the O-RU (253-1) provides the U-plane through the LLS interface.
[0050] In FIG. 2B, to explain the O-RAN, entities of the base station (110) are described as O-DU and O-RU. However, these names are not to be construed as limiting the embodiments of the present disclosure. In the embodiments described below, it is obvious that the operations of the DU (210) can be performed by the O-DU (251). The description of the DU (210) can be applied to the O-DU (251). Similarly, in the embodiments described below, it is obvious that the operations of the RU (220) can be performed by the O-RU (253-1). The description of the RU (220) can be applied to the O-DU (253-1).
[0051] Figure 3a illustrates an example of the functional configuration of a DU (distributed unit).
[0052] The configuration illustrated in Fig. 3a can be understood as a configuration of the DU (210) of Fig. 2a (or the O-DU (251) of Fig. 2b) as part of a base station. Terms such as "...unit" and "...unit" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.
[0053] Referring to FIG. 3a, DU (210) includes a transceiver (310), memory (320), and processor (330).
[0054] The transceiver (310) can perform functions for transmitting and receiving signals in a wired communication environment. The transceiver (310) can include a wired interface for controlling direct connections between devices via a transmission medium (e.g., copper wire, optical fiber). For example, the transceiver (310) can transmit electrical signals to other devices via copper wire, or perform conversion between electrical signals and optical signals. The DU (210) can communicate with a radio unit (RU) via the transceiver (310). The DU (210) can be connected to a core network or a CU in a distributed arrangement via the transceiver (310).
[0055] The transceiver (310) may perform functions for transmitting and receiving signals in a wireless communication environment. For example, the transceiver (310) may perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the transceiver (310) generates complex symbols by encoding and modulating the transmitted bit stream. In addition, when receiving data, the transceiver (310) restores the received bit stream by demodulating and decoding the baseband signal. In addition, the transceiver (310) may include multiple transmission and reception paths. In addition, according to one embodiment, the transceiver (310) may be connected to the core network or other nodes (e.g., an integrated access backhaul (IAB).
[0056] The transceiver (310) can transmit and receive signals. For example, the transceiver (310) can transmit a management plane (M-plane) message. For example, the transceiver (310) can transmit a management plane (S-plane) message. For example, the transceiver (310) can transmit a control plane (C-plane) message. For example, the transceiver (310) can transmit a user plane (U-plane) message. For example, the transceiver (310) can receive a user plane message. Although only the transceiver (310) is illustrated in FIG. 3A, in other implementations, the DU (210) may include two or more transceivers.
[0057] The transceiver (310) transmits and receives signals as described above. Accordingly, all or part of the transceiver (310) may be referred to as a "communication unit," a "transmitter," a "receiver," or a "transmitter-receiver unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the transceiver (310) performs the processing described above.
[0058] Although not illustrated in FIG. 3A, the transceiver (310) may further include a backhaul transceiver for connection to the core network or other base stations. The backhaul transceiver provides an interface for communicating with other nodes within the network. That is, the backhaul transceiver converts a bit stream transmitted from the base station to other nodes, such as other access nodes, other base stations, upper nodes, the core network, etc., into a physical signal, and converts a physical signal received from other nodes into a bit stream.
[0059] The memory (320) stores data such as basic programs, application programs, and setting information for the operation of the DU (210). The memory (320) may be referred to as a storage unit. The memory (320) may be composed of volatile memory, nonvolatile memory, or a combination of volatile memory and nonvolatile memory. In addition, the memory (320) provides stored data upon request from the processor (330).
[0060] The processor (330) controls the overall operations of the DU (210). The processor (380) may be referred to as a control unit. For example, the processor (330) transmits and receives signals through the transceiver (310) (or through the backhaul communication unit). In addition, the processor (330) records and reads data from the memory (320). In addition, the processor (330) may perform the functions of the protocol stack required by the communication standard. Although only the processor (330) is illustrated in FIG. 3A, the DU (210) may include two or more processors according to other implementation examples.
[0061] For example, the processor (330) may include various processing circuits and / or multiple processors. For example, the term "processor" as used herein, including in the claims, may include various processing circuits including at least one processor, one or more of which may be configured to individually and / or collectively perform the various functions described below in a distributed manner. As used herein, when "processor," "at least one processor," and "one or more processors" are described as being configured to perform various functions, these terms encompass, for example, and without limitation, situations where one processor performs some of the recited functions and other processor(s) perform other parts of the recited functions, and also situations where one processor may perform all of the recited functions. Additionally, the at least one processor may include a combination of processors that perform the various functions enumerated / disclosed, for example, in a distributed manner. At least one processor may execute program instructions to achieve or perform the various functions.
[0062] The configuration of DU (210) illustrated in FIG. 3A is merely an example, and examples of DUs performing embodiments of the present disclosure are not limited to the configuration illustrated in FIG. 3A. In some embodiments, some configurations may be added, deleted, or changed.
[0063] Figure 3b illustrates an example of the functional configuration of a RU (radio unit).
[0064] The configuration illustrated in Fig. 3b can be understood as a configuration of the RU (220) of Fig. 2a or the O-RU (253-1) of Fig. 2b as part of a base station. Terms such as "... unit" and "... unit" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.
[0065] Referring to FIG. 3b, the RU (220) includes an RF transceiver (360), a fronthaul transceiver (365), a memory (370), and a processor (380).
[0066] The RF transceiver (360) performs functions for transmitting and receiving signals via a wireless channel. For example, the RF transceiver (360) upconverts a baseband signal into an RF band signal and transmits it via an antenna, and downconverts an RF band signal received via the antenna into a baseband signal. For example, the RF transceiver (360) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like.
[0067] The RF transceiver (360) may include multiple transmission and reception paths. Furthermore, the RF transceiver (360) may include an antenna unit. The RF transceiver (360) may include at least one antenna array composed of multiple antenna elements. In terms of hardware, the RF transceiver (360) may be composed of digital circuits and analog circuits (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the RF transceiver (360) may include multiple RF chains. The RF transceiver (360) may perform beamforming. The RF transceiver (360) may apply beamforming weights to a signal to be transmitted and received in order to impart directionality according to the settings of the processor (380). According to one embodiment, the RF transceiver (360) may include an RF (radio frequency) block (or RF unit).
[0068] According to one embodiment, the RF transceiver (360) can transmit and receive signals on a radio access network. For example, the RF transceiver (360) can transmit a downlink signal. The downlink signal can include a synchronization signal (SS), a reference signal (RS) (e.g., a cell-specific reference signal (CRS), a demodulation (DM)-RS), system information (e.g., a MIB, a SIB, remaining system information (RMSI), other system information (OSI)), a configuration message, control information, or downlink data. In addition, for example, the RF transceiver (360) can receive an uplink signal. The uplink signal may include a random access related signal (e.g., a random access preamble (RAP) (or Msg1 (message 1)), Msg3 (message 3)), a reference signal (e.g., a sounding reference signal (SRS), DM-RS), or a power headroom report (PHR). Although only the RF transceiver (360) is illustrated in FIG. 3b, in other implementation examples, the RU (220) may include two or more RF transceivers.
[0069] The fronthaul transceiver (365) can transmit and receive signals. According to one embodiment, the fronthaul transceiver (365) can transmit and receive signals on the fronthaul interface. For example, the fronthaul transceiver (365) can receive a management plane (M-plane) message. For example, the fronthaul transceiver (365) can receive a management plane (S-plane) message. For example, the fronthaul transceiver (365) can receive a control plane (C-plane) message. For example, the fronthaul transceiver (365) can transmit a user plane (U-plane) message. For example, the fronthaul transceiver (365) can receive a user plane message. Although only the fronthaul transceiver (365) is shown in FIG. 3b, according to other implementation examples, the RU (220) may include two or more fronthaul transceivers.
[0070] The RF transceiver (360) and the fronthaul transceiver (365) transmit and receive signals as described above. Accordingly, all or part of the RF transceiver (360) and the fronthaul transceiver (365) may be referred to as a 'communication unit', a 'transmitter unit', a 'receiver unit', or a 'transmitter-receiver unit'. In addition, in the following description, transmission and reception performed through a wireless channel are used to mean that the processing as described above is performed by the RF transceiver (360). In the following description, transmission and reception performed through a wireless channel are used to mean that the processing as described above is performed by the RF transceiver (360).
[0071] The memory (370) stores data such as basic programs, application programs, and setting information for the operation of the RU (220). The memory (370) may be referred to as a storage unit. The memory (370) may be configured as volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. In addition, the memory (370) provides the stored data according to a request from the processor (380). According to one embodiment, the memory (370) may include a memory for conditions, commands, or setting values related to the SRS transmission method.
[0072] The processor (380) controls the overall operations of the RU (220). The processor (380) may be referred to as a control unit. For example, the processor (380) transmits and receives signals through the RF transceiver (360) or the fronthaul transceiver (365). In addition, the processor (380) records and reads data in the memory (370). In addition, the processor (380) may perform functions of a protocol stack required by a communication standard. Although only the processor (380) is illustrated in FIG. 3B, the RU (220) may include two or more processors according to other implementation examples. The processor (380) may be a set of instructions or codes stored in the memory (370), or may be a storage space that stores instructions / codes or instructions / codes that are at least temporarily residing in the processor (380), or may be a part of the circuitry that constitutes the processor (380). Additionally, the processor (380) may include various modules for performing communication. The processor (380) may control the RU (220) to perform operations according to the embodiments described below.
[0073] For example, the processor (380) may include various processing circuits and / or multiple processors. For example, the term "processor" as used herein, including in the claims, may include various processing circuits including at least one processor, one or more of which may be configured to individually and / or collectively perform the various functions described below in a distributed manner. As used herein, when "processor," "at least one processor," and "one or more processors" are described as being configured to perform various functions, these terms encompass, for example, and without limitation, situations where one processor performs some of the recited functions and other processor(s) perform other parts of the recited functions, and also situations where one processor may perform all of the recited functions. Additionally, the at least one processor may include a combination of processors that perform the various functions enumerated / disclosed, for example, in a distributed manner. At least one processor may execute program instructions to achieve or perform the various functions.
[0074] The configuration of RU (220) illustrated in FIG. 3b is merely an example, and examples of RUs performing embodiments of the present disclosure are not limited to the configuration illustrated in FIG. 3b. In some embodiments, some configurations may be added, deleted, or changed.
[0075] Figure 4 illustrates an example of function split between DU and RU.
[0076] As wireless communication technology advances (e.g. 5G (5 thWith the introduction of 5G communication systems (or NR (new radio) communication systems), the frequency bands used have increased further. As the cell radius of the base station has become significantly smaller, the number of RUs required for installation has also increased further. Furthermore, in the 5G communication system, the amount of data transmitted has increased by a factor of up to ten, significantly increasing the transmission capacity of the wired network transmitted to the fronthaul. Due to the factors described above, the installation cost of the wired network in the 5G communication system may increase significantly. Therefore, in order to lower the transmission capacity of the wired network and reduce the installation cost of the wired network, 'function split' can be utilized, which transfers some of the functions of the modem of the DU to the RU, thereby lowering the transmission capacity of the fronthaul.
[0077] To reduce the burden on the DU, the role of the RU, which is traditionally solely responsible for RF functions, can be expanded to include some physical layer functions. As the RU performs higher-layer functions, its throughput increases, which can increase transmission bandwidth in the fronthaul while reducing latency requirements due to response processing. However, as the RU performs higher-layer functions, virtualization gains decrease, and the RU's size, weight, and cost increase. Considering the trade-offs between the advantages and disadvantages described above, implementing an optimal functional separation is required.
[0078] Referring to Figure 4, the functional separation in the physical layer below the MAC layer is illustrated. For the downlink (DL) that transmits a signal to a terminal through a wireless network, the base station can sequentially perform channel encoding / scrambling, modulation, layer mapping, antenna mapping, RE mapping, digital beamforming (e.g., precoding), iFFT transform / CP insertion, and RF transform. For the uplink (UL) that receives a signal from a terminal through a wireless network, the base station can sequentially perform RF transform, FFT transform / CP removal, digital beamforming (pre-combining), RE demapping, channel estimation, layer demapping, demodulation, and decoding / descrambling. The separation of uplink and downlink functions can be defined in various types depending on the needs of vendors, discussions in standards, etc., according to the above-mentioned trade-offs.
[0079] In the first functional separation (405), the RU performs the RF function, and the DU performs the PHY function. The first functional separation is one in which the PHY function is not substantially implemented in the RU, and may be referred to as Option 8, for example. In the second functional separation (410), the RU performs iFFT conversion / CP insertion in the DL and FFT conversion / CP removal in the UL of the PHY function, and the DU performs the remaining PHY functions. As an example, the second functional separation (410) may be referred to as Option 7-1. In the third functional separation (420a), the RU performs iFFT conversion / CP insertion in the DL and FFT conversion / CP removal and digital beamforming in the UL of the PHY function, and the DU performs the remaining PHY functions. As an example, the third functional separation (420a) may be referred to as Option 7-2x Category A. In the fourth functional separation (420b), the RU performs up to digital beamforming in both the DL and UL, and the DU performs upper PHY functions after the digital beamforming. For example, the fourth functional separation (420b) may be referred to as Option 7-2x Category B. In the fifth functional separation (425), the RU performs up to RE mapping (or RE demapping) in both the DL and UL, and the DU performs upper PHY functions after RE mapping (or RE demapping). For example, the fifth functional separation (425) may be referred to as Option 7-2. In the sixth functional separation (430), the RU performs up to modulation (or demodulation) in both the DL and UL, and the DU performs upper PHY functions after modulation (or demodulation). For example, the sixth functional separation (430) may be referred to as Option 7-3. In the seventh functional separation (440), the RU performs encoding / scrambling (or decoding / descrambling) in both the DL and UL, and the DU performs subsequent upper PHY functions up to modulation (or demodulation). For example, the seventh functional separation (440) may be referred to as Option 6.
[0080] In one embodiment, when a large amount of signal processing is expected, such as in the FR 1 MMU, functional separation at a relatively high layer (e.g., the fourth functional separation (420b)) may be required to reduce fronthaul capacity. In addition, functional separation at too high a layer (e.g., the sixth functional separation (430)) may complicate the control interface and cause a burden on the implementation of the RU due to the inclusion of a large number of PHY processing blocks within the RU. Therefore, appropriate functional separation may be required depending on the arrangement and implementation method of the DU and the RU.
[0081] In one embodiment, if the precoding of data received from the DU cannot be processed (i.e., if the precoding capability of the RU is limited), the third functional separation (420a) or a lower functional separation (e.g., the second functional separation (410)) may be applied. Conversely, if the DU has the capability to process the precoding of data received from the DU, the fourth functional separation (420b) or a higher functional separation (e.g., the sixth functional separation (430)) may be applied.
[0082] Hereinafter, embodiments in the present disclosure are described based on the third functional separation (420a) (which may be referred to as category A (CAT-A)) or the fourth functional separation (420b) (which may be referred to as category B (CAT-B)) for performing beamforming processing in an RU unless otherwise specified. The O-RAN standard distinguishes the types of O-RUs depending on whether the precoding function is located at the interface of the O-DU or the O-RU interface. An O-RU that does not perform precoding (i.e., has low complexity) may be referred to as a CAT-A O-RU. An O-RU that performs precoding may be referred to as a CAT-B O-RU.
[0083] Hereinafter, the term "upper-PHY" refers to physical layer processing performed in the DU of the fronthaul interface. For example, the upper-PHY may include FEC encoding / decoding, scrambling, and modulation / demodulation. Hereinafter, the term "lower-PHY" refers to physical layer processing performed in the RU of the fronthaul interface. For example, the lower-PHY may include FFT / iFFT, digital beamforming, and PRACH (physical random access channel) extraction and filtering. However, the above-described criteria do not exclude embodiments through other functional separations. The functional configuration, signaling, or operation described below may be applied not only to the third functional separation (420a) or the fourth functional separation (420b), but also to other functional separations.
[0084] Embodiments of the present disclosure exemplarily describe the standards of eCPRI and O-RAN as fronthaul interfaces when transmitting messages between a DU (e.g., DU (210) of FIG. 2A) and an RU (e.g., RU (220) of FIG. 2A). The Ethernet payload of the message may include an eCPRI header, an O-RAN header, and additional fields. Hereinafter, various embodiments of the present disclosure are described using standard terms of eCPRI or O-RAN, but other expressions having equivalent meanings to each term may be used instead in various embodiments of the present disclosure.
[0085] The fronthaul transport protocol can use Ethernet and eCPRI, which are easy to share with networks. The Ethernet payload can include an eCPRI header and an O-RAN header. The eCPRI header can be located at the beginning of the Ethernet payload. The contents of the eCPRI header are as follows.
[0086] 1) ecpriVersion (4 bits): This parameter indicates the eCPRI protocol version.
[0087] 2) ecpriReserved (3 bits): This parameter is reserved for further use by eCPRI.
[0088] 3) ecpriConcatenation (1 bit): This parameter indicates when eCPRI concatenation is in use.
[0089] 4) ecpriMessage (1 byte): This parameter indicates the type of service carried by the message type. For example, the parameter indicates an IQ data message, a real-time control data message, or a transmission network delay measurement message.
[0090] 5) ecpriPayload (2 bytes): This parameter indicates the byte size of the payload portion of the eCPRI message.
[0091] 6) ecpriRtcid / ecpriPcid (2 bytes): This parameter is the eAxC (extended antenna-carrier) identifier (eAxC ID) and identifies a specific data flow associated with each C-plane (ecpriRtcid) or U-plane (ecpriPcid) message.
[0092] 7) ecpriSeqid (2 bytes): This parameter provides unique message identification and ordering at both levels. The first octet of this parameter is a sequence ID used to identify the order of messages within the eAxC message stream. The sequence ID is used to ensure that all messages are received and to reorder out-of-order messages. The second octet of this parameter is a subsequence ID. The subsequence ID is used to ensure ordering and implement reordering when radio-transport-level (eCPRI or IEEE-1914.3) fragmentation occurs.
[0093] The eAxC identifier (ID) includes a band and sector identifier ('BandSector_ID'), a component carrier identifier ('CC_ID'), a spatial stream identifier ('RU_Port_ID'), and a distributed unit identifier ('DU_Port_ID'). The bit allocation of the eAxC ID can be distinguished as follows.
[0094] 1) DU_port ID: The DU_port ID is used to distinguish processing units (e.g., different baseband cards) in the O-DU. The O-DU is expected to allocate bits for the DU_port ID, and the O-RU is expected to append the same value to the UL U-plane message carrying the same sectionId data.
[0095] 2) BandSector_ID: Aggregated cell identifier (band and sector distinction supported by O-RU).
[0096] 3) CC_ID: CC_ID identifies the carrier component supported by the O-RU.
[0097] 4) RU_port ID: The RU_port ID specifies logical flows such as data layer or spatial streams, and signaling channels that require separate numerologies (e.g. PRACH) or special antenna allocation such as SRS.
[0098] The application protocol of the fronthaul may include a control plane (C-plane), a user plane (U-plane), a synchronization plane (S-plane), and a management plane (M-plane).
[0099] The control plane may be configured to provide scheduling information and beamforming information via control messages. The control plane refers to real-time control between DUs and RUs. The user plane may include IQ sample data transmitted between DUs and RUs. The user plane may include user downlink data (IQ data or SSB / RS), uplink data (IQ data or SRS / RS), or PRACH data. A weight vector of the beamforming information described above may be multiplied by the user's data. The synchronization plane generally refers to traffic between DUs and RUs for a synchronization controller (e.g., IEEE grand master). The synchronization plane may be related to timing and synchronization. The management plane refers to non-real-time control between DUs and RUs. The management plane may be related to initial setup, non-realtime reset or reset, and non-realtime report.
[0100] Control plane messages, or C-plane messages, can be encapsulated based on a two-layer header approach. The first layer can consist of the eCPRI common header or the IEEE 1914.3 common header, which contains fields used to indicate the message type. The second layer is the application layer, which contains fields necessary for control and synchronization. Within the application layer, sections define the characteristics of U-plane data transmitted or received on a beam with a single pattern ID. The following section types are supported within the C-plane:
[0101] Section Type can indicate the purpose of control messages transmitted on the control plane. For example, the purposes of each Section Type are as follows.
[0102] 1) sectionType=0: Used to indicate resource blocks or symbols not used in DL or UL.
[0103] 2) sectionType=1: Used for most DL / UL wireless channels. Here, 'most' indicates channels that do not require time or frequency offsets, such as those required for mixed numerology channels.
[0104] 3) sectionType=2: reserved for further use
[0105] 4) sectionType=3: PRACH and mixed-numerology channels. Channels that require a time or frequency offset or differ from the nominal SCS value(s).
[0106] 5) sectionType=4: reserved for further use
[0107] 6) sectionType=5: UE scheduling information. Transmits UE scheduling information so that the RU can perform real-time BF weight calculations (O-RAN optional BF method).
[0108] 7) sectionType=6: Transmits UE-specific channel information. Periodically transmits UE channel information to enable the RU to perform real-time BF weight calculations (O-RAN optional BF method).
[0109] 8) sectionType=7: Used for LAA support
[0110] Open Radio Access Network (ORAN) is an organization that defines fronthaul interface standards between DUs and RUs according to various functional separation structures, and provides a standard interface in a separation structure that applies Ethernet (e.g., 7-2x functional separation structure).
[0111] FIG. 5a illustrates an example of how a DU detects a random access signal based on a specified functional separation.
[0112] FIG. 5A illustrates an example (500) of a method for a DU (210) to detect a random access signal based on the third functional separation (420a) (or the fourth functional separation (420b)) of FIG. 4. For example, the random access signal may include a random access preamble. For example, the random access preamble may be referred to as a preamble or a physical random access channel (PRACH). For example, the random access preamble may be included in message 1 (MSG1).
[0113] Referring to example (500), the DU (210) may include a plurality of components. For example, the plurality of components of the DU (210) may include an uplink scheduler (UL scheduler) (501), a control plane message generator (C-plane Msg generator) (503), a user plane message processor (U-plane Msg processor) (517), and a modem (modulator and demodulator, MODEM) (519). The plurality of components of the DU (210) illustrated in example (500) may be implemented by hardware, software, or a combination of hardware and software.
[0114] Also, referring to the example, the RU (220) may include a plurality of components. For example, the plurality of components of the RU (220) may include a control plane message interpreter (C-plane Msg interpreter) (505), a weight generator (507), a weight memory (509), a fast Fourier transform (FFT) module (511), a weight multiplication (513) (or a pre-combining module), and a user plane message processor (515). The plurality of components of the RU (220) illustrated in the example (550) may be implemented by hardware, software, or a combination of hardware and software. For example, the RU (220) may be referred to as a massive MIMO (multiple input multiple output) unit (MMU).
[0115] Referring to FIG. 5a, DU (210) can generate a control plane message based on scheduling information provided from UL scheduler (501) through control plane message generator (503). For example, DU (210) can transmit (or provide) the generated control plane message to RU (220).
[0116] For example, the RU (220) can identify configuration information based on the received (or acquired) control plane message through the control plane message interpreter (505). For example, the RU (220) can identify a scheduling beam index through the weight generator (507) based on the control plane message. For example, the RU (220) can identify a weight corresponding to the scheduling beam index through the weight memory (509). In addition, the RU (220) can receive the random access preamble from a user equipment (not shown). For example, the RU (220) can receive a message including the random access preamble from the user equipment. For example, the RU (220) can perform an FFT on the random access preamble through the FFT module (511). For example, the RU (220) may perform pre-combining through a weight multiplier (513) based on the output of the FFT module (511) and the weights. At this time, the pre-combining may include an operation of grouping antenna ports to reduce the number of paths. The RU (220) may generate IQ (in-phase and quadrature phase) data for the random access preamble through a user plane message processor (515) and generate a user plane message for the IQ data. For example, the RU (220) may transmit (or provide) the generated user plane message to the DU (210).
[0117] For example, DU (210) may process the received (or acquired) user plane message via user plane message processor (517). For example, DU (210) may identify the IQ data for the PRACH from the user plane message. DU (210) may perform PRACH detection via modem (519) based on the IQ data. For example, the PRACH detection may include identifying a specific random access preamble used in performing communication with the terminal. A random access procedure may be performed based on the specific random access preamble. For example, based on the specific random access preamble, Message 2 (MSG2) may be transmitted from RU (220) to the terminal. For example, Message 2 may be referred to as a random access response (RAR).
[0118] Referring to example (500) of FIG. 5A, the RU (220) may convert the information on the random access preamble received from the terminal into IQ data without performing detection, and provide the converted IQ data to the DU (210) through a user plane message. The DU (210) may perform PRACH detection based on the user plane message. At this time, a designated resource region may be required for the RU (220) to provide the user plane message to the DU (210). For example, if the random access preamble is a long preamble, 72 RBs (resource blocks) may be required. In other words, the RU (220) transmitting the user plane message to the DU (210) through the fronthaul (215) (e.g., eCPRI) may cause a capacity limitation of the fronthaul (215). In addition, since detection of the random access preamble is performed in DU (210), the number of objects that DU (210) must process increases, so the processing time for random access increases, and a lot of time may be required to complete the random access.
[0119] Hereinafter, the present disclosure proposes a method in which an RU (220) receives a random access preamble (or random access signal) for performing signal synchronization, and the RU (220) detects the random access preamble. Detecting the random access preamble may include identifying an index of a specific random access preamble and identifying a timing advance (TA) according to the index. By providing information about the detected random access preamble to a DU (210), the device and method according to embodiments of the present disclosure can reduce the processing time of the DU (210) and perform a random access procedure more quickly. The fact that the random access procedure is performed relatively quickly may indicate that a call connection delay time is shortened.
[0120] Figure 5b illustrates an example of how an RU detects a random access signal based on a specified functional separation.
[0121] FIG. 5b illustrates an example (550) of how RU (220) detects the random access signal based on the sixth functional separation (430) of FIG. 4. However, the embodiments of the present disclosure are not limited thereto. For example, the embodiments of the present disclosure can be applied to functional separations substantially identical to the sixth functional separation (430).
[0122] Referring to example (550), DU (210) may include a plurality of components. For example, the plurality of components of DU (210) may include an uplink scheduler (551), a control plane message generator (553), an uplink message processor (U-plane Msg processor) (569), and a RACH scheduler (571). For example, the uplink message may include a user plane message and a control plane message. For example, the RACH scheduler (571) may be included in the modem (519) of example (500). The plurality of components of DU (210) illustrated in example (550) may be implemented by hardware, software, or a combination of hardware and software.
[0123] Also, referring to the example, the RU (220) may include a plurality of components. For example, the plurality of components of the RU (220) may include a control plane message interpreter (555), a weight generator (557), a weight memory (559), an FFT module (561), a weight multiplier (563) (or a pre-combining module), a PRACH detector (565), and an uplink message processor (567). For example, the uplink message may include a user plane message and a control plane message. The plurality of components of the RU (220) illustrated in the example (550) may be implemented by hardware, software, or a combination of hardware and software. For example, the RU (220) may be referred to as a massive MIMO (multiple input multiple output) unit (MMU).
[0124] Referring to FIG. 5b, the DU (210) may generate a control plane message based on scheduling information provided from the UL scheduler (551) through the control plane message generator (553). For example, the DU (210) may transmit (or provide) the generated control plane message to the RU (220). For example, the control plane message may include extended type information used by the RU (220) to perform detection for a random access preamble. For example, the extended type information may be used in concatenation with a section type associated with the control plane message. For example, the extended type information may be used for a specific section type. For example, the extended type information may include information for detection of the random access preamble. The extended type information for detection of the random access preamble is described in detail in FIGS. 6a, 6b, and 7 below.
[0125] For example, the RU (220) can identify configuration information based on the received (or acquired) control plane message through the control plane message interpreter (555). For example, the RU (220) can identify the extended type information. For example, the RU (220) can identify a scheduling beam index through the weight generator (557) based on the control plane message. For example, the RU (220) can identify a weight corresponding to the scheduling beam index through the weight memory (559). In addition, the RU (220) can receive the random access preamble from a user equipment (not shown). For example, the RU (220) can receive a message including a random access preamble from the user equipment. For example, the RU (220) may perform FFT on the random access preamble through the FFT module (561). For example, the RU (220) may perform pre-combining through the weight multiplier (563) based on the output of the FFT module (561) and the weight. At this time, the pre-combining may include an operation of grouping antenna ports to reduce the number of paths. The RU (220) may perform detection on the random access preamble through the PRACH detector (565). For example, the RU (220) may perform the detection based on the extension type information (or the control plane message including the extension type information). Thereafter, the RU (220) may generate an uplink message including information on the result of the detection (hereinafter, referred to as the detection result) through the uplink message processor (567). For example, the uplink message may include a control plane message or a user plane message.For example, RU (220) can transmit (or provide) the generated uplink message to DU (210). For example, the detection result included in the control plane message may include the number of detected random access preambles, the index of each of the detected random access preambles, TA, and detected energy. Specific details related thereto are described below in FIG. 8A. Alternatively, for example, the detection result included in the control plane message may include the number of detected random access preambles, the index of each of the detected random access preambles, TA, detected energy, and eAxCID. Specific details related thereto are described below in FIG. 8B. Alternatively, for example, the detection result included in the user plane message may include the number of detected random access preambles, the index of each of the detected random access preambles, TA, and detected energy. Specific details related thereto are described below in FIG. 9A and FIG. 9B. Alternatively, for example, the detection result included in the user plane message may include the number of detected random access preambles, an index of each of the detected random access preambles, a TA, detected energy, and an eAxCID. Specific details related thereto are described below in FIGS. 9c and 9d.
[0126] For example, the DU (210) can process the received (or acquired) user plane message through the uplink message processor (569). For example, the DU (210) can identify the detected random access preambles from the user plane message. The DU (210) can identify a specific random access preamble among the detected random access preambles through the RACH scheduler (571). Based on the specific random access preamble, a random access procedure can be performed. For example, based on the specific random access preamble, Message 2 (MSG2) can be transmitted from the RU (220) to the terminal.
[0127] Referring to FIG. 5B, the device and method according to embodiments of the present disclosure can reduce resource usage (or capacity) of the fronthaul interface by providing information about a detected random access preamble to the DU (210) by the RU (220). In addition, the device and method according to embodiments of the present disclosure can reduce the processing time of the DU (210) and perform the random access procedure more quickly. The fact that the random access procedure is performed relatively quickly may indicate that the call connection delay time is shortened. In the following, the present disclosure describes configuration information required for the RU (220) to perform detection of the random access preamble, the format of an uplink message for reporting the result of the detection, and a time interval for transmitting the result of the detection.
[0128] Figure 6a illustrates an example of an extension type for detection of a random access preamble.
[0129] FIG. 6A illustrates an example of an extension type (600) for detecting the random access preamble. For example, DU (210) may transmit (or provide) a control plane message including information about the extension type (600) to RU (220). Accordingly, RU (220) may perform the detection based on the control plane message (or the extension type). For example, RU (220) may receive a message (e.g., message 1) including a random access preamble from terminal (120). For example, RU (220) may perform the detection for the random access preamble based on the control plane message (or the extension type). For example, the detection may be performed based on the energy of the random access preamble.
[0130] Referring to FIG. 6A, the extension type (600) for detecting the random access preamble may include configuration information required to perform detection of the random access preamble. The extension type (600) may be referred to as extension type information or section extension (SE).
[0131] According to one embodiment, the extension type (600) may include common parameters. For example, the common parameters may include ef (extension flag) (601), extType (extension type) (603), and extLen (extension length) (605).
[0132] For example, ef(601) can be used to indicate whether another extension type following the extension type (600) exists. For example, ef(601) can have a field length of 1 bit. For example, if the value of ef(601) is 1, the other extension type may exist. Conversely, if the value of ef(601) is 0, the other extension type may not exist. ef(601) can be referenced as an extension flag.
[0133] For example, extType (603) can be used to indicate an extension type (600). For example, extType (603) can provide an extension type that provides additional parameters specific to a subject data extension. For example, extType (603) can have a field length of 7 bits. For example, extType (603) can have different values for each extension type. For example, extType (603) of the extension type (600) for the detection of the random access preamble can include 0xA. The A can represent any order or number. The A can represent a number of two or more digits (e.g., 32). An extension type (600) whose extType (603) is A can be referred to as an extension type A. The extType (603) can be referred to as an index of extension type information.
[0134] For example, extLen (605) can provide the length of the extension type (600). For example, extLen (605) can provide the length of the extension type (600) in units of 32 bits (or 4 bytes) words. For example, extLen (605) can have a field length of 8 bits. However, the embodiments of the present disclosure are not limited thereto. For example, depending on the information included in the extension type (600), extLen (605) can have a field length of 16 bits or more. extLen (605) can be referred to as the length of the extension type information. For example, the extension type (600) can have a length of 8 bytes indicated by extLen (605).
[0135] According to one embodiment, the extension type (600) may include parameters for the detection of the random access preamble. For example, the parameters for the detection may include a 1R report (1R (reception path) report) setting (606), a restricted set setting (607), a root sequence index (609), a number of cyclic shifts (611), indication information for detected random access preambles (613, 615), and a maximum number of reported random access preambles (617).
[0136] For example, the 1R report setting (606) may be used to indicate whether the detection result of the random access preamble is to be transmitted through one reception path (Rx path) associated with the random access preamble. For example, the 1R report setting (606) may have a field length of 1 bit. For example, when the 1R report setting (606) is 0, the detection result may be transmitted through each of all reception paths established between the RU (220) and the DU (210). For example, when the 1R report setting (606) is 1, the detection result may be transmitted through one reception path. The one reception path may be identified based on the random access preamble (or preamble index). For example, the one reception path may indicate a path with the highest energy among the same preamble indices. For example, the path may include an eAxC identifier (eAxcID). As described below, the detection results may be included in a control plane message (e.g., FIGS. 8a and 8b) or a user plane message (e.g., FIGS. 9a to 9d).
[0137] For example, the restricted set configuration (607) may indicate information related to mobility. For example, the value of the restricted set configuration (607) may be related to the mobility. For example, the value of the restricted set configuration (607) may include unrestrictedset, restrictedSetTypeA, and restrictedSetTypeB. For example, the restricted set configuration (607) may have a field length of 2 bits. For example, the unrestrictedset may indicate a low or medium mobility state. For example, the unrestrictedset may indicate a case where the Doppler frequency offset (or frequency offset) is less than or equal to half of the subcarrier spacing. For example, the restrictedSetTypeA may indicate a high mobility state. For example, the restrictedSetTypeA may indicate a case where the Doppler frequency offset is less than or equal to the subcarrier spacing. For example, the restrictedSetTypeB may indicate a very high mobility state. For example, the restrictedSetTypeB may indicate a case where the Doppler frequency offset is less than or equal to twice the subcarrier spacing.
[0138] For example, the root sequence index (609) may indicate an index of a root sequence for generating a random access preamble. For example, the root sequence index (609) may have a field length of 12 bits. For example, the root sequence index (609) may include a restricted set configuration (607) and 4 consecutive bits (e.g., OctetN N+2) and the following 8 bits (e.g., OctetN N+3).
[0139] For example, the number of circular shifts (Ncs )(611) may be indicated by a zero correlation zone (ZCZ) configuration (ZCZC). For example, the number of cyclic shifts (611) may have a field length of 9 bits. For example, the number of cyclic shifts (611) may include a first part of 7 bits (e.g., OctetN N+4) and a second part of 2 bits (e.g., OctetN N+5). For example, the number of cyclic shifts (611) may be associated with a restricted set configuration (607).
[0140] For example, the indication information (613, 615) for the detection random access preambles may indicate the random access preambles to be detected. For example, the indication information (613, 615) may indicate the preambles to be detected among the maximum number of configurable random access preambles (e.g., 64). For example, the detection random access preamble may be referred to as a detection target preamble, a detection preamble, a first random access preamble, or a first preamble. For example, the indication information (613, 615) may include a start number (613) of the detection random access preambles. The start number (613) of the detection random access preambles may have a field length of 6 bits. For example, the start number (613) may include an index (or start index) of the detection random access preambles. For example, the instruction information (613, 615) may include the end number (615) of the detection random access preambles. The end number (615) of the detection random access preambles may have a field length of 6 bits. For example, the end number (615) may include the index (or start index) of the detection random access preambles.
[0141] For example, the maximum number (617) of report random access preambles (report random access preambles, reporting random access preambles) may indicate the number of random access preambles that are subject to reporting. For example, the maximum number (617) may indicate the maximum number of reporting random access preambles among the detection random access preambles. The reporting random access preamble may be referred to as a reporting target preamble, a reporting preamble, a second random access preamble, or a second preamble. For example, the maximum number (617) may have a field length of 6 bits. In the above example, when the indexes of the detection random access preambles indicated by the indication information (613, 615) are 1 to 32 (i.e., 32), the maximum number (617) of reporting random access preambles may be a value smaller than 32.
[0142] Although not shown in FIG. 6A, the extended type (600) may further include additional parameters. For example, the extended type (600) may include at least one of a maximum TA threshold, a detection energy threshold, or whitening information for interference elimination. For example, the maximum TA threshold may indicate a threshold for a TA value corresponding to a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the maximum TA threshold. For example, the detection energy threshold may indicate a threshold for the energy of a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the detection energy threshold. For example, the whitening information may be used to indicate whether to perform whitening filtering for interference elimination. For example, when the value of the whitening information is 0, the RU (220) may perform the whitening filtering. In contrast, if the value of the whitening information is 1, the RU (220) may not perform (or omit) the whitening filtering.
[0143] Referring to FIG. 6A, the extended type (600) may include a plurality of reserved bits. For example, the plurality of reserved bits may be used for parameters different from the above parameters. For example, the parameters may include the maximum TA threshold, the detection energy threshold, or whitening information for interference removal.
[0144] According to one embodiment, the extension type (600) may be used in concatenation with a designated section type. For example, the designated section type may include section type 3 related to PRACH. However, the embodiments of the present disclosure are not limited thereto. For example, the extension type (600) may be used in concatenation with section type 0 for indicating uplink resources. Furthermore, according to one embodiment, the extension type (600) may be used in concatenation with a designated section type and another extension type. For example, the extension type (600) may be used in concatenation with section type 3 and extension type 10. The extension type 10 may be used to indicate a predefined beam (e.g., beam ID) for measuring a random access preamble. Alternatively, for example, the extension type (600) may be used in concatenation with section type 3 and extension type 1. The above extension type 1 can be used to indicate an undefined beam (e.g., beamforming weight value) for measuring a random access preamble.
[0145] As described above, the section extensions (or extension types) that can be supported depending on the section type can be defined through the user plane configuration module (or YANG module). The module can define the section extensions that can be supported depending on the section type as follows.
[0146]
[0147] Referring to the above table, with respect to the extension type (600), the value (uint8) of supported-section-extensions may indicate the value (A) of extType (603). In this case, the value (uint8) of section-type may indicate 3 (i.e., section type 3). However, as described above, the value of extType (603) and the value of section-type according to it are merely exemplary, and the embodiments of the present disclosure are not limited thereto.
[0148] The extended type (600) of FIG. 6A is merely exemplary, and the embodiments of the present disclosure are not limited thereto. For example, the positions and lengths of parameters within the extended type (600) may be changed.
[0149] Figure 6b illustrates an example of an extension type for detection of a random access preamble.
[0150] FIG. 6B illustrates an example of an extension type (650) for detecting the random access preamble. For example, DU (210) may transmit (or provide) a control plane message including information about the extension type (650) to RU (220). Accordingly, RU (220) may perform the detection based on the control plane message (or the extension type). For example, RU (220) may receive a message (e.g., message 1) including a random access preamble from terminal (120). For example, RU (220) may perform the detection for the random access preamble based on the control plane message (or the extension type). For example, the detection may be performed based on the energy of the random access preamble.
[0151] Referring to FIG. 6b, the extension type (650) for detecting the random access preamble may include configuration information required to perform detection of the random access preamble. The extension type (650) may be referred to as extension type information or section extension (SE).
[0152] According to one embodiment, the extension type (650) may include common parameters. For example, the common parameters may include ef (extension flag) (651), extType (extension type) (653), and extLen (extension length) (655).
[0153] For example, ef(651) can be used to indicate whether another extension type following the extension type (650) exists. For example, ef(651) can have a field length of 1 bit. For example, if the value of ef(651) is 1, the other extension type may exist. Conversely, if the value of ef(651) is 0, the other extension type may not exist. ef(651) can be referenced as an extension flag.
[0154] For example, extType (653) can be used to indicate an extension type (650). For example, extType (653) can provide an extension type that provides additional parameters specific to a subject data extension. For example, extType (653) can have a field length of 7 bits. For example, extType (653) can have different values for each extension type. For example, extType (653) of the extension type (650) for the detection of the random access preamble can include 0xA. A can represent any order or number. A can represent a number of two or more digits (e.g., 32). An extension type (650) whose extType (653) is A can be referred to as an extension type A. extType (653) can be referred to as an index of extension type information.
[0155] For example, extLen (655) can provide the length of the extension type (650). For example, extLen (655) can provide the length of the extension type (650) in units of 32 bits (or 4 bytes) words. For example, extLen (655) can have a field length of 8 bits. However, the embodiments of the present disclosure are not limited thereto. For example, depending on the information included in the extension type (650), extLen (655) can have a field length of 16 bits or more. extLen (655) can be referred to as the length of the extension type information. For example, the extension type (650) can have a length of 8 bytes indicated by extLen (655).
[0156] According to one embodiment, the extended type (650) may include parameters for the detection of the random access preamble. For example, the parameters for the detection may include a 1R report setting (656), a restricted set setting (657), a root sequence index (659), a number of cyclic shifts (661), indication information for detected random access preambles (663, 665), and a maximum number of reported random access preambles (667).
[0157] For example, the 1R report setting (656) may be used to indicate whether the detection result of the random access preamble is to be transmitted through one reception path (Rx path) associated with the random access preamble. For example, the 1R report setting (656) may have a field length of 1 bit. For example, when the 1R report setting (656) is 0, the detection result may be transmitted through each of all reception paths established between the RU (220) and the DU (210). For example, when the 1R report setting (656) is 1, the detection result may be transmitted through one reception path. The one reception path may be identified based on the random access preamble (or preamble index). For example, the one reception path may indicate a path with the highest energy among the same preamble indices. For example, the path may include an eAxC identifier (eAxcID). As described below, the detection results may be included in a control plane message (e.g., FIGS. 8a and 8b) or a user plane message (e.g., FIGS. 9a to 9d).
[0158] For example, the restricted set configuration (657) may indicate information related to mobility. For example, the value of the restricted set configuration (657) may be related to the mobility. For example, the value of the restricted set configuration (657) may include unrestrictedset, restrictedSetTypeA, and restrictedSetTypeB. For example, the restricted set configuration (657) may have a field length of 2 bits. For example, the unrestrictedset may indicate a low or medium mobility state. For example, the unrestrictedset may indicate a case where the Doppler frequency offset (or frequency offset) is less than or equal to half of the subcarrier spacing. For example, the restrictedSetTypeA may indicate a high mobility state. For example, the restrictedSetTypeA may indicate a case where the Doppler frequency offset is less than or equal to the subcarrier spacing. For example, the restrictedSetTypeB may indicate a very high mobility state. For example, the restrictedSetTypeB may indicate a case where the Doppler frequency offset is less than or equal to twice the subcarrier spacing.
[0159] For example, the root sequence index (659) may indicate the index of the root sequence for generating a random access preamble. For example, the root sequence index (659) may have a field length of 12 bits. For example, the root sequence index (659) may include a restricted set configuration (657) and 4 consecutive bits (e.g., OctetN N+2) and the following 8 bits (e.g., OctetN N+3).
[0160] For example, the number of circular shifts (N-cs )(661) may be indicated by a zero correlation zone (ZCZ) configuration (ZCZC). For example, the number of cyclic shifts (661) may have a field length of 9 bits. For example, the number of cyclic shifts (661) may include a first part of 7 bits (e.g., OctetN N+4) and a second part of 2 bits (e.g., OctetN N+5). For example, the number of cyclic shifts (661) may be associated with a restricted set configuration (657).
[0161] For example, the indication information (663, 665) for the detection random access preambles may indicate the random access preambles to be detected. For example, the indication information (663, 665) may indicate the preambles to be detected among the maximum number of configurable random access preambles (e.g., 64). For example, the detection random access preamble may be referred to as a detection target preamble, a detection preamble, a first random access preamble, or a first preamble. For example, the indication information (663, 665) may include a start number (663) of the detection random access preambles. The start number (663) of the detection random access preambles may have a field length of 6 bits. For example, the start number (663) may include an index (or start index) of the detection random access preambles. For example, the instruction information (613, 615) may include the length (665) of the detection random access preambles. The length (665) of the detection random access preambles may have a field length of 6 bits. For example, the length (665) may include the number of consecutive detection random access preambles from the start number (663).
[0162] For example, the maximum number (667) of report random access preambles may indicate the number of random access preambles that are subject to reporting. For example, the maximum number (667) may indicate the maximum number of report random access preambles among the detection random access preambles. The report random access preamble may be referred to as a report target preamble, a report preamble, a second random access preamble, or a second preamble. For example, the maximum number (667) may have a field length of 6 bits. In the above example, when the indexes of the detection random access preambles indicated by the indication information (663, 665) are 1 to 32 (i.e., 32), the maximum number (667) of report random access preambles may be a value less than 32.
[0163] Although not shown in FIG. 6B, the extended type (650) may further include additional parameters. For example, the extended type (650) may include at least one of a maximum TA threshold, a detection energy threshold, or whitening information for interference elimination. For example, the maximum TA threshold may indicate a threshold for a TA value corresponding to a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the maximum TA threshold. For example, the detection energy threshold may indicate a threshold for the energy of a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the detection energy threshold. For example, the whitening information may be used to indicate whether to perform whitening filtering for interference elimination. For example, when the value of the whitening information is 0, the RU (220) may perform the whitening filtering. In contrast, if the value of the whitening information is 1, the RU (220) may not perform (or omit) the whitening filtering.
[0164] Referring to FIG. 6B, the extended type (650) may include a plurality of reserved bits. For example, the plurality of reserved bits may be used for parameters different from the above parameters. For example, the parameters may include the maximum TA threshold, the detection energy threshold, or whitening information for interference removal.
[0165] In one embodiment, the extension type (650) may be used in conjunction with a designated section type. For example, the designated section type may include section type 3 associated with PRACH. However, the embodiments of the present disclosure are not limited thereto. For example, the extension type (650) may also be used in conjunction with section type 0 for indicating uplink resources.
[0166] Additionally, according to one embodiment, the extension type (650) may be used in conjunction with a designated section type and other extension types. For example, the extension type (650) may be used in conjunction with section type 3 and extension type 10. The extension type 10 may be used to indicate a predefined beam (e.g., beam ID) for measuring a random access preamble. Alternatively, for example, the extension type (650) may be used in conjunction with section type 3 and extension type 1. The extension type 1 may be used to indicate an undefined beam (e.g., beamforming weight value) for measuring a random access preamble.
[0167] As described above, the section extensions (or extension types) that can be supported depending on the section type can be defined through the user plane setting module (or YANG module). The module can define the section extensions that can be supported depending on the section type as shown in Table 1. Referring to Table 1 described above, with respect to the extension type (650), the value (uint8) of supported-section-extensions can indicate the value (A) of extType (653). In this case, the value (uint8) of section-type can indicate 3 (i.e., section type 3). However, as described above, the value of extType (653) and the value of section-type according to it are merely exemplary, and the embodiments of the present disclosure are not limited thereto.
[0168] The extended type (650) of FIG. 6b is merely exemplary, and the embodiments of the present disclosure are not limited thereto. For example, the positions and lengths of parameters within the extended type (650) may be changed.
[0169] Referring to FIGS. 6A and 6B , the extended type (600) (or extended type (650)) may include indication information (613, 615) (or indication information (663, 665)) for consecutive detection random access preambles. The RU (220) may identify the consecutive detection random access preambles based on the extended type (600) (or extended type (650)). Hereinafter, FIG. 7 illustrates an example of an extended type that includes information indicating non-consecutive detection random access preambles.
[0170] Figure 7 illustrates an example of an extension type for detection of a random access preamble.
[0171] FIG. 7 illustrates an example of an extension type (700) for detecting the random access preamble. For example, DU (210) may transmit (or provide) a control plane message including information about the extension type (700) to RU (220). Accordingly, RU (220) may perform the detection based on the control plane message (or the extension type). For example, RU (220) may receive a message (e.g., message 1) including a random access preamble from terminal (120). For example, RU (220) may perform the detection for the random access preamble based on the control plane message (or the extension type). For example, the detection may be performed based on the energy of the random access preamble.
[0172] Referring to FIG. 7, the extension type (700) for detecting the random access preamble may include configuration information required to perform detection of the random access preamble. The extension type (700) may be referred to as extension type information or section extension (SE).
[0173] According to one embodiment, the extension type (700) may include common parameters. For example, the common parameters may include ef (extension flag) (701), extType (extension type) (703), and extLen (extension length) (705).
[0174] For example, ef(701) can be used to indicate whether another extension type following the extension type(700) exists. For example, ef(701) can have a field length of 1 bit. For example, if the value of ef(701) is 1, the other extension type may exist. Conversely, if the value of ef(701) is 0, the other extension type may not exist. ef(701) can be referenced as an extension flag.
[0175] For example, extType (703) can be used to indicate an extension type (700). For example, extType (703) can provide an extension type that provides additional parameters specific to a subject data extension. For example, extType (703) can have a field length of 7 bits. For example, extType (703) can have different values for each extension type. For example, extType (703) of the extension type (700) for the detection of the random access preamble can include 0xA. The A can represent any order or number. The A can represent a number of two or more digits (e.g., 32). An extension type (700) whose extType (703) is A can be referred to as an extension type A. The extType (703) can be referred to as an index of extension type information.
[0176] For example, extLen (705) can provide the length of the extension type (700). For example, extLen (705) can provide the length of the extension type (700) in units of 32 bits (or 4 bytes) words. For example, extLen (705) can have a field length of 8 bits. However, the embodiments of the present disclosure are not limited thereto. For example, depending on the information included in the extension type (700), extLen (705) can have a field length of 16 bits or more. extLen (705) can be referred to as the length of the extension type information. For example, the extension type (700) can have a length of 16 bytes indicated by extLen (705).
[0177] According to one embodiment, the extended type (700) may include parameters for the detection of the random access preamble. For example, the parameters for the detection may include a 1R report setting (706), a restricted set setting (707), a root sequence index (709), and the number of cyclic shifts (N cs )(711), a bitmap (713) for indicating detection random access preambles, and a maximum number of reporting random access preambles (715).
[0178] For example, the 1R report setting (706) may be used to indicate whether the detection result of the random access preamble is to be transmitted through one reception path (Rx path) associated with the random access preamble. For example, the 1R report setting (706) may have a field length of 1 bit. For example, when the 1R report setting (706) is 0, the detection result may be transmitted through each of all reception paths established between the RU (220) and the DU (210). For example, when the 1R report setting (706) is 1, the detection result may be transmitted through one reception path. The one reception path may be identified based on the random access preamble (or preamble index). For example, the one reception path may indicate a path with the highest energy among the same preamble indices. For example, the path may include an eAxC identifier (eAxcID). As described below, the detection results may be included in a control plane message (e.g., FIGS. 8a and 8b) or a user plane message (e.g., FIGS. 9a to 9d).
[0179] For example, the restricted set configuration (707) may indicate information related to mobility. For example, the value of the restricted set configuration (707) may be related to the mobility. For example, the value of the restricted set configuration (707) may include unrestrictedset, restrictedSetTypeA, and restrictedSetTypeB. For example, the restricted set configuration (707) may have a field length of 2 bits. For example, the unrestrictedset may indicate a low or medium mobility state. For example, the unrestrictedset may indicate a case where the Doppler frequency offset (or frequency offset) is less than or equal to half of the subcarrier spacing. For example, the restrictedSetTypeA may indicate a high mobility state. For example, the restrictedSetTypeA may indicate a case where the Doppler frequency offset is less than or equal to the subcarrier spacing. For example, the restrictedSetTypeB may indicate a very high mobility state. For example, the restrictedSetTypeB may indicate a case where the Doppler frequency offset is less than or equal to twice the subcarrier spacing.
[0180] For example, the root sequence index (709) may indicate an index of a root sequence for generating a random access preamble. For example, the root sequence index (709) may have a field length of 12 bits. For example, the root sequence index (709) may include a restricted set configuration (707) and 4 consecutive bits (e.g., OctetN N+2) and the following 8 bits (e.g., OctetN N+3).
[0181] For example, the number of circular shifts (Ncs )(711) may be indicated by a zero correlation zone (ZCZ) configuration (ZCZC). For example, the number of cyclic shifts (711) may have a field length of 9 bits. For example, the number of cyclic shifts (711) may include a first part of 7 bits (e.g., OctetN N+4) and a second part of 2 bits (e.g., OctetN N+5). For example, the number of cyclic shifts (711) may be associated with a restricted set configuration (707).
[0182] For example, the bitmap (713) for indicating detection random access preambles can indicate random access preambles to be detected. For example, the bitmap (713) can indicate preambles to be detected among the maximum number of configurable random access preambles (e.g., 64). For example, the detection random access preamble can be referred to as a detection target preamble, a detection preamble, a first random access preamble, or a first preamble. For example, the bitmap (713) can have a field length of 64 bits. For example, the bitmap (713) can include bits within Octet N+6 to Octet N+13. For example, when the value of the bitmap (713) is 1, the random access preamble of the corresponding index can be identified as a detection target. In other words, a random access preamble whose value of the bitmap (713) is 1 can be identified as a detection random access preamble. Conversely, if the value of the bitmap (713) is 0, the random access preamble of that index can be identified as not being detected.
[0183] For example, the maximum number (715) of report random access preambles may indicate the number of random access preambles that are subject to reporting. For example, the maximum number (715) may indicate the maximum number of report random access preambles among the detection random access preambles. The report random access preamble may be referred to as a report target preamble, a report preamble, a second random access preamble, or a second preamble. For example, the maximum number (715) may have a field length of 6 bits. In the example described above, when the total number of detection random access preambles indicated by the bitmap (713) is 32, the maximum number (715) of report random access preambles may be a value less than 32.
[0184] Although not shown in FIG. 7, the extended type (700) may further include additional parameters. For example, the extended type (700) may include at least one of a maximum TA threshold, a detection energy threshold, or whitening information for interference elimination. For example, the maximum TA threshold may indicate a threshold for a TA value corresponding to a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the maximum TA threshold. For example, the detection energy threshold may indicate a threshold for the energy of a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the detection energy threshold. For example, the whitening information may be used to indicate whether to perform whitening filtering for interference elimination. For example, when the value of the whitening information is 0, the RU (220) may perform the whitening filtering. In contrast, if the value of the whitening information is 1, the RU (220) may not perform (or omit) the whitening filtering.
[0185] Referring to FIG. 7, the extended type (700) may include a plurality of reserved bits. For example, the plurality of reserved bits may be used for parameters different from the above parameters. For example, the parameters may include the maximum TA threshold, the detection energy threshold, or whitening information for interference removal.
[0186] In one embodiment, the extension type (700) may be used in conjunction with a designated section type. For example, the designated section type may include section type 3 associated with PRACH. However, the embodiments of the present disclosure are not limited thereto. For example, the extension type (700) may also be used in conjunction with section type 0 for indicating uplink resources.
[0187] Additionally, according to one embodiment, the extension type (700) may be used in conjunction with a designated section type and other extension types. For example, the extension type (700) may be used in conjunction with section type 3 and extension type 10. The extension type 10 may be used to indicate a predefined beam (e.g., beam ID) for measuring a random access preamble. Alternatively, for example, the extension type (650) may be used in conjunction with section type 3 and extension type 1. The extension type 1 may be used to indicate an undefined beam (e.g., beamforming weight value) for measuring a random access preamble.
[0188] As described above, the section extensions (or extension types) that can be supported depending on the section type can be defined through the user plane setting module (or YANG module). The module can define the section extensions that can be supported depending on the section type as shown in Table 1. Referring to Table 1 described above, with respect to the extension type (700), the value (uint8) of supported-section-extensions can indicate the value (A) of extType (703). In this case, the value (uint8) of section-type can indicate 3 (i.e., section type 3). However, as described above, the value of extType (703) and the value of section-type according to it are merely exemplary, and the embodiments of the present disclosure are not limited thereto.
[0189] The extended type (700) of FIG. 7 is merely exemplary, and the embodiments of the present disclosure are not limited thereto. For example, the positions and lengths of parameters within the extended type (700) may be changed.
[0190] Referring to FIG. 7, based on the extended type (700) including the bitmap (713), the RU (220) can identify any random access preambles as detected random access preambles. In other words, when using the extended type (700) compared to the extended type (600) (or extended type (650)), more free operation may be possible.
[0191] Figures 8a and 8b illustrate examples of control plane messages including detection results of random access preambles.
[0192] FIG. 8A illustrates an example of a control plane message (800) including the detection result of the random access preamble. The control plane message (800) including the detection result may be included in an uplink message that the RU (220) transmits to the DU (210). For example, the RU (220) may perform the detection on the random access preamble and generate information including the result of the detection (hereinafter, referred to as a detection result). For example, the RU (220) may provide (or transmit) the control plane message (800) including the detection result to the DU (210).
[0193] Referring to FIG. 8A, a control plane message (800) including the detection result may be used to transmit the result of detection of the random access preamble. For example, the control plane message (800) may be associated with a specific section type. For example, the specific section type may include section type B. B may represent any order or number. For example, B may include 13. In other words, the control plane message (800) may be associated with the section type B.
[0194] According to one embodiment, when a control plane message (800) is newly defined, a new definition for an endpoint of a section type may be required. For example, the endpoint may be defined for each channel. For example, the channel may include PRACH, PUCSH (physical uplink shared channel), PUCCH (physical uplink control channel), PDSCH, and PDCCH. For example, the endpoint may indicate a section type (or supporting section type) that is supportable for each channel. As described above, when the control plane message (800) is associated with the section type B, the endpoint may indicate the section type B.
[0195] As described above, the supportable section types can be defined through the user plane configuration module (or YANG module). The module can define the supportable section types as follows.
[0196]
[0197] Referring to the above table, with respect to the control plane message (800), the value (uint8) of section-type may indicate B (i.e., section type B). However, the control plane message (800) and the corresponding section-type value as described above are merely exemplary, and the embodiments of the present disclosure are not limited thereto. In this case, the section type B may be used for the extension type A (e.g., the extension type (600) of FIG. 6A, the extension type (650) of FIG. 6B, or the extension type (700) of FIG. 7). For example, the section type B may be used in response to the extension type A and a designated section type concatenated thereto (e.g., section type 3).
[0198] Referring to FIG. 8A, according to one embodiment, a control plane message (800) may include time header information (801), section type information (803), the number of detected preambles (805), and detection results (810, 820, 830).
[0199] For example, the time header information (801) may include a frame ID (frameID), a subframe ID (subframeID), and a slot ID (slotID). For example, the time header information (801) may indicate a location where the detected random access preambles are identified. For example, the detected random access preamble may be referred to as a random access preamble in which detection was performed, a received random access preamble, a third random access preamble, a third preamble, or a detected preamble. The location may indicate a timing at which the detected random access preambles are received.
[0200] For example, section type information (803) may be used to indicate the section type B. For example, section type information (803) may have a field length of 12 bits. For example, section type information (803) may have different values for each section type.
[0201] For example, the number of detected preambles (805) may indicate the number of detected random access preambles among the random access preambles received by the RU (220). For example, the detected random access preambles may indicate a preamble identified based on the detection among the random access preambles received from the terminal (120). For example, the number of detected preambles (805) may have a field length of 7 bits. In other words, the range of the number indicated by the number of detected preambles (805) may be formed as 0 to 127. That is, the number of detected preambles (805) may indicate up to 64 preambles (e.g., when the number of detected random access preambles is 64 and the number of reported random access preambles is also 64). For example, the number (805) of detected preambles may be less than or equal to the maximum number (617) (or the maximum number (667), the maximum number (715)) included in the extended type (600) (or the extended type (650), the extended type (700)). In other words, the number of detected random access preambles may be less than the number of reported random access preambles. According to one embodiment, the number (805) of detected preambles may be related to the number of detection results (810, 820, 830). For example, the number of detection results (810, 820, 830) may correspond to the number (805) of detected preambles. For example, if the number of detected preambles (805) is 4, the number of detection results (810, 820, 830) may be 4 (i.e., m=4 in FIG. 8a).
[0202] According to one embodiment, the detection result (810) may include information about a first detected preamble among the detected preambles. For example, the detection result (810) may include a preamble index (811), a TA (813) corresponding to the preamble index, and detected energy (815).
[0203] For example, the preamble index (811) may include an index indicating the first detected preamble among the detected preambles. For example, the preamble index (811) may have a field length of 6 bits. Accordingly, the preamble index (811) may indicate a total of 64 random access preambles. For example, the TA (813) corresponding to the preamble index may include a determined TA value for the preamble index (811) of the first detected preamble. For example, the TA (813) may have a field length of 12 bits. For example, the detected energy (815) may include a value of the detected energy for the first detected preamble. For example, the detected energy (815) may have a field length of 16 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (815) may include an absolute value of the energy. According to one embodiment, the reserved bit (817) included in the detection result (810) may be used to indicate the type of the detected energy (815). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP).
[0204] Additionally, according to one embodiment, the detection result (820) may include information about a second detected preamble among the detected preambles. For example, the detection result (820) may include a preamble index (821), a TA (823) corresponding to the preamble index, and detected energy (825).
[0205] For example, the preamble index (821) may include an index indicating the second detected preamble among the detected preambles. For example, the preamble index (821) may have a field length of 6 bits. Accordingly, the preamble index (821) may indicate a total of 64 random access preambles. For example, the TA (823) corresponding to the preamble index may include a determined TA value for the preamble index (821) of the second detected preamble. For example, the TA (823) may have a field length of 12 bits. For example, the detected energy (825) may include a value of the detected energy for the second detected preamble. For example, the detected energy (825) may have a field length of 16 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (825) may include an absolute value of the energy. According to one embodiment, the reserved bit (827) included in the detection result (820) may be used to indicate the type of the detected energy (825). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP).
[0206] Additionally, according to one embodiment, the detection result (830) may include information about the detected m-th preamble among the detected preambles. For example, the detection result (830) may include a preamble index for the m-th detected preamble, a TA corresponding to the preamble index, and detected energy. In this regard, the contents of the detection result (810) or the detection result (820) may be substantially equally applied.
[0207] FIG. 8B illustrates an example of a control plane message (850) including the detection result of the random access preamble. The control plane message (850) including the detection result may be included in an uplink message transmitted by the RU (220) to the DU (210). For example, the RU (220) may perform the detection on the random access preamble and generate information including the result of the detection (hereinafter, referred to as a detection result). For example, the RU (220) may provide (or transmit) the control plane message (850) including the detection result to the DU (210).
[0208] Referring to FIG. 8B, a control plane message (850) including the detection result may be used to transmit the result of detection of the random access preamble. For example, the control plane message (850) may be associated with a specific section type. For example, the specific section type may include section type B. B may represent any order or number. For example, B may include 13. In other words, the control plane message (850) may be associated with the section type B.
[0209] Referring to FIG. 8B, according to one embodiment, a control plane message (850) may include time header information (851), section type information (853), the number of detected preambles (855), and detection results (860, 870, 880). The content of the control plane message (850) of FIG. 8B may be substantially identical to the content of the control plane message (800) of FIG. 8A. For example, the time header information (851) may correspond to the time header information (801). For example, the section type information (803) may correspond to the section type information (803). For example, the number of detected preambles (855) may correspond to the number of detected preambles (805).
[0210] The detection results (860, 870, 880) included in the control plane message (850) of FIG. 8b may be different from the detection results (810, 820, 830) included in the control plane message (800) of FIG. 8a. For example, the control plane message (800) of FIG. 8a may be transmitted in response to a case where the 1R report setting (e.g., the 1R report setting (606) of FIG. 6a, the 1R report setting (656) of FIG. 6b, or the 1R report setting (706) of FIG. 7) included in the extension type A (e.g., the extension type (600) of FIG. 6a, the extension type (650) of FIG. 6b, or the extension type (700) of FIG. 7)) is 0. In contrast, the control plane message (850) of FIG. 8b may be transmitted in response to a 1R report setting (e.g., 1R report setting (606) of FIG. 6a, 1R report setting (656) of FIG. 6b, or 1R report setting (706) of FIG. 7) included in the extension type A (e.g., extension type (600) of FIG. 6a, extension type (650) of FIG. 6b, or extension type (700) of FIG. 7)) being 1.
[0211] According to one embodiment, the detection result (860) may include information about a first detected preamble among the detected preambles. For example, the detection result (860) may include a preamble index (861), a TA (863) corresponding to the preamble index, a detected energy (865), and an eAxCID (869).
[0212] For example, the preamble index (861) may include an index indicating the first detected preamble among the detected preambles. For example, the preamble index (861) may have a field length of 6 bits. Accordingly, the preamble index (861) may indicate a total of 64 random access preambles. For example, the TA (863) corresponding to the preamble index may include a determined TA value for the preamble index (861) of the first detected preamble. For example, the TA (863) may have a field length of 12 bits. For example, the detected energy (865) may include a value of the detected energy for the first detected preamble. For example, the detected energy (865) may have a field length of 16 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (865) may include an absolute value of the energy. According to one embodiment, the reserved bit (867) included in the detection result (860) may be used to indicate the type of the detected energy (865). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). For example, the eAxCID (869) may have a field length of 16 bits.For example, the control plane message (850) may include the eAxCID (869) of the reception path having the highest energy among the reception paths, if the 1R report setting is 1 and the detected preamble for each of the reception paths established between the RU (220) and the DU (210) has the same index (e.g., the first detected preamble).
[0213] Additionally, according to one embodiment, the detection result (870) may include information about a second detected preamble among the detected preambles. For example, the detection result (870) may include a preamble index (871), a TA (873) corresponding to the preamble index, a detected energy (875), and an eAxCID (879).
[0214] For example, the preamble index (871) may include an index indicating the second detected preamble among the detected preambles. For example, the preamble index (871) may have a field length of 6 bits. Accordingly, the preamble index (871) may indicate a total of 64 random access preambles. For example, the TA (873) corresponding to the preamble index may include a determined TA value for the preamble index (871) of the second detected preamble. For example, the TA (873) may have a field length of 12 bits. For example, the detected energy (875) may include a value of the energy detected for the second detected preamble. For example, the detected energy (875) may have a field length of 16 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (875) may include an absolute value of the energy. According to one embodiment, the reserved bit (877) included in the detection result (870) may be used to indicate the type of the detected energy (875). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). For example, the eAxCID (879) may have a field length of 16 bits.For example, the control plane message (850) may include the eAxCID (879) of the reception path having the highest energy among the reception paths, if the 1R report setting is 1 and the detected preamble for each of the reception paths established between the RU (220) and the DU (210) has the same index (e.g., the second detected preamble).
[0215] Additionally, according to one embodiment, the detection result (880) may include information about the detected m-th preamble among the detected preambles. For example, the detection result (880) may include a preamble index for the m-th detected preamble, a TA corresponding to the preamble index, detected energy, and eAxCID. In this regard, the contents of the detection result (860) or the detection result (870) may be substantially equally applied.
[0216] In the examples of FIGS. 8A and 8B, an example is described in which the RU (220) reports the detection result to the DU (210) via a control plane message (800) or a control plane message (850), but the embodiments of the present disclosure are not limited thereto. In the following FIGS. 9A to 9D, a method in which the RU (220) reports the detection result to the DU (210) via a user plane rather than a control plane is described.
[0217] Figures 9a to 9d illustrate examples of user plane messages including detection results of a random access preamble.
[0218] FIGS. 9A and 9B illustrate examples of a user plane message (900) including the detection result of the random access preamble. For convenience of explanation, the user plane message (900) is illustrated separately in FIGS. 9A and 9B. However, the user plane message (900) of FIGS. 9A and 9B may represent examples of a single user plane message. The user plane message (900) including the detection result may be included in an uplink message transmitted by the RU (220) to the DU (210). For example, the RU (220) may perform the detection for the random access preamble and generate the detection result. For example, the RU (220) may provide (or transmit) the user plane message (900) including the detection result to the DU (210).
[0219] Referring to FIGS. 9A and 9B , a user plane message (900) may be used to provide IQ data generated by an RU (220) to a DU (210). At this time, the user plane message (900) may include the detection result instead of information for transmitting the IQ data. For example, since the detection result for the random access preamble is not IQ data, information related to PRB (e.g., start PRB (startPrbu) number of PRBs (numPrbu)) may be unnecessary information for the detection result. Since the detection result is not the IQ data, compression for octets may not be required. Therefore, the user plane message (900) including the detection result may be transmitted instead of information related to the PRB.
[0220] Referring to FIGS. 9A and 9B , according to one embodiment, a user plane message (900) may include time header information (901), a number of PRBs (903), and detection results (910, 920, 930).
[0221] For example, the time header information (901) may include a frame ID (frameID), a subframe ID (subframeID), and a slot ID (slotID). For example, the time header information (901) may indicate a location where the detected random access preambles are identified. For example, the detected random access preamble may be referred to as a random access preamble in which detection was performed, a received random access preamble, a third random access preamble, a third preamble, or a detected preamble. The location may indicate a timing at which the detected random access preambles are received.
[0222] For example, the PRB count (903) may include information on PRBs allocated for the IQ data. According to one embodiment, the user plane message (900) including the detection result may use the PRB count (903) for indicating the number of detected preambles, rather than the PRB count (903) for information on RPBs. For example, when the extension type A is used within the designated section type (e.g., section type 3), the PRB count (903) may indicate the number of detected preambles instead of the information on the PRB. For example, the use of the extension type A within the designated section type may be identified based on the section ID (902) of the user plane message (900). For example, if the section type and extension type of a control plane message having a section ID corresponding to the section ID (902) of a user plane message (900) are the specified section type and the extension type A, the RU (220) can identify that the extension type A is used within the specified section type. For example, the number of PRBs (903) can have a field length of 8 bits. In this case, the number of detected preambles can be indicated through at least a part (e.g., 7 bits) of the field length of 8 bits.
[0223] In one embodiment, the number of detected preambles may be related to the number of detection results (910, 920, 930). For example, the number of detection results (910, 920, 930) may correspond to the number of detected preambles. For example, if the number of detected preambles is 4, the number of detection results (910, 920, 930) may be 4 (i.e., m=4 in FIGS. 9A and 9B ).
[0224] According to one embodiment, the detection result (910) may include information about a first detected preamble among the detected preambles. For example, the detection result (910) may include a preamble index (911), a TA (913) corresponding to the preamble index, and detected energy (915).
[0225] For example, the preamble index (911) may include an index indicating the first detected preamble among the detected preambles. For example, the preamble index (911) may have a field length of 6 bits. Accordingly, the preamble index (911) may indicate a total of 64 random access preambles. For example, the TA (913) corresponding to the preamble index may include a determined TA value for the preamble index (911) of the first detected preamble. For example, the TA (913) may have a field length of 12 bits. For example, the detected energy (915) may include a value of the detected energy for the first detected preamble. For example, the detected energy (915) may have a field length of 22 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (915) may include an absolute value of the energy. According to one embodiment, the reserved bit (917) included in the detection result (910) may be used to indicate the type of the detected energy (915). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP).
[0226] Additionally, according to one embodiment, the detection result (920) may include information about a second detected preamble among the detected preambles. For example, the detection result (920) may include a preamble index (921), a TA (923) corresponding to the preamble index, and detected energy (925).
[0227] For example, the preamble index (921) may include an index indicating the second detected preamble among the detected preambles. For example, the preamble index (921) may have a field length of 6 bits. Accordingly, the preamble index (921) may indicate a total of 64 random access preambles. For example, the TA (923) corresponding to the preamble index may include a determined TA value for the preamble index (921) of the second detected preamble. For example, the TA (923) may have a field length of 12 bits. For example, the detected energy (925) may include a value of the energy detected for the second detected preamble. For example, the detected energy (925) may have a field length of 22 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (925) may include an absolute value of the energy. According to one embodiment, the reserved bit (927) included in the detection result (920) may be used to indicate the type of the detected energy (925). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP).
[0228] Additionally, according to one embodiment, the detection result (930) may include information about the detected m-th preamble among the detected preambles. For example, the detection result (930) may include a preamble index for the m-th detected preamble, a TA corresponding to the preamble index, and detected energy. In this regard, the contents of the detection result (910) or the detection result (920) may be substantially equally applied.
[0229] According to one embodiment, the user plane message (900) may include a PRB number (905) corresponding to the section ID (904). For example, the PRB number (905) may include information on PRBs allocated for the IQ data. According to one embodiment, the user plane message (900) including the detection result may use the PRB number (905) for indicating the number of detected preambles, rather than the PRB number (905) for information on RPBs. For example, whether the extension type A is used within the designated section type may be identified based on the section ID (904) of the user plane message (900). For example, when the section type and the extension type of a control plane message having a section ID corresponding to the section ID (904) of the user plane message (900) are the designated section type and the extension type A, the RU (220) may identify that the extension type A is used within the designated section type.
[0230] Referring to the above, the user plane message (900) may include detection results for each section ID. For example, the user plane message (900) may include detection results (910, 920, 930) for the section ID (902) and detection results (940) for the section ID (904). The content of the detection results (940) may be substantially identical to the content of the detection results (910, 920, 930).
[0231] FIGS. 9C and 9D illustrate examples of a user plane message (950) including the detection result of the random access preamble. For convenience of explanation, the user plane message (950) is illustrated separately in FIGS. 9C and 9D. However, the user plane message (950) of FIGS. 9C and 9D may represent examples of one user plane message. The user plane message (950) including the detection result may be included in an uplink message transmitted by the RU (220) to the DU (210). For example, the RU (220) may perform the detection for the random access preamble and generate the detection result. For example, the RU (220) may provide (or transmit) the user plane message (950) including the detection result to the DU (210).
[0232] Referring to FIGS. 9C and 9D , a user plane message (950) may be used to provide IQ data generated by an RU (220) to a DU (210). At this time, the user plane message (950) may include the detection result instead of information for transmitting the IQ data. For example, since the detection result for the random access preamble is not IQ data, information related to PRB (e.g., start PRB (startPrbu) number of PRBs (numPrbu)) may be unnecessary information for the detection result. Since the detection result is not the IQ data, compression for octets may not be required. Therefore, a user plane message (950) including the detection result may be transmitted instead of information related to the PRB.
[0233] Referring to FIGS. 9C and 9D , according to one embodiment, a user plane message (950) may include time header information (951), a PRB count (953), and detection results (960, 970, 980). The content of the user plane message (950) of FIGS. 9C and 9D may be substantially identical to the content of the user plane message (900) of FIGS. 9A and 9B . For example, the time header information (951) may correspond to the time header information (901). For example, the PRB count (953) may correspond to the PRB count (903).
[0234] The detection results (960, 970, 980) included in the user plane message (950) of FIGS. 9C and 9D may be different from the detection results (910, 920, 930) included in the user plane message (900) of FIGS. 9A and 9B. For example, the user plane message (900) of FIGS. 9A and 9B may be transmitted in response to a case where the 1R report setting (e.g., the 1R report setting (606) of FIG. 6A, the 1R report setting (656) of FIG. 6B, or the 1R report setting (706) of FIG. 7) included in the extension type A (e.g., the extension type (600) of FIG. 6A, the extension type (650) of FIG. 6B, or the extension type (700) of FIG. 7)) is 0. In contrast, the user plane message (950) of FIGS. 9c and 9d may be transmitted in response to a 1R report setting (e.g., 1R report setting (606) of FIG. 6a, 1R report setting (656) of FIG. 6b, or 1R report setting (706) of FIG. 7) included in the extension type A (e.g., extension type (600) of FIG. 6a, extension type (650) of FIG. 6b, or extension type (700) of FIG. 7)) being 1.
[0235] According to one embodiment, the detection result (960) may include information about a first detected preamble among the detected preambles. For example, the detection result (960) may include a preamble index (961), a TA (963) corresponding to the preamble index, detected energy (965), and an eAxCID (967).
[0236] For example, the preamble index (961) may include an index indicating the first detected preamble among the detected preambles. For example, the preamble index (961) may have a field length of 6 bits. Accordingly, the preamble index (961) may indicate a total of 64 random access preambles. For example, the TA (963) corresponding to the preamble index may include a determined TA value for the preamble index (961) of the first detected preamble. For example, the TA (963) may have a field length of 12 bits. For example, the detected energy (965) may include a value of the detected energy for the first detected preamble. For example, the detected energy (965) may have a field length of 22 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (965) may include an absolute value of the energy. According to one embodiment, the reserved bit (967) included in the detection result (960) may be used to indicate the type of the detected energy (965). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). For example, the eAxCID (967) may have a field length of 16 bits.For example, the user plane message (950) may include the eAxCID (967) of the reception path having the highest energy among the reception paths, if the 1R report setting is 1 and the detected preamble for each of the reception paths established between the RU (220) and the DU (210) has the same index (e.g., the first detected preamble).
[0237] Additionally, according to one embodiment, the detection result (970) may include information about a second detected preamble among the detected preambles. For example, the detection result (970) may include a preamble index (971), a TA (973) corresponding to the preamble index, a detected energy (975), and an eAxCID (977).
[0238] For example, the preamble index (971) may include an index indicating the second detected preamble among the detected preambles. For example, the preamble index (971) may have a field length of 6 bits. Accordingly, the preamble index (971) may indicate a total of 64 random access preambles. For example, the TA (973) corresponding to the preamble index may include a determined TA value for the preamble index (971) of the second detected preamble. For example, the TA (973) may have a field length of 12 bits. For example, the detected energy (975) may include a value of the energy detected for the second detected preamble. For example, the detected energy (975) may have a field length of 22 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the detected energy (975) may include an absolute value of the energy. According to one embodiment, the reserved bit (977) included in the detection result (970) may be used to indicate the type of the detected energy (975). For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). For example, the eAxCID (977) may have a field length of 16 bits.For example, the user plane message (950) may include the eAxCID (977) of the reception path having the highest energy among the reception paths, if the 1R report setting is 1 and the detected preamble for each of the reception paths established between the RU (220) and the DU (210) has the same index (e.g., the second detected preamble).
[0239] Additionally, according to one embodiment, the detection result (980) may include information about the detected m-th preamble among the detected preambles. For example, the detection result (980) may include a preamble index for the m-th detected preamble, a TA corresponding to the preamble index, and detected energy. In this regard, the contents of the detection result (960) or the detection result (970) may be applied substantially identically.
[0240] According to one embodiment, the user plane message (950) may include the number of PRBs (955) corresponding to the section ID (954). For example, the number of PRBs (955) may include information on PRBs allocated for the IQ data. According to one embodiment, the user plane message (950) including the detection result may use the number of PRBs (955) to indicate the number of detected preambles, rather than the number of PRBs (955) for information on RPBs. For example, whether the extension type A is used within the designated section type may be identified based on the section ID (954) of the user plane message (950). For example, when the section type and the extension type of a control plane message having a section ID corresponding to the section ID (954) of the user plane message (950) are the designated section type and the extension type A, the RU (220) may identify that the extension type A is used within the designated section type.
[0241] Referring to the above, the user plane message (950) may include detection results for each section ID. For example, the user plane message (950) may include detection results (960, 970, 980) for the section ID (952) and detection results (990) for the section ID (954). The content of the detection results (990) may be substantially identical to the content of the detection results (960, 970, 980).
[0242] Referring to FIGS. 9A to 9D , examples of a user plane message (900) that does not include an eAxCID and a user plane message (950) that includes an eAxCID are illustrated based on the value of the 1R report setting, but the present disclosure is not limited thereto. For example, an eAxCID may not be included in a detection result associated with a specific section ID of a user plane message, and an eAxCID may be included in a detection result associated with a section ID different from the specific section ID of the user plane message. In other words, the user plane messages (900) of FIGS. 9A and 9B and the user plane messages (950) of FIGS. 9C and 9D may be combined.
[0243] Figure 10a illustrates an example of a transmission window for an uplink message.
[0244] FIG. 10A illustrates an example (1000) of a transmission window for an uplink message (1040) including the detection result. For example, the uplink message (1040) may include the control plane message (800) of FIG. 8A, the control plane message (850) of FIG. 8B, the user plane message (900) of FIGS. 9A and 9B, or the user plane message (950) of FIGS. 9C and 9D.
[0245] According to one embodiment, the RU (220) may obtain (or receive) a control plane message from the DU (210). For example, the RU (220) may obtain the control plane message from the DU (210) within a time interval (1010). For example, the control plane message obtained within the time interval (1010) may include the extended type A and a designated section type of FIGS. 6A to 7 .
[0246] In one embodiment, the RU (220) may transmit (or provide) the uplink message (1040) to the DU (210) within the transmission window (1035). For example, the RU (220) may transmit the uplink message (1040) including the detection result to the DU (210) within the transmission window (1035). For example, the transmission window (1035) may indicate a time interval between a minimum required time (1025) and a maximum required time (1030). The transmission window (1035) may be referred to as a transmission time interval, a transmission time duration, a transmission interval, or a transmission period. The uplink message (1040) may include information (or a detection result) about a random access preamble detected based on the control plane message. For example, a transmission window (1035) may be identified based on a reference time (1020), a minimum requirement time (1025), and a maximum requirement time (1030). The minimum requirement time (1025) may be referred to as a minimum time or a minimum timing. The maximum requirement time (1030) may be referred to as a maximum time or a maximum timing.
[0247] According to one embodiment, the reference time (1020) may be identified based on the control plane message obtained within the time interval (1010). For example, the reference time (1020) may be indicated by a start symbol identifier (ID) for obtaining a user plane message related to a PRACH. For example, the start symbol identifier may be included in the control plane message obtained within the time interval (1010). In this case, the control plane message may include the designated section type and the extension type A. Alternatively, for example, the reference time (1020) may be indicated as the earliest time at which an uplink message is received based on the antenna port of the DU (210). For example, the reference time may be referred to as a reference timing or a reference point.
[0248] In one embodiment, the minimum required time (1025) and the maximum required time (1030) may be identified based on the control plane message including the extension type A indicating the reference time (1020). For example, the minimum required time (1025) may be set as the minimum required time for transmitting the detection result. Alternatively, for example, the maximum required time (1030) may be set as the maximum required time for transmitting the detection result.
[0249] According to one embodiment, the minimum required time (1025) and the maximum required time (1030) may be defined through the user plane configuration module (or YANG module). For example, within the user plane configuration module (or YANG module), the minimum required time (1025) may be defined as ta3_min_seA, and the maximum required time (1030) may be defined as ta3_max_seA. Unlike the minimum required time (1025) and the maximum required time (1030) for transmitting the detection result, the minimum required time and the maximum required time for other uplink transmissions may be defined as ta3_min and ta3-max, respectively. According to one embodiment, the transmission window (1035) for the uplink message (1040) may be formed longer than the transmission window (or delay) between the minimum required time and the maximum required time for the other uplink transmissions. This may be because the RU (220) detects a random access preamble based on the control plane message acquired within the time interval (1010), generates an uplink message (1040), and then transmits the uplink message (1040).
[0250] Figure 10b illustrates an example of a signal flow for transmitting an uplink message.
[0251] FIG. 10b illustrates an example (1050) of signal flow between DU (210) and RU (220) for the example (1000) of FIG. 10a.
[0252] Referring to example (1050), in operation (1060), DU (210) may transmit (or provide) a control plane message to RU (220). For example, RU (220) may receive (or obtain) the control plane message from DU (210). For example, the control plane message obtained within the time interval (1010) may include the extended type A and the designated section type of FIGS. 6A to 7.
[0253] Referring to example (1050), in operation (1070), RU (220) may transmit an uplink message to DU (210). For example, the uplink message may include a control plane message (800) of FIG. 8A, a control plane message (850) of FIG. 8B, a user plane message (900) of FIGS. 9A and 9B, or a user plane message (950) of FIGS. 9C and 9D. In this case, when the uplink message is a control plane message (800) (or a control plane message (850)), a section type associated with the uplink message may be section type B. Additionally, if the uplink message is a user plane message (900) (or user plane message (950)), the section ID of the user plane message (900) (or user plane message (950)) may correspond to the section ID of the control plane message provided to the RU (220) in operation (1060).
[0254] Referring to example (1050), RU (220) can transmit the uplink message within the transmission window (1035). For example, the transmission window (1035) can be identified based on a reference time (1020), a minimum required time (1025), and a maximum required time (1030). For example, the reference time (1020) can represent a symbol indicated by the control plane message.
[0255] Referring to example (1050), DU (210) can receive the uplink message within the reception window (1080). At this time, the reception window (1080) can be identified based on the transmission window (1035). For example, the reception window (1080) can be identified based on the transmission window (1035) and a fronthaul delay. For example, the fronthaul delay can represent a time delay while transmitting a message within the fronthaul between DU (210) and RU (220).
[0256] Although not illustrated in FIG. 10b, according to one embodiment, the RU (220) may receive Message 1 from the terminal (120) during a time interval between operations (1060) and (1070). For example, the RU (220) may perform detection on a random access preamble based on the received Message 1 and the control plane message (or the extended type A). The RU (220) may provide (or transmit) the uplink message including the result of the detection to the DU (210) within operation (1070). However, the embodiments of the present disclosure are not limited thereto. For example, the RU (220) may receive Message 1 from the terminal (120) prior to operation (1060) and perform the detection based on the control plane message received within operation (1060) for the received Message 1.
[0257] FIG. 11 illustrates an example of an operational flow for a method of reporting detection results based on extended type information for detection of a random access preamble.
[0258] At least some of the methods of FIG. 11 may be performed by the RU (220) of FIG. 3b. For example, at least some of the methods may be controlled by the processor (380) of the RU (220). In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel.
[0259] In operation (1110), RU (220) may obtain a control plane message including extended type information for detection of a random access preamble. For example, RU (220) may receive the control plane message including the extended type information for the detection from DU (210).
[0260] According to one embodiment, the extended type information may include common parameters. For example, the common parameters may include ef (extension flag), extType (extension type), and extLen (extension length). For specific details related thereto, the contents of FIGS. 6A to 7 may be applied substantially identically.
[0261] According to one embodiment, the extended type may include parameters for detecting the random access preamble. For example, the parameters for detection may include a 1R report setting, a restricted set setting, a root sequence index, a number of cyclic shifts, indication information for detected random access preambles, and a maximum number of reported random access preambles. As for specific details related thereto, the contents of FIGS. 6A to 7 may be applied substantially identically.
[0262] According to one embodiment, the instruction information may include a start number of the detection random access preambles and an end number of the detection random access preambles. For example, the start number may include an index (or start index) of the detection random access preambles. For example, the end number may include an index (or start index) of the detection random access preambles.
[0263] According to one embodiment, the instruction information may include a start number of the detection random access preambles and a length of the detection random access preambles. For example, the length may include the number of consecutive detection random access preambles from the start number.
[0264] According to one embodiment, the instruction information may include a bitmap. For example, the bitmap for indicating the detected random access preambles may indicate the preambles to be detected among the maximum number of configurable random access preambles (e.g., 64). For example, the bitmap may have a field length of 64 bits.
[0265] In one embodiment, the maximum number may indicate the number of random access preambles that are subject to reporting. For example, the maximum number may indicate the maximum number of reported random access preambles among the detected random access preambles.
[0266] According to one embodiment, the extension type may further include additional parameters. For example, the extension type may include at least one of a maximum TA threshold, a detection energy threshold, or whitening information for interference elimination. For example, the maximum TA threshold may indicate a threshold for a TA value corresponding to a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the maximum TA threshold. For example, the detection energy threshold may indicate a threshold for the energy of a random access preamble. For example, the RU (220) may detect and report a random access having a TA less than or equal to the detection energy threshold. For example, the whitening information may be used to indicate whether to perform whitening filtering for interference elimination. For example, when the value of the whitening information is 0, the RU (220) may perform the whitening filtering. In contrast, if the value of the whitening information is 1, the RU (220) may not perform (or omit) the whitening filtering.
[0267] In one embodiment, the extension type may be used in conjunction with a designated section type. For example, the designated section type may include section type 3 associated with PRACH. However, the embodiments of the present disclosure are not limited thereto. For example, the extension type (700) may also be used in conjunction with section type 0 for indicating uplink resources.
[0268] Additionally, according to one embodiment, the extension type may be used in conjunction with a designated section type and another extension type. For example, the extension type may be used in conjunction with section type 3 and extension type 10. The extension type 10 may be used to indicate a predefined beam (e.g., beam ID) for measuring a random access preamble. Alternatively, for example, the extension type (650) may be used in conjunction with section type 3 and extension type 1. The extension type 1 may be used to indicate an undefined beam (e.g., beamforming weight value) for measuring a random access preamble.
[0269] As described above, the section extensions (or extension types) that can be supported depending on the section type can be defined through the user plane configuration module (or YANG module). The module can define the section extensions that can be supported depending on the section type as shown in Table 1. Referring to Table 1 described above, with respect to the extension type, the value (uint8) of supported-section-extensions can indicate the value (A) of extType. In this case, the value (uint8) of section-type can indicate 3 (i.e., section type 3). However, as described above, the value of extType and the value of section-type according to it are merely exemplary, and the embodiments of the present disclosure are not limited thereto.
[0270] Although not illustrated in FIG. 11, according to one embodiment, RU (220) may receive Message 1 from Terminal (120) after receiving the control plane message. For example, RU (220) may perform detection for a random access preamble based on the received Message 1 and the control plane message (or the extended type A). In other words, RU (220) may identify the detected random access preambles. However, the embodiments of the present disclosure are not limited thereto.
[0271] In operation (1120), RU (220) may transmit an uplink message including information about the detected random access preambles. For example, RU (220) may provide the uplink message including information about the detected random access preambles to DU (210). For example, the uplink message may include a control plane message or a user plane message.
[0272] According to one embodiment, when the uplink message includes the control plane message (e.g., the control plane message (800) of FIG. 8A or the control plane message (850) of FIG. 8B), the uplink message may include time header information, section type information, the number of detected preambles, and detection results. Specific details related thereto may be substantially identically applied to the contents of FIG. 8A and FIG. 8B.
[0273] In one embodiment, the section type information may be used to indicate the section type B. The section type B may be used for an extension type A (e.g., extension type (600) of FIG. 6A, extension type (650) of FIG. 6B, or extension type (700) of FIG. 7). For example, the section type B may be used in response to the extension type A and a designated section type contiguous therewith (e.g., section type 3).
[0274] According to one embodiment, the number of detected preambles may represent the number of detected random access preambles among the random access preambles received by the RU (220). For example, the detected random access preambles may represent a preamble identified based on the detection among the random access preambles received from the terminal (120). For example, the number of detected preambles may be less than or equal to the maximum number included in the extended type A. In other words, the number of detected random access preambles may be less than the number of reported random access preambles.
[0275] In one embodiment, the number of detected preambles may be related to the number of detection results. For example, the number of detection results may correspond to the number of detected preambles.
[0276] According to one embodiment, a first detection result among the detection results may include information about a first detected preamble among the detected preambles. For example, the first detection result may include a first preamble index, a first TA corresponding to the first preamble index, and a first detected energy.
[0277] For example, the first preamble index may include an index indicating the first detected preamble among the detected preambles. For example, the first preamble index may have a field length of 6 bits. Accordingly, the first preamble index may indicate a total of 64 random access preambles. For example, the first TA corresponding to the preamble index may include a determined TA value for the first preamble index of the first detected preamble. For example, the first TA may have a field length of 12 bits. For example, the first detected energy may include a value of energy detected for the first detected preamble. For example, the first detected energy may have a field length of 16 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the first detected energy may include an absolute value of the energy.
[0278] In one embodiment, the reserved bits included in the first detection result may be used to indicate the type of the first detected energy. For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP).
[0279] Additionally, according to one embodiment, a second detection result among the detection results may include information about a second detected preamble among the detected preambles. For example, the second detection result may include a second preamble index, a second TA corresponding to the second preamble index, and the second detected energy.
[0280] According to one embodiment, when the uplink message includes the user plane message (e.g., the user plane message (900) of FIGS. 9A and 9B or the user plane message (950) of FIGS. 9C and 9D), the uplink message may include time header information, section type information, the number of detected preambles, and detection results. Specific details related thereto may be substantially identically applied to the contents of FIGS. 9A and 9B or FIGS. 9C and 9D.
[0281] According to one embodiment, the user plane message may include time header information, a number of PRBs, and detection results.
[0282] According to one embodiment, the number of PRBs may include information on PRBs allocated for the IQ data. According to one embodiment, the user plane message may use the number of PRBs for indicating the number of detected preambles, rather than the number of PRBs for information on the RPBs. For example, when the extension type A is used within the designated section type (e.g., section type 3), the number of PRBs may indicate the number of detected preambles instead of information on the PRBs. For example, the use of the extension type A within the designated section type may be identified based on the section ID of the user plane message. For example, when the section type and the extension type of a control plane message having a section ID corresponding to the section ID of the user plane message are the designated section type and the extension type A, the RU (220) may identify that the extension type A is used within the designated section type.
[0283] In one embodiment, the number of detected preambles may be related to the number of detection results. For example, the number of detection results may correspond to the number of detected preambles.
[0284] According to one embodiment, a first detection result among the detection results of the user plane message may include information about a first detected preamble among the detected preambles. For example, the first detection result may include a first preamble index, a first TA corresponding to the first preamble index, and a first detected energy.
[0285] For example, the first preamble index may include an index indicating the first detected preamble among the detected preambles. For example, the first preamble index may have a field length of 6 bits. Accordingly, the first preamble index may indicate a total of 64 random access preambles. For example, the first TA may include a determined TA value for the first preamble index of the first detected preamble. For example, the first TA may have a field length of 12 bits. For example, the first detected energy may include a value of energy detected for the first detected preamble. For example, the first detected energy may have a field length of 22 bits. For example, the energy may include at least one of power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP). The value of the first detected energy may include an absolute value of the energy.
[0286] In one embodiment, the reserved bits included in the first detection result may be used to indicate the type of the first detected energy. For example, the type may include power, signal to noise ratio (SNR), received signal strength indicator (RSSI), or reference signal received power (RSRP).
[0287] Additionally, according to one embodiment, the second detection result among the detection results of the user plane message may include information about a second detected preamble among the detected preambles. For example, the detection result may include a second preamble index, a second TA corresponding to the second preamble index, and a second detected energy.
[0288] According to one embodiment, the user plane message may include a number of PRBs corresponding to another section ID other than the section ID. For example, the other number of PRBs may include information on PRBs allocated for the IQ data. Referring to the above, the user plane message may include detection results for each section ID. For example, the user plane message may include detection results for the section ID and detection results for the other section ID.
[0289] According to one embodiment, the RU (220) may transmit (or provide) the uplink message to the DU (210) within a transmission window. For example, the RU (220) may transmit the uplink message including the detection result to the DU (210) within the transmission window. For example, the transmission window may indicate a time interval between a minimum required time and a maximum required time.
[0290] According to one embodiment, the transmission window may be identified based on a reference time, the minimum required time, and the maximum required time. The reference time may be identified based on the control plane message. In this case, the control plane message may include the designated section type and the extension type A. For example, the reference time may be indicated by a start symbol identifier (ID) for obtaining a user plane message related to a PRACH.
[0291] According to one embodiment, the minimum required time and the maximum required time may be defined through the user plane configuration module (or YANG module). For example, within the user plane configuration module (or YANG module), the minimum required time may be defined as ta3_min_seA, and the maximum required time may be defined as ta3_max_seA. Unlike the minimum required time and the maximum required time for transmitting the detection result, the minimum required time and the maximum required time for other uplink transmission may be defined as ta3_min and ta3-max, respectively. According to one embodiment, the transmission window for the uplink message may be formed longer than the transmission window (or delay) between the minimum required time and the maximum required time for the other uplink transmission. This may be because the RU (220) detects a random access preamble based on the control plane message, generates the uplink message, and then transmits the uplink message.
[0292] Referring to FIGS. 1 to 11, the device and method according to embodiments of the present disclosure can reduce resource usage (or capacity) of the fronthaul interface by providing information about a detected random access preamble to the DU (210) by the RU (220). In addition, the device and method according to embodiments of the present disclosure can reduce the processing time of the DU (210) and perform the random access procedure more quickly.
[0293] In embodiments, a radio unit (RU) may include a transceiver. The RU may include a processor. The RU may include a memory. Instructions stored in the memory, when executed by the processor, may cause the RU to obtain, from a distributed unit (DU), a control plane message including extension type information for detection of a random access preamble. Instructions stored in the memory, when executed by the processor, may cause the RU to transmit, to the DU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The above extended type information may include indication information for detection random access preambles and information on the maximum number of reporting random access preambles.
[0294] In one embodiment, the instructions stored in the memory, when executed by the processor, may further cause the RU to receive, via the transceiver, signals transmitted from a first user equipment (UE). The instructions stored in the memory, when executed by the processor, may further cause the RU to detect a first random access preamble associated with the first UE based on the signals received from the first UE and the extended type information. The instructions stored in the memory, when executed by the processor, may further cause the RU to receive, via the transceiver, signals transmitted from a second UE. The instructions stored in the memory, when executed by the processor, may further cause the RU to detect a second random access preamble associated with the second UE based on the signals received from the second UE and the extended type information. The information about the random access preambles included in the uplink message transmitted to the DU may be generated based on the first random access preamble and the second random access preamble.
[0295] According to one embodiment, the extended type information may include an extension flag, an index of the extended type information, a length of the extended type information, a number of cyclic shifts indicated by a zero correlation zone (ZCZ) configuration, a root sequence index, and a restricted set configuration.
[0296] According to one embodiment, the extended type information may further include at least one of a maximum timing advance (TA) threshold, a detection energy threshold, or whitening information for interference removal.
[0297] According to one embodiment, the indication information may include a start number of the detection random access preambles and an end number of the detection random access preambles. The information regarding the maximum number may indicate a maximum number of the reporting random access preambles according to an ascending order of detected energy for each of the detection random access preambles. The number of the random access preambles may be less than or equal to the maximum number.
[0298] According to one embodiment, the indication information may include a bitmap for indicating the detected random access preambles. The maximum number information may indicate the maximum number of the reported random access preambles in ascending order of detected energy for each of the detected random access preambles. The number of the random access preambles may be less than or equal to the maximum number.
[0299] According to one embodiment, the control plane message may be associated with section type 3.
[0300] According to one embodiment, the uplink message may include an uplink control plane message. The uplink control plane message may include time resource information on which the random access preambles are transmitted, information indicating the number of the random access preambles, and a detection result for each of the random access preambles. The detection result may include an index of the random access preamble, a timing advance (TA) corresponding to the index, and information on detected energy.
[0301] According to one embodiment, the uplink message may include an uplink user plane message. The uplink user plane message may include time resource information on which the random access preambles are transmitted, information on the number of physical resource blocks (PRBs) for indicating the number of the random access preambles, and a detection result for each of the random access preambles. The detection result may include information on an index of the random access preamble, a timing advance (TA) corresponding to the index, and detected energy.
[0302] In one embodiment, if the control plane message includes a 1R (reception path) report setting, and the value of the 1R report setting indicates that the information about the random access preambles is to be transmitted through one reception path, the uplink message may further include information indicating the reception path.
[0303] According to one embodiment, the instructions stored in the memory, when executed by the processor, may further cause the RU to transmit the uplink message including the information about the random access preambles within a transmission window. The transmission window may be identified based on a minimum required time for transmission of the uplink message set with respect to a reference time and a maximum required time for transmission of the uplink message set with respect to the reference time. The reference time may be indicated based on a start symbol identity included in the control plane message.
[0304] In embodiments, a method performed by a radio unit (RU) may include obtaining, from a distributed unit (DU), a control plane message including extension type information for detection of a random access preamble. The method may include transmitting, to the DU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The extension type information may include indication information about detection random access preambles and information about a maximum number of reporting random access preambles.
[0305] According to one embodiment, the method may further include receiving, through the transceiver, signals transmitted from a first user equipment (UE). The method may further include detecting a first random access preamble associated with the first UE based on the signals received from the first UE and the extension type information. The method may further include receiving, through the transceiver, signals transmitted from a second UE. The method may further include detecting a second random access preamble associated with the second UE based on the signals received from the second UE and the extension type information. The information about the random access preambles included in the uplink message transmitted to the DU may be generated based on the first random access preamble and the second random access preamble.
[0306] According to one embodiment, the extended type information may include an extension flag, an index of the extended type information, a length of the extended type information, a number of cyclic shifts indicated by a zero correlation zone (ZCZ) configuration, a root sequence index, and a restricted set configuration.
[0307] According to one embodiment, the extended type information may further include at least one of a maximum timing advance (TA) threshold, a detection energy threshold, or whitening information for interference removal.
[0308] According to one embodiment, the indication information may include a start number of the detection random access preambles and an end number of the detection random access preambles. The information regarding the maximum number may indicate a maximum number of the reporting random access preambles according to an ascending order of detected energy for each of the detection random access preambles. The number of the random access preambles may be less than or equal to the maximum number.
[0309] According to one embodiment, the indication information may include a bitmap for indicating the detected random access preambles. The maximum number information may indicate the maximum number of the reported random access preambles in ascending order of detected energy for each of the detected random access preambles. The number of the random access preambles may be less than or equal to the maximum number.
[0310] According to one embodiment, the control plane message may be associated with section type 3.
[0311] According to one embodiment, the uplink message may include an uplink control plane message. The uplink control plane message may include time resource information on which the random access preambles are transmitted, information indicating the number of the random access preambles, and a detection result for each of the random access preambles. The detection result may include an index of the random access preamble, a timing advance (TA) corresponding to the index, and information on detected energy.
[0312] According to one embodiment, the uplink message may include an uplink user plane message. The uplink user plane message may include time resource information on which the random access preambles are transmitted, information on the number of physical resource blocks (PRBs) for indicating the number of the random access preambles, and a detection result for each of the random access preambles. The detection result may include information on an index of the random access preamble, a timing advance (TA) corresponding to the index, and detected energy.
[0313] In one embodiment, if the control plane message includes a 1R (reception path) report setting, and the value of the 1R report setting indicates that the information about the random access preambles is to be transmitted through one reception path, the uplink message may further include information indicating the reception path.
[0314] According to one embodiment, the method may further include transmitting the uplink message including the information about the random access preambles within a transmission window. The transmission window may be identified based on a minimum required time for transmission of the uplink message set with respect to a reference time and a maximum required time for transmission of the uplink message set with respect to the reference time. The reference time may be indicated based on a start symbol identity included in the control plane message.
[0315] In embodiments, a non-transitory computer-readable storage medium may store one or more programs, including instructions that, when executed by at least one processor of a device for a radio unit (RU) including a transceiver, cause the device to obtain, from a distributed unit (DU), a control plane message including extension type information for detection of a random access preamble. The non-transitory computer-readable storage medium may store one or more programs, including instructions that, when executed by the at least one processor, cause the device to transmit, to the DU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The extension type information may include indication information about detection random access preambles and information about a maximum number of reporting random access preambles.
[0316] In embodiments, a distributed unit (DU) may include a transceiver. The DU may include a processor. The DU may include a memory. Instructions stored in the memory, when executed by the processor, may cause the DU to transmit a control plane message including extension type information for detection of a random access preamble to a radio unit (RU). Instructions stored in the memory, when executed by the processor, may cause the DU to obtain an uplink message including information about random access preambles from the RU. The random access preambles may be detected based on the extension type information. The above extended type information may include indication information for detection random access preambles and information on the maximum number of reporting random access preambles.
[0317] In embodiments, a method performed by a distributed unit (DU) may include transmitting, to a radio unit (RU), a control plane message including extension type information for detection of a random access preamble. The method may include obtaining, from the RU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The extension type information may include indication information about detection random access preambles and information about a maximum number of reporting random access preambles.
[0318] In embodiments, a non-transitory computer-readable storage medium may store one or more programs, including instructions that, when executed by a processor of a distributed unit (DU) including a transceiver, cause the processor to transmit, to a radio unit (RU), a control plane message including extension type information for detection of a random access preamble. The non-transitory computer-readable storage medium may store one or more programs, including instructions that, when executed by the processor, cause the processor to obtain, from the RU, an uplink message including information about random access preambles. The random access preambles may be detected based on the extension type information. The extension type information may include indication information about detection random access preambles and information about a maximum number of reporting random access preambles.
[0319] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0320] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure. The one or more programs may be provided as a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.
[0321] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.
[0322] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.
[0323] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0324] According to embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.
[0325] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible within the scope of the present disclosure.
Claims
1. In the device of RU (radio unit), transceiver; At least one processor comprising a processing circuit; and A memory storing instructions and including one or more storage media, The above instructions, when individually or collectively executed by the at least one processor, cause the device to: Obtaining a control plane message including extension type information for detection of a random access preamble from a distributed unit (DU); and Causes the DU to transmit an uplink message containing information about random access preambles, The above random access preambles are detected based on the above extended type information, The above extended type information includes information on indications for detection random access preambles and information on the maximum number of reporting random access preambles. device.
2. In claim 1, The above instructions, when individually or collectively executed by the at least one processor, cause the device to: Receives signals transmitted from a first UE (user equipment) through the transceiver; Detecting a first random access preamble associated with the first UE based on the signals received from the first UE and the extended type information; Receiving signals transmitted from a second UE through the transceiver; and further cause a second random access preamble associated with the second UE to be detected based on the signals received from the second UE and the extended type information, The information about the random access preambles included in the uplink message transmitted to the DU is generated based on the first random access preamble and the second random access preamble. device.
3. In claim 1, The above extension type information includes an extension flag, an index of the extension type information, a length of the extension type information, a number of cyclic shifts indicated by a ZCZ (zero correlation zone) configuration, a root sequence index, and a restricted set configuration. device.
4. In claim 3, The above extended type information further includes at least one of a maximum TA (timing advance) threshold, a detection energy threshold, or whitening information for interference removal. device.
5. In claim 1, The above instruction information includes a start number of the detection random access preambles and an end number of the detection random access preambles, The information about the above maximum number indicates the maximum number of the reporting random access preambles in ascending order of detected energy for each of the detection random access preambles, and The number of the above random access preambles is less than or equal to the above maximum number. device.
6. In claim 1, The above instruction information includes a bitmap for indicating the detection random access preambles, The above maximum number information indicates the maximum number of the reporting random access preambles in ascending order of detected energy for each of the detection random access preambles, and The number of the above random access preambles is less than or equal to the above maximum number. device.
7. In claim 1, The above control plane message is associated with section type 3. RU.
8. In claim 1, The above uplink message includes an uplink control plane message, The above uplink control plane messages are: Time resource information when the above random access preambles were transmitted; Information indicating the number of the above random access preambles; and Contains a detection result for each of the above random access preambles; The above detection result includes information about the index of the random access preamble, the TA (timing advance) corresponding to the index, and the detected energy. device.
9. In claim 1, The above uplink message includes an uplink user plane message, The above uplink user plane messages are: Time resource information when the above random access preambles were transmitted; Information on the number of PRBs (physical resource blocks) for indicating the number of the above random access preambles; and Contains a detection result for each of the above random access preambles; The above detection result includes information about the index of the random access preamble, the TA (timing advance) corresponding to the index, and the detected energy. device.
10. In claim 8, If the control plane message includes a 1R (reception path) report setting, and the value of the 1R report setting indicates that the information about the random access preambles is to be transmitted through one reception path, the uplink message further includes information indicating the reception path. device.
11. In claim 1, The above instructions, when individually or collectively executed by the at least one processor, cause the device to: further causing the uplink message including the information about the random access preambles to be transmitted within a transmission window, The above transmission window is identified based on a minimum required time for transmission of the uplink message set with respect to a reference time and a maximum required time for transmission of the uplink message set with respect to the reference time, The above reference time is indicated based on the start symbol identity included in the control plane message. device. In the device of 12.DU(distributed unit), transceiver; At least one processor comprising a processing circuit; and A memory storing instructions and including one or more storage media, The above instructions, when individually or collectively executed by the at least one processor, cause the device to: Transmitting, to a radio unit (RU), a control plane message including extension type information for detection of a random access preamble; and Causing to obtain, from the RU, an uplink message containing information about random access preambles, The above random access preambles are detected by the RU based on the extended type information, The above extended type information includes information on indications for detection random access preambles and information on the maximum number of reporting random access preambles. device. In a method performed by 13.RU (radio unit), An operation of obtaining, from a distributed unit (DU), a control plane message including extension type information for detection of a random access preamble; and An operation of transmitting, to the DU, an uplink message including information about random access preambles, The above random access preambles are detected based on the above extended type information, The above extended type information includes information on indications for detection random access preambles and information on the maximum number of reporting random access preambles. method.
14. In claim 13, The above method: An operation of receiving signals transmitted from a first UE (user equipment); An operation of detecting a first random access preamble associated with the first UE based on the signals received from the first UE and the extended type information; An operation of receiving signals transmitted from a second UE; and Further comprising an operation of detecting a second random access preamble associated with the second UE based on the signals received from the second UE and the extended type information, The information about the random access preambles included in the uplink message transmitted to the DU is generated based on the first random access preamble and the second random access preamble. method.
15. A non-transitory computer-readable storage medium, when executed individually or collectively by at least one processor of a radio unit (RU) including a transceiver, Obtaining a control plane message including extension type information for detection of a random access preamble from a distributed unit (DU); and storing one or more programs including instructions causing the DU to transmit an uplink message including information about random access preambles; The above random access preambles are detected based on the above extended type information, The above extended type information includes information on indications for detection random access preambles and information on the maximum number of reporting random access preambles. A non-transitory computer-readable storage medium.
Citation Information
Patent Citations
A method, an apparatus, an electronic device, a storage medium, a roadside device, a cloud control platform, and computer program product for processing trajectory
KR1020210138523A
Compound, coating composition comprising same, method for preparing compound and electronic device
KR1020230139095A
Distributed unit (DU) measurement and event reporting in disaggregated base station
US20210337412A1
Provision of RACH related information for connection failure detection
US20220124817A1
Enabling physical random-access channel repetition combining in radio unit for o-ran-based radio access network
WO2023028935A1
Cited By
Physical random access channel fronthaul interface bandwidth reduction for open radio access network
WO2026195153A1
