Management node, distributed unit, wireless communication system, and wireless communication method

Abstract

This communication device constitutes a management node for managing a first base station and / or a second base station disposed on a front haul. The communication device is provided with: an acquisition unit that acquires a delay profile of the second base station; a control unit that determines a window parameter for use in specifying a reception window and / or a transmission window to be used at the first base station, on the basis of the delay profile of the second base station and a delay parameter defined by the front haul; and a notification unit that notifies the first base station of the window parameter.

Description

[Technical field]

[0001] The present invention relates to a communication device compatible with a fronthaul interface. [Background technology]

[0002] With the aim of promoting open and intelligent radio access networks (RANs) in the 5G era, Open The RAN (Radio Access Network) Alliance was established, and today many operators and vendors have joined and are engaged in discussions.

[0003] Several architectures are being discussed for O-RAN, one of which is an open fronthaul (FH) interface that would enable interconnection between baseband processing units and radio units between different vendors.

[0004] Specifically, O-RAN defines the O-RAN Distributed Unit (O-DU) and O-RAN Radio Unit (O-RU) as a group of functions performing Layer 2 functions, baseband signal processing, and radio signal processing, and is being discussed as an interface between the O-DU and O-RU.

[0005] The O-DU is a logical node that mainly hosts the Radio Link Control layer (RLC), Medium Access Control layer (MAC) and PHY-High layer based on the lower layer functional. The O-RU is a logical node that mainly hosts the PHY-Low layer and RF processing based on the lower layer functional division.

[0006] In O-RAN, the O-DU / O-RU functional division point is located in the physical (PHY) layer, so strict timing accuracy is required. For this reason, FH delay management is performed, and transmission and reception windows are used as a method (Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] "ORAN-WG4.CUS.0-v02.00", O-RAN Fronthaul Working Group, Control, User and Synchronization Plane Specification, O-RAN Alliance, August 2019 Summary of the Invention

[0008] In recent years, assuming a case where O-DU / O-RU are provided by different vendors / operators, studies are underway on NMS (Network Management System) that manages O-DU / O-RU provided by different vendors / operators.

[0009] However, the function of the NMS in managing FH delays has not been clearly defined, and this needs to be clarified.

[0010] Therefore, the present invention has been made in consideration of the above circumstances, and has an object to provide a communication device that enables appropriate management of fronthaul (FH) delays using an NMS.

[0011] One aspect of the present disclosure is a communication device, which constitutes a management node that manages at least one of a first base station and a second base station provided on a fronthaul, and includes an acquisition unit that acquires a delay profile of the second base station, a control unit that determines window parameters used to identify at least one of a receive window and a transmit window used by the first base station based on the delay profile of the second base station and delay parameters defined in the fronthaul, and a notification unit that notifies the first base station of the window parameters.

[0012] One aspect of the present disclosure is a communication device, the communication device constituting a first base station that communicates with a second base station over a fronthaul, comprising: an acquisition unit that acquires window parameters used to specify at least one of a receive window and a transmit window to be used in the first base station from a management node that manages at least one of the first base station and the second base station; and a control unit that sets at least one of the receive window and the transmit window based on the window parameters, and the window parameters are determined in the management node based on a delay profile of the second base station and delay parameters defined in the fronthaul.

[0013] One aspect of the present disclosure is a communication device, comprising: a first base station that configures communication with a second base station over a fronthaul; an acquisition unit that acquires a delay profile of the second base station from the second base station and acquires delay parameters defined in the fronthaul from a management node that manages at least one of the first base station and the second base station; and a control unit that sets at least one of a receive window and a transmit window used in the first base station based on the delay profile and the delay parameters of the second base station.

[0014] One aspect of the present disclosure is a communication device, which constitutes a management node that manages at least one of a first base station and a second base station provided on a fronthaul, and has a notification unit that notifies the first base station of a delay parameter defined in the fronthaul, and the delay parameter, together with a delay profile of the second base station, is used to set at least one of a receive window and a transmit window used in the first base station. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10 according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the internal configuration of a gNB 100 that employs a fronthaul (FH) interface according to an embodiment. [Diagram 3] FIG. 3 is a diagram showing a network that employs an FH interface according to the embodiment. [Figure 4A] FIG. 4A is a diagram illustrating an example of a fronthaul configuration (without an intermediate device) according to the embodiment. [Figure 4B] FIG. 4B is a diagram illustrating an example of a fronthaul configuration (with intermediate device, FHM configuration) according to the embodiment. [Figure 4C] FIG. 4C is a diagram illustrating an example of a fronthaul configuration (with intermediate device, cascade configuration) according to the embodiment. [Diagram 5] FIG. 5 is a functional block diagram of the NMS 300 according to the embodiment. [Figure 6] FIG. 6 is a functional block configuration diagram of the O-DU 110 according to the embodiment. [Figure 7] FIG. 7 is a functional block diagram of the O-RU 120 according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of delay management of a fronthaul in a UL according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of delay management of a fronthaul in DL according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of an O-RU delay profile according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of window parameters according to the embodiment. [Figure 12] FIG. 12 is a sequence diagram for explaining the first procedure according to the embodiment. [Figure 13] FIG. 13 is a sequence diagram for explaining the second procedure according to the embodiment. [Figure 14] FIG. 14 is a sequence diagram for explaining the third procedure according to the embodiment. [Figure 15]FIG. 15 is a diagram illustrating an example of the hardware configuration of the O-DU 110, the O-RU 120, and the NMS 300. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, an embodiment will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and the description thereof will be omitted as appropriate.

