Communication device, communication method, and program

Abstract

To provide a technique for performing communication on a path that supports slice requests in a network in which communication is performed using BAP.SOLUTION: A communication device in a network for performing communication using BAP (Backhaul Adaptation Protocol) identifies, based on a received first packet, a slice type that another communication device that transfers the first packet in the network should support, further identifies another communication device that supports the identified slice type based on the slice type supported by the other communication device in the network, and transmits, to the identified other communication device, a second packet that is generated based on the first packet, is to be communicated using BAP, and has a header set according to an identified result.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present invention relates to a communication device, a communication method, and a program.

Background Art

[0002] In 3GPP (3rd Generation Partnership Project), the standardization of IAB (Integrated Access and Backhaul) technology as a communication technology for backhaul is progressing. The IAB technology is a technology that 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).

[0003] In a backhaul communication network using IAB technology (hereinafter, IAB network), a relay device called an IAB node relays communication from an IAB donor corresponding to a conventional base station to a destination UE. In the IAB network, in case the wireless communication situation between the IAB donor and the IAB nodes deteriorates, it is considered to restore and improve the communication situation by switching the communication path or forming a plurality of communication paths (hereinafter, multipath). Also, in the IAB network, communication between the IAB donor and the IAB nodes and between the IAB nodes uses BAP (Backhaul Adaptation Protocol). BAP is mainly defined as a protocol for routing communication packets between a plurality of IAB nodes.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Here, in the next-generation public network, consideration is underway for introducing the concept of network slicing, which virtually provides network slices (hereinafter referred to as slices) corresponding to the requirement conditions of a plurality of different services on a common network. As types of slices, enhanced Mobile BroadBand (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC) are defined. eMBB is an abbreviation for enhanced Mobile BroadBand. Also, URLLC is an abbreviation for Ultra-Reliable and Low Latency Communication, and mMTC is an abbreviation for massive Machine Type Communication. For example, studies are underway on a mechanism in which a UE requests a predetermined network slice and communicates using the requested network by the base station passing through the Core Network (CN) responding.

[0006] However, in an IAB network, there are cases where packets are routed by a communication device that does not support the slice requirements of the relayed packets, and there is a possibility that communication that satisfies the slice requirements cannot be performed.

[0007] The present invention has been made in view of the above problems, and an object thereof is to provide a technique for performing communication through a path that supports slice requirements in a network that communicates using a BAP (Backhaul Adaptation Protocol).

Means for Solving the Problems

[0008] To solve the above problems, a communication device according to the present invention is a communication device in a network that communicates using a BAP (Backhaul Adaptation Protocol), a first specifying means for specifying a slice type that other communication devices in the network that transfer the first packet should support based on the received first packet; a second specifying means for specifying other communication devices that support the slice type specified by the first specifying means based on the slice type supported by other communication devices in the network; A second packet communicated using a BAP generated based on the first packet, the second packet having a header set according to a specific result of the second specific means, and a transmission means for transmitting the second packet to the other communication device specified by the second specific means; It is characterized by comprising.

Effect of the Invention

[0009] According to the present invention, in a network that communicates using BAP, it is possible to provide a technique for performing communication on a path that supports slice requests.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the present invention according to the claims, and not all combinations of the features described in this embodiment are essential for the solution means of the present invention.

[0012] <Embodiment 1> FIG. 1 is a diagram showing an example of an IAB network according to the present invention. The IAB network 100 shown in FIG. 1 includes an IAB donor 101 and IAB nodes 102 to 105 (hereinafter sometimes referred to as IAB nodes without distinction). The IAB donor 101 provides a connection to the CN 130. In the IAB network 100, NR (New Radio) communication is used for both backhaul links and access links within the network. The IAB donor 101 forms an IAB network (NR backhaul network) including IAB nodes. Here, CN is an abbreviation for Core Network, and is responsible for various processes such as authentication of user devices UE110 to 118 (hereinafter sometimes referred to as UEs without distinction) and registration for using network slices (slices).

[0013] The IAB donor 101 is an example of a base station device that centrally controls each IAB node and forms an area covered by its own station. Also, it is assumed that the type of network slice that each IAB node can support is assigned to each IAB node by the IAB donor 101. Further, it is assumed that the IAB donor 101 manages the slice information supported by each IAB node as a list of NSSAI. Here, NSSAI is an abbreviation for Network Slice Selection Assistance Information.

[0014] As will be described below, the IAB donor 101 and the IAB nodes function as communication devices, and in the following description, the communication device will be described as being either the IAB donor 101 or the IAB node.

