Communication methods and related devices

Abstract

A communication method and related equipment are provided. The method includes: a first donor node generating first information, the first information indicating a slice corresponding to a first backhaul radio link control (RLC) channel, the first backhaul RLC channel being a backhaul RLC channel corresponding to a first integrated access and backhaul (IAB) node. The first donor node transmits the first information to the first IAB node. In this method, the first information indicates a slice corresponding to the first backhaul RLC channel corresponding to the first IAB node, and as a result, slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation in the IAB architecture and ensuring preferred and reliable communication for high-priority services.

Description

Technical Field

[0001]

[0001] This application claims priority to Chinese Patent Application No. 202310309625.5, titled "Communication Method and Related Device", filed with the China National Intellectual Property Administration on March 17, 2023, and Chinese Patent Application No. 202311140366.4, titled "Communication Method and Related Device", filed with the China National Intellectual Property Administration on September 5, 2023. The entire disclosures of both applications are incorporated herein by reference.

[0002]

[0002] Technical Field This application relates to the field of communication technologies, and particularly relates to communication methods and related devices.

Background Art

[0003]

[0003] Compared to fourth-generation mobile communication systems, fifth-generation (5G) mobile communication systems and future mobile communication systems impose stricter requirements on network performance metrics. For example, compared to 4G, 5G achieves a 1000-fold increase in capacity and has requirements for wider coverage, ultra-high reliability, low latency, and similar factors. In one aspect, to meet the ultra-high capacity requirements of 5G, high-frequency small-cell networking is becoming increasingly popular, assuming that high-frequency carrier frequency resources are abundant in hotspot areas. High-frequency carriers have poor propagation characteristics, are severely attenuated by obstacles, and have low coverage. Therefore, a large number of small cells need to be densely deployed. However, providing fiber optic backhaul to a large number of densely deployed small cells is costly and difficult to construct. Therefore, a cost-effective and convenient backhaul solution is required. In another aspect, given the requirements for broad coverage, deploying fiber optics is difficult and costly to provide network coverage in some remote areas. Therefore, there is a need to design flexible and convenient access and backhaul solutions. Integrated access and backhaul (IAB) technology offers an idea to solve the two aforementioned problems. Its access link and backhaul link (BL) each reduce the deployment of fiber optics by using wireless transmission solutions.

[0004]

[0004] In an IAB network, relay nodes (RN) or IAB nodes can provide radio access services and service data transfer to user equipment (UE). The UE's service data is transmitted by the IAB node to the IAB donor via a radio backhaul link. The IAB donor is sometimes called a donor node or donor base station (donor gNodeB, DgNB). An IAB node includes a mobile termination (MT) part and a distributed unit (DU) part. When facing a parent node, the IAB node can function as a terminal device, i.e., as an MT. When facing a child node (which may be another IAB node or UE), the IAB node is considered a network device, i.e., as a DU. A donor base station (DgNB) may be an access network element with full base station functionality, or it may be an access network element in which a central unit (CU) and distributed units (DU) are separated. The donor base station is connected to a core network element corresponding to the UE (e.g., connected to a 5G core network) and provides radio backhaul functionality to the IAB node.

[0005]

[0005] As a mandatory characteristic of UE end-to-end protocol data unit (PDU) sessions, slicing cannot achieve end-to-end slice resource isolation in the IAB architecture. As a result, it is not possible to guarantee prioritized and reliable communication for high-priority services. [Overview of the project]

[0006]

[0006] Embodiments of the present application provide a communication method and related apparatus for achieving end-to-end slice resource isolation in an IAB architecture, thereby ensuring preferred and reliable communication for high-priority services.

[0007]

[0007] According to a first aspect, embodiments of the present application provide a communication method. The method may be performed by a communication device. The communication device may be a device, or a chip (system) or circuit used in a device. This is not limited to the present application. The method includes the following:

[0008]

[0008] The first donor node generates first information, which indicates a slice corresponding to the first backhaul radio link control RLC channel, and the first backhaul RLC channel is the backhaul RLC channel corresponding to the first integrated access and backhaul IAB node.

[0009]

[0009] The first donor node transmits the first information to the first IAB node.

[0010]

[0010] This embodiment of the present application provides a communication method. A first donor node generates first information and transmits the first information to a first integrated access and backhaul (IAB) node. The first information indicates a slice corresponding to a first backhaul radio link control (RLC) channel corresponding to the first IAB node. After receiving the first information, it will be understood that the first IAB node establishes a first backhaul RLC channel based on the slice indicated by the first information. Since the resources used by the first backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel can be achieved, thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, a backhaul RLC channel corresponding to a high-priority service can use specific slice resources to ensure preferred and reliable communication of the high-priority service.

[0011]

[0011] In a possible implementation, the first information includes one or more slice identifiers corresponding to a first backhaul RLC channel.

[0012]

[0012] This implementation of the present application provides a specific possible implementation of the first information. Specifically, the first information includes one or more slice identifiers corresponding to a first backhaul RLC channel, and the first information can specify a slice corresponding to the first backhaul RLC channel by using the slice identifiers contained in the first information, thereby enabling slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0013]

[0013] In a possible implementation, the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the first backhaul RLC channel.

[0014]

[0014] This implementation of the present application provides a specific possible implementation of the first information. Specifically, the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, where reserved resources are a proportion of resources reserved on the air interface for the first backhaul RLC channel, and the proportion of reserved resources may include, but not limited to, preferred resources (resources used preferentially by the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared and used by multiple backhaul RLC channels such as the first backhaul RLC channel), or similar. This is not limited to this embodiment of the present application. In this embodiment of the present application, the first information indicates that the first backhaul RLC channel uses reserved resources and implements slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0015]

[0015] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0016]

[0016] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the first backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0017]

[0017] In a possible implementation, before the first donor node transmits the first information to the first IAB node, the method further includes the following:

[0018]

[0018] The first donor node receives second information from the first node, the second information indicating that the resources used by the first protocol data unit PDU session are reserved resources, and the first PDU session includes a PDU session corresponding to the first donor node.

[0019]

[0019] This implementation of the present application provides a specific possible implementation of slice-based IAB backhaul configuration. Specifically, a first donor node receives second information from the first node, which indicates that the resources used by a protocol data unit (PDU) session corresponding to the first donor node are reserved resources. In a scenario in which the first node initiates a PDU session resource configuration request to the first donor node, it will be understood that, after receiving the second information, the first donor node establishes the PDU session based on the reserved resources indicated by the second information. In this embodiment of the present application, the second information indicates that the PDU session uses the reserved resources to implement slice resource isolation between the transmit and receive ends corresponding to a first backhaul RLC channel used by the PDU session.

[0020]

[0020] In a possible implementation, before the first donor node transmits the first information to the first IAB node, the method further includes the following:

[0021]

[0021] The first donor node receives third information from the first node, and the third information indicates that the first IAB node is a node that provides first priority services.

[0022]

[0022] This implementation of the present application provides a specific possible implementation of slice-based IAB backhaul configuration. Specifically, a first donor node receives third information from the first node, which indicates that the first IAB node is a node providing a first priority service, which may be a node providing a high priority service such as public safety. In a scenario in which the first IAB node first registers with and accesses the network, it will be understood that the first node initiates a UE context configuration request to the first donor node, which includes the third information. After receiving the third information, the first donor node may determine, in accordance with the instructions of the third information, that the first IAB node is a node providing a high priority service, and by using the first information, instruct the first IAB node to establish a corresponding first backhaul RLC channel based on the slice indicated by the first information, and may implement slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel. In this embodiment of the present application, the third piece of information indicates that the first IAB node is a node providing a first priority service, and that slice resource isolation is implemented between the transmitting and receiving ends corresponding to the first backhaul RLC channel corresponding to the first IAB node.

[0023]

[0023] In possible implementations, the method further includes the following:

[0024]

[0024] The first donor node receives the fourth information from the first IAB node, which indicates that the first IAB node is a node that provides a first priority service.

[0025]

[0025] In this implementation of the present application, a specific implementation form of slice-based IAB backhaul configuration is provided. Specifically, the first donor node receives fourth information from the first IAB node, and the fourth information indicates that the first IAB node is a node that provides services with a first priority, for example, a node that provides high-priority services such as public safety. In the scenario where the first IAB node first registers and accesses the network, it will be understood that the first IAB node transmits the fourth information to the first donor node. After receiving the fourth information, the first donor node determines, according to the instruction of the fourth information, that the first IAB node is a node that provides high-priority services, and by using the first information, instructs the first IAB node to establish a corresponding first backhaul RLC channel based on the slice indicated by the first information, and may implement slice resource separation between the transmitting end and the receiving end corresponding to the first backhaul RLC channel. In this embodiment of the present application, the fourth information indicates that the first IAB node is a node that provides services with a first priority, and slice resource separation is implemented between the transmitting end and the receiving end corresponding to the first backhaul RLC channel corresponding to the first IAB node.

[0026]

[0026] In a possible implementation, the method further includes the following.

[0027]

[0027] The first donor node determines, based on the third information, that the first backhaul RLC channel needs to use reserved resources.

[0028]

[0028] This implementation of the present application provides a specific implementation that enables slice-based IAB backhaul configuration. Specifically, after receiving third information from a first node, the first donor node determines, in accordance with the instructions of the third information, that the first IAB node is a node that provides high-priority services and that the first backhaul RLC channel needs to use reserved resources, and by using the first information, instructs the first IAB node to establish a corresponding first backhaul RLC channel based on the slice indicated by the first information, thereby implementing slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0029]

[0029] In a possible implementation, the first information includes a slice identifier corresponding to the first migration data, the first migration data includes data transmitted after the first IAB node transitions from a connection with a first donor node to a connection with a second donor node, the second donor node being different from the first donor node.

[0030]

[0030] In this implementation of the present application, a possible specific implementation form of the first information is provided. Specifically, in the IAB inter-topology data migration scenario, for example, the first IAB node migrates from a connection with the first donor node to a connection with the second donor node. Correspondingly, after the migration of the first IAB node between the connections with the donor nodes, the first migration data is transmitted, and the first information further includes a slice identifier corresponding to the first migration data, specifically, it may include one or more slice identifiers corresponding to the first migration data. The first information is a slice identifier corresponding to the first migration data. By using the slice identifier included in the first information, the slice corresponding to the backhaul RLC channel used by the first migration data is specified, the slice resource separation between the transmitter and the receiver corresponding to the backhaul RLC channel used by the first migration data is implemented, the end-to-end slice resource separation in the IAB architecture is implemented, and it is possible to ensure the preferentially reliable communication of high-priority services.

[0031]

[0031] In a possible implementation, the first information further indicates a slice corresponding to the second backhaul RLC channel, and the second backhaul RLC channel is the backhaul RLC channel corresponding to the second donor node.

[0032]

[0032] This implementation of the present application provides a specific possible implementation of the first information. Specifically, in an IAB inter-topology data migration scenario, for example, a first IAB node transitions from a connection with a first donor node to a connection with a second donor node. The first donor node can notify the second donor node of the slice corresponding to the first backhaul RLC channel in its topology, and the second donor node, based on the slice corresponding to the first backhaul RLC channel, sets the slice corresponding to the second backhaul RLC channel in the topology of the second donor node and feeds back the slice corresponding to the second backhaul RLC channel to the first donor node. In this case, the first information transmitted by the first donor node to the first IAB node can further indicate the slice corresponding to the second backhaul RLC channel. It will be understood that the slice corresponding to the second backhaul RLC channel may be the same as or different from the slice corresponding to the first backhaul RLC channel. This is not limited to this embodiment of the present application. It will be understood that, after receiving the first information, the first IAB node establishes the second backhaul RLC channel based on the slice indicated by the first information and performs IAB inter-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation can be implemented between the transmitting and receiving ends corresponding to the second backhaul RLC channel, thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to a high-priority service can use specific slice resources to ensure preferred and reliable communication of the high-priority service.

[0033]

[0033] Optionally, the first information includes one or more slice identifiers corresponding to the second backhaul RLC channel.

[0034]

[0034] Optionally, the first information further indicates that the resources used by the second backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the second backhaul RLC channel.

[0035]

[0035] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0036]

[0036] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the second backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0037]

[0037] In possible implementations, the slice corresponding to the second backhaul RLC channel differs from the slice corresponding to the first backhaul RLC channel in that the first information further indicates the mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.

[0038]

[0038] In possible implementations, the mapping relationships include the following:

[0039]

[0039] The slice identifier corresponding to the first backhaul RLC channel is the same as or different from the slice identifier corresponding to the second backhaul RLC channel.

[0040]

[0040] In possible implementations, the mapping relationships include the following:

[0041]

[0041] The slice / service type SST corresponding to the first backhaul RLC channel is the same as the slice / service type SST corresponding to the second backhaul RLC channel, and the slice differentiator (SD) corresponding to the first backhaul RLC channel is different from the slice differentiator SD corresponding to the second backhaul RLC channel; or

[0042]

[0042] The slice / service type SST corresponding to the first backhaul RLC channel is different from the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is the same as the slice distinguisher SD corresponding to the second backhaul RLC channel.

[0043]

[0043] In possible implementations, the method further includes the following:

[0044]

[0044] The first donor node receives the fifth piece of information from the first IAB node, and the fifth piece of information indicates slice resource congestion.

[0045]

[0045] This embodiment of the present application provides a specific possible embodiment of indicating slice resource congestion. Specifically, a first donor node receives fifth information from a first IAB node, the fifth information indicating slice resource congestion. After receiving the fifth information, the first donor node determines that the current slice resource is congested and performs traffic control of different slice services to ensure the quality of service of the slice services.

[0046]

[0046] In a possible implementation, the nodes in the first backhaul adaptive protocol BAP topology support the slice indicated by the first information, the first BAP topology is managed by the first donor node, and the first IAB node belongs to the first BAP topology.

[0047]

[0047] This implementation of the present application provides a specific implementation form that allows backhaul adaptation protocol (BAP) route configuration. Specifically, the nodes in a first BAP topology support slices indicated by first information, the first BAP topology includes a first donor node and a first IAB node, and the first BAP topology is managed by the first donor node. When configuring a BAP route, it will be understood that the first donor node must take into account the slice types supported by each hop of the IAB node and ensure that each IAB node on the BAP path supports the target slice.

[0048]

[0048] According to a second aspect, embodiments of the present application provide a communication method. The method may be performed by a communication device. The communication device may be a device, or a chip (system) or circuit used in a device. This is not limited to the present application. The method includes the following:

[0049]

[0049] The first integrated access and backhaul IAB node receives first information from the first donor node, the first information indicating a slice corresponding to the first backhaul radio link control RLC channel, the first backhaul RLC channel being the backhaul RLC channel corresponding to the first IAB node.

[0050]

[0050] The first donor node establishes a first backhaul RLC channel based on the first information.

[0051]

[0051] This embodiment of the present application provides a communication method. A first IAB node receives first information from a first donor node and establishes a first backhaul RLC channel based on the first information. The first information indicates a slice corresponding to the first backhaul channel corresponding to the first IAB node. After receiving the first information, it will be understood that the first IAB node establishes a first backhaul RLC channel based on the slice indicated by the first information. Since the resources used by the first backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation can be implemented between the transmitting and receiving ends corresponding to the first backhaul RLC channel, thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, a backhaul RLC channel corresponding to a high-priority service can use specific slice resources to ensure preferred and reliable communication of the high-priority service.

[0052]

[0052] In a possible implementation, the first information includes one or more slice identifiers corresponding to a first backhaul RLC channel.

[0053]

[0053] This implementation of the present application provides a specific possible implementation of the first information. Specifically, the first information includes one or more slice identifiers corresponding to a first backhaul RLC channel, and the first information can specify a slice corresponding to the first backhaul RLC channel by using the slice identifiers contained in the first information, thereby enabling slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0054]

[0054] In a possible implementation, the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the first backhaul RLC channel.

[0055]

