Communication control method and relay device

The communication control method and relay device address backhaul link failures by re-establishing links and verifying donor device compatibility, ensuring secure and efficient data transfer in mobile communication systems.

JP7581297B2Active Publication Date: 2024-11-12KYOCERA CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2022161243
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-08-07
Filing Date
2022-10-05
Publication Date
2024-11-12
Estimated Expiration
2040-08-07

AI Technical Summary

Technical Problem

Existing mobile communication systems face challenges in effectively managing and recovering from failures in backhaul links within relay devices, which disrupt data transmission paths and require efficient re-establishment of communication routes.

Method used

A communication control method and relay device that re-establishes backhaul links by determining whether a new higher-level device is managed by the same donor device, allowing for the appropriate handling of buffered data and ensuring secure data transfer by verifying donor device compatibility.

Benefits of technology

Enables robust handling of backhaul link failures by ensuring secure and efficient data transfer by verifying donor device compatibility, thereby maintaining communication integrity and reducing data loss.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007581297000001
    Figure 0007581297000001
  • Figure 0007581297000002
    Figure 0007581297000002
  • Figure 0007581297000003
    Figure 0007581297000003
Patent Text Reader

Abstract

In a system in which an upstream path is formed between a user device and a first donor device using a plurality of relay devices, a communication control method and a relay device are provided which are executed in a relay device included in the plurality of relay devices when a failure occurs in a backhaul link established between the relay device and a first higher-level device. [Solution] A communication control method transfers data received from a lower-level device lower than a relay device on an upstream path to a first higher-level device higher than the relay device, buffers data that has not yet been sent to the first higher-level device, and, if a failure occurs in the backhaul link established between the relay device and the first higher-level device, re-establishes the backhaul link of the relay device with a second higher-level device, and determines whether to transfer the buffered data to the second higher-level device based on whether a second donor device managing the second higher-level device is the same as the first donor device.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a communication control method and a relay device used in a mobile communication system. [Background technology]

[0002] In the 3GPP (3rd Generation Partnership Project) (registered trademark, hereinafter the same), a standardization project for mobile communication systems, a new relay device called an IAB (Integrated Access and Backhaul) node is being considered. One or more relay devices are intervening in communication between a base station, which is a donor device, and a user device, and relay this communication.

[0003] Such a relay device has a user equipment function and a base station function, and performs wireless communication with a higher-level device (a base station or a higher-level relay device) using the user equipment function, and performs wireless communication with a lower-level device (a user equipment or a lower-level relay device) using the base station function.

[0004] A wireless section between a user device and a relay device or a base station may be called an access link. A wireless section between a relay device and a base station or another relay device may be called a backhaul link. Non-Patent Document 1 describes a method for dynamically switching a data transfer path by integrating and multiplexing data communication of an access link and data communication of a backhaul link in layer 2 and dynamically allocating wireless resources to the backhaul link. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP contribution “RP-182894” Summary of the Invention

[0006] A communication control method according to a first aspect is a method executed by a relay device included in a plurality of relay devices in a mobile communication system in which an upstream path is formed between a user device and a first donor device using the plurality of relay devices. The communication control method includes forwarding data received from a lower-level device lower than the relay device in the upstream path to a first higher-level device upper than the relay device, buffering data not yet transmitted to the first higher-level device, re-establishing the backhaul link of the relay device with a second higher-level device when a failure occurs in a backhaul link established between the relay device and the first higher-level device, and determining whether to forward the buffered data to the second higher-level device based on whether a second donor device managing the second higher-level device is the same as the first donor device.

