Wireless communication node

Abstract

This wireless communication node (100B) sets the number of first symbols used for dynamically adjusting the transmission timing when performing uplink transmission on a first wireless link connected to an upper node, and notifies the upper node of the set number.

Description

[Technical field]

[0001] The present disclosure relates to a wireless communication node for configuring wireless access and wireless backhaul. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has established specifications for Long Term Evolution (LTE), and is also establishing specifications for successor systems to LTE, such as LTE-Advanced (hereinafter, LTE-Advanced will be referred to as LTE) with the aim of further increasing speeds, as well as 5G New Radio (NR) or Next Generation (NG).

[0003] For example, in the NR radio access network (RAN), Integrated Access and Backhaul (IAB) is being considered, which integrates wireless access to terminals (User Equipment, UE) and wireless backhaul between wireless communication nodes such as radio base stations (gNBs) (see Non-Patent Document 1).

[0004] In the IAB, an IAB node has a Mobile Termination (MT), which is a function for connecting to a parent node (which may be called an IAB donor), and a Distributed Unit (DU), which is a function for connecting to a child node or UE.

[0005] In 3GPP Release 16, half-duplex and time division multiplexing (TDM) are assumed for wireless access and wireless backhaul. In addition, in 3GPP Release 17, the application of frequency division multiplexing (FDM), space division multiplexing (SDM) and full-duplex is considered. In other words, in 3GPP Release 17, simultaneous operation of MT and DU is considered.

[0006] In Non-Patent Document 1, seven cases are specified regarding the alignment of transmission timing between a parent node and an IAB node. Specifically, Non-Patent Document 1 specifies, for example, the alignment of the transmission timing of the downlink (DL) between the IAB node and the IAB donor (Case #1), the alignment of the transmission timing of the DL and the uplink (UL) in the IAB node (Case #2), the alignment of the reception timing of the DL and the uplink (UL) in the IAB node (Case #3), the combination of the alignment of the transmission timing of the DL in Case #1 and the UL in Case #2 (Case #6), and the combination of the alignment of the transmission timing of the DL in Case #1 and the reception timing of the UL in Case #3 (Case #7).

[0007] In 3GPP Release 16, a proposal is made to avoid contention caused by a difference between the transmission timing and reception timing of an MT of an IAB node and the transmission timing and reception timing of a DU of the IAB node. Specifically, in 3GPP Release 16, a proposal is made to introduce a guard symbol into the transition portion between the transmission timing and reception timing of an MT of an IAB node and the transmission timing and reception timing of a DU of the IAB node. [Prior art documents] [Non-patent literature]

[0008] [Non-Patent Document 1] 3GPP TR 38.874 V16.0.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhaul; (Release 16), 3GPP, December 2018 Summary of the Invention

[0009] Here, as a method for realizing simultaneous operation of an MT and a DU in an IAB node, for example, a configuration that dynamically switches between two or more of the above seven cases is being considered.

[0010] In the above configuration, in order to avoid the above-mentioned contention, it is considered necessary to notify the number of guard symbols set in accordance with the above-mentioned multiple cases, for example.

[0011] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a wireless communication node that can reliably perform the timing adjustments necessary to achieve simultaneous operation of MT and DU.

[0012] One aspect of the present disclosure is a wireless communication node (wireless communication node 100B) that includes a control unit (control unit 190) that sets a first number of symbols used to dynamically adjust transmission timing when transmitting in the uplink direction in a first wireless link connecting to an upper node, and a transmission unit (wireless transmission unit 161) that notifies the upper node of the first number of symbols. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. As shown in FIG. [Diagram 2] FIG. 2 is a diagram showing an example of a basic configuration of the IAB. [Diagram 3] FIG. 3 is a functional block diagram of the wireless communication node 100A. [Figure 4] FIG. 4 is a functional block diagram of the wireless communication node 100B. [Diagram 5] FIG. 5 is a diagram showing the configuration of a MAC-CE defined in Release 16 of 3GPP. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of an Enhanced MAC-CE in operation example 1-3-1. [Figure 7]FIG. 7 is a diagram illustrating an example of the configuration of an Enhanced MAC-CE in operation example 1-3-1. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of an Enhanced MAC-CE in operation example 1-3-1. [Figure 9] FIG. 9 is a diagram illustrating an example of the configuration of an Enhanced MAC-CE in the operation example 1-3-2. [Figure 10] FIG. 10 is a diagram illustrating an example of the configuration of an Enhanced MAC-CE in the operation example 1-3-2. [Figure 11] FIG. 11 is a diagram illustrating an example of the configuration of an Enhanced MAC-CE in the operation example 1-3-2. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of an Enhanced MAC-CE in operation example 1-3-3. [Figure 13] FIG. 13 is a diagram for explaining the fourth operation example. [Figure 14] FIG. 14 is a diagram illustrating an example of a hardware configuration of the CU 50, the wireless communication nodes 100A to 100C, and the UE 200. As shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0015] (1) Overall configuration of wireless communication system 1 is a schematic diagram of an overall configuration of a wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and is composed of a plurality of wireless communication nodes and terminals.

[0016] Specifically, the wireless communication system 10 includes wireless communication nodes 100A, 100B, 100C, and a user equipment 200 (hereinafter, referred to as UE 200).

[0017] The wireless communication nodes 100A, 100B, and 100C can set up wireless access with the UE 200 and a wireless backhaul (BH) between the wireless communication nodes. Specifically, a backhaul (transmission path) by a wireless link is set between the wireless communication node 100A and the wireless communication node 100B, and between the wireless communication node 100A and the wireless communication node 100C.

[0018] Such a configuration in which the wireless access to the UE 200 and the wireless backhaul between the wireless communication nodes are integrated is called Integrated Access and Backhaul (IAB).

