Communication device, method for controlling communication device, program

Abstract

To appropriately determine and convey information about a network slice that can be supported by a node.SOLUTION: A communication device that functions as a base station in a communication network receives, from a node that relays communication between the communication device and a user device, first information about a route between the node and the communication device and second information about a status at the node, determines the type of network slice supported by the node on the basis of the first information and the second information, and notifies the node of the determined type of network slice.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) as backhaul communication (Patent Document 1). By applying the IAB technology, it is possible to expand the area coverage at low cost compared to conventional wired communication using optical fibers or the like, and thus it is expected as an effective technology for constructing the next-generation public network.

[0003] In backhaul communication using the IAB technology, a relay device called an IAB node relays communication from an IAB donor corresponding to a conventional base station by millimeter-wave communication. Further, the IAB node can form a bearer with a plurality of other IAB nodes and form a network tree (IAB network) starting from the IAB donor, thereby expanding the area. The IAB node as an extension means for expanding the area of the IAB donor can be controlled via BAP (Backhaul Adaptation Protocol), which is a routing protocol for IAB.

[0004] On the other hand, in next-generation public networks, consideration is underway for introducing the concept of network slicing, which virtually provides network slices corresponding to the requirements of multiple different services on a common network. 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 defined.

[0005] For example, Patent Document 2 discloses a method in which a UE transmits a request for a network slice to a base station, and the base station responds as to whether it supports it, enabling the UE to receive a desired service. In this way, consideration is being given to a mechanism that allows a UE to select and make available the network slices provided by the base station according to the purpose.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0007] In the BAP (Backhaul Adaptation Protocol), there is no clear regulation on the operation of network slices in communication networks such as IAB networks. Therefore, in the case of an IAB network, an IAB node will directly notify the NSSAI (Network Slice Selection Assistance Information) received from the connected IAB donor to the lower-level IAB nodes and UEs as it is. Note that the NSSAI is information in which the SST (Slice / Service type), which indicates the types of network slices that can be supported, is shown in a list format.

[0008] Under such an operation, for example, an IAB node far from the IAB donor can only notify the same NSSAI as the IAB donor even if it does not have a configuration to support the network slices supported by the IAB donor. As a result, a UE that receives the notified NSSAI may not be provided with the desired quality even if it selects and requests the network slice it wants to use.

[0009] The present invention has been made in view of the above problems, and an object thereof is to appropriately determine and transmit information on network slices that can be supported by a node.

Means for Solving the Problems

[0010] As one means for achieving the above object, a communication device of the present invention has the following configuration. That is, a communication device that functions as a base station in a communication network, a receiving means for receiving, from a node that relays communication between the communication device and a user device, first information regarding a path between the node and the communication device and second information regarding a status of the node, a determining means for determining a type of network slice supported by the node based on the first information and the second information, and a notifying means for notifying the node of the determined type of network slice. [Effect of the Invention]

[0011] According to the present invention, it becomes possible to appropriately determine and transmit information on network slices that can be supported by nodes. [Brief Description of the Drawings]

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

[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. 1 is a diagram showing an 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. In communication system 100, there is an IAB (Integrated Access and Backhaul) donor 101 that provides connection to a core network (Core Network (CN)) 130. The IAB donor 101 forms an IAB network (communication network) consisting of the IAB donor 101 and IAB nodes 102 to 105. Each IAB donor can function as a radio base station device in the communication network. Also, each IAB node can also function as a radio base station device.

[0015] The IAB donor 101 comprehensively controls each of the IAB nodes 102 to 105 and forms an area covered by the IAB donor 101 itself. The UEs 110 to 119 are connected to the IAB donor or an IAB node to perform communication according to a desired application. In the initial state, as shown in FIG. 1, the UEs 110 to 119 are in a state of being connected to the IAB donor 101 or the IAB nodes 102 to 105 having the highest radio wave intensity for each of them. Note that, 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] At the time of the initial construction of the IAB network, the type of network slice (SST (Slice / Service Type); hereinafter, simply referred to as slice type) that can be supported in each of the IAB nodes 102 to 105 has not yet been determined. The slice types that can be supported in the IAB nodes 102 to 105 are determined by the IAB donor 101 that oversees the communication system 100 and are notified to each of the IAB nodes 102 to 105.

