Communication device, method for controlling communication device, and program

Abstract

To provide a communication device, a control method, and a program for reconfiguring a connection route and providing a desired communication service for a user device.SOLUTION: A communication device that functions as a node connected to a user device in an integrated access and backhaul (IAB) network determines whether the type of a network slice requested by the user device is supported by a first other node upstream-connected to the communication device, determines whether there are one or more other nodes that support the network slice type among the one or more other nodes that can be upstream-connected to the communication device when it is determined that the network slice type is not supported by the first other node, and is connected with a second other node among the one or more other nodes that support the network slice type when it is determined that there are one or more other nodes that support the network slice type.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present invention relates to wireless communication technology.

Background Art

[0002] In 3GPP (3rd Generation Partnership Project), the standardization of IAB (Integrated Access and Backhaul) as a communication technology for backhaul is progressing. The IAB technology is a technology that simultaneously uses millimeter-wave wireless communication such as the 28 GHz band used for access communication between a base station and a user equipment (UE (User Equipment)) as backhaul communication (Patent Document 1). In backhaul communication using the IAB technology, a relay device called an IAB node relays communication from an IAB donor that is a base station by millimeter-wave communication. By using the IAB technology, it is possible to expand the area coverage at a lower cost compared to conventional wired communication using optical fibers or the like.

[0003] In backhaul communication, communication from an IAB donor that is a relay source is relayed in order from a parent node to a child node. For example, the IAB donor provides backhaul communication to an IAB node connected to the IAB donor, where the IAB donor is a parent node and the IAB node connected to the IAB donor is a child node. Also, the IAB node relays backhaul communication to an IAB node that is a child node connected to the IAB node, with the IAB donor (relay source) or another IAB node to which the IAB node is connected as the parent node. Also, it is possible for a plurality of IAB nodes to be connected to a parent node, and a tree starting from the IAB donor can be configured.

[0004] When using IAB technology, a wireless link failure (BH RLF (Backhaul Radio Link Failure)) may occur in the link between nodes in a network (IAB network) by backhaul communication, and communication may be interrupted due to the disconnection of the connection between IAB nodes. When a BH RLF occurs, the IAB node can switch the connection to another connectable IAB node and restore communication by re-establishing the network by backhaul communication. Also, even when a BH RLF does not occur, there may be cases where it is necessary to change the already established route due to effects such as deterioration of communication quality between IAB nodes.

[0005] On the other hand, in the next-generation public network, consideration is being given to introducing network slicing technology, which is a technology for providing communication services (network slices) after specifying network characteristics such as bandwidth and delay. As types of network slices, eMBB (enhanced Mobile Broadband) for high-speed large-capacity communication, URLLC (Ultra-Reliable and Low Latency Communications) for low-latency communication, and MIot (Massive Internet of Things) for simultaneous multiple connections have already been standardized.

[0006] As a method for a UE to determine an IAB node (or an IAB donor, which will be described using the IAB node here) to connect to using a desired network slice of the UE, two methods can be considered. The first method is for the UE to request a specific desired network slice from the IAB node. In this case, if the UE is notified of permission for the specific network slice from the IAB node, it can determine to connect to the IAB node using the specific network slice. The second method is for the IAB node to notify (inform) the network slices supported by the IAB node itself. In this case, if the UE can determine that the desired network slice is supported by the IAB node, it can determine to connect to the IAB node using the desired network slice.

Prior Art Documents

Patent Documents

[0007]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0008] However, in a backhaul communication network such as an IAB network, when a desired network slice (communication service) of the UE is not supported on the route to which the UE connects, there is a problem that the desired network slice is not provided to the UE.

[0009] The present invention has been made in view of the above problems, and an object thereof is to provide a mechanism for providing a desired communication service of a user device to the user device by reconfiguring a connection route.

Means for Solving the Problems

[0010] As one means for achieving the above object, a communication device according to an aspect of the present invention has the following configuration. That is, a communication device that functions as a node connected to a user device in an IAB (Integrated Access and Backhaul) network, and determines whether the type of network slice requested by the user device is supported by a first other node that is hierarchically connected to the communication device. Obtain a predetermined signal to be shown to do Obtain means, and the Obtain When the type of the network slice is not supported by the first other node by the means, The predetermined signal indicating that has been obtained the communication device Connect to determines whether there is one or more other nodes that support the type of the network slice among one or more other nodes to which connection can be continued. Search to do Search means and , before recording Search When one or more other nodes that support the type of the network slice are Discover found, connection means for connecting to a second other node among one or more other nodes that support the type of the network slice.

