Communication Equipment

Abstract

The communication device constitutes a management node that manages at least one of the first base station and the second base station set on the fronthaul. The communication device comprises: an acquisition unit that acquires the window parameter of the first base station and the delay characteristic of the second base station from the first base station; and a control unit that determines whether the second base station can be connected to the first base station based on the window parameter of the first base station and the delay characteristic of the second base station.

Description

Technical Field

[0001] The present invention relates to a communication device supporting a fronthaul interface. Background Art

[0002] The O-RAN Alliance was established to promote the openness and intelligence of the radio access network (RAN) in the 5G era. Currently, a large number of operators and suppliers have joined and are discussing.

[0003] A variety of architectures have been discussed in O-RAN, and one of them is an open fronthaul (FH) interface that enables interconnection between baseband processing units and radio units of different vendors.

[0004] Specifically, in O-RAN, as a functional group that performs layer 2 functions, baseband signal processing, and wireless signal processing, the O-RAN distributed unit (O-DU Distributed Unit: O-DU) and the O-RAN wireless unit (O-RU Radio Unit: O-RU) are defined and discussed as the interface between the O-DU and the O-RU.

[0005] 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 lower layer functionalities. O-RU is a logical node that mainly hosts the PHY-Low layer and RF processing based on lower layer functional division.

[0006] In O-RAN, since the O-DU / O-RU function sharing point is set in the physical (PHY) layer, strict timing accuracy is required. Therefore, FH delay management is performed, and as a method, the sending window and the receiving window are used (Non-Patent Document 1).

[0007] Prior art literature

[0008] Non-patent literature

[0009] 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

[0010] In recent years, it is envisioned that O-DU / O-RU may be provided by different vendors / operators, and research on NMS (Network Management System) that manages O-DU / O-RU provided by different vendors has been advanced.

[0011] However, the role that NMS should play in delay management of FH has not been clearly defined and needs to be clarified.

[0012] Therefore, the present invention has been made in view of such a situation, and an object of the present invention is to provide a communication device capable of appropriately performing delay management of forward haul (FH) using an NMS.

[0013] The main purpose of one embodiment of the present disclosure is a communication device, wherein the communication device constitutes a management node for managing at least one of a first base station and a second base station set on a fronthaul, and the communication device comprises: an acquisition unit, which acquires the window parameters of the first base station from the first base station and acquires the delay characteristics of the second base station; and a control unit, which determines whether the second base station can be connected to the first base station based on the window parameters of the first base station and the delay characteristics of the second base station.

[0014] The main purpose of one embodiment of the present disclosure is a communication device, wherein the communication device constitutes a first base station that communicates with a second base station on a fronthaul, and the communication device has a notification unit that notifies a management node that manages at least either the first base station or the second base station of a window parameter of the first base station, and the window parameter of the first base station is used together with a delay characteristic of the second base station to determine whether the second base station can be connected to the first base station.

[0015] One embodiment of the present disclosure is directed to a communication device, wherein the communication device constitutes a first base station that communicates with a second base station on a fronthaul, and the communication device comprises: an acquisition unit that acquires the delay characteristics of the second base station from the second base station; a control unit that determines whether the second base station can be connected to the first base station based on the window parameters of the first base station and the delay characteristics of the second base station; and a notification unit that, when the second base station cannot be connected to the first base station, notifies a management node that manages at least either the first base station or the second base station that the second base station cannot be connected to the first base station. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a diagram schematically showing the overall configuration of a wireless communication system 10 according to an embodiment.

[0017] Figure 2 2 is a diagram showing an example of the internal structure of a gNB 100 using a fronthaul (FH) interface of an implementation scheme.

[0018] Figure 3 is a diagram showing a network employing an FH interface according to an embodiment.

[0019] Figure 4A It is a diagram showing a configuration example (without an intermediate device) of a forward transmission according to an embodiment.

[0020] Figure 4B It is a diagram showing a configuration example of a forward haul according to an embodiment (with an intermediate device and an FHM configuration).

[0021] Figure 4C This is a diagram showing a configuration example (with an intermediate device and a cascade structure) of a forward transmission according to an embodiment.

[0022] Figure 5 4 is a functional block diagram of the NMS 300 according to the embodiment.

[0023] Figure 6 2 is a functional block diagram of the O-DU 110 according to the embodiment.

[0024] Figure 7 FIG. 1 is a functional block diagram of the O-RU 120 according to the embodiment.

[0025] Figure 8 This is a diagram showing an example of delay management of the fronthaul in the UL according to the embodiment.

[0026] Fig. 9 This is a diagram showing an example of delay management of forward transmission in DL according to the embodiment.

[0027] Fig.10 This is a diagram showing an example of an O-RU delay profile according to an embodiment.

[0028] Fig.11 It is a diagram showing an example of window parameters according to the embodiment.

[0029] Fig.12 It is a timing chart for explaining the first process of the implementation mode.

[0030] Fig.13 It is a timing chart for explaining the second process of the implementation method.

[0031] Fig.14 It is a timing chart for explaining the third process of the implementation method.

[0032] Fig.15 1 is a diagram showing an example of the hardware configuration of the O-DU 110 , the O-RU 120 , and the NMS 300 . DETAILED DESCRIPTION

[0033] Hereinafter, the embodiments will be described with reference to the drawings. In addition, the same or similar reference numerals are given to the same functions and structures, and the description thereof will be appropriately omitted.

[0034] [Implementation Method]

[0035] (1) Overall schematic structure of wireless communication system

[0036] Figure 1 This is an overall schematic configuration example of a wireless communication system 10 according to an implementation method. In the implementation method, the wireless communication system 10 is a wireless communication system that complies with the 5G New Radio (NR) standard, and includes a next generation radio access network 20 (Next Generation-Radio Access Network) (hereinafter referred to as NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter referred to as UE 200).

[0037] NG-RAN 20 includes a radio base station 100 (hereinafter referred to as gNB 100). In addition, the specific structure of the wireless communication system 10 including the number of gNBs and UEs is not limited to Figure 1 Example shown.

[0038] NG-RAN 20 actually includes multiple NG-RAN nodes (NG-RAN Node), specifically multiple gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). In addition, NG-RAN 20 and 5GC can be simply referred to as "network".