[0017] The IAB donor 101 and each IAB node 102-105 notify the UE 110-119 of the determined slice type together with the cell ID (identifier) corresponding to the IAB donor 101 / each IAB node 102-105. Note that the information notified together with the slice type is not limited to the cell ID, and any information that can identify (distinguish) the IAB donor 101 / each IAB node 102-105, which is the notification source of the slice type, may be used.

[0018] Based on the received slice type / cell ID, each UE 110-119 can determine whether the slice type desired to be used according to the application to be executed is supported by the IAB donor 101 or the IAB nodes 102-105, and perform a connection or connection change. Alternatively, each UE 110-119 may request the IAB donor 101 and the IAB nodes 102-105 for the slice type desired to be used, and perform a connection or connection change based on the response to the request.

[0019] (Configuration of IAB Donor / IAB Node) Next, the configurations of the IAB donor 101 and the IAB nodes 102-105 will be described. FIG. 2 is a block diagram showing an example of the hardware configuration of the IAB donor 101. Here, the description of the hardware configuration assuming the IAB donor 101 will be given, but the IAB nodes 102-105 can also have the same hardware configuration as that in FIG. 2.

[0020] As an example of the hardware configuration, the IAB donor 101 includes a control unit 201, a storage unit 202, a wireless communication unit 203, an antenna control unit 204, and an antenna 205. The control unit 201 controls the entire device by executing a control program stored in the storage unit 202. The control unit 201 is composed of, for example, one or more CPUs (Central Processing Units) or MPUs (Micro Processing Units).

[0021] The storage unit 202 is composed of a ROM (Read Only Memory), a RAM (Random Access Memory), etc. The storage unit 202 stores a control program executed by the control unit 201, and various information such as cell IDs, UE information to be connected, and routing information of subordinate IAB nodes (IAB nodes 102 to 105 in FIG. 1). Further, the storage unit 202 may store information on network slices (slice types) supported by the IAB donor 101. Various operations described later may be performed by the control unit 201 executing the control program stored in the storage unit 202.

[0022] The wireless communication unit 203 is a wireless communication unit for performing cellular network communication such as LTE (Long Term Evolution) and 5G (5th Generation) compliant with 3GPP (3rd Generation Partnership Project) standards. In the antenna control unit 204, the antenna 205 used for wireless communication executed in the wireless communication unit 203 is controlled. The antenna 205 may be composed of a plurality of antennas.

[0023] FIG. 3 is a block diagram showing an example of the software functional configuration of the IAB donor 101 according to the present embodiment. The IAB donor 101 includes, as an example of the software functional configuration, a signal transmission unit 301, a signal reception unit 302, a storage control unit 303, a connection control unit 304, a slice type determination unit 305, and a signal generation unit 306. Here, an explanation of the software functional configuration assuming the IAB donor 101 will be given, and the IAB nodes 102 to 105 will be described later.

[0024] The signal transmission unit 301 and the signal reception unit 302 control the wireless communication unit 203 and the antenna control unit 204 via the control unit 201, and perform cellular network communication (transmission and reception respectively) such as LTE and 5G compliant with 3GPP standards with other communication devices (IAB nodes and UEs). The storage control unit 303 controls (stores / reads out, etc.) and manages various data stored in the storage unit 202. The connection control unit 304 controls the connection with other communication devices, for example, by communication via the signal transmission unit 301 and the signal reception unit 302.