[0017] [Embodiment] (1) Overall configuration of wireless communication system 1 is a schematic diagram of an overall configuration of a wireless communication system 10 according to an embodiment. In the embodiment, the wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).

[0018] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.

[0019] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may be simply referred to as a network.

[0020] The gNB 100 is a radio base station conforming to 5G, and executes 5G radio communication with the UE 200. The gNB 100 and the UE 200 can support Massive MIMO, which generates a more directional beam by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) by bundling them, and Dual Connectivity (DC), which simultaneously communicates between the UE and each of multiple NG-RAN Nodes.

[0021] Also, in an embodiment, the gNB 100 adopts a fronthaul (FH) interface defined by O-RAN.

[0022] (2) Fronthaul configuration Fig. 2 shows an example of the internal configuration of a gNB 100 that employs a fronthaul (FH) interface. As shown in Fig. 2, the gNB 100 includes an O-DU 110 (O-RAN Distributed Unit) and an O-RU 120 (O-RAN Radio Unit). The O-DU 110 and the O-RU 120 are functionally separated (Function split) in the physical (PHY) layer defined by 3GPP.

[0023] The O-DU 110 may be referred to as an O-RAN distributed unit. The O-DU 110 is a logical node that mainly hosts a radio link control layer (RLC), a medium access control layer (MAC), and a PHY-High layer based on lower layer functional. Here, the O-DU 110 is provided on the side closer to the NG-RAN 20 with respect to the O-RU 120. Hereinafter, the side closer to the NG-RAN 20 may be referred to as the RAN side.

[0024] The O-RU 120 may be referred to as an O-RAN radio unit. The O-RU 120 is a logical node that mainly hosts a PHY-Low layer and RF processing based on a functional division of a low layer. Here, the O-RU 120 is provided on the side of the O-DU 110 that is remote from the NG-RAN 20. Hereinafter, the side that is remote from the NG-RAN 20 may be referred to as the air side.

[0025] The PHY-High layer is the PHY processing part on the O-DU110 side of the fronthaul interface, which performs functions such as Forward Error Correction (FEC) encoding / decoding, scrambling, and modulation / demodulation.

[0026] The PHY-Low layer is the PHY processing part on the O-RU 120 side of the fronthaul interface, such as Fast Fourier Transform (FFT) / iFFT, digital beamforming, and Physical Random Access Channel (PRACH) extraction and filtering.

[0027] O-CU stands for O-RAN Control Unit and is a logical node that hosts the Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and other control functions.

[0028] The fronthaul (FH) may be interpreted as a line between the baseband processing unit of a wireless base station (base station device) and the wireless device, and optical fiber or the like is used.

[0029] (3) Network configuration 3 shows a network employing an FH interface according to an embodiment of the present invention. As shown in FIG. 3, the network includes an NMS (Network Management System) 300, an O-DU 110, and an O-RU 120.

[0030] The NMS 300 is an example of a management node that manages at least one of the O-DU 110 and the O-RU 120. The NMS 300 is an example of a non-real-time RIC (RAN Intelligent Controller). The NMS 300 may be provided in a core network. In an embodiment, the NMS 300 may have a delay management function of the FH. An interface between the NMS 300 and the O-DU 110 may be referred to as an A1 interface between a non-real-time RIC and a real-time RIC (e.g., the gNB 100).

[0031] As described above, the O-DU 110 may be referred to as an O-RAN distributed unit. The O-DU 110 is provided on the FH and is an example of a first base station that communicates with the O-RU 120 on the FH. The O-DU 110 is provided on the RAN side of the O-RU 120. A network may include one or more O-DUs 110. In FIG. 3, the case where the O-DU 110A and the O-DU 110B are provided is illustrated as the O-DU 110. The O-DU 110A and the O-DU 110B may be provided by different vendors or operators.