[0055] This implementation of the present application provides a specific possible implementation of the first information. Specifically, the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, where reserved resources are allocations of resources reserved on the air interface for the first backhaul RLC channel, and the allocation of reserved resources may include, but are not limited to, preferred resources (resources used preferentially by the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared and used by multiple backhaul RLC channels such as the first backhaul RLC channel), or similar. This is not limited to this embodiment of the present application. In this embodiment of the present application, the first information indicates that the first backhaul RLC channel uses reserved resources and implements slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0056]

[0056] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0057]

[0057] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the first backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0058]

[0058] In a possible implementation, before the first integrated access and backhaul IAB node receives the first information from the first donor node, the method further includes:

[0059]

[0059] The first IAB node transmits the fourth information to the first donor node, which indicates that the first IAB node is the node providing the first priority service.

[0060]

[0060] This implementation of the present application provides a specific implementation form of slice-based IAB backhaul configuration. Specifically, a first IAB node transmits a fourth piece of information to a first donor node, which indicates that the first IAB node is a node providing a first priority service, which may be a node providing a high priority service such as public safety. In a scenario in which the first IAB node first registers with and accesses the network, it will be understood that the first IAB node transmits the fourth piece of information to the first donor node. After receiving the fourth piece of information, the first donor node may determine, in accordance with the instructions of the fourth piece of information, that the first IAB node is a node providing a high priority service, and by using the first piece of information, instruct the first IAB node to establish a corresponding first backhaul RLC channel based on the slice indicated by the first piece of information, and may implement slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel. In this embodiment of the present application, the fourth piece of information indicates that the first IAB node is a node providing a first priority service, and that slice resource isolation is implemented between the transmitting and receiving ends corresponding to the first backhaul RLC channel corresponding to the first IAB node.

[0061]

[0061] In a possible implementation, the first information includes a slice identifier corresponding to the first migration data, the first migration data includes data transmitted after the first IAB node transitions from a connection with a first donor node to a connection with a second donor node, the second donor node being different from the first donor node.

[0062]

[0062] This implementation of the present application provides a specific possible implementation of the first information. Specifically, in an IAB inter-topology data migration scenario, for example, a first IAB node migrates from a connection with a first donor node to a connection with a second donor node. Correspondingly, after the migration of the first IAB node between connections with donor nodes, the first migration data is transmitted, and the first information further includes slice identifiers corresponding to the first migration data, and specifically may include one or more slice identifiers corresponding to the first migration data. The first information is a slice identifier corresponding to the first migration data, and by using the slice identifier contained in the first information, it is possible to specify the slice corresponding to the backhaul RLC channel used by the first migration data, thereby implementing slice resource isolation between the transmitting and receiving ends corresponding to the backhaul RLC channel used by the first migration data, implementing end-to-end slice resource isolation in the IAB architecture, and ensuring preferred and reliable communication for high-priority services.

[0063]

[0063] In a possible implementation, the first information further indicates a slice corresponding to a second backhaul RLC channel, the second backhaul RLC channel being the backhaul RLC channel corresponding to a second donor node.

[0064]

[0064] This implementation of the present application provides a specific possible implementation of the first information. Specifically, in an IAB inter-topology data migration scenario, for example, a first IAB node transitions from a connection with a first donor node to a connection with a second donor node. The first donor node can notify the second donor node of the slice corresponding to the first backhaul RLC channel in its topology, and the second donor node, based on the slice corresponding to the first backhaul RLC channel, sets the slice corresponding to the second backhaul RLC channel in the topology of the second donor node and feeds back the slice corresponding to the second backhaul RLC channel to the first donor node. In this case, the first information transmitted by the first donor node to the first IAB node can further indicate the slice corresponding to the second backhaul RLC channel. It will be understood that the slice corresponding to the second backhaul RLC channel may be the same as or different from the slice corresponding to the first backhaul RLC channel. This is not limited to this embodiment of the present application. It will be understood that, after receiving the first information, the first IAB node establishes the second backhaul RLC channel based on the slice indicated by the first information and performs IAB inter-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation can be implemented between the transmitting and receiving ends corresponding to the second backhaul RLC channel, thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to a high-priority service can use specific slice resources to ensure preferred and reliable communication of the high-priority service.

[0065]

[0065] Optionally, the first information includes one or more slice identifiers corresponding to the second backhaul RLC channel.

[0066]

[0066] Optionally, the first information further indicates that the resources used by the second backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the second backhaul RLC channel.

[0067]

[0067] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0068]

[0068] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the second backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0069]

[0069] In possible implementations, the slice corresponding to the second backhaul RLC channel differs from the slice corresponding to the first backhaul RLC channel in that the first information further indicates the mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.

[0070]

[0070] In possible implementations, the mapping relationships include the following:

[0071]

[0071] The slice identifier corresponding to the first backhaul RLC channel is the same as or different from the slice identifier corresponding to the second backhaul RLC channel.

[0072]

[0072] In possible implementations, the mapping relationships include the following:

[0073]

[0073] The slice / service type SST corresponding to the first backhaul RLC channel is the same as the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is different from the slice distinguisher SD corresponding to the second backhaul RLC channel; or

[0074]

[0074] The slice / service type SST corresponding to the first backhaul RLC channel is different from the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is the same as the slice distinguisher SD corresponding to the second backhaul RLC channel.

[0075]

[0075] In possible implementations, the method further includes the following:

[0076]

[0076] The first IAB node transmits the fifth piece of information to the first donor node, and the fifth piece of information indicates slice resource congestion.

[0077]

[0077] This embodiment of the present application provides a specific possible embodiment of indicating slice resource congestion. Specifically, a first IAB node transmits a fifth piece of information to a first donor node, the fifth piece of information indicating slice resource congestion. After receiving the fifth piece of information, the first donor node determines that the current slice resource is congested and performs traffic control for different slice services to ensure the quality of service of the slice services.

[0078]

[0078] In a possible implementation, the nodes in the first backhaul adaptive protocol BAP topology support the slice indicated by the first information, the first BAP topology is managed by the first donor node, and the first IAB node belongs to the first BAP topology.

[0079]

[0079] This implementation of the present application provides a specific implementation form in which BAP route configuration is possible. Specifically, the nodes in a first BAP topology support slices indicated by first information, the first BAP topology includes a first donor node and a first IAB node, and the first BAP topology is managed by the first donor node. When configuring a BAP route, it will be understood that the first donor node must take into account the slice types supported by each hop of the IAB node to ensure that each IAB node on the BAP path supports the target slice.

[0080]

[0080] In possible implementations, the method further includes the following:

[0081]

[0081] The first IAB node transmits the first data packet to the second IAB node based on the slice identifier corresponding to the first data packet, and the second IAB node is an IAB node that supports the slice corresponding to the first data packet.

[0082]

[0082] This implementation of the present application provides a specific implementation that enables BAP rerouting. Specifically, if the next-hop backhaul link is unavailable, the first IAB node can select a next-hop IAB node that supports the target slice for rerouting based on the slice identifier corresponding to the first data packet, and send the first data packet to the next-hop IAB node (the second IAB node), thereby ensuring that each IAB node in the BAP path supports the target slice.

[0083]

[0083] According to a third aspect, embodiments of the present application provide a communication method. The method may be performed by a communication device. The communication device may be a device, or a chip (system) or circuit used in a device. This is not limited to the present application. The method includes the following:

[0084]

[0084] The first donor node generates first information, which indicates that the resources used by the first backhaul radio link control RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, the at least one backhaul RLC channel includes the first backhaul RLC channel, the first backhaul RLC channel is a backhaul RLC channel corresponding to the first integrated access and backhaul IAB node.

[0085]

[0085] The first donor node transmits the first information to the first IAB node.

[0086]

[0086] This implementation of the present application provides a communication method. A first donor node generates first information and transmits the first information to a first IAB node. The first information indicates that a resource used by the first backhaul RLC channel is a reserved resource, where reserved resource is an allocation of resources reserved on the air interface for the first backhaul RLC channel, and the allocation of reserved resource may include, but is not limited to, a preferred resource (a resource used preferentially by the first backhaul RLC channel), a dedicated resource (a resource used only by the first backhaul RLC channel), a shared resource (a resource shared and used by multiple backhaul RLC channels such as the first backhaul RLC channel), or similar. This is not limited to this embodiment of the present application. In this embodiment of the present application, the first information indicates that the first backhaul RLC channel uses reserved resources, thereby implementing slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel, and thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to high-priority services can use specific slice resources to ensure preferred and reliable communication of high-priority services.

[0087]

[0087] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0088]

[0088] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the first backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0089]

[0089] According to a fourth aspect, embodiments of the present application provide a communication method. The method may be performed by a communication device. The communication device may be a device, or a chip (system) or circuit used in a device. This is not limited to the present application. The method includes the following:

[0090]

[0090] The first integrated access and backhaul IAB node receives first information from the first donor node, the first information indicating that the resources used by the first backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, the at least one backhaul RLC channel includes the first backhaul RLC channel, the first backhaul RLC channel is the backhaul RLC channel corresponding to the first IAB node.

[0091]

[0091] The first IAB node establishes a first backhaul RLC channel based on the first information.

[0092]

[0092] This implementation of the present application provides a communication method. A first IAB node receives first information from a first donor node and establishes a first backhaul RLC channel based on the first information. The first information indicates that the resources used by the first backhaul RLC channel are reserved resources, where reserved resources are allocations of resources reserved on the air interface for the first backhaul RLC channel, and the allocation of reserved resources may include, but are not limited to, preferred resources (resources used preferentially by the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared and used by multiple backhaul RLC channels such as the first backhaul RLC channel), or similar. This is not limited to this embodiment of the present application. In this embodiment of the present application, the first information indicates that the first backhaul RLC channel uses reserved resources, thereby implementing slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel, and thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to high-priority services can use specific slice resources to ensure preferred and reliable communication of high-priority services.

[0093]

[0093] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0094]

[0094] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the first backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0095]

[0095] According to a fifth aspect, embodiments of the present application provide a communication method. The method may be performed by a communication device. The communication device may be a device, or a chip (system) or circuit used in a device. This is not limited to the present application. The method includes the following:

[0096]

[0096] The first donor node generates first information, which includes a slice identifier corresponding to first migration data, and the first migration data includes data transmitted after the first IAB node transitions from a connection with the first donor node to a connection with the second donor node, the second donor node being different from the first donor node.

[0097]

[0097] The first donor node transmits the first information to the first IAB node.

[0098]

[0098] This implementation of the present application provides a communication method. A first donor node generates first information and transmits the first information to a first IAB node. The first information includes slice identifiers corresponding to first migration data. In an IAB inter-topology data migration scenario, it would be understood, for example, that a first IAB node transitions from a connection with a first donor node to a connection with a second donor node. Correspondingly, after the transition of the first IAB node between connections with donor nodes, first migration data is transmitted, and the first information further includes one or more slice identifiers corresponding to the first migration data, specifically, one or more slice identifiers corresponding to the first migration data. The first information is a slice identifier corresponding to the first migration data, and by using the slice identifier contained in the first information, it is possible to specify the slice corresponding to the backhaul RLC channel used by the first migration data, thereby implementing slice resource isolation between the transmitting and receiving ends corresponding to the backhaul RLC channel used by the first migration data, implementing end-to-end slice resource isolation in the IAB architecture, and ensuring preferred and reliable communication for high-priority services.

[0099]

[0099] In a possible implementation, the first information further indicates a slice corresponding to a second backhaul RLC channel, the second backhaul RLC channel being the backhaul RLC channel corresponding to a second donor node.

[0100]

[0100] This implementation of the present application provides a specific possible implementation of the first information. Specifically, in an IAB inter-topology data migration scenario, for example, a first IAB node transitions from a connection with a first donor node to a connection with a second donor node. The first donor node can notify the second donor node of the slice corresponding to the first backhaul RLC channel in its topology, and the second donor node, based on the slice corresponding to the first backhaul RLC channel, sets the slice corresponding to the second backhaul RLC channel in the topology of the second donor node and feeds back the slice corresponding to the second backhaul RLC channel to the first donor node. In this case, the first information transmitted by the first donor node to the first IAB node can further indicate the slice corresponding to the second backhaul RLC channel. It will be understood that the slice corresponding to the second backhaul RLC channel may be the same as or different from the slice corresponding to the first backhaul RLC channel. This is not limited to this embodiment of the present application. It will be understood that, after receiving the first information, the first IAB node establishes the second backhaul RLC channel based on the slice indicated by the first information and performs IAB inter-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation can be implemented between the transmitting and receiving ends corresponding to the second backhaul RLC channel, thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to a high-priority service can use specific slice resources to ensure preferred and reliable communication of the high-priority service.

[0101]

[0101] Optionally, the first information includes one or more slice identifiers corresponding to the second backhaul RLC channel.

[0102]

[0102] Optionally, the first information further indicates that the resources used by the second backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the second backhaul RLC channel.

[0103]

[0103] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0104]

[0104] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the second backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0105]

[0105] According to the sixth aspect, embodiments of the present application provide a communication method. The method may be performed by a communication device. The communication device may be a device, or a chip (system) or circuit used in a device. This is not limited to the present application. The method includes the following:

[0106]

[0106] The first integrated access and backhaul IAB node receives first information from the first donor node, the first information includes a slice identifier corresponding to first migration data, the first migration data includes data transmitted after the first IAB node transitions from a connection with the first donor node to a connection with the second donor node, the second donor node being different from the first donor node.

[0107]

[0107] The first IAB node transmits the first migration data based on the first information.

[0108]

[0108] This implementation of the present application provides a communication method. A first IAB node receives first information from a first donor node and transmits first migration data based on the first information. The first information includes slice identifiers corresponding to the first migration data. In an IAB inter-topology data migration scenario, it would be understood, for example, that a first IAB node transitions from a connection with a first donor node to a connection with a second donor node. Correspondingly, after the transition of the first IAB node between connections with donor nodes, first migration data is transmitted, and the first information further includes slice identifiers corresponding to the first migration data, specifically, one or more slice identifiers corresponding to the first migration data. The first information is a slice identifier corresponding to the first migration data, and by using the slice identifier contained in the first information, it is possible to specify the slice corresponding to the backhaul RLC channel used by the first migration data, thereby implementing slice resource isolation between the transmitting and receiving ends corresponding to the backhaul RLC channel used by the first migration data, implementing end-to-end slice resource isolation in the IAB architecture, and ensuring preferred and reliable communication for high-priority services.

[0109]

[0109] In a possible implementation, the first information further indicates a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is the backhaul RLC channel corresponding to a second donor node.

[0110]

[0110] This implementation of the present application provides a specific possible implementation of the first information. Specifically, in an IAB inter-topology data migration scenario, for example, a first IAB node transitions from a connection with a first donor node to a connection with a second donor node. The first donor node can notify the second donor node of the slice corresponding to the first backhaul RLC channel in its topology, and the second donor node, based on the slice corresponding to the first backhaul RLC channel, sets the slice corresponding to the second backhaul RLC channel in the topology of the second donor node and feeds back the slice corresponding to the second backhaul RLC channel to the first donor node. In this case, the first information transmitted by the first donor node to the first IAB node can further indicate the slice corresponding to the second backhaul RLC channel. It will be understood that the slice corresponding to the second backhaul RLC channel may be the same as or different from the slice corresponding to the first backhaul RLC channel. This is not limited to this embodiment of the present application. It will be understood that, after receiving the first information, the first IAB node establishes the second backhaul RLC channel based on the slice indicated by the first information and performs IAB inter-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation can be implemented between the transmitting and receiving ends corresponding to the second backhaul RLC channel, thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to a high-priority service can use specific slice resources to ensure preferred and reliable communication of the high-priority service.

[0111]

[0111] Optionally, the first information includes one or more slice identifiers corresponding to the second backhaul RLC channel.

[0112]

[0112] Optionally, the first information further indicates that the resources used by the second backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the second backhaul RLC channel.

[0113]

[0113] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0114]

[0114] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the second backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0115]

[0115] According to the seventh aspect, an embodiment of the present application provides a communication device. The device includes a module or unit configured to perform a method according to any implementation of the first aspect.