[0015] In the IAB network 100, when each UE receives service provision from the CN 130, packets from the CN 130 are downlink transmitted to each UE via the IAB donor 101. On the other hand, in the uplink, packets from each UE are similarly transmitted to the CN 130 via the IAB donor 101.

[0016] Here, within the IAB network 100, packets in the format of BAP data PDUs (Protocol Data Units) as packets (hereinafter sometimes referred to as BAP data packets) are transmitted. For example, an IP (Internet Protocol) packet destined for UE118 from CN130 is converted into a BAP data packet at the IAB donor 101 and transferred into the IAB network 100. The transferred BAP data packet is relayed by the IAB nodes 102 to 105, converted back into an IP packet at the IAB node 105, and delivered to the destination UE118. Similarly, for an IP packet from UE118, it is also converted into a BAP data packet at the IAB node 105, converted back into an IP packet at the IAB donor 101 via the IAB network 100, and transferred to CN130.

[0017] In the IAB network 100, when the IAB donor 101 transfers a packet destined for UE118, it is necessary to select either the communication path of the IAB node 102 or 103. Similarly, a multi-path is also formed from the IAB node 102 to the IAB node 105, and it is necessary to select a path for transferring the BAP data packet.

[0018] Here, the IAB nodes may have different types of network slices (slice types) that meet the communication requirements, that is, the supported slice types may be different. For example, the IAB node 102 supports eMBB and URLLC as slice types of IP packets, while the IAB node 104 may support only mMTC. In such a case, when transferring a BAP data packet based on an IP packet with a slice type of eMBB to UE118 via the path P1, since the IAB node 104 does not support eMBB, the slice type requirement (slice requirement) cannot be met.

[0019] Therefore, in the IAB donor 101 and the routing of BAP data packets at the IAB node, when a packet destined for the UE 118 requests a specific slice type, it is necessary to route through an IAB node that satisfies the slice request. In the following, in a network where a multi-path is formed like the IAB network 100, a method for transferring a packet with a specific slice request through a path configured by a communication device that supports the slice request will be described. Note that in this embodiment, downlink communication in which a packet from the CN 130 is transferred via the IAB donor 101 to the IAB nodes 102 to 105 will be described.

[0020] FIG. 2 is a hardware block diagram of a communication device according to this embodiment. The communication device includes a control unit 201, a storage unit 202, a wireless communication unit 203, and an antenna control unit 204.

[0021] The control unit 201 controls the entire communication device by executing a control program stored in the storage unit 202. In one example, the control unit 201 includes a processor that expands and executes the control program in a memory.

[0022] The storage unit 202 stores a control program executed by the control unit 201. Further, the storage unit 202 stores information used in the IAB network, such as the BAP address of its own station, the supported NSSAI, the UE information to be connected, and the routing information of the IAB nodes 102 to 105. Here, the BAP address is an address that can identify the IAB donor 101 or the IAB nodes 102 to 105 in the IAB network, and is used in the destination field of the header portion of the BAP data packet.

[0023] Also, as will be described later, the storage unit 202 stores information that can identify the communication path of the BAP data packet that has been communicated in the IAB network 100 in the past. For example, for the BAP data packet that has been communicated in the past, information that can identify the communication path may be stored in association with the source BAP address and the destination BAP address.

[0024] The wireless communication unit 203 is a wireless communication unit for performing cellular network communication such as LTE (Long Term Evolution) and 5G (fifth-generation mobile communication system) compliant with 3GPP standards. The antenna control unit 204 controls the antenna used for the wireless communication executed in the wireless communication unit 203.

[0025] Note that a plurality of control units 201 to antenna control units 204 may be arranged. Further, the communication device may include a configuration normally provided in a base station device, such as a wired communication unit.

[0026] FIG. 3 is a software block diagram of the communication device according to the present embodiment. The software block of the communication device is realized by the control unit 201 executing a program stored in the storage unit 202. The software block of the communication device includes a transmission / reception unit 301, a storage unit 302, a connection control unit 303, a slice request specifying unit 304, a route specifying unit 305, a notification unit 306, and a slice management unit 307.

[0027] The transmission / reception unit 301 controls the wireless communication unit 203 via the control unit 201, performs cellular network communication such as LTE and 5G compliant with 3GPP standards between the communication device and the UE, and transmits and receives IP packets. Further, the transmission / reception unit 301 transmits and receives BAP data packets within the IAB network 100. The connection control unit 303 controls the antenna control unit 204 via the control unit 201 during wireless communication.