[0025] The slice type determination unit 305 determines the slice types of the IAB nodes 102 to 105 based on the path information and status information received (acquired) from the IAB nodes 102 to 105 via the signal reception unit 302. In the present embodiment, the slice type determination unit 305 acquires the path information and status information from each of the IAB nodes 102 to 105, and determines the slice types of the IAB nodes 102 to 105 respectively. In the present embodiment, the path information can refer to (include) the number of hops from the IAB donor 101 to each of the IAB nodes 102 to 105, and information related to routing in the IAB nodes 102 to 105. Also, the status information can refer to (include) the value of SNR (Signal to Noise Ratio) as the received signal quality, the number of connected UEs, specification information (whether it supports TSN (Time-Sensitive Networking)), etc. in each of the IAB nodes 102 to 105. TSN is a network technology that enables the interoperability between industrial networks that extend standard Ethernet and IT networks. Note that in the present embodiment, SNR is used, but information indicating other received signal qualities may be used instead of SNR.

[0026] The signal generation unit 306 generates packets (signals) for notifying / informing various information to the IAB nodes 102 to 105 and the UEs 110 to 119. The signal generation unit 306 in the IAB donor 101 generates two types of packets.

[0027] As the first type of packet, the signal generation unit 306 generates a control packet for notifying the slice type determined by the slice type determination unit 305 to the IAB nodes 102 to 105. In the present embodiment, the slice type is notified by a control packet using the BAP (Backhaul Adaptation Protocol). However, this is not restrictive, and other control packets may be used. For example, when the IAB nodes 102 to 105 can interpret the RRC (Radio Resource Control) protocol, the slice type may be notified by a control packet using the RRC protocol or a protocol of a communication layer above the RRC layer in the protocol hierarchy.

[0028] As the second type of packet, the signal generation unit 306 generates a notification packet for notifying the UE 110 to 119 of the cell ID that can identify the IAB donor 101 together with the slice type determined by the slice type determination unit 305.

[0029] Next, the software function configuration of the IAB nodes 102 to 105 according to the present embodiment will be described. The software function configuration of the IAB nodes 102 to 105 may be the same as the software configuration of the IAB donor 101 described with reference to FIG. 3. However, in the above description regarding FIG. 3, other communication devices (IAB nodes and UEs) are read as other devices (IAB donors and UEs). Also, the IAB nodes 102 to 105 do not have a slice type determination unit 305, and the signal generation unit 306 does not generate the first type of packet described above. The signal generation unit 306 generates a notification packet for notifying the UE 110 to 119 of the cell ID that can identify each of the IAB nodes 102 to 105 together with the slice type notified from the IAB donor 101. The connection control unit 304 can perform control for link connection / release with the UE.

[0030] (Slice Type Determination Procedure by IAB Donor) FIG. 4 is a flowchart showing a process for determining the slice type of an IAB node by IAB according to the present embodiment. It is assumed that the IAB donor 101 supports all slice types of high-speed large-capacity (eMBB (enhanced Mobile Broadband)), low latency (URLLC (Ultra-Reliable and Low Latency Communications)), and simultaneous multiple connections (MIot (Massive Internet of Things)). Information on the supported slice types can be stored in the storage unit 202. In the present embodiment, it is assumed that the IAB nodes 102 to 105 can support MIot.

[0031] The processes between S400 and S411 are repeated to determine the slice type for all the IAB nodes 102 to 105 having the IAB donor 101 as the root. In the present embodiment, as a non-limiting example, the IAB donor determines the slice type in ascending order of the number of hops from the IAB donor 101. Although the number of hops from the IAB donor 101 to the IAB nodes 102 and 103 is the same, in the present embodiment, the IAB donor 101 determines the slice type in the order of the IAB nodes 102, 103, 104, and 105. Hereinafter, the IAB node for which the slice type is determined in one loop between S400 and S411 is referred to as the target IAB node.

[0032] After the connection control unit 304 establishes a connection with the target IAB node, in S401, the slice type determination unit 305 acquires the path information and status information of the target IAB node. Note that the slice type determination unit 305 may collect information on all the IAB nodes 102 to 105 in advance outside the loop of S400 to S411.

[0033] S402 to S405 are processes for determining whether the target IAB node supports high-speed and large-capacity communication (eMBB in this embodiment) as a slice type. In S402, the slice type determination unit 305 determines whether the SNR value included in the status information acquired from the target IAB node is equal to or greater than a first specified value. The SNR can be the SNR between the target IAB node and the node (parent node) connected above (upward). Here, the first specified value is a value preset to satisfy the communication speed (data rate) at which eMBB communication is possible. If the SNR value is equal to or greater than the first specified value (Yes in S402), the process proceeds to S403; otherwise (No in S402), the process proceeds to S406.