[0116]

[0116] In a possible design, the device: A processing unit configured to generate first information, wherein the first information indicates a slice corresponding to a first backhaul radio link control RLC channel, and the first backhaul RLC channel is a backhaul RLC channel corresponding to a first integrated access and backhaul IAB node, and the processing unit It includes a communication unit configured to transmit first information to a first IAB node.

[0117]

[0117] For the method performed by the processing unit and the communication unit, please refer to the method corresponding to the first embodiment. Details will not be explained again here.

[0118]

[0118] In implementation, the communication device is a communication device. When the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0119]

[0119] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit or the like in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit or the like.

[0120]

[0120] For technical effects resulting from the seventh aspect and any possible implementation of the seventh aspect, please refer to the description of the first aspect and the technical effects corresponding to the corresponding implementation of the first aspect.

[0121]

[0121] According to the eighth aspect, an embodiment of the present application provides a communication device. The device includes a module or unit configured to perform a method according to any implementation of the second aspect.

[0122]

[0122] In a possible design, the device: A communication unit configured to receive first information from a first donor node, wherein the first information indicates a slice corresponding to a first backhaul radio link control RLC channel, and the first backhaul RLC channel is a backhaul RLC channel corresponding to a communication device, and a processing unit, The system includes a processing unit configured to establish a first backhaul RLC channel based on first information.

[0123]

[0123] For the method performed by the processing unit and the communication unit, please refer to the method corresponding to the second embodiment. Details will not be explained again here.

[0124]

[0124] In implementation, the communication device is a communication device. When the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0125]

[0125] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit or the like in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit or the like.

[0126]

[0126] For the technical effects brought about by the eighth aspect and any possible implementation of the eighth aspect, please refer to the description of the technical effects corresponding to the second aspect and the corresponding implementation of the second aspect.

[0127]

[0127] According to the ninth aspect, an embodiment of the present application provides a communication device. The device includes a module or unit configured to perform a method according to any implementation of the third aspect.

[0128]

[0128] In a possible design, the device: A processing unit configured to generate first information, wherein the first information indicates that a resource used by a first backhaul radio link control RLC channel is a reserved resource, the reserved resource includes resources reserved for at least one backhaul RLC channel, the at least one backhaul RLC channel includes a first backhaul RLC channel, and the first backhaul RLC channel is a backhaul RLC channel corresponding to a first integrated access and backhaul IAB node, and the processing unit It includes a communication unit configured to transmit first information to a first IAB node.

[0129]

[0129] For the method performed by the processing unit and the communication unit, please refer to the method corresponding to the third embodiment. Details will not be explained again here.

[0130]

[0130] In implementation, the communication device is a communication device. When the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0131]

[0131] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit or the like in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit or the like.

[0132]

[0132] For the technical effects brought about by the ninth aspect and any possible implementation of the ninth aspect, please refer to the description of the technical effects corresponding to the third aspect and the corresponding implementation of the third aspect.

[0133]

[0133] According to the tenth aspect, an embodiment of the present application provides a communication device. The device includes a module or unit configured to perform a method according to any implementation of the fourth aspect.

[0134]

[0134] In a possible design, the device: A communication unit configured to receive first information from a first donor node, wherein the first information indicates that a resource used by a first backhaul RLC channel is a reserved resource, the reserved resource includes resources reserved for at least one backhaul RLC channel, the at least one backhaul RLC channel includes a first backhaul RLC channel, and the first backhaul RLC channel is a backhaul RLC channel corresponding to a first IAB node, and the communication unit The system includes a processing unit configured to establish a first backhaul RLC channel based on first information.

[0135]

[0135] For the method performed by the processing unit and the communication unit, please refer to the method corresponding to the fourth aspect. Details will not be explained again here.

[0136]

[0136] In implementation, the communication device is a communication device. When the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0137]

[0137] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit or the like in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit or the like.

[0138]

[0138] For the technical effects brought about by the tenth aspect and any possible implementation of the tenth aspect, please refer to the description of the technical effects corresponding to the fourth aspect and the corresponding implementation of the fourth aspect.

[0139]

[0139] According to the eleventh aspect, an embodiment of the present application provides a communication device. The device includes a module or unit configured to perform a method according to any implementation of the fifth aspect.

[0140]

[0140] In possible designs, the device: A processing unit configured to generate first information, wherein the first information includes a slice identifier corresponding to first migration data, and the first migration data includes data transmitted after the first IAB node transitions from a connection with a first donor node to a connection with a second donor node, and the second donor node is different from the first donor node; It includes a communication unit configured to transmit first information to a first IAB node.

[0141]

[0141] For the method performed by the processing unit and the communication unit, please refer to the method corresponding to the fifth aspect. Details will not be explained again here.

[0142]

[0142] In implementation, the communication device is a communication device. When the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0143]

[0143] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit or similar in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit or similar.

[0144]

[0144] For technical effects resulting from the eleventh aspect and any possible implementation of the eleventh aspect, please refer to the description of the fifth aspect and the technical effects corresponding to the corresponding implementation of the fifth aspect.

[0145]

[0145] According to the twelfth aspect, an embodiment of the present application provides a communication device. The device includes a module or unit configured to perform a method according to any implementation of the sixth aspect.

[0146]

[0146] In a possible design, the device: A communication unit configured to receive first information from a first donor node, wherein the first information includes a slice identifier corresponding to first migration data, and the first migration data includes data transmitted after the communication device transitions from a connection with a first donor node to a connection with a second donor node, and the second donor node is different from the first donor node; It includes a processing unit configured to transmit first migration data based on first information.

[0147]

[0147] For the method performed by the processing unit and the communication unit, please refer to the method corresponding to the sixth aspect. Details will not be explained again here.

[0148]

[0148] In implementation, the communication device is a communication device. When the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0149]

[0149] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit or the like in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit or the like.

[0150]

[0150] For the technical effects brought about by the twelfth aspect and any possible implementation of the twelfth aspect, please refer to the description of the sixth aspect and the technical effects corresponding to the corresponding implementation of the sixth aspect.

[0151]

[0151] According to the thirteenth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor. The processor is coupled to memory and can be configured to execute instructions in memory and to perform methods according to the first to sixth aspects and possible implementations thereof. Optionally, the communication device further includes memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0152]

[0152] According to the fourteenth aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and a communication interface. The communication interface is configured to receive or transmit information. The logic circuit is configured to receive or transmit information via the communication interface to perform the methods of the first to sixth aspects and possible implementations thereof.

[0153]

[0153] According to the fifteenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program (which may be referred to as code or instructions). When the computer program is executed on a computer, a method according to any one of the first through sixth aspects and possible implementations thereof is performed.

[0154]

[0154] According to the sixteenth aspect, an embodiment of the present application provides a computer program product. The computer program product includes a computer program (which may be referred to as code or instructions). When the computer program is executed, the computer becomes capable of performing any one of the methods of the first through sixth aspects and possible implementations thereof.

[0155]

[0155] According to the 17th aspect, an embodiment of the present application provides a chip. The chip includes a processor. The processor is configured to execute instructions. When the processor executes instructions, the chip becomes capable of performing a method according to any one of the first through sixth aspects and possible implementations of the first through sixth aspects. Optionally, the chip further includes a communication interface, which is configured to receive or transmit signals.

[0156]

[0156] According to the 18th aspect, an embodiment of the present application provides a communication system. The communication system includes at least one communication device according to the 7th to 12th aspects, a communication device according to the 13th aspect, a communication device according to the 14th aspect, or a chip according to the 17th aspect.

[0157]

[0157] According to the 19th aspect, an embodiment of the present application provides a communication system. The communication system includes a first donor node and a first IAB node. The first donor node is configured to perform a method according to the first, third, or fifth aspect and any one of the possible implementations of the first, third, or fifth aspect. The first IAB node is configured to perform a method according to the second, fourth, or sixth aspect and any one of the possible implementations of the second, fourth, or sixth aspect.

[0158]

[0158] Furthermore, in a process of performing a method according to any one of the first to sixth embodiments and possible implementations thereof, processes relating to transmitting and / or receiving information in the method may be understood as processes that output information by the processor and / or processes that receive input information by the processor. When outputting information, the processor may output information to a transceiver (or communication interface or transmitting module), and as a result the transceiver transmits the information. After the information is output by the processor, it may be necessary for other processing to be performed on the information before it arrives at the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface or transmitting module) receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, it may be necessary for other processing to be performed on the information before it is input to the processor.

[0159]

[0159] Based on the principle described above, for example, transmitting information in the method described above may be understood as the processor outputting information. In another example, receiving information may be understood as the processor receiving input information.

[0160]

[0160] Optionally, operations such as transmission, sending, and receiving associated with the processor may be more generally understood as operations such as output, receiving, and input of the processor, unless otherwise specified, or unless the operation is inconsistent with the actual function or internal logic of the operation in the relevant description.

[0161]

[0161] Optionally, in the process of performing the method according to any one of the first to sixth embodiments and possible implementations thereof, the processor may be a processor specifically configured to perform the method, or a processor that performs the method by executing computer instructions in memory, such as a general-purpose processor. The memory may be non-transitory memory, such as read-only memory (ROM). The memory and processor may be integrated on the same chip, or they may be located separately on different chips. The type of memory, and the arrangement of the memory and processor, are not limited to this embodiment of the present application.

[0162]

[0162] In possible implementations, at least one memory is located outside the device.

[0163]

[0163] In another possible implementation, at least one memory is located within the device.

[0164]

[0164] In yet another possible implementation, at least one portion of the memory is located inside the device, and the other portion of the memory is located outside the device.

[0165]

[0165] In this application, the processor and memory may, alternatively, be integrated into a single device. In other words, the processor and memory may, alternatively, be integrated together.

[0166]

[0166] In the embodiments of the present application, the first information indicates a slice corresponding to a first backhaul RLC channel corresponding to a first IAB node, thereby enabling slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel, thereby realizing end-to-end slice resource isolation in the IAB architecture and ensuring preferred and reliable communication for high-priority services. [Brief explanation of the drawing]

[0167]

[0167] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the accompanying drawings used in the embodiments of the present application are briefly described below. It is obvious that the accompanying drawings described below illustrate only some embodiments of the present application, and that a person skilled in the art may derive other drawings from these accompanying drawings without any creative effort. [Figure 1]

[0168] Figure 1 is a structural diagram of the IAB system according to the embodiment of this application. [Figure 2]

[0169] Figure 2 is a structural diagram of an IAB node according to the embodiment of this application. [Figure 3]

[0170] Figure 3 is a structural diagram of the IAB network according to the embodiment of this application. [Figure 4]

[0171] Figure 4 shows an example of a diagram of the IAB network architecture according to the embodiment of this application. [Figure 5]

[0172] Figure 5 shows an example of a BAP topology for an IAB network according to the embodiment of this application. [Figure 6]

[0173] Figure 6 is a schematic flowchart of the transport migration management process according to the embodiment of the present application. [Figure 7A]

[0174] Figure 7A is a diagram of the mapping according to the embodiment of the present application. [Figure 7B]

[0175] Figure 7B is a diagram of the mapping according to the embodiment of the present application. [Figure 8]

[0176] Figure 8 is a schematic flowchart of the communication method according to the embodiment of the present application. [Figure 9]

[0177] Figure 9 is a schematic flowchart of the communication method according to the embodiment of the present application. [Figure 10]

[0178] Figure 10 is a schematic flowchart of the communication method according to the embodiment of the present application. [Figure 11A]

[0179] Figure 11A is a diagram of an information element according to an embodiment of the present application. [Figure 11B]

[0180] Figure 11B is a diagram of an information element according to an embodiment of the present application. [Figure 12]

[0181] Figure 12 is a schematic flowchart of the communication method according to the embodiment of the present application. [Figure 13]

[0182] Figure 13 is a structural diagram of a communication device according to an embodiment of the present application. [Figure 14]

[0183] Figure 14 is a structural diagram of a communication device according to an embodiment of the present application. [Figure 15]

[0184] Figure 15 is a structural diagram of a communication device according to an embodiment of the present application. [Figure 16]

[0185] Figure 16 is a structural diagram of a chip according to an embodiment of the present application. [Modes for carrying out the invention]

[0168]

[0186] To further clarify the purpose, technical solution, and advantages of this application, embodiments of this application will be described below with reference to the accompanying drawings of embodiments of this application.

[0169]

[0187] The terms “first,” “second,” and similar terms in the specification, claims, and accompanying drawings of this application are used to distinguish different subjects and are not used to describe a particular order. Furthermore, the terms “includes,” “has,” and any other variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, device, or similar comprising a series of steps or units is not limited to the listed steps or units, but optionally includes further steps, units, or similar not listed, or optionally includes further steps or units of another specific step or unit of the process, method, product, device, or similar.

[0170]

[0188] The “embodiments” as used in this specification indicate that certain characteristics, structures, or features described with reference to these embodiments may be included in at least one embodiment of this application. The terms appearing in various parts of this specification do not necessarily mean the same embodiment, nor do they imply mutually exclusive, independent, or alternative embodiments. Unless otherwise specified or unless a logical contradiction arises, the terminology and / or descriptions in the embodiments of this application are consistent, may be mutually referenced, and technical features in different embodiments may be combined on the basis of their internal logical relationships to form new embodiments, which will be understood both explicitly and implicitly by those skilled in the art.

[0171]

[0189] In this application, it should be understood that "at least one (item)" means one or more, "multiple" means two or more, "at least two (items)" means two, three or more, and "and / or" is used to describe the relationship of association between the relevant subjects, indicating that three relationships may exist. For example, "A and / or B" could indicate one of the following three cases: only A exists, only B exists, or both A and B exist, where A and B may be singular or plural. The letter " / " generally indicates an "or" relationship between the relevant subjects. "At least one of the following items (pieces)" or similar expressions means any combination of these items, including any combination of singular items (pieces) or plural items (plural pieces). For example, at least one of a, b, or c could indicate a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

[0172]

[0190] It should be noted in this application that “instruction” may include direct, indirect, explicit, and implicit instructions. When instructional information is described as indicating A, it can be understood as the instructional information conveying A, directly doing A, or indirectly indicating A.

[0173]

[0191] In this application, the information indicated by the indicating information is referred to as the indicated information (or indicated information) (to-be-indicated). In a particular implementation process, there are many ways of indicating the indicated information. For example, the method may be a method that directly indicates the indicated information, such as the indicated information itself or an index of the indicated information, or a method that indirectly indicates the indicated information by indicating other information. A relationship of association exists between the other information and the indicated information. Alternatively, only a portion of the indicated information may be indicated, and the other parts of the information to be indicated may be known or pre-agreed. For example, certain information may, alternatively, be indicated by using a pre-agreed (e.g., specified in a protocol) arrangement sequence of information in order to reduce the indicating overhead to some extent. The indicated information may be transmitted as a whole, or it may be divided into multiple sub-informations to be transmitted separately. Furthermore, the transmission cycle and / or transmission opportunities of these sub-informations may be the same or different. Specific transmission methods are not limited in this application. The transmission cycle and / or transmission opportunities for this sub-information may be predefined, for example, according to a protocol, or may be set by the transmitting end device sending configuration information to the receiving end device.

[0174]

[0192] It should be noted in this application that "transmitting" may be understood as "output," and "receiving" may be understood as "input." In the case of "transmitting information to A," "to A" only indicates the direction of information transmission, where A is the destination, and "transmitting information to A" is not necessarily performed directly via an air interface. "Transmitting information to A" includes directly transmitting information to A and indirectly transmitting information to A via a transmitter. Therefore, "transmitting information to A" may be understood as "outputting information to A." Similarly, "receiving information from A" indicates that A is the source of the information and includes directly receiving information from A and indirectly receiving information from A via a receiver. Therefore, "receiving information from A" may be understood as "inputting information from A."

[0175]

[0193] Before describing the present application, we will first briefly explain and state some of the terms used in the embodiments of this application in order to facilitate understanding for those skilled in the art.

[0176]