[0032] As described above, the O-RU 120 may be referred to as an O-RAN radio unit. The O-RU 120 is provided on the FH and is an example of a second base station that communicates with the O-DU 110 on the FH. The O-RU 120 is provided on the air side of the O-DU 110. A network may include one or more O-RUs 120. FIG. 3 illustrates a case in which O-RU 120A1, O-RU 120A2, O-RU 120A3, and O-RU 120A4 are provided as O-RUs 120 on the air side of the O-DU 110A. FIG. 3 illustrates a case in which O-RU 120B1, O-RU 120B2, and O-RU 120B3 are provided as O-RUs 120 on the air side of the O-DU 110B. O-RU 120A1 to O-RU 120A4 may be provided by different vendors or businesses, and O-RU 120B1 to O-RU 120B3 may be provided by different vendors or businesses. Furthermore, O-RU 120A1 to O-RU 120A4 may be provided by a vendor or business different from O-DU 110A, and O-RU 120B1 to O-RU 120B3 may be provided by a vendor or business different from O-DU 110B.

[0033] In the example shown in FIG. 3, the delay time of the FH between the O-DU110A and the O-RU120A1 may be shorter than the delay time of the FH between the O-DU110A and the O-RU120A2. The delay time of the FH between the O-DU110A and the O-RU120A2 may be shorter than the delay time of the FH between the O-DU110A and the O-RU120A3. The delay time of the FH between the O-DU110A and the O-RU120A3 may be shorter than the delay time of the FH between the O-DU110A and the O-RU120A4. Similarly, the delay time of the FH between the O-DU110B and the O-RU120B1 may be shorter than the delay time of the FH between the O-DU110B and the O-RU120B2. The delay time of the FH between the O-DU 110B and the O-RU 120B2 may be shorter than the delay time of the FH between the O-DU 110B and the O-RU 120B3.

[0034] Here, the following signal communications are performed in the FH between the O-DU 110 and the O-RU 120. Specifically, in the FH between the O-DU 110 and the O-RU 120, signal communications are performed in a plurality of planes (for example, U / C / M / S-planes).

[0035] U-Plane is a protocol for transferring user data, C-Plane is a protocol for transferring control signals, M-Plane is a management plane that handles maintenance and monitoring signals, and S-Plane is a protocol for achieving synchronization between devices.

[0036] Specifically, U-Plane signals include signals that the O-RU 120 transmits to the wireless section (DL) and receives from the wireless section (UL), and are exchanged as digital IQ signals. Note that in addition to so-called U-Plane signals (data such as User Datagram Protocol (UDP) and Transmission Control Protocol (TCP)), C-Plane signals (RRC, Non-Access Stratum (NAS), etc.) defined by 3GPP are all considered U-Plane from the FH perspective.

[0037] C-Plane signals include signals necessary for various controls related to the transmission and reception of U-Plane signals (signals for notifying information related to the corresponding U-Plane radio resource mapping and beamforming). Note that C-Plane signals (RRC, NAS, etc.) defined by 3GPP refer to completely different signals.

[0038] The M-Plane signals include signals necessary for managing the O-DU 110 and the O-RU 120. For example, these signals are used for the O-RU 120 to notify various hardware (HW) capabilities of the O-RU 120 and for the O-DU 110 to notify the O-RU 120 of various setting values.

[0039] The S-Plane signal is a signal required for synchronous control between the O-DU 110 and the O-RU 120.

[0040] In this embodiment, under such circumstances, a description will be given of a procedure for setting at least one of the receive window and the transmit window of the O-DU 110. As such a procedure, the following first to third procedures are considered.

[0041] In the first procedure, NMS300 acquires the delay profile of each O-RU120 (hereinafter, O-RU delay profile) from the O-DU110. NMS300 determines window parameters used to specify at least one of a receive window and a transmit window used by the O-DU110, based on delay parameters defined in the FH between the O-DU110 and the O-RU120 (hereinafter, FH delay parameters) and the O-RU delay profile. NMS300 notifies the O-DU110 of the window parameters. The O-DU110 sets at least one of a receive window and a transmit window used by the O-DU110, based on the window parameters.

[0042] In the second procedure, the O-DU 110 acquires an O-RU delay profile from each O-RU 120. The O-DU 110 acquires an FH delay parameter from the NMS 300. The O-DU 110 sets at least one of a receive window and a transmit window used by the O-DU 110 based on the O-RU delay profile and the FH delay parameter.

[0043] In a third procedure, NMS 300 acquires an O-RU delay profile from each O-RU 120. NMS 300 determines a window parameter used to specify at least one of a receive window and a transmit window used by O-DU 110, based on the FH delay parameter and the O-RU delay profile. NMS 300 notifies O-DU 110 of the window parameter. O-DU 110 sets at least one of a receive window and a transmit window used by O-DU 110, based on the window parameter.

[0044] The O-RU delay profile, the FH delay parameters and the window parameters will be described in detail later (see FIGS. 8 to 11).

[0045] (4) Shared Cell Configuration In O-RAN, there is a station placement method in which one cell is composed of multiple O-RUs, and a configuration using a device that bundles O-RUs (FHM: Fronthaul Multiplexing) and a configuration in which O-RUs are connected in series (cascade configuration) are being considered. These are collectively called Shared Cells. Such Shared Cells may be adopted in the network shown in Figure 3.