[0007] A relay device according to a second aspect is a relay device included in a plurality of relay devices in a mobile communication system in which an upstream path is formed between a user device and a first donor device using a plurality of relay devices. The relay device includes a control unit that executes a process of forwarding data received from a lower-level device lower than the relay device in the upstream path to a first higher-level device higher than the relay device, a process of buffering data not yet transmitted to the first higher-level device, a process of re-establishing the backhaul link of the relay device with a second higher-level device when a failure occurs in a backhaul link established between the relay device and the first higher-level device, and a process of determining whether to forward the buffered data to the second higher-level device based on whether a second donor device that manages the second higher-level device is the same as the first donor device. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram showing a configuration of a mobile communication system according to an embodiment; [Diagram 2] FIG. 2 is a diagram illustrating a configuration of a base station according to an embodiment. [Diagram 3] FIG. 2 is a diagram illustrating a configuration of a relay device according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating a configuration of a user device according to an embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of a protocol stack configuration according to an embodiment. [Figure 6] FIG. 2 is a diagram illustrating an operation scenario of a mobile communication system according to an embodiment. [Figure 7] FIG. 11 is a flow diagram illustrating an example of an operation of a relay device according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] In a situation where an upstream path using multiple relay devices is formed between a user device and a first donor device, if a failure occurs in a backhaul link established between the relay device and its higher-level device (first higher-level device), it may be necessary to re-form the upstream path by re-establishing the backhaul link of the relay device with the second higher-level device.

[0010] Therefore, an object of the present disclosure is to provide a communication control method and a relay device that can appropriately deal with a failure in a backhaul link.

[0011] A mobile communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0012] (Configuration of a mobile communication system) First, a configuration of a mobile communication system according to an embodiment will be described. Fig. 1 is a diagram showing a configuration of a mobile communication system 1 according to an embodiment. The mobile communication system 1 is a fifth generation (5G) mobile communication system based on the 3GPP standard. Specifically, the radio access method in the mobile communication system 1 is NR (New Radio), which is a 5G radio access method. However, LTE (Long Term Evolution) may be applied at least partially to the mobile communication system 1.

[0013] As shown in Fig. 1, the mobile communication system 1 includes a 5G core network (5GC) 10, a user equipment (UE: User Equipment) 100, a base station (called a gNB) 200, and an IAB node 300. The IAB node 300 is an example of a relay device.

[0014] In one embodiment, an example in which the base station is an NR base station is mainly described, but the base station may also be an LTE base station (i.e., an eNB).

[0015] The 5GC 10 has an Access and Mobility Management Function (AMF) 11 and a User Plane Function (UPF) 12. The AMF 11 is a device that performs various mobility controls for the UE 100. The AMF 11 manages information on the area in which the UE 100 is located by communicating with the UE 100 using Non-Access Stratum (NAS) signaling. The UPF 12 is a device that performs transfer control of user data.

[0016] The gNB 200 is connected to the 5GC 10 via an interface called an NG interface. In FIG. 1, three gNBs 200-1 to 200-3 connected to the 5GC 10 are illustrated. The gNB 200 is a fixed wireless communication device that performs wireless communication with the UE 100. When the gNB 200 has a donor function, the gNB 200 may perform wireless communication with an IAB node wirelessly connected to the gNB 200.

[0017] The gNB 200 is connected to other adjacent gNBs 200 via an inter-base station interface called an Xn interface. FIG. 1 shows an example in which a gNB 200-1 is connected to a gNB 200-2 and a gNB 200-2.

[0018] Each gNB 200 manages one or more cells. A cell is used as a term indicating the smallest unit of a wireless communication area. A cell may be used as a term indicating a function or resource for performing wireless communication with a UE 100. One cell belongs to one carrier frequency.

[0019] The UE 100 is a mobile wireless communication device that performs wireless communication with the gNB 200. The UE 100 may perform wireless communication with the IAB node 300. The UE 100 may be a device that performs wireless communication with the gNB 200 or the IAB node 300. For example, the UE 100 is a mobile phone terminal, a tablet terminal, a notebook PC, a sensor or a device provided in a sensor, or a vehicle or a device provided in a vehicle.

[0020] FIG. 1 shows an example in which UE 100-1 is wirelessly connected to gNB 200-1, UE 100-2 is wirelessly connected to IAB node 300-1, and UE 100-3 is wirelessly connected to IAB node 300-2. UE 100-1 directly communicates with gNB 200-1. UE 100-2 indirectly communicates with gNB 200-1 via IAB node 300-1. UE 100-3 indirectly communicates with gNB 200-1 via IAB node 300-1 and IAB node 300-2.