[0039] The gNB 100 is a 5G-compliant wireless base station that performs 5G-compliant wireless communications with the UE 200. The gNB 100 and the UE 200 can support Massive MIMO, which generates a more directional beam by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which bundles and uses multiple Component Carriers (CCs), and Dual Connectivity (DC), which allows simultaneous communication between the UE and multiple NG-RAN nodes.

[0040] In addition, in an embodiment, the gNB 100 adopts a fronthaul (FH) interface specified by O-RAN.

[0041] (2) Fronthaul Structure

[0042] Figure 2 An example of the internal structure of gNB 100 using a fronthaul (FH) interface is shown. Figure 2 As shown, 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 specified by 3GPP.

[0043] The O-DU 110 may also be referred to as an O-RAN distribution unit. The O-DU 110 is a logical node that mainly hosts the radio link control layer (RLC), the medium access control layer (MAC), and the PHY-High layer based on lower layer functionalities. Here, the O-DU 110 is arranged on a side close to the NG-RAN 20 relative to the O-RU 120. Hereinafter, the side close to the NG-RAN 20 is sometimes referred to as the RAN side.

[0044] The O-RU 120 may also be referred to as an O-RAN radio unit. The O-RU 120 is a logical node that mainly carries out PHY-Low layer and RF processing based on the functional division of the lower layer. Here, the O-RU 120 is provided on a side away from the NG-RAN 20 relative to the O-DU 110. Hereinafter, the side away from the NG-RAN 20 is sometimes referred to as the radio (air) side.

[0045] The PHY-High layer is a part of the PHY processing of the fronthaul interface on the O-DU 110 side, such as forward error correction (FEC) encoding / decoding, scrambling, modulation / demodulation, etc.

[0046] The PHY-Low layer is the PHY processing part of the fronthaul interface on the O-RU 120 side, including fast Fourier transform (FFT) / iFFT, digital beamforming, physical random access channel (PRACH) extraction and filtering.

[0047] O-CU is the abbreviation of O-RAN Control Unit, which 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.

[0048] In addition, the fronthaul (FH) can be interpreted as a line between the baseband processing unit of the wireless base station (base station device) and the wireless device, and optical fiber or the like can be used.

[0049] (3) Network structure

[0050] Figure 3 is a network showing an FH interface using an embodiment. Figure 3 As shown, the network includes a Network Management System (NMS) 300 , an O-DU 110 , and an O-RU 120 .

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

[0052] As described above, the O-DU 110 may also 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 at a position closer to the RAN side than the O-RU 120. A network only needs to have one or more O-DUs 110. Figure 3 , a case where the O-DU 110A and the O-DU 110B are provided as the O-DU 110 is exemplified. The O-DU 110A and the O-DU 110B may be provided by different vendors or operators.

[0053] As described above, the O-RU 120 may also be referred to as an O-RAN radio unit. The O-RU 120 is installed 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 installed on the air side of the O-DU 110. A network only needs to have one or more O-RUs 120. Figure 3 , a case where O-RU 120A1, O-RU 120A2, O-RU 120A3, and O-RU 120A4 are provided at a position closer to the air side than O-DU 110A as O-RU 120 is illustrated. A case where O-RU 120B1, O-RU 120B2, and O-RU 120B3 are provided at a position closer to the air side than O-DU 110B is illustrated as O-RU 120. O-RU 120A1 to O-RU 120A4 may be provided by different suppliers or operators, and O-RU 120B1 to O-RU 120B3 may be provided by different suppliers or operators. Furthermore, the O-RUs 120A1 to 120A4 may be provided by a different supplier or operator than the O-DU 110A, and the O-RUs 120B1 to 120B3 may be provided by a different supplier or operator than the O-DU 110B.

[0054] exist Figure 3 In the example shown, the delay time of FH between O-DU 110A and O-RU 120A1 may be shorter than the delay time of FH between O-DU 110A and O-RU 120A2. The delay time of FH between O-DU 110A and O-RU 120A2 may be shorter than the delay time of FH between O-DU 110A and O-RU 120A3. The delay time of FH between O-DU 110A and O-RU 120A3 may be shorter than the delay time of FH between O-DU 110A and O-RU 120A4. Similarly, the delay time of FH between O-DU 110B and O-RU 120B1 may be shorter than the delay time of FH between O-DU 110B and O-RU 120B2. The delay time of FH between the O-DU 110B and the O-RU 120B2 may be shorter than the delay time of FH between the O-DU 110B and the O-RU 120B3.

[0055] Here, the following signals are communicated 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, signals in multiple planes (eg, U / C / M / S-planes) are communicated.

[0056] U-Plane is a protocol for forwarding user data, C-Plane is a protocol for forwarding control signals, M-Plane is a management plane for processing maintenance and monitoring signals, and S-Plane is a protocol for achieving synchronization between devices.

[0057] Specifically, the U-Plane signal includes the (DL) signal sent by the O-RU 120 to the wireless section and the (UL) signal received from the wireless section, and is exchanged through the digital IQ signal. In addition, it should be noted that in addition to the so-called U-Plane signal (data such as the User Datagram Protocol (UDP) and the Transmission Control Protocol (TCP), etc.), the C-Plane (RRC, Non-Access Stratum (NAS), etc.) defined in 3GPP also becomes U-Plane from the perspective of FH.

[0058] C-Plane signals include signals required for various controls related to the transmission and reception of U-Plane signals (signals for notifying information related to the radio resource mapping and beamforming of the corresponding U-Plane). In addition, it should be noted that C-Plane (RRC, NAS, etc.) defined in 3GPP refers to completely different signals.

[0059] The M-Plane signal includes a signal necessary for managing the O-DU 110 / O-RU 120. For example, the M-Plane signal is a signal for notifying the O-RU 120 of various hardware (HW) capabilities of the O-RU 120 or notifying the O-DU 110 of various setting values.

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

[0061] In the embodiment, a process of determining whether the O-RU 120 and the O-DU 110 can be connected in this context is described. As such a process, the first to third processes shown below are considered. Here, based on the viewpoint of the delay time between the O-DU 110 and the O-RU 120, "connectable" means that a signal transmitted within the transmission window of the O-DU 110 can be received by the O-RU 120, or a signal transmitted from the O-RU 120 can be received within the reception window of the O-DU.