[0046] Figures 4A to 4C show examples of fronthaul configurations. Figure 4A shows an example in which one cell is configured with one O-RU. Meanwhile, Figures 4B and 4C show examples of a shared cell configuration.

[0047] Specifically, Fig. 4B shows a configuration example using an FHM 130. Also, Fig. 4C shows an example in which an O-RU 130A is interposed between an O-DU 110 and an O-RU 120 and connected in cascade.

[0048] In the case of FIG. 4B, the FHM 130 combines the two FH signals from each O-RU 120 and transmits the combined signal to the O-DU 110.

[0049] In the case of FIG. 4C, O-RU 130A (O-RU(1)) combines the signal it itself receives in the wireless section with the FH signal received from O-RU 120 (O-RU(2)), and transmits the combined signal to O-DU 110.

[0050] In the following description, the FHM 130 and the O-RU 130A are collectively referred to as intermediate device 130. However, the intermediate device may be called by a different name. The intermediate device 130 is provided on the air side of the O-DU 110 and on the RAN side of the O-RU 120.

[0051] A feature of such a shared cell configuration is that, for downlink (DL), intermediate device 130 transfers a DL signal received from O-DU 110 to O-RU 120. Note that in the case of cascaded connection of O-RUs, intermediate device 130 may further transmit a DL signal of the O-RU itself.

[0052] For the uplink (UL), intermediate device 130 combines UL signals received from O-RU 120 and transfers the combined signal to O-DU 110. In the case of a cascade connection of O-RUs, intermediate device 130 also combines radio signals received by the O-RUs themselves.

[0053] These characteristics enable O-DU 110 to process signals in the same manner as if one O-RU were connected.

[0054] (5) Functional block configuration of wireless communication system Next, a description will be given of the functional block configuration of the wireless communication system 10. Specifically, the functional block configurations of the NMS 300, the O-DU 110, and the O-RU 120 will be described.

[0055] (5.1) NMS300 5 is a functional block diagram of the NMS 300. As shown in FIG. 5, the NMS 300 includes a communication unit 310, an acquisition unit 330, a notification unit 350, and a control unit 370.

[0056] The communication unit 310 executes communication with the O-DU 110. The communication unit 310 may execute communication with the O-RU 120. The communication unit 310 executes communication of parameters used to set a receive window and a transmit window used in the O-DU 110.

[0057] The acquiring unit 330 acquires various parameters. For example, the acquiring unit 330 acquires the O-RU delay profile from the O-DU 110 in the above-mentioned first procedure. The acquiring unit 330 acquires the O-RU delay profile from the O-RU 120 in the above-mentioned third procedure.

[0058] The notification unit 350 notifies various parameters. For example, the notification unit 350 notifies the O-DU 110 of the window parameter in the above-mentioned second procedure.

[0059] The control unit 370 controls the NMS 300. For example, in the first and third procedures described above, the control unit 370 determines the window parameters based on the FH delay parameters and the O-RU delay profile.

[0060] (5.2) O-DU110 Fig. 6 is a functional block configuration diagram of the O-DU 110. As shown in Fig. 6, the O-DU 110 includes a communication unit 111, an acquisition unit 113, a notification unit 115, and a control unit 117.

[0061] The communication unit 111 communicates with the O-RU 120. The communication unit 111 may communicate with the NMS 300. For example, the communication unit 111 communicates signals of the various planes described above.

[0062] Acquiring unit 113 acquires various parameters. For example, acquiring unit 113 acquires an O-RU delay profile from O-RU 120 in the above-described first to third procedures. Acquiring unit 113 acquires a window parameter from NMS 300 in the above-described first and third procedures. Acquiring unit 113 acquires an FH delay parameter from NMS 300 in the above-described second procedure.

[0063] The notification unit 115 notifies various parameters. For example, the notification unit 115 notifies the NMS 300 of the O-RU delay profile in the first procedure described above.

[0064] The control unit 117 controls the O-DU 110. For example, in the above-mentioned first and third procedures, the control unit 117 sets at least one of the reception window and the transmission window based on the window parameters. In the above-mentioned second procedure, the control unit 117 sets at least one of the reception window and the transmission window based on the O-RU delay profile and the FH delay parameter.

[0065] (5.3) O-RU120 Fig. 7 is a functional block configuration diagram of the O-RU 120. As shown in Fig. 7, the O-RU 120 includes a communication unit 121, an acquisition unit 123, a notification unit 125, and a control unit 127.

[0066] The communication unit 121 executes communication with the O-DU 110. The communication unit 121 may execute communication with the NMS 300. For example, the communication unit 121 executes communication of signals of the various planes described above.

[0067] The acquisition unit 123 acquires various parameters. The acquisition unit 123 acquires parameters used in software management from the O-DU 110. Software management is a procedure defined in Chapter 5 of ORAN-WG4.MP.0-v02.00 and the like.

[0068] The notification unit 125 notifies various parameters. In the above-mentioned first to third procedures, the notification unit 125 notifies the O-RU delay profile to the O-DU 110. In the above-mentioned third procedure, the notification unit 125 notifies the O-RU delay profile to the NMS. 300 Notify.