[0194] (1) The terminal device is a device that provides voice and / or data connectivity to the user. In the embodiments of this application, the terminal device may be referred to as user equipment (UE), terminal device, terminal, mobile station (MS), mobile terminal (MT), or similar. For example, the terminal device may include a portable device with wireless connectivity or a communication device connected to a wireless modem. The terminal device can communicate with the core network via a radio access network (RAN) and exchange voice and / or data with the RAN.

[0177]

[0195] Some examples of terminal devices include mobile stations (MS), subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistants (PDAs), computers, tablet computers, wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, wearable devices, and in-vehicle terminal devices. Terminal devices may further include devices with limitations, such as low-power consumption devices, devices with limited memory capacity, or devices with limited processing power. Terminal devices may further include information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning systems (GPS), or laser scanners.

[0178]

[0196] The functionality of the terminal device may be implemented by hardware components within the terminal device, which may be a processor and / or programmable chip within the terminal device. Optionally, the chip may be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be any one of a complex programmable logic device (CPLD), a field programmable gate array (FPGA), a generic array logic (GAL), and a system on a chip (SoC), or any combination thereof.

[0179]

[0197] (2) A donor base station (donor gNodeB), sometimes called a donor node, can access the core network through a donor node. In other words, a donor base station is a device in a communication system that connects terminal devices to the core network. Donor base stations are typically connected to the core network via a wired link (e.g., fiber optic cable). A donor base station may be responsible for receiving data from the core network and forwarding it to a wireless backhaul device (e.g., an IAB node), or receiving data from a wireless backhaul device and forwarding it to the core network. Typically, donor base stations can be connected to the network via a wired method.

[0180]

[0198] For example, a donor base station may include a radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), baseband unit (BBU), and similar components; or it may include an evolved base station (Node B, eNB, or e-Node B, evolved Node B) in an LTE-Advanced (LTE-A) system; or it may include a next-generation Node B (next-generation Node B, gNB) in a 5th generation (5G) mobile communication technology / new radio (NR) system. In another example, a donor base station may include a central unit (CU) (abbreviated as donor CU or gNB-CU in this application) and a distributed unit (DU) (abbreviated as donor DU or gNB-DU in this application). The gNB-CU and gNB-DU are connected via an F1 interface. The F1 interface may further include a control plane interface (F1-C) and a user plane interface (F1-U). The donor CU is connected to the core network via a next-generation (NG) interface. Alternatively, the gNB-CU or donor CU may exist in a form in which the user plane (UP) (abbreviated as CU-UP in this application) and the control plane (CP) (abbreviated as CU-CP in this application) are separated. In other words, the gNB-CU or donor CU includes CU-CP and CU-UP. One gNB-CU may contain one gNB-CU-CP and at least one gNB-CU-UP. Alternatively, one donor CU may contain one donor CU-CP and at least one donor CU-UP.

[0181]

[0199] The functions of the donor base station may be implemented by hardware components within the donor base station, such as a processor and / or programmable chip within the donor base station. For example, the chip may be implemented by an ASIC or a PLD. The PLD may be any one of CPLD, FPGA, GAL, and SoC, or any combination thereof.

[0182]

[0200] This application provides a communication method applicable to the field of communication technology, for example, communication in IAB networks. To more clearly explain the solution of this application, some knowledge related to IAB will be explained below.

[0183]

[0201] In an IAB network, an IAB node can establish a radio backhaul link to one or more higher-level nodes and access the core network through those higher-level nodes. Higher-level nodes can control relay nodes (e.g., by performing data scheduling, timing modulation, and power control) using various types of signaling. Relay nodes can also establish access links to one or more lower-level nodes and provide access services to those lower-level nodes. The higher-level node of a relay node may be a base station or another relay node. The lower-level node of a relay node may be a terminal or another relay node. In some cases, the higher-level node of an IAB node may be called the upstream or parent node, and the lower-level node may be called the downstream or child node.

[0184]

[0202] Figure 1 is a structural diagram of the IAB system according to the embodiment of this application.

[0185]

[0203] As shown in Figure 1, the IAB node provides wireless access and wireless backhaul for access services for the UE. The IAB donor node provides wireless backhaul functionality for the IAB node and provides an interface between the UE and the core network. The IAB node is connected to the IAB donor node via a wireless backhaul link, and as a result, the UE served by the IAB node is connected to the core network.

[0186]

[0204] Figure 2 is a structural diagram of an IAB node according to the embodiment of this application.

[0187]

[0205] As shown in Figure 2, an IAB node in NR can be divided into two parts: MT and DU. The MT can also be understood as a component similar to a UE but located within the IAB node, and is called the function that camps on to the IAB node. Since the MT is similar to the function of a common UE, it will be understood that the MT is used for communication between the IAB node and higher-level nodes. The DU relates to the CU function of a network device, and is used for communication between the IAB node and lower-level nodes. It should be understood that the higher-level node may be a base station or another IAB node, and the lower-level node may be a UE or another IAB node.

[0188]

[0206] The communication methods provided in the embodiments of this application may be applicable to various communication systems including relay nodes, such as NR systems, LTE systems, LTE-A systems, worldwide interoperability for microwave access (WiMAX) systems, or wireless local area networks (WLANs). In LTE, relay nodes are generally referred to as RNs. In NR, relay nodes are generally referred to as IAB nodes. In some embodiments, relay nodes may also be referred to as relay devices or relay transmission reception points (rTRPs), and higher-level nodes of relay nodes may be network devices (including network device DUs, network device CUs, or similar).

[0189]

[0207] Figure 3 is a structural diagram of the IAB network according to the embodiment of this application.

[0190]

[0208] As shown in Figure 3, an IAB network includes multiple UEs and multiple IAB nodes. Figure 3 uses an example that includes two UEs and five IAB nodes. The two UEs are UE 1 and UE 2, and the five IAB nodes are IAB node 1 through IAB node 5. In Figure 3, it should be understood that thick lines represent access links and thin lines represent backhaul links. UE 2 can be connected to the donor base station via IAB node 5, IAB node 2, and IAB node 1. Alternatively, UE 2 can be connected to the donor base station via IAB node 4, IAB node 2, and IAB node 1. Alternatively, UE 2 can be connected to the donor base station via IAB node 4, IAB node 3, and IAB node 1. UE 1 can be connected to the donor base station via IAB node 4, IAB node 3, and IAB node 1. UE 1 can be connected to the donor base station via IAB node 4, IAB node 2, and IAB node 1.

[0191]

[0209] It should be noted that the communication system shown in Figure 3 is merely an example and does not constitute a limitation on the application scenarios applicable to the embodiments of this application. It should be understood that the IAB node is used in the embodiments of this application for illustrative purposes only. This does not imply that the solutions in the embodiments of this application are used only in NR scenarios. In the embodiments of this application, the IAB node can generally be any node or device with relay functionality, and the usages of IAB node and relay node in the embodiments of this application should be understood as having the same meaning.

[0192]

[0210] In an IAB network, IAB nodes are connected to the core network via IAB donor nodes. For example, in a standalone (SA) 5G architecture, IAB nodes are connected to the 5G core network (5GC / 5GCN) via IAB donor nodes. In another example, in a dual connectivity (DC) or multi-connectivity (MC) 5G architecture (e.g., a non-standalone (NSA) scenario), on the primary path, IAB nodes may be connected to the evolved packet core (EPC) via evolved NodeB (eNB), or to the 5G core network via IAB donors.

[0193]

[0211] In an IAB network, one or more IAB nodes may be included in the transmission path between a UE and an IAB donor. Each IAB node must maintain a wireless backhaul link to its parent node and wireless links to its child nodes. If a child node of an IAB node is a UE, a wireless access link exists between the IAB node and its child node (i.e., the UE). If a child node of an IAB node is another IAB node, a wireless backhaul link exists between the IAB node and its child node (i.e., the other IAB node). See, for example, Figure 3. “UE1 → IAB Node 4 → IAB Node 3 → IAB Node 1 → IAB Donor” In this path, UE1 accesses IAB node 4 via a wireless access link, IAB node 4 is connected to IAB node 3 via a wireless backhaul link, IAB node 3 is connected to IAB node 1 via a wireless backhaul link, and IAB node 1 is connected to an IAB donor node via a wireless backhaul link.

[0194]

[0212] In the embodiments of this application, the access IAB node is an IAB node accessed by the UE, and the intermediate IAB node is an IAB node that provides wireless backhaul services to the UE or an IAB node. See, for example, Figure 3. “UE1 → IAB node 4 → IAB node 3 → IAB node 1 → IAB donor” In this path, IAB node 4 is an access IAB node, and IAB nodes 3 and 1 are intermediate IAB nodes. It should be noted that an IAB node is an access IAB node for a UE when the UE accesses another IAB node; and an IAB node is an intermediate IAB node for a UE when the UE accesses yet another IAB node. Therefore, whether an IAB node is specifically an access IAB node or an intermediate IAB node is not fixed and can be determined based on the specific application scenario.

[0195]

[0213] It should be noted that the communication system shown in Figure 3 is merely an example and does not constitute a limitation on the application scenarios applicable to the embodiments of this application. It should be understood that the IAB node is used in the embodiments of this application for illustrative purposes only. This does not imply that the solution in the embodiments of this application is only applicable in new radio (NR) scenarios.

[0196]

[0214] The communication method provided in this application is primarily applicable to IAB networks, which include standalone (SA) IAB networks and non-standalone (NSA) IAB networks. An IAB node includes an MT portion and a DU portion. An IAB donor can be further divided into a DU portion and a CU portion, and the CU can be further divided into a CU-CP portion and a CU-UP portion.

[0197]

[0215] Figure 4 shows an example of a diagram of the IAB network architecture according to the embodiment of this application.

[0198]

[0216] As shown in Figure 4, an example is illustrated in which an IAB node is connected to an IAB donor via a wireless backhaul link. Figure 4 uses an example that includes one UE, two IAB nodes, and two IAB donors. The two IAB nodes are IAB Node 1 and IAB Node 2, and the two IAB nodes each include an MT portion and a DU portion. The two IAB donors are IAB Donor 1 and IAB Donor 2. Each IAB donor can be further divided into a DU portion and a CU portion, and the CU can be further divided into a CU-CP portion and a CU-UP portion. In Figure 4, communication is performed via a wireless backhaul (BH) link between the MT of IAB node 2 and the DU of IAB node 1, between the MT of IAB node 1 and the DU of IAB donor 1, and between the MT of IAB node 1 and the DU of IAB donor 2; a Uu interface is established between the UE and the IAB2-DU; an F1-C interface is established between the IAB donor DU and the IAB donor CU-CP; and an F1-U interface is established between the IAB donor DU and the IAB donor CU-UP; the DU of IAB donor 2 is connected to the CU of IAB donor 1 via an Internet Protocol (IP) network.

[0199]

[0217] An F1 interface exists between the DU of each IAB node and the CU of the IAB donor. The F1 interface may include two parts: a control plane portion and a user plane portion. The user plane portion is maintained between the IAB-DU and the IAB donor CU-UP, and the control plane portion is maintained between the IAB-DU and the IAB donor CU-CP. The F1 interface between the IAB-DU and the IAB donor CU is not shown in Figure 4. Indeed, the F1 interface may also be called the F1* interface. The name of the interface is not limited to the embodiments of this application. Also, for example, in this specification, the interface is referred to as the F1 interface.

[0200]

[0218] The F1 interface can support user plane protocols (F1-U / F1*-U) and control plane protocols (F1-C / F1*-C). The user plane protocol includes one or more of the following protocol layers: the general packet radio service (GPRS) tunneling protocol user plane (GTP-U) layer, the user datagram protocol (UDP) layer, the IP protocol layer, or similar. The control plane protocol includes one or more of the following protocol layers: the F1 application protocol (F1AP) layer, the stream control transport protocol (SCTP) layer, the IP protocol layer, or similar. Interface management, IAB-DU management, UE context-related settings, and similar operations may be performed between the IAB node and the IAB donor via the control plane of the F1 / F1* interface. Functions such as user-plane data transmission and downlink transmission status feedback may be performed between IAB nodes and IAB donors via the user plane of the F1 / F1* interface.

[0201]

[0219] When an IAB node operates in SA mode, it is possible to establish a single connection to one parent node or a dual connection to two parent nodes. The two parent nodes may be controlled by the same IAB donor or by different IAB donors. An F1 interface is established between the DU portion of the IAB node and one IAB donor, which can be connected to the 5G core network, i.e., the dashed portion in Figure 4. The IAB-donor-CU-CP is connected to control plane network elements (e.g., access and mobility management functions) in the 5GC via the NG control plane interface (NG-C), and the IAB-donor-CU-UP is connected to user plane network elements (e.g., user plane functions) in the 5GC via the NG user plane interface (NG-U).

[0202]

[0220] When the IAB node operates in NSA mode, the IAB-donor-CU-UP is connected to the EPC via the S1 user plane interface (S1-U) (for example, connected to the serving gateway (SGW)), there is an LTE-Uu air interface connection between the MeNB and the IAB node's MT, there is an X2-C interface between the MeNB and the IAB-donor-CU-CP, and the MeNB is connected to the EPC via the S1 interface (including the S1 interface user plane and the S1 interface control plane), i.e., the dashed line portion in Figure 4.

[0203]

[0221] In another possible case, the MeNB in ​​Figure 4 may be replaced by a 5G base station gNB. Correspondingly, the LTE-Uu interface in Figure 4 is replaced by an NR-Uu interface. A user-plane interface and / or control-plane interface may be established between the gNB and the 5GC. The gNB and IAB donor provide dual connectivity services to the IAB node. The gNB can function as the primary base station or a secondary base station for the IAB node.

[0204]

[0222] The above is an example of an application scenario for the technical solution in the embodiments of this application. It should be understood that the technical solution in the embodiments of this application is not limited to being applied only to the network architecture shown in Figure 4.

[0205]

[0223] Boundary nodes in an IAB network are sometimes called boundary IAB nodes, or simply boundary nodes. Boundary nodes in an IAB network have the following characteristics: The IAB-donor-CU to which the DU of a boundary node is terminated is different from the IAB-donor-CU to which the DU of at least one parent node of the boundary node is terminated. Assume that an IAB node in an IAB network has two parent nodes, and the DU of the IAB node is terminated at the CU of IAB donor 1, the DU of one of the parent nodes of the IAB node is terminated at the CU of IAB donor 1, and the DU of the other parent node of the IAB node is terminated at the CU of IAB donor 2. In this case, the IAB node is a boundary node (for example, IAB node 2 in Figure 5). For example, in an IAB network, boundary nodes may perform a partial migration process to enhance network robustness and achieve more sophisticated load balancing and topology management. Specifically, the boundary node MT (IAB-MT 2 in Figure 5) is handed over from one parent node (IAB node 1 in Figure 5) to the other parent node (IAB node 3 in Figure 5). The two parent nodes belong to topologies controlled by different donor CUs. Specifically, IAB node 1 in Figure 5 belongs to a topology controlled by donor CU 1 (solid box in Figure 5), and IAB node 3 belongs to a topology controlled by donor CU 2 (dashed box in Figure 5). In the partial migration process, IAB-MT 2 switches from an RRC connection with CU1 to an RRC connection with CU2, but the F1 connection of IAB-DU2 still terminates at CU1 (indicated by a solid arrow in Figure 5) and does not migrate to CU2 along with IAB-MT2. It will be understood that the F1 connection of IAB node 4, a child node of IAB node 2, can also be terminated at CU1 (shown by a dashed line in Figure 5).

[0206]

[0224] For example, if the F1 interface of IAB node 2 is terminated at CU1, IAB donor 1 may be called the F1-terminating IAB-donor of IAB node 2. If an RRC connection exists between CU2 and IAB node 2, but the F1 connection of IAB node 2 is not terminated at CU2, IAB donor 2 may be called the non-F1-terminating IAB-donor of IAB node 2.

[0207]