[0021] The IAB node 300 is a device (relay device) that is involved in communication between the eNB 200 and the UE 100 and relays this communication. In FIG. 1, an example is shown in which the IAB node 300-1 is wirelessly connected to the gNB 200-1, which is a donor device, and the IAB node 300-2 is wirelessly connected to the IAB node 300-1. Each IAB node 300 manages a cell. The cell ID of the cell managed by the IAB node 300 may be the same as or different from the cell ID of the cell of the donor gNB 200-1.

[0022] The IAB node 300 has a UE function (user equipment function) and a gNB function (base station function). Such a UE function may be referred to as an MT, and the gNB function may be referred to as a DU.

[0023] The IAB node 300 performs wireless communication with a higher-level device (gNB 200 or higher-level IAB node 300) using its own UE function (MT), and performs wireless communication with a lower-level device (UE 100 or lower-level IAB node 300) using its own gNB function (DU). The UE function (MT) means at least a part of the functions of the UE 100, and the IAB node 300 does not necessarily have all the functions of the UE 100. The gNB function (DU) means at least a part of the functions of the gNB 200, and the IAB node 300 does not necessarily have all the functions of the gNB 200. For example, the gNB function (DU) does not have to have an RRC layer, a PDCP layer, etc.

[0024] A wireless section between the UE 100 and the IAB node 300 or the gNB 200 may be referred to as an access link (or Uu). A wireless section between the IAB node 300 and the gNB 200 or another IAB node 300 may be referred to as a backhaul link (or Un). Such a backhaul link may be referred to as a fronthaul link.

[0025] It is possible to integrate and multiplex the data communication of the access link and the data communication of the backhaul link in layer 2, dynamically allocate radio resources to the data communication of the backhaul link, and dynamically switch the relay path. The access link and the backhaul link may use a millimeter wave band. The access link and the backhaul link may be multiplexed by time division and / or frequency division.

[0026] (Base station configuration) Next, a configuration of the gNB 200, which is a base station according to an embodiment, will be described. Fig. 2 is a diagram showing the configuration of the gNB 200. As shown in Fig. 2, the gNB 200 has a wireless communication unit 210, a network communication unit 220, and a control unit 230.

[0027] The wireless communication unit 210 is used for wireless communication with the UE 100 and wireless communication with the IAB node 300. The wireless communication unit 210 has a receiving unit 211 and a transmitting unit 212. The receiving unit 211 performs various receptions under the control of the control unit 230. The receiving unit 211 includes an antenna, converts a wireless signal received by the antenna into a baseband signal (received signal), and outputs the signal to the control unit 230. The transmitting unit 212 performs various transmissions under the control of the control unit 230. The transmitting unit 212 includes an antenna, converts a baseband signal (transmitted signal) output by the control unit 230 into a wireless signal, and transmits the wireless signal from the antenna.

[0028] The network communication unit 220 is used for wired communication (or wireless communication) with the 5GC10 and wired communication (or wireless communication) with other adjacent gNBs 200. The network communication unit 220 has a receiving unit 221 and a transmitting unit 222. The receiving unit 221 performs various receptions under the control of the control unit 230. The receiving unit 221 receives a signal from the outside and outputs the received signal to the control unit 230. The transmitting unit 222 performs various transmissions under the control of the control unit 230. The transmitting unit 222 transmits a transmission signal output by the control unit 230 to the outside.

[0029] The control unit 230 performs various controls in the gNB 200. The control unit 230 includes at least one memory and at least one processor electrically connected to the memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processing. The processor executes the processing described below.

[0030] (Configuration of relay device) Next, a configuration of an IAB node 300 which is a relay device according to an embodiment will be described. Fig. 3 is a diagram showing a configuration of the IAB node 300. As shown in Fig. 3, the IAB node 300 has a wireless communication unit 310 and a control unit 320. The IAB node 300 may have a plurality of wireless communication units 310.

[0031] The wireless communication unit 310 is used for wireless communication (backhaul link) with the gNB 200 and for wireless communication (access link) with the UE 100. The wireless communication unit 310 for backhaul link communication and the wireless communication unit 310 for access link communication may be provided separately.