[0034] In S403, the slice type determination unit 305 determines whether the total number of UEs connected between the IAB donor 101 and the target IAB node (the total number of connected UEs in the IAB donor 101 and the target IAB node) is equal to or less than a second specified value. In the case of the communication system 100 shown in FIG. 1, when the target IAB node is the IAB node 102, the total number of connected UEs is 3, and when the target IAB node is the IAB node 104, the total number of connected UEs is 5. In this embodiment, the second specified value is 4, but other values may also be used. If the total number of connected UEs is equal to or less than the second specified value (Yes in S403), the process proceeds to S404; otherwise (No in S403), the process proceeds to S406.

[0035] In S404, the slice type determination unit 305 determines whether the node (parent node) that is connected to the target IAB node in the upper (upward) direction supports eMBB based on the acquired status information and the information stored in the storage unit 202. When the target IAB node is the IAB node 102, the parent node is the IAB donor 101, and when the target IAB node is the IAB node 104, the parent node is the IAB node 102. That is, the parent node can be the IAB donor 101 or another IAB node different from the target IAB node that is directly connected to the target IAB node between the target IAB node and the IAB donor 101. If the parent node supports eMBB (Yes in S404), the process proceeds to S405, and if not (No in S404), the process proceeds to S406.

[0036] In S405, the signal generation unit 306 adds eMBB to the NSSAI (Network Slice Selection Assistance Information). As described above, the NSSAI is information in which the supportable slice types (SSTs (Slice Service Types)) are shown in a list format. Specifically, the signal generation unit 306 sets the SST value corresponding to eMBB to the information element of the NSSAI.

[0037] S406 to S409 are processes for determining whether the target IAB node supports low-latency communication (URLLC in this embodiment) as a slice type. In S406, the slice type determination unit 305 determines whether the target IAB node supports TSN (Time-Sensitive Networking) based on the status information acquired from the target IAB node. If the target IAB node supports TSN (Yes in S406), the process proceeds to S407, and if not (No in S406), the process proceeds to S410.

[0038] In S407, the slice type determination unit 305 determines whether the number of hops from the IAB donor 101 to the target IAB node is less than or equal to a third specified value based on the path information acquired from the target IAB node. When the target IAB node is the IAB node 102, the number of hops is 1. In the present embodiment, the third specified value is set to 2 and the following description will be made based on this. If the number of hops is less than or equal to the third specified value (Yes in S407), the process proceeds to S408; otherwise (No in S407), the process proceeds to S410. In S408, the slice type determination unit 305 determines whether the parent node supports URLLC based on the acquired status information and the information stored in the storage unit 202. S408 is the same process as S404 although the target for determining support is different. If the parent node supports URLLC (Yes in S408), the process proceeds to S409; otherwise (No in S408), the process proceeds to S410. In S409, the signal generation unit 306 adds URLLC to the NSSAI. Specifically, the signal generation unit 306 sets the SST value corresponding to URLLC in the information element of the NSSAI. In the subsequent S410, the signal generation unit 306 sets the SST value corresponding to MIot in the information element of the NSSAI.

[0039] After the processes of S400 to S411 are performed for all the target IAB nodes in the order of the IAB nodes 102 to 105, the signal generation unit 306 generates a BAP control packet including the set (generated) information element of the NSSAI for each of the IAB nodes 102 to 105. Then, in S412, the signal transmission unit 301 notifies the NSSAI (list of slice types) by transmitting the generated BAP control packet for each of the IAB nodes 102 to 105 to each of the IAB nodes 102 to 105.

[0040] As described above, the IAB donor 101 can determine the slice type for each of the IAB nodes 102 to 105 in consideration of the path information and the status information. That is, the IAB donor 101 can assign a slice type to each IAB node according to the communication situation and the topology.