[0019] The IAB reuses existing functions and interfaces defined for radio access, in particular Mobile-Termination (MT), gNB-DU (Distributed Unit), gNB-CU (Central Unit), User Plane Function (UPF), Access and Mobility Management Function (AMF) and Session Management Function (SMF), as well as the corresponding interfaces, e.g. NR Uu (MT to gNB / DU), F1, NG, X2 and N4, are used as the baseline.

[0020] The wireless communication node 100A is connected to an NR radio access network (NG-RAN) and a core network (Next Generation Core (NGC) or 5GC) via a wired transmission path such as fiber transport. The NG-RAN / NGC includes a Central Unit 50 (hereinafter, CU50), which is a communication node. The NG-RAN and NGC may be simply referred to as a "network."

[0021] The CU 50 may be configured by any one or a combination of the UPF, AMF, and SMF described above, or may be a gNB-CU as described above.

[0022] Fig. 2 is a diagram showing a basic configuration example of an IAB. As shown in Fig. 2, in this embodiment, the wireless communication node 100A constitutes a parent node in the IAB, and the wireless communication node 100B (and the wireless communication node 100C) constitutes an IAB node in the IAB.

[0023] In addition, the parent node may be called a higher-level node in relation to the IAB node. In addition, the parent node may be called an IAB donor. In addition, the IAB node may be called a lower-level node in relation to the parent node.

[0024] A child node in the IAB is configured by another wireless communication node not shown in Fig. 1. Alternatively, the UE 200 may configure the child node. The IAB node may be called a higher-level node in relation to the child node, and the child node may be called a lower-level node in relation to the IAB node.

[0025] A wireless link is set between the parent node and the IAB node. Specifically, a wireless link called Link_parent is set.

[0026] A wireless link is set between the IAB node and the child node. Specifically, a wireless link called Link_child is set.

[0027] Such a wireless link established between wireless communication nodes is called a wireless backhaul link. Link_parent is composed of a DL Parent BH in the downlink direction and a UL Parent BH in the uplink direction. Link_child is composed of a DL Child BH in the downlink direction and a UL Child BH in the uplink direction.

[0028] The radio link established between the UE 200 and the IAB node or the parent node is called a radio access link. Specifically, the radio link is configured by a DL Access in the downlink direction and a UL Access in the uplink direction.

[0029] An IAB node has a Mobile Termination (MT) that is a function for connecting to a parent node, and a Distributed Unit (DU) that is a function for connecting to a child node (or UE 200). Although omitted in FIG. 2, the parent node and the child node also have an MT and a DU.

[0030] From the DU's point of view, the radio resources used by the DU, including the downlink (DL), uplink (UL) and flexible time-resource (D / U / F), are classified into one of the types: hardware, software or not available (H / S / NA). Also, within the software (S), available or not available is specified.

[0031] Although the IAB configuration example shown in Fig. 2 uses CU / DU division, the IAB configuration is not necessarily limited to this configuration. For example, the IAB may be configured by tunneling using GPRS Tunneling Protocol (GTP)-U / User Datagram Protocol (UDP) / Internet Protocol (IP) in the wireless backhaul.

[0032] The main advantage of such an IAB is that it allows flexible and dense deployment of NR cells without densifying the transport network. IAB can be applied to various scenarios, such as outdoor small cell deployment, indoor, and even mobile relay (e.g., in buses and trains).

[0033] The IAB may also support NR-only standalone (SA) deployments, as shown in Figures 1 and 2, or non-standalone (NSA) deployments that include other RATs (such as LTE).

[0034] In this embodiment, the wireless access and wireless backhaul operate on the premise of half-duplex communication. However, this is not necessarily limited to half-duplex communication, and full-duplex communication may be used as long as the requirements are met.

[0035] Additionally, time division multiplexing (TDM), space division multiplexing (SDM) and frequency division multiplexing (FDM) are available as multiplexing methods.

[0036] When an IAB node operates in half-duplex communication, the DL Parent BH is the receiving (RX) side, the UL Parent BH is the transmitting (TX) side, the DL Child BH is the transmitting (TX) side, and the UL Child BH is the receiving (RX) side. In addition, in the case of Time Division Duplex (TDD), the DL / UL setting pattern in an IAB node is not limited to DL-F-UL only, and setting patterns such as UL-F-DL only and wireless backhaul (BH) only may be applied.

[0037] In addition, in this embodiment, SDM / FDM is used to realize simultaneous operation of the DU and MT of the IAB node.