[0062] In the first process, the NMS 300 obtains the delay characteristics of each O-RU 120 (hereinafter referred to as the O-RU delay characteristics) from the O-DU 110. The NMS 300 obtains the window parameters of the O-DU 110 (hereinafter referred to as the O-DU window parameters) from the O-DU 110. The O-DU window parameters are parameters for determining at least one of the transmission window and the reception window used in the O-DU 110. The NMS 300 determines whether the O-RU 120 can be connected to the O-DU 110, for the O-RU 120 disposed at a position closer to the air side than the O-DU 110, based on the O-RU delay characteristics and the window parameters.

[0063] When the O-RU 120 cannot be connected to the O-DU 110, the NMS 300 notifies the O-DU 110 that the O-RU 120 cannot be connected to the O-DU 110 (hereinafter referred to as Failure). The Failure includes information for identifying the O-RU 120 that cannot be connected to the O-DU 110.

[0064] In the second process, the O-DU 110 obtains the O-RU delay characteristics from each O-RU 120. The O-DU 110 determines whether the O-RU 120 can be connected to the O-DU 110 for the O-RU 120 located closer to the air side than the O-DU 110 based on the O-RU delay characteristics and the O-DU window parameter. When the O-RU 120 cannot be connected to the O-DU 110, the O-DU 110 notifies the NMS 300 of a Failure. The Failure includes information for identifying the O-RU 120 that cannot be connected to the O-DU 110.

[0065] In the third process, the NMS 300 obtains the O-RU delay characteristics from each O-RU 120. The NMS 300 obtains the window parameters of the O-DU 110 from the O-DU 110. The NMS 300 determines whether the O-RU 120 and the O-DU 110 can be connected based on the O-RU delay characteristics and the window parameters for the O-RU 120 located closer to the air side than the O-DU 110. When the O-RU 120 and the O-DU 110 cannot be connected, the NMS 300 notifies the O-DU 110 of a Failure.

[0066] In addition, regarding the O-RU delay characteristics, the details of the window parameters and the determination method will be described later (see Figure 8 to Figure 11 ).

[0067] (4) Shared Cell Structure

[0068] In O-RAN, there is also a method of deploying a cell using multiple O-RUs. Research is underway on the structure of a device that bundles O-RUs (FHM: Fronthaul Multiplexing) and a structure that continuously connects O-RUs (cascade structure). These are collectively referred to as Shared Cells. In the network shown in Figure 4, such Shared Cells can be used.

[0069] Figure 4A to Figure 4C A structural example of the prequel is shown. Figure 4A This is an example of a cell consisting of 1O-RU. Figure 4B and Figure 4C An example of a Shared Cell structure is shown.

[0070] Specifically, Figure 4B A configuration example using the FHM 130 is shown. Figure 4C An example is shown in which the O-RU 130A is interposed between the O-DU 110 and the O-RU 120 to form a cascade connection.

[0071] exist Figure 4B In this case, the FHM 130 combines the two FH signals from each O-RU 120 and transmits them to the O-DU 110.

[0072] exist Figure 4C In this case, O-RU 130A combines the signal received by O-RU 130A (O-RU(1)) itself 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.

[0073] In the following description, the FHM 130 and the O-RU 130A are collectively referred to as the intermediate device 130. However, the intermediate device may be referred to by another name. The intermediate device 130 is provided at a position closer to the air side than the O-DU 110, and at a position closer to the RAN side than the O-RU 120.

[0074] As a feature of this Shared Cell structure, the intermediate device 130 forwards the DL signal received from the O-DU 110 to the O-RU 120 for the downlink (DL). In addition, in the case of a cascade connection of O-RUs, the intermediate device 130 can also send the DL signal of the O-RU itself.

[0075] In addition, for uplink (UL), the intermediate device 130 synthesizes UL signals received from the O-RU 120 and forwards them to the O-DU 110. In addition, in the case of cascade connection of O-RUs, wireless signals received by the O-RU itself are also synthesized.

[0076] According to this feature, the O-DU 110 can perform signal processing as in the case where one O-RU is connected.

[0077] (5) Functional block structure of wireless communication system

[0078] Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configuration of the NMS 300, the O-DU 110, and the O-RU 120 will be described.

[0079] (5.1)NMS 300

[0080] Figure 5 This is the functional block diagram of NMS 300. Figure 5 As shown, the NMS 300 includes a communication unit 310 , an acquisition unit 330 , a notification unit 350 , and a control unit 370 .

[0081] The communication unit 310 performs communication with the O-DU 110. The communication unit 310 may also perform communication with the O-RU 120. The communication unit 310 performs communication of parameters used for determining whether the O-RU 120 and the O-DU 110 can be connected.

[0082] The acquisition unit 330 acquires various parameters. For example, the acquisition unit 330 acquires the O-RU delay characteristics from the O-DU 110 in the first process described above. The acquisition unit 330 acquires the O-RU delay characteristics from the O-RU 120 in the third process described above. The acquisition unit 330 acquires the window parameter from the O-DU 110 in the first process and the third process described above.

[0083] The notification unit 350 notifies various parameters. For example, the notification unit 350 notifies the O-DU 110 of the above-mentioned Failure in the first process and the third process.

[0084] The control unit 370 controls the NMS 300. For example, in the first and third processes described above, the control unit 370 determines whether the O-RU 120 and the O-DU 110 can be connected based on the O-RU delay characteristics and the O-DU window parameter.

[0085] (5.2)O-DU 110

[0086] Figure 6is a functional block diagram of O-DU 110. Figure 6 As shown, the O-DU 110 includes a communication unit 111 , an acquisition unit 113 , a notification unit 115 , and a control unit 117 .

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

[0088] The acquisition unit 113 acquires various parameters. For example, the acquisition unit 113 acquires O-RU delay characteristics from the O-RU 120 in the first to third processes described above. The acquisition unit 113 acquires Failure from the NMS 300 in the first and third processes described above.

[0089] The notification unit 115 notifies various parameters. For example, in the first process described above, the notification unit 115 notifies the NMS 300 of the O-RU delay characteristics. In the first and third processes described above, the notification unit 115 notifies the NMS 300 of the O-DU window parameters. In the second process described above, the notification unit 115 notifies the NMS 300 of Failure.

[0090] The control unit 117 controls the O-DU 110. For example, in the second process described above, the control unit 117 determines whether the O-RU 120 can be connected to the O-DU 110 based on the O-RU delay characteristics and the O-DU window parameter.

[0091] (5.3)O-RU 120

[0092] Figure 7 is a functional block diagram of O-RU 120. Figure 7 As shown, the O-RU 120 includes a communication unit 121 , an acquisition unit 123 , a notification unit 125 , and a control unit 127 .

