Communication method and related apparatus
Patent Information
- Application Number
- MYPI2025005497
- Authority / Receiving Office
- MY · MY
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-05
- Filing Date
- 2024-03-11
- Publication Date
- 2024-09-17
AI Technical Summary
Under the IAB architecture, end-to-end slicing resource isolation cannot be achieved, resulting in the inability to ensure priority and reliable communication for high-priority services.
By transmitting the first information between IAB nodes and instructing the slicing of the backhaul wireless link control RLC channel, the slicing resource isolation from the transmitting end to the receiving end is realized, ensuring that high-priority services use specific slicing resources.
It realizes end-to-end slicing resource isolation under the IAB architecture, ensuring priority and reliable communication of high-priority services.
Smart Images

Figure PI2025005497_DRAWING_001 
Figure PI2025005497_DRAWING_002 
Figure PI2025005497_DRAWING_003
Abstract
Description
Communication method and related device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on March 17, 2023, with application number 202310309625.5 and application name “Communication Method and Related Device”. This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 5, 2023, with application number 202311140366.4 and application name “Communication Method and Related Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method and related devices. Background Art
[0003] Compared to the fourth-generation mobile communication system, the fifth-generation (5G) and future mobile communication systems impose even more stringent requirements on various network performance indicators. For example, 5G boasts a 1,000-fold increase in capacity compared to 4G, requiring wider coverage, ultra-high reliability, and ultra-low latency. Given the abundance of high-frequency carrier frequency resources, the use of high-frequency small cell networks is becoming increasingly popular in hotspots to meet the ultra-high capacity requirements of 5G. Due to the poor propagation characteristics of high-frequency carriers, severe attenuation due to obstruction, and limited coverage, a large number of small cells need to be deployed densely. However, providing fiber backhaul for these densely deployed small cells is costly and difficult to implement, necessitating the need for economical and convenient backhaul solutions. Furthermore, to meet the need for wide coverage, fiber deployment is challenging and expensive in remote areas, necessitating the design of flexible and convenient access and backhaul solutions. Integrated access and backhaul (IAB) technology provides a solution to the above two problems: its access link (access link) and backhaul link (backhaul link, BL) both use wireless transmission solutions, reducing the deployment of optical fibers.
[0004] In an IAB network, a relay node (RN), also known as an IAB node, provides wireless access services and forwards service data for user equipment (UE). The UE's service data is transmitted by the IAB node via a wireless backhaul link to an IAB donor, also known as a donor node or donor gNodeB (DgNB). An IAB node consists of a mobile termination (MT) and a distributed unit (DU). When facing its parent node, the IAB node acts as a terminal device, i.e., the MT. When facing its child node (which may be another IAB node or a UE), it is considered a network device, i.e., the DU. A donor base station (DgNB) can be an access network element with full base station functionality, or an access network element with a separate centralized unit (CU) and distributed unit (DU). The host base station is connected to the core network element (e.g., connected to the 5G core network) serving the UE and provides wireless backhaul functionality for the IAB node.
[0005] Slicing is a mandatory feature of end-to-end UE protocol data unit (PDU) sessions. It is impossible to achieve end-to-end slice resource isolation under the IAB architecture, and thus it is impossible to ensure priority and reliable communication of high-priority services.
[0006] Summary of the Invention
[0007] The embodiments of the present application provide a communication method and related devices that can achieve end-to-end slice resource isolation under the IAB architecture, thereby ensuring priority and reliable communication of high-priority services.
[0008] In a first aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method includes:
[0009] The first host node generates first information, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to a first access and backhaul integrated IAB node.
[0010] The first host node sends first information to the first IAB node.
[0011] In an embodiment of the present application, a communication method is provided, in which a first host node generates first information and sends the first information to a first integrated access and backhaul (IAB) node, where the first information is used to indicate a slice corresponding to a first backhaul radio link control (RLC) channel corresponding to the first IAB node. It is understandable that after receiving the first information, the first IAB node will establish a first backhaul RLC channel according to 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, the slice resource isolation from the transmitting end to the receiving end corresponding to the first backhaul RLC channel can be achieved, thereby achieving end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of the high-priority service.
[0012] In a possible implementation, the first information includes one or more slice identifiers corresponding to the first return RLC channel.
[0013] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, the first information includes one or more slice identifiers corresponding to the first return RLC channel. The first information can indicate the slice corresponding to the first return RLC channel through the slice identifiers it contains, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel.
[0014] In a possible implementation, the first information is further used to indicate that resources used by the first backhaul RLC channel are reserved resources, where 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.
[0015] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, the first information is also used to indicate that the resources used by the first backhaul RLC channel are reserved resources, and the reserved resources are a portion of the resources reserved for the first backhaul RLC channel by the air interface. The reserved portion of the resources can be priority resources (resources given priority to the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared by multiple backhaul RLC channels including but not limited to the first backhaul RLC channel), etc. The embodiment of the present application does not limit this. The first information in the embodiment of the present application realizes the isolation of slice resources from the sending end to the receiving end corresponding to the first backhaul RLC channel by instructing the first backhaul RLC channel to use the reserved resources.
[0016] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0017] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the first return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0018] In a possible implementation, before the first host node sends the first information to the first IAB node, the method further includes:
[0019] The first host node receives second information from the first node, where the second information is used to indicate that 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 host node.
[0020] In an embodiment of the present application, a possible specific implementation of a slice-based IAB backhaul configuration is provided, specifically, the first host node receives the second information from the first node, and the second information is used to indicate that the resources used by the protocol data unit (PDU) session corresponding to the first host node are reserved resources. It can be understood that in the scenario where the first node initiates a PDU session resource establishment request to the first host node, after the first host node receives the second information, it will establish a PDU session according to the reserved resources indicated by the second information. The second information in the embodiment of the present application realizes the isolation of slice resources from the sending end to the receiving end corresponding to the first backhaul RLC channel used for the PDU session by instructing the PDU session to use the reserved resources.
[0021] In a possible implementation, before the first host node sends the first information to the first IAB node, the method further includes:
[0022] The first host node receives third information from the first node, where the third information is used to indicate that the first IAB node is a node providing a business service of the first priority.
[0023] In an embodiment of the present application, a possible specific implementation of slice-based IAB backhaul configuration is provided, specifically, a first host node receives third information from a first node, the third information being used to indicate that the first IAB node is a node providing a first-priority service, for example, a node providing a high-priority service such as public safety, etc. It is understandable that in the scenario where the first IAB node initially registers with the network, the first node initiates a UE context establishment request containing the third information to the first host node. After the first host node receives the third information, it can determine that the first IAB node is a node providing a high-priority service based on the indication of the third information, thereby instructing the first IAB node to establish a corresponding first backhaul RLC channel according to the slice indicated by the first information through the first information, thereby achieving slice resource isolation from the sender to the receiver corresponding to the first backhaul RLC channel. The third information in the embodiment of the present application achieves slice resource isolation from the sender to the receiver corresponding to the first backhaul RLC channel corresponding to the first IAB node by indicating that the first IAB node is a node providing a first-priority service.
[0024] In one possible implementation, the method further includes:
[0025] The first host node receives fourth information from the first IAB node, where the fourth information is used to indicate that the first IAB node is a node that provides a business service of the first priority.
[0026] In an embodiment of the present application, a possible specific implementation of a slice-based IAB backhaul configuration is provided, specifically, the first host node receives fourth information from the first IAB node, and the fourth information is used to indicate that the first IAB node is a node providing a first-priority service. For example, it can be a node providing high-priority service such as public safety, etc. It can be understood that in the scenario where the first IAB node initially registers with the network, the first IAB node sends the fourth information to the first host node. After the first host node receives the fourth information, it can determine that the first IAB node is a node providing a high-priority service based on the indication of the fourth information. Thus, the first information instructs the first IAB node to establish a corresponding first backhaul RLC channel according to the slice indicated by the first information, thereby achieving slice resource isolation from the sending end to the receiving end corresponding to the first backhaul RLC channel. The fourth information in the embodiment of the present application achieves slice resource isolation from the sending end to the receiving end corresponding to the first backhaul RLC channel corresponding to the first IAB node by indicating that the first IAB node is a node providing a first-priority service.
[0027] In one possible implementation, the method further includes:
[0028] The first donor node determines, based on the third information, that the first backhaul RLC channel needs to use reserved resources.
[0029] In an embodiment of the present application, a possible specific implementation method of a slice-based IAB backhaul configuration is provided. Specifically, after receiving the third information from the first node, the first host node can determine that the first IAB node is a node providing high-priority business services based on the indication of the third information, thereby determining that the first backhaul RLC channel needs to use reserved resources, and instruct the first IAB node through the first information to establish a corresponding first backhaul RLC channel according to the slice indicated by the first information, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the first backhaul RLC channel.
[0030] In a possible embodiment, the first information also includes a slice identifier corresponding to the first migration data, and the first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to the connection with the second host node, and the second host node is different from the first host node.
[0031] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node, and accordingly, the first IAB node and the host node transmit the first migration data after the connection is migrated. The first information also includes a slice identifier corresponding to the first migration data, which may specifically include one or more slice identifiers corresponding to the first migration data. The first information can indicate the slice corresponding to the return RLC channel used for the first migration data through the slice identifier corresponding to the first migration data contained therein, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the return RLC channel used for the first migration data, realizing end-to-end slice resource isolation under the IAB architecture, and ensuring priority and reliable communication of high-priority services.
[0032] In a possible implementation, the first information is further used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second donor node.
[0033] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node, the first host node will inform the second host node of the slice corresponding to the first return RLC channel in the topology, and the second host node will configure the slice corresponding to the second return RLC channel in its own topology based on the slice corresponding to the first return RLC channel, and feed back the slice corresponding to the second return RLC channel to the first host node. At this time, the first information sent by the first host node to the first IAB node can also be used to indicate the slice corresponding to the second return RLC channel. It can be understood that the slice corresponding to the second return RLC channel can be the same as or different from the slice corresponding to the first return RLC channel, and the embodiment of the present application does not limit this. It can be understood that after the first IAB node receives the first information, it will establish a second backhaul RLC channel according to the slice indicated by the first information to perform IAB cross-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, the slice resource isolation from the sending end to the receiving end corresponding to the second backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0034] Optionally, the first information includes one or more slice identifiers corresponding to the second return RLC channel.
[0035] Optionally, the first information is further used to indicate that resources used by the second backhaul RLC channel are reserved resources, where 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.
[0036] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0037] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the second return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0038] In a possible implementation, when the slice corresponding to the second backhaul RLC channel is different from the slice corresponding to the first backhaul RLC channel, the first information is further used to indicate a mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.
[0039] In a possible implementation, the mapping relationship includes:
[0040] The slice identifier corresponding to the first backhaul RLC channel and the slice identifier corresponding to the second backhaul RLC channel are the same or different.
[0041] In a possible implementation, the mapping relationship includes:
[0042] 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;
[0043] Alternatively, the slice service type SST corresponding to the first return RLC channel is different from the slice service type SST corresponding to the second return RLC channel, and the slice distinguisher SD corresponding to the first return RLC channel is the same as the slice distinguisher SD corresponding to the second return RLC channel.
[0044] In one possible implementation, the method further includes:
[0045] The first host node receives fifth information from the first IAB node, and the fifth information is used to indicate slice resource congestion.
[0046] In an embodiment of the present application, a possible specific implementation method for indicating slice resource congestion is provided, specifically, the first host node receives fifth information from the first IAB node, where the fifth information is used to indicate slice resource congestion. It is understandable that after receiving the fifth information, the first host node determines that the current slice resource is congested and performs flow control for different slice services to ensure the service quality of the slice service.
[0047] In a possible implementation, nodes in a first backhaul adaptation protocol BAP topology support the slice indicated by the first information, the first BAP topology is managed by a first host node, and the first IAB node belongs to the first BAP topology.
[0048] In an embodiment of the present application, a possible specific implementation of backhaul adaptation protocol (BAP) routing configuration is provided, specifically, nodes in a first BAP topology support slices indicated by first information, the first BAP topology includes a first host node and a first IAB node, and the first BAP topology is managed by the first host node. It is understood that when configuring BAP routing, the first host node needs to consider the slice types supported by each hop IAB node to ensure that each IAB node on the BAP path supports the target slice.
[0049] In a second aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method includes:
[0050] The first access and backhaul integrated IAB node receives first information from the first host node, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to the first IAB node.
[0051] The first IAB node establishes a first backhaul RLC channel according to the first information.
[0052] In an embodiment of the present application, a communication method is provided, in which a first IAB node receives first information from a first host node and establishes a first return RLC channel based on the first information, wherein the first information is used to indicate the slice corresponding to the first return channel corresponding to the first IAB node. It can be understood that after the first IAB node receives the first information, it will establish the first return RLC channel based on the slice indicated by the first information. Since the resources used by the first return RLC channel are the slice resources indicated by the first information, the slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel can be achieved, thereby achieving end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the return RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0053] In a possible implementation, the first information includes one or more slice identifiers corresponding to the first return RLC channel.
[0054] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, the first information includes one or more slice identifiers corresponding to the first return RLC channel. The first information can indicate the slice corresponding to the first return RLC channel through the slice identifiers it contains, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel.
[0055] In a possible implementation, the first information is further used to indicate that resources used by the first backhaul RLC channel are reserved resources, where 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.
[0056] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, the first information is also used to indicate that the resources used by the first backhaul RLC channel are reserved resources, and the reserved resources are a portion of the resources reserved for the first backhaul RLC channel by the air interface. The reserved portion of the resources can be priority resources (resources given priority to the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared by multiple backhaul RLC channels including but not limited to the first backhaul RLC channel), etc. The embodiment of the present application does not limit this. The first information in the embodiment of the present application realizes the isolation of slice resources from the sending end to the receiving end corresponding to the first backhaul RLC channel by instructing the first backhaul RLC channel to use the reserved resources.
[0057] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0058] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the first return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0059] In a possible implementation, before the first integrated access and backhaul IAB node receives the first information from the first host node, the method further includes:
[0060] The first IAB node sends fourth information to the first host node, where the fourth information is used to indicate that the first IAB node is a node that provides a business service of the first priority.
[0061] In an embodiment of the present application, a possible specific implementation of a slice-based IAB backhaul configuration is provided, specifically, the first IAB node sends fourth information to the first host node, and the fourth information is used to indicate that the first IAB node is a node providing a first-priority service. For example, it can be a node providing high-priority service such as public safety, etc. It can be understood that in the scenario where the first IAB node initially registers with the network, the first IAB node sends the fourth information to the first host node. After the first host node receives the fourth information, it can determine that the first IAB node is a node providing a high-priority service based on the indication of the fourth information, thereby instructing the first IAB node to establish a corresponding first backhaul RLC channel according to the slice indicated by the first information through the first information, thereby achieving slice resource isolation from the sending end to the receiving end corresponding to the first backhaul RLC channel. The fourth information in the embodiment of the present application achieves slice resource isolation from the sending end to the receiving end corresponding to the first backhaul RLC channel corresponding to the first IAB node by indicating that the first IAB node is a node providing a first-priority service.
[0062] In a possible embodiment, the first information also includes a slice identifier corresponding to the first migration data, and the first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to the connection with the second host node, and the second host node is different from the first host node.
[0063] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node, and accordingly, the first IAB node and the host node transmit the first migration data after the connection is migrated. The first information also includes a slice identifier corresponding to the first migration data, which may specifically include one or more slice identifiers corresponding to the first migration data. The first information can indicate the slice corresponding to the return RLC channel used for the first migration data through the slice identifier corresponding to the first migration data contained therein, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the return RLC channel used for the first migration data, realizing end-to-end slice resource isolation under the IAB architecture, and ensuring priority and reliable communication of high-priority services.
[0064] In a possible implementation, the first information is further used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second donor node.
[0065] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node, the first host node will inform the second host node of the slice corresponding to the first return RLC channel in the topology, and the second host node will configure the slice corresponding to the second return RLC channel in its own topology based on the slice corresponding to the first return RLC channel, and feed back the slice corresponding to the second return RLC channel to the first host node. At this time, the first information sent by the first host node to the first IAB node can also be used to indicate the slice corresponding to the second return RLC channel. It can be understood that the slice corresponding to the second return RLC channel can be the same as or different from the slice corresponding to the first return RLC channel, and the embodiment of the present application does not limit this. It can be understood that after the first IAB node receives the first information, it will establish a second backhaul RLC channel according to the slice indicated by the first information to perform IAB cross-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, the slice resource isolation from the sending end to the receiving end corresponding to the second backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0066] Optionally, the first information includes one or more slice identifiers corresponding to the second return RLC channel.
[0067] Optionally, the first information is further used to indicate that resources used by the second backhaul RLC channel are reserved resources, where 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.
[0068] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0069] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the second return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0070] In a possible implementation, when the slice corresponding to the second backhaul RLC channel is different from the slice corresponding to the first backhaul RLC channel, the first information is further used to indicate a mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.
[0071] In a possible implementation, the mapping relationship includes:
[0072] The slice identifier corresponding to the first backhaul RLC channel and the slice identifier corresponding to the second backhaul RLC channel are the same or different.
[0073] In a possible implementation, the mapping relationship includes:
[0074] 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;
[0075] Alternatively, the slice service type SST corresponding to the first return RLC channel is different from the slice service type SST corresponding to the second return RLC channel, and the slice distinguisher SD corresponding to the first return RLC channel is the same as the slice distinguisher SD corresponding to the second return RLC channel.
[0076] In one possible implementation, the method further includes:
[0077] The first IAB node sends fifth information to the first host node, where the fifth information is used to indicate slice resource congestion.
[0078] In an embodiment of the present application, a possible specific implementation method for indicating slice resource congestion is provided, specifically, the first IAB node sends fifth information to the first host node, where the fifth information is used to indicate slice resource congestion. It is understandable that after receiving the fifth information, the first host node determines that the current slice resource is congested and performs flow control for different slice services to ensure the service quality of the slice service.
[0079] In a possible implementation, nodes in a first backhaul adaptation protocol BAP topology support the slice indicated by the first information, the first BAP topology is managed by a first host node, and the first IAB node belongs to the first BAP topology.
[0080] In an embodiment of the present application, a possible specific implementation of BAP routing configuration is provided, specifically, nodes in a first BAP topology support slices indicated by first information, the first BAP topology includes a first host node and a first IAB node, and the first BAP topology is managed by the first host node. It is understood that when configuring BAP routing, the first host node needs to consider the slice types supported by each hop IAB node to ensure that each IAB node on the BAP path supports the target slice.
[0081] In one possible implementation, the method further includes:
[0082] The first IAB node transmits the first data packet to the second IAB node according to the slice identifier corresponding to the first data packet. The second IAB node is an IAB node that supports the slice corresponding to the first data packet.
[0083] In an embodiment of the present application, a possible specific implementation method of BAP rerouting is provided, specifically, when the next-hop backhaul link is unavailable, the first IAB node can select the next-hop IAB node that supports the target slice according to the slice identifier corresponding to the first data packet to perform rerouting, and 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.
[0084] In a third aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method includes:
[0085] The first host node generates first information, and the first information is used to indicate that the resources used by the first backhaul radio link control RLC channel are reserved resources, and the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes a first backhaul RLC channel, and the first backhaul RLC channel is the backhaul RLC channel corresponding to the first access and backhaul integrated IAB node.
[0086] The first host node sends first information to the first IAB node.
[0087] In an embodiment of the present application, a communication method is provided, in which a first host node generates first information and sends the first information to a first IAB node, wherein the first information is used to indicate that the resources used by the first backhaul RLC channel are reserved resources, and the reserved resources are a portion of the resources reserved for the first backhaul RLC channel by the air interface. The reserved portion of the resources can be priority resources (resources given priority to the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared by multiple backhaul RLC channels including but not limited to the first backhaul RLC channel), etc. The embodiment of the present application does not limit this. The first information in the embodiment of the present application instructs the first backhaul RLC channel to use reserved resources, thereby achieving slice resource isolation from the sending end to the receiving end corresponding to the first backhaul RLC channel, and achieving end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of the high-priority service.
[0088] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0089] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the first return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0090] In a fourth aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method includes:
[0091] The first access and backhaul integrated IAB node receives first information from the first host node, where the first information is used to indicate that resources used by the first backhaul RLC channel are reserved resources, where the reserved resources include resources reserved for at least one backhaul RLC channel, where the at least one backhaul RLC channel includes a first backhaul RLC channel, and where the first backhaul RLC channel is the backhaul RLC channel corresponding to the first IAB node.
[0092] The first IAB node establishes a first backhaul RLC channel according to the first information.
[0093] In an embodiment of the present application, a communication method is provided, in which a first IAB node receives first information from a first host node and establishes a first backhaul RLC channel based on the first information, wherein the first information is further used to indicate that the resources used by the first backhaul RLC channel are reserved resources, and the reserved resources are a portion of the resources reserved for the first backhaul RLC channel by the air interface. The reserved portion of the resources can be priority resources (resources given priority to the first backhaul RLC channel), dedicated resources (resources used only by the first backhaul RLC channel), shared resources (resources shared by multiple backhaul RLC channels including but not limited to the first backhaul RLC channel), etc., and the embodiment of the present application does not limit this. The first information in the embodiment of the present application instructs the first backhaul RLC channel to use reserved resources, thereby achieving slice resource isolation from the sending end to the receiving end corresponding to the first backhaul RLC channel, and achieving end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of the high-priority service.
[0094] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0095] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the first return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0096] In a fifth aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method includes:
[0097] The first host node generates first information, the first information includes a slice identifier corresponding to the first migration data, the first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to the connection with the second host node, and the second host node is different from the first host node.
[0098] The first host node sends first information to the first IAB node.
[0099] In an embodiment of the present application, a communication method is provided, in which a first host node generates first information and sends the first information to a first IAB node, where the first information includes a slice identifier corresponding to the first migration data. It can be understood that in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node. Accordingly, the first IAB node transmits the first migration data after the connection with the host node is migrated. The first information also includes a slice identifier corresponding to the first migration data, which may specifically include one or more slice identifiers corresponding to the first migration data. The first information can indicate the slice corresponding to the return RLC channel used for the first migration data through the slice identifier corresponding to the first migration data contained therein, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the return RLC channel used for the first migration data, realizing end-to-end slice resource isolation under the IAB architecture, and ensuring priority and reliable communication of high-priority services.
[0100] In a possible implementation, the first information is further used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second donor node.
[0101] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node, the first host node will inform the second host node of the slice corresponding to the first return RLC channel in the topology, and the second host node will configure the slice corresponding to the second return RLC channel in its own topology based on the slice corresponding to the first return RLC channel, and feed back the slice corresponding to the second return RLC channel to the first host node. At this time, the first information sent by the first host node to the first IAB node can also be used to indicate the slice corresponding to the second return RLC channel. It can be understood that the slice corresponding to the second return RLC channel can be the same as or different from the slice corresponding to the first return RLC channel, and the embodiment of the present application does not limit this. It can be understood that after the first IAB node receives the first information, it will establish a second backhaul RLC channel according to the slice indicated by the first information to perform IAB cross-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, the slice resource isolation from the sending end to the receiving end corresponding to the second backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0102] Optionally, the first information includes one or more slice identifiers corresponding to the second return RLC channel.
[0103] Optionally, the first information is further used to indicate that resources used by the second backhaul RLC channel are reserved resources, where 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.
[0104] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0105] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the second return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0106] In a sixth aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method includes:
[0107] The first access and backhaul integrated IAB node receives first information from the first host node. The first information includes a slice identifier corresponding to the first migration data. The first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to the connection with the second host node. The second host node is different from the first host node.
[0108] The first IAB node transmits first migration data according to the first information.
[0109] In an embodiment of the present application, a communication method is provided, in which a first IAB node receives first information from a first host node and transmits first migration data based on the first information, wherein the first information includes a slice identifier corresponding to the first migration data. It can be understood that in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node, and accordingly, the first IAB node transmits the first migration data after the connection with the host node is migrated, and the first information also includes a slice identifier corresponding to the first migration data, which can specifically include one or more slice identifiers corresponding to the first migration data. The first information can indicate the slice corresponding to the return RLC channel used by the first migration data through the slice identifier corresponding to the first migration data contained therein, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the return RLC channel used by the first migration data, realizing end-to-end slice resource isolation under the IAB architecture, and ensuring priority and reliable communication of high-priority services.
[0110] In a possible implementation, the first information is further used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second donor node.
[0111] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, in the scenario of IAB cross-topology data migration, for example, the connection between the first IAB node and the first host node is migrated to the connection with the second host node, the first host node will inform the second host node of the slice corresponding to the first return RLC channel in the topology, and the second host node will configure the slice corresponding to the second return RLC channel in its own topology based on the slice corresponding to the first return RLC channel, and feed back the slice corresponding to the second return RLC channel to the first host node. At this time, the first information sent by the first host node to the first IAB node can also be used to indicate the slice corresponding to the second return RLC channel. It can be understood that the slice corresponding to the second return RLC channel can be the same as or different from the slice corresponding to the first return RLC channel, and the embodiment of the present application does not limit this. It can be understood that after the first IAB node receives the first information, it will establish a second backhaul RLC channel according to the slice indicated by the first information to perform IAB cross-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, the slice resource isolation from the sending end to the receiving end corresponding to the second backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0112] Optionally, the first information includes one or more slice identifiers corresponding to the second return RLC channel.
[0113] Optionally, the first information is further used to indicate that resources used by the second backhaul RLC channel are reserved resources, where 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.
[0114] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0115] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the second return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0116] In a seventh aspect, an embodiment of the present application provides a communication device, which includes a module or unit for executing any method of the first aspect.
[0117] In one possible design, the apparatus includes:
[0118] The processing unit is used to generate first information, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to a first access and backhaul integrated IAB node.
[0119] The communication unit is configured to send first information to the first IAB node.
[0120] The methods performed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned first aspect, and will not be repeated here.
[0121] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0122] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0123] Regarding the technical effects brought about by the seventh aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the first aspect and the corresponding implementation method.
[0124] In an eighth aspect, an embodiment of the present application provides a communication device, which includes a module or unit for executing any method of the second aspect.
[0125] In one possible design, the apparatus includes:
[0126] A communication unit is used to receive first information from a first host node, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to the communication device.
[0127] The processing unit is configured to establish a first backhaul RLC channel according to the first information.
[0128] The methods performed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned second aspect, and will not be repeated here.
[0129] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0130] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0131] Regarding the technical effects brought about by the eighth aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the second aspect and the corresponding implementation method.
[0132] In a ninth aspect, an embodiment of the present application provides a communication device comprising a module or unit for executing any method of the third aspect.
[0133] In one possible design, the apparatus includes:
[0134] A processing unit is used to generate first information, where the first information is used to indicate that resources used by the first backhaul radio link control RLC channel are reserved resources, where the reserved resources include resources reserved for at least one backhaul RLC channel, where the at least one backhaul RLC channel includes a first backhaul RLC channel, and where the first backhaul RLC channel is a backhaul RLC channel corresponding to the first access and backhaul integrated IAB node.
[0135] The communication unit is configured to send first information to the first IAB node.
[0136] The methods performed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned third aspect, and will not be repeated here.
[0137] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0138] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0139] Regarding the technical effects brought about by the ninth aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the third aspect and the corresponding implementation method.
[0140] In a tenth aspect, an embodiment of the present application provides a communication device, which includes a module or unit for executing any method of the fourth aspect.
[0141] In one possible design, the apparatus includes:
[0142] A communication unit is used to receive first information from a first host node, where the first information is used to indicate that resources used by a first return RLC channel are reserved resources, where the reserved resources include resources reserved for at least one return RLC channel, where the at least one return RLC channel includes a first return RLC channel, and where the first return RLC channel is a return RLC channel corresponding to the communication device.
[0143] The processing unit is configured to establish a first backhaul RLC channel according to the first information.
[0144] The methods performed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned fourth aspect, and will not be repeated here.
[0145] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0146] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0147] Regarding the technical effects brought about by the tenth aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the fourth aspect and the corresponding implementation method.
[0148] In the eleventh aspect, an embodiment of the present application provides a communication device, which includes a module or unit for executing any method of the fifth aspect.
[0149] In one possible design, the apparatus includes:
[0150] A processing unit is used to generate first information, the first information includes a slice identifier corresponding to first migration data, the first migration data includes data transmitted after the connection between the first IAB node and the communication device is migrated to the connection with the second host node, and the second host node is different from the communication device.
[0151] The communication unit is configured to send first information to the first IAB node.
[0152] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned fifth aspect, which will not be repeated here.
[0153] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0154] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0155] Regarding the technical effects brought about by the eleventh aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the fifth aspect and the corresponding implementation method.
[0156] In the twelfth aspect, an embodiment of the present application provides a communication device, which includes a module or unit for executing any method as described in the sixth aspect.
[0157] In one possible design, the apparatus includes:
[0158] A communication unit is used to receive first information from a first host node, where the first information includes a slice identifier corresponding to first migration data, and the first migration data includes data transmitted after the connection between the communication device and the first host node is migrated to the connection with the second host node, where the second host node is different from the first host node.
[0159] The processing unit is configured to transmit first migration data according to the first information.
[0160] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned sixth aspect, which will not be repeated here.
[0161] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0162] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0163] Regarding the technical effects brought about by the twelfth aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the sixth aspect and the corresponding implementation method.
[0164] In a thirteenth aspect, an embodiment of the present application provides a communication device, comprising a processor. The processor is coupled to a memory and can be configured to execute instructions in the memory to implement the method of any one of the first to sixth aspects and any possible implementation methods described above. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.
[0165] In a fourteenth aspect, an embodiment of the present application provides a communication device, comprising: a logic circuit and a communication interface. The communication interface is configured to receive or send information; and the logic circuit is configured to receive or send information via the communication interface, so that the communication device executes the method of any of aspects 1 to 6 above and any possible implementation thereof.
[0166] In the fifteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program (also referred to as code, or instructions); when the computer program runs on a computer, the method of any one of the above-mentioned aspects from the first to the sixth aspect and any possible implementation method is implemented.
[0167] In the sixteenth aspect, an embodiment of the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions); when the computer program is run, it enables the computer to execute any one of the above-mentioned aspects from the first to the sixth aspect and any possible implementation method.
[0168] In a seventeenth aspect, an embodiment of the present application provides a chip, comprising a processor configured to execute instructions. When the processor executes the instructions, the chip performs the method of any one of aspects one to six, and any possible implementation thereof. Optionally, the chip further comprises a communication interface configured to receive or transmit signals.
[0169] In the eighteenth aspect, an embodiment of the present application provides a communication system, which includes at least one communication device as described in aspects seven to twelfth, or the communication device of aspect thirteen, or the communication device of aspect fourteen, or the chip of aspect seventeen.
[0170] In the nineteenth aspect, an embodiment of the present application provides a communication system, the communication system including a first host node and a first IAB node, the first host node is used to execute the method of the above-mentioned first aspect or third aspect or fifth aspect and any possible implementation method, and the first IAB node is used to execute the above-mentioned second aspect or fourth aspect or sixth aspect and any possible implementation method.
[0171] In addition, in the process of executing any one of the first to sixth aspects and any possible implementation methods of the above-mentioned method, the process of sending information and / or receiving information in the above-mentioned method can be understood as the process of the processor outputting information and / or the process of the processor receiving input information. When outputting information, the processor can output the information to the transceiver (or communication interface, or sending module) so that it can be transmitted by the transceiver. After the information is output by the processor, it may also need to undergo other processing before it reaches the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface, or sending module) receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before it is input into the processor.
[0172] Based on the above principles, for example, the sending of information mentioned in the above method can be understood as the processor outputting information. For another example, the receiving of information can be understood as the processor receiving input information.
[0173] Optionally, for the operations such as transmission, sending and receiving involved in the processor, if there is no special explanation, or if they do not conflict with their actual functions or internal logic in the relevant description, they can be more generally understood as processor output, reception, input and other operations.
[0174] Optionally, in the process of executing the method of any aspect of the first to sixth aspects and any possible implementation method, the processor may be a processor specifically used to execute these methods, or a processor that executes these methods by executing computer instructions in a memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be separately provided on different chips. The embodiment of the present application does not limit the type of memory and the configuration of the memory and the processor.
[0175] In a possible implementation, the at least one memory is located outside the device.
[0176] In yet another possible implementation, the at least one memory is located within the device.
[0177] In another possible implementation, part of the at least one memory is located inside the device, and another part of the memory is located outside the device.
[0178] In this application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.
[0179] In an embodiment of the present application, by indicating the slice corresponding to the first return RLC channel corresponding to the first IAB node through the first information, the slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture, ensuring priority and reliable communication of high-priority services. BRIEF DESCRIPTION OF THE DRAWINGS
[0180] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0181] FIG1 is a schematic diagram of the structure of an IAB system provided in an embodiment of the present application;
[0182] FIG2 is a schematic diagram of the structure of an IAB node provided in an embodiment of the present application;
[0183] FIG3 is a schematic diagram of the structure of an IAB network provided in an embodiment of the present application;
[0184] FIG4 is an example of an IAB network architecture diagram provided in an embodiment of the present application;
[0185] FIG5 is an example of a BAP topology of an IAB network provided in an embodiment of the present application;
[0186] FIG6 is a flow chart of a transport migration management process provided in an embodiment of the present application;
[0187] FIG7A is a schematic diagram of a mapping provided in an embodiment of the present application;
[0188] FIG7B is a schematic diagram of a mapping provided in an embodiment of the present application;
[0189] FIG8 is a flow chart of a communication method provided in an embodiment of the present application;
[0190] FIG9 is a flow chart of a communication method provided in an embodiment of the present application;
[0191] FIG10 is a flow chart of a communication method provided in an embodiment of the present application;
[0192] FIG11A is a schematic diagram of a cell provided in an embodiment of the present application;
[0193] FIG11B is a schematic diagram of a cell provided in an embodiment of the present application;
[0194] FIG12 is a flow chart of a communication method provided in an embodiment of the present application;
[0195] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0196] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0197] FIG15 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0198] FIG16 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION
[0199] In order to make the purpose, technical solutions and advantages of this application clearer, the embodiments of this application will be described below in conjunction with the drawings in the embodiments of this application.
[0200] The terms "first" and "second" in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.
[0201] The “embodiment” mentioned herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It can be understood explicitly and implicitly by those skilled in the art that in the various embodiments of the present application, unless otherwise specified and there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship.
[0202] It should be understood that in the present application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0203] It should be noted that in this application, "indication" can include direct indication, indirect indication, explicit indication, and implicit indication. When describing that a certain indication information is used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.
[0204] In this application, the information indicated by the indication information is referred to as the information to be indicated. In specific implementations, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, where the other information is associated with the information to be indicated. Alternatively, only a portion of the information to be indicated can be indicated, while the rest of the information to be indicated is known or agreed upon in advance. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-specified) order of the various information, thereby reducing indication overhead to a certain extent. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be pre-defined, for example, according to a protocol, or can be configured by the transmitting device sending configuration information to the receiving device.
[0205] It should be noted that in this application, "send" can be understood as "output" and "receive" can be understood as "input". "Send information to A", where "to A" only indicates the direction of information transmission, A is the destination, and does not limit "sending information to A" to direct transmission on the air interface. "Sending information to A" includes sending information directly to A, and also includes sending information indirectly to A through a transmitter, so "sending information to A" can also be understood as "outputting information to A". Similarly, "receiving information from A" indicates that the source of the information is A, including receiving information directly from A, and also including receiving information indirectly from A through a receiver, so "receiving information from A" can also be understood as "inputting information from A".
[0206] Before introducing the present application, some of the terms used in the embodiments of the present application are briefly explained to facilitate understanding by those skilled in the art.
[0207] 1) Terminal side device is a device that provides voice and / or data connectivity to users. In the embodiments of the present application, the terminal side device may be referred to as user equipment (UE), terminal device, terminal, mobile station (MS), mobile terminal (MT), etc. For example, the terminal side device may include a handheld device with a wireless connection function, or a communication device connected to a wireless modem. The terminal side device can communicate with the core network via the radio access network (RAN) and exchange voice and / or data with the RAN.
[0208] Some examples of terminal-side devices include: mobile stations (MS), subscriber units, cellular phones, smart phones, wireless data cards, personal digital assistants (PDAs), computers, tablet computers, wireless modems, handsets, laptop computers, machine type communication (MTC) terminals, wearable devices, and vehicle-mounted terminal devices. Terminal-side devices also include restricted devices, such as devices with low power consumption, limited storage capacity, or limited computing power. Terminal-side devices also include information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners.
[0209] The functions of the terminal-side device can be implemented by hardware components inside the terminal device, and the above-mentioned hardware components can be a processor and / or a programmable chip inside the above-mentioned terminal device. Optionally, the chip can be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The above-mentioned PLD can be any one of a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), and a system on a chip (SOC), or any combination thereof.
[0210] 2) Donor gNodeB, also known as the donor node, can access the core network through the donor node. In other words, the donor base station is a device in the communication system that connects the terminal side device to the core network. The donor base station is generally connected to the core network through a wired link (such as an optical fiber cable). The donor base station can be responsible for receiving data from the core network and forwarding it to the wireless backhaul device (such as an IAB node), or receiving data from the wireless backhaul device and forwarding it to the core network. The donor base station can generally be connected to the network via a wired connection.
[0211] As an example, the donor base station may include a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or home Node B, HNB), a base band unit (BBU), etc., and may also include an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in an evolved LTE system (LTE-Advanced, LTE-A), or may also include a next generation node B (gNB) in a fifth generation mobile communication technology (5G) new radio (NR) system. As another example, the donor base station may include a centralized 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 the F1 interface, which may further include a control plane interface (F1-C) and a user plane interface (F1-U). The donor-CU and the core network are connected via a next-generation (NG) interface. A gNB-CU or donor-CU may exist with a separate user plane (UP) (referred to herein as CU-UP) and control plane (CP) (referred to herein as CU-CP). Specifically, a gNB-CU or donor-CU consists of a CU-CP and a CU-UP. A gNB-CU may include one gNB-CU-CP and at least one gNB-CU-UP. Alternatively, a donor-CU may include one donor-CU-CP and at least one donor-CU-UP.
[0212] 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 using an ASIC or a programmable logic device (PLD). The PLD may be any one of a CPLD, an FPGA, a GAL, and a SOC, or any combination thereof.
[0213] This application provides a communication method, which is applied to the field of communication technology, such as communication in an IAB network. In order to more clearly describe the solution of this application, some knowledge related to IAB is first introduced below.
[0214] In an IAB network, an IAB node can establish a wireless backhaul link with one or more upper-level nodes and access the core network through the upper-level node. The upper-level node can perform certain control on the relay node through various signaling (for example, data scheduling, timing modulation, power control, etc.). In addition, the relay node can establish an access link with one or more lower-level nodes and provide access services for one or more lower-level nodes. The upper-level node of the relay node can be a base station or another relay node. The lower-level node of the relay node can be a terminal or another relay node. In some cases, the upper-level node of an IAB node can also be referred to as its upstream node or parent node, and the lower-level node of the IAB node can also be referred to as its downstream node or child node.
[0215] Please refer to FIG1 , which is a schematic structural diagram of an IAB system provided in an embodiment of the present application.
[0216] As shown in Figure 1, an IAB node provides wireless access and wireless backhaul for UEs. An IAB donor node provides wireless backhaul functionality to the IAB node and provides an interface between the UE and the core network. The IAB node connects to the IAB donor node via a wireless backhaul link, connecting the UE served by the IAB node to the core network.
[0217] Please refer to FIG. 2 , which is a schematic diagram of the structure of an IAB node provided in an embodiment of the present application.
[0218] As shown in Figure 2, the IAB node in NR can be divided into two parts: the Mobile Equipment Unit (MT) and the User Equipment Unit (DU). The MT can also be understood as a component similar to a UE. In an IAB node, the MT is referred to as a function residing on the IAB node. Since the MT functions similarly to a regular UE, it can be understood that the MT is used for communication between the IAB node and its upper-level nodes. The DU, in contrast to the CU function of network equipment, is used for communication between the IAB node and its lower-level nodes. It should be understood that the upper-level node can be a base station or other IAB node, and the lower-level node can be a UE or other IAB node.
[0219] The communication method provided in the embodiments of the present application can be applied to various communication systems including relay nodes, such as NR systems, LTE systems, LTE-A systems, worldwide interoperability for microwave access (WiMAX), or wireless local area networks (WLAN). 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 and reception points (rTRPs), and the upper node of the relay node may be a network device (including a DU of a network device, or including a CU of a network device, etc.).
[0220] Please refer to FIG3 , which is a schematic diagram of the structure of an IAB network provided in an embodiment of the present application.
[0221] As shown in Figure 3, the IAB network includes multiple UEs and multiple IAB nodes. Figure 3 takes two UEs and five IAB nodes as an example. Among them, the two UEs are UE1 and UE2, and the five IAB nodes are IAB nodes 1 to IAB nodes 5. It should be understood that the thick line in Figure 3 indicates the access link, and the thin line indicates the backhaul link. Among them, UE2 can be connected to the host base station via IAB node 5, IAB node 2, and IAB node 1. UE2 can also be connected to the host base station via IAB node 4, IAB node 2, and IAB node 1. Alternatively, UE2 can also be connected to the host base station via IAB node 4, IAB node 3, and IAB node 1. UE1 can be connected to the host base station via IAB node 4, IAB node 3, and IAB node 1. UE1 can be connected to the host base station via IAB node 4, IAB node 2, and IAB node 1.
[0222] It should be noted that the communication system shown in Figure 3 is only an example and does not limit the application scenarios applicable to the embodiments of the present application. It should be understood that the use of IAB nodes in the embodiments of the present application is only for descriptive purposes and does not mean that the solution of the embodiments of the present application is only used in NR scenarios. In the embodiments of the present application, IAB nodes can generally refer to any node or device with a relay function. The use of IAB nodes and relay nodes in the implementation of this application should be understood to have the same meaning.
[0223] In an IAB network, an IAB node is connected to the core network via an IAB host node. For example, in a standalone (SA) 5G architecture, an IAB node is connected to the 5G core network (5GC / 5GCN) via an IAB host node. For another example, in a dual connectivity (DC) or multi-connectivity (MC) 5G architecture (e.g., non-standalone, NSA scenarios), on the primary path, an IAB node can be connected to the evolved packet core (EPC) via an evolved NodeB (eNB), or to the 5G core network via an IAB host.
[0224] In the IAB network, a transmission path between the UE and the IAB host may include one or more IAB nodes. Each IAB node needs to maintain a wireless backhaul link towards the parent node, and also needs to maintain a wireless link with the child node. If the child node of the IAB node is a UE, there is a wireless access link between the IAB node and its child node (i.e., the UE). If the child node of the IAB node is another IAB node, there is a wireless backhaul link between the IAB node and its child node (i.e., the other IAB node). For example, referring to Figure 3, in the path "UE1→IAB node 4→IAB node 3→IAB node 1→IAB host", UE1 accesses IAB node 4 through a wireless access link, IAB node 4 is connected to IAB node 3 through a wireless backhaul link, IAB node 3 is connected to IAB node 1 through a wireless backhaul link, and IAB node 1 is connected to the IAB host node through a wireless backhaul link.
[0225] In the embodiment of the present application, the access IAB node refers to the IAB node accessed by the UE, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services for the UE or IAB node. For example, referring to Figure 3, in the path "UE1→IAB node 4→IAB node 3→IAB node 1→IAB host", IAB node 4 is the access IAB node, and IAB node 3 and IAB node 1 are intermediate IAB nodes. It should be noted that an IAB node is an access IAB node for the UE accessing the IAB node; it is an intermediate IAB node for the UE accessing other IAB nodes. Therefore, whether an IAB node is an access IAB node or an intermediate IAB node is not fixed and can be determined according to the specific application scenario.
[0226] It should be noted that the communication system shown in Figure 3 is only an example and does not limit the application scenarios applicable to the embodiments of the present application. It should be understood that the use of the IAB node in the embodiments of the present application is only for descriptive purposes and does not mean that the solution of the embodiments of the present application is only used in new radio (NR) scenarios.
[0227] The communication method provided in this application is primarily applicable to IAB networks, including standalone (SA) and non-standalone (NSA) IAB networks. An IAB node consists of a mobile operator (MT) and a user-defined unit (DU). An IAB donor can be further divided into a DU and a user-defined unit (CU). The CU can also be divided into a CU-CP and a CU-UP.
[0228] Please refer to FIG4 , which is an example of an IAB network architecture diagram provided in an embodiment of the present application.
[0229] Figure 4 shows an example of an IAB node connected to an IAB donor via a wireless backhaul link. Figure 4 uses an example system consisting of one UE, two IAB nodes, and two IAB donors. The two IAB nodes are IAB node 1 and IAB node 2, each consisting of an MT and a DU. The two IAB donors are IAB donor 1 and IAB donor 2. Each IAB donor can be further divided into a DU and a CU, and the CU can be further divided into a CU-CP and a CU-UP. In Figure 4, the MT of IAB node 2 and the DU of IAB node 1, the MT of IAB node 1 and the DU of IAB donor 1, and the MT of IAB node 1 and the DU of IAB donor 2 all communicate through a wireless backhaul (BH) link; 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 and the CU of IAB donor 1 are connected through an Internet protocol (IP) network.
[0230] There is an F1 interface between the DU of each IAB node and the CU of the IAB host. The F1 interface may include two parts: a control plane and a user plane. The user plane part is maintained between the IAB-DU and the IAB donor CU-UP, while the control plane part 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. Of course, the F1 interface can also be called an F1* interface, and the embodiment of the present application does not limit the name of the interface. In this article, the interface is called the F1 interface as an example.
[0231] The F1 interface supports user plane protocols (F1-U / F1*-U) and control plane protocols (F1-C / F1*-C). The user plane protocols include one or more of the following protocol layers: the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U), the User Datagram Protocol (UDP), and the Internet Protocol (IP). The control plane protocols include one or more of the following protocol layers: the F1 Application Protocol (F1AP), the Stream Control Transport Protocol (SCTP), and the Internet Protocol (IP). The control plane of the F1 / F1* interface enables interface management, IAB-DU management, and UE context configuration between the IAB node and the IAB host. The user plane of the F1 / F1* interface enables user plane data transmission and downlink transmission status feedback between the IAB node and the IAB host.
[0232] When the IAB node operates in SA mode, the IAB node can be connected to one parent node or two parent nodes. The two parent nodes can be controlled by the same IAB donor or by different IAB donors. An F1 interface is established between the DU part of the IAB node and an IAB donor. The IAB donor can be connected to the 5G core network, which is the dotted line part in Figure 4. The IAB-donor-CU-CP is connected to the control plane network elements (such as access and mobility management functions) in the 5GC through the NG control plane interface (NG-C), and the IAB-donor-CU-UP is connected to the user plane network elements (such as user plane functions) in the 5GC through the NG user plane interface (NG-U).
[0233] When the IAB node works in NSA mode, the IAB-donor-CU-UP can be connected to the EPC (for example, connected to the serving gateway (SGW)) through the S1 user plane interface (S1-U), there is an LTE Uu air interface connection between the MeNB and the MT of the IAB node, there is an X2-C interface between the MeNB and the IAB-donor-CU-CP, and the MeNB is connected to the EPC through the S1 interface (including the S1 interface user plane and the S1 interface control plane), which is the dotted line part in Figure 4.
[0234] In another possible scenario, the MeNB in Figure 4 can be replaced with a 5G gNB. The LTE-Uu interface in Figure 4 is correspondingly replaced with the NR-Uu interface. The gNB can establish user plane and / or control plane interfaces with the 5GC. The gNB and IAB-donor provide dual connectivity services for the IAB node. The gNB can act as the primary base station or secondary base station for the IAB node.
[0235] The above is an example of an application scenario of the technical solution of the embodiment of the present application. It should be understood that the technical solution of the embodiment of the present application is not limited to application only in the network architecture shown in Figure 4.
[0236] The border nodes in the IAB network can be called border IAB nodes, or simply border nodes. The border nodes in the IAB network have the following characteristics: the IAB-donor-CU at which the DU of the border node terminates is different from the IAB-donor-CU at which the DU of at least one of its parent nodes terminates. Assuming that an IAB node in the IAB network has two parent nodes, the DU of the IAB node terminates at the CU of IAB-donor 1, the DU of one parent node of the IAB node terminates at the CU of IAB-donor 1, and the DU of the other parent node of the IAB node terminates at the CU of IAB-donor 2, then the IAB node is a border node (such as IAB-node2 in Figure 5). For example, in the IAB network, in order to enhance network robustness and achieve more refined load balancing and topology management, the border node can perform a partial migration process, that is, the MT of the border node (IAB-MT2 in Figure 5) switches from one parent node (IAB-node1 in Figure 5) to another parent node (IAB-node3 in Figure 5). The two parent nodes belong to topologies controlled by different host CUs, that is, IAB-node1 in Figure 5 belongs to the topology controlled by Donor-CU1 (the solid box in Figure 5), and IAB-node3 belongs to the topology controlled by Donor-CU2 (the dotted box in Figure 5). During the partial migration process, the RRC connection of IAB-MT2 is switched from CU1 to CU2, but the F1 connection of IAB-DU2 is still terminated in CU1 (as shown by the solid arrow in Figure 5) and is not migrated to CU2 along with IAB-MT2. It can be understood that the F1 connection of IAB node 4, the child node of IAB node 2, can also terminate in CU1 (as shown by the dotted arrow in Figure 5).
[0237] For example, the F1 interface of IAB node 2 is terminated at CU1, and IAB host 1 can be referred to as the F1-terminating IAB-donor of IAB node 2. CU2 has an RRC connection with IAB node 2, but the F1 connection of IAB node 2 is not terminated at CU2, and IAB host 2 can be referred to as the non-F1-terminating IAB-donor of IAB node 2.
[0238] After IAB node 2 switches from the CU1 topology to the CU2 topology, the 3rd Generation Partnership Project (3GPP) Release-17 standard (R17) introduces the IAB Transport Migration Management process to achieve data traffic migration from the CU1 topology to the CU2 topology. That is, CU1 can perform the IAB Transport Migration Management process to migrate the data traffic of IAB node 2 to CU2 through the Xn interface between CU1 and CU2. The IAB Transport Migration Management process is shown in Figure 6. The details are as follows:
[0239] Step S601: CU1 sends an IAB Transport Migration Management request message to CU2. Correspondingly, CU2 receives the IAB Transport Migration Management request message.
[0240] CU1 is the F1-terminating IAB-donor of IAB node 2, and CU2 is the non-F1-terminating IAB-donor of IAB node 2. The IAB transport migration management request message is used to request migration of data traffic of IAB node 2 to CU2.
[0241] Step S602: CU2 sends an IAB Transport Migration Management response message to CU1. Correspondingly, CU1 receives the IAB Transport Migration Management response message.
[0242] The IAB transport migration management response message is used to respond to the IAB transport migration management request message, so as to migrate the data traffic of the IAB node 2 to the CU2.
[0243] During the IAB Transport Migration Management process, CUs exchange Quality of Service (QoS) and integrated access and backhaul (BAP) configuration information to offload data traffic. The Release 17 standard specifies that this process is initiated by the F1-terminating IAB-donor (CU1 in Figure 5) to the non-F1-terminating IAB-donor (CU2 in Figure 5).
[0244] To support flexible and dense deployment of NR cells, the IAB network supports multi-hop backhaul, which involves routing between nodes. To simplify the IAB external interface and reduce the impact on the 5G network, 3GPP introduced a new IAB-specific protocol, the Backhaul Adaptation Protocol (BAP), which is responsible for the routing and bearer mapping functions of data packets in the IAB network.
[0245] The BAP routing function enables data to be transmitted from the sending end to the receiving end via a specified route. The sending end adds a BAP header (including the destination BAP address and BAP path ID) to the upper layer data, and the receiving end removes the BAP header and forwards the data to the upper layer.
[0246] The BAP return channel mapping function can realize the bearer mapping of data packets in the IAB network and meet the quality of service (QoS) requirements of data packets.
[0247] The IAB-donor-CU assigns a unique Layer 2 address (BAP address) to each IAB-node it controls, thus uniquely identifying each IAB-node in the network. In the case of multiple paths, each BAP address can be associated with multiple path IDs. Source nodes (IAB-donor-DU in the downlink (DL) direction, access IAB-node in the uplink (UL) direction) at their BAP layer add a BAP header to the data packets they are transmitting. The BAP header includes the BAP address and BAP path ID.
[0248] Each IAB-node is configured with routing tables for uplink (UL) and downlink (DL) (configured by the IAB-donor-CU), which contain the next-hop identifier for each BAP path ID. Separate routing tables are maintained for the DL and UL directions, with the IAB-DU using the DL table and the IAB-MT using the UL table. The routing table indicates to which child node (if DL) or parent node (if UL) the packet should be forwarded. When the access IAB-node receives a packet, it is forwarded to higher layers and processed in the same way as a normal DU processes an incoming F1-U or F1-C packet.
[0249] In addition to forwarding packets to child or parent nodes, the BAP protocol also performs mapping between ingress and egress BH RLC channels. Since BH RLC channels are used to transmit packets between IAB nodes (or between an IAB-donor-DU and an IAB-node), BH RLC channel mapping must meet the quality of service (QoS) requirements of the packets. Similar to the RLC channels between DUs and UEs, different BH RLC channels can be configured with different QoS parameters, such as priority and guaranteed bit rate. The IAB-node configures the mapping and uses a routing table to identify the next child / parent node and the egress BH RLC channel to which the packet should be forwarded.
[0250] The mapping between UE radio bearers and BH RLC channels supports 1:1 mapping and N:1 mapping. For details, please refer to Figures 7A and 7B, which are mapping diagrams provided in embodiments of the present application.
[0251] As shown in Figure 7A, UE radio bearers and BH RLC channels support 1:1 mapping, mapping each UE radio bearer to a separate BH RLC channel. For example, UE1 radio bearer DRB1 is mapped to a separate BH RLC channel 1, UE1 radio bearer DRB2 is mapped to a separate BH RLC channel 2, UE2 radio bearer DRB1 is mapped to a separate BH RLC channel 3, UE3 radio bearer DRB1 is mapped to a separate BH RLC channel 4, and UE3 radio bearer DRB2 is mapped to a separate BH RLC channel 5. This ensures fine QoS granularity at the UE radio bearer level. 1:1 mapping requires more BH RLC channels and more signaling overhead to establish and release BH RLC channels.
[0252] As shown in Figure 7B , the mapping of UE radio bearers to BH RLC channels supports N:1 mapping. Based on the bearer's QoS template and specific parameters, multiple UE radio bearers are multiplexed onto a single BH RLC channel. 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 fewer BH RLC channels and therefore requires less signaling overhead.
[0253] In addition, with the development of mobile communication technology, various new services and application scenarios are constantly emerging. These services have very different requirements for network functions, connection performance and security. If a single network is used to carry these services, it will be difficult to simultaneously meet the requirements of high bandwidth, low latency, high reliability, etc. In addition, building a new network for each service will bring huge costs. This requires 5G to be flexible and scalable while being able to meet different business needs. To this end, 5G provides users with customized network services through end-to-end network slicing. Specifically, through flexible allocation of network resources and on-demand networking, 5G virtualizes multiple logical subnets with different characteristics and isolation from each other on the same set of physical facilities to provide targeted services to users. Different logical subnets are identified and distinguished by "single network slice selection assistance information" (S-NSSAI). Each S-NSSAI may include but is not limited to the following:
[0254] Slice / service type (SST), which refers to the slice-specific features and service types;
[0255] Slice differentiator (SD), as a supplement to SST, can further distinguish multiple network slice instances that meet the same SST and is optional.
[0256] Currently, IAB requires support for UE access, and slicing is a mandatory feature for end-to-end UE PDU sessions. However, existing slicing only considers the isolation of slice resources and functional network elements between the access and core network sides, and does not consider the backhaul link in IAB scenarios. In other words, slicing cannot achieve end-to-end slice resource isolation under the IAB architecture, and thus cannot guarantee the priority and reliable communication of high-priority services.
[0257] In response to the above-mentioned technical problem that end-to-end slice resource isolation cannot be achieved under the IAB architecture, and thus priority and reliable communication of high-priority services cannot be guaranteed, a new communication method is provided in an embodiment of the present application. By designing a slice-based backhaul link configuration in the IAB scenario, end-to-end slice isolation can be achieved under the IAB architecture, thereby ensuring priority and reliable communication of high-priority services.
[0258] Please refer to Figure 8, which is a flow chart of a communication method provided in an embodiment of the present application. The communication method is applied to the field of communication technology, such as communication in an IAB network, and includes but is not limited to the following steps:
[0259] S801: A first host node generates first information.
[0260] S802: The first host node sends first information to the first IAB node. Correspondingly, the first IAB node receives the first information from the first host node.
[0261] It is understandable that the first host node in the embodiment of the present application is a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions, and the embodiment of the present application does not limit this. Optionally, the first host node can be the IAB host node in Figure 1 above, or the host base station in Figure 3 above, or the IAB donor 1 or IAB donor 2 in Figure 4 above, or CU1 or CU2 in Figures 5 and 6 above, etc., for executing the communication method in the embodiment of the present application to achieve end-to-end slice isolation under the IAB architecture and ensure priority and reliable communication of high-priority services.
[0262] It is understood that the first IAB node in the embodiment of the present application is a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions, and the embodiment of the present application does not limit this. Optionally, the first IAB node can be the IAB node in Figure 1 above, or the IAB node in Figure 2 above, or the IAB node 1, IAB node 2, IAB node 3, IAB node 4, IAB node 5 in Figure 3 above, or the IAB node 1, IAB node 2 in Figure 4 above, and so on, for participating in the execution of the communication method in the embodiment of the present application to achieve end-to-end slice isolation under the IAB architecture and ensure priority and reliable communication of high-priority services.
[0263] The first information is used to indicate the slice corresponding to the first backhaul RLC channel corresponding to the first IAB node.
[0264] It can be understood that after the first IAB node receives the first information, it will establish a first backhaul RLC channel according to 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, the slice resource isolation from the transmitting end to the receiving end corresponding to the first backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0265] Specifically, the first information indicating the slice corresponding to the first backhaul RLC channel corresponding to the first IAB node may be implemented in the following manner:
[0266] Method 1: The first information includes one or more slice identifiers corresponding to the first return RLC channel.
[0267] Exemplarily, the slice identifier included in the first information may be single network slice selection support information (S-NSSAI), which is used to identify and distinguish different slices. Each S-NSSAI may include but is not limited to the following:
[0268] SST, which refers to slice-specific features and service types;
[0269] SD, as a supplement to SST, can further distinguish multiple network slice instances that meet the same SST and can be used as optional content.
[0270] It can be understood that the first information can indicate the slice corresponding to the first return RLC channel through the slice identifier it contains, thereby realizing the slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel.
[0271] Mode 2: The first information indicates that the resources used by the first backhaul RLC channel are reserved resources.
[0272] The reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes a first backhaul RLC channel. The at least one backhaul RLC channel may be preset or specified by a protocol, or may be configured through signaling. Exemplarily, the reserved resources may be proportional resources reserved on an air interface (e.g., a Uu interface). For example, the reserved resources may be 5% of the air interface resources. When only 5% of the resources on the air interface are schedulable, the remaining 5% of the resources are the reserved resources. 95% of the resources that have been scheduled for use are non-scheduled resources.
[0273] Optionally, the reserved resources may be specific resources reserved on the air interface. For example, the reserved resources may be specific time-frequency positions or regions. Resources outside the specific time-frequency positions or regions are non-reserved resources.
[0274] The non-reserved resources can be scheduled according to the normal air interface resource scheduling algorithm. The reserved resources can only be scheduled for use by the at least one backhaul RLC channel.
[0275] The reserved resources may be priority resources (resources given priority to the first return RLC channel), dedicated resources (resources used only by the first return RLC channel), shared resources (resources shared by multiple return RLC channels including but not limited to the first return RLC channel), etc., and the embodiments of the present application do not impose any restrictions on this.
[0276] The reserved resources may be resources that can only be used by at least one backhaul RLC channel (the at least one backhaul RLC channel includes the first backhaul RLC channel) in the absence of non-reserved resources.
[0277] Optionally, the reserved resource may be a reserved resource carrying a slice identifier corresponding to the first return RLC channel, or a reserved resource without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0278] The first information in the embodiment of the present application instructs the first return RLC channel to use reserved resources, thereby achieving slice resource isolation from the transmitting end to the receiving end corresponding to the first return RLC channel.
[0279] It can be understood that the above two methods are only possible exemplary descriptions and should not be used to limit the embodiments of the present application. Embodiments obtained based on the supplement or reasonable deformation of the above exemplary methods all fall within the scope of protection of the embodiments of the present application.
[0280] In a possible embodiment, before the first host node sends the first information to the first IAB node, the first host node further receives second information from the first node.
[0281] The second information is used to indicate that 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 host node.
[0282] The first node in the embodiment of the present application is a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions, and the embodiment of the present application is not limited to this. Optionally, the first node can be an access and mobility management function (AMF), which is used to participate in the execution of the communication method in the embodiment of the present application to achieve end-to-end slice isolation under the IAB architecture and ensure priority and reliable communication of high-priority services.
[0283] It is understandable that in a scenario where the first node initiates a PDU session resource establishment request to the first host node, after receiving the second information, the first host node will establish a PDU session according to the reserved resources indicated by the second information.
[0284] The second information in the embodiment of the present application instructs the PDU session to use reserved resources, thereby achieving slice resource isolation from the transmitting end to the receiving end corresponding to the first return RLC channel used by the PDU session.
[0285] In a possible embodiment, before the first host node sends the first information to the first IAB node, the first host node further receives third information from the first node.
[0286] The third information is used to indicate that the first IAB node is a node that provides a first-priority business service. For example, it may be a node that provides a high-priority business service such as public safety, etc. This embodiment of the present application does not impose any restrictions on this.
[0287] In the embodiments of the present application, the first node is a device equipped with a processor / chip capable of executing computer-executable instructions. Alternatively, it may be a processor / chip capable of executing computer-executable instructions, and the embodiments of the present application are not limited thereto. Optionally, the first node may be an AMF, which is used to participate in executing the communication method in the embodiments of the present application to achieve end-to-end slice isolation under the IAB architecture, ensuring priority and reliable communication for high-priority services.
[0288] It can be understood that in the scenario where the first IAB node initially registers and joins the network, the first node initiates a UE context establishment request containing third information to the first host node. After receiving the third information, the first host node can determine that the first IAB node is a node providing high-priority business services based on the indication of the third information, thereby instructing the first IAB node through the first information to establish a corresponding first return RLC channel according to the slice indicated by the first information, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel.
[0289] The third information in the embodiment of the present application realizes the isolation of slice resources from the sending end to the receiving end corresponding to the first return RLC channel corresponding to the first IAB node by indicating that the first IAB node is a node providing first-priority business services.
[0290] Optionally, before the first host node sends the first information to the first IAB node, the first host node further receives fourth information from the first IAB node.
[0291] The fourth information is used to indicate that the first IAB node is a node that provides a first-priority business service. For example, it may be a node that provides a high-priority business service such as public safety, etc. This embodiment of the present application does not limit this.
[0292] It can be understood that in the scenario where the first IAB node initially registers and joins the network, the first IAB node sends the fourth information to the first host node. After receiving the fourth information, the first host node can determine that the first IAB node is a node providing high-priority business services based on the indication of the fourth information, thereby instructing the first IAB node through the first information to establish a corresponding first return RLC channel according to the slice indicated by the first information, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel.
[0293] The fourth information in the embodiment of the present application realizes the isolation of slice resources from the sending end to the receiving end corresponding to the first return RLC channel corresponding to the first IAB node by indicating that the first IAB node is a node providing first-priority business services.
[0294] Optionally, after receiving the third information from the first node, the first host node determines, based on the third information, that the first backhaul RLC channel needs to use reserved resources.
[0295] It can be understood that after receiving the third information from the first node, the first host node can determine that the first IAB node is a node providing high-priority business services based on the indication of the third information, thereby determining that the first return RLC channel needs to use reserved resources, and instruct the first IAB node through the first information to establish a corresponding first return RLC channel according to the slice indicated by the first information, thereby realizing slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel.
[0296] In a possible embodiment, the first information further includes a slice identifier corresponding to the first migration data.
[0297] The first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to a connection with a second host node, where the second host node is different from the first host node.
[0298] The second host node in the embodiment of the present application is a device equipped with a processor / chip that can be used to execute computer-executable instructions, and can also be a processor / chip that can be used to execute computer-executable instructions. The embodiment of the present application does not limit this. Optionally, the second host node can be IAB donor 2 in Figure 4 above, and the first host node is IAB donor 1 in Figure 4 above, or the second host node can also be CU2 in Figures 5 and 6 above, and the first host node is CU1 in Figures 5 and 6 above, and so on. The second host node is used to participate in the execution of the communication method in the embodiment of the present application to achieve end-to-end slice isolation under the IAB architecture and ensure priority and reliable communication of high-priority services.
[0299] It can be understood that in the scenario of IAB cross-topology data migration, the connection between the first IAB node and the first host node is migrated to the connection with the second host node. Accordingly, the first migration data is transmitted after the connection between the first IAB node and the host node is migrated. The first information also includes the slice identifier corresponding to the first migration data, which may specifically include one or more slice identifiers corresponding to the first migration data.
[0300] The first information in the embodiment of the present application can indicate the slice corresponding to the return RLC channel used by the first migration data through the slice identifier corresponding to the first migration data contained therein, thereby realizing the slice resource isolation from the sending end to the receiving end corresponding to the return RLC channel used by the first migration data, realizing end-to-end slice resource isolation under the IAB architecture, and ensuring priority and reliable communication of high-priority services.
[0301] In a possible embodiment, the first information is also used to indicate a slice corresponding to the second backhaul RLC channel.
[0302] The second backhaul RLC channel is the backhaul RLC channel corresponding to the second host node.
[0303] Optionally, the first information includes one or more slice identifiers corresponding to the second return RLC channel.
[0304] The specific description is as in the above-mentioned method 1: the first information includes one or more slice identifiers corresponding to the first return RLC channel, which will not be repeated here.
[0305] Optionally, the first information is further used to indicate that resources used by the second backhaul RLC channel are reserved resources.
[0306] The specific description is as in the above-mentioned method 2: the first information indicates that the resources used by the first backhaul RLC channel are reserved resources, which will not be described in detail here.
[0307] It is understandable that in the scenario of IAB cross-topology data migration, the connection between the first IAB node and the first host node is migrated to the connection with the second host node. The first host node will inform the second host node of the slice corresponding to the first return RLC channel in the topology. The second host node configures the slice corresponding to the second return RLC channel in its own topology based on the slice corresponding to the first return RLC channel, and feeds back the slice corresponding to the second return RLC channel to the first host node. At this time, the first information sent by the first host node to the first IAB node can also be used to indicate the slice corresponding to the second return RLC channel. It is understandable that the slice corresponding to the second return RLC channel can be the same as or different from the slice corresponding to the first return RLC channel, and the embodiment of the present application does not limit this.
[0308] It can be understood that after the first IAB node receives the first information, it will establish a second backhaul RLC channel according to the slice indicated by the first information to perform IAB cross-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, the slice resource isolation from the sending end to the receiving end corresponding to the second backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0309] In a possible embodiment, when the slice corresponding to the second backhaul RLC channel is different from the slice corresponding to the first backhaul RLC channel, the first information is also used to indicate the mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.
[0310] Optionally, the above mapping relationship includes:
[0311] The slice identifier corresponding to the first backhaul RLC channel and the slice identifier corresponding to the second backhaul RLC channel are the same or different.
[0312] Optionally, the above mapping relationship includes:
[0313] 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;
[0314] Alternatively, 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.
[0315] Through the embodiment of the present application, the first IAB node can establish a corresponding backhaul RLC channel according to the mapping relationship indicated by the first information, thereby achieving end-to-end resource isolation under the IAB architecture and ensuring priority and reliable communication of high-priority services.
[0316] It can be understood that the bearer mapping configuration of the backhaul RLC channel in the embodiment of the present application is for the case where the backhaul RLC channel carries only a single S-NSSAI.
[0317] The first host node configures a mapping relationship between the first backhaul RLC channel and the second backhaul RLC channel according to the slice information (S-NSSAI) corresponding to the backhaul RLC channel.
[0318] Optionally, the slice information can be S-NSSAI, or a slice group ID, i.e. (network slice AS group, NSAG) ID, or slice list information, which is not limited in the embodiment of the present application.
[0319] In a possible embodiment, for a case where a backhaul RLC channel carries multiple S-NSSAIs, the bearer mapping configuration of the backhaul RLC channel may be as follows:
[0320] The first host node configures a mapping relationship between the first backhaul RLC channel and the second backhaul RLC channel according to the slice information (S-NSSAI) corresponding to the backhaul RLC channel.
[0321] Optionally, the slice information may be S-NSSAI, a slice group ID, i.e., NSAG ID, or slice list information, which is not limited in the embodiment of the present application.
[0322] For a single IAB node, configuring the mapping relationship between the first backhaul RLC channel and the second backhaul RLC channel may include but is not limited to the following:
[0323] (1) The S-NSSAI lists corresponding to the first backhaul RLC channel and the second backhaul RLC channel are the same;
[0324] (2) The S-NSSAI lists corresponding to the first backhaul RLC channel and the second backhaul RLC channel are not exactly the same;
[0325] (3) In the S-NSSAI lists corresponding to the first backhaul RLC channel and the second backhaul RLC channel, the same S-NSSAI is the largest number;
[0326] (4) In the S-NSSAI lists corresponding to the first backhaul RLC channel and the second backhaul RLC channel, the same SST is the largest.
[0327] Through the bearer mapping configuration of the backhaul RLC channel in the embodiment of the present application, end-to-end resource isolation under the IAB architecture can be achieved, ensuring priority and reliable communication of high-priority services.
[0328] In one possible embodiment, the first IAB node also supports rerouting, that is, when the wireless link of the next-hop IAB node fails or the cache is insufficient, the current IAB node can forward the data packet through other connected IAB nodes. The embodiment of the present application provides a slice-based rerouting method, which ensures that the data packet can obtain the resource guarantee of the corresponding slice on the rerouted path, as follows:
[0329] For the case where the backhaul RLC channel carries a single or multiple S-NSSAIs, during rerouting at the first IAB node:
[0330] For the uplink (UL) direction, after selecting the next-hop IAB node, the first IAB node selects the backhaul RLC channel with the same S-NSSAI (SST) as the backhaul RLC channel where the rerouted data packet is located, or the backhaul RLC channel with the most overlap in S-NSSAI (SST) to forward the UL data packet;
[0331] For the downlink (DL) direction, the first IAB node selects the child node of the return RLC channel with the same S-NSSAI (SST) as the return RLC channel where the rerouted data packet is located, or the return RLC channel with the most S-NSSAI (SST) overlap as the next hop node for rerouting. Other operations are the same as UL.
[0332] Through the embodiments of the present application, reliable slice-based data transmission can be achieved under the IAB architecture, ensuring priority and reliable communication of high-priority services.
[0333] In a possible embodiment, the first host node further receives fifth information from the first IAB node.
[0334] Among them, the fifth information is used to indicate slice resource congestion.
[0335] It can be understood that after receiving the fifth information, the first host node determines that the current slice resources are congested and performs flow control for different slice services to ensure the service quality of the slice services.
[0336] In a possible embodiment, the nodes in the first backhaul adaptation protocol BAP topology support the slices indicated by the above-mentioned first information.
[0337] The nodes in the first BAP topology support the slices indicated by the first information, the first BAP topology includes a first host node and a first IAB node, and the first BAP topology is managed by the first host node.
[0338] It is understandable that when configuring the BAP route, the first host node needs to consider the slice type supported by each hop IAB node to ensure that each IAB node on the BAP path supports the target slice.
[0339] In a possible embodiment, the first IAB node transmits the first data packet to the second IAB node according to the slice identifier corresponding to the first data packet.
[0340] The second IAB node is an IAB node that supports the slice corresponding to the first data packet.
[0341] It can be understood that when the next-hop backhaul link is unavailable, the first IAB node can select the next-hop IAB node that supports the target slice based on the slice identifier corresponding to the first data packet to perform rerouting, and transmit the first data packet to the next-hop IAB node (the second IAB node) to ensure that every IAB node on the BAP path supports the target slice.
[0342] Please refer to Figure 9, which is a flowchart of a communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be regarded as reasonable variations or supplements to the embodiment in Figure 8 above; or, it is understood that the communication method in the embodiment of the present application can also be regarded as an embodiment that can be executed independently, and the present application does not limit this. The communication method provided in the embodiment of the present application is applied to the field of communication technology, such as communication in an IAB network, and the communication method includes but is not limited to the following steps:
[0343] S901: The UE initiates a PDU session establishment request to the AMF. Correspondingly, the AMF receives the PDU session establishment request from the UE, which contains the S-NSSAI corresponding to each PDU session.
[0344] S902: The AMF initiates a PDU session resource establishment request to the host IAB-CU. Correspondingly, the host IAB-CU receives the PDU session resource establishment request from the AMF, which includes the S-NSSAI corresponding to each PDU session.
[0345] Optionally, the PDU session resource establishment request further carries session type indication information, which is used to indicate that the PDU session corresponding to the host IAB-CU needs to use reserved resources.
[0346] S903: The host IAB-CU initiates a UE context establishment request for each IAB-MT to the upstream IAB-DU connected to the IAB node. Correspondingly, the upstream IAB-DU connected to the IAB node receives the UE context establishment request from the host IAB-CU.
[0347] The upstream IAB-DU connected to the IAB node may be a DU of a host IAB node or a DU of an intermediate IAB node, which is not limited in the embodiment of the present application.
[0348] The UE context establishment request may also carry one or more of the following information:
[0349] (1) Each established backhaul RLC channel carries the corresponding S-NSSAI. All backhaul RLC channels involved are used to carry the slice data in step S901.
[0350] (2) Each established backhaul RLC channel carries the corresponding S-NSSAI list, i.e., NSSAI. Due to the N:1 bearer mapping, a single backhaul RLC channel can carry data from multiple slices.
[0351] It can be understood that in this case, when scheduling resources, the upstream IAB-DU can refer to whether each S-NSSAI has reserved resources on the air interface. If there is at least one S-NSSAI with reserved resources, the corresponding reserved resources are used to schedule the return RLC channel.
[0352] (3) Carrying a Reserve indication, which is used to instruct the backhaul RLC channel corresponding to the upstream IAB-DU to use the reserved resources of the air interface.
[0353] S904: The host IAB-CU sends a radio resource control (RRC) reconfiguration message to the access IAB-MT. Correspondingly, the access IAB-MT receives the RRC reconfiguration message from the host IAB-CU.
[0354] The RRC reconfiguration message may also carry one or more pieces of information, which are consistent with the one or more pieces of information carried by the UE context establishment request in step S903 above, and are not described in detail here.
[0355] S905: The host IAB-CU sends a UE context establishment request to the access IAB-DU. Correspondingly, the access IAB-DU receives the UE context establishment request from the host IAB-CU, which may carry the corresponding S-NSSAI.
[0356] It should be understood that when the host IAB-CU configures the mapping bearer relationship, the return RLC channels belonging to the same S-NSSAI or Reserved indication reserved resources are associated, that is, a single return RLC channel can only be mapped to a return RLC channel carrying the same S-NSSAI or using reserved resources.
[0357] In an embodiment of the present application, by indicating the slice corresponding to the first return RLC channel corresponding to the first IAB node through the first information, the slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture, ensuring priority and reliable communication of high-priority services.
[0358] Please refer to Figure 10, which is a flow chart of a communication method provided in an embodiment of the present application. It is understandable that the steps in the embodiment of the present application can be regarded as reasonable variations or supplements of the embodiment in Figure 8 above, or as reasonable variations of the embodiment in Figure 9 above; or, it is understandable that the communication method in the embodiment of the present application can also be regarded as an embodiment that can be executed independently, and the present application does not limit this. The communication method provided in the embodiment of the present application is applied to the field of communication technology, such as communication in an IAB network, and the communication method includes but is not limited to the following steps:
[0359] S1001: IAB-MT initial registration.
[0360] Optionally, the IAB-MT may instruct the network through RRC or NAS that the IAB-MT serves as a service node for high-priority services (eg, public safety services).
[0361] S1002: The AMF sends a UE context establishment request to the host IAB-CU. Correspondingly, the host IAB-CU receives the UE context establishment request from the AMF.
[0362] The UE context establishment request may include the supported NSSAI for the IAB-MT and the supported public network integrated non-public network (PNI-NPN). Optionally, it may also carry indication information that the IAB-MT is a high-priority service node.
[0363] S1003: The host IAB-CU determines that the backhaul link associated with the IAB-MT needs to use the reserved resources of the air interface based on the NSSAI, PNI-NPN, or service type indication information sent by the AMF.
[0364] S1004: The host IAB-CU initiates a UE context establishment request for each IAB-MT to the upstream IAB-DU connected to the IAB node. Correspondingly, the upstream IAB-DU connected to the IAB node receives the UE context establishment request from the host IAB-CU.
[0365] The upstream IAB-DU connected to the IAB node may be a DU of a host IAB node or a DU of an intermediate IAB node, which is not limited in the embodiment of the present application.
[0366] The UE context establishment request may also carry one or more of the following information:
[0367] (1) Each established backhaul RLC channel carries the corresponding S-NSSAI. All backhaul RLC channels involved are used to carry the slice data in step S901.
[0368] (2) Each established backhaul RLC channel carries the corresponding S-NSSAI list, i.e., NSSAI. Due to the N:1 bearer mapping, a single backhaul RLC channel can carry data from multiple slices.
[0369] It can be understood that in this case, when scheduling resources, the upstream IAB-DU can refer to whether each S-NSSAI has reserved resources on the air interface. If there is at least one S-NSSAI with reserved resources, the corresponding reserved resources are used to schedule the return RLC channel.
[0370] (3) Carrying a Reserve indication, which is used to instruct the backhaul RLC channel corresponding to the upstream IAB-DU to use the reserved resources of the air interface.
[0371] S1005: The host IAB-CU sends an RRC reconfiguration message to the access IAB-MT. Correspondingly, the access IAB-MT receives the RRC reconfiguration message from the host IAB-CU.
[0372] The RRC reconfiguration message may also carry one or more pieces of information, which are consistent with the one or more pieces of information carried by the UE context establishment request in the above step S1004, and are not described again here.
[0373] It should be understood that when the host IAB-CU configures the mapping bearer relationship, the return RLC channels belonging to the same S-NSSAI or Reserved indication reserved resources are associated, that is, a single return RLC channel can only be mapped to a return RLC channel carrying the same S-NSSAI or using reserved resources.
[0374] In an embodiment of the present application, by indicating the slice corresponding to the first return RLC channel corresponding to the first IAB node through the first information, the slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture, ensuring priority and reliable communication of high-priority services.
[0375] In addition, an embodiment of the present application also provides a communication method. It is understandable that the steps in the embodiment of the present application can be regarded as a reasonable variation or supplement of the embodiment in Figure 8 above, or as a reasonable variation of the embodiment in Figure 9 above, or as a reasonable variation of the embodiment in Figure 10 above; or, it is understandable that the communication method in the embodiment of the present application can also be regarded as an embodiment that can be executed independently, and the present application does not limit this. The communication method provided in the embodiment of the present application is applied to the field of communication technology, such as communication in an IAB network, and the communication method includes but is not limited to the following steps:
[0376] The first host node generates first information and sends the first information to the first IAB node. Correspondingly, the first IAB node receives the first information from the first host node.
[0377] Among them, the first information is used to indicate that the resources used by the first backhaul radio link control RLC channel are reserved resources, and the reserved resources include resources reserved for at least one backhaul RLC channel, and the at least one backhaul RLC channel includes a first backhaul RLC channel, and the first backhaul RLC channel is the backhaul RLC channel corresponding to the first access and backhaul integrated IAB node.
[0378] It can be understood that the reserved resources are a partial proportion of resources reserved for the air interface for the first return RLC channel. The reserved partial proportion of resources can be priority resources (resources that are given priority for use by the first return RLC channel), dedicated resources (resources used only by the first return RLC channel), shared resources (resources shared by multiple return RLC channels including but not limited to the first return RLC channel), etc. The embodiment of the present application does not limit this.
[0379] Optionally, the reserved resources are resources that can only be used by at least one backhaul RLC channel in the absence of non-reserved resources.
[0380] Optionally, the reserved resources may be reserved resources carrying a slice identifier corresponding to the first return RLC channel, or may be reserved resources without a slice identifier, and this embodiment of the present application does not impose any restrictions on this.
[0381] The first information in the embodiment of the present application instructs the first return RLC channel to use reserved resources, thereby achieving slice resource isolation from the transmitting end to the receiving end corresponding to the first return RLC channel, and realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the return RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0382] In addition, the embodiments of the present application also provide a communication method. It is understood that the steps in the embodiments of the present application can be regarded as reasonable variations or supplements of the embodiment in Figure 8 above, as reasonable variations of the embodiment in Figure 9 above, or as reasonable variations of the embodiment in Figure 10 above; or, it is understood that the communication method in the embodiments of the present application can also be regarded as an embodiment that can be executed independently, and the present application does not limit this.
[0383] The communication method provided in the embodiments of the present application is applied to the field of communication technology, such as communication in an IAB network, and in particular, in the scenario of IAB cross-topology data migration. For details, see Figures 5 and 6 above. The connection between a first IAB node and a first host node is migrated to a connection with a second host node. Accordingly, after the connection between the first IAB node and the host node is migrated, first migration data is transmitted. The communication method includes but is not limited to the following steps:
[0384] The first host node generates first information and sends the first information to the first IAB node. Correspondingly, the first IAB node receives the first information from the first host node.
[0385] The first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to a connection with the second host node, and the second host node is different from the first host node.
[0386] The first information includes a slice identifier corresponding to the first migration data, and may specifically include one or more slice identifiers corresponding to the first migration data. For details, please refer to Figure 11A. Figure 11A is a schematic diagram of a signal element provided in an embodiment of the present application. In Figure 11A, considering slice enhancement, the S-NSSAI corresponding to the migration data is added to the first information.
[0387] It can be understood that the first information can indicate the slice corresponding to the return RLC channel used by the first migration data through the slice identifier corresponding to the first migration data contained therein, thereby realizing the slice resource isolation from the sending end to the receiving end corresponding to the return RLC channel used by the first migration data, realizing end-to-end slice resource isolation under the IAB architecture, and ensuring priority and reliable communication of high-priority services.
[0388] In a possible embodiment, the first information is also used to indicate a slice corresponding to the second backhaul RLC channel.
[0389] The second backhaul RLC channel is the backhaul RLC channel corresponding to the second host node.
[0390] Optionally, the first information includes one or more slice identifiers corresponding to the second return RLC channel.
[0391] The specific description is as in the above-mentioned method 1: the first information includes one or more slice identifiers corresponding to the first return RLC channel, which will not be repeated here.
[0392] Optionally, the first information is further used to indicate that resources used by the second backhaul RLC channel are reserved resources.
[0393] The specific description is as in the above-mentioned method 2: the first information indicates that the resources used by the first backhaul RLC channel are reserved resources, which will not be described in detail here.
[0394] For details, please refer to Figure 11B, which is a schematic diagram of a signal element provided in an embodiment of the present application. In Figure 11A, considering slice enhancement, the first information needs to indicate the S-NSSAI (list) corresponding to each return RLC channel, or the Reserve indication, which is used to indicate the slices or reserved resources used by the return RLC channel related to the other CU.
[0395] It is understandable that the CU can perform access control on the return RLC channel based on the slice, that is, if the corresponding slice is not supported, the return RLC channel is refused to be established.
[0396] It can be understood that the CU can implement slice remapping for the return RLC channel, that is, the slices corresponding to the ingress and egress return RLC channels can be different, and the return RLC channel is actually carried by different slice resources.
[0397] It can be understood that after the first IAB node receives the first information, it will establish a second backhaul RLC channel according to the slice indicated by the first information to perform IAB cross-topology data migration. Since the resources used by the second backhaul RLC channel are the slice resources indicated by the first information, the slice resource isolation from the sending end to the receiving end corresponding to the second backhaul RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture; due to the end-to-end slice resource isolation, the backhaul RLC channel corresponding to the high-priority service can use specific slice resources, thereby ensuring priority and reliable communication of high-priority services.
[0398] Please refer to Figure 12, which is a flow chart of a communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be regarded as supplements to the embodiments in Figures 8, 9, and 10 above, or it is understood that the communication method in the embodiment of the present application can also be regarded as an embodiment that can be executed independently, and the present application does not limit this. The communication method provided in the embodiment of the present application is applied to the field of communication technology, such as communication in an IAB network, and the communication method includes but is not limited to the following steps:
[0399] S1201: The first IAB node (IAB-DU) sends a congestion indication to the first host node (Donor-CU) to indicate that the slice resource is congested. Correspondingly, the first host node (Donor-CU) receives the congestion indication from the first IAB node (IAB-DU).
[0400] It can be understood that after receiving the congestion indication, the first host node determines that the current slice resources are congested and performs flow control for different slice services to ensure the service quality of the slice services.
[0401] Alternatively, optionally, the first IAB node transmits the first data packet to the second IAB node according to the slice identifier corresponding to the first data packet.
[0402] The second IAB node is an IAB node that supports the slice corresponding to the first data packet.
[0403] It can be understood that when the next-hop backhaul link is unavailable (for example, slice resources are congested), the first IAB node can select the next-hop IAB node that supports the target slice based on the slice identifier corresponding to the first data packet to perform rerouting, and transmit the first data packet to the next-hop IAB node (the second IAB node) to ensure that every IAB node on the BAP path supports the target slice.
[0404] The above describes in detail the methods of the embodiments of the present application. The following provides an apparatus for implementing any method in the embodiments of the present application. For example, an apparatus is provided that includes units (or means) for implementing each step performed by the device in any of the above methods.
[0405] Please refer to FIG. 13 , which is a schematic structural diagram of a communication device provided in an embodiment of the present application.
[0406] 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.
[0407] The communication unit 1301 can implement a sending function and / or a receiving function, and can also be described as a transceiver unit. The communication unit 1301 can also be a unit that integrates an acquisition unit and a transmission unit, wherein the acquisition unit is used to implement the receiving function and the transmission unit is used to implement the transmission function. Optionally, the communication unit 1301 can be used to receive information sent by other devices, and can also be used to send information to other devices.
[0408] In one possible design, the communication device 130 may correspond to the first host node in the method embodiments shown in Figures 8, 9, and 10 above. For example, the communication device 130 may be the first host node or a chip in the first host node. The communication device 130 may include a unit for executing the operations performed by the first host node in the method embodiments shown in Figures 8, 9, and 10 above, and each unit in the communication device 130 is respectively for implementing the operations performed by the first host node in the method embodiments shown in Figures 8, 9, and 10 above. The description of each unit is as follows:
[0409] The processing unit 1302 is configured to generate first information, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to a first integrated access and backhaul IAB node.
[0410] The communication unit 1301 is configured to send first information to a first IAB node.
[0411] In a possible implementation, the first information includes one or more slice identifiers corresponding to the first return RLC channel.
[0412] In a possible implementation, the first information is further used to indicate that resources used by the first backhaul RLC channel are reserved resources, where 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.
[0413] In a possible implementation, the communication unit 1301 is further used to receive second information from the first node, where the second information is used to indicate that 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 communication device.
[0414] In a possible implementation, the communication unit 1301 is further configured to receive third information from the first node, where the third information is used to indicate that the first IAB node is a node providing a first-priority service.
[0415] In a possible implementation, the communication unit is further configured to receive fourth information from the first IAB node, where the fourth information is used to indicate that the first IAB node is a node providing a first-priority service.
[0416] In a possible implementation, the processing unit 1302 is further configured to determine, according to the third information, that the first backhaul RLC channel needs to use reserved resources.
[0417] In a possible embodiment, the first information also includes a slice identifier corresponding to the first migration data, and the first migration data includes data transmitted after the connection between the first IAB node and the communication device is migrated to the connection with the second host node, and the second host node is different from the communication device.
[0418] In a possible implementation, the first information is further used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second donor node.
[0419] In a possible implementation, the communication unit 1301 is further used to receive fifth information from the first IAB node, where the fifth information is used to indicate slice resource congestion.
[0420] In a possible implementation, nodes in a first backhaul adaptation protocol BAP topology support the slice indicated by the first information, the first BAP topology is managed by the communication device, and the first IAB node belongs to the first BAP topology.
[0421] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0422] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0423] In another possible design of the communication device 130 shown in FIG13 , the communication device 130 may correspond to the first IAB node in the method embodiments shown in FIG8 , FIG9 , and FIG10 . For example, the communication device 130 may be the first IAB node or a chip in the first IAB node. The communication device 130 may include a unit for executing the operations performed by the first IAB node in the method embodiments shown in FIG8 , FIG9 , and FIG10 . Furthermore, each unit in the communication device 130 is for implementing the operations performed by the first IAB node in the method embodiments shown in FIG8 , FIG9 , and FIG10 . The description of each unit is as follows:
[0424] The communication unit 1301 is used to receive first information from the first host node, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to the communication device.
[0425] The processing unit 1302 is configured to establish a first backhaul RLC channel according to the first information.
[0426] In a possible implementation, the first information includes one or more slice identifiers corresponding to the first return RLC channel.
[0427] In a possible implementation, the first information is further used to indicate that resources used by the first backhaul RLC channel are reserved resources, where 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.
[0428] In a possible implementation, the communication unit 1301 is further configured to send fourth information to the first host node, where the fourth information is used to indicate that the communication device is a node providing a first-priority service.
[0429] In a possible embodiment, the first information also includes a slice identifier corresponding to the first migration data, and the first migration data includes data transmitted after the connection between the communication device and the first host node is migrated to the connection with the second host node, and the second host node is different from the first host node.
[0430] In a possible implementation, the first information is further used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second donor node.
[0431] In a possible implementation, the communication unit 1301 is further used to send fifth information to the first host node, where the fifth information is used to indicate slice resource congestion.
[0432] In a possible implementation, nodes in a first backhaul adaptation protocol BAP topology support the slice indicated by the first information, the first BAP topology is managed by a first host node, and the communication device belongs to the first BAP topology.
[0433] In a possible implementation, the processing unit 1302 is further configured to transmit the first data packet to a second IAB node according to a slice identifier corresponding to the first data packet, where the second IAB node is an IAB node that supports the slice corresponding to the first data packet.
[0434] In one implementation, the communication apparatus is a communication device. When the communication apparatus 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.
[0435] 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, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.
[0436] According to an embodiment of the present application, each unit in the device shown in Figure 13 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.
[0437] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in FIG. 8 , FIG. 9 , and FIG. 10 .
[0438] In the communication device 130 described in Figure 13, the slice corresponding to the first return RLC channel corresponding to the first IAB node is indicated by the first information, so that the slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture, ensuring priority and reliable communication of high-priority services.
[0439] Please refer to FIG14 , which is a schematic structural diagram of a communication device provided in an embodiment of the present application.
[0440] It should be understood that the communication device 140 shown in Figure 14 is only an example. The communication device of the embodiment of the present application may also include other components, or include components with similar functions to the various components in Figure 14, or not include all the components in Figure 14.
[0441] The communication device 140 includes a communication interface 1401 and at least one processor 1402 .
[0442] The communication device 140 may correspond to any node or device among the first host node and the first IAB node. The communication interface 1401 is used to send and receive signals, and at least one processor 1402 executes program instructions so that the communication device 140 implements the corresponding process of the method executed by the corresponding device in the above method embodiment.
[0443] In one possible design, the communication device 140 may correspond to the first host node in the method embodiments shown in Figures 8, 9, and 10 above. For example, the communication device 140 may be the first host node or a chip in the first host node. The communication device 140 may include components for executing the operations performed by the first host node in the above method embodiments, and each component in the communication device 140 is respectively for implementing the operations performed by the first host node in the above method embodiments. Specifically, it may be as follows:
[0444] The first host node generates first information, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to a first access and backhaul integrated IAB node.
[0445] The first host node sends first information to the first IAB node.
[0446] In another possible design, the communication device 140 may correspond to the first IAB node in the method embodiments shown in Figures 8, 9, and 10 above. 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 for executing the operations performed by the first IAB node in the method embodiments described above. Furthermore, each component within the communication device 140 is configured to implement the operations performed by the first IAB node in the method embodiments described above. Specifically, the operations may be as follows:
[0447] The first access and backhaul integrated IAB node receives first information from the first host node, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to the first IAB node.
[0448] The first IAB node establishes a first backhaul RLC channel according to the first information.
[0449] In the communication device 140 described in Figure 14, the slice corresponding to the first return RLC channel corresponding to the first IAB node is indicated by the first information, so that the slice resource isolation from the sending end to the receiving end corresponding to the first return RLC channel can be achieved, thereby realizing end-to-end slice resource isolation under the IAB architecture, ensuring priority and reliable communication of high-priority services.
[0450] It should be understood that when communication device 140 is a first host node, FIG14 illustrates another form of communication device 140. In FIG15 , communication device 150 is a first host node. It should be understood that the first host node includes a CU and a DU. The CU may include a communication interface, a processor, and optionally a memory. The communication interface may be used to communicate with the CU of the host node or the DU of the IAB node. The DU may also include a communication interface, a processor, and a memory, as well as a bus connecting the communication interface, processor, and memory. The communication interface is used to communicate with the MT of the IAB node.
[0451] For the case where the communication device may be a chip or a chip system, reference may be made to the schematic structural diagram of the chip shown in FIG16 .
[0452] As shown in Figure 16 , chip 160 includes a processor 1601 and an interface 1602. There may be one or more processors 1601, and there may be multiple interfaces 1602. It should be noted that the functions corresponding to processor 1601 and interface 1602 can be implemented through hardware design, software design, or a combination of hardware and software, without limitation.
[0453] Optionally, the chip 160 may further include a memory 1603 , which is used to store necessary program instructions and data.
[0454] In the present application, processor 1601 may be configured to call from memory 1603 an implementation program for the communication method provided in one or more embodiments of the present application on one or more devices or nodes in the first host node or the first IAB node, and execute the instructions contained in the program. Interface 1602 may be configured to output the execution results of processor 1601. In the present application, interface 1602 may be specifically configured to output various messages or information from processor 1601.
[0455] Regarding the communication method provided by one or more embodiments of the present application, reference may be made to the embodiments shown in FIG. 8 , FIG. 9 , and FIG. 10 , which will not be described in detail here.
[0456] The processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0457] The memory in the embodiments of the present application is used to provide storage space, in which data such as an operating system and computer programs can be stored. 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).
[0458] According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on one or more processors, the method shown in Figures 8, 9, and 10 can be implemented.
[0459] According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a computer program product, which includes a computer program. When the computer program runs on a processor, it can implement the method shown in Figures 8, 9, and 10 above.
[0460] An embodiment of the present application also provides a system, which includes at least one communication device 130, communication device 140, communication device 150 or chip 160 as described above, and is used to execute the steps executed by the corresponding device in any of the embodiments of Figures 8, 9, and 10.
[0461] An embodiment of the present application also provides a system, which includes a first host node and a first IAB node. The first host node is used to execute the steps executed by the first host node in any of the above embodiments of Figures 8, 9, and 10. The first IAB node is used to execute the steps executed by the first IAB node in any of the above embodiments of Figures 8, 9, and 10.
[0462] An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is used to execute the method in any of the above method embodiments.
[0463] It should be understood that the above-mentioned processing device can be a chip. For example, the processing device can 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 other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chip. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.
[0464] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0465] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disc (SSD)).
[0466] The units in the above-mentioned various apparatus embodiments completely correspond to the electronic devices in the method embodiments, and the corresponding modules or units perform the corresponding steps. For example, the communication unit (transceiver) performs the receiving or sending steps in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be referred to the corresponding method embodiments. Among them, there can be one or more processors.
[0467] It is understood that in the embodiments of the present application, the electronic device can perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples, and the embodiments of the present application can also perform other operations or variations of various operations. In addition, the various steps can be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.
[0468] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0469] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0470] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0471] The units described as separate components may or may not be physically separate, and the components 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0472] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0473] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
[0474] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.
Claims
1. A communication method, characterized in that: include: The first host node generates first information, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to a first access backhaul integrated IAB node; The first host node sends the first information to the first IAB node.
2. The method according to claim 1, characterized in that The first information includes one or more slice identifiers corresponding to the first return RLC channel.
3. The method according to claim 1 or 2, characterized in that: The first information is further used to indicate that resources used by the first backhaul RLC channel are reserved resources, where 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. The method according to any one of claims 1 to 3, characterized in that Before the first host node sends the first information to the first IAB node, the method further includes: The first host node receives second information from the first node, where the second information is used to indicate that resources used by a first protocol data unit PDU session are reserved resources, and the first PDU session includes a PDU session corresponding to the first host node.
5. The method according to any one of claims 1 to 3, characterized in that Before the first host node sends the first information to the first IAB node, the method further includes: The first host node receives third information from the first node, where the third information is used to indicate that the first IAB node is a node that provides a business service of a first priority.
6. The method according to claim 5, characterized in that The method further comprises: The first host node receives fourth information from the first IAB node, where the fourth information is used to indicate that the first IAB node is a node that provides the first priority business service.
7. The method according to claim 5 or 6, characterized in that: The method further comprises: The first host node determines, based on the third information, that the first backhaul RLC channel needs to use reserved resources.
8. The method according to any one of claims 1 to 7, characterized in that The first information also includes a slice identifier corresponding to first migration data, and the first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to a connection with a second host node, and the second host node is different from the first host node.
9. The method according to claim 8, characterized in that The first information is also used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second host node.
10. The method according to claim 9, characterized in that In a case where the slice corresponding to the second backhaul RLC channel is different from the slice corresponding to the first backhaul RLC channel, the first information is further used to indicate a mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.
11. The method according to claim 10, characterized in that The mapping relationship includes: The slice identifier corresponding to the first backhaul RLC channel and the slice identifier corresponding to the second backhaul RLC channel are the same or different.
12. The method according to claim 10 or 11, characterized in that: The mapping relationship includes: 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; Alternatively, 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. The type SST is different, 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, characterized in that The method further comprises: The first host node receives fifth information from the first IAB node, and the fifth information is used to indicate slice resource congestion.
14. The method according to any one of claims 1 to 13, characterized in that The nodes in the first backhaul adaptation protocol BAP topology support the slices indicated by the first information, the first BAP topology is managed by the first host node, and the first IAB node belongs to the first BAP topology.
15. A communication method, characterized in that: include: The first access backhaul integrated IAB node receives first information from the first host node, where the first information is used to indicate a slice corresponding to a first backhaul radio link control RLC channel, where the first backhaul RLC channel is a backhaul RLC channel corresponding to the first IAB node; The first IAB node establishes the first backhaul RLC channel according to the first information.
16. The method according to claim 15, characterized in that The first information includes one or more slice identifiers corresponding to the first return RLC channel.
17. The method according to claim 15 or 16, characterized in that The first information is further used to indicate that resources used by the first backhaul RLC channel are reserved resources, where 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. The method according to any one of claims 15 to 17, characterized in that Before the first access and backhaul integrated IAB node receives the first information from the first host node, the method further includes: The first IAB node sends fourth information to the first host node, where the fourth information is used to indicate that the first IAB node is a node that provides the business service of the first priority.
19. The method according to any one of claims 15 to 18, characterized in that The first information also includes a slice identifier corresponding to first migration data, and the first migration data includes data transmitted after the connection between the first IAB node and the first host node is migrated to a connection with a second host node, and the second host node is different from the first host node.
20. The method according to claim 19, characterized in that The first information is also used to indicate a slice corresponding to a second backhaul RLC channel, where the second backhaul RLC channel is a backhaul RLC channel corresponding to the second host node.
21. The method according to claim 20, characterized in that In a case where the slice corresponding to the second backhaul RLC channel is different from the slice corresponding to the first backhaul RLC channel, the first information is further used to indicate a mapping relationship between the second backhaul RLC channel and the first backhaul RLC channel.
22. The method according to claim 21, characterized in that The mapping relationship includes: The slice identifier corresponding to the first backhaul RLC channel and the slice identifier corresponding to the second backhaul RLC channel are the same or different.
23. The method according to claim 21 or 22, characterized in that The mapping relationship includes: 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; Alternatively, 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, characterized in that The method further comprises: The first IAB node sends fifth information to the first host node, and the fifth information is used to indicate slice resource congestion.
25. The method according to any one of claims 15 to 24, characterized in that The nodes in the first backhaul adaptation protocol BAP topology support the slices indicated by the first information, the first BAP topology is managed by the first host node, and the first IAB node belongs to the first BAP topology.
26. The method according to any one of claims 15 to 25, characterized in that The method further comprises: The first IAB node transmits the first data packet to a second IAB node according to a 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.
27. A communication device, characterized in that: The method comprises a module or a unit for executing the method as claimed in any one of claims 1 to 14 or claims 15 to 26.
28. A communication device, characterized in that: include: processor; When the processor calls the computer program or instruction in the 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, characterized in that: comprising a logic circuit and an interface, wherein the logic circuit and the interface are coupled; The interface is used to input data to be processed, the logic circuit processes the data to be processed according to the method as described in any one of claims 1 to 14 or claims 15 to 26 to obtain processed data, and the interface is used to output the processed data.
30. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium is used to store instructions or computer programs; when the instructions or the computer program are executed, the method according to any one of claims 1 to 14 is implemented, or the method according to any one of claims 15 to 26 is implemented.
31. A computer program product, characterized in that include: instructions or computer programs; When the instructions or the computer program are executed, 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.
32. A communication system, characterized in that: Comprising the communication device according to claim 27, or the communication device according to claim 28, or the communication device according to claim 29.
33. A communication system, characterized in that: include: a first host node and a first IAB node; The first host node is used to execute the method according to any one of claims 1 to 14, and the first IAB node is used to execute the method according to any one of claims 15 to 26.
