Communication device, control method of communication device, and computer-readable storage medium

Abstract

A communication device used as a base station in a communication network receives, from a node used to relay communication between a communication device and a user equipment, first information related to a path between the node and the communication device and second information related to a status at the node, determines a type of network slice supported by the node based on the first information and the second information, and notifies the node of the determined type of network slice.

Description

Technical Field

[0001] The present invention relates to a communication device, a control method for the communication device, and a non-transitory computer-readable storage medium. Background Technology

[0002] In 3GPP (3rd Generation Partnership Project), IAB (Integrated Access and Backhaul) has been standardized as a backhaul communication technology. IAB technology utilizes 28GHz millimeter-wave wireless communication, used for access communication between base stations and user equipment (UEs), as backhaul communication (Patent Document 1). Compared to wired communication using traditional optical fibers, the use of IAB technology makes it possible to extend regional coverage at a lower cost, thus IAB technology is expected to be effective in building next-generation public networks.

[0003] In backhaul communication using IAB technology, relay devices called IAB nodes use millimeter-wave communication to relay communications from IAB donors, which are equivalent to traditional base stations. Furthermore, IAB nodes can extend their area by forming bearers between themselves and multiple other IAB nodes, creating a network tree (IAB network) starting from the IAB donor. The IAB nodes, which serve as extension components for extending the area of ​​the IAB donor, can be controlled via BAP (Backhaul Adaptation Protocol), where BAP is a routing protocol for IAB.

[0004] On the other hand, in next-generation public networks, the concept of network slicing is being studied, which involves virtually providing network slices on a shared network to meet the requirements of multiple different services. eMBB (enhanced Mobile Broadband) for high-speed and high-capacity communication, URLLC (ultra-reliable and low-latency communication) for low-latency communication, and MIot (massive Internet of Things) for simultaneous multi-connection have been identified as types of network slices.

[0005] Patent Document 2 discloses a method in which, for example, the UE can receive the desired service as a result of the UE transmitting a network slice request to the base station and the base station responding with whether it supports network slicing. A mechanism has been investigated that enables the UE to select a network slice provided by the base station according to its purpose, and makes the network slice available in such a manner.

[0006] Citation List

[0007] Existing technical documents

[0008] Patent Document 1: Japanese Patent Application Publication No. 2019-534625

[0009] Patent Document 2: Japanese Patent Application Publication No. 2020-511863 Summary of the Invention

[0010] The problem the invention aims to solve

[0011] The BAP (Backhaul Adaptation Protocol) does not explicitly define network slicing operations in communication networks such as IAB networks. Therefore, in the case of IAB networks, IAB nodes directly notify lower-level IAB nodes and the UE of the NSSAI (Network Slice Selection Auxiliary Information) received from the connected IAB donor. Note that NSSAI includes SST (Slice / Service Type) information in list form, where SST indicates the types of network slices that can be supported.

[0012] In this operation, for example, even when an IAB node far from the IAB donor is not configured to support network slices supported by the IAB donor, the IAB node far from the IAB donor may only notify the same NSSAI as the IAB donor. As a result, even when the UE receives the NSSAI notification and selects and requests the desired network slice, the UE may not be able to provide the desired quality.

[0013] In view of the above problems, the present invention has been implemented, and the object of the present invention is to properly determine and transmit information related to the network slices that a node can support.

[0014] Solution for solving the problem

[0015] As a means to achieve this purpose, the communication device according to the present invention has the following configuration. That is, the communication device functions as a base station in a communication network. The communication device includes: a receiving component for receiving first information relating to the path between the node and the communication device and second information relating to the state of the node from a node used for relaying communication between the communication device and a user equipment; a determining component for determining the type of network slice supported by the node based on the first and second information; and a reporting component for reporting the determined type of network slice to the node.

[0016] The effects of the invention

[0017] According to the present invention, information relating to the network slices that a node can support can be appropriately determined and transmitted.