[0038] (2) Functional block configuration of wireless communication system Next, a description will be given of a functional block configuration of the wireless communication node 100A and the wireless communication node 100B that configure the wireless communication system 10. Note that in this disclosure, each of the seven cases (Case #1 to Case #7) defined in 3GPP TR 38.874 may be referred to as a timing mode or a timing adjustment method.

[0039] (2.1) Wireless communication node 100A 3 is a functional block diagram of a wireless communication node 100A constituting a parent node. As shown in FIG. 3, the wireless communication node 100A includes a wireless transmitting unit 110, a wireless receiving unit 120, a NW IF unit 130, an IAB node connecting unit 140, and a control unit 150.

[0040] The wireless transmission unit 110 transmits a wireless signal conforming to the 5G specification. The wireless reception unit 120 receives the wireless signal conforming to the 5G specification. In this embodiment, the wireless transmission unit 110 and the wireless reception unit 120 perform wireless communication with the wireless communication node 100B constituting the IAB node.

[0041] In this embodiment, the wireless communication node 100A has the functions of MT and DU, and the wireless transmitting unit 110 and the wireless receiving unit 120 also transmit and receive wireless signals in accordance with MT / DU.

[0042] The NW IF unit 130 provides a communication interface that realizes a connection with the NGC side, etc. For example, the NW IF unit 130 can include interfaces such as X2, Xn, N2, and N3.

[0043] The IAB node connection unit 140 provides an interface that realizes a connection with an IAB node (or a child node including a UE). Specifically, the IAB node connection unit 140 provides a function of a Distributed Unit (DU). That is, the IAB node connection unit 140 is used for a connection with an IAB node (or a child node).

[0044] The IAB node may be expressed as a RAN node that supports wireless access for the UE 200 and wirelessly backhauls access traffic, and the parent node, i.e., the IAB donor, may be expressed as a RAN node that provides an interface for the UE to the core network and wireless backhaul functionality to the IAB node.

[0045] The control unit 150 executes control of each functional block constituting the wireless communication node 100A. In particular, in this embodiment, the control unit 150 controls DL and UL transmission timing, and UL reception timing. Specifically, the control unit 150 can adjust DL transmission timing and UL transmission timing in a lower node, for example, the wireless communication node 100B (IAB node). The control unit 150 can also adjust UL reception timing in the wireless communication node 100B (IAB node).

[0046] The adjustment of the DL transmission timing of each wireless communication node including the wireless communication node 100A may correspond to Case #1 defined in 3GPP TR 38.874.

[0047] Also, the adjustment of DL and UL transmission timings in the IAB node may correspond to Case #2 in the same case. Furthermore, the adjustment of DL and UL reception timings in the IAB node may correspond to Case #3 in the same case.

[0048] In addition, the adjustment in the IAB node may include adjustment of DL transmission timing in the IAB node, and DL and UL transmission timing may be adjusted within the IAB node.

[0049] That is, the control unit 150 can support Case #6, which is a combination of adjustment of transmission timing between DL in Case #1 and UL in Case #2.

[0050] Furthermore, the adjustment at the IAB node may include adjusting DL transmit timing at the IAB node, and DL and UL receive timing may be adjusted within the IAB node.

[0051] That is, the control unit 150 can support Case #7, which is a combination of the DL transmission timing adjustment of Case #1 and the UL reception timing adjustment of Case #3.

[0052] The control unit 150 can dynamically switch between three timing modes, Case #1, Case #6, and Case #7, based on the number of guard symbols notified from the wireless communication node 100B.

[0053] (2.2) Wireless communication node 100B 4 is a functional block diagram of a wireless communication node 100B constituting an IAB node. As shown in FIG. 4, the wireless communication node 100B includes a wireless transmitting unit 161, a wireless receiving unit 162, a higher-level node connecting unit 170, a lower-level node connecting unit 180, and a control unit 190.

[0054] Thus, the wireless communication node 100B has similar functional blocks to the wireless communication node 100A (parent node) described above, but differs in that it has an upper node connection unit 170 and a lower node connection unit 180, and in the functions of the control unit 190.

[0055] The wireless transmission unit 161 transmits a wireless signal conforming to the 5G specifications. The wireless reception unit 162 receives a wireless signal conforming to the 5G specifications. In this embodiment, the wireless transmission unit 161 and the wireless reception unit 162 perform wireless communication with the wireless communication node 100A constituting a parent node, and wireless communication with a child node (including the case of the UE 200).

[0056] The wireless transmitting unit 161 can notify the upper node (parent node) of the number of guard symbols (first number of symbols) set by the control unit 190 to enable simultaneous operation of the upper node connection unit 170 and the lower node connection unit 180.

[0057] The wireless transmitting unit 161 can notify the lower node (child node) of the number of guard symbols (second number of symbols) set by the control unit 190 to enable simultaneous operation of the upper node connection unit 170 and the lower node connection unit 180.

[0058] In notifying the number of guard symbols, the MAC-CE (MAC-Control Element) of Release 16 may be used, or an enhanced MAC-CE (specific examples will be described later) which is an extension of the MAC-CE may be used.

[0059] For example, the MAC-CE of Release 16 has a configuration as shown in Fig. 5. In Fig. 5, "R" represents reserved bits, "SCS" represents subcarrier spacing, and "NmbGS i " (i=1 to 8) represents the number of guard symbols corresponding to each of the eight switching scenarios defined in 3GPP TR 38.821 V16.0.0. The number of guard symbols may be set within the range of 0 to 4, for example.

[0060] The guard symbols are provided to avoid contention caused by a difference between the transmission timing and reception timing of the MT of the IAB node and the transmission timing and reception timing of the DU of the IAB node. Therefore, the number of guard symbols may be set according to, for example, the propagation delay of the wireless backhaul link and the wireless access link, the capability of the IAB node, the timing mode, etc. In addition, the IAB node needs to avoid the above contention.

[0061] The above eight switching scenarios include four scenarios that indicate switching from MT operation to DU operation and four scenarios that indicate switching from DU operation to MT operation between each wireless communication node (upper node, IAB node, and lower node) that constitutes the IAB.

[0062] Switching from MT to DU operation includes switching from DL RX to DL TX, switching from DL RX to UL RX, switching from UL TX to DL TX, and switching from UL TX to UL RX.

[0063] In the four scenarios showing switching from MT operation to DU operation, the number of guard symbols indicated in "NmbGS1" is set when switching from DL RX to DL TX, the number of guard symbols indicated in "NmbGS2" is set when switching from DL RX to UL RX, the number of guard symbols indicated in "NmbGS3" is set when switching from UL TX to DL TX, and the number of guard symbols indicated in "NmbGS4" is set when switching from UL TX to UL RX.

[0064] Switching from DU to MT operation includes switching from DL TX to DL RX, switching from UL RX to DL RX, switching from DL TX to UL TX, and switching from UL RX to UL TX.

[0065] In the four scenarios showing switching from DU operation to MT operation, the number of guard symbols indicated in "NmbGS5" is set when switching from DL TX to DL RX, the number of guard symbols indicated in "NmbGS6" is set when switching from UL RX to DL RX, the number of guard symbols indicated in "NmbGS7" is set when switching from DL TX to UL TX, and the number of guard symbols indicated in "NmbGS8" is set when switching from UL RX to UL TX.

[0066] The radio receiving unit 162 receives downlink control information (DCI) from an upper node. Specifically, the radio receiving unit 162 can receive DCI indicating which timing mode among Case #1, Case #6, and Case #7 has been used to adjust the timing in the upper node.

[0067] The wireless receiver 162 receives uplink control information (UCI) from a lower node. Specifically, the wireless receiver 162 can receive UCI indicating which timing mode among Case #1, Case #6, and Case #7 has been used to adjust the timing in the lower node.

[0068] The upper node connection unit 170 provides an interface for realizing a connection with a node higher than the IAB node. Note that the higher node means a wireless communication node located on the network side, specifically, on the core network side (which may be called the upstream side or uplink side), higher than the IAB node.

[0069] Specifically, the upper node connection unit 170 provides a function of Mobile Termination (MT). That is, in this embodiment, the upper node connection unit 170 is used for connection to a parent node that constitutes an upper node.

[0070] The lower node connection unit 180 provides an interface for realizing a connection with a node lower than the IAB node. Note that the lower node means a wireless communication node located on the end user side (which may be called the downstream side or downlink side) of the IAB node.

[0071] Specifically, the lower node connection unit 180 provides a function of a distributed unit (DU). That is, in this embodiment, the lower node connection unit 180 is used for connection to a child node (which may be the UE 200) constituting a lower node.

[0072] The control unit 190 executes control of each functional block constituting the wireless communication node 100B. In particular, in this embodiment, the control unit 190 controls DL and UL transmission timings and UL reception timings. Specifically, the control unit 190 can adjust DL transmission timings and UL transmission timings in lower nodes, for example, child nodes including UEs. The control unit 190 can also adjust UL reception timings in child nodes.

[0073] The adjustment of the DL transmission timing of each wireless communication node including the wireless communication node 100B may correspond to Case #1 defined in 3GPP TR 38.874.

[0074] Moreover, the adjustment of DL and UL transmission timings in a lower node may correspond to Case #2 in the same case. Furthermore, the adjustment of DL and UL reception timings in a lower node may correspond to Case #3 in the same case.

[0075] In addition, the adjustment in the lower node may include adjustment of DL transmission timing in the lower node, and DL and UL transmission timing may be adjusted within the lower node.

[0076] That is, the control unit 190 can support Case #6, which is a combination of adjustment of transmission timing between DL in Case #1 and UL in Case #2.

[0077] Furthermore, the adjustment at the lower node may include adjusting the DL transmit timing at the lower node, and the DL and UL receive timing may be adjusted within the lower node.

[0078] That is, the control unit 190 can support Case #7, which is a combination of the DL transmission timing adjustment of Case #1 and the UL reception timing adjustment of Case #3.

[0079] When a timing adjustment according to Case #7 is performed at an upper node based on information contained in the DCI received by the radio receiving unit 162, the control unit 190 can perform operations related to a timing mode of Case #7a in which the transmission timing of UL TX is adjusted in accordance with the timing adjustment.

[0080] When a timing adjustment according to Case #6 is performed in a lower node based on information contained in the UCI received by the radio receiving unit 162, the control unit 190 can perform operations related to a timing mode of Case #6a in which the UL RX reception timing is adjusted in accordance with the timing adjustment.

[0081] The control unit 190 can adjust the transmission timing of UL TX while dynamically switching between three timing modes, Case #1, Case #6, and Case #7a, based on information contained in the DCI received by the radio receiving unit 162.

[0082] The control unit 190 can adjust the UL RX reception timing while dynamically switching between three timing modes, Case #1, Case #6a, and Case #7, based on information contained in the UCI received by the wireless receiving unit 162.

[0083] The control unit 190 can set the number of guard symbols every time the timing mode is switched.

[0084] That is, the IAB node (wireless communication node 100B) can set the number of guard symbols (first number of symbols) used to dynamically adjust the transmission timing when performing uplink transmission (UL TX) in a first wireless link (Link_parent) connecting to an upper node (wireless communication node 100A) and can notify the upper node of the number of guard symbols. Also, the IAB node (wireless communication node 100B) can set the number of guard symbols (second number of symbols) used to dynamically adjust the reception timing when performing uplink reception (UL RX) in a second wireless link (Link_child) connecting to a lower node (child node) and can notify the lower node of the number of guard symbols.

[0085] In this embodiment, even in nodes (child nodes) lower than the wireless communication node 100B (IAB node), the three timing modes of Case #1, Case #6, and Case #7 are supported, and the three timing modes can be dynamically switched.

[0086] (3) Operation of wireless communication system Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation related to the adjustment of the transmission timing and reception timing of DL and UL in the case where simultaneous operation (simultaneous Tx / Rx) of the DU and MT of the IAB node is realized.

[0087] More specifically, this section describes the operation related to adjusting the transmission timing and reception timing of DL and UL to enable the DU and MT of an IAB node to operate simultaneously when the parent node and child node that constitute the IAB support the three timing modes of Case #1, Case #6, and Case #7 specified in 3GPP TR 38.874.

[0088] In this embodiment, since it is necessary to guarantee DL transmission timing adjustment between each wireless communication node constituting the IAB, it is assumed that the UL RX reception timing and the DL TX transmission timing do not change even in different timing modes.

[0089] (3.1) General operation Based on the information contained in the DCI transmitted from the wireless communication node 100A, the wireless communication node 100B (IAB node) selects one of the three timing modes, Case #1, Case #6, and Case #7a, and adjusts the transmission timing and reception timing according to the selected timing mode.

[0090] The wireless communication node 100B (IAB node) sets the number of guard symbols according to one timing mode selected based on the information contained in the DCI, and notifies the wireless communication node 100A (parent node) of the set number of guard symbols via MAC-CE.

[0091] The wireless communication node 100B (IAB node) selects one of three timing modes, Case #1, Case #6a, and Case #7, based on the information contained in the UCI transmitted from the lower node, and adjusts the transmission timing and reception timing according to the selected timing mode.

[0092] The radio communication node 100B sets the number of guard symbols according to one timing mode selected based on the information included in the UCI, and notifies the lower node of the set number of guard symbols by MAC-CE.

[0093] (3.2) Example of operation Next, the operation of the IAB node with regard to setting and notifying the number of guard symbols will be described.

[0094] (3.2.2) Example 1 In this operation example, it is only necessary to set the number of guard symbols when switching between MT and DU, assuming that different timing modes (for example, Case #1, Case #6, and Case #7) are set in Link_parent.

[0095] (3.2.2.1) Operation example 1-1 In this operation example, the number of guard symbols may be notified to the wireless communication node 100A while utilizing the MAC-CE of Release 16. Also, in this operation example, the same number of guard symbols may be used in a plurality of timing modes. Also, in this operation example, the number of guard symbols according to any of the following may be notified by the MAC-CE.

[0096] (Alt.1) The number of guard symbols depends on the implementation of the three timing modes: Case #1, Case #6 and Case #7a.

[0097] (Alt.2) The minimum number of guard symbols set in the three timing modes, Case #1, Case #6 and Case #7a.

[0098] (Alt.3) The maximum number of guard symbols set in the three timing modes, Case #1, Case #6 and Case #7a.

[0099] (3.2.2.2) Operation example 1-2 In this operation example, the number of guard symbols may be notified to the wireless communication node 100A while utilizing the MAC-CE of Release 16. Also, in this operation example, different numbers of guard symbols may be used in a plurality of timing modes. Also, in this operation example, the wireless communication node 100A may calculate the number of guard symbols in each timing mode using the notification of the MAC-CE. Note that, in calculating the number of guard symbols in this operation example, for example, a value of TA (Timing Advance) in each timing mode may be used.

[0100] (3.2.2.2.1) Operation example 1-2-1 The number of guard symbols in UL TX in Case #1 may be set to a number according to the transmission timing of UL TX in Case #1, and may be notified to the wireless communication node 100A by the MAC-CE.

[0101] The number of guard symbols in Case #6 is set (calculated) based on the number of guard symbols set according to the transmission timing of UL TX in Case #1 and the difference between the TA (Timing Advance) of UL TX in Case #6 and the TA (Timing Advance) of UL TX in Case #1, and is notified to the wireless communication node 100A by the MAC-CE.

[0102] The number of guard symbols in Case #7a is set (calculated) based on the number of guard symbols set according to the transmission timing of UL TX in Case #1 and the difference between the TA (Timing Advance) of UL TX in Case #7a and the TA (Timing Advance) of UL TX in Case #1, and is notified to the wireless communication node 100A by the MAC-CE.

[0103] (3.2.2.2.2) Operation example 1-2-2 The number of guard symbols in UL TX in Case #6 may be set to a number according to the transmission timing of UL TX in Case #6, and may be notified to the wireless communication node 100A by the MAC-CE.

[0104] The number of guard symbols in Case #1 is set (calculated) based on the number of guard symbols set according to the transmission timing of UL TX in Case #6 and the difference between the TA (Timing Advance) of UL TX in Case #1 and the TA (Timing Advance) of UL TX in Case #6, and is notified to the wireless communication node 100A by the MAC-CE.

[0105] The number of guard symbols in Case #7a is set (calculated) based on the number of guard symbols set according to the transmission timing of UL TX in Case #6 and the difference between the TA (Timing Advance) of UL TX in Case #7a and the TA (Timing Advance) of UL TX in Case #6, and is notified to the wireless communication node 100A by the MAC-CE.

[0106] (3.2.2.2.3) Operation example 1-2-3 The number of guard symbols in UL TX in Case #7a may be set to a number according to the transmission timing of UL TX in Case #7a, and may be notified to the wireless communication node 100A by the MAC-CE.

[0107] The number of guard symbols in Case #1 is set (calculated) based on the number of guard symbols set according to the transmission timing of UL TX in Case #7a and the difference between the TA (Timing Advance) of UL TX in Case #1 and the TA (Timing Advance) of UL TX in Case #7a, and is notified to the wireless communication node 100A by the MAC-CE.

[0108] The number of guard symbols in Case #6 is set (calculated) based on the number of guard symbols set according to the transmission timing of UL TX in Case #7a and the difference between the TA (Timing Advance) of UL TX in Case #6 and the TA (Timing Advance) of UL TX in Case #7a, and is notified to the wireless communication node 100A by the MAC-CE.

[0109] (3.2.2.3) Operation example 1-3 In this operation example, the number of guard symbols may be notified to the wireless communication node 100A while using Enhanced MAC-CE, which is an extension of MAC-CE in Release 16. Also, in this operation example, different numbers of guard symbols may be used in a plurality of timing modes. Also, in this operation example, the wireless communication node 100A may calculate the number of guard symbols in each timing mode using the notification of Enhanced MAC-CE. Note that, in calculating the number of guard symbols in this operation example, for example, a value of TA (Timing Advance) in each timing mode may be used.

[0110] (3.2.2.3.1) Operation example 1-3-1 The Enhanced MAC-CE in this operation example may include an index corresponding to a particular switching scenario, an indication of one or more timing modes, and one or more fields indicating the number of guard symbols corresponding to the one or more timing modes.

[0111] Specifically, the Enhanced MAC-CE in this operation example may have a configuration as shown in FIG. 6 or FIG.

[0112] The Enhanced MAC-CE shown in Fig. 6 shows a configuration example in which an instruction for one timing mode is included. In addition, in Fig. 6, "R" represents a reserved bit, "SCS" represents a subcarrier interval, "Switching scenario" represents an index corresponding to a specific switching scenario, "Timing mode" represents an instruction for one timing mode, and "NmbGS" represents a field indicating the number of guard symbols corresponding to the one timing mode.

[0113] The "Switching scenario" in Fig. 6 is not limited to being represented by 3 bits, but may be represented by other numbers of bits. Also, the "Timing mode" in Fig. 6 is not limited to being represented by 2 bits, but may be represented by other numbers of bits.

[0114] The Enhanced MAC-CE shown in Fig. 7 shows a configuration example in which one or more timing mode instructions are included. In addition, in Fig. 7, "SCS" represents a subcarrier interval, "Switching scenario" represents one index corresponding to a specific switching scenario, "T0" represents the presence or absence of an instruction for the timing mode of Case #1, "T1" represents the presence or absence of an instruction for the timing mode of Case #6, "T2" represents the presence or absence of an instruction for the timing mode of Case #7a, and "NmbGS" represents one or more fields indicating the number of guard symbols corresponding to one or more timing modes.

[0115] According to the Enhanced MAC-CE shown in FIG. 7, for example, when a switching scenario corresponding to switching from DL RX to UL RX is set and “T0” is set to “1”, the number of guard symbols used to adjust the reception timing of UL RX corresponding to the timing mode of Case #1 is represented by one field of “NmbGS”.

[0116] According to the Enhanced MAC-CE shown in FIG. 7, for example, when a switching scenario corresponding to switching from DL RX to UL RX is set and “T1” is set to “1”, the number of guard symbols used to adjust the transmission timing of UL TX corresponding to the timing mode of Case #6 is represented by one field of “NmbGS”.

[0117] In the Enhanced MAC-CE shown in FIG. 7, "NmbGS" corresponding to the timing mode set to "0" among "T0", "T1", and "T2" is not included.

[0118] The "Switching scenario" in Fig. 7 is not limited to being represented by 3 bits, but may be represented by other numbers of bits. Also, the "Timing mode" in Fig. 7 is not limited to being represented by 3 bits, but may be represented by other numbers of bits.

[0119] According to this operation example, for example, a bitmap including p (p≧2) Enhanced MAC-CEs having the configuration as shown in FIG. 6 or FIG. 7 can be used to notify the number of guard symbols according to the timing mode in each of the p switching scenarios.

[0120] Furthermore, according to this operation example, when the Enhanced MAC-CE includes "NmbGS" for all timing modes supported by the wireless communication node 100B, the timing mode indication by "Timing mode" can be omitted, for example, as shown in FIG. 8.

[0121] The Enhanced MAC-CE shown in Fig. 8 includes "R", "SCS", and "Switching scenario" similar to those in Fig. 6. In addition, the Enhanced MAC-CE shown in Fig. 8 includes three "NmbGS" fields corresponding to the three timing modes supported by the wireless communication node 100B.

[0122] In other words, if the total number of timing modes supported by the wireless communication node 100B is n, the timing mode indication by "Timing mode" can be omitted by setting n "NmbGS" fields in the Enhanced MAC-CE.

[0123] (3.2.2.3.2) Operation example 1-3-2 The Enhanced MAC-CE in this operation example may include one index corresponding to a particular timing mode, an indication of one or more switching scenarios, and one or more fields indicating the number of guard symbols corresponding to the one or more switching scenarios.

[0124] Specifically, the Enhanced MAC-CE in this operation example may have a configuration as shown in FIG. 9 or FIG.

[0125] The Enhanced MAC-CE shown in Fig. 9 shows a configuration example in which an instruction for one switching scenario is included. In Fig. 9, "R" represents a reserved bit, "SCS" represents a subcarrier interval, "Timing mode" represents an index corresponding to a specific timing mode, "Switching scenario" represents an instruction for one switching scenario, and "NmbGS" represents a field indicating the number of guard symbols corresponding to the one switching scenario.

[0126] The "Switching scenario" in Fig. 9 is not limited to being represented by 3 bits, but may be represented by another number of bits. Also, the "Timing mode" in Fig. 8 is not limited to being represented by 2 bits, but may be represented by another number of bits.

[0127] The Enhanced MAC-CE shown in Fig. 10 shows a configuration example in which one or more switching scenario instructions are included. In Fig. 10, "SCS" represents the subcarrier interval, "Timing mode" represents one index corresponding to a specific timing mode, "S0" to "S7" represent the presence or absence of an instruction for each of eight switching scenarios, and "NmbGS" represents one or more fields indicating the number of guard symbols corresponding to one or more switching scenarios.

[0128] According to the Enhanced MAC-CE shown in FIG. 10, for example, when “S0” is set to “1”, the number of guard symbols used in switching from DL RX to DL TX is represented by one field of “NmbGS”.

[0129] According to the Enhanced MAC-CE shown in FIG. 10, for example, when “S1” is set to “1”, the number of guard symbols used in switching from DL RX to UL TX is represented by one field of “NmbGS”.

[0130] In the Enhanced MAC-CE shown in FIG. 10, "NmbGS" corresponding to the timing mode set to "0" among "S0" to "S7" is not included.

[0131] The "Switching scenario" in Fig. 10 is not limited to being expressed by 8 bits, but may be expressed by another number of bits. Also, the "Timing mode" in Fig. 10 is not limited to being expressed by 2 bits, but may be expressed by another number of bits.

[0132] According to this operation example, for example, a bitmap including q (q≧2) Enhanced MAC-CEs having a configuration as shown in FIG. 9 or FIG. 10 can be used to notify the number of guard symbols according to a switching scenario in each of the q timing modes.

[0133] Furthermore, according to this operation example, when the Enhanced MAC-CE includes "NmbGS" for all switching scenarios supported by the wireless communication node 100B, the instruction of the switching scenario by "Switching scenario" can be omitted, for example, as shown in FIG. 11.

[0134] The Enhanced MAC-CE shown in Fig. 11 includes "R", "SCS", and "Switching scenario" similar to those in Fig. 9. Also, the Enhanced MAC-CE shown in Fig. 10 includes eight "NmbGS" fields corresponding to the eight switching scenarios supported by the wireless communication node 100B.

[0135] In other words, if the total number of switching scenarios supported by the wireless communication node 100B is m, the instruction of the switching scenario by "Switching scenario" can be omitted by setting m "NmbGS" fields in the Enhanced MAC-CE.

[0136] (3.2.2.3.3) Operation example 1-3-3 The Enhanced MAC-CE in this operation example may include the number of guard symbols for all switching scenarios corresponding to all timing modes supported by the wireless communication nodes 100A, 100B, and 100C.

[0137] Specifically, in the Enhanced MAC-CE of this operation example, for example, as shown in FIG. 12, eight "NmbGS" fields corresponding to eight types of switching scenarios are provided for each timing mode.

[0138] The Enhanced MAC-CE shown in Fig. 12 shows a configuration example in which the number of guard symbols corresponding to each of eight switching scenarios in the first timing mode and the number of guard symbols corresponding to each of eight switching scenarios in the second timing mode are notified. In Fig. 12, "R" represents a reserved bit, and "SCS" represents a subcarrier spacing.

[0139] (3.2.3) Example 2 In this operation example, it is only necessary to set the number of guard symbols when switching between MT and DU, assuming that different timing modes (for example, Case #1, Case #6, and Case #7) are set in Link_parent and Link_child.

[0140] (3.2.3.1) Operation example 2-1 In this operation example, the number of guard symbols is notified to the child node while using Enhanced MAC-CE having the configuration as exemplified in Operation Example 1-3. Also, in this operation example, the number of guard symbols of Link_child is set based on the number of guard symbols of Link_parent set according to Operation Example 1-2.

[0141] Specifically, the number of guard symbols in one timing mode (among Case #1, Case #6, and Case #7a) used to adjust the transmission timing of UL TX is used as a reference, and the number of guard symbols in each timing mode (Case #1, Case #6a, and Case #7) used to adjust the reception timing of UL RX is set.

[0142] (3.2.3.1.1) Operation example 2-1-1 The number of guard symbols in each timing mode used to adjust the reception timing of UL RX is set based on the number of guard symbols of UL TX in Case #1 calculated in a manner similar to that of Operation Example 1-2-1, and is notified to the child node by a MAC-CE having a configuration as exemplified in Operation Example 1-3.

[0143] According to this operation example, the number of guard symbols of UL TX in Case #6 and Case #7a may be calculated in the same manner as in operation example 1-2-1.

[0144] (3.2.3.1.2) Operation example 2-1-2 The number of guard symbols in each timing mode used to adjust the reception timing of UL RX is set based on the number of guard symbols of UL TX in Case #6 calculated in a manner similar to that of Operation Example 1-2-2, and is notified to the child node by a MAC-CE having a configuration as exemplified in Operation Example 1-3.

[0145] According to this operation example, the number of guard symbols of UL TX in Case #1 and Case #7a may be calculated in the same manner as in operation example 1-2-2.

[0146] (3.2.3.1.3) Operation example 2-1-3 The number of guard symbols in each timing mode used to adjust the reception timing of UL RX is set based on the number of guard symbols of UL TX in Case #7a calculated in a manner similar to that of Operation Example 1-2-3, and is notified to the child node by a MAC-CE having a configuration as exemplified in Operation Example 1-3.

[0147] According to this operation example, the number of guard symbols of UL TX in Case #1 and Case #6 may be calculated in the same manner as in operation example 1-2-3.

[0148] (3.2.3.2) Example 2-2 In this operation example, the number of guard symbols may be notified to a child node while using an Enhanced MAC-CE having a configuration as exemplified in operation example 1-3. Also, in this operation example, the number of guard symbols of Link_child may be set according to the number of guard symbols of Link_parent set according to operation example 1-3.

[0149] Specifically, the number of guard symbols in each timing mode (Case #1, Case #6a, and Case #7) used to adjust the reception timing of UL RX may be set according to the number of guard symbols in all timing modes (Case #1, Case #6, and Case #7a) used to adjust the transmission timing of UL TX. In this operation example, the Enhanced MAC-CE having the configuration as exemplified in Operation Example 1-3 may indicate a combination of the number of guard symbols in all timing modes (Case #1, Case #6, and Case #7a) used to adjust the transmission timing of UL TX and the number of guard symbols in all timing modes (Case #1, Case #6a, and Case #7) used to adjust the reception timing of UL RX.

[0150] (3.2.4) Example 3 In this operation example, the timing mode supported by the IAB node and / or the child node may be notified to the parent node.

[0151] Specifically, in this operation example, for example, the timing mode of UL TX supported in the IAB node may be notified to the parent node by the MAC-CE of Release 16 or the Enhanced MAC-CE described above. That is, in this operation example, the wireless communication node 100B may notify the wireless communication node 100A of the timing adjustment methods (Case #1, Case #6, and Case #7a) available for dynamically adjusting the transmission timing of UL TX.

[0152] Also, in this operation example, for example, the timing mode of UL RX supported in the IAB node may be notified to the parent node by the MAC-CE of Release 16 or the Enhanced MAC-CE described above. That is, in this operation example, the wireless communication node 100B may notify the wireless communication node 100A of the timing adjustment methods (Case #1, Case #6a, and Case #7) available for dynamically adjusting the reception timing of UL RX.

[0153] In addition, in this operation example, for example, the UL TX timing mode supported in the child node may be notified to the parent node by the Release 16 MAC-CE or the above-mentioned Enhanced MAC-CE.

[0154] (3.2.5) Example 4 In this operation example, different numbers of guard symbols may be used in a plurality of timing modes. Also, in this operation example, the numbers of guard symbols may be set according to the timing mode in Link_parent and the timing mode in Link_child.

[0155] Specifically, for example, when transitioning from operation related to UL RX in the DU to operation related to UL TX in the MT as shown in FIG. 13, the number of guard symbols may be set to be equal to the sum of the number of guard symbols for UL TX in Case #1 and the number of guard symbols for UL RX in Case #7.

[0156] (4) Actions and Effects According to the above-described embodiment, the following advantageous effects can be obtained.

[0157] The IAB node (wireless communication node 100B) can set a first symbol number used to dynamically adjust transmission timing when performing uplink transmission (UL TX) in a first wireless link (Link_parent) connecting with an upper node (wireless communication node 100A) and notify the upper node of the first symbol number. Therefore, the IAB node can reliably perform timing adjustment required to realize simultaneous operation of MT and DU when performing wireless communication with the parent node.

[0158] In addition, the IAB node (wireless communication node 100B) can set a second symbol number used to dynamically adjust reception timing when performing uplink reception (UL RX) in a second wireless link (Link_child) connecting with a lower node (child node) and notify the lower node of the second symbol number. Therefore, the IAB node can reliably perform timing adjustment required to realize simultaneous operation of MT and DU when performing wireless communication with a child node.

[0159] In addition, the IAB node (wireless communication node 100B) can notify the upper node (wireless communication node 100A) of the timing adjustment methods (Case #1, Case #6, and Case #7a) that can be used to dynamically adjust the transmission timing when performing uplink transmission (UL TX) in the first wireless link (Link_parent). Therefore, the IAB node can reliably perform the timing adjustment required to realize simultaneous operation of MT and DU when performing wireless communication with the parent node.

[0160] In addition, the IAB node (wireless communication node 100B) can notify the upper node (wireless communication node 100A) of the timing adjustment methods (Case #1, Case #6a, and Case #7) that can be used to dynamically adjust the reception timing when performing uplink reception (UL RX) in the second wireless link (Link_child). Therefore, the IAB node can reliably perform the timing adjustment required to realize simultaneous operation of MT and DU when performing wireless communication with the parent node.

[0161] In addition, the IAB node (wireless communication node 100B) can set different numbers of guard symbols in a plurality of timing adjustment methods available for dynamically adjusting transmission timing when performing uplink transmission (UL TX) in the first wireless link (Link_parent). Therefore, the IAB node can reliably and flexibly perform timing adjustment required to realize simultaneous operation of MT and DU when performing wireless communication with the parent node.

[0162] (5) Other embodiments Although the embodiment has been described above, it will be apparent to those skilled in the art that the present invention is not limited to the description of the embodiment and that various modifications and improvements are possible.

[0163] In the above-described embodiments, the number of symbols (number of guard symbols) may be replaced with terms such as, for example, a symbol period, a symbol time, a number of slots, a slot period, a guard time, a protection time, and a prohibition time.

[0164] In the above-described embodiment, the wireless communication node 100A (IAB donor) may be configured to include a CU and one or more DUs. In addition, when a CP (Control Plane) and a UP (User Plane) are separated in a gNB-CU, the IAB donor may be configured to include a CU-CP, multiple CU-UPs, and multiple DUs.

[0165] For example, in the above-described embodiment, the names of parent node, IAB node, and child node are used, but as long as a wireless communication node configuration in which a wireless backhaul between wireless communication nodes such as gNBs and wireless access to terminals are integrated is adopted, the names may be different. For example, they may be simply called a first node, a second node, or the like, or may be called an upper node, a lower node, a relay node, an intermediate node, or the like.

[0166] Furthermore, the wireless communication node may simply be called a communication device or a communication node, and may be read as a wireless base station.

[0167] In the above-described embodiment, the terms downlink (DL) and uplink (UL) are used, but other terms may be used. For example, they may be replaced with or correspond to terms such as forward link, reverse link, access link, and backhaul. Alternatively, terms such as first link, second link, first direction, and second direction may simply be used.

[0168] Moreover, the block diagrams (FIGS. 3 and 4) 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. Furthermore, 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 blocks may be realized by combining the one device or the multiple devices with software.

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

[0170] Furthermore, the above-mentioned CU 50, the wireless communication nodes 100A to 100C, and the UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 14 is a diagram showing an example of a hardware configuration of the devices. As shown in Fig. 14, the devices 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, and a bus 1007.

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

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

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

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

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

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

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

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

[0179] 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).

[0180] 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).

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

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

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

[0184] Each aspect / embodiment described in the present disclosure may be implemented in accordance with Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5 th The present invention may be applied to at least one of a system using a next-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), or other suitable system, and a next-generation system extended based on these. In addition, a combination of a plurality of systems (for example, a combination of at least one of LTE and LTE-A and 5G) may be applied.

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

[0186] 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).

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

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

[0189] 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).

[0190] 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).

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

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

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

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

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

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

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

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

[0199] 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)).

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

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

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

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

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

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

[0206] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called 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.

[0207] 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 the transceiver performs in the frequency domain, a particular windowing operation that the transceiver performs in the time domain, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0223] 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".

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

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

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