[0032] The wireless communication unit 310 has a receiving unit 311 and a transmitting unit 312. The receiving unit 311 performs various receptions under the control of the control unit 320. The receiving unit 311 includes an antenna, and converts a wireless signal received by the antenna into a baseband signal (received signal), and outputs the signal to the control unit 320. The transmitting unit 312 performs various transmissions under the control of the control unit 320. The transmitting unit 312 includes an antenna, and converts a baseband signal (transmitted signal) output by the control unit 320 into a wireless signal, and transmits the signal from the antenna.

[0033] The control unit 320 performs various controls in the IAB node 300. The control unit 320 includes at least one memory and at least one processor electrically connected to the memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processing. The processor executes the processing described below.

[0034] (Configuration of user device) Next, a configuration of a UE 100 which is a user device according to an embodiment will be described. Fig. 4 is a diagram showing the configuration of the UE 100. As shown in Fig. 4, the UE 100 includes a radio communication unit 110 and a control unit 120.

[0035] The wireless communication unit 110 is used for wireless communication in the access link, i.e., wireless communication with the gNB 200 and wireless communication with the IAB node 300. The wireless communication unit 110 has a receiving unit 111 and a transmitting unit 112. The receiving unit 111 performs various receptions under the control of the control unit 120. The receiving unit 111 includes an antenna, and converts a wireless signal received by the antenna into a baseband signal (received signal) and outputs the signal to the control unit 120. The transmitting unit 112 performs various transmissions under the control of the control unit 120. The transmitting unit 112 includes an antenna, and converts a baseband signal (transmitted signal) output by the control unit 120 into a wireless signal and transmits the signal from the antenna.

[0036] The control unit 120 performs various controls in the UE 100. The control unit 120 includes at least one memory and at least one processor electrically connected to the memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of a baseband signal. The CPU executes programs stored in the memory to perform various processing. The processor executes the processing described below.

[0037] (An example of a protocol stack configuration) Next, an example of a protocol stack configuration in the mobile communication system 1 according to an embodiment will be described. Fig. 5 is a diagram showing an example of a protocol stack configuration of a user plane. Fig. 5 shows an example of a protocol stack configuration related to user data transmission between the UE 100-3 and the UPF 12 of the 5GC 10 shown in Fig. 1.

[0038] 5, the UPF 12 has a GPRS Tunneling Protocol for User Plane (GTP-U), a User Datagram Protocol (UDP), an Internet Protocol (IP), and Layer 1 / Layer 2 (L1 / L2). The gNB 200-1 (donor gNB) is provided with protocol stacks corresponding to these.

[0039] The gNB 200-1 also has a central unit (CU) and a distributed unit (DU). In the protocol stack of the wireless interface, the CU has layers above the packet data convergence protocol (PDCP), and the DU has layers below the radio link control (RLC), and the CU and the DU are connected via an interface called an F1 interface.

[0040] Specifically, the CU has a Service Data Adaptation Protocol (SDAP), a PDCP, an IP, and L1 / L2. The SDAP and PDCP of the CU communicate with the SDAP and PDCP of the UE 100 via the DU, the IAB node 300-1, and the IAB node 300-2.

[0041] In addition, the DU has an RLC, an adaptation layer (Adapt), a MAC (Medium Access Control), and a PHY (Physical layer) in the protocol stack of the radio interface. These protocol stacks are protocol stacks for gNBs. Note that the hierarchical relationship between the adaptation layer and the RLC (S-RLC) may be reversed. The adaptation layer may be called a backhaul adaptation protocol (BAP) layer.

[0042] The IAB node 300-1 is provided with a protocol stack ST1 for UEs corresponding to these. Furthermore, the IAB node 300-1 is provided with a protocol stack ST2 for gNBs. Both the protocol stack ST1 and the protocol stack ST2 are composed of layers (sublayers) below layer 2. That is, the IAB node 300-1 is a layer 2 relay device that relays user data using layers below layer 2. The IAB node 300-1 relays data without using layers above layer 3 (specifically, layers above PDCP). The IAB node 300-2 has a protocol stack configuration similar to that of the IAB node 300-1.

[0043] Here, the protocol stack configuration in the user plane has been described. However, in the control plane, the gNB 200-1, the IAB node 300-1, the IAB node 300-2, and the UE 100-3 each have a radio resource control (RRC) corresponding to layer 3.