[0225] After IAB Node 2 is switched from the CU1 topology to the CU 2 topology, the 3rd Generation Partnership Project (3GPP) Release 17 standard (R17) introduces the IAB Transport Migration Management process to migrate IAB Node 2's data traffic from the CU1 topology to the CU2 topology. Specifically, CU1 can execute the IAB Transport Migration Management process using the Xn interface between CU1 and CU2 to transfer IAB Node 2's data traffic to CU2. The IAB Transport Migration Management process is shown in Figure 6. Further details are as follows.

[0208]

[0226] Step S601: CU1 sends an IAB Transport Migration Management request message to CU2. In response, CU2 receives the IAB Transport Migration Management request message.

[0209]

[0227] CU1 is the F1-terminated IAB donor for IAB node 2, and CU2 is the non-F1-terminated IAB donor for IAB node 2. The IAB transport migration management request message is used to request the migration of data traffic from IAB node 2 to CU2.

[0210]

[0228] Step S602: CU2 sends an IAB Transport Migration Management response message to CU1. In response, CU1 receives the IAB Transport Migration Management response message.

[0211]

[0229] The IAB Transport Migration Management Response message is used in response to the IAB Transport Migration Management Request message to migrate data traffic from IAB Node 2 to CU2.

[0212]

[0230] In the "IAB Transport Migration Management" process, the CU (Control Unit) exchanges data traffic quality of service (QoS) information with corresponding integrated access and backhaul (BAP) configuration information to perform data traffic offloading. The R17 standard specifies that the process is initiated by an F1-terminated IAB donor (i.e., CU1 in Figure 5) for a non-F1-terminated IAB donor (i.e., CU2 in Figure 5).

[0213]

[0231] To support the flexible and dense deployment of NR cells, the IAB network supports multi-hop backhaul. The multi-hop network relates to routing capabilities between nodes. In addition, to simplify the IAB external interface and reduce its impact on the 5G network, 3GPP will introduce a new IAB-specific protocol, namely the backhaul adaptation protocol (BAP), which is responsible for data packet routing and bearer mapping functions in the IAB network.

[0214]

[0232] The BAP routing function enables data transmission from the transmitting end to the receiving end via a specified route. A BAP packet header (including the destination BAP address and BAP path ID) is added to the upper layer data at the transmitting end, and this BAP packet header is removed at the receiving end before the data is forwarded to the upper layer.

[0215]

[0233] The BAP (Backhaul Channel Mapping) function enables bearer mapping of data packets in an IAB network to meet the quality of service (QoS) requirements for data packets.

[0216]

[0234] The IAB donor CU assigns a unique L2 address (BAP address) to each IAB node controlled by the IAB donor CU, thereby making each IAB node in the network uniquely identifiable. If multiple paths exist, each BAP address can be associated with multiple path IDs. The source node (IAB donor DU in the downlink DL direction, and access IAB node in the uplink UL direction) adds a BAP packet header at the source node's BAP layer to the data packets transmitted by the source node. The BAP packet header includes the BAP address and the BAP path ID.

[0217]

[0235] Each IAB node is configured with a routing table (configured by the IAB donor CU) for uplink UL and downlink DL, and the routing table includes the next-hop identifier for each BAP route ID. Separate routing tables are maintained for the DL direction and the UL direction. The IAB-DU uses the DL table, and the IAB-MT uses the UL table. The routing table can indicate a specific child node (in the case of DL) or a specific parent node (in the case of UL) to which a data packet needs to be forwarded. When an access IAB node receives a data packet, the data packet is forwarded to the upper layer and processed by the common DU in the same manner as incoming F1-U or F1-C data packets.

[0218]

[0236] In addition to forwarding data packets to child or parent nodes, BAP also performs mapping between ingress and egress BH RLC channels. Since BH RLC channels are used to transmit data packets between IAB nodes (or between IAB-donor-DU and IAB-node), BH RLC channel mapping must meet the quality of service (QoS) requirements for data packets. Similar to RLC channels between DUs and UEs, different BH RLC channels may be configured with different QoS parameters, such as priority and guaranteed bit rate. IAB nodes are configured using mapping relationships and, based on their routing tables, identify the next child / parent node and egress BH RLC channel through which data packets should be forwarded.

[0219]

[0237] The mapping between the UE radio bearer and the BH RLC channel supports 1:1 mapping and N:1 mapping. For details, please refer to Figures 7A and 7B. Figures 7A and 7B are diagrams of mapping according to embodiments of the present application.

[0220]

[0238] As shown in Figure 7A, the mapping between UE radio bearers and BH RLC channels supports 1:1 mapping, where each UE radio bearer is mapped to a separate BH RLC channel. For example, UE1 wireless bearer DRB1 is mapped to a separate BH RLC channel 1. The UE1 radio bearer DRB2 is mapped to a separate BH RLC channel 2. The UE2 wireless bearer DRB1 is mapped to a separate BH RLC channel 3. The UE3 wireless bearer DRB1 is mapped to a separate BH RLC channel 4. The UE3 wireless bearer DRB2 is mapped to a separate BH RLC channel 5, ensuring fine-grained QoS granularity at the UE wireless bearer level. 1:1 mapping requires more BH RLC channels and more signaling overhead to establish and release BH RLC channels.

[0221]

[0239] As shown in Figure 7B, the mapping between UE radio bearers and BH RLC channels supports N:1 mapping. Multiple UE radio bearers are multiplexed onto a single BH RLC channel based on a QoS template and specific bearer parameters. For example, UE1 radio bearer DRB3, UE2 radio bearer DRB2, and UE3 radio bearer DRB3 are mapped to a single BH RLC channel 6. N:1 mapping requires less signaling overhead because it necessitates the establishment of a small number of BH RLC channels.

[0222]

[0240] Furthermore, with the development of mobile communication technology, various new services and application scenarios are constantly emerging, and the requirements for these services regarding network functionality, connectivity performance, security, and similar aspects vary greatly. If a single network is used to carry these services, it is difficult to meet the requirements for high bandwidth, low latency, and high reliability. Also, building a new network for each type of service incurs significant costs. This demands that 5G be flexible, scalable, and capable of meeting diverse service requirements. Therefore, 5G provides customized network services for users through end-to-end network slicing. Specifically, through flexible allocation of network resources and on-demand networking, 5G virtualizes multiple isolated logical subnets with different characteristics on the same physical infrastructure to provide specific services to users. Different logical subnets are identified and distinguished by using multiple "single network slice selection assistance information" (S-NSSAI). Each S-NSSAI may include, but is not limited to, the following: Slice / service type (SST) refers to the specific characteristics and service type of a slice; and A slice differentiator (SD) is used as a supplement to SST and may be used further to distinguish between multiple network slice instances that satisfy the same SST; it is an optional component.

[0223]

[0241] Currently, IAB requires support for UE access, and slicing is an essential feature for end-to-end UE PDU sessions. However, existing slicing solutions only consider slice resource and functional network element isolation on the access side and core network side, and do not consider the backhaul link portion in IAB scenarios. In other words, slicing fails to implement end-to-end slice resource isolation in the IAB architecture. As a result, it cannot guarantee prioritized and reliable communication for high-priority services.

[0224]

[0242] To address the technical problem that end-to-end slice resource isolation cannot be implemented in the IAB architecture, and as a result, preferred and reliable communication for high-priority services cannot be guaranteed, a new communication method is provided in the embodiments of this application. The slice-based backhaul link configuration in the IAB scenario is designed to achieve end-to-end slice isolation in the IAB architecture and to guarantee preferred and reliable communication for high-priority services.

[0225]

[0243] Figure 8 is a schematic flowchart of a communication method according to an embodiment of the present application. The communication method is applicable to the field of communication technology, for example, communication in an IAB network. The communication method includes, but is not limited to, the following steps.

[0226]

[0244] S801: The first donor node generates the first piece of information.

[0227]

[0245] S802: The first donor node transmits the first information to the first IAB node, and in response, the first IAB node receives the first information from the first donor node.

[0228]

[0246] It will be understood that the first donor node in this embodiment of the present application may be a device having a processor / chip that can be configured to execute computer executable instructions, or may be a processor / chip that can be configured to execute computer executable instructions. This is not limited to this embodiment of the present application. Optionally, the first donor node may be the IAB donor node in Figure 1, the donor base station in Figure 3, IAB donor 1 or IAB donor 2 in Figure 4, CU1 or CU2 in Figures 5 and 6, or similar, and is configured to perform the communication method in this embodiment of the present application to achieve end-to-end slice isolation in the IAB architecture and to ensure preferred and reliable communication for high-priority services.

[0229]

[0247] It will be understood that the first IAB node in this embodiment of the present application may be a device equipped with a processor / chip that can be configured to execute computer executable instructions, or may be a processor / chip that can be configured to execute computer executable instructions. This is not limited to this embodiment of the present application. Optionally, the first IAB node may be the IAB node in Figure 1, the IAB node in Figure 2, IAB node 1, IAB node 2, IAB node 3, IAB node 4, or IAB node 5 in Figure 3, IAB node 1 or IAB node 2 in Figure 4, or similar, and may be involved in performing the communication method in this embodiment of the present application, and may be configured to achieve end-to-end slice isolation in the IAB architecture and to ensure preferred and reliable communication for high-priority services.

[0230]

[0248] The first piece of information indicates the slice corresponding to the first backhaul RLC channel corresponding to the first IAB node.

[0231]

[0249] It will be understood that, after receiving the first information, the first IAB node establishes a first backhaul RLC channel based on the slice indicated by the first information. Since the resources used by the first backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation can be achieved between the transmitting and receiving ends corresponding to the first backhaul RLC channel, thereby achieving end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, a backhaul RLC channel serving a high-priority service can use specific slice resources to ensure preferred and reliable communication of that service.

[0232]

[0250] Specifically, the first piece of information can indicate the slice corresponding to the first backhaul RLC channel corresponding to the first IAB node in the following manner.

[0233]

[0251] Method 1: The first information includes one or more slice identifiers corresponding to the first backhaul RLC channel.

[0234]

[0252] For example, the slice identifier included in the first piece of information may be Single Network Slice Selection Assistance Information (S-NSSAI), which is used to identify and distinguish between different slices. Each S-NSSAI may include, but is not limited to, the following: SST refers to specific characteristics and service types of slices; and It is an SD, used as a supplement to SST, and may be used further to distinguish multiple network slice instances that satisfy the same SST, and may be optional content.

[0235]

[0253] It will be understood that the first piece of information, by using the slice identifier contained in the first piece of information, can be used to specify the slice corresponding to the first backhaul RLC channel, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0236]

[0254] Method 2: The first piece of information indicates that the resource used by the first backhaul RLC channel is a reserved resource.

[0237]

[0255] A reserved resource includes resources reserved for at least one backhaul RLC channel, and at least one backhaul RLC channel includes a first backhaul RLC channel. The at least one backhaul RLC channel may be pre-configured or specified in the protocol, or it may be configured using signaling. For example, a reserved resource may be an allocation of resources reserved on an air interface (e.g., a Uu interface). For example, a reserved resource may be 5% of the air interface resources. If only 5% of the schedulable resources remain on the air interface, the remaining 5% of the resources are reserved resources. 95% of the resources that are already scheduled and used are unscheduled resources.

[0238]

[0256] Optionally, a reserved resource may be a specific resource reserved on an air interface. For example, a reserved resource may be a specific time-frequency location or area. Resources outside of a specific time-frequency location or area are non-reserved resources.

[0239]

[0257] Unreserved resources can be scheduled according to the standard air interface resource scheduling algorithm. Reserved resources can only be scheduled for use by at least one backhaul RLC channel.

[0240]

[0258] Reserved resources may be priority resources (resources used preferentially by a first backhaul RLC channel), dedicated resources (resources used only by a first backhaul RLC channel), shared resources (resources shared and used by multiple backhaul RLC channels, such as a first backhaul RLC channel), or similar. This is not limited to this embodiment of the present application.

[0241]

[0259] A reserved resource may be a resource that can only be used by at least one backhaul RLC channel (at least one backhaul RLC channel including the first backhaul RLC channel), even if no unreserved resources exist.

[0242]

[0260] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the first backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0243]

[0261] In this embodiment of the present application, the first information indicates that the first backhaul RLC channel uses reserved resources, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0244]

[0262] It will be understood that the two methods described above are used merely as possible examples for illustrative purposes and should not constitute a limitation on the embodiments of this application. All embodiments obtained based on supplements or appropriate modifications of the exemplary methods fall within the scope of protection of the embodiments of this application.

[0245]

[0263] In a possible embodiment, the first donor node receives second information from the first node before transmitting the first information to the first IAB node.

[0246]

[0264] The second piece of information indicates that the resources used by the first protocol data unit (PDU) session are reserved resources, and the first PDU session includes the PDU session corresponding to the first donor node.

[0247]

[0265] The first node in this embodiment of the present application may be a device having a processor / chip that can be configured to execute computer executable instructions, or it may be a processor / chip that can be configured to execute computer executable instructions. This is not limited to this embodiment of the present application. Optionally, the first node may be an access and mobility management function (AMF) that is involved in executing the communication method in this embodiment of the present application and is configured to achieve end-to-end slice isolation in the IAB architecture and to ensure preferred and reliable communication for high-priority services.

[0248]

[0266] In a scenario where the first node initiates a PDU session resource configuration request to the first donor node, it will be understood that, after receiving the second piece of information, the first donor node will establish a PDU session based on the reserved resources indicated by the second piece of information.

[0249]

[0267] In this embodiment of the present application, second information indicates that the PDU session uses reserved resources, thereby achieving slice resource isolation between the transmit and receive ends corresponding to the first backhaul RLC channel used by the PDU session.

[0250]

[0268] In a possible embodiment, the first donor node receives third information from the first node before transmitting the first information to the first IAB node.

[0251]

[0269] The third piece of information indicates that the first IAB node is a node providing a first-priority service, which may be a node providing a high-priority service such as public safety. This is not limited to this embodiment of the present application.

[0252]

[0270] The first node in this embodiment of the present application may be a device having a processor / chip configured to execute computer executable instructions, or it may be a processor / chip configured to execute computer executable instructions. This is not limited to this embodiment of the present application. Optionally, the first node may be an AMF, which is involved in executing the communication method of this embodiment of the present application and is configured to achieve end-to-end slice isolation in the IAB architecture and to ensure preferred and reliable communication for high-priority services.

[0253]

[0271] In a scenario where the first IAB node initially registers with and accesses the network, it will be understood that the first node initiates a UE context setup request to the first donor node, which includes the third piece of information. After receiving the third piece of information, the first donor node, following the instructions of the third piece of information, determines that the first IAB node is the node providing high-priority services, and may use the first piece of information to instruct the first IAB node to establish a corresponding first backhaul RLC channel based on the slice indicated by the first piece of information, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0254]

[0272] In this embodiment of the present application, the third piece of information indicates that the first IAB node is a node providing a first priority service, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel corresponding to the first IAB node.

[0255]

[0273] Optionally, before sending the first piece of information to the first IAB node, the first donor node may receive a fourth piece of information from the first IAB node.

[0256]

[0274] The fourth piece of information indicates that the first IAB node is a node providing a first-priority service, which may be a node providing a high-priority service such as public safety. This is not limited to this embodiment of the present application.

[0257]

[0275] In a scenario where the first IAB node initially registers with and accesses the network, it will be understood that the first IAB node sends fourth information to the first donor node. After receiving the fourth information, the first donor node may, following the instructions of the fourth information, determine that the first IAB node is a node that provides high-priority services, and by using the first information, instruct the first IAB node to establish a corresponding first backhaul RLC channel based on the slice indicated by the first information, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0258]

[0276] In this embodiment of the present application, the fourth piece of information indicates that the first IAB node is a node providing a first priority service, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel corresponding to the first IAB node.

[0259]

[0277] Optionally, after receiving third information from the first node, the first donor node determines, based on the third information, that the first backhaul RLC channel needs to use reserved resources.

[0260]

[0278] It will be understood that, after receiving the third information from the first node, the first donor node may, in accordance with the instructions of the third information, determine that the first IAB node is a node that provides high-priority services, that the first backhaul RLC channel should use reserved resources, and by using the first information, instruct the first IAB node to establish the corresponding first backhaul RLC channel based on the slice indicated by the first information, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel.