[0069] Control unit 127 controls O-RU 120. For example, control unit 127 sets at least one of a receiving window and a transmitting window.

[0070] (6) Window settings First, the UL signal will be described with reference to FIG.

[0071] As shown in FIG. 8, the transmission window (UL) of the O-RU 120 can be defined by parameters (Ta3_min, Ta3_max). That is, the Transmission window (UL) can be expressed by the difference between Ta3_max and Ta3_min. The parameters (Ta3_min, Ta3_max) may be interpreted as the measurement results from reception at the O-RU antenna to output at the O-RU port (R3). Ta3_min and Ta3_max are examples of an O-RU delay profile. Ta3_min and Ta3_max may be different for each O-RU 120.

[0072] On the other hand, the reception window (Reception window (UL)) of the O-DU 110 can be defined by parameters (Ta4_min, Ta4_max). That is, the reception window (UL) can be expressed by the difference between Ta4_max and Ta4_min. The parameters (Ta4_min, Ta4_max) may be interpreted as a measurement result from reception at the O-RU antenna to reception at the O-DU port (R4). The parameters (Ta4_min, Ta4_max) may be measured by a delay measurement message (Measured Transport Method).

[0073] Here, as the above-mentioned FH delay parameter, a parameter (T34_min) indicating the difference between Ta4_min and Ta3_min may be defined in advance. As the above-mentioned FH delay parameter, a parameter (T34_max) indicating the difference between Ta4_max and Ta3_max may be defined in advance. The FH delay parameter is managed by the NMS 300. T34_min and T34_max may be determined for each use case of the O-RAN. T34_min and T34_max may be different for each O-DU 110, or may be common to the O-DU 110.

[0074] Under these assumptions, Ta4_min, which defines the Reception window (UL), only needs to satisfy the condition that it is a value equal to or less than Ta3_min+T34_min for O-RU 120 located on the air side of O-DU 110. Ta4_max, which defines the Reception window (UL), only needs to satisfy the condition that it is a value equal to or greater than Ta3_max+T34_max for O-RU 120 located on the air side of O-DU 110. NMS 300 determines the window parameters so as to satisfy these conditions (window conditions). Alternatively, O-DU 110 sets the Reception window (UL) so as to satisfy the window conditions.

[0075] Thus, the Reception window (UL) may be determined by the O-RU delay profile (Ta3_min, Ta3_max) and the FH delay parameters (T34_min, T34_max). The window parameters may include Ta4_min and Ta4_max.

[0076] Secondly, the DL signal will be described with reference to FIG.

[0077] As shown in FIG. 9, the transmission window (DL) of the O-DU 110 can be defined by parameters (T1a_min_up, T1a_max_up). The transmission window (DL) can be expressed by the difference between T1a_max_up and T1a_min_up. The parameters (T1a_min_up, T1a_max_up) may be interpreted as a measurement result from the output at the O-DU port (R1) to radio transmission. The parameters (T1a_min_up, T1a_max_up) may be measured by a delay measurement message (Measured Transport Method).

[0078] On the other hand, the reception window (DL) of the O-RU 120 can be defined by parameters (T2a_min_up, T2a_max_up). The reception window (DL) can be expressed by the difference between T2a_max_up and T2a_min_up. The parameters (T2a_min_up, T2a_max_up) may be interpreted as measurement results from reception at the O-RU port (R2) to radio transmission. T2a_min_up and T2a_max_up are examples of an O-RU delay profile. T2a_min_up and T2a_max_up may be different for each O-RU 120.

[0079] Here, as the above-mentioned FH delay parameter, a parameter (T12_min) indicating the difference between T1a_max_up and T2a_max_up may be defined in advance. As the above-mentioned FH delay parameter, a parameter (T12_max) indicating the difference between T1a_min_up and T2a_min_up may be defined in advance. The FH delay parameter is managed by the NMS 300. T12_min and T12_max may be determined for each use case of the O-RAN. T12_min and T12_max may be different for each O-DU 110, or may be common to the O-DU 110.

[0080] Under such a premise, it is sufficient that T1a_min_up, which defines the Transmission window (DL), is equal to or greater than T2a_min_up+T12_max for O-RU 120 located on the air side of O-DU 110. It is sufficient that T1a_max_up, which defines the Transmission window (DL), is equal to or less than T2a_max_up+T12_min for O-RU 120 located on the air side of O-DU 110. NMS 300 determines the window parameters so as to satisfy these conditions (window conditions). Alternatively, O-DU 110 sets the Transmission window (DL) so as to satisfy the window conditions.

[0081] Thus, the Transmission window (DL) may be determined by the O-RU delay profile (T2a_min_up, T2a_max_up) and the FH delay parameters (T12_min, T12_max). The window parameters may include T1a_min_up and T1a_max_up.