[0093] The communication unit 121 communicates with the O-DU 110. The communication unit 121 may also communicate with the NMS 300. For example, the communication unit 121 communicates signals of various planes as described above.

[0094] 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 process defined in Chapter 5 of ORAN-WG4.MP.0-v02.00 and the like.

[0095] The notification unit 125 notifies various parameters. In the first to third processes described above, the notification unit 125 notifies the O-DU 110 of the O-RU delay characteristics. In the third process described above, the notification unit 125 notifies the NMS 130 of the O-RU delay characteristics.

[0096] The control unit 127 controls the O-RU 120. For example, the control unit 127 sets at least one of a reception window and a transmission window.

[0097] (6) Window settings

[0098] First, refer to Figure 8 The UL signal is described.

[0099] like Figure 8 As shown, the transmission window (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 represented by the difference between Ta3_max and Ta3_min. The parameters (Ta3_min, Ta3_max) can be interpreted as the measurement results from the reception at the O-RU antenna to the output at the O-RU port (R3). Ta3_min and Ta3_max are examples of O-RU delay characteristics. Ta3_min and Ta3_max can be different for each O-RU 120.

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

[0101] Here, as the FH delay parameter, a parameter (T34_min) indicating the difference between Ta4_min and Ta3_min may be predefined. As the FH delay parameter, a parameter (T34_max) indicating the difference between Ta4_max and Ta3_max may also be predefined. The FH delay parameter is managed by the NMS 300. The FH delay parameter may be known by the O-DU 110 or may be notified to the O-DU 110 from 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 shared by the O-DU 110.

[0102] Under this premise, Ta4_min of the Reception window (UL) is defined to satisfy a condition that the value is less than Ta3_min+T34_min for the O-RU 120 located closer to the air side than the O-DU 110. Ta4_max of the Reception window (UL) is defined to satisfy a condition that the value is greater than Ta3_max+T34_max for the O-RU 120 located closer to the air side than the O-DU 110.

[0103] Here, Ta4_min, which can be set as a value defining the reception window (UL) of the O-DU 110, is referred to as minimum_capable_Ta4_min. Similarly, Ta4_max, which can be set as a value defining the reception window (UL) of the O-DU 110, is referred to as maximum_capable_Ta4_max. In addition, "capable" means that it can be set as the capability of the O-DU 110. "Maximum" may mean the maximum value that the value can take. "Minimum" may mean the minimum value that the value can take.

[0104] The NMS 300 may determine that, in the first and third procedures, the O-RU 120 that does not satisfy the condition (connection condition) that minimum_capable_Ta4_min is less than Ta3_min+T34_min and maximum_capable_Ta4_max is greater than Ta3_max+T34_max cannot be connected to the O-DU 110. Alternatively, the O-DU 110 may determine that, in the second procedure, the O-RU 120 that does not satisfy the connection condition cannot be connected to the O-DU 110. minimum_capable_Ta4_min and maximum_capable_Ta4_max are examples of the above-mentioned O-DU window parameters.

[0105] Second, refer to Fig. 9 The DL signal is described.

[0106] like Fig. 9 As shown, the transmission window (Transmission window (DL)) of O-DU 110 can be defined by parameters (T1a_min_up, T1a_max_up). Transmission window (DL) can be represented by the difference between T1a_max_up and T1a_min_up. Parameters (T1a_min_up, T1a_max_up) can be interpreted as the measurement results from the output at the O-DU port (R1) to the wireless transmission. Parameters (T1a_min_up, T1a_max_up) can be measured by the delay measurement message (Measured Transport Method).

[0107] On the other hand, the reception window (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 represented by the difference between T2a_max_up and T2a_min_up. The parameters (T2a_min_up, T2a_max_up) can be interpreted as the measurement results from the reception at the O-RU port (R2) to the wireless transmission. T2a_min_up and T2a_max_up are examples of O-RU delay characteristics. T2a_min_up and T2a_max_up can be different for each O-RU 120.

[0108] Here, as an FH delay parameter, a parameter (T12_min) indicating the difference between T1a_max_up and T2a_max_up may be predefined. As an FH delay parameter, a parameter (T12_max) indicating the difference between T1a_min_up and T2a_min_up may also be predefined. The FH delay parameter is managed by the NMS 300. The FH delay parameter may be known by the O-DU 110 or notified to the O-DU 110 from 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 shared by the O-DU 110.

[0109] Under this premise, T1a_min_up defining the transmission window (DL) may also satisfy a condition that the value is greater than T2a_min_up+T12_max for the O-RU 120 located closer to the air side than the O-DU 110. T1a_max_up defining the transmission window (DL) may also satisfy a condition that the value is less than T2a_max_up+T12_min for the O-RU 120 located closer to the air side than the O-DU 110.

[0110] Here, T1a_min_up that can be set as a value defining the Transmission window (DL) of the O-DU 110 is referred to as maximum_capable_T1a_min_up. Similarly, T1a_max_up that can be set as a value defining the Transmission window (DL) of the O-DU 110 is referred to as minimum_capable_T1a_max_up. In addition, "capable" means that it can be set as the capability of the O-DU 110. "Maximum" may mean the maximum value that the value can take. "Minimum" may mean the minimum value that the value can take.

[0111] The NMS 300 may determine that, in the first and third procedures, the O-RU 120 that does not satisfy the condition (connection condition) that maximum_capable_T1a_min_up is greater than or equal to T2a_min_up+T12_max and minimum_capable_T1a_max_up is less than or equal to T2a_max_up+T12_min cannot be connected to the O-DU 110. Alternatively, the O-DU 110 may determine that, in the second procedure, the O-RU 120 that does not satisfy the connection condition cannot be connected to the O-DU 110. maximum_capable_T1a_min_up and minimum_capable_T1a_max_up are examples of the above-mentioned O-DU window parameters.

[0112] In addition, "up" means U-Plane. Parameters related to the DL signal of C-Plane may include maximum_capable_T1a_min_cp_dl, minimum_capable_T1a_max_cp_dl, T2a_min_cp_dl, T2a_max_cp_dl, Tcp_adv_dl. In this case, "cp" means C-Plane. Maximum_capable_T1a_min_cp_dl can be expressed by maximum_capable_T1a_min_up+Tcp_adv_dl, and minimum_capable_T1a_max_cp_dl can be expressed by minimum_capable_T1a_max_up+Tcp_adv_dl. Likewise, T2a_min_cp_dl can be represented by T2a_min_up+Tcp_adv_dl, and T2a_max_cp_dl can be represented by T2a_max_up+Tcp_adv_dl.

[0113] Therefore, regarding the DL signal of C-Plane, T2a_min_cp_dl and T2a_max_cp_dl are examples of O-RU delay characteristics. Tcp_adv_dl can be a value determined according to each use case of O-RAN. Tcp_adv_dl can be an example of O-RU delay characteristics. maximum_capable_T1a_min_cp_dl and minimum_capable_T1a_max_cp_dl can be examples of O-DU window parameters.

[0114] (7) Parameters

[0115] First, the O-RU delay characteristics are explained.

[0116] like Fig.10 As shown, the O-RU delay characteristic (ro ru-delay-profile) may include T2a_min_up (rot2a-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.

[0117] In addition, although Figure 8 and Fig. 9 Although the description is omitted, the O-RU delay characteristics may also include parameters used in the UL signal of the C-plane (T2a_min_cp_ul (ro t2a-min-cp-ul), T2a_max_cp_ul (ro t2a-max-cp-ul)). T2a_min_cp_ul may be a value determined according to each use case of O-RAN. T2a_max_cp_ul may satisfy the condition of a value greater than T2a_min_cp_ul + (T12_max - T12_min) + O-DU Transmission Window.

[0118] Second, the O-DU window parameter is described. The O-DU window parameter can be replaced by a delay characteristic related to the O-DU 110 (O-DU delay characteristic).

[0119] like Fig.11 As shown, the O-DU window parameters may include maximum_capable_T1a_min_up, maximum_capable_T1a_max_up, maximum_capable_T1a_min_cp_dl, maximum_capable_T1a_max_cp_dl, minimum_capable_Ta4_min, maximum_capable_Ta4_max, etc.

[0120] In addition, although Figure 8 and Fig. 9Although the description is omitted, the O-DU window parameters may also include the parameters used in the UL signal of the C-plane (maximum_capable_T1a_min_cp_ul, maximum_capable_T1a_max_cp_ul. maximum_capable_T1a_min_cp_ul may satisfy the condition that the value is greater than T12_max+T2a_min_cp_ul. maximum_capable_T1a_max_cp_ul may satisfy the condition that the value is less than T12_min+T2a_max_cp_ul.

[0121] (8) Operation of wireless communication system

[0122] Next, the operation of the wireless communication system 10 will be described. Specifically, the first to third processes described above will be described. Figure 12 to Figure 14 Although omitted in FIG. 1 , more than two O-DUs 110 and more than two O-RUs 120 may be provided.

[0123] First, refer to Fig.12 The first process will be described.

[0124] like Fig.12 As shown, in step S10, the process of M-Plane connection establishment is performed between the NMS 300 and the O-DU 110. In step S11, the process of M-Plane connection establishment is performed between the O-DU 110 and the O-RU 120. The process of M-Plane connection establishment is a process for setting the M-Plane.

[0125] In step S12, the O-RU 120 sends the O-RU delay characteristics to the O-DU 110. For example, the O-RU delay characteristics include Fig.10 However, since the parameters related to the C-plane can be calculated by the O-DU 110, they may not be included in the O-RU delay characteristics.

[0126] In step S13, the O-DU 110 sends the O-RU delay characteristics to the NMS 300. For example, the O-RU delay characteristics include Fig.10However, since the parameters related to the C-plane can be calculated by the O-DU 110, they may not be included in the O-RU delay characteristics. In addition, the O-DU 110 sends the O-DU window parameters to the NMS 300. For example, the O-DU window parameters include Fig.11 However, since the parameters related to the C-plane can be calculated by the O-DU 110, they may not be included in the O-DU window parameters.

[0127] In step S14, the NMS 300 determines whether the O-RU 120 can be connected to the O-DU 110 based on the O-RU delay characteristics and the O-DU window parameters. In addition to the O-RU delay characteristics and the O-DU window parameters, the NMS 300 can also determine whether the O-RU 120 can be connected to the O-DU 110 based on the FH delay parameters. Specifically, the NMS 300 identifies the O-RU 120 that does not meet the above connection conditions (failure detection).

[0128] In step S15, the NMS 300 sends "Failure" to the O-DU 110. For example, Failure may include information for determining the O-RU 120 that does not meet the connection condition. The O-DU 110 that receives the Failure excludes the O-RU 120 that does not meet the connection condition, and continues the process for the O-RU 120 that meets the connection condition.

[0129] In step S16, a software management process is performed between the O-DU 110 and the O-RU 120. The software management process is a process for downloading, installing, and starting desired software through the O-RU 120 (refer to Chapter 5 of ORAN-WG4.MP.0-v02.00, etc.).

[0130] Second, refer to Fig.13 The second process is described.

[0131] like Fig.13 As shown, in step S20, similar to step S10, the process of M-Plane connection establishment is performed between NMS 300 and O-DU 110. In step S21, similar to step S11, the process of M-Plane connection establishment is performed between O-DU 110 and O-RU 120.

[0132] In step S22 , similar to step S12 , the O-RU 120 sends the O-RU delay characteristics to the O-DU 110 .

[0133] In step S23, the O-DU 110 determines whether the O-RU 120 can be connected to the O-DU 110 according to the O-RU delay characteristics and the O-DU window parameters. In addition to the O-RU delay characteristics and the O-DU window parameters, the O-DU 110 can also determine whether the O-RU 120 can be connected to the O-DU 110 according to the FH delay parameters. Specifically, the O-DU 110 determines the O-RU 120 that does not meet the connection conditions (Failure detection). The O-DU 110 excludes the O-RU 120 that does not meet the connection conditions, and continues the process for the O-RU 120 that meets the connection conditions.

[0134] In step S24, the O-DU 110 sends "Failure" to the NMS 300. Failure may include information determining that the O-RU 120 does not satisfy the connection condition.

[0135] In step S25 , similarly to step S16 , a software management process is performed between the O-DU 110 and the O-RU 120 .

[0136] Third, refer to Fig.14 The third process is described.

[0137] like Fig.14 As shown, in step S30, similar to step S10, the process of M-Plane connection establishment is performed between NMS 300 and O-DU 110. In step S31, similar to step S11, the process of M-Plane connection establishment is performed between O-DU 110 and O-RU 120.

[0138] In step S32 , similar to step S12 , the O-RU 120 sends the O-RU delay characteristics to the O-DU 110 .

[0139] In step S33, the O-RU 120 sends the O-RU delay characteristics to the NMS 300. For example, the O-RU delay characteristics include Fig.10 However, since the parameters related to the C-plane can be calculated by the O-DU 110, they may not be included in the O-RU delay characteristics.

[0140] In step S34, similar to step S14, the NMS 300 determines whether the O-RU 120 can be connected to the O-DU 110 based on the O-RU delay characteristics and the O-DU window parameters. In addition to the O-RU delay characteristics and the O-DU window parameters, the NMS 300 can also determine whether the O-RU 120 can be connected to the O-DU 110 based on the FH delay parameter.

[0141] In step S35, similar to step S15, the NMS 300 sends "Failure" to the O-DU 110. The O-DU 110 that receives the Failure excludes the O-RUs 120 that do not satisfy the connection condition, and continues the process for the O-RUs 120 that satisfy the connection condition.

[0142] In step S36 , similarly to step S16 , a software management process is performed between the O-DU 110 and the O-RU 120 .

[0143] (9) Function / Effect

[0144] In the embodiment, the NMS 300 determines whether the O-RU 120 can be connected to the O-DU 110 based on the O-RU delay characteristics and the O-DU window parameters (the first process or the third process). According to this structure, when the O-DU 110 and the O-RU 120 are provided by different vendors or operators, the NMS 300 can re-estimate the site location of the O-RU 120 by understanding the defects of the FH, and can appropriately manage the delay of the FH.

[0145] In the embodiment, when the O-DU 110 cannot connect the O-RU 120 with the O-DU 110, the O-DU 110 notifies the NMS 300 that the O-RU 120 cannot connect with the O-DU 110 (Failure). According to this structure, when the O-DU 110 and the O-RU 120 are provided by different vendors or operators, the NMS 300 can re-estimate the site location of the O-RU 120 by understanding the defect of the FH, and can appropriately perform delay management of the FH.

[0146] [Other embodiments]

[0147] As mentioned above, although the content of this invention was demonstrated based on an Example, this invention is not limited to these descriptions, and it is obvious to a person skilled in the art that various deformation|transformation and improvement are possible.

[0148] In an embodiment, the O-DU window parameter includes a parameter that can be set as a capability of the O-DU 110. However, the embodiment is not limited thereto. Specifically, the O-DU window parameter may be a parameter currently set in the O-DU 110. That is, whether the O-RU 120 can be connected to the O-DU 110 can be determined based on the parameter currently set in the O-DU 110. In other words, when a Failure is detected, there may be room for changing the sending window or receiving window (hereinafter collectively referred to as a window) used in the O-DU 110.

[0149] In the embodiment, the case where the O-RU 120 that does not satisfy the connection condition is excluded and the process is continued for the O-RU 120 that satisfies the connection condition is illustrated. However, the embodiment is not limited to this. Specifically, in the case where the sending window or the receiving window (hereinafter collectively referred to as the window) used in the O-DU 110 can be changed, the window can be changed within the range that does not exceed the capability of the O-DU 110. For example, in the above-mentioned first process or third process, the NMS 300 can send a window change indication to the O-DU 110 together with the sending of the Failure, and the NMS 300 can also send a window change indication to the O-DU 110 instead of sending the Failure. Alternatively, in the above-mentioned second process, the O-DU 110 can change the window so that the O-RU 110 that does not satisfy the connection condition satisfies the connection condition.

[0150] The block diagram used in the description of the above-mentioned embodiment ( Figures 5 to 7 ) shows blocks in units of functions. These functional blocks (structural parts) are implemented by any combination of at least one of hardware and software. In addition, there is no particular limitation on the implementation method of each functional block. That is, each functional block can be implemented using a device that is physically or logically combined, or two or more physically or logically separated devices can be directly or indirectly connected (for example, using wires, wirelessly, etc.) and implemented using these multiple devices. The functional block can also be implemented by combining software with the above-mentioned one device or the above-mentioned multiple devices.

[0151] Functions include, but are not limited to, judging, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. For example, a functional block (structural part) that enables the sending function is called a transmitting unit or a transmitter. In short, as mentioned above, there is no particular limitation on the implementation method.

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

[0153] In the following description, the word "device" may be replaced by "circuit", "device", "unit", etc. The hardware structure of the device may include one or more of the devices shown in the figure, or may exclude some of the devices.

[0154] Each functional block of the device (refer to Figure 5 , 6 ) is implemented by any hardware element or combination of hardware elements of the computer device.

[0155] In addition, each function in the device is implemented by the following method: predetermined software (program) is read into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of the reading and writing of data in memory 1002 and storage 1003.

[0156] The processor 1001 controls the entire computer by, for example, executing an operating system. The processor 1001 may be constituted by a central processing unit (CPU) including an interface with peripheral devices, a control device, a calculation device, a register, and the like.

[0157] In addition, the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the memory 1003 and the communication device 1004 to the memory 1002, and performs various processes accordingly. As a program, a program that causes a computer to perform at least a part of the actions described in the above-mentioned embodiments is used. In addition, with respect to the above-mentioned various processes, although it is described that the above-mentioned various processes are performed by one processor 1001, the above-mentioned various processes can also be performed simultaneously or sequentially by more than two processors 1001. The processor 1001 can also be installed by more than one chip. In addition, the program can also be sent from the network via a telecommunication line.

[0158] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (main storage device), etc. The memory 1002 may store a program (program code), a software module, etc. that can execute a method according to an embodiment of the present disclosure.

[0159] The memory 1003 is a computer-readable recording medium, and may be composed of at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a floppy disk, a magneto-optical disk (e.g., a compressed 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, etc. The memory 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, and other appropriate media that includes at least one of the memory 1002 and the memory 1003.

[0160] The communication device 1004 is hardware (transceiver) used to communicate between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, etc.

[0161] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., for example, in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0162] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that implements output to the outside (e.g., a display, a speaker, an LED light, etc.). In addition, the input device 1005 and the output device 1006 may also be integrally formed (e.g., a touch panel).

[0163] In addition, the processor 1001 and the memory 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or may be configured using different buses for each device.

[0164] 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), and the like, and a part or all of each functional block may be implemented by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0165] In addition, the notification of information is not limited to the form / implementation method described in the present disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., downlink control information (DCI: Downlink Control Information), uplink control information (UCI: Uplink Control Information), high-layer signaling (e.g., RRC signaling, medium access control (MAC: Medium Access Control) signaling, broadcast information (Master Information Block (MIB: Master Information Block), System Information Block (SIB: System Information Block)), other signals or a combination thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, it may also be an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message, etc.

[0166] Each form / embodiment described in the present disclosure may also be applied to at least one of 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), CDMA 2000, 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), systems using other appropriate systems, and next-generation systems extended therefrom. In addition, a combination of a plurality of systems (for example, a combination of at least one of LTE and LTE-A with 5G, etc.) may be applied.

[0167] The processing procedures, timings, processes, etc. of each form / implementation described in this disclosure may be changed in order without contradiction. For example, for the method described in this disclosure, the elements of various steps are presented in an illustrative order, but are not limited to the specific order presented.

[0168] In the present disclosure, specific actions performed by a base station are sometimes performed by its upper node depending on the situation. In a network consisting of one or more network nodes having a base station, various actions performed to communicate with a terminal can be performed by at least one of the base station and other network nodes other than the base station (for example, consider MME or S-GW, etc., but not limited to these). In the above, the case where there is one other network node other than the base station is illustrated, but the other network node may also be a combination of multiple other network nodes (for example, MME and S-GW).

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

[0170] The input or output information can be stored in a specific location (e.g., memory) or managed using a management table. The input or output information can be rewritten, updated, or appended. The output information can also be deleted. The input information can also be sent to other devices.

[0171] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparison of numerical values ​​(for example, comparison with a predetermined value).

[0172] Each form / implementation described in the present disclosure may be used alone or in combination, and may be switched according to execution. In addition, notification of scheduled information is not limited to being performed explicitly (e.g., notification of "yes X"), but may also be performed implicitly (e.g., notification of the scheduled information is not performed).

[0173] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be interpreted broadly to refer to commands, sets of commands, codes, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0174] In addition, software, commands, information, etc. may be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[0175] The information, signals, etc. described in the present disclosure may also be represented by any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc. that may be involved in the above description as a whole may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0176] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may also be a signal (signaling). In addition, a signal may also be a message. In addition, a component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, etc.

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