Advantages of the Invention

[0011] According to the present invention, by reconfiguring the connection route, it becomes possible to provide a desired communication service of a user device to the user device.

Brief Description of the Drawings

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Modes for Carrying Out the Invention

[0013] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims. Although a plurality of features are described in the embodiments, not all of these plurality of features are essential to the invention, and the plurality of features may be arbitrarily combined. Further, in the accompanying drawings, the same or similar configurations are denoted by the same reference numerals, and redundant descriptions are omitted.

[0014] [Embodiment 1] (Configuration of Communication System) FIG. 3 is a diagram showing a configuration example of a backhaul communication system (hereinafter, communication system) according to Embodiment 1. The communication network by the backhaul communication may include an NR (New Radio) backhaul link and an NR access link. Here, it will be described as a communication system using IAB (Integrated Access and Backhaul) technology. In communication system 300, there are an IAB donor 302 and an IAB donor 306 that provide connections to a core network (CN) 301. The IAB donor 302 and the IAB donor 306 provide connections to the core network 301 via backhaul communication to IAB nodes connected to themselves as child nodes (that is, provide backhaul communication). An IAB node 303 is connected to the IAB donor 302 as a child node. Further, an IAB node 304 and an IAB node 305 are connected to the IAB node 303 as child nodes. Further, an IAB node 309 is connected to the IAB node 305 as a child node. On the other hand, an IAB node 307 is connected to the IAB donor 306 as a child node, and an IAB node 308 is connected to the IAB node 307 as a child node. Each IAB donor and IAB node functions as a radio base station device.

[0015] A UE (User Equipment) 310 that communicates in a cell area 311 of a cell provided by the IAB node 309 can be connected to the core network 301 via each IAB donor or IAB node. In the initial state, in the communication system shown in FIG. 3, it is assumed that the UE 310 is connected to the IAB node 309, which is the IAB node with the highest radio wave intensity for the UE 310. As an example of the radio wave intensity, there are an RSRP (Reference Signal Received Power) value, an RSCP (Received Signal Code Power) value, and the like.

[0016] The IAB node 309 is assumed to be able to communicate with the IAB nodes 304, 305, and 308 in the upper (upward) direction (the upward direction indicates the direction towards the core network 301). In the initial state, the IAB node 309 is only connected to the IAB node 304 (connection 1), and it is assumed that the connections with the IAB node 305 (connection 2) and the IAB node 308 (connection 3) are not established. In this embodiment, the IAB node 309 can change the connection from connection 1 to connection 2 or connection 3 when the IAB node 304 does not support the type of network slice required by the UE 310.

[0017] (Hardware Configuration and Functional Configuration of IAB Node) The configuration (hardware configuration and software functional configuration) of the IAB node (RAN (Radio Access Network) node) according to this embodiment will be described. FIG. 1 shows an example of the hardware configuration of the IAB node. The control unit 101 is composed of one or more CPUs (Central Processing Units) or the like, and controls the entire device by executing a control program stored in the storage unit 102. The storage unit 102 is composed of storage means such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and stores a control program executed by the control unit 101 and various information such as cell information, connected terminal information, and IAB routing information. Various operations to be described later can be performed by the control unit 101 executing the control program stored in the storage unit 102. Further, in the storage unit 102, a PLMN (Public Land Mobile Network) ID (Identity), which is an ID capable of identifying a communication carrier, can be set and stored (registered) by the communication carrier. The wireless communication unit 103 performs wireless communication such as cellular network communication such as LTE (Long Term Evolution) and 5G (5th Generation) compliant with the 3GPP (3rd Generation Partnership Project) standard. The antenna control unit 104 controls the antenna 105 for the wireless communication performed by the wireless communication unit 103.

[0018] FIG. 2 shows an example of the software functional configuration of the IAB node. The transmission unit 201 transmits various signals (including frames and information) to other communication devices (communication partner devices) via the wireless communication unit 103 (FIG. 1). The reception unit 202 receives various signals from other communication devices via the wireless communication unit 103.