[0028] The storage unit 302 controls and manages the storage unit 202 and stores programs executed by the control unit 201 such as the operating system of the communication device. Further, the storage unit 302 stores and holds the network topology of the IAB network 100, the communication route, the BAP address of the communication device, and information regarding the UE.

[0029] The slice management unit 307 stores and manages the NSSAI information supported by each IAB node. The NSSAI information is collected, for example, by BAP data packets or packets conforming to various control PDUs of BAP (hereinafter referred to as BAP control packets), but may also be collected by other means.

[0030] The slice request identification unit 304 identifies the slice requested by the packet received by the communication device. For example, when the IAB donor 101 receives an IP packet from the CN 130, the slice request is identified based on the IP packet. Also, when the IAB node receives a BAP data packet from the UE or another communication device, the slice request may be identified based on the received BAP data packet.

[0031] The path identification unit 305 identifies a communication path (path) composed of at least one of the communication devices such as the IAB donor 101 and the IAB nodes 102 to 105 that support the slice type of the received packet. Here, the communication device stores in the storage unit 302 a correspondence list (hereinafter referred to as a routing list) between the identifier (path ID) of the path set in the IAB network 100 and the slice types that can be supported.

[0032] In one example, the path identification unit 305 identifies the communication path by selecting a path that satisfies the slice requested by the communication packet based on the routing list. The method of path selection will be described later. The information that can identify the communication path identified by the path identification unit 305 is set in the path field of the BAP data packet as a path parameter.

[0033] When the path that satisfies the slice request cannot be identified, the notification unit 306 notifies the destination UEs 110 to 118 or the CN 130 that the slice request cannot be satisfied by using a BAP data message or a BAP control message. As a notification method, for example, it may be indicated that the slice request is not achieved in the PDU type field of the BAP control message.

[0034] Here, the path parameter is communication path information including the IAB donor 101, the BAP addresses of the IAB nodes 102 to 105, and the path ID. The path ID is information that identifies a path constituted by a combination of a series of relay IAB nodes from the IAB donor 101 to the destination IAB node of the BAP data packet.

[0035] FIG. 4 is a diagram for explaining a path within the IAB network 100 according to Embodiment 1. Here, the IAB network 100 will be described as an example with respect to the path ID included in the path parameter set in the BAP data packet. In the example of FIG. 4, the slice types supported by the communication device are shown in parentheses as slice type eMBB = 1, URLLC = 2, mMTC = 3. For example, the IAB donor 101, the IAB node 102, and the IAB node 105 support slice types 1, 2, 3. Also, the IAB node 103 supports slice types 2, 3, and the IAB node 104 supports slice types 1, 3.

[0036] In the IAB network 100, the paths from the IAB donor 101 to each of the IAB nodes 102 to 105 can be represented by paths with identifiers P1 to P3. The path P1 is a path ID that connects from the IAB donor 101 to the IAB node 105 via the radio sections (sections) 400, 403, 405. Also, P2 is a path ID that connects from the IAB donor 101 to the IAB node 105 via sections 400, 402, 404. Furthermore, P3 is a path ID that connects from the IAB donor 101 to the IAB node 105 via sections 401, 404. In this embodiment, it is described assuming that only three paths are set, but other paths such as a path connecting to the IAB node 105 via sections 401, 402, 403, 405 may be additionally or alternatively set.

[0037] In the IAB network 100 according to this embodiment, the communication device identifies a slice request based on an IP packet, identifies a path based on the identified slice request, and generates a BAP data packet in which path parameters capable of identifying the identified path are set. As a result, when converting an IP packet into a BAP data packet, the communication path within the IAB network 100 can be specified. Further, the IAB nodes 102 to 105 that relay the BAP data packet can identify the path for transferring the packet based on the path parameters included in the BAP data packet.

[0038] (Processing Example 1) FIG. 5 is a flowchart showing a method in which a communication device according to Processing Example 1 generates and transmits an IP packet as a BAP data packet. In the following description, it is assumed that the IAB donor 101 receives an IP packet from the CN 130, generates a BAP data packet, and transmits it to the IAB node.