[0018] Other features and advantages of the invention will become apparent from the following description taken in conjunction with the accompanying drawings. Note that in all the drawings, the same reference numerals denote the same or similar components. Attached Figure Description

[0019] Embodiments of the invention are illustrated in conjunction with the accompanying drawings, which are included in and form part of this specification, and together with the specification serve to explain the principles of the invention.

[0020] Figure 1This is a diagram illustrating an example of a backhaul communication system.

[0021] Figure 2 This is a block diagram illustrating an example of the hardware configuration of an IAB donor.

[0022] Figure 3 This is a block diagram illustrating an example of the software functionality configuration of an IAB donor.

[0023] Figure 4A This is a flowchart illustrating the process for determining the slice type of an IAB node according to an embodiment.

[0024] Figure 4B This is a flowchart illustrating the process for determining the slice type of an IAB node according to an embodiment.

[0025] Figure 5 An example of a conceptual diagram showing NSSAI information elements.

[0026] Figure 6A This is a diagram illustrating a communication sequence in a communication system according to an embodiment.

[0027] Figure 6B This is a diagram illustrating a communication sequence in a communication system according to an embodiment.

[0028] Figure 7 This is a diagram illustrating the network topology after determining the slice type according to an embodiment. Detailed Implementation

[0029] In the following, 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. Several features are described in the embodiments, but the invention is not limited to requiring all such features, and multiple such features can be suitably combined. Furthermore, in the drawings, the same reference numerals are given the same or similar configuration, and redundant descriptions thereof are omitted.

[0030] Example 1

[0031] Configuration of communication system

[0032] Figure 1This is a diagram illustrating an example of a backhaul communication system (hereinafter referred to as the "communication system") according to Embodiment 1. The communication network using backhaul communication may include NR (New Radio) backhaul links and NR access links. In the communication system 100, there are IAB (Integrated Access and Backhaul) donors 101 for providing connectivity to the core network (CN) 130. The IAB donors 101 form an IAB network (communication network) consisting of IAB donors 101 and IAB nodes 102 to 105. Each IAB donor can be used as a wireless base station device in the communication network. IAB nodes can also be used as wireless base station devices.

[0033] IAB donor 101 performs overall control of IAB nodes 102 to 105 and forms the area covered by IAB donor 101. UEs 110 to 119 connect to the IAB donor or IAB nodes to communicate according to the desired application. Figure 1 As shown, in the initial state, UEs 110 to 119 are connected to IAB donor 101 or IAB nodes 102 to 105, which have the highest radio wave strength. Note that examples of radio wave strength include RSRP (Reference Signal Received Power) and RSCP (Received Signal Code Power) values.

[0034] In the initial phase of IAB network construction, the types of network slices (SSTs, hereinafter referred to as "slice types") that IAB nodes 102 to 105 can support have not yet been determined. The slice types that IAB nodes 102 to 105 can support are determined by the IAB donor 101, which is responsible for the overall control of the communication system 100, and the slice types are reported to IAB nodes 102 to 105.

[0035] IAB donor 101 and IAB nodes 102 to 105 notify UEs 110 to 119 of the determined slice type and the cell ID (identifier) ​​corresponding to IAB donor 101 / IAB nodes 102 to 105. Note that the notification is information given along with the slice type, and such information is not limited to the cell ID, and only needs to be able to specify (identify) the information of IAB donor 101 / IAB nodes 102 to 105 used to inform the UE of the slice type.

[0036] UEs 110 to 119 can determine whether IAB donor 101 or IAB nodes 102 to 105 support the slice type to be used based on the received slice type / cell ID, and establish or change the connection accordingly. Alternatively, UEs 110 to 119 can request the slice type to be used from IAB donor 101 and IAB nodes 102 to 105, and establish or change the connection based on the response to the request.

[0037] IAB donor / IAB node configuration