[0041] FIG. 5 shows an example of a conceptual diagram of an information element of the NSSAI indicating the slice types of each of the IAB nodes 102 to 105 determined by the process of FIG. 4. The NSSAIs 501 to 504 each represent a conceptual diagram of the information element of the NSSAI for the IAB nodes 102 to 105 determined by the IAB donor 101. In the example of FIG. 5, the SST value corresponding to eMBB is set to "1", the SST value corresponding to URLLC is set to "2", and the SST value corresponding to MIoT is set to "3". From FIG. 5, it can be seen that the IAB nodes 102 and 103 support eMBB, URLLC, and MIoT, the IAB node 104 supports URLLC and MIoT, and the IAB node 105 supports only MIoT. Note that in FIG. 5, an example in which the SST values corresponding to three types of slice types can be set is shown, but by adding other SST / SST values, slice types corresponding to other services and purposes can be defined and provided.

[0042] (Operations in the communication system) FIG. 6 is a diagram showing a communication sequence in the communication system 100 according to the present embodiment. Here, the operation until the IAB donor 101 determines the slice types that can be supported by the IAB nodes 103 and 105 and notifies the UEs 118 and 119, and the UEs 118 and 119 connect to the IAB node that supports the desired slice type will be described. Note that the same processing is performed for the other IAB nodes 102 and 104 and the UEs 110 to 117, but here the description will be limited to the above communication devices for simplicity of explanation.

[0043] As an initial state of the communication system 100 described in FIG. 1, in F600 and F601, each of the UEs 118 and 119 makes a connection request to the IAB node 105 with the highest radio wave intensity. In F602, the IAB node 105 permits the connection requests from the UEs 118 and 119, and connection processing is performed between the IAB node and each of the UEs 118 and 119. It is assumed that the UE 119 wishes to receive eMBB service provision according to the application to be executed.

[0044] In F603 to F605, the IAB donor 101 requests the IAB nodes 103 and 105 to transmit route information and status information, and the IAB nodes 103 and 105 receive the request. In F606, the IAB node 105 transmits the route information and status information in the IAB node 105 itself to the IAB donor 101. Similarly, in F607, the IAB node 103 transmits the route information and status information in the IAB node 103 itself to the IAB donor 101. In F608, the IAB donor 101 receives the route information and status information from the IAB nodes 103 and 105. Here, the IAB donor 101 may collect (receive) the route information and status information of the IAB nodes 103 and 105 at a predetermined regular timing, or the IAB nodes 103 and 105 may spontaneously transmit the information to the IAB donor 101 when there is a change in the communication status.

[0045] In F609, the IAB donor 101 performs the processing of the flowchart shown in FIG. 4 to determine the slice types supported by each of the IAB nodes 103 and 105. The determined slice types are those shown in FIG. 5. The IAB node 103 supports all (eMBB, URLLC, MIot) slice types, and the IAB node 105 supports only MIot.

[0046] In F610 and F611, the IAB donor 101 notifies the IAB node 103 of the NSSAI indicating the determined slice type, and the IAB node 103 receives it. Similarly, in F610 and F612, the IAB donor 101 notifies the IAB node 105 of the NSSAI indicating the determined slice type, and the IAB node 105 receives it.

[0047] In F613 - F615, the IAB node 103 notifies the UE 118 and 119 of the NSSAI notified in F611 together with the cell ID that can identify the IAB node 103, and the UE 118 and 119 receive it. Similarly, in F616 - F618, the IAB node 105 notifies the UE 118 and 119 of the NSSAI notified in F612 together with the cell ID that can identify the IAB node 105, and the UE 118 and 119 receive it.

[0048] As described above, the UE 119 hopes to receive the eMBB service provision. Therefore, in F619 and F620, the UE 119 sends a connection request to the IAB node 103 that supports eMBB, and the IAB node 103 returns a connection permission response, and a connection is established between the UE 119 and the IAB node 103. Here, when the UE 119 connects to the IAB node 103, the total number of connected UEs in the IAB node 103 changes from 3 to 4. As described above, in this embodiment, since the second specified value (S403 in FIG. 4) used to determine whether the IAB node supports eMBB is 4, the IAB node 103 can determine that it can maintain eMBB and returns a permission response to the UE 119. Also, when the total number of connected UEs in the IAB node 103 increases, the IAB node 103 may again inquire the IAB donor 101 about the re - allocation of the NSSAI, update the NSSAI, and then determine whether the UE 119 can connect.