[0039] In S500, the IAB donor 101 receives an IP packet from the CN 130. In S501, the IAB donor 101 identifies the BAP addresses of the IAB nodes 102 to 105 to which the BAP data packet is to be transferred from the destination IP address (UE's IP address) of the received IP packet, and sets them in the destination field of the BAP data packet. For example, when the destination is UE118, the BAP address set in the destination field of the BAP data packet is the BAP address of the IAB node 105.

[0040] In S502, the slice type required is identified by analyzing the destination IP address of the received IP packet or the application header. For example, when the range of IP address utilization is determined as a subnet for each slice within the IAB network 100, the slice type required can be identified only by the destination IP address. For example, for each slice type of the UE, the IP address of the UE that requests the slice type eMBB can be assigned from a predetermined range such as "192.168.1.*", URLLC is "192.168.2.*", and mMTC is "192.168.3.*". Here, * is an integer from 0 to 255. In this case, the IAB donor 101 can identify the slice request based on the address range of the destination IP address.

[0041] Alternatively, when the IAB donor 101 has a network interface (NIC) or a virtual NIC for each slice type, the IAB donor 101 may identify the slice request based on the NIC or virtual NIC that received the IP packet.

[0042] The processes of S503 to S505 are repeatedly processed for each path. Here, the path ID is used as a path parameter that identifies the path to the destination IAB node in combination with the destination BAP address determined in S501.

[0043] In S504, it is determined whether the path with the path ID of Pn (n is an integer from 1 to the number of paths) satisfies the slice request. Here, referring to the routing list, it is determined whether the path satisfies the slice request only for the IAB node 105 to which the destination UE 118 is connected. If Pn satisfies the slice in S504, S507 is processed; otherwise, the determination is made for the next path ID in S506. If there is no path that satisfies the slice request for all path IDs, the repeated processing of S503 to S505 is exited and S509 is processed.

[0044] In S507, according to the route identification result, Pn is set as the path ID that satisfies the slice request in the path ID field of the BAP data packet. In S508, the generated BAP data packet is transmitted to end the process shown in FIG. 5.

[0045] In S509, the IAB donor 101 generates a BAP control packet notifying that the slice request is not satisfied, and transmits it to the IAB nodes 102 to 105 to which the destination UEs 110 to 118 are connected to end the process shown in FIG. 5. In one example, the IAB donor 101 may notify the CN 130 as the source that the required slice is not satisfied by means of an IP packet or the like.

[0046] In this embodiment, it is assumed that communication between the CN 130 and the UEs 110 to 118 is performed using IP packets, but the route can be identified in the same way for other destinations. Also, in this embodiment, the process for transferring IP packets as BAP data packets has been described, but communication packets of other protocols can be processed in the same procedure.

[0047] As described above, in the route identification unit 305, by selecting a path that satisfies the slice request up to the IAB node to which the destination UE is connected and setting it in the path field of the header of the BAP data packet, it becomes possible to transfer the packet so as to satisfy the slice request.

[0048] FIG. 6 shows an example of the routing list of the IAB donor 101 according to this embodiment.

[0049] In FIG. 6, in the network configuration of FIG. 4, it is described that the IAB nodes 102 and 105 support eMBB, URLLC, and mMTC, the IAB node 103 supports URLLC and mMTC, and the IAB node 104 supports eMBB and URLLC.

[0050] The routing list 601 is a routing list managed by the IAB donor 101 and is composed of a BAP address, a path ID, and a supported slice type. The routing list 601 associates the BAP address as the address of other communication devices, the path ID as the path information composed of communication devices in the network, and the slice type supported by the communication devices. The slice type corresponds to SST (Slice Service Type). In FIG. 6, eMBB is shown as SST = "1", URLLC is shown as SST = "2", and mMTC is shown as SST = "3". Also, the BAP address is "0001" for IAB node 102, "0002" for IAB node 103, "0003" for IAB node 104, and "0004" for IAB node 105. The path IDs are P1 to P3 described with reference to FIG. 4.

[0051] In 601, since the IAB node 103 does not support eMBB (SST = 1), eMBB (SST = 1) is not supported in paths P2 and P3 via the IAB node 103 with the BAP address "0002". Also, since the IAB node 104 does not support URLLC, URLLC (SST = 2) is not supported in path P1 via the IAB node 104 with the BAP address "0003".

[0052] Here, taking the case where the IAB donor 101 transfers a packet requesting eMBB as a slice request to the UE 118 as an example, the operation of specifying the path will be described.

[0053] In S501, the IAB donor 101 specifies the destination BAP address based on the destination of the IP packet. Since the UE 118 is connected to the IAB node 105, the IAB donor 101 specifies that the destination BAP address of the BAP data packet is "0004" and sets "0004" as the destination address of the BAP data packet.

[0054] In the routing list 601, the path IDs for the BAP address "0004" are P1, P2, and P3, and the path ID that can support eMBB in S503 to S505 is P1. Therefore, the IAB donor 101 sets the path field of the BAP data packet to transfer the BAP data packet using path P1. As a result, the IAB nodes 102, 104, and 105 that receive the BAP data packet can relay the BAP data packet in a communication device that satisfies the slice requirement by referring to the path field and relaying the packet.

[0055] Also, when the IAB donor 101 transfers a communication packet requesting URLLC to UE117, the BAP address is "0004", and it is specified that the path ID for packet transfer by a communication device that supports URLLC is P2.

[0056] (Method for creating a routing list) Here, with reference to FIG. 6, the process of creating a routing list will be described.

[0057] Here, in the network configuration shown in FIG. 4, for the path IDs P1, P2, and P3, the process of creating the routing list shown in FIG. 6 will be described. In this embodiment, the description will be made assuming that the IAB donor 101 creates the routing list, but other nodes such as CN130 may create it and send the routing list to the IAB donor 101. Alternatively, the IAB node may create the routing list in the same way. That is, the communication device may create a routing list based on the slice type and path supported by other communication devices, or the communication device may receive a routing list from other communication devices or CN130.

[0058] Here, it is assumed that the IAB donor 101 has information regarding the identifiers of the IAB nodes through which the path IDs P1, P2, and P3 pass, and the slice types supported by each IAB node. For example, the IAB donor 101 has information that can identify that for the path ID P1, it passes through the IAB nodes 102, 104, and IAB node 105. Note that for each path ID, it may be associated with whether it is a path used in downlink communication or a path used in uplink communication. Also, the IAB donor 101 has information that can identify that the IAB node 102 supports slice types 1, 2, 3, the IAB node 104 supports slice types 1, 3, and the IAB node 105 supports slice types 1, 2, 3.

[0059] In this case, for the IAB node 102 through which the path ID P1 first passes, the slice types 1, 2, 3 are supported. From this, the IAB donor 101 registers the data 611 indicating that the slice types 1, 2, 3 are supported at the BAP address 0001 (IAB node 102) for the path ID P1.

[0060] Subsequently, for the path ID P1, the slice types 1, 3 are supported at the BAP address 0003 (IAB node 104). Also, the slice types 1, 2, 3 are supported in the path P1 from the IAB node 104 to the IAB node 102 connected to it. Therefore, the IAB donor 101 determines that the slice types common to the slice types supported in the path up to the BAP address 0003 and the slice types 1, 3 supported by the BAP address 0003 are supported in the path P1 up to the BAP address 0003. For this reason, the IAB donor 101 registers the data 612 indicating that the slice types 1, 3 are supported at the BAP address 0003 (IAB node 104) for the path ID P1.

[0061] Next, regarding path ID P1, at BAP address 0004 (IAB node 105), slice types 1, 2, and 3 are supported. Also, on path P1 from IAB node 105 to IAB node 104 connected to it, slice types 1 and 3 are supported. Therefore, IAB donor 101 determines that on path P1 up to BAP address 0004, it supports the slices that are common between the slice types supported on the path up to BAP address 0004 and the slice types 1, 2, and 3 supported by BAP address 0004. For this reason, IAB donor 101 registers data 613 indicating that slice types 1 and 3 are supported at BAP address 0004 (IAB node 105) for path ID P1.

[0062] By making the same determination for other path IDs, it is possible to determine the supported slice types in association with the path IDs and the nodes located on the paths.

[0063] FIG. 7 is a sequence diagram showing the process of specifying a path according to the slice type according to the present embodiment.

[0064] In S700, in IAB network 100, an RRC (Radio Resource Control) link is established and a path ID is assigned by IAB donor 101. RRC has functions such as connection establishment, admission control, RRC state management, notification of peripheral cell information and access restrictions in IAB nodes 102 to 105 and UEs 110 to 119.

[0065] In S701, IAB donor 101 collects the NSSAI, which is the slice support information of each IAB node 102 to 105. In S702, UE 118 sends a Registration request to CN 130 to request the use of an eMBB slice. In S704, CN 130 sends a Registration accept permitting the use of the slice by UE 118.

[0066] In S705 and S706, similarly, for UE117 to perform URLLC usage registration, CN130 exchanges Registration request and Registration accept. Similarly, in S708 and S710, UE118 requests mMTC from CN130, and CN130 permits the request. Although omitted in FIG. 7, each UE requests the network slice it wishes to use from CN130.

[0067] In S703, S706, and S709, IAB donor 101 stores the IP addresses of UE117 and 118 and the slice types permitted for each. This is to identify the required slice when receiving IP packets from CN130 for each UE117 and 118. In this embodiment, it is described that when receiving an IP packet from CN130, the required slice is identified based on the destination address of the IP packet. However, as described above, the required slice may be identified by other methods.

[0068] In S711, IAB donor 101 creates an IAB routing list from the path ID and BAP address assigned in S700 and the slice support information of each IAB node collected in S701.

[0069] In S712, CN130 sends an IP packet requesting eMBB for UE118. In S713, IAB donor 101 identifies the required slice of the received IP packet from the destination IP address.

[0070] In S714, the BAP address of IAB node 105 is identified from the IP address of UE118, and P1 is identified as the path ID that meets eMBB from the routing list. Also, IAB donor 101 generates a BAP data packet based on the IP packet. Further, IAB donor 101 sets the BAP address and the path ID in the header of the BAP data packet and transmits it to IAB node 105. In S715 and S716, IAB nodes 102 and 104 transfer the BAP data packet according to P1 set in the path ID. In S717, IAB node 105, which is the destination BAP address, receives the BAP data packet, reconverts it into an IP packet for transfer to UE118, and transmits it to UE118. In S718, UE118 receives the IP packet transferred via a path that meets the eMBB requirement.

[0071] In S719, CN130 transmits an IP packet requesting URLLC for UE117. In S720, IAB donor 101 identifies the requested slice of the received IP packet.

[0072] In S721, the BAP address of IAB node 105 is identified from the IP address of UE117, P2 is selected as the path ID that meets URLLC from the routing list, a BAP data packet is generated and transmitted to IAB node 105. In S722 and S723, IAB nodes 102 and 103 transfer the BAP data packet according to P2 set in the path ID. In S724, IAB node 105 receives the BAP data packet, converts it into an IP packet, and transmits it to UE117. In S725, UE117 receives the IP packet that meets the URLLC requirement.

[0073] As described above, when IAB donor 101 receives an IP packet, it generates and transmits a BAP data packet with the path parameters that meet the slice requirement set in the header. As a result, in the IAB network 100 with a multi-path formed, it becomes possible to relay the BAP data packet through a communication path composed of communication devices in the network that meet the slice requirements to the destination UE.

[0074] (Processing Example 2) In Processing Example 1, the downlink transmission of sending IP packets from CN130 to destination UEs 117 and 118 via IAB network 100 from IAB donor 101 was described. In Processing Example 2, the uplink operation of sending packets requesting a specific slice from UE118 to CN130 via IAB network 100 from IAB node 105 will be described.

[0075] When IAB node 105 receives an IP packet addressed to CN130 from UE118, similar to Processing Example 1, IAB node 105 converts it into a BAP data packet and transmits it. At this time, the address of IAB donor 101 is set as the BAP address. Also, the path ID is selected by referring to the routing list.

[0076] The routing list in IAB node 105 is created from the path ID in IAB network 100, the BAP addresses of IAB donor 101 and each of IAB nodes 102 to 105, and the supported NSSAI in the same manner as in Processing Example 1. Note that for IAB nodes 102 to 105 according to Processing Example 2, each node may create a routing list, or may receive a routing list created by IAB donor 101 or CN130.

[0077] Fig. 8 shows an example of the routing list of IAB node 105 according to this embodiment.

[0078] In routing list 801, the BAP address "0000" is the address of IAB donor 101. Here, as shown in Fig. 4, assume that IAB node 103 supports URLLC and mMTC, and IAB node 104 supports eMBB and URLLC. Also, assume that IAB nodes 102 and 105 support eMBB, URLLC, and mMTC.

[0079] Taking the case where the IAB node 105 transfers the packets requesting eMBB from the UE 118 using the routing list 801 as an example, the process of identifying the path for transferring the BAP data packets in FIG. 5 will be described.

[0080] In S501, the IAB node 105 receives an IP packet with the slice type of eMBB from the UE 118. Since the CN 130 is connected to the IAB donor 101, the destination BAP address of the BAP data packet becomes "0000". Therefore, in S502, the IAB node 105 identifies that the destination BAP address of the IP packet received from the UE 118 is "0000", and sets the destination BAP address "0000" in the BAP data packet.

[0081] In the routing list 801, among the path IDs P1, P2, and P3 for the BAP address "0000", the path ID that can support eMBB (slice type 1) is P1. Therefore, in S507, the IAB node 105 sets P1 in the path field of the header of the BAP data packet, and transmits the BAP data packet in S508.

[0082] Also, when the IAB node 105 transfers the URLLC packets from the source UE 117, similarly, the BAP address becomes "0000", and the path through which the packets are transferred by the communication device supporting URLLC (slice type 2) is P2 or P3. Therefore, based on the path previously determined to be the path supporting URLLC, the header of the BAP data packet is set and transmitted.

[0083] Note that in the example of FIG. 5, it is shown that when a path satisfying the slice request is found, the loop processing of S503 to S505 ends. In one example, the communication device may determine whether each path satisfies the slice request, and then select the path that satisfies the slice request and proceed to the processing of S507 to S508. In this case, when multiple paths support the slice type, the multiple paths may be used in order.

[0084] As described above, even in the case of an uplink that transmits a communication packet requesting a specific slice from the UEs 110 to 118 to the CN 130, it is possible to perform communication through a path that satisfies the slice request within the IAB network 100.

[0085] <Embodiment 2> In Embodiment 1, the process in which a communication device receives an IP packet, identifies the slice type and communication path that a communication device that transfers a BAP data packet should support, sets the header of the BAP data packet, and performs the transfer was described.

[0086] In Embodiment 2, the communication device transmits the slice type of the received IP packet to a first other communication device that supports the slice type, together with information capable of identifying the slice type. The first other communication device that has received the BAP data packet from the communication device identifies the slice type, identifies a second other communication device that supports the slice type, and transfers the BAP data packet.

[0087] A communication method executed by the communication device according to this embodiment will be described with reference to FIG. 9. The process shown in FIG. 9 is executed by the control unit 201 of the communication device.

[0088] In S900, the communication device receives a packet. For example, the IAB donor 101 receives an IP packet from the CN 130, the IAB node receives an IP packet from the UE, or the IAB node receives a BAP packet from another IAB node.

[0089] In S901, the communication device identifies the slice type that a communication device that transfers a BAP data packet should support based on the received packet. When the IAB donor 101 or the IAB node receives an IP packet, the slice type may be identified based on the destination IP address or address range as described above. Also, when the IAB node receives a BAP packet from another IAB node, the slice type may be identified based on the header of the BAP data packet.

[0090] Subsequently, in S902 to S904, the communication device determines whether other directly connected communication devices (adjacent nodes) support the slice type specified in S901. For example, in the topology of FIG. 4, when the IAB node 102 receives a BAP data packet from the IAB donor 101, it determines the slice types supported by the IAB nodes 103 and 104. If it is determined that any of the adjacent nodes supports the slice request (Yes in S903), the communication device proceeds to S906. In S906, based on the information of the adjacent nodes that satisfy the slice request specified in S902 to S904, a BAP data packet with the NEXT HOP of the path field set is generated. Subsequently, the communication device transmits the generated BAP data packet to the specified adjacent node (S907). When the communication device receives a BAP data packet in S900, only the path field of the BAP data packet may be updated. When the communication device receives an IP packet in S900, a BAP data packet is generated based on the IP packet, and a value indicating the specified slice request is set in the packet header. In one example, the SST value is assigned to the reserved bits of the packet header.

[0091] The processes of S907 and S908 are the same as S508 and S509 in FIG. 5, so the description is omitted.

[0092] As described above, when relaying a BAP data packet, the communication device according to this embodiment identifies another communication device that supports the slice type, creates a BAP data packet, and transmits it. As a result, if each communication device can identify the slice types supported by adjacent nodes, the IAB donor 101 can route the BAP data packet through a communication path that satisfies the slice request without creating a routing list.

[0093] <Other Embodiments> Also, in one example, the communication device acquires information regarding communication history, such as the addresses and paths of other communication devices, included in the headers of BAP data packets transmitted and received in the past within the network, and identifies the destination of the BAP data packet based on the acquisition result. Thereby, it is possible to identify other communication devices that transmit BAP data packets based on the packets transmitted and received by the communication device in the past.

[0094] For example, in Processing Example 2 of Embodiment 1, the IAB nodes 102 to 105 were described as determining the path ID using a routing list. In another example, the path ID of the BAP data packet from the IAB donor 101 received in the past and the IP address of the UE may be stored, and when converting an IP packet from the UE, an uplink path corresponding to the same path or a downlink path may be set and transmitted.

[0095] Also, for example, in Embodiment 2, as a result of transferring a packet based on whether an adjacent node supports the slice type of the BAP data packet, there may be a case where a transfer destination cannot be found. In such a case, the communication device that has received a notification of failure to identify another communication device that supports the slice type can transfer the BAP data packet to an adjacent node within a network different from the previously transmitted adjacent node.

[0096] 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. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

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

Description of Reference Numerals

[0098] 100 IAB network, 101 IAB donor, 102 - 105 IAB nodes, 110 - 118 UEs, 201 control unit, 202 memory unit, 203 wireless communication unit, 204 antenna control unit, 301 transceiver unit, 302 memory unit, 303 connection control unit, 304 slice request specifying unit, 305 path specifying unit, 306 notification unit, 307 slice management unit

Claims

1. A communication device in a network that communicates using BAP (Backhaul Adaptation Protocol), comprising: first specifying means for specifying a slice type that should be supported by another communication device in the network that transfers the first packet based on the received first packet; second specifying means for specifying another communication device that supports the slice type specified by the first specifying means based on the slice type supported by another communication device in the network; transmission means for transmitting, to the other communication device specified by the second specifying means, a second packet communicated using BAP generated based on the first packet, wherein the header of the second packet is set according to the specification result of the second specifying means; A communication device characterized by comprising the above.

2. The second specifying means specifies a communication path that supports the slice type as the other communication device that supports the slice type, The communication device according to claim 1, wherein the header of the second packet includes an identifier of a communication path from the communication device to another communication device that is the destination of the second packet.

3. The communication device further comprises storage means for storing a routing list associating an identifier of a communication path for transferring a packet in the network, an address of another communication device in the network, and a slice type supported by the other communication device, The communication device according to claim 2, wherein the second specifying means specifies another communication device included in a communication path that supports the slice type specified by the first specifying means based on the routing list.

4. The communication device according to claim 3, further comprising creation means for creating the routing list.

5. The communication device according to any one of claims 2 to 4, wherein the identifier of the communication path is set in a path field of the second packet.

6. The second specifying means specifies another communication device that supports the slice type and is directly connected to the communication device, The communication device according to claim 1, wherein the header of the second packet includes the BAP address of the other communication device as NEXT HOP.

7. The communication device according to any one of claims 1 to 6, wherein the communication device is an IAB (Integrated Access Backhaul) node that uses NR (New Radio) communication for both a backhaul link and an access link in the network, or an IAB donor that centrally controls the IAB node.

8. The communication device according to any one of claims 1 to 7, wherein the first specifying means specifies the slice type based on the destination address of the first packet or the application header of the first packet.

9. The communication device according to any one of claims 1 to 8, further comprising a notifying means for notifying that the specification has failed when another communication device that supports the slice type specified by the first specifying means cannot be specified by the second specifying means.

10. The communication device further has a second obtaining means for obtaining information regarding the header of a second packet transmitted and received in the network in the past, The communication device according to any one of claims 1 to 9, wherein the second specifying means specifies another communication device that supports the slice type specified by the first specifying means based on the acquisition result of the second obtaining means.

11. The communication device according to any one of claims 1 to 10, wherein the first packet is an IP (Internet Protocol) packet, and the communication device receives the first packet from a CN (Core Network) node or a user equipment (UE).

12. The communication device according to any one of claims 1 to 10, wherein the first packet is a BAP data packet, and the communication device receives the first packet from an IAB donor or an IAB node.

13. A communication method for a communication device in a network that communicates using BAP (Backhaul Adaptation Protocol), comprising: specifying, based on a received first packet, a slice type that another communication device in the network that transfers the first packet should support; and specifying, based on the slice type supported by another communication device in the network, another communication device that supports the specified slice type. A second packet communicated using a BAP generated based on the first packet, the second packet having a header set according to a specific result, is transmitted to the identified other communication device. A communication method characterized by including the above.

14. A program executed by a communication device of a network that communicates using BAP (Backhaul Adaptation Protocol), a first specifying step of specifying a slice type that another communication device in the network that transfers the first packet should support, based on the received first packet; a second specifying step of specifying another communication device that supports the slice type specified in the first specifying step, based on the slice type supported by another communication device in the network; a transmission step of transmitting, to the other communication device specified in the second specifying step, a second packet communicated using a BAP generated based on the first packet, the second packet having a header set according to the specifying result of the second specifying step; A program characterized by causing the above to be executed.

Images