[0178] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources may also be indicated by indexes.

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

[0180] In the present disclosure, the terms "base station (BS)", "wireless 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" and the like are used interchangeably. Sometimes, the base station is also referred to as macro cell, small cell, femto cell, pico cell and the like.

[0181] A base station can accommodate one or more (for example, 3) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station for indoor use (Remote Radio Head: RRH).

[0182] The terms "cell" or "sector" refer to a part or the entirety of a coverage area of ​​at least one of a base station and a base station subsystem that provide communication services within the coverage area.

[0183] In the present disclosure, terms such as “mobile station (MS)”, “user terminal (user terminal)”, “user equipment (UE)”, and “terminal” may be used interchangeably.

[0184] For mobile stations, those skilled in the art sometimes also use the following terms: 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 appropriate terms.

[0185] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. In addition, at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a means of transportation (e.g., a car, an airplane, etc.), a mobile body that moves in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. 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.

[0186] In addition, the base station in the present disclosure may also be replaced by a mobile station (user terminal, the same below). For example, various forms / implementations of the present disclosure may also be applied to a structure in which the communication between a base station and a mobile station is replaced by the communication between multiple mobile stations (for example, may also be referred to as D2D (Device-to-Device), Vehicle-to-Everything (V2X), etc. In this case, it may also be set as a structure in which the mobile station has the functions of the base station. In addition, terms such as "uplink" and "downlink" may also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, an uplink channel, a downlink channel, etc. may also be replaced by a side channel.

[0187] Likewise, the mobile station in the present disclosure may be replaced by a base station. In this case, the base station may have the same functions as the mobile station.

[0188] A radio frame may be composed of one or more frames in the time domain. In the time domain, one or more frames may be referred to as subframes.

[0189] A subframe may consist of one or more time slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) that is independent of numerology.