[0044] An RRC connection is established between the RRC of the gNB 200-1 (donor gNB) and the RRC of the IAB node 300-1, and RRC messages are transmitted and received using this RRC connection. Also, an RRC connection is established between the RRC of the gNB 200-1 and the RRC of the IAB node 300-2, and RRC messages are transmitted and received using this RRC connection. Furthermore, an RRC connection is established between the RRC of the gNB 200-1 and the RRC of the UE 100-3, and RRC messages are transmitted and received using this RRC connection.

[0045] (Operation according to the embodiment) Next, the operation of the mobile communication system 1 according to an embodiment will be described.

[0046] FIG. 6 is a diagram showing an operation scenario of the mobile communication system 1 according to an embodiment.

[0047] 6, an upstream path using multiple relay devices (IAB node 300a, IAB node 300b, and IAB node 300c) is formed between the UE 100 and the donor gNB 200a. The donor gNB 200a corresponds to a first donor device.

[0048] In the following, the IAB node 300b (relay device) on the upstream path will be mainly described. The lower device below the IAB node 300b on the upstream path is the IAB node 300a, and the first upper device above the IAB node 300b on the upstream path is the IAB node 300c. Also, it is assumed that a failure occurs in the backhaul link established between the IAB node 300b and the IAB node 300c (first upper device), and the IAB node 300b re-establishes the backhaul link with the IAB node 300d (second upper device).

[0049] The donor gNB 200a manages the IAB nodes 300a, 300b, 300c, and 300d, and functions as a donor for the IAB nodes 300a, 300b, 300c, and 300d. In other words, the IAB nodes 300a, 300b, 300c, and 300d are under the control of the donor gNB 200a.

[0050] Alternatively, the donor gNB 200b may manage the IAB node 300d and function as a donor for the IAB node 300d. In other words, the IAB node 300d may be under the donor gNB 200b, not under the donor gNB 200a. Hereinafter, the donor gNB that manages the IAB node 300d is referred to as a second donor device. The second donor device is the donor gNB 200a or the donor gNB 200b.

[0051] The UE 100 transmits upstream data to the donor gNB 200a via the paths of the IAB nodes 300a, 300b, and 300c, but not via the IAB node 300d. In one embodiment, the upstream data is a PDCP Protocol Data Unit (PDU). However, assuming that there is no segmentation (segmentation) of the PDCP PDU, the upstream data may be an RLC SDU. The upstream data may also be a BAP PDU.

[0052] PDCP PDU#0 has been received by the donor gNB 200a, and PDCP PDU#1 and #2 have been received by the IAB node 300c. PDCP PDU#3 has not yet been received by the IAB node 300c and is being transmitted by the RLC layer of the IAB node 300b. PDCP PDU#4, #5, and #6 have been received by the IAB node 300b but have not yet been passed from the PDCP layer to the RLC layer in the IAB node 300b. PDCP PDU#7 has been received by the IAB node 300a. PDCP PDU#8 and #9 are buffered on the UE 100 side.

[0053] Under such a situation, a radio link failure (i.e., BH RLF) of the backhaul link occurs between the IAB node 300b and the IAB node 300c. The IAB node 300b re-establishes a backhaul link with the IAB node 300d, which is a new parent node (upper device). For example, the IAB node 300b re-establishes a backhaul link with the IAB node 300d by performing an RRC re-establishment process via the IAB node 300d. After the RRC re-establishment, the RLC entity of the IAB node 300b is re-established. Here, it is assumed that the IAB node 300b buffers untransmitted PDCP PDUs #3, #4, #5, and #6, for example, in the BAP layer.

[0054] Thus, in one embodiment, in a situation where an upstream path is formed between the UE 100 and the donor gNB 200a (first donor device), if a failure occurs in the backhaul link established between the IAB node 300b and the IAB node 300c, the IAB node 300b re-establishes the backhaul link of the IAB node 300b with the IAB node 300d (second higher-level device), thereby re-forming the upstream path.