[0082] Here, "up" means U-Plane. The parameters related to the DL signal of the C-Plane may include T1a_min_cp_dl, T1a_max_cp_dl, T2a_min_cp_dl, T2a_max_cp_dl, and Tcp_adv_dl. In such a case, "cp" means C-Plane. T1a_min_cp_dl may be represented by T1a_min_up+Tcp_adv_dl, and T1a_max_cp_dl may be represented by T1a_max_up+Tcp_adv_dl. Similarly, T2a_min_cp_dl may be represented by T2a_min_up+Tcp_adv_dl, and T2a_max_cp_dl may be represented by T2a_max_up+Tcp_adv_dl.

[0083] Therefore, for a DL signal of the C-Plane, T2a_min_cp_dl and T2a_max_cp_dl are an example of an O-RU delay profile. Tcp_adv_dl may be a value determined for each use case of the O-RAN. Tcp_adv_dl may be an example of an O-RU delay profile. T1a_min_cp_dl and T1a_max_cp_dl may be an example of a window parameter.

[0084] (7) Parameters First, the O-RU delay profile is described.

[0085] As shown in FIG. 10, the O-RU delay profile (ro ru-delay-profile) may include T2a_min_up (ro t2a-min-up), T2a_max_up (ro t2a-max-up), T2a_min_cp_dl (ro t2a-min-cp-dl), T2a_max_cp_dl (ro t2a-max-cp-dl), Tcp_adv_dl (ro tcp-adv-dl), Ta3_min (ro ta3-min), Ta3_max (ro ta3-max), etc.

[0086] Although not illustrated in FIG. 8 and FIG. 9, the O-RU delay profile may include parameters (T2a_min_cp_ul (ro t2a-min-cp-ul), T2a_max_cp_ul (ro t2a-max-cp-ul)) used in the UL signal of the C-plane. T2a_min_cp_ul may be a value determined for each use case of the O-RAN. T2a_max_cp_ul only needs to satisfy the condition that it is a value equal to or greater than T2a_min_cp_ul+(T12_max-T12_min)+O-DU Transmission Window.

[0087] Secondly, the window parameter will be described. The window parameter may be read as a delay profile related to the O-DU 110 (O-DU delay profile).

[0088] As shown in FIG. 11, the window parameter (rw O-DU-delay-profile) may include T1a_min_up (rw t1a-min-up), T1a_max_up (rw t1a-max-up), T1a_min_cp_dl (rw t1a-min-cp-dl), T1a_max_cp_dl (rw t1a-max-cp-dl), Ta4_min (rw ta4-min), Ta4_max (rw ta4-max), etc.

[0089] Although not illustrated in Figures 8 and 9, the window parameters may include parameters used in the UL signal of C-plane (T1a_min_cp_ul (rw t1a-min-cp-ul), T1a_max_cp_ul (rw t1a-max-cp-ul)). T1a_min_cp_ul only needs to satisfy the condition that it is a value equal to or greater than T12_max+T2a_min_cp_ul. T1a_max_cp_ul only needs to satisfy the condition that it is a value equal to or less than T12_min+T2a_max_cp_ul.

[0090] (8) Operation of wireless communication systems Next, a description will be given of the operation of the wireless communication system 10. Specifically, the above-mentioned first to third procedures will be described. Although omitted in Fig. 12 to Fig. 14, two or more O-DUs 110 may be provided, and two or more O-RUs 120 may be provided.

[0091] First, the first step will be described with reference to FIG.

[0092] 12, in step S10, a procedure for M-Plane connection establishment is performed between the NMS 300 and the O-DU 110. In step S11, a procedure for M-Plane connection establishment is performed between the O-DU 110 and the O-RU 120. The procedure for M-Plane connection establishment is a procedure for setting the M-Plane.

[0093] In step S12, the O-RU 120 transmits the O-RU delay profile to the O-DU 110. For example, the O-RU delay profile includes the parameters shown in Fig. 10. However, since the parameters related to the C-plane can be calculated by the O-DU 110, they do not need to be included in the O-RU delay profile.

[0094] In step S13, the O-DU 110 transmits the O-RU delay profile to the NMS 300. For example, the O-RU delay profile includes the parameters shown in Fig. 10. However, since the parameters related to the C-plane can be calculated by the O-DU 110, they do not need to be included in the O-RU delay profile.

[0095] In step S14, the NMS 300 determines window parameters to be used to specify at least one of a transmit window and a receive window to be used by the O-DU 110 based on the O-RU delay profile and the FH delay parameters.

[0096] In step S15, NMS 300 transmits the window parameters determined in step S14 to O-DU 110. For example, the window parameters include the parameters shown in Fig. 11. However, since parameters related to the C-plane can be calculated by O-DU 110, they do not need to be included in the window parameters. The window parameters are determined so as to satisfy the window conditions.

[0097] In step S16, the O-DU 110 sets at least one of a transmission window and a reception window based on the window parameters.