[0038] The configuration of IAB donor 101 and IAB nodes 102 to 105 will be described next. Figure 2 This is a block diagram illustrating an example hardware configuration of IAB donor 101. Although the hardware configuration will be described here assuming IAB donor 101, IAB nodes 102 to 105 may also have similar configurations. Figure 2 The hardware configuration is similar to that in [the text].

[0039] As an example of 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 performs overall control of the entire device by executing the control program stored in the storage unit 202. For example, the control unit 201 consists of one or more CPUs (Central Processing Units) or MPUs (Microprocessors).

[0040] Storage unit 202 is composed of ROM (Read-Only Memory) or RAM (Random Access Memory), etc. Storage unit 202 stores various types of information, such as control programs executed by control unit 201, information related to the cell ID or UE to be connected, and controlled IAB nodes (…). Figure 1 The storage unit 202 can store path information for IAB nodes 102 to 105. Furthermore, the storage unit 202 can store information related to the network slices (slice types) supported by the IAB donor 101. Various operations, which will be described later, can be performed by the control unit 201 executing the control program stored in the storage unit 202.

[0041] The wireless communication unit 203 is a wireless communication unit for performing cellular network communications such as LTE (Long Term Evolution) and 5G (Fifth Generation) compliant with 3GPP (3rd Generation Partnership Project) standards. The antenna control unit 204 controls the antenna 205 for wireless communication performed in the wireless communication unit 203. The antenna 205 may include multiple antennas.

[0042] Figure 3 This is a block diagram illustrating an example of the software function configuration of IAB donor 101 according to this embodiment. As an example of the software function configuration, IAB donor 101 includes a signal transmission unit 301, a signal receiving unit 302, a storage control unit 303, a connection control unit 304, a slice type determination unit 305, and a signal generation unit 306. The software function configuration will be described assuming IAB donor 101, and IAB nodes 102 to 105 will be described later.

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

[0044] The slice type determination unit 305 determines the slice type of IAB nodes 102 to 105 based on the path information and status information received (acquired) from IAB nodes 102 to 105 via the signal receiving unit 302. In this embodiment, the slice type determination unit 305 acquires path information and status information from IAB nodes 102 to 105 and determines the slice type of IAB nodes 102 to 105. In this embodiment, the path information may refer to (including) information related to the hop count from IAB donor 101 to each IAB node 102 to 105, and information related to the routing in IAB nodes 102 to 105. Furthermore, the status information may refer to (including) information related to the SNR (signal-to-noise ratio) value of IAB nodes 102 to 105 as a received signal quality, the number of connected UEs, and specification information (whether TSN (Time-Sensitive Networking) is supported), etc. TSN is a network technology that enables interoperability between IT networks and industrial networks used to extend standard Ethernet. Note that although SNR is used in this embodiment, other information used to indicate the quality of the received signal can be used instead of SNR.

[0045] Signal generation unit 306 generates packets (signals) for reporting / notifying various types of information to IAB nodes 102 to 105 and UEs 110 to 119. Signal generation unit 306 in IAB donor 101 generates two types of packets.

[0046] The signal generation unit 306 generates a control packet as a first type of packet, which is used to inform IAB nodes 102 to 105 of the slice type determined by the slice type determination unit 305. In this embodiment, a control packet based on BAP (Backhaul Adaptation Protocol) is used to inform the IAB nodes of the slice type. However, this is not a limitation, and other control packets can be used. For example, if IAB nodes 102 to 105 can interpret the RRC (Radio Resource Control) protocol, control packets based on the RRC protocol or a communication layer protocol higher than the RRC layer can be used to inform IAB nodes 102 to 105.

[0047] Signal generation unit 306 generates a notification packet as a second type of packet, which is used to notify UEs 110 to 119 of the cell ID that can identify IAB donor 101 together with the slice type determined by slice type determination unit 305.