[0049] In F622 - F623, the UE 119 sends a disconnection request to the IAB node 105, and after the IAB node 105 returns a disconnection permission response, it releases the link with the UE 119.

[0050] FIG. 7 is a diagram showing the network topology after slice type determination by the IAB donor 101 in the communication system 100 according to the present embodiment. In the communication system 100, after the sequence of FIG. 6 is executed, the UE 119 that was connected to the IAB node 105 via the communication link 700 forms and connects a new link 701 with the IAB node 103. The communication link 700 is disconnected and released, and the UE 119 can communicate with the slice type of eMBB.

[0051] As described above, according to the present embodiment, by the IAB donor 101 determining (allocating) the slice type to each of the IAB nodes 102 to 105 and notifying the NSSAI, it is possible to provide the UE 110 to 119 with information on the appropriate slice type.

[0052] Note that, as described above, the slice type is not limited to three types (eMBB, URLLC, MIot), and even when a new slice type SST is added, the above-described slice type determination method can be applied by using a predetermined condition. Furthermore, even when using the SD (Slice Differentiator), which is an option of the SST, the above-described slice type determination method can be applied.

[0053] [Embodiment 2] In Embodiment 1, the method of allocating the NSSAI by the IAB donor 101 to each of the IAB nodes 102 to 105 in the initial state when the communication system 100 starts operation or in a static communication situation was described. As Embodiment 2, the case where the communication environment in the communication system 100 changes (for example, the SNR changes, the total number of connected UEs changes, etc.) will be described. Note that descriptions common to Embodiment 1 will be omitted.

[0054] In this embodiment, as a case where the communication environment changes, it is assumed that the communication status (communication quality) between the IAB donor 101 and the IAB node 103 in the communication system 100 deteriorates (for example, the SNR decreases). In this case, the IAB node 103 requests the IAB donor 101 to reallocate the NSSAI. Alternatively, the IAB node 103 determines that it is difficult (impossible) to maintain the network slice allocated to the IAB node 103 based on the received NSSAI, and may send a notification indicating that the SST cannot be maintained (information indicating that network slice maintenance is impossible) to the IAB donor 101. In response to receiving such a request / notification, the IAB donor 101 can update and determine the slices supported by the IAB node 103, and notify the IAB node 103 of the generated NSSAI accordingly.

[0055] Also, when the communication environment changes as described above, the IAB node 103 may notify the UEs 113 to 115, 119 of the deterioration of the communication state for implementing eMBB. In this case, further, the UEs 113 to 115, 119 may search for other IAB nodes 102, 104 to 105 that are connectable and support eMBB, and may send a connection request if the conditions are favorable.

[0056] As described above, according to this embodiment, in response to a change in the communication environment, the IAB donor 101 updates and determines (allocates) the types of network slices that can be supported by the IAB node and notifies the IAB node of the NSSAI. Alternatively, in response to a change in the communication environment, the UEs 110 to 119 are notified of the deterioration of the communication state for implementing a predetermined network slice. Thereby, the IAB node can provide information regarding an appropriate slice type to the UEs 110 to 119.

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

[0058] The invention is not limited to the above embodiments, and various changes and modifications can be made 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

[0059] 100 Communication system, 101 IAB donor, 102 - 105 IAB nodes, 110 - 119 UEs

Claims

1. A communication device that functions as a base station in a communication network, receiving means for receiving, from a node that relays communication between the communication device and a user device, first information regarding a path between the node and the communication device and second information regarding a status of the node; determining means for determining a type of network slice supported by the node based on the first information and the second information; notifying means for notifying the node of the determined type of network slice; A communication device characterized by comprising the above.