[0098] In step S17, a software management procedure is executed between the O-DU 110 and the O-RU 120. The software management procedure is a procedure for allowing desired software to be downloaded, installed, and started in the O-RU 120 (see Chapter 5 of ORAN-WG4.MP.0-v02.00, etc.).

[0099] Secondly, the second procedure will be described with reference to FIG.

[0100] As shown in FIG. 13, in step S20, similarly to step S10, the procedure of M-Plane connection establishment is executed between the NMS 300 and the O-DU 110. 11 Similarly, the M-Plane connection establishment procedure is executed between the O-DU 110 and the O-RU 120.

[0101] In step S22, the O-RU 120 transmits the O-RU delay profile to the O-DU 110, similar to step S12.

[0102] In step S23, the NMS 300 transmits the FH delay parameters to the O-DU 110. The FH delay parameters include T12_min, T12_max, T34_min, and T34_max.

[0103] In step S24, the O-DU 110 sets at least one of a transmission window and a reception window based on the O-RU delay profile and the FH delay parameter. For example, the O-DU 110 sets a reception window (UL) so as to satisfy the window condition. Similarly, the O-DU 110 sets a transmission window (DL) so as to satisfy the window condition.

[0104] In step S25, similar to step S17, a software management procedure is executed between the O-DU 110 and the O-RU 120.

[0105] Thirdly, the third procedure will be described with reference to FIG.

[0106] 14, in step S30, similar to step S10, a procedure for M-Plane connection establishment is performed between the NMS 300 and the O-DU 110. In step S31, similar to step S11, a procedure for M-Plane connection establishment is performed between the O-DU 110 and the O-RU 120.

[0107] In step S32, the O-RU 120 transmits the O-RU delay profile to the O-DU 110, similar to step S12.

[0108] In step S33, O-RU 120 transmits the O-RU delay profile to NMS 300. For example, the O-RU delay profile includes the parameters shown in Fig. 10. However, since parameters related to the C-plane can be calculated by O-DU 110, they do not need to be included in the O-RU delay profile.

[0109] In step S34, NMS 300 determines the window parameters based on the O-RU delay profile and the FH delay parameters, similar to step S14.

[0110] In step S35, the NMS 300 transmits the window parameters determined in step S34 to the O-DU 110, similar to step S15.

[0111] In step S36, the O-DU 110 sets at least one of the transmission window and the reception window based on the window parameters, similar to step S16.

[0112] In step S37, similar to step S17, a software management procedure is executed between the O-DU 110 and the O-RU 120.

[0113] (9) Actions and Effects In the embodiment, the NMS 300 determines the window parameters based on the O-RU delay profile and the FH delay parameters (first and third procedures). With this configuration, even in a case where the O-DU 110 and the O-RU 120 are provided by different vendors or operators, the NMS 300 can intervene to appropriately set the transmission window or reception window used in the O-DU 110. This allows appropriate FH delay management.

[0114] In the embodiment, the O-DU 110 sets a transmission window or a reception window based on the FH delay parameters and the O-RU delay profile acquired from the NMS 300 (second procedure). With this configuration, even in a case where the O-DU 110 and the O-RU 120 are provided by different vendors or operators, the NMS 300 can intervene to appropriately set the transmission window or reception window used by the O-DU 110. This allows appropriate FH delay management.

[0115] [Other embodiments] The present invention has been described above with reference to the embodiments. However, the present invention is not limited to these embodiments, and it will be obvious to those skilled in the art that various modifications and improvements are possible.

[0116] In the above-mentioned first and third procedures, the O-DU110 sets either the transmission window or the reception window (hereinafter, simply referred to as the window) based on a window parameter acquired from the NMS300. In such a case, the NMS300 may transmit a parameter that directly specifies the window to the O-DU110 as the window parameter. The NMS300 may transmit a parameter that indirectly specifies the window to the O-DU110 as the window parameter. The parameter that indirectly specifies the window may be a parameter that specifies a range or condition that the window should satisfy.

[0117] In the above-described first and third procedures, NMS300 acquires O-RU delay parameters from O-DU110 or O-RU120. In such a case, the O-RU delay parameters may include parameters related to the U-plane without including parameters related to the C-plane. Furthermore, the window parameters notified from NMS300 to O-DU110 may include parameters related to the U-plane without including parameters related to the C-plane. Furthermore, notification of parameters already known by O-DU110 or parameters that can be calculated by O-DU110 may be omitted.

[0118] The block diagrams (FIGS. 5 to 7) used in the description of the above-mentioned embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by using wires, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.

[0119] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. As described above, there is no particular limitation on the method of realization of any of these.

[0120] Furthermore, the above-mentioned O-DU 110 and intermediate device 130 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. 15 FIG. 1 is a diagram showing an example of a hardware configuration of the device. 15 As shown in the figure, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0121] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0122] Each functional block of the device (see FIGS. 5 and 6) is realized by any hardware element of the computer device, or a combination of the hardware elements.