[0227] 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."

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

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

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

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

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

[0233] 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."

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

[0235] 10. Wireless communication systems 50 CU 100A, 100B, 100C wireless communication nodes 110 Radio transmitter 120 Radio receiver 130 NW IF Section 140 IAB Node Connection 150 Control section 161 Radio transmitter 162 Radio receiving unit 170 Upper node connection part 180 Lower Node Connection 190 Control section 200UE 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device 1007 Bus

Claims

1. A wireless communication node, comprising: a control unit that sets different numbers of guard symbols in a first adjustment method for adjusting a transmission timing of a downlink between an upper node and the wireless communication node and in a second adjustment method for adjusting the transmission timing of the downlink and also the transmission timing or the reception timing of an uplink; a transmission unit that notifies the upper node or the lower node of the set number of guard symbols; A wireless communication node comprising:

2. 2. A wireless communication node according to claim 1, The control unit sets the number of guard symbols in a transition between a first function for connecting to the higher-level node and a second function for connecting to the lower-level node.

3. A wireless communication node as claimed in claim 1, The transmitting unit notifies the number of guard symbols using a control element of Medium Access Control (MAC).

4. A wireless communication method in a wireless communication node, comprising: setting different numbers of guard symbols in a first adjustment method for adjusting a transmission timing of a downlink between an upper node and the wireless communication node and in a second adjustment method for adjusting the transmission timing of the downlink and also the transmission timing or reception timing of an uplink; notifying the upper node or the lower node of the set number of guard symbols; A wireless communication method comprising:

Images