[0048] Next, the software functional configuration of IAB nodes 102 to 105 according to this embodiment will be described below. The software functional configuration of IAB nodes 102 to 105 can be compared with the reference Figure 3 The software configuration of the described IAB donor 101 is similar. However, in the above regarding Figure 3 In the description, other communication devices (IAB nodes and UEs) are interpreted as other devices (IAB donors and UEs). Furthermore, IAB nodes 102 to 105 do not have a slice type determination unit 305, and signal generation unit 306 does not generate packets of the first type. Signal generation unit 306 generates a notification packet to notify UEs 110 to 119 of the cell ID that identifies IAB nodes 102 to 105 and the slice type that IAB donor 101 has been reported. Connection control unit 304 can control the link connection with / release from the UE.

[0049] Slice type determination process performed by IAB donors

[0050] Figure 4A and Figure 4B This is a flowchart illustrating the process for determining the slice type of an IAB node using IAB according to this embodiment. Note that it is assumed that IAB donor 101 supports all slice types: high-speed and high-capacity (eMBB (enhanced Mobile Broadband)), low latency (URLLC (Ultra-Reliable and Low-Latency Communication)), and simultaneous multiple connections (MIot (Massive Internet of Things)). Information related to the supported slice types can be stored in storage unit 202. Furthermore, in this embodiment, it is assumed that IAB nodes 102 to 105 can support MIot.

[0051] The process from steps S400 to S411 is repeated to determine the slice type of all IAB nodes 102 to 105 rooted at IAB donor 101. In this embodiment, as a non-limiting example, it is assumed that the IAB donor determines the slice type in ascending order of hop count from IAB donor 101. Note that it is assumed that the hop count from IAB donor 101 to IAB node 102 is the same as the hop count from IAB donor 101 to IAB node 103, but IAB donor 101 determines the slice type in the order of IAB nodes 102, 103, 104, and 105. The object IAB node used to determine the slice type in one loop from steps S400 to S411 is referred to as the "object IAB node".

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

[0053] The processes from steps S402 to S405 are used to determine whether the target IAB node supports high-speed and high-capacity communication (eMBB in this embodiment) as a slice type. In step S402, the slice type determination unit 305 determines whether the SNR value included in the status information obtained from the target IAB node is greater than or equal to a first predetermined value. The SNR can be the SNR between the target IAB node and the upstream node (parent node) connected to the target IAB node. The first predetermined value used here is a value preset to meet the communication speed (data rate) required for eMBB communication. If the SNR value is greater than or equal to the first predetermined value ("Yes" in step S402), the process proceeds to step S403; if the SNR value is not greater than or equal to the first predetermined value ("No" in step S402), the process proceeds to step S406.

[0054] In step 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 UEs connected between the IAB donor 101 and the target IAB node) is less than or equal to a second predetermined value. Figure 1 In the communication system 100 shown, when the target IAB node is IAB node 102, the total number of connected UEs is 3, and when the target IAB node is IAB node 104, the total number of connected UEs is 5. In this embodiment, the second specified value is 4, but it can be other values. If the total number of connected UEs is less than or equal to the second specified value ("Yes" in step S403), the process proceeds to step S404; if the total number of connected UEs is not less than or equal to the second specified value ("No" in step S403), the process proceeds to step S406.

[0055] In step S404, the slice type determination unit 305 determines whether the node (parent node) upstream connected to the object IAB node supports eMBB based on the acquired status information or the information stored in the storage unit 202. If the object IAB node is IAB node 102, the parent node is IAB donor 101; and if the object IAB node is IAB node 104, the parent node is IAB node 102. That is, the parent node can be IAB donor 101, which is directly connected to the object IAB node between the object IAB node and IAB donor 101, or another IAB node different from the object IAB node. If the parent node supports eMBB ("Yes" in step S404), the process proceeds to step S405; and if the parent node does not support eMBB ("No" in step S404), the process proceeds to step S406.

[0056] In step S405, the signal generation unit 306 adds the eMBB to NSSAI (Network Slice Selection Auxiliary Information). As described above, NSSAI includes information on supported slice types (SST (Slice Service Type)) in list form. Specifically, the signal generation unit 306 sets the SST value corresponding to the eMBB as an NSSAI information element.