[0190] A parameter set may be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. The parameter set may, for example, represent at least one of a subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, a wireless frame structure, a specific filtering process performed by a transceiver in the frequency domain, a specific windowing process performed by a transceiver in the time domain, and the like.

[0191] A slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. A slot may be a time unit based on a parameter set.

[0192] A time slot may contain multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may be composed of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in units of time greater than a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type B.

[0193] A radio frame, a subframe, a time slot, a mini-time slot, and a symbol all represent time units for transmitting signals. A radio frame, a subframe, a time slot, a mini-time slot, and a symbol may be referred to by other corresponding names.

[0194] For example, 1 subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, and 1 time slot or 1 mini time slot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1ms) in the existing LTE, or a period shorter than 1ms (for example, 1-13 code elements), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but may be called a time slot, a mini time slot, etc.

[0195] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules the allocation of wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) to each user terminal in units of TTI. In addition, the definition of TTI is not limited to this.

[0196] TTI can be a transmission time unit for data packets (transport blocks), code blocks, code words, etc. after channel coding, and can also be a processing unit for scheduling, link adaptation, etc. In addition, when TTI is given, the time interval (e.g., the number of symbols) to which the transport block, code block, code word, etc. is actually mapped can be shorter than the TTI.

[0197] In addition, when 1 time slot or 1 mini time slot is called TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can constitute the minimum time unit of scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit of scheduling can be controlled.