[0019] The signal generation unit 203 generates various signals transmitted via the transmission unit 201. For example, the signal generation unit 203 generates a notification signal (notification information) including NSSAI (Network Slice Selection Assistance Information) transmitted via the transmission unit 201. The NSSAI is composed of one or more SSTs (Slice / Service type) indicating the type of network slice (hereinafter simply referred to as slice type). The NSSAI included in the notification signal indicates the slice types supported by the IAB node. As the slice types, eMBB (enhanced Mobile Broadband) for high-speed large-capacity communication, URLLC (Ultra-Reliable and Low Latency Communications) for low-latency communication, and MIot (Massive Internet of Things) for simultaneous multiple connections have already been standardized. The notification signal may include information for identifying the IAB donor to which the IAB node is connected. The notification signal generated by the signal generation unit 203 is periodically transmitted (notified) by the transmission unit 201 in the communicable area (cell area) provided by the IAB node. In addition, the signal generation unit 203 can generate a notification signal for notifying a specific destination. The notification signal can also include the NSSAI.

[0020] The connection control unit 204 performs connection control with other communication devices through communication via the transmission unit 201 and the reception unit 202. For example, the connection control unit 204 executes processes related to connection and disconnection with other communication devices by communicating RRC (Radio Resource Control) messages via the transmission unit 201 and the reception unit 202.

[0021] The slice type confirmation unit 205 confirms the slice types that the IAB node itself can support. The slice types that the IAB node itself can support can be determined by the NSSAI notified by other IAB nodes or IAB donors that are connected to the IAB node at a higher level (upward). That is, the IAB node can support the slice types included in the NSSAI notified by other IAB nodes or IAB donors that are connected to the IAB node at a higher level. The notification signal confirmation unit 206 confirms the slice types supported by the other IAB node (or IAB donor) based on the notification signal (notification information) from the other IAB node (or IAB donor) received by the reception unit 202.

[0022] Note that the IAB donor can also have the same hardware configuration (Figure 2) and software function configuration (Figure 3) as the IAB node. However, the IAB donor does not necessarily need to include the notification signal confirmation unit 206.

[0023] (Flow of processing) Subsequently, the operation of the IAB node connected to the UE will be described. Figure 4 shows a flowchart of the processing executed by the IAB node according to the present embodiment. The flowchart shown in Figure 4 can be realized by the control unit 101 of the IAB node executing the control program stored in the storage unit 102 and performing operations and processing of information and controlling each hardware.

[0024] Here, assuming the communication system 300 shown in Figure 3, the processing by the IAB node 309 will be described. Also, it is assumed that the IAB node 309 is connected to the IAB node 304 (Connection 1). Also, as described above, it is assumed that the UE 310 is connected to the IAB node 309, which is the IAB node with the highest radio wave intensity for the UE 310 in the cell area 311 in the initial state.

[0025] In the S400, the receiving unit 202 of the IAB node 309 receives a slice type request signal from the UE 310. The request signal includes an NSSAI for indicating the requested slice type. As described above, the NSSAI is composed of one or more SSTs (Slice / Service type) indicating the slice type. The NASSI included in the request signal indicates the slice type requested by the UE 310.

[0026] Subsequently, in S401, the slice type confirmation unit 205 of the IAB node 309 checks (determines) whether the slice type in the NSSAI included in the received request signal is included in the slice types supported by the IAB node 309. That is, the slice type confirmation unit 205 determines whether the IAB node 309 supports the slice type requested by the UE 310. As described above, the IAB node can support the slice types included in the NSSAI notified from other IAB nodes or the IAB donor that are hierarchically connected to the IAB node. Therefore, in S401, the slice type confirmation unit 205 of the IAB node 309 determines whether the IAB node 304 hierarchically connected to the IAB node 309 supports the slice type requested by the UE 310. If the IAB node supports the slice type requested by the UE 310 (Yes in S401), the process proceeds to S402; otherwise (No in S401), the process proceeds to S403.

[0027] Proceeding to S402 means that the communication path / route between the IAB node 309 and the IAB donor 302 (the communication path between one or more IAB nodes through which the IAB node 309 is connected to the IAB donor 302) supports the slice type requested by the UE. Therefore, in S402, the IAB node 309 maintains the connection, that is, allows the UE 310 to use the communication path to which the UE 310 is connected, and ends the process.

[0028] After S403, it is processing based on a notification signal notified from another IAB node and received by the receiving unit 202 of the IAB node 309. The notification signal is assumed to include a NASSI including a slice type that can be supported by the source IAB node or IAB donor, and information for identifying the IAB donor to which the source IAB node is connected (the IAB donor itself if the source is an IAB donor).