[0057] The processes from steps S406 to S409 are used to determine whether the target IAB node supports low-latency communication (URLLC) as a slice type. In step S406, the slice type determination unit 305 determines whether the target IAB node supports TSN (Time-Sensitive Networking) based on the status information obtained from the target IAB node. If the target IAB node supports TSN ("Yes" in step S406), the process proceeds to step S407; if the target IAB node does not support TSN ("No" in step S406), the process proceeds to step S410.

[0058] In step S407, the slice type determination unit 305 determines whether the number of hops from IAB donor 101 to the object IAB node is less than or equal to a third predetermined value based on the path information obtained from the object IAB node. If the object IAB node is IAB node 102, the number of hops is 1. In this embodiment, the following description will be given assuming the third predetermined value is 2. If the number of hops is less than or equal to the third predetermined value (yes in step S407), the process proceeds to step S408; if the number of hops is not less than or equal to the third predetermined value (no in step S407), the process proceeds to step S410. In step S408, the slice type determination unit 305 determines whether the parent node supports URLLC based on the obtained status information or the information stored in the storage unit 202. Although the objects used to determine support differ, the process in step S408 is the same as that in step S404. If the parent node supports URLLC (Yes in step S408), the process proceeds to step S409; otherwise, if the parent node does not support URLLC (No in step S408), the process proceeds to step S410. In step S409, the signal generation unit 306 adds the URLLC to NSSAI. Specifically, the signal generation unit 306 sets the SST value corresponding to the URLLC to the NSSAI information element. In the subsequent step S410, the signal generation unit 306 sets the SST value corresponding to MIot to the NSSAI information element.

[0059] Processing is performed on all object IAB nodes in the order of IAB nodes 102, 103, 104, and 105 from steps S400 to S411. Then, signal generation unit 306 generates BAP control packets for IAB nodes 102 to 105, including the set (generated) NSSAI information elements. Then, in step S412, signal transmission unit 301 notifies IAB nodes 102 to 105 of the NSSAI (Slice Type List) by transmitting the generated BAP control packets to IAB nodes 102 to 105.

[0060] As described above, IAB donor 101 can determine the slice type of IAB nodes 102 to 105 by considering path information and status information. That is, IAB donor 101 can assign slice types to IAB nodes according to communication status and topology.

[0061] Figure 5 This example shows a conceptual diagram of an NSSAI information element, which illustrates how NSSAI information elements are displayed through... Figure 4A and Figure 4BThe processing shown represents the slice types of IAB nodes 102 to 105 as determined by the process. NSSAI 501 to NSSAI 504 represent conceptual diagrams of the NSSAI information elements of IAB nodes 102 to 105 as determined by IAB donor 101, respectively. Figure 5 In the example shown, 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". Figure 5 It can be seen that IAB nodes 102 and 103 support eMBB, URLLC, and MIot; IAB node 104 supports URLLC and MIot; and IAB node 105 only supports MIot. Note that... Figure 5 Examples of SST values ​​that can be set corresponding to the three slice types are shown. However, by adding other SST / SST values, slice types can be defined and provided according to other services and purposes.

[0062] Operation in a communication system

[0063] Figure 6A and Figure 6B This is a diagram illustrating the communication sequence in the communication system 100 according to this embodiment. The following describes the operations performed from the time IAB donor 101 determines the slice types that IAB nodes 103 and 105 can support and reports the slice types to UEs 118 and 119 until UEs 118 and 119 connect to the IAB nodes that support the desired slice types. Note that the same processing is performed on the other IAB nodes 102 and 104 and UEs 110 to 117, but for simplicity, only the above-described communication apparatus will be described.