[0261]

[0279] In possible embodiments, the first information further includes a slice identifier corresponding to the first migration data.

[0262]

[0280] The first migration data includes data transmitted after the first IAB node transitions from its connection to the first donor node to its connection to the second donor node, where the second donor node is different from the first donor node.

[0263]

[0281] The second donor node in this embodiment of the present application may be a device having a processor / chip configured to execute computer executable instructions, or it may be a processor / chip configured to execute computer executable instructions. This is not limited to this embodiment of the present application. Optionally, the second donor node may be IAB donor 2 in Figure 4 and the first donor node may be IAB donor 1 in Figure 4; the second donor node may be CU2 in Figures 5 and 6 and the first donor node may be CU1 in Figures 5 and 6; or another combination may be used. The second donor node is involved in executing the communication method in this embodiment of the present application and is configured to achieve end-to-end slice isolation in the IAB architecture and to ensure preferred and reliable communication for high-priority services.

[0264]

[0282] In an IAB inter-topology data migration scenario, it would be understood that the first IAB node migrates from a connection to a first donor node to a connection to a second donor node. Correspondingly, after the migration of the first IAB node between the connections to the donor nodes, the first migration data is transmitted, and the first information further includes slice identifiers corresponding to the first migration data, and specifically, may include one or more slice identifiers corresponding to the first migration data.

[0265]

[0283] In this embodiment of the present application, the first information is a slice identifier corresponding to the first migration data. By using the slice identifier included in the first information, the slice corresponding to the backhaul RLC channel used by the first migration data is specified, slice resource separation between the transmitting end and the receiving end corresponding to the backhaul RLC channel used by the first migration data is realized, end-to-end slice resource separation in the IAB architecture is realized, and it is possible to guarantee prioritized reliable communication for high-priority services.

[0266]

[0284] In a possible embodiment, the first information further indicates a slice corresponding to a second backhaul RLC channel.

[0267]

[0285] The second backhaul RLC channel is a backhaul RLC channel corresponding to a second donor node.

[0268]

[0286] As an option, the first information includes one or more slice identifiers corresponding to the second backhaul RLC channel.

[0269]

[0287] For specific descriptions, refer to Method 1: The first information includes one or more slice identifiers corresponding to the first backhaul RLC channel. Details will not be described again here.

[0270]

[0288] As an option, the first information further indicates that the resources used by the second backhaul RLC channel are reserved resources.

[0271]

[0289] For specific descriptions, refer to Method 2: The first information indicates that the resources used by the first backhaul RLC channel are reserved resources. Details will not be described again here.

[0272]

[0290] In the IAB inter-topology data migration scenario, it will be understood that the first IAB node migrates from the connection with the first donor node to the connection with the second donor node. The first donor node can notify the second donor node of the slice corresponding to the first backhaul RLC channel in the topology, and the second donor node sets the slice corresponding to the second backhaul RLC channel in the topology of the second donor node based on the slice corresponding to the first backhaul RLC channel, and feeds back the slice corresponding to the second backhaul RLC channel to the first donor node. In this case, the first information transmitted by the first donor node to the first IAB node can further indicate the slice corresponding to the second backhaul RLC channel. It will be understood that the slice corresponding to the second backhaul RLC channel may be the same as or different from the slice corresponding to the first backhaul RLC channel. This is not limited in this embodiment of the present application.

[0273]

[0291] After receiving the first information, it will be understood that the first IAB node establishes the second backhaul RLC channel based on the slice indicated by the first information and performs IAB inter-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, it is possible to realize the slice resource separation between the transmitter and the receiver corresponding to the second backhaul RLC channel, thereby realizing the end-to-end slice resource separation in the IAB architecture. Due to the end-to-end slice resource separation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources to ensure the preferentially reliable communication of the high-priority service.

[0274]

[0292] In possible embodiments, if the slice corresponding to the second backhaul RLC channel is different from the slice corresponding to the first backhaul RLC channel, the first information further indicates the mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.

[0275]

[0293] Optional mapping relationships include the following:

[0276]

[0294] The slice identifier corresponding to the first backhaul RLC channel is either the same as or different from the slice identifier corresponding to the second backhaul RLC channel.

[0277]

[0295] Optional mapping relationships include the following:

[0278]

[0296] The slice / service type SST corresponding to the first backhaul RLC channel is the same as the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is different from the slice distinguisher SD corresponding to the second backhaul RLC channel; or The slice / service type SST corresponding to the first backhaul RLC channel is different from the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is the same as the slice distinguisher SD corresponding to the second backhaul RLC channel.

[0279]

[0297] In this embodiment of the present application, a first IAB node can establish a corresponding backhaul RLC channel based on the mapping relationship indicated by the first information, thereby achieving end-to-end resource isolation in the IAB architecture and ensuring preferred and reliable communication for high-priority services.

[0280]

[0298] It will be understood that the bearer mapping setting for the backhaul RLC channel in this embodiment of the present application is for the case where only a single S-NSSAI is carried for the backhaul RLC channel.

[0281]

[0299] The first donor node establishes a mapping relationship between the first backhaul RLC channel and the second backhaul RLC channel based on the slice information (S-NSSAI) corresponding to the backhaul RLC channel.

[0282]

[0300] Optionally, the slice information may be S-NSSAI, or a slice group ID, specifically a network slice AS group (NSAG) ID, or slice list information. This is not limited to this embodiment of the present application.

[0283]

[0301] In possible embodiments, when multiple S-NSSAIs are transported for a backhaul RLC channel, the bearer mapping settings for the backhaul RLC channel may be as follows:

[0284]

[0302] The first donor node establishes a mapping relationship between the first backhaul RLC channel and the second backhaul RLC channel based on the slice information (S-NSSAI) corresponding to the backhaul RLC channel.

[0285]

[0303] Optionally, the slice information may be S-NSSAI, or a slice group ID, specifically an NSAG ID, or slice list information. This is not limited to this embodiment of the present application.

[0286]

[0304] For a single IAB node, establishing a mapping relationship between the first backhaul RLC channel and the second backhaul RLC channel includes, but is not limited to, the following: (1) The S-NSSAI lists corresponding to the first backhaul RLC channel and the second backhaul RLC channel are the same; (2) The S-NSSAI lists corresponding to the first backhaul RLC channel and the second backhaul RLC channel are not exactly the same; (3) In the S-NSSAI list corresponding to the first backhaul RLC channel and the second backhaul RLC channel, the same S-NSSAI portion is most numerous; or (4) In the S-NSSAI list corresponding to the first backhaul RLC channel and the second backhaul RLC channel, the same SST is most frequently found.

[0287]

[0305] In this embodiment of the present application, the bearer mapping configuration of the backhaul RLC channel can be used to achieve end-to-end resource isolation in the IAB architecture and to ensure preferred and reliable communication for high-priority services.

[0288]

[0306] In possible embodiments, the first IAB node further supports rerouting. Specifically, if a radio link failure or buffer shortage occurs at the next-hop IAB node, the current IAB node may forward the data packet through another connected IAB node. This embodiment of the present application provides a slice-based rerouting method to ensure that the data packet can obtain resource assurance for the corresponding slice on the rerouting path. Details are as follows:

[0289]

[0307] When one or more S-NSSAIs are transported for the backhaul RLC channel, the following occurs during rerouting at the first IAB node:

[0290]

[0308] In the uplink (UL) direction, after selecting the next-hop IAB node, the first IAB node selects a backhaul RLC channel that has the maximum number of S-NSSAIs (overlapping SST) overlapping with or the same S-NSSAI (a same SST) as the backhaul RLC channel where the data packet to be rerouted is located, for transferring the UL data packet; and In the downlink (DL) direction, the first IAB node selects, as the next-hop node for rerouting, a child node corresponding to a backhaul RLC channel that has the maximum number of S-NSSAIs (overlapping SST) overlapping with or the same S-NSSAI (a same SST) as the backhaul RLC channel where the data packet to be rerouted is located, and other operations are consistent with those in the UL.

[0291]

[0309] In this embodiment of the present application, it is possible to realize slice-based reliable data transmission in the IAB architecture and guarantee preferentially reliable communication for high-priority services.

[0292]

[0310] In a possible embodiment, the first donor node further receives the fifth information from the first IAB node.

[0293]

[0311] The fifth information indicates slice resource congestion.

[0294]

[0312] It will be understood that after receiving the fifth information, the first donor node determines that the current slice resources are congested and performs traffic control for different slice services to guarantee the service quality of the slice services.

[0295]

[0313] In possible embodiments, nodes in the first backhaul adaptive protocol BAP topology support slices indicated by the first information.

[0296]

[0314] The nodes in the first BAP topology support the slices indicated by the first information, the first BAP topology includes a first donor node and a first IAB node, and the first BAP topology is managed by the first donor node.

[0297]

[0315] When configuring a BAP route, it will be understood that the first donor node must ensure that each IAB node on the BAP route supports the target slice, taking into account the slice types supported by each hop of the IAB nodes.

[0298]

[0316] In a possible embodiment, the first IAB node transmits the first data packet to the second IAB node based on the slice identifier corresponding to the first data packet.

[0299]

[0317] The second IAB node is an IAB node that supports the slice corresponding to the first data packet.

[0300]

[0318] It will be understood that if the next-hop backhaul link is unavailable, the first IAB node will select a next-hop IAB node that supports the target slice for rerouting based on the slice identifier corresponding to the first data packet, and send the first data packet to the next-hop IAB node (the second IAB node) to ensure that each IAB node on the BAP path supports the target slice.

[0301]

[0319] Figure 9 is a schematic flowchart of the communication method according to an embodiment of the present application. It will be understood that the steps in this embodiment of the present application may be considered as appropriate modifications or supplements to the embodiment in Figure 8. Alternatively, it will be understood that the communication method in this embodiment of the present application may be considered as an embodiment that can be performed independently. This is not limited to the present application. The communication method provided in this embodiment of the present application is applicable to the field of communication technology, for example, communication in IAB networks. The communication method includes, but is not limited to, the following steps:

[0302]

[0320] S901: The UE initiates a PDU session establishment request to the AMF, and in response, the AMF receives a PDU session establishment request from the UE, which includes an S-NSSAI corresponding to each PDU session.

[0303]

[0321] S902: The AMF initiates a PDU session resource configuration request to the donor IAB-CU, and in response, the donor IAB-CU receives a PDU session resource configuration request from the AMF, which includes an S-NSSAI corresponding to each PDU session.

[0304]

[0322] Optionally, the PDU session resource configuration request further carries session type indication information, showing that the PDU session corresponding to the donor IAB-CU needs to use reserved resources.

[0305]

[0323] S903: The donor IAB-CU initiates a UE context setting request for each IAB-MT to the upstream IAB-DU of the access IAB node, and in response, the upstream IAB-DU of the access IAB node receives the UE context setting request from the donor IAB-CU.

[0306]

[0324] The upstream IAB-DU of an access IAB node may be the DU of a donor IAB node or the DU of an intermediate IAB node. This is not limited to this embodiment of the present application.

[0307]

[0325] A UE context setting request can further carry one or more of the following information: (1) The corresponding S-NSSAI to be transported to each established backhaul RLC channel, and all associated backhaul RLC channels are those used to transport slice data in step S901; (2) For each established backhaul RLC channel, a corresponding S-NSSAI list, i.e., NSSAI, is carried, where, due to the use of N:1 bearer mapping, a single backhaul RLC channel can carry data from multiple slices; In this case, when performing resource scheduling, the upstream IAB-DU may refer to whether each S-NSSAI has reserved resources on the air interface, and if at least one S-NSSAI has reserved resources, the corresponding reserved resources will be used to schedule the backhaul RLC channel; and (3) A reservation instruction that is carried to indicate a backhaul RLC channel corresponding to an upstream IAB-DU in order to use a reserved resource on the air interface.

[0308]

[0326] S904: The donor IAB-CU sends a radio resource control (RRC) reset message to the access IAB-MT, and in response, the access IAB-MT receives an RRC reset message from the donor IAB-CU.

[0309]

[0327] The RRC reset message may carry one or more pieces of information that match one or more pieces of information carried in the UE context setting request in step S903. Further details are not provided here.

[0310]

[0328] S905: The donor IAB-CU sends a UE context setting request to the access IAB-DU, and in response, the access IAB-DU receives the UE context setting request from the donor IAB-CU, where the UE context setting request can carry the corresponding S-NSSAI.

[0311]

[0329] When a donor IAB-CU establishes a mapping bearer relationship, it should be understood that the relationship is associated with backhaul RLC channels belonging to the same S-NSSAI, or backhaul RLC channels whose corresponding reservation indications indicate reserved resources. In other words, a single backhaul RLC channel can only be mapped to backhaul RLC channels that carry the same S-NSSAI, or backhaul RLC channels that use reserved resources.

[0312]

[0330] In this embodiment of the present application, the first information indicates a slice corresponding to a first backhaul RLC channel corresponding to a first IAB node, thereby enabling slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel, thereby achieving end-to-end slice resource isolation in the IAB architecture and ensuring preferred and reliable communication for high-priority services.

[0313]

[0331] Figure 10 is a schematic flowchart of the communication method according to an embodiment of the present application. It will be understood that the steps in this embodiment of the present application may be considered as appropriate modifications or supplements to the embodiment in Figure 8, or as appropriate modifications to the embodiment in Figure 9. Alternatively, it will be understood that the communication method in this embodiment of the present application may be considered as an embodiment that can be performed independently. This is not limited to the present application. The communication method provided in this embodiment of the present application is applicable to the field of communication technology, for example, communication in IAB networks. The communication method includes, but is not limited to, the following steps:

[0314]

[0332] S1001: IAB-MT performs initial registration.

[0315]

[0333] Optionally, IAB-MT can represent the network using RRC or NAS, and IAB-MT can function as a serving node for high-priority services (e.g., public safety services).

[0316]

[0334] S1002: The AMF sends a UE context setting request to the donor IAB-CU, and in response, the donor IAB-CU receives the UE context setting request from the AMF.

[0317]

[0335] The UE context configuration request may include the supported NSSAI and supported public network integrated non-public network (PNI-NPN) for the IAB-MT. Optionally, further instructional information indicating that the IAB-MT will function as a serving node for high-priority services may be carried.

[0318]

[0336] S1003: The donor IAB-CU determines, based on service type instruction information transmitted by NSSAI, PNI-NPN, or AMF, that the backhaul link associated with the IAB-MT needs to use reserved resources on the air interface.

[0319]

[0337] S1004: The donor IAB-CU initiates a UE context setting request for each IAB-MT to the upstream IAB-DU of the access IAB node, and in response, the upstream IAB-DU of the access IAB node receives the UE context setting request from the donor IAB-CU.

[0320]

[0338] The upstream IAB-DU of an access IAB node may be the DU of a donor IAB node or the DU of an intermediate IAB node. This is not limited to this embodiment of the present application.

[0321]

[0339] A UE context setting request can further carry one or more of the following information: (1) The corresponding S-NSSAI to be transported to each established backhaul RLC channel, and all associated backhaul RLC channels are those used to transport slice data in step S901; (2) For each established backhaul RLC channel, a corresponding S-NSSAI list, i.e., NSSAI, is carried, where, due to the use of N:1 bearer mapping, a single backhaul RLC channel can carry data from multiple slices; In this case, when performing resource scheduling, the upstream IAB-DU may refer to whether each S-NSSAI has reserved resources on the air interface, and if at least one S-NSSAI has reserved resources, the corresponding reserved resources will be used to schedule the backhaul RLC channel; and (3) A reservation instruction that is carried to indicate a backhaul RLC channel corresponding to an upstream IAB-DU in order to use a reserved resource on the air interface.

[0322]

[0340] S1005: The donor IAB-CU sends an RRC reset message to the access IAB-MT, and in response, the access IAB-MT receives an RRC reset message from the donor IAB-CU.

[0323]

[0341] The RRC reset message may carry one or more pieces of information that match one or more pieces of information carried in the UE context setting request in step S1004. Further details are not described here.

