Communication control device, method for controlling communication device, and program
By detecting and transferring the relay nodes in the IAB network, the problem that the slice communication requirements in the IAB network cannot be met is solved, and the slice communication requirements of the user equipment are restored.
Patent Information
- Application Number
- CN202380033726.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-18
- Filing Date
- 2023-03-03
- Publication Date
- 2024-11-26
AI Technical Summary
In an IAB network, an IAB node that meets slice communication requirements may not be able to continue to provide communications that meet these requirements due to changes in the processing load or communication environment of the IAB node and the IAB donor of higher order connections.
The detection component detects whether the communication requirements of a particular slice are met, and based on the detection result, an instruction is provided to transfer the connection to a second relay node that meets the slice requirements.
In an integrated access and backhaul (IAB) network, when the slice communication requirements cannot be met, the slice communication requested by the UE can be provided to ensure the recovery of communication quality.
Smart Images

Figure CN119032592A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a communication control device, a method for controlling a communication device, and a program. Background Art
[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has been conducting standardization of Integrated Access and Backhaul (IAB) as a communication technology for backhaul. The IAB technology also uses millimeter wave wireless communication in the 28 GHz band for access communication between a base station and a user equipment (UE) as backhaul communication at the same time (PTL 1).
[0003] In a backhaul communication network using the IAB technology (hereinafter referred to as an "IAB network"), a relay device called an IAB node relays communications from an IAB donor, which is equivalent to a conventional base station, to a destination UE. In the event that the wireless communication conditions between the IAB donor and the IAB node in the IAB network deteriorate, research has been conducted to restore and improve the communication conditions by switching the communication path or forming multiple communication paths (hereinafter referred to as "multipath"). In the IAB network, a Backhaul Adaptation Protocol (BAP) is used in communications between the IAB donor and the IAB node and between the IAB nodes. BAP is defined as a protocol primarily used to route communication data packets between multiple IAB nodes.
[0004] Citation List
[0005] Patent Literature
[0006] PTL 1: Japanese Patent Publication No. 2019-534625 Summary of the invention
[0007] Technical issues
[0008] Here, research has been conducted on the introduction of the concept of network slicing, which virtually provides network slices (hereinafter referred to as "slices") that meet the requirements and conditions of a variety of different services on a public network in the next generation of public networks. The defined slice types include high speed / large capacity (eMBB), low latency (URLLC), and simultaneous multiple access (mMTC). "eMBB" is an abbreviation for "enhanced mobile broadband". "URLLC" is an abbreviation for "ultra-reliable and low-latency communication", and "mMTC" is an abbreviation for "massive machine type communication". For example, a mechanism is being examined in which a UE makes a request for a specific network slice, and the CN (core network) of the base station responds to perform communication using the requested network.
[0009] In an IAB network, due to changes in the processing load or communication environment of the IAB nodes and IAB donors of the higher-order connections, the IAB nodes that meet the communication requirements in the slice may no longer be able to provide communications that meet these requirements. In such a case, the UE cannot continue the communication in the slice.
[0010] The present invention is made in view of the above-mentioned problems, and aims to provide communication in a slice requested by a UE when the communication requirements in a slice in an integrated access and backhaul (IAB) network become unsatisfactory.
[0011] Solution to the problem
[0012] In order to solve the above problems, a communication control device according to the present invention is
[0013] A communication control device for integrated access and backhaul IAB network, characterized in that the device comprises:
[0014] A detection component, configured to detect that a first relay node communicating with a base station of a network through a first communication path no longer meets requirements for communication in a specific slice; and
[0015] An instruction component is used to provide an instruction to connect to a second relay node based on the result of the detection performed by the detection component, wherein the second relay node is located on a second communication path that meets the requirements of communication in a specific slice and can be connected from the first relay node.
[0016] Advantageous Effects of the Invention
[0017] According to the present invention, when communication requirements in a slice in an integrated access and backhaul (IAB) network become unable to be met, communication in a slice requested by a UE may be provided.
[0018] Other features and advantages of the present invention will be apparent from the following description taken in conjunction with the accompanying drawings.It is noted that throughout the accompanying drawings, the same reference numerals designate the same or similar components. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the present invention.
[0020] Figure 1 is a diagram illustrating an example of a wireless communication system.
[0021] Figure 2 It is the hardware functional block diagram of the communication device.
[0022] Figure 3 It is the software functional block diagram of the communication device.
[0023] Figure 4is a flowchart illustrating a method of determining a new connection destination according to Embodiment 1.
[0024] Figure 5 An example of the connection candidate list of the IAB node 105 according to Embodiment 1 is shown.
[0025] Fig. 6A An example of NSSAI lists of the IAB donor 101 and the IAB nodes 102 to 105 according to Embodiment 1 is shown.
[0026] Figure 6B An example of NSSAI lists of the IAB donor 101 and the IAB nodes 102 to 105 according to Embodiment 1 is shown.
[0027] Figure 7 is a sequence diagram illustrating establishment of a multipath connection according to Embodiment 1.
[0028] Figure 8 1 is a diagram showing a topology after a new communication path is connected according to the first embodiment.
[0029] Fig. 9 FIG. 1 is a flowchart for determining a new communication path at an IAB donor according to the second embodiment.
[0030] Fig.10 An example of a connection candidate list of the IAB 104 according to the second embodiment is shown.
[0031] Fig.11 An example of NSSAI lists of the IAB donor 101 and the IAB nodes 102 to 105 according to Embodiment 2 is shown.
[0032] Fig.12 FIG. 1 is a diagram showing a topology after a new communication path is connected according to the second embodiment. DETAILED DESCRIPTION
[0033] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the scope of the claimed invention. A plurality of features are described in the embodiments, but no limitation is imposed on the invention requiring all such features, and a plurality of such features may be appropriately combined. In addition, in the accompanying drawings, the same reference numerals are given to the same or similar configurations, and redundant descriptions thereof are omitted.
[0034] In the backhaul communication using IAB technology, a relay device (relay node) called an IAB node relays the communication from the IAB donor equivalent to the traditional base station by means of millimeter wave communication. The IAB node can form a communication link with multiple other IAB nodes to form a network with the IAB donor as the starting point, thereby expanding the network area.
[0035] In the IAB technology, the Backhaul Adaptation Protocol (BAP) is used to perform control between the IAB donor and the IAB node and between the IAB nodes. BAP is defined as a protocol for routing data between the IAB donor and the IAB node. In the case where the wireless communication condition between the IAB donor and the IAB node deteriorates in the backhaul communication using the IAB technology, it has been studied to restore and improve the communication condition by switching the communication path or forming multiple communication paths (hereinafter referred to as "multi-path connection"). For example, a mechanism has been studied in which the network slices provided by the base station are notified, each UE selects or requests a network slice according to its purpose, and the IAB donor responds to enable the UE to use the selected or requested network slice.
[0036] Here, in the case where the IAB donor provides a slice to the UE, requirements (slice requirements) are defined for communication in a specific slice. Slice requirements include, for example, communication speed (throughput), packet loss rate, and round-trip delay. Depending on the slice type, there are slice requirements with different parameters. In such a case, there may be a situation where the slice requirements are met when the IAB donor initially provides communication in the slice to the UE, but the slice requirements become unsatisfactory due to changes in the processing load of the IAB node or a communication link failure. In such a case, the UE cannot meet the communication requirements in the slice.
[0037] To solve this problem, if it is detected that communication in a specific communication path provided to a specific UE no longer satisfies the requirements, the communication control apparatus according to the present embodiment instructs the relay node on the specific communication path to connect to a communication path that satisfies the requirements.
[0038] Example 1
[0039] Figure 1 is a diagram showing an example of a wireless communication system according to the present invention. Figure 1The wireless communication system 100 shown in the figure includes an IAB donor 101 that provides a connection to a CN 130 and IAB nodes 102 to 105 (hereinafter also referred to as "IAB nodes" without distinction). The wireless communication system 100 is a network (IAB network) that performs communication using a backhaul adaptation protocol (BAP). The IAB donor 101 provides a connection to the CN 130 via an IAB node and a backhaul link. The IAB node provides a connection to the IAB donor 101 to the UE through an access link. In the wireless communication system 100, new radio (NR) communication is used on both the backhaul link and the access link in the network. The IAB donor 101 forms an IAB network (NR backhaul network) including an IAB node. Here, "CN" is an abbreviation for "core network" and is responsible for various types of processing, such as authentication of UEs 110 to 118 (hereinafter also referred to as "UEs" without distinction) as user equipment, and registration of the use of network slices (slices).
[0040] The IAB donor 101 is an example of a base station device that centrally controls the IAB node and forms its coverage area. In the description of this embodiment, the IAB donor 101 is a communication control device that performs the above-mentioned communication control. However, the function of the communication control device can be provided in an IAB node, a network node of a core network, or a device different from the IAB node and the IAB donor 101 in the wireless communication system 100.
[0041] The IAB donor 101 determines the type of network slices that the IAB node can support for each IAB node and assigns the determined type to the IAB node. In addition, it is assumed that the IAB donor 101 manages information about the slices supported by each IAB node as an NSSAI list. Here, "NSSAI" is an abbreviation for "Network Slice Selection Assistance Information". If any of the slices supported by the IAB nodes 102 to 105 changes, the IAB donor 101 is notified of the change by means of a BAP control message.
[0042] The IAB donor 101 and the IAB node function as communication devices as described below, and each communication device in the following description is any one of the IAB donor 101 or the IAB node.
[0043] It is assumed that the BAP control message refers to a message transmitted and received according to the BAP control protocol data unit (PDU) format. The PDU type field may be used as control information to provide notification, or any other reserved field may also be used.
[0044] In the wireless communication system 100, when each UE receives a service provided by the CN 130, a data packet from the CN 130 is downlinked to the UE via the IAB donor 101. Meanwhile, in the uplink, a data packet from each UE is similarly transmitted to the CN 130 via the IAB donor 101.
[0045] Here, data packets conforming to the BAP data protocol data unit (PDU) format (hereinafter also referred to as "BAP data packets") are transmitted in the wireless communication system 100. For example, an Internet Protocol (IP) data packet from the CN 130 and addressed to the UE 118 is converted into a BAP data packet at the IAB donor 101 and transmitted to the IAB network 100. The transmitted BAP data packet is relayed by the IAB nodes 102 to 105, converted into an IP data packet again at the IAB node 105, and delivered to the destination UE 118. Similarly, an IP data packet from the UE 118 is converted into a BAP data packet at the IAB node 105, transmitted via the IAB network 100, and converted into an IP data packet again at the IAB donor 101, and transmitted to the CN 130.
[0046] It is assumed that UEs 110 to 119 (hereinafter also referred to as "UEs" without distinction) are executing applications using desired slices provided by the IAB node. As described above, the defined slice types include high speed / large capacity (eMBB), low latency (URLLC), and simultaneous multiple access (mMTC). For example, UE 118 is executing an application requiring MIoT slices, while UE 119 is executing an application requiring eMBB.
[0047] Here, assuming that Figure 1 In the wireless communication system 100 shown in , the radio quality in the communication path between the IAB nodes 104 and 105 has deteriorated, and a link failure has occurred. In this case, the IAB node 105 no longer meets the requirements for communication in the slice (slice requirements), and errors may occur in the application executed by the UE 119. This embodiment assumes that the slice requirements of the eMBB are not met here. In this case, the IAB node 105 detects that it has become unable to meet the slice requirements of the eMBB, and notifies the IAB donor 101 by means of a BAP control message that it no longer meets the slice requirements (non-satisfaction of the requirements). In one example, the IAB node may notify the IAB donor 101 of the change in NSSAI by means of a BAP control message. The IAB node 105 may detect the non-satisfaction of the slice requirements based on the occurrence of an eMBB slice request from the UE 119, or may make a determination on its own based on the signal quality from the IAB node 104 measured regularly by means of RRM. "RRM" is an abbreviation for "Radio Resource Management".
[0048] For example, non-fulfillment of the slice requirement at the IAB node 104 may be detected based on the occurrence of an eMBB slice request signal from the UE 119, or may be determined by the IAB node 104 itself based on the signal quality from the IAB node 102 measured periodically via RRM.
[0049] Next, a method is described by which the IAB donor 101 serving as a communication control device determines a connection destination to form a new communication path in order to recover a slice that no longer satisfies the slice requirement at the IAB node 105 .
[0050] Figure 2 2 is a hardware block diagram of the communication device according to the present embodiment. The communication device is composed of hardware including a controller 201 , a storage unit 202 , a wireless communication unit 203 , and an antenna control unit 204 .
[0051] The controller 201 controls the entire device by executing a control program stored in the storage unit 202. In one example, the controller 201 includes a processor that loads the control program into the memory and executes the loaded program. The storage unit 202 stores the control program to be executed by the controller 201. The storage unit 202 of the IAB donor 101 also stores various types of information, such as information about a cell ID and a connected UE, and routing information about the IAB nodes 102 to 105.
[0052] The wireless communication unit 203 is used to perform cellular network communications that comply with the 3GPP (registered trademark) standard, such as Long Term Evolution (LTE) or 5G (fifth generation mobile communication system). The wireless communication unit 203 is capable of measuring the communication conditions with the IAB node and the UE according to the RRM, and is capable of providing notifications to the IAB donor 101 and the IAB nodes 102 to 105 by means of the RRC. "RRC" is an abbreviation for "radio resource control". The RRC message has functions such as connection establishment between the IAB nodes 102 to 105 and the UEs 110 to 119, admission control, RRC state management, and notification of surrounding cell information and access restrictions. It is assumed that the received reference signal power, received reference signal quality, etc. of the adjacent cell can be obtained as a communication condition that can be measured by means of the RRM as an RRC function.
[0053] The antenna control unit 204 controls an antenna used for wireless communication performed by the wireless communication unit 203. Note that the number of controllers 201, the number of storage units 202, the number of wireless communication units 203, and the number of antenna control units 204 may be more than one in a single communication device. The communication device may also include a constituent unit generally provided in base station equipment, such as a wired communication unit.
[0054] Figure 32 is a software functional block diagram of a communication device according to the present invention. The software functional blocks are stored in the storage unit 202 and are implemented as a result of being executed by the controller 201. The software functional blocks include a sending / receiving unit 301, a storage unit 302, a connection control unit 303, a requirement unsatisfied detection unit 304, a connection candidate identification unit 305, a slice management unit 306, and a communication path determination unit 307.
[0055] The transmission / reception unit 301 controls the wireless communication unit 203 via the controller 201, and performs cellular network communication conforming to the 3GPP (registered trademark) standard, such as LTE or 5G, with the IAB nodes 102 to 105 and the UEs 110 to 119. The storage unit 302 controls and manages the storage unit 202, and stores programs executed by the controller 201, such as an operating system of the communication device. The storage unit 302 stores and maintains the network topology of the IAB network 100, routing information about the IAB nodes 102 to 105, information related to the UEs 110 to 119, and the like. The connection control unit 303 controls the antenna control unit 204 via the controller 201 during wireless communication.
[0056] The requirement non-satisfaction detection unit 304 detects that the IAB node has become unable to meet the slice requirement (non-satisfaction of the requirement). For example, the requirement non-satisfaction detection unit 304 may compare the NSSAI list received from the IAB node with the NSSAI list managed by the slice management unit 306, and detect the non-satisfaction of the requirement based on the change of the slice type included in the list. Alternatively, when a slice request for a specific slice is received again from a UE that has been allocated to the slice, it can be detected that the IAB node to which the UE is connected does not meet the requirement. The requirement non-satisfaction detection unit 304, which has detected the non-satisfaction of the requirement, notifies the communication path determination unit 307 and updates the slice management unit 306.
[0057] The connection candidate identification unit 305 manages connection candidates that can be connected from each IAB node, and identifies an IAB node (connection candidate node) that can be connected from a specific IAB node. In one example, the connection candidate identification unit 305 collects and manages a list of connection candidate IAB nodes from each IAB node. For example, the IAB donor 101 transmits a request signal for a connection candidate list to a specific IAB node. After receiving the request signal, the IAB node transmits a response including the connection candidate list stored in the storage unit 302. This will be referred to later. Figure 5 A method for an IAB node to create and update a connection candidate list is described. In another example, the IAB node having received the request signal may update the connection candidate list and transmit a response including the updated connection candidate list.
[0058] The slice management unit 306 stores and manages the NSSAI list of slices supported by each IAB node obtained from the IAB node via the BAP control message.
[0059] In response to the notification from the requirement non-satisfaction detection unit 304, the communication path determination unit 307 refers to the connection candidate list of the IAB node that has been detected and the slice information about the communication device and each IAB node, and determines the communication path with the new connection destination that can achieve the recovery of the IAB node that has been detected and the requirement non-satisfaction. With the help of the RRC control message, the determined new connection destination is notified to the IAB node that has been detected and the requirement non-satisfaction. Here, the RRC control message is a message that conforms to the PDU format defined by RRC and is implemented using any one of the fields indicating the RRC function. Notification to the IAB node by means of the RRC control message can be made using only the neighboring cell list (NCL) of the new connection destination.
[0060] Although the functional blocks of the communication control device have been described here, other communication devices also have the same configuration except for the requirement unsatisfied detecting unit 304 , the connection candidate identifying unit 305 , and the communication path determining unit 307 .
[0061] Figure 4 1 is a flowchart illustrating a method of determining a new connection destination performed by the communication control device according to Embodiment 1. This flowchart may be started when the IAB donor 101 serving as the communication control device receives a BAP control message. In the description of this processing example, Figure 1 In the network topology shown in , the quality of wireless communication through the communication path between IAB nodes 104 and 105 has deteriorated and a link failure has occurred, resulting in the IAB node 105 being unable to meet the eMBB requirements.
[0062] In step S400, the requirement unsatisfied detection unit 304 of the IAB donor 101 detects that the IAB node 105 no longer meets the slice requirement based on the received RRC control message. For the IAB node 105 that no longer meets the slice requirement, the requirement unsatisfied detection unit 304 instructs the connection candidate identification unit 305 to identify the connection candidate node.
[0063] In step S401, the connection candidate identification unit 305 identifies connection candidates by collecting a connection candidate list via an RRC control message. It is assumed that in step S401, the IAB donor 101 transmits a transmission request for the connection candidate list to the IAB node 105, and the IAB node 105 transmits a request response including the connection candidate list in response to the transmission request. However, the connection candidate identification unit 305 may alternatively identify the connection candidate node by retrieving the connection candidate list stored in the storage unit 302, or may transmit the transmission request for the connection candidate list to an IAB node other than the IAB node 105.
[0064] The processing in steps S402 to S411 is repeated for all IAB nodes (the IAB nodes 102 and 103 in this example) included in the connection candidate list of the IAB node 105 that does not satisfy the slice.
[0065] In step S403, the NSSAI list of the connection candidate node n managed by the slice management unit 306 is referenced, and it is determined whether the connection candidate node n meets the eMBB slice requirement. If the requirement is met ("Yes" in S403), step S406 is executed. If not ("No" in S403), step S405 is executed, and the determination in step S403 is performed for the next connection candidate node n.
[0066] In step S406, the IAB node 105 is notified by means of an RRC control message that a multipath connection is to be performed with the connection candidate node n. The RRC control message transmitted in step S406 includes identification information about the connection candidate node n. Therefore, the IAB node 105 having received the notification can transmit a connection request to the connection candidate node n. Here, it is assumed that the connection candidate node n has established a communication path with the IAB donor 101, and this communication path satisfies the slice request. The IAB node 105 can connect to the communication path that satisfies the slice request by transmitting the aforementioned connection request to the connection candidate node n.
[0067] In another example, in step S406, the connection candidate node n may be notified of the update of the communication path instead. For example, the connection candidate node n may be instructed to update the communication path by transmitting identification information about the IAB node 105 to the connection candidate node n in association with an identifier of the communication path.
[0068] The IAB node 105 having received the notification of the multipath connection from the IAB donor 101 is connected to the IAB nodes 102 and 103 as the new connection destination and is provided with eMBB. Here, the IAB node 105 can perform a reconnection operation according to cell reselection according to the RRC protocol only for a subnet of a specific slice (eMBB).
[0069] exist Figure 4 In the description of the example shown in , the IAB node 105 maintains the connection with the IAB node 104, and the UE 118 continues to perform communications in the MIot slice. In one example, the IAB node 105 can be disconnected from the IAB node 104 and connected to a new connection destination IAB node. In this case, in step S406, the IAB donor 101 can instruct the IAB node 105 to switch the connection (handover) from the IAB node 104. That is, it is sufficient to provide an instruction to connect to the connection candidate node n that meets the slice requirements in step S406, and whether the IAB node 105 performs multipath connection can be changed as needed.
[0070] For example, if the IAB node 102 as the new connection destination meets all requirements for communication in the slice to be supported by the IAB node 105, the IAB donor 101 can instruct the IAB node 105 to disconnect from the IAB node 104. In this case, the IAB donor 101 can also instruct the IAB node 105 to perform communication in the slice to be supported through the communication path with the IAB node 102.
[0071] In another example, if the IAB node 102 as the new connection destination is located on the communication path that has been established by the IAB node 105, the IAB donor 101 can instruct the IAB donor 105 to disconnect from the communication path previously established by the IAB node 105. For example, the IAB node 105 has been communicating with the IAB donor 101 via the IAB nodes 102 and 104. Here, if the IAB node 102 is determined as the new connection destination, the path connecting the IAB donor 101, the IAB node 102, and the IAB node 104 includes a new communication path, that is, a communication path connecting the IAB donor 101 and the IAB node 102. In this case, the communication path that has been established adopts the same route as the new communication path, so the new communication path needs to meet the requirements of the slices to be supported by the IAB node 105. Also in this case, the IAB donor 101 may disconnect the IAB node 105 from the IAB node 104 and switch the communication path so that the IAB node 105 performs communication in the slice to be supported by the IAB node 105 through the new communication path.
[0072] Figure 5An example of a connection candidate list of the IAB donor 105 according to Embodiment 1 is shown. The connection candidate list 500 is created by each of the IAB nodes 102 to 105 generating a connection candidate list as neighboring cell information based on an RRM measurement result and the connection candidate identification unit 305 of the IAB donor 101 collecting and managing the connection candidate list thus generated via an RRC control message. As another method, the IAB donor 101 may collect the RRM measurement results at the IAB nodes 102 to 105 by means of an RRC protocol control message, and generate the connection candidate list 500 by, for example, listing the IAB nodes in descending order of radio field strength.
[0073] Alternatively, the IAB donor 101 may collect and use the NCL as a connection candidate list of the IAB nodes. Figure 5 In the connection candidate list 500 shown in , the IAB node 102 has the highest radio field strength among the connection candidate IAB nodes of the IAB node 105. That is, it is determined that the IAB node 102 has the highest communication quality among the connection candidate nodes.
[0074] Next, an example of the NSSAI list of the IAB donor 101 and the IAB nodes 102 to 105 is illustrated, and a description is given of a process for determining whether the IAB node 102 satisfies the slicing requirement in the process of step S403.
[0075] Fig. 6A and Figure 6B An example of NSSAI lists of the IAB donor 101 and the IAB nodes 102 to 105 according to Embodiment 1 is shown.
[0076] Fig. 6A Shown in Figure 1 FIG. 1 is an NSSAI list of the IAB donor 101 and the IAB nodes before a communication link failure occurs among the IAB nodes in the wireless communication system 100 shown in FIG.
[0077] The NSSAI list 600 is an example of slice support information about an IAB node that can be connected from the IAB donor 101. The NSSAI lists 601 to 604 are examples of slice support information about the IAB nodes 102 to 105 managed by the slice management unit 306. Here, 604 represents the NSSAI list of the IAB node 105 before being updated due to slice unsatisfaction detected from the IAB node 105.
[0078] Each value in NSSAI indicates a slice service type (SST), i.e. - a supportable slice type, and values 1, 2, 3 indicate eMBB, URLLC, MIoT, respectively.
[0079] For example, as shown in NSSAI list 600, IAB donor 101 supports all slice types eMBB, URLLC, and MIot. As shown in NSSAI lists 601 to 604, IAB nodes 102 to 105 support eMBB and MIot SST. Here, a specific IAB node supporting a specific slice type means that the IAB node can meet the communication requirements in the specific slice through the communication path between the specific IAB node and the IAB donor 101. This means that, for example, when the IAB node 102 newly receives an eMBB slice request, the IAB node 102 has a communication path that meets the eMBB communication requirements.
[0080] Here, a communication link failure occurs between the IAB nodes 104 and 105. The IAB node 105 is affected by the communication link failure and becomes unable to provide eMBB, and then only supports MIot SST. Figure 6B The updated NSSAI list of the IAB node 105 shown in includes only "3" indicating MIoT. Here, 605 represents the NSSAI list of the IAB node 105 after being updated due to the unsatisfied slice detected from the IAB node 105 in step S400.
[0081] As shown in 601 , the IAB node 102 as a connection destination candidate supports eMBB. Therefore, the IAB donor 101 selects the IAB node 102 as a new connection destination of the IAB node 105 .
[0082] Figure 7 1 is a sequence diagram illustrating establishment of a multipath connection performed by the wireless communication system 100 according to Embodiment 1. Figure 7 The operation of establishing a multipath connection to the IAB node 102 through a new communication path to recover the eMBB that the IAB node 105 becomes unable to support due to a communication link failure is illustrated.
[0083] In step S700, UE 119 performs communication of an application requesting eMBB. Here, UE 119 communicates in a slice whose slice type is eMBB via IAB node 105, which is directly connected to IAB node 104 and communicates with IAB donor 101 via IAB nodes 104 and 102. In step S700, no communication link failure occurs between IAB nodes 104 and 105, and IAB node 105 satisfies the requirements of eMBB communication requested by UE 119.
[0084] Here, in step S701, a failure occurs on the radio link between the IAB nodes 105 and 104, the packet loss rate on the radio link increases, and the requirements for throughput, packet loss rate, round trip delay, etc. required for communication are no longer met. It is assumed here that the throughput supporting eMBB is no longer guaranteed. Then, in step S702, the UE 119, which detects that the eMBB requirements are no longer met due to the link failure, again makes a request to the IAB node 105 for a slice supporting eMBB based on the NSSAI.
[0085] In step S703 , in response to the NSSAI request from the UE 119 , it is detected that the IAB node 105 has become unable to satisfy eMBB.
[0086] In step S704, the IAB node 105 notifies the IAB donor 101 of the change in NSSAI of the slices that the IAB node 105 can support by means of a BAP control message. In step S705, the IAB donor 101 having received the BAP control message from the IAB node detects that the IAB node 105 has become unable to satisfy the eMBB slices.
[0087] In step S706, the IAB donor 101 makes a request for a connection candidate list to the IAB node 105 by means of an RRC control message. In step S707, the IAB node 105 transmits the connection candidate list generated based on the RRM measurement result to the IAB donor 101 by means of an RRC control message.
[0088] In step S708, the IAB donor 101 Figure 4 The flowchart shown in determines the IAB node 102 as a new connection destination based on the connection candidate list of the IAB node 105 and the NSSAI list managed by the slice management unit 306.
[0089] In steps S709 and S710, the IAB donor 101 notifies the IAB node 105 of the multipath connection with the IAB node 102 by means of an RRC control message. Here, the IAB node 102 can be specified as the connection destination by means of an NCL defined by the RRC protocol. In steps S711 and S712, the IAB node 105 transmits an RRC connection reconfiguration message to form an RRC link with the IAB node 102. In step S713, a random access procedure is performed according to the RRC protocol, and an RRC link is established between the IAB nodes 105 and 102. In steps S714 and S715, the IAB node 102 transmits an RRC connection reconfiguration completion message to the IAB node 105.
[0090] In steps S716 and S717, the IAB node 105 notifies the IAB donor 101 of the completion of the multipath connection by means of an RRC control message.
[0091] In step S718, the IAB node 105 notifies the IAB node 104 that its connection is maintained by means of an RRC control message instead of an RRC release message transmitted when the communication path is switched. Although a message when a communication path defined by RRC is changed is used here to establish an RRC link, it is not limited thereto, and any other message may be used. In the above description, each control message may be sent and received by means of BAP and RRC, but this is not necessarily the case. For example, the control message may be controlled by sending and receiving an application layer message.
[0092] Thus, as shown in step S719, the IAB node 105 can support communication in the slice whose slice type is eMBB requested by the UE 119.
[0093] Figure 8 FIG. 1 is a diagram showing the topology of the IAB network after a new communication path has been established according to Embodiment 1. Figure 7 After the sequence shown in , the IAB node 105 establishes a multipath connection using the path 800 to the IAB node 102 and the path 801 to the IAB node 104. The IAB node 105 can use the path 800 to the IAB node 102 to provide communications in the slice supporting eMBB to the UE 119. In addition, the IAB node 105 can continue to maintain the communication path to the IAB node 104 and provide communications in the slice supporting the MIot requested by the UE 118.
[0094] As described above, when an IAB node becomes unable to meet the requirements of a particular slice, the IAB donor 101 instructs the IAB node to establish a communication path to a new connection destination that supports the slice. This makes it possible to recover the slice whose requirements are no longer met.
[0095] Example 2
[0096] In Example 1, it is given that Figure 1 Description of a method of determining a new connection destination when a link failure occurs between IAB nodes 105 and 104 in the wireless communication system 100 shown in FIG.
[0097] In Example 2, the Figure 1Description of a method in which a new connection destination is determined to restore the eMBB slice type requested by UEs 117 and 119 when a communication link failure occurs between IAB nodes 104 and 102 as shown in . Note that the same reference numerals are assigned to the same configurations, functions, and processes as those of Embodiment 1, and a detailed description thereof is omitted.
[0098] Fig. 9 FIG. 1 is a flowchart of determining a new communication path executed by the IAB donor 101 according to Embodiment 2. The IAB donor 101 may start when receiving a BAP control message. Fig. 9 in the processing.
[0099] In step S900, the IAB donor 101 detects an IAB node that does not meet the slice requirement. In this example, the IAB donor 101 receives a BAP control message indicating a change in NSSAI that can support slices from the IAB nodes 104 and 105, and detects that the IAB nodes 104 and 105 do not meet the slice requirement.
[0100] In step S901 , the IAB donor 101 determines that a link failure has occurred between the IAB nodes 104 and 102 based on the routing information stored in the storage unit 202 and the hop counts of the IABs 104 and 105 .
[0101] In step S902 , the IAB donor 101 collects a connection candidate list of the IAB node 104 and a lower-order connected IAB node (ie, the IAB node 105 ).
[0102] For the IAB nodes that do not meet the slicing requirements, the processes in steps S903 to S908 are repeatedly performed in descending order of the number of hops to the IAB donor 101 .
[0103] For each connection candidate of a specific IAB node, the processing in steps S904 to S906 is repeatedly performed. In step S905, the IAB donor 101 determines whether the connection candidate n of the IAB node meets the slicing requirements. If the requirements are met ("Yes" in S905), step S910 is performed. If not ("No" in S905), the process proceeds to step S906.
[0104] Note that in step S905, the IAB donor 101 may determine whether the slice requirement of the communication in the slice requested by the UEs 116 to 119 connected to the IAB nodes 104 and 105 is satisfied. In another example, the IAB donor 101 may determine whether the slice requirement of the communication in the slice requested by the UEs 116 and 117 connected to the IAB node 104 is satisfied only. In this case, the IAB donor 101 may also perform the processing in steps S903 to S908 for the IAB node 105 after giving an instruction of the relay node as the new connection destination to the IAB node 104. That is, the IAB nodes 104 and 105 for which non-satisfaction of the slice requirement has been detected may individually determine a communication path with a new connection destination.
[0105] In step S906, if the processing in step S905 has been performed on all connection candidates, the process proceeds to step S908. If not, the process proceeds to step S907, where the processing in step S905 is performed on the next connection candidate. If in step S908, the processing in steps S904 to S906 has been performed on all IAB nodes that do not meet the slicing requirements, then Fig. 9 If, in step S908, an IAB node that does not satisfy the slicing requirement and has not been subjected to the processing in steps S904 to S906 remains, the process proceeds to step S909, and the processing in steps S904 to S906 is performed on the IAB node 105 that is the next connection candidate n.
[0106] In step S910, the IAB donor 101 transmits an instruction to perform a multipath connection with the connection candidate n to the IAB node by means of an RRC control message.
[0107] In this processing example, if there is no IAB node that is a connection candidate node that can be connected from the IAB node 104 and meets the slicing requirements, an IAB node that is a connection candidate node that can be connected from the IAB node 105 and meets the slicing requirements is determined. If it is determined that there is a connection candidate node that can be connected from the IAB node 105 and meets the slicing requirements, the IAB node 105 is instructed to connect to this IAB node. Here, the IAB node 104 can also be instructed to perform communication through the communication path newly established by the IAB node 105. This makes it possible to restore not only the IAB node 104, but also the slices to be supported by the IAB node 104.
[0108] Fig.10 An example of a connection candidate list of the IAB donor 104 according to Embodiment 2 is shown. Note that the connection candidate list of the IAB node 105 is different from Figure 5 The same as that of Example 1 shown in FIG.
[0109] Fig.11 An updated NSSAI list of IAB nodes is shown after a communication link failure has occurred between the IAB nodes 102 and 104 and slice unsatisfaction has been detected from the IAB nodes 104 and 105 in step S900 .
[0110] The NSSAI lists 1100 and 1101 that no longer support eMBB have been updated in response to the NSSAI change notifications from the IAB nodes 104 and 105 .
[0111] In the connection candidate list 1000, among the connection candidates of the IAB node 104, the IAB node 104 receives the highest radio field strength from the IAB donor 101. In addition, the IAB donor 101 can provide eMBB based on S600. Therefore, in step S905, the IAB donor 101 is selected as the connection destination of the IAB node 104. Here, the IAB donor 101 is included in the connection candidate list.
[0112] The IAB nodes in 1000 are limited to nodes with higher order connections and have higher order connections than IAB nodes 104 and
[0113] In response to this, in step S910, IAB donor 101 instructs IAB node 104 to connect to IAB donor 101, and ends the process. Fig. 9 in the processing.
[0114] Fig.12 FIG. 1 shows the topology of the IAB network after a new communication path is connected according to the second embodiment.
[0115] In the wireless communication system 100, according to Fig. 9 12, a connection between the IAB donor 101 and the IAB node 104 via the path 1200 is established. This allows the IAB node 104 to perform communications in a slice supporting eMBB. In addition, the IAB node 104 can support the eMBB slice type, thereby allowing the IAB node 105 to also support eMBB. This can solve the unsatisfied slice requirements of the IAB node 105. This makes it possible to provide UEs 117 and 119 with communications in a slice supporting eMBB.
[0116] In the description of this embodiment, the unsatisfied slice requirement of the IAB node 105 can be resolved by establishing the path 1200. However, if the unsatisfied slice requirement of the IAB node 105 cannot be resolved even if the path 1200 is established, the BAP control message is again transmitted from the IAB node 105 to the IAB donor 101. In this case, the IAB donor 101 again instructs the IAB node 105 to perform a multipath connection in order to meet the slice requirement.
[0117] Other embodiments
[0118] The multipath connection has been described in Embodiments 1 and 2. However, if a radio link failure (RLF) is notified instead of deterioration of communication quality as a BAP control message, the communication path can be switched to a newly determined connection destination. Note that the switching process is performed in the same manner as when the multipath connection is performed, and in step S717, the RRC release message is transmitted to the original connection destination.
[0119] If the IAB node 102 determined as the new connection destination is a higher-order connected node with respect to the currently connected IAB node 104 as in Embodiment 1, the MIoT requested by the UE 118 is supported, and thus the connection of the communication path can be switched.
[0120] In addition, in Embodiments 1 to 2, a single slice is restored among the IAB nodes 102 to 105. However, in the case where the requirement for more than one slice cannot be met, rescue priority may be given to the slice requested by the maximum number of UEs. In addition, if the slice requested by the maximum number of UEs cannot be restored, a new communication path is determined to restore the slice requested by the next maximum number of UEs.
[0121] In this embodiment, if Figure 5 As shown in , a process of determining a connection destination IAB node based on the received signal strength of a connection candidate node has been given. However, the connection destination IAB node may be determined based on any other type of communication quality instead. For example, which IAB node is the connection destination may be determined based on a parameter related to the communication path between the connection candidate node and the IAB donor 101. The parameter may be at least one combination of the maximum communication capacity, the difference between the maximum communication capacity and the currently used communication capacity, the processing load of the connection candidate node, the free buffer capacity of the connection candidate node, and the processing load of the connection candidate node.
[0122] The present invention can be implemented by supplying a program for implementing one or more functions of the above-mentioned embodiments to a system or device via a network or storage medium, and causing one or more processors in a computer of the system or device to read out and execute the processing of the program. The present invention can also be implemented by a circuit (e.g., ASIC) for implementing one or more functions.
[0123] The present invention is not limited to the above-described embodiments, and various changes and modifications can be made within the spirit and scope of the present invention. Therefore, in order to apprise the public of the scope of the present invention, the following claims are made.
[0124] This application claims priority based on Japanese Patent Application No. 2022-068465 filed on April 18, 2022, the entire contents of which are incorporated herein by reference.
Claims
1. A communication control device for integrated access and backhaul IAB network, characterized in that: The device comprises: A detection component, configured to detect that a first relay node communicating with a base station of a network through a first communication path no longer meets requirements for communication in a specific slice; and An instruction component is used to provide an instruction to connect to a second relay node based on the result of the detection performed by the detection component, wherein the second relay node is located on a second communication path that meets the requirements of communication in a specific slice and can be connected from the first relay node.
2. The communication control device according to claim 1, characterized in that The instruction section identifies the second relay node based on the relay nodes not included in the first communication path.
3. The communication control device according to claim 1 or 2, characterized in that further comprising a storage means for storing connection candidate nodes connectable from the first relay node and communication qualities between the connection candidate nodes and the first relay node in association with each other, If the instruction component identifies multiple relay nodes that can be connected from the first relay node and meet the requirements of communication in a specific slice, the instruction component identifies a relay node with high communication quality relative to the first relay node as a second relay node.
4. The communication control device according to any one of claims 1 to 3, characterized in that Also includes an obtaining means for obtaining a connection candidate list indicating relay nodes connectable from the first relay node, wherein the instruction means identifies a relay node connectable from the first relay node based on the connection candidate list obtained by the obtaining means.
5. The communication control device according to any one of claims 1 to 4, characterized in that In the case where the instruction component cannot identify the second relay node, the instruction component identifies a fourth relay node, the second relay node is located on a second communication path that meets the requirements for communication in the specific slice and can be connected from the first relay node, the fourth relay node can be connected from a third relay node that communicates with the base station via the first relay node and meets the requirements for communication in the specific slice, and The instruction component instructs the third relay node to connect to the fourth relay node.
6. The communication control device according to any one of claims 1 to 5, characterized in that In case the second communication path meets the requirements for communication in the slice to be supported by the first relay node, the instruction component instructs the first relay node to disconnect from the first communication path.
7. The communication control device according to any one of claims 1 to 6, characterized in that In a case where the second communication path includes the first communication path, the instruction section instructs the first relay node to disconnect from the first communication path.
8. The communication control device according to any one of claims 1 to 7, characterized in that Also includes a storage component for storing, for each relay node in the network, satisfied requirements information indicating requirements that can be satisfied in communications in a slice supported by the relay node, and In a case where the satisfaction information stored in the storage component indicates that the first relay node satisfies the requirements for communication in a specific slice, the detection component determines that the first communication path no longer satisfies the requirements for communication in the specific slice in response to receiving a slice request for the specific slice from a user equipment UE assigned to the specific slice and connected to the first relay node.
9. The communication control device according to any one of claims 1 to 8, characterized in that Also includes an obtaining means for obtaining, for each relay node in the network, satisfying requirement information indicating requirements that can be satisfied in communications in a slice supported by the relay node, if the detecting means detects that the first relay node no longer satisfies the requirements for communications in a particular slice, Wherein, based on the requirement satisfaction information obtained by the obtaining component, a relay node with the smallest number of hops to the base station is identified from relay nodes that no longer meet the requirements for communication in a specific slice, and a relay node that can be connected from the identified relay node and meets the requirements for communication in the slice supported by the identified relay node is determined.
10. The communication control device according to any one of claims 1 to 9, characterized in that When the detection component detects that the first communication path no longer meets the communication requirements in multiple slices, the instruction component provides priority to slices requested by a larger number of UEs and provides instructions to connect to a second relay node that meets the communication requirements in the slices provided with priority.
11. A communication control method to be performed by a communication control device for an integrated access and backhaul IAB network, characterized in that, The method comprises: detecting that a first relay node communicating with a base station of a network via a first communication path no longer meets requirements for communication in a particular slice; and Based on the detection result, an instruction to connect to a second relay node is provided, which is located on a second communication path that meets the requirements for communication in the specific slice and can be connected from the first relay node.
12. A program for causing a computer to function as each component of the communication control device according to any one of claims 1 to 10.