[0064] As Figure 1 In the initial state of the communication system 100 described herein, in F600 and F601, UEs 118 and 119 send connection requests to the IAB node 105 with the highest radio wave strength. In F602, the IAB node 105 acknowledges the connection requests transmitted from UEs 118 and 119 and performs the processing required for establishing a connection between the IAB node and UEs 118 and 119. It is assumed that UE 119 expects to receive eMBB service provision based on the application to be executed.

[0065] In steps F603 to F605, IAB donor 101 requests path and status information from IAB nodes 103 and 105, and IAB nodes 103 and 105 receive the request. In step F606, IAB node 105 transmits path and status information related to itself to IAB donor 101. In step F607, IAB node 103 transmits path and status information related to itself to IAB donor 101 in a similar manner. In step F608, IAB donor 101 receives path and status information from IAB nodes 103 and 105. Here, IAB donor 101 can collect (receive) path and status information related to IAB nodes 103 and 105 at specific periodic intervals. Alternatively, IAB nodes 103 and 105 can spontaneously transmit information to IAB donor 101 when the communication state changes.

[0066] In F609, IAB donor 101 performs... Figure 4A and Figure 4B The flowchart shown illustrates the processing and determines the slice types supported by IAB nodes 103 and 105. The determined slice types are... Figure 5 As shown in the diagram, IAB node 103 supports all slice types (eMBB, URLLC, MIot), while IAB node 105 only supports MIot.

[0067] In F610 and F611, IAB donor 101 reports an NSSAI to IAB node 103 indicating the slice type determined by IAB node 103, and IAB node 103 receives the NSSAI. Similarly, in F610 and F612, IAB donor 101 reports an NSSAI to IAB node 105 indicating the slice type determined by IAB node 105, and IAB node 105 receives the NSSAI.

[0068] In F613 to F615, IAB node 103 will notify UEs 118 and 119 of the NSSAI already reported by IAB donor 101 in F611, along with the cell ID that can identify IAB node 103, and UEs 118 and 119 will receive the NSSAI and cell ID. In F616 to F618, IAB node 105 will notify UEs 118 and 119 of the NSSAI already reported by IAB donor 101 in F612, along with the cell ID that can identify IAB node 105, and UEs 118 and 119 will receive the NSSAI and cell ID.