[0324]

[0342] When a donor IAB-CU establishes a mapping bearer relationship, it should be understood that the relationship is associated with backhaul RLC channels belonging to the same S-NSSAI, or backhaul RLC channels whose corresponding reservation indications indicate reserved resources. In other words, a single backhaul RLC channel can only be mapped to backhaul RLC channels that carry the same S-NSSAI, or backhaul RLC channels that use reserved resources.

[0325]

[0343] In this embodiment of the present application, the first information indicates a slice corresponding to a first backhaul RLC channel corresponding to a first IAB node, thereby enabling slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel, thereby achieving end-to-end slice resource isolation in the IAB architecture and ensuring preferred and reliable communication for high-priority services.

[0326]

[0344] Furthermore, embodiments of the present application provide a communication method. It will be understood that the steps in this embodiment of the present application may be considered as appropriate modifications or supplements to the embodiment in Figure 8, or as appropriate modifications to the embodiment in Figure 9, or as appropriate modifications to the embodiment in Figure 10. Alternatively, it will be understood that the communication method in this embodiment of the present application may be considered as an embodiment that can be performed independently. This is not limited to the present application. The communication method provided in this embodiment of the present application is applicable to the field of communication technology, for example, communication in IAB networks. The communication method includes, but is not limited to, the following steps:

[0327]

[0345] The first donor node generates the first information and sends the first information to the first IAB node. In response, the first IAB node receives the first information from the first donor node.

[0328]

[0346] The first piece of information indicates that the resources used by the first backhaul radio link control RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, the at least one backhaul RLC channel includes the first backhaul RLC channel, and the first backhaul RLC channel is a backhaul RLC channel corresponding to the first integrated access and backhaul IAB node.

[0329]

[0347] It will be understood that reserved resources are allocations of resources reserved on the air interface for a first backhaul RLC channel, and that the allocation of reserved resources may include, but not limited to, preferred resources (resources used preferentially by the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared and used by multiple backhaul RLC channels such as the first backhaul RLC channel), or similar. This is not limited to this embodiment of the present application.

[0330]

[0348] Optionally, reserved resources are resources that can only be used by at least one backhaul RLC channel if no unreserved resources exist.

[0331]

[0349] Optionally, the reserved resource may be a reserved resource that carries a slice identifier corresponding to the first backhaul RLC channel, or it may be a reserved resource that does not carry a slice identifier. This is not limited to this embodiment of the present application.

[0332]

[0350] In this embodiment of the present application, the first information indicates that the first backhaul RLC channel uses reserved resources, thereby implementing slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel, and thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to high-priority services can use specific slice resources to ensure preferred and reliable communication of high-priority services.

[0333]

[0351] Furthermore, embodiments of the present application provide a communication method. It will be understood that the steps in this embodiment of the present application may be considered as appropriate modifications or supplements to the embodiment in Figure 8, or as appropriate modifications to the embodiment in Figure 9, or as appropriate modifications to the embodiment in Figure 10. Alternatively, it will be understood that the communication method in this embodiment of the present application may be considered as an embodiment that can be performed independently. This is not limited to the present application.

[0334]

[0352] The communication method provided in this embodiment of the present application is applicable to the field of communication technology, for example, communication in an IAB network, and more specifically, to an IAB inter-topology data migration scenario. For details, please refer to Figures 5 and 6. The first IAB node transitions from a connection with a first donor node to a connection with a second donor node. Correspondingly, the first migration data is transmitted after the transition of the first IAB node between the connections with the donor nodes. The communication method includes, but is not limited to, the following steps.

[0335]

[0353] The first donor node generates the first information and sends the first information to the first IAB node. In response, the first IAB node receives the first information from the first donor node.

[0336]

[0354] The first migration data includes data transmitted after the first IAB node transitions from its connection to the first donor node to its connection to the second donor node, where the second donor node is different from the first donor node.

[0337]

[0355] The first information includes slice identifiers corresponding to the first migration data, and may specifically include one or more slice identifiers corresponding to the first migration data. See Figure 11A for details. Figure 11A is a diagram of the information elements according to an embodiment of the present application. In Figure 11A, S-NSSAI corresponding to the migration data is added to the first information to account for slice expansion.

[0338]

[0356] The first information is a slice identifier corresponding to the first migration data, and by using the slice identifier contained in the first information, the slice corresponding to the backhaul RLC channel used by the first migration data is specified, thereby achieving slice resource isolation between the transmitting and receiving ends corresponding to the backhaul RLC channel used by the first migration data, thereby achieving end-to-end slice resource isolation in the IAB architecture, and ensuring preferred and reliable communication for high-priority services.

[0339]

[0357] In possible embodiments, the first information further indicates slices corresponding to a second backhaul RLC channel.

[0340]

[0358] The second backhaul RLC channel is the backhaul RLC channel corresponding to the second donor node.

[0341]

[0359] Optionally, the first piece of information includes one or more slice identifiers corresponding to the second backhaul RLC channel.

[0342]

[0360] For a detailed explanation, please refer to Method 1: The first piece of information includes one or more slice identifiers corresponding to the first backhaul RLC channel. Further details are not provided here.

[0343]

[0361] Optionally, the first piece of information further indicates that the resources used by the second backhaul RLC channel are reserved resources.

[0344]

[0362] For a detailed explanation, please refer to Method 2: The first piece of information indicates that the resource used by the first backhaul RLC channel is a reserved resource. Further details are not provided here.

[0345]

[0363] For further details, please refer to Figure 11B. Figure 11B is a diagram of information elements according to an embodiment of the present application. In Figure 11B, considering slice expansion, the first information needs to indicate the S-NSSAI(list) or reservation instruction corresponding to each backhaul RLC channel, and indicate the slice or reserved resource used by the backhaul RLC channel associated with the peer CU.

[0346]

[0364] It will be understood that the CU can perform access control on the backhaul RLC channel based on the slice. Specifically, if the corresponding slice is not supported, the CU will refuse to establish the backhaul RLC channel.

[0347]

[0365] It will be understood that the CU is capable of performing slice remapping directed towards backhaul RLC channels. Specifically, the slices corresponding to the inlet and outlet backhaul RLC channels may differ, and the backhaul RLC channels are transported by using different slice resources.

[0348]

[0366] It will be understood that, after receiving the first information, the first IAB node establishes a second backhaul RLC channel based on the slice indicated by the first information and performs IAB inter-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, slice resource isolation can be implemented between the transmitting and receiving ends corresponding to the second backhaul RLC channel, thereby implementing end-to-end slice resource isolation in the IAB architecture. Due to end-to-end slice resource isolation, the backhaul RLC channel corresponding to a high-priority service can use a specific slice resource to ensure preferred and reliable communication of that service.

[0349]

[0367] Figure 12 is a schematic flowchart of the communication method according to an embodiment of the present application. It will be understood that the steps in this embodiment of the present application may be considered supplementary to the embodiments in Figures 8, 9, or 10. Alternatively, it will be understood that the communication method in this embodiment of the present application may be considered as an embodiment that can be performed independently. This is not limited to the present application. The communication method provided in this embodiment of the present application is applicable to the field of communication technology, for example, communication in IAB networks. The communication method includes, but is not limited to, the following steps:

[0350]

[0368] S1201: The first IAB node (IAB-DU) sends a congestion instruction to the first donor node (donor CU) to indicate slice resource congestion. In response, the first donor node (donor-CU) receives a congestion instruction from the first IAB node (IAB-DU).

[0351]

[0369] It will be understood that, upon receiving a congestion instruction, the first donor node determines that the current slice resource is congested and performs traffic control for different slice services to ensure the quality of service for those slice services.

[0352]

[0370] Alternatively, as an option, the first IAB node sends the first data packet to the second IAB node based on the slice identifier corresponding to the first data packet.

[0353]

[0371] The second IAB node is an IAB node that supports the slice corresponding to the first data packet.

[0354]

[0372] It will be understood that if the next-hop backhaul link is unavailable (for example, if the slice resources are congested), the first IAB node will select a next-hop IAB node that supports the target slice for rerouting based on the slice identifier corresponding to the first data packet, and will transmit the first data packet to the next-hop IAB node (the second IAB node), ensuring that each IAB node on the BAP path supports the target slice.

[0355]

[0373] The above describes in detail the methods provided in the embodiments of the present application. Below, we provide an apparatus for carrying out any one of the methods in the embodiments of the present application. For example, we provide an apparatus that includes a unit (or means) for carrying out a step performed by a device in any one of the aforementioned methods.

[0356]

[0374] Figure 13 is a structural diagram of a communication device according to an embodiment of the present application.

[0357]

[0375] As shown in Figure 13, the communication device 130 may include a communication unit 1301 and a processing unit 1302. The communication unit 1301 and the processing unit 1302 may be software, hardware, or a combination of software and hardware.

[0358]

[0376] The communication unit 1301 can implement a transmit function and / or a receive function, and the communication unit 1301 may also be described as a transceiver unit. Alternatively, the communication unit 1301 may be a unit that integrates an acquisition unit and a transmit unit. The acquisition unit is configured to implement a receive function, and the transmit unit is configured to implement a transmit function. Optionally, the communication unit 1301 may be configured to receive information transmitted by another device, and may also be further configured to transmit information to another device.

[0359]

[0377] In possible designs, the communication device 130 may correspond to the first donor node in the embodiments of the methods shown in Figures 8, 9, and 10. For example, the communication device 130 may be the first donor node or a chip within the first donor node. The communication device 130 may include units configured to perform the operations performed by the first donor node in the embodiments of the methods shown in Figures 8, 9, and 10. The units within the communication device 130 are also configured separately to perform the operations performed by the first donor node in the embodiments of the methods shown in Figures 8, 9, and 10. Each unit is described below.

[0360]

[0378] The processing unit 1302 is configured to generate first information, which indicates a slice corresponding to a first backhaul radio link control RLC channel, and the first backhaul RLC channel is a backhaul RLC channel corresponding to a first integrated access and backhaul IAB node.

[0361]

[0379] The communication unit 1301 is configured to transmit the first information to the first IAB node.

[0362]

[0380] In a possible implementation, the first piece of information includes one or more slice identifiers corresponding to the first backhaul RLC channel.

[0363]

[0381] In a possible implementation, the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the first backhaul RLC channel.

[0364]

[0382] In a possible implementation, the communication unit 1301 is further configured to receive second information from a first node, the second information indicating that a resource used by a first protocol data unit (PDU) session is a reserved resource, and the first PDU session includes a PDU session corresponding to a communication device.

[0365]

[0383] In a possible implementation, the communication unit 1301 is further configured to receive third information from the first node, the third information indicating that the first IAB node is a node providing first priority services.

[0366]

[0384] In a possible implementation, the communication unit is further configured to receive a fourth piece of information from the first IAB node, the fourth piece of information indicating that the first IAB node is a node providing a first priority service.

[0367]

[0385] In a possible implementation, the processing unit 1302 is further configured to determine, based on third information, that the first backhaul RLC channel needs to use a reserved resource.

[0368]

[0386] In a possible implementation, the first information further includes a slice identifier corresponding to the first migration data, the first migration data includes data transmitted after the first IAB node transitions from a connection with a communication device to a connection with a second donor node, the second donor node being different from the communication device.

[0369]

[0387] In a possible implementation, the first information further indicates the slice corresponding to the second backhaul RLC channel, which is the backhaul RLC channel corresponding to the second donor node.

[0370]

[0388] In a possible implementation, the communication unit 1301 is further configured to receive a fifth piece of information from the first IAB node, the fifth piece of information indicating slice resource congestion.

[0371]

[0389] In possible implementations, nodes in the first backhaul adaptive protocol (BAP) topology support slices indicated by the first information, the first BAP topology is managed by a communication device, and the first IAB nodes belong to the first BAP topology.

[0372]

[0390] In implementation, the communication device is a communication device. If the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0373]

[0391] In another implementation, the communication device is a chip (system) or circuit used in a communication device. If the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit, or similar in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit, or similar.

[0374]

[0392] In another possible design of the communication device 130 shown in Figure 13, the communication device 130 may correspond to the first IAB node in the embodiments of the methods shown in Figures 8, 9, and 10. For example, the communication device 130 may be the first IAB node or a chip within the first IAB node. The communication device 130 may include units configured to perform operations performed by the first IAB node in the embodiments of the methods shown in Figures 8, 9, and 10. The units within the communication device 130 are also configured separately to perform operations performed by the first IAB node in the embodiments of the methods shown in Figures 8, 9, and 10. Each unit is described below.

[0375]

[0393] The communication unit 1301 is configured to receive first information from a first donor node, the first information indicating a slice corresponding to a first backhaul radio link control RLC channel, and the first backhaul RLC channel is a backhaul RLC channel corresponding to a communication device.

[0376]

[0394] The processing unit 1302 is configured to establish a first backhaul RLC channel based on the first information.

[0377]

[0395] In a possible implementation, the first piece of information includes one or more slice identifiers corresponding to the first backhaul RLC channel.

[0378]

[0396] In a possible implementation, the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, the reserved resources include reserved resources for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the first backhaul RLC channel.

[0379]

[0397] In a possible implementation, the communication unit 1301 is further configured to transmit a fourth piece of information to the first donor node, the fourth piece of information indicating that the communication device is a node providing a first priority service.

[0380]

[0398] In a possible implementation, the first information further includes a slice identifier corresponding to the first migration data, the first migration data includes data transmitted after the communication device transitions from a connection with a first donor node to a connection with a second donor node, the second donor node being different from the first donor node.

[0381]

[0399] In a possible implementation, the first information further indicates the slice corresponding to the second backhaul RLC channel, which is the backhaul RLC channel corresponding to the second donor node.

[0382]

[0400] In a possible implementation, the communication unit 1301 is further configured to transmit a fifth piece of information to the first donor node, the fifth piece of information indicating slice resource congestion.

[0383]

[0401] In possible implementations, nodes in the first backhaul adaptive protocol (BAP) topology support slices indicated by the first information, the first BAP topology is managed by the first donor node, and the communication device belongs to the first BAP topology.

[0384]

[0402] In a possible implementation, the processing unit 1302 is further configured to send the first data packet to a second IAB node based on the slice identifier corresponding to the first data packet, the second IAB node being an IAB node that supports the slice corresponding to the first data packet.

[0385]

[0403] In implementation, the communication device is a communication device. If the communication device is a communication device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0386]

[0404] In another implementation, the communication device is a chip (system) or circuit used in a communication device. If the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, associated circuit, or similar in the chip (system) or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit, or similar.

[0387]

[0405] According to this embodiment of the present application, the units in the device shown in Figure 13 may be separate, or all may be combined with one or more other units, or certain units (or some certain units) in the device may be further divided into multiple units having more detailed functions. This is possible without affecting the implementation of the technical effects of this embodiment of the present application. The aforementioned units are obtained through division based on logical functions. In actual application, the function of one unit may be performed by multiple units, or the function of multiple units may be performed by one unit. In other embodiments of the present application, the electronic device may further include other units. In actual application, the function may alternatively be performed with the assistance of other units, or it may be performed in coordination with multiple units.

[0388]

[0406] It should be noted that for implementation of the unit, further reference is available to the corresponding descriptions in the embodiments of the method shown in Figures 8, 9, and 10.

[0389]

[0407] In the communication device 130 described in Figure 13, the first information indicates a slice corresponding to the first backhaul RLC channel corresponding to the first IAB node. As a result, slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation in the IAB architecture and ensuring prioritized and reliable communication for high-priority services.

[0390]

[0408] Figure 14 is a structural diagram of a communication device according to an embodiment of the present application.

[0391]

[0409] It should be understood that the communication device 140 shown in Figure 14 is merely an example. The communication device in this embodiment of the present application may further include other components, or may include components having functions similar to those of each component in Figure 14, or it is not necessarily required to include all of the components in Figure 14.

[0392]

[0410] The communication device 140 includes a communication interface 1401 and at least one processor 1402.

[0393]