[0198] A TTI having a time length of 1 ms is also 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 time 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 mini-time slot, a sub-time slot, a time slot, etc.

[0199] In addition, for a long TTI (for example, a normal TTI, a subframe, etc.), it can be replaced with a TTI having a time length exceeding 1ms, and for a short TTI (for example, a shortened TTI, etc.), it can be replaced with a TTI length that is smaller than the long TTI (longTTI) and has a TTI length of more than 1ms.

[0200] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain. In the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers contained in an RB may be the same regardless of the parameter set, for example, it may be 12. The number of subcarriers contained in an RB may also be determined according to the parameter set.

[0201] In addition, the time domain of an RB may include one or more symbols, and may be the length of 1 slot, 1 mini slot, 1 subframe, or 1 TTI. 1 TTI, 1 subframe, etc. may be composed of one or more resource blocks, respectively.

[0202] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, and the like.

[0203] In addition, a resource block may be composed of one or more resource elements (RE). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

[0204] A Bandwidth Part (BWP) (also called a partial bandwidth, etc.) represents a subset of contiguous common RBs (common resource blocks) for a parameter set in a certain carrier. Here, the common RBs can be identified by the index of the RB based on the common reference point of the carrier. PRBs can be defined in a BWP and numbered within the BWP.

[0205] 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.