[0029] In S403, the notification signal confirmation unit 206 of the IAB node 309 checks (determines) whether an upper-connectable IAB node under the same IAB donor as the IAB donor in the connection route of the IAB node 309 supports the slice type requested by the UE 310. Specifically, the notification signal confirmation unit 206 checks (determines) whether the NASSI included in the notification signal notified from the IAB node under the IAB donor 302 includes the slice type requested by the UE 310. If an IAB node under the same IAB donor supports the slice type requested by the UE 310 (the slice type requested by the UE 310 is included in the NASSI from the IAB node under the IAB donor 302) (Yes in S403), the process proceeds to S406. Otherwise (No in S403), the process proceeds to S404.

[0030] In S404, the notification signal confirmation unit 206 of the IAB node 309 checks (determines) whether an upper-connectable IAB node under an IAB donor different from the IAB donor in the connection route of the IAB node 309 supports the slice type requested by the UE 310. Specifically, the notification signal confirmation unit 206 checks (determines) whether the NASSI included in the notification signal notified from the IAB node under the IAB donor 306 includes the slice type requested by the UE 310. If an IAB node under a different IAB donor supports the slice type requested by the UE 310 (the slice type requested by the UE 310 is included in the NASSI from the IAB node under the IAB donor 306) (Yes in S404), the process proceeds to S406. Otherwise (No in S404), the process proceeds to S405.

[0031] Through the processes of S403 and S404, the IAB node 309 will preferentially select and connect to the nodes under the IAB donor in the route to which the IAB node 309 is connected.

[0032] In S405, the signal generation unit 203 of the IAB node 309 generates a notification signal indicating that there is no IAB node that supports the slice type requested by the UE 310, and the transmission unit 201 notifies (transmits) this to the UE 310, and the process ends.

[0033] In S406, the connection control unit 204 of the IAB node 309 performs a connection switching process to a higher-level IAB node that supports the slice type requested by the UE 310. For example, if the IAB node 304 does not support the slice type requested by the UE 310 (No in S401), but the IAB node 305 supports it (Yes in S403), the IAB node 309 disconnects from the IAB node 304 and establishes a connection with the IAB node 305.

[0034] After that, the process proceeds to S407, and the connection control unit 204 of the IAB node 309 generates a new communication path to a higher-level IAB node / IAB donor that supports the slice type requested by the UE 310, and the process ends.

[0035] As described above, the IAB node 309 can connect to a higher-level node that satisfies the slice type requested by the UE 310. That is, by connecting to a higher-level node that provides the slice type requested by the UE 310 according to the communication situation and topology, it becomes possible to provide the communication service requested by the UE 310.

[0036] Here, the IAB node 309 is used as an example for explanation. However, the same explanation can be applied not only when the node to which the IAB node is hierarchically connected is an IAB node but also when it is an IAB donor. For example, assume a case where a UE (not shown) is connected to the IAB node 303. In this case, the IAB node 303 can confirm, in S403, based on the notification signal, whether the IAB donor 302 supports the slice type requested by the UE. Further, the IAB node 303 can confirm, in S404, based on the notification signal, whether the IAB donor 306 supports the slice type requested by the UE. Also, the IAB node 309 may newly connect to the IAB donor 306 based on the notification signal from the IAB donor 306.

[0037] Also, in this embodiment, it has been described assuming that the UE connected to the IAB node 309 is only the UE310. However, when another UE is connected to the IAB node 309, the IAB node 309 may switch the connection with the UE310 and maintain the connection with the other UE.

[0038] Also, when the answer is No in S404, the IAB node 309 may newly connect to another IAB node / IAB donor with high radio wave intensity with respect to the IAB node 309, and / or maintain the connection with the connected IAB node 304.

[0039] Also, after the IAB node 309 establishes a connection with the IAB node 305 in S406 and S407, the UE310 may disconnect the connection with the IAB node 309 due to the end of the application or the like. At this time, for example, if there is no other UE that uses the slice type requested by the UE310 among the plurality of UEs connected to the IAB node 309, the IAB node 309 may disconnect the connection with the IAB node 305.