[0055] In one embodiment, the BAP layer of IAB node 300b may forward the buffered upstream data (i.e., PDCP PDUs #3, #4, #5, and #6) to IAB node 300d. In other words, the BAP layer of IAB node 300b may reroute the upstream data using the new upstream path.

[0056] However, if the IAB node 300d is not under the control of the donor gNB 200a but is under the control of the donor gNB 200b, the donor gNB 200b cannot process the upstream data buffered by the IAB node 300b even if the donor gNB 200b receives the upstream data via the IAB node 300d. Specifically, the PDCP PDU is encrypted by the UE 100 using a security key, and a paired PDCP entity exists in the donor 200a. The donor gNB 200a performs decryption (decryption) using the security key, but the donor gNB 200b does not have this security key and cannot decrypt the PDCP PDU.

[0057] In contrast, when the IAB node 300d is under the control of the donor gNB 200a, the donor gNB 200a can process the upstream data buffered by the IAB node 300b when the donor gNB 200a receives the upstream data via the IAB node 300d.

[0058] In one embodiment, the IAB node 300b is able to appropriately handle a backhaul link failure by determining whether to forward buffered upstream data to the IAB node 300d depending on whether the IAB node 300d is under the control of a donor gNB 200a.

[0059] First, the IAB node 300b transfers upstream data received from the IAB node 300a, which is a lower-level device of the IAB node 300b, to the IAB node 300c, which is a first higher-level device of the IAB node 300b. Also, the IAB node 300b buffers upstream data that has not yet been sent to the IAB node 300c.

[0060] Second, if a failure occurs in the backhaul link established between IAB node 300b and IAB node 300c, IAB node 300 re-establishes the backhaul link of IAB node 300b with IAB node 300d, which is the second higher-level device.

[0061] Third, the BAP layer of IAB node 300b decides whether to forward the buffered upstream data to IAB node 300d based on whether the donor device (second donor device) managing IAB node 300d is the same as donor gNB 200a (first donor device).

[0062] Specifically, when the BAP layer of the IAB node 300b determines that the donor device of the IAB node 300d is the same as the donor gNB 200a, it transfers the buffered upstream data to the IAB node 300d. In this case, when the BAP layer or the RLC layer of the IAB node 300b completes the transfer of the buffered upstream data, it may transmit an ACK (e.g., an RLC ACK) corresponding to the buffered upstream data to the IAB node 300a, which is a lower device.

[0063] On the other hand, if the BAP layer of the IAB node 300b determines that the donor device of the IAB node 300d is different from the donor gNB 200a (for example, if the donor device of the IAB node 300d is the donor gNB 200b), the BAP layer of the IAB node 300b discards the buffered upstream data. Also, if the BAP layer or the RLC layer of the IAB node 300b determines that the donor device of the IAB node 300d is different from the donor gNB 200a, the BAP layer or the RLC layer of the IAB node 300b may transmit a NACK (for example, an RLC NACK) corresponding to the buffered upstream data to the IAB node 300a, which is a lower device.

[0064] In one embodiment, the MT of the IAB node 300b may receive an identifier for the donor device of the IAB node 300d from the IAB node 300d. The MT or BAP layer of the IAB node 300b may determine whether the donor device of the IAB node 300d is the same as the donor gNB 200a based on the identifier received from the IAB node 300d.

[0065] For example, the IAB node 300b may receive an RRC Reconfiguration message from the IAB node 300d that includes an identifier for a donor device of the IAB node 300d. The RRC Reconfiguration message may be transmitted from the donor gNB 200a to the IAB node 300b via the IAB node 300d.

[0066] Alternatively, the IAB node 300b may receive an RRC Reconfiguration message from the IAB node 300c, the RRC Reconfiguration message including an identifier for the donor device of the IAB node 300d. The RRC Reconfiguration message may be transmitted from the donor gNB 200a to the IAB node 300b via the IAB node 300c.

[0067] The RRC Reconfiguration message may be an RRC Reconfiguration message for handover or an RRC Reconfiguration message for RRC re-establishment. The MT of the IAB node 300b may hold the identifier included in the received RRC Reconfiguration message.

[0068] Alternatively, the IAB node 300b may receive a system information block (SIB) including an identifier related to a donor device of the IAB node 300d from the IAB node 300d. The SIB is notification information that the IAB node 300d transmits by broadcast. The MT of the IAB node 300b may hold the identifier included in the received SIB.

[0069] The identifier for the donor device of the IAB node 300d includes at least one of the base station identifier (gNB ID) of the donor device of the IAB node 300d and the identifier of the CU (Central Unit) of the donor device of the IAB node 300d. The MT or BAP layer of the IAB node 300b compares the identifier for the donor gNB 200a (previously held identifier) ​​with the identifier for the donor device of the IAB node 300d (newly acquired identifier), and determines that the donor device managing the IAB node 300d is the same as the donor gNB 200a only if the two identifiers match.

[0070] Alternatively, the identifier for the donor device of the IAB node 300d may include at least one of an identifier indicating whether the donor device of the IAB node 300d is the same as the donor gNB 200a and an identifier indicating whether the buffered upstream data is permitted to be forwarded to the IAB node 300d. Based on such identifier, the MT or BAP layer of the IAB node 300b determines whether the donor device managing the IAB node 300d is the same as the donor gNB 200a, i.e., whether the buffered upstream data is permitted to be forwarded to the IAB node 300d.

[0071] Alternatively, the MT of the IAB node 300b may receive a list of the IAB nodes 300b under the donor gNB 200a from the IAB node 300c. This list may be included in an RRC Reconfiguration message transmitted from the donor gNB 200a to the IAB node 300b via the IAB node 300c. The MT or BAP layer of the IAB node 300b determines whether the donor device of the IAB node 300d is the same as the donor gNB 200a based on the list received from the IAB node 300c. For example, the MT or BAP layer of the IAB node 300b determines that the donor device of the IAB node 300d is the same as the donor gNB 200a if an identifier for the IAB node 300d is included in the list.

[0072] Fig. 7 is a flow diagram showing an example of the operation of a relay device according to an embodiment. Here, the operation of the IAB node 300b in the operation scenario shown in Fig. 6 will be described. However, the operation shown in Fig. 7 may be executed by the IAB node 300a shown in Fig. 6. The IAB node 300a is an IAB node having an access link with the UE 100, and may be called an access IAB node.

[0073] As shown in FIG. 7, in step S1, the IAB node 300b, together with the IAB nodes 300a and 300c, forms an upstream path between the UE 100 and a first donor device (donor gNB 200a).

[0074] In step S2, the IAB node 300b receives a list of IAB nodes under the first donor device (donor gNB 200a) from the IAB node 300c. This list may be a list of identifiers of each IAB node under the first donor device (donor gNB 200a). This list may be transmitted from the first donor device (donor gNB 200a) to the IAB node 300b via the IAB node 300c. Note that the process of step S6 described below may be executed without executing the process of step S2.

[0075] In step S3, the IAB node 300b transfers the upstream data received from the lower device (IAB node 300a) of the IAB node 300b on the upstream route to the first upper device (IAB node 300bc) of the IAB node 300b. Also, the IAB node 300b buffers the upstream data that has not yet been transmitted to the IAB node 300c.

[0076] In step S4, the IAB node 300b determines whether a failure (BH RLF) has occurred in the backhaul link established between the IAB node 300b and the first higher-level device (IAB node 300c). If a BH RLF has not occurred (step S4: NO), the process returns to step S3. On the other hand, if a BH RLF has occurred (step S4: YES), the process proceeds to step S5.

[0077] In step S5, the IAB node 300b re-establishes the backhaul link of the IAB node 300b with the second upstream device (IAB node 300d), thereby re-forming the upstream path.

[0078] In step S6, the IAB node 300b receives an identifier related to the donor device of the IAB node 300d from the IAB node 300d. The IAB node 300b may receive an RRC Reconfiguration message including an identifier related to the donor device of the IAB node 300d from the IAB node 300d. This RRC Reconfiguration message may be transmitted from the donor gNB 200a to the IAB node 300b via the IAB node 300d. Note that if the process of step S2 described above is executed, the process of step S6 may not be executed. In order for the IAB node 300b to make a determination in step S7 described below, at least one of the processes of step S2 and step S6 must be executed. Both the processes of step S2 and step S6 may be executed.

[0079] In step S7, the IAB node 300b determines whether the second donor device managing the second higher-level device (IAB node 300d) is the same as the first donor device (donor gNB 200a) based on the list received in step S2 or the identifier received in step S6. In other words, the IAB node 300b determines whether the buffered upstream data is allowed to be forwarded to the IAB node 300d.

[0080] If it is determined that the second donor device managing the second upstream device (IAB node 300d) is the same as the first donor device (donor gNB 200a) (step S7: YES), in step S8, the IAB node 300b transfers the buffered upstream data to the second upstream device (IAB node 300d).

[0081] On the other hand, if it is determined that the second donor device managing the second higher-level device (IAB node 300d) is different from the first donor device (donor gNB 200a) (step S7: NO), in step S9, the IAB node 300b discards the buffered upstream data. Then, in step S10, the IAB node 300b transmits a NACK corresponding to the buffered upstream data to the IAB node 300a, which is a lower-level device.

[0082] (Other embodiments) In the above-described embodiment, a base station (hereinafter, referred to as a master base station) that manages each IAB node 300 may exist in addition to the donor gNB 200. The master base station may be an LTE base station. The MT of each IAB node 300 may have two connections (i.e., dual connections), a connection with the master base station and a connection with a higher-level device (higher IAB node or donor gNB). The master base station may be a master node, and the connection may be a Master Cell Group (MCG) link. The higher-level device (higher IAB node or donor gNB) may be a secondary node, and the connection may be a Secondary Cell Group (SCG) link. Under such a premise, the MT of the IAB node 300b may receive the list of step S3 or the identifier of step S6 in FIG. 7 from the master base station via the MCG link.

[0083] Also, in the above-mentioned embodiment, an example in which the mobile communication system 1 is a 5G mobile communication system has been mainly described. However, the base station in the mobile communication system 1 may be an eNB, which is an LTE base station. Also, the core network in the mobile communication system 1 may be an EPC (Evolved Packet Core). Furthermore, the gNB may be connected to the EPC, the eNB may be connected to the 5GC, and the gNB and the eNB may be connected via an inter-base station interface (Xn interface, X2 interface).

[0084] A program for causing a computer to execute each process according to the above-described embodiment may be provided. The program may be recorded in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in the computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. A chipset may be provided that is configured by a memory that stores a program for executing each process performed by the UE 100, the gNB 200, or the IAB node 300, and a processor that executes the program stored in the memory.

[0085] This application claims priority to Japanese Patent Application No. 2019-145743 (filed August 7, 2019), the entire contents of which are incorporated herein by reference.

Claims

1. A communication control method executed in a relay device belonging to an upstream path formed between a user device and a first donor device using a plurality of relay devices, comprising: receiving a BAP (Backhaul Adaptation Protocol) data unit from a lower relay device of the relay device belonging to the upstream path; When a failure occurs in a backhaul link between a first upper relay device belonging to the upstream path and the relay device, determining whether to transmit the BAP data unit through a backhaul link established between the relay device and a second upper relay device; The determining step includes determining, when the second upper relay device is not under the control of a second donor device but is under the control of the first donor device, to transmit the BAP data unit via a backhaul link established with the second upper relay device. Communications control method.

2. A relay device belonging to an upstream path formed between a user device and a first donor device using a plurality of relay devices, A control unit is provided, The control unit is A process of receiving a BAP (Backhaul Adaptation Protocol) data unit from a lower relay device of the relay device belonging to the upstream route; When a failure occurs in a backhaul link between an upper relay device belonging to the upstream path and the relay device, a process of determining whether to transmit the BAP data unit through a backhaul link established between the relay device and a second upper relay device; Run The process of determining includes a process of determining to transmit the BAP data unit via a backhaul link established between the second upper relay device and the second upper relay device when the second upper relay device is not subordinate to the second donor device but subordinate to the first donor device. Relay device.

3. A processor for controlling a relay device belonging to an upstream path formed using a plurality of relay devices between a user device and a first donor device, A process of receiving a BAP (Backhaul Adaptation Protocol) data unit from a lower relay device of the relay device belonging to the upstream route; When a failure occurs in a backhaul link between an upper relay device belonging to the upstream path and the relay device, a process of determining whether to transmit the BAP data unit through a backhaul link established between the relay device and a second upper relay device; Run The process of determining includes a process of determining to transmit the BAP data unit via a backhaul link established with the second higher level relay device when the second higher level relay device is not subordinate to the second donor device but subordinate to the first donor device. Processor.