[0206] At least one of the set BWPs may be active, and it is not assumed that the UE transmits or receives a predetermined signal / channel outside the activated BWP. In addition, "cell", "carrier" and the like in the present disclosure may be replaced with "BWP".

[0207] The above structures of radio frames, subframes, time slots, mini-time slots, and symbols are only examples. For example, the number of subframes included in a radio frame, the number of time slots per subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP: Cyclic Prefix) length, and the like can be changed in various ways.

[0208] The terms "connected", "coupled" or all variations of these terms are intended to indicate any direct or indirect connection or combination between two or more elements, and may include the situation where there is one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be a physical combination or connection, a logical combination or connection, or a combination of these. For example, "access" may be used to replace "connection". In the context of the present disclosure, for two elements, it may be considered that they are "connected" or "coupled" to each other by using at least one of one or more wires, cables, and printed electrical connections, and as some non-limiting and non-inclusive examples, by using electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible) region, etc.

[0209] The reference signal may be referred to as Reference Signal (RS) for short, or may be referred to as a pilot signal depending on the applied standard.

[0210] The phrase "according to" used in the present disclosure does not mean "only according to" unless otherwise expressly stated. In other words, the phrase "according to" means both "only according to" and "at least according to".

[0211] The “unit” in the configuration of each of the above-mentioned devices may be replaced with a “section”, “circuit”, “device” or the like.

[0212] Any reference to an element using the designations "first," "second," etc., used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, a reference to a first and a second element does not mean that only two elements can be used here or that the first element must precede the second element in any form.

[0213] When the terms "include," "including," and variations thereof are used in the present disclosure, these terms are intended to be inclusive, as is the term "comprising." Furthermore, the term "or" used in the present disclosure does not mean an exclusive or.

[0214] In the present disclosure, when an article is added by translation, such as a, an, and the in English, for example, the present disclosure may also include a case where the noun following the article is in a plural form.

[0215] The terms "determining" and "determining" used in the present disclosure sometimes also include a variety of actions. "Judgment" and "determination" may include, for example, considering matters that have been judged, calculated, calculated, processed, derived, investigated, searched (for example, searched in a table, database or other data structure), confirmed (ascertaining) as matters that have been "judged" or "determined", etc. In addition, "judgment" and "determination" may include matters that have been received (for example, receiving information), transmitted (for example, sending information), input, output, accessed (for example, accessing data in memory) as matters that have been "judged" or "determined", etc. In addition, "judgment" and "determination" may include matters that have been resolved (resolving), selected (selecting), chosen (choosing), established (establishing), compared (comparing), etc. as matters that have been "judged" or "determined". That is, "judgment" and "decision" can include matters of "judgment" and "decision" of any action. In addition, "judgment (decision)" can also be replaced by "assuming (assuming)", "expecting (expecting)", "considering (considering)" and the like.

[0216] In the present disclosure, the term "A and B are different" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same way as "different".

[0217] The present disclosure is described in detail above, but it should be 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 as a modification and variation without departing from the subject matter and scope of the present disclosure as determined by the claims. Therefore, the purpose of the description of the present disclosure is to illustrate and not to have any limiting meaning on the present disclosure.

[0218] Description of symbols

[0219] 10: Wireless communication system;

[0220] 20: NG-RAN;

[0221] 100: gNB;

[0222] 110: O-DU;

[0223] 111: Ministry of Communications;

[0224] 113: Acquisition Department;

[0225] 115: Notification Department;

[0226] 117: Control Department;

[0227] 120: O-RU;

[0228] 121: Ministry of Communications;

[0229] 123: Acquisition Department;

[0230] 125: Notification Department;

[0231] 127: Control Department;

[0232] 130: intermediate device (FHM);

[0233] 130A: O-RU;

[0234] 200:UE;

[0235] 300: NMS;

[0236] 310: Ministry of Communications;

[0237] 330: Acquisition Department;

[0238] 350: Notification Department;

[0239] 370: Control Department;

[0240] 1001: processor;

[0241] 1002: Memory;

[0242] 1003: memory;

[0243] 1004: Communication device;

[0244] 1005: input device;

[0245] 1006: output device;

[0246] 1007: Bus.

Claims

1. A communication device, wherein: The communication device constitutes a management node that manages at least one of the distributed unit O-DU and the radio unit O-RU provided on the fronthaul. The communication device comprises: an acquisition unit, which acquires a window parameter of the distributed unit O-DU from the distributed unit O-DU, and acquires a delay characteristic of the radio unit O-RU; and A control unit determines whether the radio unit O-RU can be connected to the distributed unit O-DU based on a window parameter of the distributed unit O-DU and a delay characteristic of the radio unit O-RU.

2. A communication device, wherein: The communication device constitutes a distributed unit O-DU that performs communication with the radio unit O-RU on the fronthaul, The communication device includes a notification unit configured to notify a management node that manages at least one of the distributed unit O-DU and the radio unit O-RU of a window parameter of the distributed unit O-DU. The window parameter of the distributed unit O-DU is used together with the delay characteristic of the radio unit O-RU to determine whether the radio unit O-RU can be connected to the distributed unit O-DU.

3. The communication device according to claim 1 or 2, wherein: The delay characteristic of the radio unit O-RU is notified to the management node from at least either one of the distributed unit O-DU and the radio unit O-RU.

4. A communication device, wherein: The communication device constitutes a distributed unit O-DU that performs communication with the radio unit O-RU on the fronthaul, The communication device comprises: an acquisition unit that acquires a delay characteristic of the radio unit O-RU from the radio unit O-RU; a control unit, which determines whether the radio unit O-RU can be connected to the distributed unit O-DU according to the window parameter of the distributed unit O-DU and the delay characteristic of the radio unit O-RU; and A notification unit, which, when the wireless unit O-RU cannot be connected to the distributed unit O-DU, notifies a management node that manages at least one of the distributed unit O-DU and the wireless unit O-RU that the wireless unit O-RU cannot be connected to the distributed unit O-DU.

Images