[0040] (Operations in the communication system) FIG. 5 is a diagram showing a communication sequence in the communication system 300 according to the present embodiment. Here, the operation until the UE 310 connects to the IAB node 309 and the IAB node 309 switches the connection to the communication path to the upper IAB node 305 that supports the slice type requested by the UE 310 from the IAB node 304 will be described. As described above, in the present embodiment, it is assumed that the IAB node can support the slice types included in the NSSAI notified from other IAB nodes or the IAB donor that are connected above the IAB node.

[0041] In F501, the IAB donor 302 that supports the eMBB and URLLC slices connects to the IAB node 303 and notifies the IAB node 303 of the NSSAI indicating the eMBB and URLLC slice types. Thereby, the IAB node 303 will support the eMBB and URLLC slice types.

[0042] Subsequently, in F502, the IAB node 303 connects to the IAB node 304 and notifies the IAB node 304 of the NSSAI indicating the eMBB slice type. For example, based on the information received from the IAB donor, the IAB node 303 determines that the IAB node 304 can support eMBB, and thus notifies the IAB node 304 of the NSSAI indicating the eMBB slice type. Thereby, the IAB node 304 will support the eMBB slice type.

[0043] Also, in F503, the IAB node 303 connects to the IAB node 305 and notifies the IAB node 305 of the NSSAI indicating the URLLC slice type. For example, based on the information received from the IAB donor, the IAB node 303 determines that the IAB node 305 can support URLLC, and thus notifies the IAB node 305 of the NSSAI indicating the URLLC slice type. Thereby, the IAB node 305 will support the URLLC slice type.

[0044] In F504, the IAB node 304 connects to the IAB node 309 and notifies the IAB node 309 of the NSSAI indicating the slice type of eMBB. Thereby, the IAB node 309 will support the slice type of eMBB.

[0045] Next, in F505, the UE 310 sends a connection request to the IAB node 309 which is the IAB node with the highest radio intensity for the UE 310, and the IAB node 309 permits this, and connection processing is performed between the UE 310 and the IAB node 309. At this time, the UE 310 sends a request signal including the NSSAI indicating URLLC which is the slice type to be requested to the IAB node 309.

[0046] When the IAB node 309 receives the said request signal, it determines whether the IAB node 309 and the IAB node 304 which is hierarchically connected to the IAB node 309 support the slice type of URLLC (S401 in FIG. 4). In this example, the IAB node 309 and the IAB node 304 do not support the slice type of eMBB (No in S401). Therefore, the IAB node 309 searches for an IAB node that supports URLLC based on the NASSI which is the information included in the notified notification signal. In F506, the IAB node 309 confirms that URLLC is included in the NASSI included in the notification signal notified from the IAB node 305 (Yes in S403). That is, the IAB node 309 confirms that the IAB node 305 supports URLLC.

[0047] Since the IAB node 305 supports URLLC, in F507, the IAB node 309 and the IAB node 305 perform synchronization establishment and RACH (Random Access Channel) processing. Thereafter, in F508, the IAB node 309 connects to the IAB node 305 through RRC connection.

[0048] In F509, since the IAB donor 302 manages the routing information with the IAB nodes connected below it, it updates the routing information between the IAB donor 302 and the IAB node 309. Specifically, it is updated from the routing information via the IAB nodes 303 and 304 to the routing information via the IAB nodes 303 and 305. Thereafter, the UE 310 can communicate via the network using the slice type of URLLC requested by the UE 310.

[0049] In addition, in F506 of this sequence, the IAB node 309 searched for an IAB node that supports URLLC based on the NSSAI included in the notification signal from the upper IAB node (which may also be an IAB donor), but it may be searched by inquiry. For example, the IAB node 309 may inquire of the upper IAB node about the availability of support for URLLC, which is the slice type requested by the UE 310, and search for an IAB node corresponding to the URLLC slice based on the response of the notification information of the upper IAB node.

[0050] Thus, according to this embodiment, even when the IAB node connected to the UE does not support the communication service (slice type) requested by the UE, it is possible to provide the communication service to the UE by establishing a new route.

[0051] [Embodiment 2] In Embodiment 1, a control method for switching the connection to another IAB node that supports (meets) the slice type requested by the UE connected to the IAB node was described. In Embodiment 2, a control method for the IAB node to connect to an IAB node that meets the slice type newly requested by the UE while maintaining the connection with the connected IAB node will be described. Note that in this embodiment, descriptions of matters common to Embodiment 1 are omitted.