[0411] The communication device 140 may correspond to any node or device in the first donor node and the first IAB node. The communication interface 1401 is configured to receive and transmit signals, and at least one processor 1402 executes program instructions, so that the communication device 140 performs the corresponding steps of the method performed by the corresponding device in the embodiment of the method.

[0394]

[0412] In possible designs, the communication device 140 may correspond to the first donor node in the embodiments of the method shown in Figures 8, 9, and 10. For example, the communication device 140 may be the first donor node or a chip within the first donor node. The communication device 140 may include components configured to perform the operations performed by the first donor node in the embodiments of the method. Furthermore, the components within the communication device 140 are separately configured to perform the operations performed by the first donor node in the embodiments of the method. Further details may be as follows:

[0395]

[0413] The first donor node generates first information, which indicates a slice corresponding to the first backhaul radio link control RLC channel, and the first backhaul RLC channel is the backhaul RLC channel corresponding to the first integrated access and backhaul IAB node.

[0396]

[0414] The first donor node transmits the first information to the first IAB node.

[0397]

[0415] In another possible design, the communication device 140 may correspond to the first IAB node in the embodiment of the method shown in Figures 8, 9, and 10. For example, the communication device 140 may be the first IAB node or a chip within the first IAB node. The communication device 140 may include components configured to perform the operations performed by the first IAB node in the embodiment of the method. Furthermore, the components within the communication device 140 are separately configured to perform the operations performed by the first IAB node in the embodiment of the method. Further details may be as follows:

[0398]

[0416] The first access and backhaul integrated IAB node receives first information from the first donor node, the first information indicating a slice corresponding to the first backhaul radio link control RLC channel, and the first backhaul RLC channel is the backhaul RLC channel corresponding to the first IAB node.

[0399]

[0417] The first IAB node establishes the first backhaul RLC channel based on the first information.

[0400]

[0418] In the communication device 140 described in Figure 14, the first information indicates a slice corresponding to the first backhaul RLC channel corresponding to the first IAB node, thereby enabling slice resource isolation between the transmitting and receiving ends corresponding to the first backhaul RLC channel, thereby achieving end-to-end slice resource isolation in the IAB architecture and ensuring prioritized and reliable communication for high-priority services.

[0401]

[0419] It should be understood that when communication device 140 is the first donor node, Figure 15 shows another form of communication device 140. In Figure 15, communication device 150 is the first donor node. It should be understood that the first donor node includes a CU and a DU. The CU may include a communication interface and a processor, and optionally further include memory. The communication interface can be configured to communicate with the CU of the donor node or the DU of the IAB node. The DU can also include a communication interface, a processor, memory, and a bus connecting the communication interface, processor, and memory. The communication interface is configured to communicate with the MT of the IAB node.

[0402]

[0420] For cases where the communication device is a chip or chip system, please refer to the chip structure diagram shown in Figure 16.

[0403]

[0421] As shown in Figure 16, the chip 160 includes a processor 1601 and an interface 1602. There may be one or more processors 1601 and multiple interfaces 1602. It should be noted that the functions corresponding to the processor 1601 and interface 1602 separately may be implemented using hardware design, software design, or a combination of software and hardware. This is not limited to the present invention.

[0404]

[0422] Optionally, the chip 160 may further include memory 1603, which is configured to store the necessary program instructions and data.

[0405]

[0423] In this application, the processor 1601 may be configured to call an implementation program of a communication method provided in one or more embodiments of this application from memory 1603 in one or more devices or nodes within the first donor node and the first IAB node, and to execute instructions contained in the program. The interface 1602 may be configured to output the execution results of the processor 1601. In this application, the interface 1602 can be specifically configured to output messages or information of the processor 1601.

[0406]

[0424] For the communication methods provided in one or more embodiments of this application, please refer to the embodiments shown in Figures 8, 9, and 10. Further details are not described here.

[0407]

[0425] The processor in this embodiment of the present application may be a Central Processing Unit (CPU), or the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), another programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

[0408]

[0426] The memory in this embodiment of the present application is configured to provide storage space capable of storing data such as operating systems and computer programs. The memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0409]

[0427] Based on the methods provided in the embodiments of the present application, embodiments of the present application further provide a computer-readable storage medium for storing a computer program. When the computer program is executed on one or more processors, the methods shown in Figures 8, 9, and 10 can be carried out.

[0410]

[0428] Based on the methods provided in the embodiments of the present application, embodiments of the present application further provide a computer program product. The computer program product includes a computer program. When the computer program is executed on a processor, the methods shown in Figures 8, 9, and 10 can be carried out.

[0411]

[0429] Embodiments of the present application further provide a system. The system includes at least one communication device 130, communication device 140, communication device 150, or chip 160 and is configured to perform steps performed by the corresponding device in any one of the embodiments of Figures 8, 9, and 10.

[0412]

[0430] Embodiments of the present application further provide a system comprising a first donor node and a first IAB node. The first donor node is configured to perform steps performed by the first donor node in any one of the embodiments of Figures 8, 9, and 10. The first IAB node is configured to perform steps performed by the first IAB node in any one of the embodiments of Figures 8, 9, and 10.

[0413]

[0431] Embodiments of the present application further provide a processing apparatus, the apparatus including a processor and an interface, the processor configured to perform a method in any one of the embodiments of the method.

[0414]

[0432] It should be understood that the processing unit may be a chip. For example, the processing unit may be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, a system on a chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or another integrated chip. The processing unit may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or similar. The steps in the method disclosed with reference to embodiments of this application may be performed and completed directly by a hardware decoding processor, or by using a combination of hardware and software modules within the decoding processor.The software module may be placed in a storage medium that is mature in the art, such as random-access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is placed in memory, the processor reads the information in memory, and in combination with the processor hardware completes the steps of the method.

[0415]

[0433] It will be understood that the memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or flash memory. Volatile memory may be random access memory (RAM) and may be used as an external cache. Many forms of RAM may be used, not as an example but as an example, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the methods and systems described herein includes, but is not limited to, these memories and any other suitable type of memory.

[0416]

[0434] All or part of the embodiments described above may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When a computer instruction is loaded onto a computer and executed, the procedure or function according to the embodiment of the present application occurs, either completely or partially. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable device. The computer instructions may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired means (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless means (e.g., infrared, radio, or microwave). Computer-readable storage media may be any available media accessible by a computer, or a data storage device that integrates one or more available media, such as a server or data center. Available media may be magnetic media (e.g., floppy disks, hard disk drives, or magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), semiconductor media (e.g., solid-state disks (SSDs)), or similar.

[0417]

[0435] The units in the above embodiments of the apparatus fully correspond to the electronic devices in the embodiments of the method, and the corresponding modules or units perform the corresponding steps. For example, a communication unit (transceiver) performs the receiving or transmitting step in the embodiments of the method, and steps other than the transmitting and receiving steps may be performed by a processing unit (processor). For the functions of a particular unit, please refer to the corresponding embodiments of the method. There may be one or more processors.

[0418]

[0436] It will be understood that in the embodiments of this application, an electronic device may perform some or all of the steps in the embodiments of this application. These steps or actions are merely examples. In the embodiments of this application, other actions or various variations of actions may be performed further. Also, the steps may be performed in an order different from the order presented in the embodiments of this application, and not all actions in the embodiments of this application may be performed.

[0419]

[0437] A person skilled in the art will recognize, in combination with the examples described in the embodiments disclosed in this specification, that units and algorithmic steps may be implemented by electronic hardware or by a combination of computer software and electronic hardware. Whether the function is performed by hardware or by software depends on the specific application and design constraints of the technical solution. A person skilled in the art may use different methods to implement the described function for each specific application, but it should not be considered that such implementations extend beyond the scope of this application.

[0420]

[0438] For the sake of convenient and concise explanation, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, apparatus, and units should be referred to in the corresponding processes in the embodiments of the method. Further details are not described here.

[0421]

[0439] In some embodiments provided in this application, it should be understood that the disclosed systems, apparatus, and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementations. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. Also, the mutual coupling, direct coupling, or communication connection shown or described may be implemented through some interface. Indirect coupling or communication connection between apparatus or units may be implemented in electrical, mechanical, or other forms.

[0422]

[0440] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected based on the actual requirements to achieve the objectives of the solution of the embodiment.

[0423]

[0441] Furthermore, the functional units in the embodiments of this application may be integrated into a single processing unit, and each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0424]

[0442] When a function is implemented in the form of a software function unit and sold or used as a standalone product, the function may be stored on a computer-readable storage medium. Based on such understanding, the technical solutions of the present application may be implemented in essence, in part, or in part in the form of a software product. A computer software product is stored on a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, network device, or similar) to perform all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory ROM, random access memory RAM, magnetic disk, or optical disk.

[0425]

[0443] The foregoing description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any modifications or substitutions that are readily conceived by a person skilled in the art within the scope of the technical scope disclosed in the present application shall also fall within the scope of protection of the present application.

Claims

1. It is a method of communication: The steps include: a first donor node generating first information, the first information indicating a slice corresponding to a first backhaul radio link control RLC channel, the first backhaul RLC channel being a backhaul RLC channel corresponding to a first integrated access and backhaul IAB node; and The first donor node transmits the first information to the first IAB node; A method that includes this.

2. The method according to claim 1, wherein the first information includes one or more slice identifiers corresponding to the first backhaul RLC channel.

3. The method according to claim 1 or 2, wherein the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the first backhaul RLC channel.

4. In the method according to any one of claims 1 to 3, prior to the step in which the first donor node transmits the first information to the first IAB node, the method: A method further comprising the step of the first donor node receiving second information from the first node, the second information indicating that a resource used by a first protocol data unit PDU session is a reserved resource, and the first PDU session includes a PDU session corresponding to the first donor node.

5. In the method according to any one of claims 1 to 3, prior to the step in which the first donor node transmits the first information to the first IAB node, the method: A method further comprising the step of the first donor node receiving third information from the first node, wherein the third information indicates that the first IAB node is a node providing a first priority service.

6. The method according to claim 5, wherein the method is: A method further comprising the step of the first donor node receiving fourth information from the first IAB node, wherein the fourth information indicates that the first IAB node is a node providing a first priority service.

7. In the method according to claim 5 or 6, the method is: The first donor node determines, based on the third information, that the first backhaul RLC channel needs to use a reserved resource; A method that further includes this.

8. A method according to any one of claims 1 to 7, wherein the first information includes a slice identifier corresponding to first migration data, the first migration data includes data transmitted after the first IAB node transitions from a connection with a first donor node to a connection with a second donor node, and the second donor node is different from the first donor node.

9. The method according to claim 8, wherein the first information further indicates a slice corresponding to a second backhaul RLC channel, the second backhaul RLC channel being a backhaul RLC channel corresponding to a second donor node.

10. The method according to claim 9, wherein the slice corresponding to the second backhaul RLC channel differs from the slice corresponding to the first backhaul RLC channel, and the first information further indicates a mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.

11. In the method according to claim 10, the mapping relationship is: A method comprising the condition that the slice identifier corresponding to the first backhaul RLC channel is the same as or different from the slice identifier corresponding to the second backhaul RLC channel.

12. In the method according to claim 10 or 11, the mapping relationship is: The slice / service type SST corresponding to the first backhaul RLC channel is the same as the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is different from the slice distinguisher SD corresponding to the second backhaul RLC channel; or A method wherein the slice / service type SST corresponding to the first backhaul RLC channel is different from the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is the same as the slice distinguisher SD corresponding to the second backhaul RLC channel.

13. The method according to any one of claims 1 to 12, wherein the method is: A method further comprising the step of the first donor node receiving fifth information from the first IAB node, wherein the fifth information indicates slice resource congestion.

14. A method according to any one of claims 1 to 13, wherein a node in a first backhaul adaptive protocol BAP topology supports a slice indicated by the first information, the first BAP topology is managed by the first donor node, and the first IAB node belongs to the first BAP topology.

15. It is a method of communication: The steps include: a first integrated access and backhaul IAB node receiving first information from a first donor node, the first information indicating a slice corresponding to a first backhaul radio link control RLC channel, and the first backhaul RLC channel being a backhaul RLC channel corresponding to the first IAB node; and The first IAB node establishes the first backhaul RLC channel based on the first information; A method that includes this.

16. The method according to claim 15, wherein the first information includes one or more slice identifiers corresponding to the first backhaul RLC channel.

17. The method according to claim 15 or 16, wherein the first information further indicates that the resources used by the first backhaul RLC channel are reserved resources, the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes the first backhaul RLC channel.

18. In the method according to any one of claims 1 to 3, prior to the step in which the first integrated access and backhaul IAB node receives the first information from the first donor node, the method: A method further comprising the step of the first IAB node transmitting fourth information to the first node, wherein the fourth information indicates that the first IAB node is a node providing a first priority service.

19. A method according to any one of claims 15 to 18, wherein the first information further includes a slice identifier corresponding to first migration data, the first migration data includes data transmitted after the first IAB node has transitioned from a connection with the first donor node to a connection with the second donor node, the second donor node being different from the first donor node.

20. The method according to claim 19, wherein the first information further indicates a slice corresponding to a second backhaul RLC channel, the second backhaul RLC channel being a backhaul RLC channel corresponding to a second donor node.

21. The method according to claim 20, wherein the slice corresponding to the second backhaul RLC channel differs from the slice corresponding to the first backhaul RLC channel, and the first information further indicates a mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.

22. In the method according to claim 21, the mapping relationship is: A method comprising the condition that the slice identifier corresponding to the first backhaul RLC channel is the same as or different from the slice identifier corresponding to the second backhaul RLC channel.

23. In the method according to claim 21 or 22, the mapping relationship is: The slice / service type SST corresponding to the first backhaul RLC channel is the same as the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is different from the slice distinguisher SD corresponding to the second backhaul RLC channel; or A method wherein the slice / service type SST corresponding to the first backhaul RLC channel is different from the slice / service type SST corresponding to the second backhaul RLC channel, and the slice distinguisher SD corresponding to the first backhaul RLC channel is the same as the slice distinguisher SD corresponding to the second backhaul RLC channel.

24. The method according to any one of claims 15 to 23, wherein the method is: A method further comprising the step of the first IAB node transmitting fifth information to the first donor node, wherein the fifth information indicates slice resource congestion.

25. A method according to any one of claims 15 to 24, wherein a node in a first backhaul adaptive protocol BAP topology supports a slice indicated by the first information, the first BAP topology is managed by the first donor node, and the first IAB node belongs to the first BAP topology.

26. The method according to any one of claims 15 to 25, wherein the method is: A method further comprising the step of the first IAB node transmitting a first data packet to a second IAB node based on a slice identifier corresponding to the first data packet, wherein the second IAB node is an IAB node that supports the slice corresponding to the first data packet.

27. A communication device comprising a module or unit configured to perform the method described in any one of claims 1 to 14 or claims 15 to 26.

28. A communication device including a processor, A communication device wherein, when the processor invokes a computer program or instruction in memory, the method according to any one of claims 1 to 14 is executed, or the method according to any one of claims 15 to 26 is executed.

29. A communication device including a logic circuit and an interface, wherein the logic circuit is coupled to the interface; A communication device wherein the interface is configured to input data to be processed; the logic circuit processes the data to be processed according to the method of any one of claims 1 to 14 or claims 15 to 26 to obtain processed data; and the interface is configured to output the processed data.

30. A computer-readable storage medium configured to store instructions or computer programs, wherein when the instructions or computer programs are executed, the method described in any one of claims 1 to 14 or the method described in any one of claims 15 to 26 is performed.

31. A computer program product that includes instructions or computer programs, A computer program product wherein, when the instruction or the computer program is executed, the method described in any one of claims 1 to 14 is executed, or the method described in any one of claims 15 to 26 is executed.

32. A communication system comprising the communication device described in claim 27, the communication device described in claim 28, or the communication device described in claim 29.

33. A communication system including a first donor node and a first IAB node, A communication system in which the first donor node is configured to perform the method described in any one of claims 1 to 14, and the first IAB node is configured to perform the method described in any one of claims 15 to 26.

Images