[0123] In addition, each function in the device is realized by loading a specific software (program) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and storage 1003.

[0124] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0125] Furthermore, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. Furthermore, the above-mentioned various processes may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0126] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0127] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0128] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0129] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0130] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0131] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0132] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0133] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0134] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.

[0135] The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0136] In the present disclosure, a specific operation performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and other network nodes other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station, it may also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0137] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and may be input and output via multiple network nodes.

[0138] The input / output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to another device.

[0139] The determination may be based on a value represented by a single bit (0 or 1), a Boolean (true or false) value, or a numerical comparison (e.g., comparison with a predetermined value).

[0140] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

[0141] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0142] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0143] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0144] In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0145] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0146] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

[0147] The names used for the above-mentioned parameters are not limiting in any way. Furthermore, the formulas using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0148] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0149] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0150] The term "cell" or "sector" refers to part or all of the coverage area of ​​a base station and / or a base station subsystem that provides communication services within that coverage.

[0151] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0152] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0153] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0154] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies below). For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0155] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station. A radio frame may be composed of one or more frames in the time domain, where each of the one or more frames in the time domain may be referred to as a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0156] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a SubCarrier Spacing (SCS), a bandwidth, a symbol length, a Cyclic Prefix length, a Transmission Time Interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation that a transceiver performs in the frequency domain, a particular windowing operation that a transceiver performs in the time domain, etc.

[0157] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based unit of time.

[0158] A slot may include multiple minislots. Each minislot may be composed of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0159] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. The radio frame, the subframe, the slot, the minislot, and the symbol may each be referred to by a different name.

[0160] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0161] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0162] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0163] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0164] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.

[0165] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0166] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0167] In addition, the time domain of the RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0168] One or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0169] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0170] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0171] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0172] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0173] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0174] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0175] The reference signal may also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.

[0176] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0177] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0178] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0179] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term "comprising." Further, as used in this disclosure, the term "or" is not intended to be an exclusive or.

[0180] In this disclosure, where articles have been added due to translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0181] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0182] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0183] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0184] 10. Wireless communication systems 20 NG-RAN 100 gNB 110 O-DU 111 Communications Department 113 Acquisition Department 115 Notification Department 117 Control Unit 120 O-RU 121 Communications Department 123 Acquisition Department 125 Notification Department 127 Control Unit 130 Intermediate equipment (FHM) 130A O-RU 200UE 300 NMS 310 Communications Department 330 Acquisition Department 350 Notification Department 370 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device 1007 Bus

Claims

1. a receiver for receiving an O-RU delay profile of a radio unit (O-RU) provided on a fronthaul; A control unit that determines a window parameter used to specify at least one of a receive window and a transmit window used in a distributed unit (O-DU) provided on the fronthaul based on the O-RU delay profile and a delay parameter between the radio unit (O-RU) and a distributed unit (O-DU) defined in the fronthaul; A management node comprising: a transmitter that transmits the window parameter to the distributed unit (O-DU).

2. 2. The management node of claim 1, wherein the O-RU delay profile includes at least one of a parameter for determining the receive window, related to a delay from radio reception at an antenna of the radio unit O-RU to output at a port of the radio unit O-RU, and a parameter for determining the transmit window, related to a delay from reception at a port of the radio unit O-RU to radio transmission at an antenna of the radio unit O-RU.

3. The management node according to claim 1 , wherein the delay parameters include a parameter relating to a delay between the radio unit O-RU and the distributed unit O-DU.

4. The window parameters include parameters that define the receiving window and the transmitting window.

2. The method of claim 1, further comprising: Logical node.

5. A distributed unit (O-DU) provided on a fronthaul, A receiving unit for receiving a window parameter from a management node; Based on the window parameters, at least one of the receive window and the transmit window is and a control unit that sets any one of the above, The window parameter is determined in the management node based on an O-RU delay profile of a radio unit O-RU provided on the fronthaul and a delay parameter between the distributed unit O-DU and the radio unit O-RU defined in the fronthaul.

6. a radio unit (O-RU) provided on the fronthaul; A distributed unit (O-DU) provided on the fronthaul; a management node; The management node, a receiving unit for receiving an O-RU delay profile of the radio unit O-RU; A control unit that determines a window parameter used to specify at least one of a receive window and a transmit window used in the distributed unit O-DU based on the O-RU delay profile and a delay parameter between the distributed unit O-DU and the radio unit O-RU defined in the fronthaul; A wireless communication system comprising: a transmitting unit that transmits the window parameter to the distributed unit (O-DU).

7. receiving an O-RU delay profile of a radio unit (O-RU) provided on a fronthaul; determining a window parameter used to specify at least one of a receive window and a transmit window used in a distributed unit O-DU provided on the fronthaul based on the O-RU delay profile and a delay parameter between the distributed unit O-DU and the radio unit O-RU defined in the fronthaul; transmitting the window parameter to the distributed unit (O-DU).

Images