[0052] (Flow of processing) FIG. 6 shows a flowchart of the processing executed by the IAB node according to the present embodiment. The flowchart shown in FIG. 6 can be realized by the control unit 101 of the IAB node executing the control program stored in the storage unit 102 and performing the calculation and processing of information and the control of each hardware.

[0053] Here, assuming the communication system 300 shown in FIG. 3, the processing by the IAB node 309 will be described. Also, it is assumed that the IAB node 309 is connected to the IAB node 304 (connection 1). Further, it is assumed that the UE 310 is connected to the IAB node 309 which is the IAB node with the highest radio wave intensity for the UE 310 in the cell area 311.

[0054] The processes of S600 to S605 are the same as those of S400 to S405 in FIG. 4 described in the first embodiment, and thus the description thereof will be omitted. In S606, the connection control unit 204 of the IAB node 309 maintains the connection with the upper IAB node 304 that is currently connected, and also performs a connection process with a new IAB node 305 that supports the slice type requested by the UE 310. Thereby, the IAB node 309 also generates a communication path with a new upper IAB node that supports the slice type requested by the UE, and ends the process.

[0055] As described above, according to the present embodiment, even when the IAB node connected to the UE does not support the communication service (slice type) requested by the UE, it is possible to provide the communication service to the UE by establishing a new route while maintaining the current route.

[0056] [Other Embodiments] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. Further, it can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

[0057] The invention is not limited to the above embodiments, and various changes and modifications are possible without departing from the spirit and scope of the invention. Therefore, the claims are appended to disclose the scope of the invention.

Description of Reference Numerals

[0058] 300 Communication system, 301 Core network, 302;306 IAB donor, 303;304;305;307;308;309 IAB node, 310 UE, 311 Cell area

Claims

1. A communication device that functions as a node connected to a user device in an IAB (Integrated Access and Backhaul) network, an acquisition means for acquiring a predetermined signal indicating whether the type of network slice requested by the user device is supported by a first other node connected to the communication device; a search means for searching whether there is one or more other nodes that support the type of network slice among one or more other nodes connectable to the communication device when the predetermined signal indicating that the type of network slice is not supported by the first other node is acquired by the acquisition means; a connection means for connecting to a second other node among one or more other nodes that support the type of network slice when one or more other nodes that support the type of network slice are discovered by the search means; A communication device characterized by comprising the above.

2. The communication device according to claim 1, further comprising a determination means for determining whether the type of network slice is supported by the first other node based on the predetermined signal acquired from the first other node.

3. The communication device according to claim 1 or 2, further comprising a second determination means for determining whether there is a node that supports the type of network slice based on a signal notified from one or more other nodes connectable to the communication device.

4. The search means queries one or more other nodes connectable to the communication device about the availability of support for the type of network slice, and searches for a node that supports the type of network slice based on the response signal of the query. The communication device according to claim 1 or 2, characterized in that.

5. The connection means disconnects the connection with the first other node and connects to the second other node. The communication device according to any one of claims 1 to 4, characterized in that.

6. The connection means maintains the connection with the first other node and connects to the second other node. The communication device according to any one of claims 1 to 4, characterized in that.

7. The connection means preferentially determines, as the second other node, a node under an IAB donor in a route to which the communication device is connected among one or more other nodes that support the type of the network slice, and connects to the node. The communication device according to any one of claims 1 to 6, characterized in that.

8. The communication device according to any one of claims 1 to 6, characterized in that at least one of the first other node and the second other node functions as an IAB donor.

9. The communication device according to any one of claims 1 to 8, further comprising notification means for notifying the user device that there is no node that supports the type of the network slice when the one or more other nodes are not discovered by the discovery means.

10. A control method for a communication device that functions as a node connected to a user device in an IAB (Integrated Access and Backhaul) network, An acquisition step of acquiring a predetermined signal indicating whether the type of the network slice requested by the user device is supported by a first other node that is hierarchically connected to the communication device; When the predetermined signal indicating that the type of the network slice is not supported by the first other node is acquired in the acquisition step, a search step of searching for one or more other nodes that support the type of the network slice among one or more other nodes connectable to the communication device; A connection step of connecting to a second other node among one or more other nodes that support the type of the network slice when one or more other nodes that support the type of the network slice are discovered in the search step; A control method characterized by comprising:

11. A program for causing a computer to function as the communication device according to any one of claims 1 to 9.

Images