2. The communication device according to claim 1, wherein the communication device is a communication device that functions as an IAB (Integrated Access and Backhaul) donor in an IAB network.

3. The communication device according to claim 1 or 2, wherein the communication network includes an NR (New Radio) backhaul link and an NR access link.

4. The communication device according to any one of claims 1 to 3, wherein the notifying means notifies the node of the determined type of one or more network slices using packets according to a BAP (Backhaul Adaptation Protocol) or an RRC (Radio Resource Control) protocol.

5. The communication device according to any one of claims 1 to 4, further comprising determining means for determining a type of network slice supported by the communication device or another node directly connected to the node between the node and the communication device.

6. The second information includes a value indicating a received signal quality at the node and a total number of user devices connected between the node and the communication device, When it is determined by the determining means that high-speed large-capacity communication is supported as the type of the network slice by the communication device or the other node, and the value indicating the received signal quality is equal to or greater than a first specified value and the total number of the user devices is equal to or less than a second specified value, the determining means determines that the high-speed large-capacity communication is supported by the node. The communication device according to claim 5, characterized in that.

7. The first information includes the number of hops from the communication device to the node, and the second information includes information indicating whether the node supports TSN (Time-Sensitive Networking). The communication device according to claim 5 or 6, wherein when it is determined by the determination means that low-latency communication is supported as the type of the network slice by the communication device or the other node, and the node supports the TSN and the number of hops is equal to or greater than a third specified value, the determination means determines that the node supports the low-latency communication.

8. The communication device according to any one of claims 1 to 7, wherein the determination means determines that the node supports simultaneous multi-connection as the type of the network slice.

9. The communication device according to any one of claims 1 to 8, wherein the receiving means receives the first information and the second information at a predetermined regular timing.

10. The communication device further comprises a requesting means for requesting the node to transmit the first information and the second information. The communication device according to any one of claims 1 to 8, wherein the receiving means receives the first information and the second information in response to a request by the requesting means.

11. The communication device according to any one of claims 1 to 10, wherein when, after the type of the network slice determined by the notifying means is notified to the node, the receiving means receives information indicating that it is impossible to maintain the support of the determined network slice from the node, the determination means updates and determines the type of the network slice supported by the node.

12. A communication device that functions as a node for relaying communication between a base station and a user device in a communication network, a transmitting means for transmitting first information regarding a path between the communication device and the base station and second information regarding a status in the communication device to the base station; a receiving means for receiving information on the type of network slice supported by the node, which is determined by the base station based on the first information and the second information; notification means for notifying the user equipment of information that can identify the communication device, together with information on the type of the network slice; A communication device, characterized by comprising the same.

13. The base station is a base station that functions as an IAB (Integrated Access and Backhaul) donor in an IAB network. The communication device according to claim 12, characterized in that.

14. The communication network includes an NR (New Radio) backhaul link and an NR access link. The communication device according to claim 12 or 13, characterized in that.

15. further comprising determination means for determining whether it is impossible to maintain the network slice assigned according to the information received by the receiving means in response to a change in the communication environment; When it is determined by the determination means that it is impossible to maintain the network slice, information indicating that it is impossible to maintain the support of the network slice is transmitted to the base station. The communication device according to any one of claims 12 to 14, characterized in that.

16. A control method for a communication device that functions as a base station in a communication network, comprising: a receiving step of receiving, from a node that relays communication between the communication device and a user device, first information regarding a path between the node and the communication device and second information regarding a status of the node; a determining step of determining a type of network slice supported by the node based on the first information and the second information; a notifying step of notifying the node of the determined type of network slice; A control method, characterized by comprising the same.

17. A control method for a communication device that functions as a node that relays communication between a base station and a user device in a communication network, comprising: a transmitting step of transmitting first information regarding a path between the communication device and the base station and second information regarding a status of the communication device to the base station; a receiving step of receiving information including a type of network slice supported by the node, determined by the base station based on the first information and the second information; a notifying step of notifying the user device of information that can identify the communication device, together with the type of the network slice; A control method, characterized by comprising the same.

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

Images