[0069] As described above, UE 119 expects to receive eMBB service. Therefore, in F619 and F620, UE 119 sends a connection request to IAB node 103, which supports eMBB. IAB node 103 then sends a connection confirmation response, and UE 119 connects to IAB node 103. Here, when UE 119 connects to IAB node 103, the total number of UEs connected to IAB node 103 changes from 3 to 4. As described above, in this embodiment, the second specified value used to determine whether an IAB node supports eMBB ( Figure 4A Step S403 in the above steps is 4, and it can be determined that IAB node 103 can maintain eMBB, and send an acknowledgment response to UE 119. In addition, if the total number of UEs connected to IAB node 103 increases, IAB node 103 can again perform a query related to reassigning NSSAI to IAB donor 101, update NSSAI, and determine whether UE 119 can connect to IAB node 103.

[0070] In F622 and F623, UE 119 transmits a disconnect request to IAB node 105, and IAB node 105 returns a disconnect confirmation response and releases the link with UE 119.

[0071] Figure 7 This is a diagram illustrating the network topology in a communication system 100 according to an embodiment after the slice type is determined by the IAB donor 101. In the communication system 100, during execution... Figure 6A and Figure 6B The sequence shown then connects UE 119, which is connected to IAB node 105 via communication link 700, to IAB node 103, forming a new link 701 and connecting to IAB node 103. Communication link 700 is then disconnected and released, and UE 119 is able to communicate using the eMBB slice type.

[0072] As described above, according to this embodiment, IAB donor 101 determines (assigns) the slice type of IAB nodes 102 to 105 and reports NSSAI to IAB nodes 102 to 105, thereby providing slice type-related information suitable for UEs 110 to 119.

[0073] Note that, as mentioned above, the slice type is not limited to the three types (eMBB, URLLC, MIot), and when adding SST as a new slice type, the slice type determination method described above can also be applied using predetermined conditions. Furthermore, when using SD (slice differentiator) as an option for SST, the slice type determination method described above can also be applied.

[0074] Example 2

[0075] In Embodiment 1, a method for IAB donor 101 to allocate NSSAI to IAB nodes 102 to 105 is described in the initial state when communication system 100 starts operating or in a static communication state. In Embodiment 2, the situation where the communication environment in communication system 100 changes (e.g., changes in SNR and changes in the total number of connected UEs, etc.) will be described. Note that descriptions common to Embodiment 1 are omitted.

[0076] In this embodiment, as a case of a change in the communication environment, it is assumed that the communication state (communication quality) between IAB donor 101 and IAB node 103 in communication system 100 deteriorates (e.g., SNR decreases). In this case, IAB node 103 requests IAB donor 101 to reallocate NSSAI. Alternatively, based on the received NSSAI, IAB node 103 may determine that it is difficult (impossible) to maintain the network slice allocated to IAB node 103, and may send the message "SST Unsustainable" (indicating that the network slice cannot be maintained) to IAB donor 101. IAB donor 101 may, in response to receiving such a request / message, update and determine the slices supported by IAB node 103, and accordingly report the generated NSSAI to IAB node 103.

[0077] Furthermore, in the event of a change in the communication environment as described above, IAB node 103 may notify UEs 113 to 115 and 119 of a deterioration in the communication status used to perform eMBB. In this case, UEs 113 to 115 and 119 may further search for other connectable IAB nodes 102, 104, and 105 that support eMBB, and make a connection request if conditions are favorable.

[0078] As described above, according to this embodiment, the IAB donor 101 updates and determines (assigns) the network slice types that the IAB node can support based on changes in the communication environment, and reports the NSSAI to the IAB node. Alternatively, the IAB donor may notify UEs 110 to 119 of deterioration in the communication state used to execute the predetermined network slice based on changes in the communication environment. As a result, the IAB node can provide UEs 110 to 119 with information related to the appropriate slice type.

[0079] Other embodiments

[0080] The present invention can be implemented by supplying a program for implementing one or more functions of the above embodiments to a system or device via a network or storage medium, and causing one or more processors of the system or device's computer to read and execute the program. The present invention can also be implemented by circuitry (e.g., an ASIC) for implementing one or more functions.

[0081] This invention is not limited to the embodiments described above, and various changes and modifications can be made within the spirit and scope of this invention. Therefore, the appended claims are set forth to inform the public of the scope of this invention.

[0082] This application claims priority to Japanese Patent Application 2021-074410, filed on April 26, 2021, which is incorporated herein by reference.

[0083] List of reference numerals

[0084] 100 Communication System

[0085] 101 IAB benefactors

[0086] 102 to 105 IAB nodes

[0087] UEs 110 to 119

Claims

1. A communication device that functions as a base station in a communication network and as an IAB donor in an IAB network, namely an Integrated Access and Backhaul network, characterized in that it comprises: A receiving component is configured to receive, from a second communication device that serves as an IAB node for relaying communication between the communication device and the user equipment, first information relating to the path between the second communication device and the communication device, and second information relating to the state of the second communication device; A determining component is used to determine the type of network slice supported by the second communication device based on the first information and the second information; as well as The reporting component is used to report the determined network slice type to the second communication device.

2. The communication device according to claim 1, wherein, The communication network includes NR backhaul links (i.e., New Radio backhaul links) and NR access links.

3. The communication device according to claim 1, wherein, The reporting component uses packets according to BAP (Backhaul Adaptation Protocol) or RRC (Radio Resource Control Protocol) to report one or more determined network slice types to the second communication device.

4. The communication device according to claim 1, further comprising: A determination component is used to determine the type of network slice supported by the communication device or other node that is directly connected between the second communication device and the second communication device.

5. The communication device according to claim 4, wherein, The second information includes values ​​indicating the quality of the received signal of the second communication device and the total number of user equipment connected between the second communication device and the communication device. If the determining component determines that high-speed and high-capacity communication is supported by the communication device or the other node as a type of network slice, and the value used to indicate the quality of the received signal is greater than or equal to a first predetermined value and the total number of user equipment is less than or equal to a second predetermined value, the determining component determines that the high-speed and high-capacity communication is supported by the second communication device.

6. The communication device according to claim 4, wherein, The first information includes the hop count from the first communication device to the second communication device, and the second information includes information indicating whether the second communication device supports TSN (Time-Sensitive Networking). If the determining component determines that low-latency communication is supported by the communication device or the other node as a type of network slice, and the second communication device supports TSN and the hop count is greater than or equal to a third predetermined value, the determining component determines that the low-latency communication is supported by the second communication device.

7. The communication device according to claim 1, wherein, The determining component is identified as a type of network slicing supported by the second communication device, which allows for simultaneous multiple connections.

8. The communication device according to claim 1, wherein, The receiving component receives the first information and the second information at specific periodic intervals.

9. The communication device according to claim 1, further comprising: The requesting component is used to request the transmission of the first information and the second information from the second communication device. The receiving component receives the first information and the second information in response to a request made by the requesting component.

10. The communication device according to any one of claims 1 to 9, wherein, If the reporting component reports the type of the determined network slice to the second communication device, and the information indicating that support for the determined network slice cannot be maintained is subsequently received by the receiving component from the second communication device, the determining component updates and determines the type of network slice supported by the second communication device.

11. A communication apparatus that serves as an IAB node (Integrated Access and Backhaul) node in a communication network for communication between a relay base station and a user equipment, wherein the base station serves as an IAB donor in the IAB network, the communication apparatus comprising: A transmission component is configured to transmit to the base station first information relating to the path between the communication device and the base station and second information relating to the state of the communication device; A receiving component is configured to receive from the base station information relating to the type of network slice supported by the communication device, wherein the type is determined by the base station based on the first information and the second information; as well as A notification component is used to notify the user equipment of information that identifies the communication device, along with information related to the type of network slice.

12. The communication device according to claim 11, wherein, The communication network includes NR backhaul links (i.e., New Radio backhaul links) and NR access links.

13. The communication device according to claim 11 or 12, further comprising: The judgment component is used to determine, based on changes in the communication environment, whether the network slice allocated according to the information received by the receiving component can no longer be maintained. If the determining component determines that the network slice cannot be maintained, it will transmit information indicating that support for the network slice cannot be maintained to the base station.

14. A method for controlling a communication device, said communication device serving as a base station in a communication network and as an IAB donor in an IAB network, i.e., an Integrated Access and Backhaul network, said method comprising: The receiving step is used to receive, from a second communication device that serves as an IAB node for relaying communication between the communication device and the user equipment, first information relating to the path between the second communication device and the communication device, and second information relating to the state of the second communication device. The determination step is used to determine the type of network slice supported by the second communication device based on the first information and the second information; as well as The reporting step is used to report the determined network slice type to the second communication device.

15. A control method for a communication device, the communication device serving as an IAB node (Integrated Access and Backhaul node) in a communication network for communication between a relay base station and a user equipment, wherein the base station serves as an IAB donor in the IAB network, the method comprising: The transmission step is used to transmit to the base station first information related to the path between the communication device and the base station and second information related to the state of the communication device; The receiving step is used to receive information from the base station including the type of network slice supported by the communication device, wherein the type is determined by the base station based on the first information and the second information; as well as The notification step is used to notify the user equipment of information that can identify the communication device used, along with the type of the network slice.

16. A non-transitory computer-readable storage medium storing a program that, when executed by a computer, implements the control method of the communication device according to claim 14 or 15.

17. A computer program product comprising a program that, when executed by a computer, implements the control method of the communication device according to claim 14 or 15.

Images