WO2022160108A1 - 无线通信方法、通信装置及通信系统 - Google Patents

无线通信方法、通信装置及通信系统 Download PDF

Info

Publication number
WO2022160108A1
WO2022160108A1 PCT/CN2021/073856 CN2021073856W WO2022160108A1 WO 2022160108 A1 WO2022160108 A1 WO 2022160108A1 CN 2021073856 W CN2021073856 W CN 2021073856W WO 2022160108 A1 WO2022160108 A1 WO 2022160108A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
information
hop
iab
access network
Prior art date
Application number
PCT/CN2021/073856
Other languages
English (en)
French (fr)
Inventor
刘菁
朱元萍
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202180088406.8A priority Critical patent/CN116711379A/zh
Priority to PCT/CN2021/073856 priority patent/WO2022160108A1/zh
Publication of WO2022160108A1 publication Critical patent/WO2022160108A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
    • H04W40/16—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality based on interference

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a wireless communication method, a communication device, and a communication system.
  • UE user equipments
  • information sent by one UE needs to be routed and forwarded by one or more nodes in the wireless network to reach another UE.
  • the nodes through which the information sent by the UE passes constitute a routing path, and how to improve the information transmission efficiency in the routing path needs to be solved at present.
  • Embodiments of the present application provide a wireless communication method, a communication device, and a communication system, so as to improve the information transmission efficiency in the routing path.
  • an embodiment of the present application provides a wireless communication method, including: a first node acquiring first information, where the first information includes at least one of the following: a load of at least one next-hop node of the first node information, the interference information of the at least one next-hop node, the channel quality between the first node and the at least one next-hop node, the first node reaching the target through the at least one next-hop node Link hop number information of the node; the first node determines, according to the first information, to transmit data packets through a second node, where the at least one next-hop node includes the second node.
  • the first node selects one of the next-hop nodes of the first node based on the information of one or more next-hop nodes of the first node to transmit data packets (such as data or signaling). node.
  • the method can realize the selection of an appropriate next-hop node for the first node, and can improve the information transmission efficiency in the routing path.
  • the first node receives the load information of the at least one next-hop node and/or the interference information of the at least one next-hop node from the access network node; or, all The first node receives the load information of the first next hop node and/or the interference information of the first next hop node from the first next hop node, and the first next hop node is the Any one of at least one next-hop node.
  • the first node receives the channel quality between the first node and the at least one next-hop node from the access network node; or, the first node Determining the channel quality between the first node and the at least one next-hop node by itself.
  • the first node receives the link hop count information from the access network node, where the link hop count information is associated with a routing identifier and the next hop node corresponds to the identification information of the target node, and the routing identification includes the identification information of the target node and the path identification.
  • the first node receives the link hop count information from the access network node, where the link hop count indicated by the link hop count information is the first link hop count information.
  • the minimum link hop count for a node to reach the target node through the next hop node, and the link hop count information corresponds to the identification information of the next hop node and the identification information of the target node.
  • the first node receives identification information of the first next-hop node from a first next-hop node, where the first next-hop node is the at least one next-hop node Jump to any one of the nodes.
  • the first node receives the identification information of the first next-hop node from the first next-hop node, including:
  • the first node receives identification information of the first next-hop node from the first next-hop node through a sidelink between the first node and the first next-hop node.
  • the first node receives identification information of a target node that can be reached by the first next-hop node from the first next-hop node.
  • the first node receives information on the minimum number of link hops from the first next-hop node to the reachable target node from the first next-hop node.
  • the first node receives first indication information from the access network node, where the first indication information instructs the first node to receive the first bearer of the data packet and the the mapping relationship between the second bearer on which the first node sends the data packet, the first bearer is a backhaul radio link control channel, and the second bearer is the first node and the at least one A radio bearer or radio link control channel on the sidelink between next-hop nodes.
  • the first node sends second indication information to the access network node, where the second indication information indicates that the first node supports sidelinks.
  • the first node receives third indication information from the access network node, where the third indication information indicates enabling the sidelink of the first node.
  • the first node and the second node are both IAB nodes, and the target node is an IAB host node or an access IAB node; or, the first node is an IAB host node , the second node is an IAB node, and the target node is an access IAB node.
  • an embodiment of the present application provides a wireless communication method, including: a first node receiving second indication information from an access network node, where the second indication information indicates enabling a sidelink of the first node The first node enables the side link of the first node according to the second indication information.
  • the sidelink of the first node can be enabled, so that the first node can communicate with other nodes through the sidelink interface with other nodes, which can improve the information transmission efficiency in the routing path.
  • the first node before the first node receives the second indication information from the access network node, the first node sends the first indication information to the access network node, and the first indication information is sent to the access network node.
  • An indication message indicates that the first node supports sidelinks.
  • the first node is an IAB node
  • the access network node is an IAB host node.
  • an embodiment of the present application provides a wireless communication method, including: a first node receiving indication information from an access network node, where the indication information indicates that a first bearer used for the first node to receive a data packet and a a mapping relationship between a second bearer used by the first node to send the data packet, the first bearer is a backhaul radio link control channel, and the second bearer is the first node and the the radio bearer or radio link control channel on the side link between the next-hop nodes of the first node; the first node, according to the indication information, receives the data from the first bearer The packet is sent to the next-hop node through the second bearer.
  • the first node can quickly determine the bearer of the sent data packet, so that the information transmission efficiency in the routing path can be improved.
  • an embodiment of the present application provides a wireless communication method, including: a first node receiving identification information of a second node from an access network node, where the first node is a node accessed by a first user equipment UE, The second node is a node accessed by the second UE; the first node sends a first data packet to the second UE through the second node, where the first data packet carries the first information and the second information, the first information includes data or signaling from the first UE, and the second information includes one or more of the following: an access stratum identifier of the second UE, an identifier of the first transmission channel information, and the first transmission channel is a channel for transmitting the first information between the second UE and the second node.
  • the first node may obtain the identification information of the node accessed by the second UE from the access network node, and then the first node may send a data packet to the second UE through the second node.
  • the routing path of the data packet can be shortened and the transmission delay of the data packet can be reduced, thereby improving the information transmission efficiency in the routing path.
  • the sending, by the first node, the first data packet to the second UE through the second node includes: the first node sending the first data packet to the second node data packet, the second node is configured to send the first data packet to the second UE; or, the first node sends the first data packet to a third node, and the third node uses the and sending the first data packet to the second UE through the second node, and the third node is an intermediate node between the first node and the second node.
  • the first node before the first node receives the identification information of the second node from the access network node, the first node receives the first node from the first UE through the second transmission channel Two data packets, the second data packet carries the first information and the application layer identifier of the second UE, and the second transmission channel is the transmission between the first UE and the first node.
  • the first node acquires the access stratum identifier of the second UE according to the application identifier of the second UE, including: the first node reporting to the access network node sending the application layer identifier of the second UE;
  • the first node receives the access stratum identity of the second UE from the access network node.
  • the application layer identifier of the second UE is carried in a medium access control MAC layer header field or a radio link control RLC layer header field of the second data packet.
  • the first node receives identification information of the first transmission channel from the access network node.
  • the second information is carried in the BAP layer header field of the backhaul adaptation protocol of the first data packet.
  • the first node receives first indication information from the access network node, where the first indication information instructs the first node to enable a local transfer function.
  • the first node before the first node receives the first indication information from the access network node, the first node sends second indication information to the access network node, and the first indication information is sent to the access network node.
  • the second indication information indicates that the first node supports the local transfer function.
  • the first node and the second node are both IAB nodes, and the access network node is an IAB host node.
  • an embodiment of the present application provides a wireless communication method, including: an access network node receiving an application layer identifier of a second UE from a first node, where the first node is a node accessed by the first UE; The access network node determines the access layer identifier of the second UE according to the application layer identifier of the second UE; the access network node sends the access layer identifier of the second UE to the first node identification and identification information of a second node, where the second node is a node accessed by the second UE.
  • the first node may obtain the identification information of the node accessed by the second UE from the access network node, and then the first node may send a data packet to the second UE through the second node.
  • the routing path of the data packet can be shortened and the transmission delay of the data packet can be reduced, thereby improving the information transmission efficiency in the routing path.
  • the access network node sends identification information of a first transmission channel to the first node, where the first transmission channel is the second UE and the second node A channel for transmitting data packets from the first UE therebetween.
  • the access network node sends first indication information to the first node, where the first indication information instructs the first node to enable the local transfer function.
  • the access network node before the access network node sends the first indication information to the first node, the access network node receives the second indication information from the first node, so the access network node receives the second indication information from the first node.
  • the second indication information indicates that the first node supports the local transfer function.
  • the first node and the second node are both IAB nodes, and the access network node is an IAB host node.
  • an embodiment of the present application provides a communication device, where the device may be a first node or a chip used for the first node.
  • the device has the function of implementing any possible implementation methods of the first aspect to the fourth aspect above. This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, and the device may be an access network node or a chip used for an access network node.
  • the device has the function of implementing any possible implementation method of the fifth aspect above. This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, including a processor, where the processor is coupled to a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the device implements the above-mentioned first aspect Any possible implementation method to the fifth aspect.
  • the memory may be located within the device or external to the device.
  • the processor includes one or more.
  • an embodiment of the present application provides a communication apparatus, including a unit or means for executing each step of any possible implementation method of the first aspect to the fifth aspect.
  • an embodiment of the present application provides a communication device, including a processor and an interface circuit, where the processor is configured to control the interface circuit to communicate with other devices, and execute any possible implementation method of the first to fifth aspects above .
  • the processor includes one or more.
  • the embodiments of the present application further provide a computer-readable storage medium, including instructions, which, when executed on a computer, cause the computer to execute any possible implementation method of the first to fifth aspects above.
  • the embodiments of the present application further provide a computer program product, which, when running on a computer, enables the computer to execute any possible implementation method of the above-mentioned first to fifth aspects.
  • an embodiment of the present application further provides a chip system, including a processor, where the processor is coupled with a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the chip system enables the above-mentioned Any possible implementation methods of the first aspect to the fifth aspect.
  • the memory may be located within the system-on-chip, or may be located outside the system-on-chip.
  • the processor includes one or more.
  • an embodiment of the present application further provides a communication system, including a first node for implementing any possible implementation method of the fourth aspect and a connection for implementing any possible implementation method of the fifth aspect. access node.
  • FIG. 1 is a schematic diagram of a wireless communication method provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a routing path
  • FIG. 3 is a schematic diagram of a wireless communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a wireless communication method provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a wireless communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a routing path
  • FIG. 7 is a schematic diagram of a routing path
  • Figure 8 is a diagram of the separation architecture of gNB-CU and gNB-DU in NR;
  • FIG. 9 is a schematic diagram of the control plane protocol stack under the gNB adopting the CU-DU separation architecture
  • Figure 10 is a schematic diagram of a user plane protocol stack under the gNB's CU-DU separation architecture
  • FIG. 11 is a schematic diagram of a two-hop data return scenario
  • 12 is a schematic diagram of a control plane protocol stack for two-hop data backhaul
  • FIG. 13 is a schematic diagram of a user plane protocol stack for two-hop data backhaul
  • Figure 15 is a schematic diagram of a networking mode
  • Figure 16 is an example diagram of a networking mode
  • Figure 17 is an example diagram of a node relationship
  • Figure 18 is an example diagram of a wireless link failure
  • Figure 19 is a schematic diagram of node communication
  • Figure 20 is a schematic diagram of node communication
  • Figure 21 is a schematic diagram of an IAB mesh networking scenario
  • Figure 22 is a schematic diagram of an IAB mesh networking scenario
  • Figure 23 is a DL data transmission protocol stack
  • Figure 24 is a schematic diagram of data transmission in local switch mode
  • Figure 25 is the flow chart of local switch in the IAB mesh networking scenario
  • FIG. 26 is a schematic diagram of a communication device according to an embodiment of the present application.
  • FIG. 27 is a schematic diagram of a communication device according to an embodiment of the present application.
  • the nodes through which the information sent by the UE passes constitute a routing path, and how to improve the information transmission efficiency in the routing path needs to be solved at present.
  • a node in the routing path cannot normally route the information to the next hop node or UE of the node.
  • a node needs to choose a node for rerouting. How to select an appropriate rerouting node for a node so as to improve the information transmission efficiency in the routing path is the first problem to be solved by the embodiments of the present application.
  • each node decides the next hop node of the data packet by itself, and how to select a suitable next hop node for the node is also a problem to be solved by the embodiment of the present application, that is, whether the data packet is It is a problem to be solved by the embodiments of the present application how to select an appropriate next-hop node for a node.
  • the embodiments of the present application take the rerouting of data packets as an example for description, and the solutions of the embodiments of the present application are also applicable to the routing scenarios of data packets, and details are not repeated here.
  • an embodiment of the present application provides a wireless communication method. As shown in FIG. 1 , the method includes the following steps:
  • Step 101 the first node obtains first information.
  • the first node is any node other than the target node in the routing path.
  • the target node refers to the node accessed by the receiver UE.
  • the first information includes at least one of the following:
  • the load information of a node can be used to reflect the resource occupancy of the node.
  • the heavier the load of a node the more resources the node occupies, and therefore the lower the routing efficiency of the node. Therefore, a node with a relatively light load is generally selected for routing.
  • the so-called routing refers to selecting the appropriate transmission path for the data packet for transmission.
  • the interference information of a node can be used to reflect the link quality status of the node.
  • the greater the interference of a node the worse the link quality of the node is, which may easily lead to packet loss. Therefore, nodes with relatively light interference are generally selected for routing.
  • the channel quality between the first node and the next-hop node of the first node may be used to reflect the information transmission quality between the first node and the next-hop node of the first node.
  • the better the channel quality the better the information transmission quality. Therefore, a node with relatively good channel quality is generally selected for routing.
  • the link hop information is used to indicate the number of nodes passed in the routing path, and each node is a hop.
  • the smaller the number of hops the smaller the transmission delay, and the faster the information can reach the target node. Therefore, nodes with relatively few link hops are generally selected for routing.
  • Step 102 the first node determines to transmit the data packet through the second node according to the first information, wherein the at least one next-hop node includes the second node.
  • the transmission of the data packet includes routing of the data packet, or rerouting of the data packet.
  • the first node selects one of the next hop nodes of the first node based on the information of one or more next hop nodes of the first node to perform data packets (such as data or signaling) rerouting node.
  • the method can realize the selection of an appropriate next-hop node for the first node, and can improve the information transmission efficiency in the routing path.
  • FIG. 2 it is a schematic diagram of a routing path.
  • node 1 also referred to as the first node
  • node 4 the next hop node in the routing path of node 1
  • node 1 needs to select the next hop node for rerouting. That is to say, the original path of the data packet is from node 1 to the destination node 1 through node 4.
  • node 1 needs to Choose a new path for the packet to transmit (ie, reroute).
  • node 1 includes three next-hop nodes, namely node 2, node 3 and node 5, that is, node 1 can reach target node 1 through node 2 or node 3 or node 5, respectively.
  • node 1 selects the next hop node for rerouting of the data packet to be node 3 (also referred to as the second node).
  • the following introduces different implementation methods for the first node to acquire the first information.
  • an access network node is a node used to manage and control nodes in a routing path.
  • the identification information of a node may be the address information of the node (such as a backhaul adaptation protocol (BAP) address or an Internet Protocol (Internet Protocol, IP) address, etc.) or an identification (ID) of the node, etc.
  • BAP backhaul adaptation protocol
  • IP Internet Protocol
  • ID identification
  • the first node receives load information of at least one next-hop node and/or interference information of at least one next-hop node of the first node from an access network node.
  • the first node receives the load information of the next-hop node and/or the interference information of the next-hop node from each next-hop node of the first node respectively.
  • any one of the at least one next-hop node of the first node is called the first next-hop node, and the first node receives the load information of the first next-hop node and/or the first next-hop node from the first next-hop node. or the interference information of the first next-hop node.
  • the first node receives the channel quality between the first node and at least one next-hop node of the first node from the access network node.
  • the first node determines the channel quality between the first node and at least one next-hop node of the first node by itself.
  • the channel quality between the first node and at least one next-hop node of the first node is obtained by measuring or calculating by the first node.
  • the first node receives, from the access network node, information on the link hop count of the first node reaching the target node through at least one next-hop node, where the link hop count information and the routing identifier and the next-hop node
  • the identification information corresponds to the routing identification
  • the routing identification includes the identification information of the target node and the path identification.
  • the routing table includes the identification information of the next-hop node of the first node, the routing identification of the first node reaching the target node through the next-hop node, and the first node Information on the number of hops of the link to the target node through the next hop node.
  • the first node receives from the access network node information on the number of link hops from the first node to the target node through at least one next-hop node, where the number of link hops indicated by the information on the link hop number indicates the number of link hops. is the minimum link hop count for the first node to reach the target node through the next hop node, and the link hop count information corresponds to the identification information of the next hop node and the identification information of the target node.
  • the access network node may indicate to the first node information on the minimum number of link hops for the first node to reach the target node through at least one next-hop node through the indication information.
  • the first node may receive identification information of the next-hop node from each next-hop node of the first node. Any one of the at least one next-hop node of the first node is referred to as the first next-hop node, and the first node may receive the identification information of the first next-hop node from the first next-hop node.
  • the first next hop node sends the identification information of the first next hop node to the first node through the air interface between the first next hop node and the first node.
  • the first next-hop node sends the identification information of the first next-hop node to the first node through a sidelink interface between the first next-hop node and the first node.
  • the first node may receive, from the first next-hop node, identification information of a target node that can be reached by the first next-hop node. That is, the first next-hop node sends all the identification information of the target nodes that the first next-hop node can reach to the first node, so that when the first node needs to select a node for transmission (such as rerouting) subsequently, it can learn Whether the first next-hop node can be used as a candidate next-hop node.
  • the first next hop node will not send the information of all link hops from the first next hop node to the target node to the first node, but will send the minimum chain link from the first next hop node to the target node to the first node.
  • the hop count information is sent to the first node.
  • the first node further receives first indication information from the access network node, where the first indication information indicates a difference between the first bearer on which the first node receives the data packet and the second bearer on which the first node sends the data packet mapping relationship, the first bearer is the backhaul radio link control channel (backhaul radio link control channel, BH RLC CH), and the second bearer is the side link between the first node and at least one next-hop node.
  • a radio bearer such as a data radio bearer or a signaling radio bearer
  • RLC CH radio link control channel
  • the first node may learn, according to the first indication information, that the data packet received from the first bearer should be sent from the second bearer to the next-hop node of the first node. It should be noted that the second bearer between the first node and different next-hop nodes is different respectively.
  • the first node may send second indication information to the access network node, where the second indication information indicates that the first node supports the side link, or indicates that the first node supports the side link.
  • a node supports the function of sidelink communication, or instructs the first node to support a sidelink interface.
  • the first node may receive third indication information from the access network node, where the third indication information indicates enabling the sidelink of the first node, so that the first node may enable the first node according to the third indication information. The sidelink of the first node.
  • the above-mentioned first node and the second node are both IAB nodes, or the above-mentioned first node is an IAB host node (ie, the above-mentioned first node is an IAB host node).
  • the DU of the IAB host node) and the second node are the IAB nodes, or, the above-mentioned first node is the IAB node and the second node is the IAB host node (ie: the DU of the IAB host node), and the access network node is the IAB host node. (ie: the CU of the IAB host node).
  • the target node is the IAB host node (ie: the DU of the IAB host node). If the above wireless communication method is applied to downlink transmission, the target node is an access IAB node.
  • the access node refers to a node accessed by the UE.
  • an embodiment of the present application further provides a wireless communication method, and the method includes the following steps:
  • Step 301 the first node receives the second indication information from the access network node.
  • the second indication information indicates that the sidelink of the first node is enabled.
  • Step 302 the first node enables the sidelink of the first node according to the second indication information.
  • the sidelink of the first node can be enabled, so that the first node can communicate with other nodes through the sidelink interface with other nodes, which can improve the information transmission efficiency in the routing path.
  • the first node sends first indication information to the access network node, where the first indication information indicates that the first node supports the side link, or indicates that the first node supports the function of side link communication , or instruct the first node to support the sidelink interface.
  • the above-mentioned first node is an IAB node, or the above-mentioned first node is an IAB host node (ie: the DU of the IAB host node), and the access network node is an IAB host node (ie: CU of the IAB host node).
  • an embodiment of the present application further provides a wireless communication method, and the method includes the following steps:
  • Step 401 the first node receives the indication information from the access network node.
  • the indication information indicates the mapping relationship between the first bearer used by the first node to receive data packets and the second bearer used by the first node to send data packets, the first bearer is the backhaul radio link control channel, and the second bearer is the backhaul radio link control channel. is the radio bearer or radio link control channel on the side link between the first node and the next hop node of the first node.
  • Step 402 the first node sends the data packet received from the first bearer to the next hop node through the second bearer according to the indication information.
  • the first node can quickly determine the bearer of the sent data packet, so that the information transmission efficiency in the routing path can be improved.
  • the above-mentioned first node is the IAB node
  • the access network node is the IAB host node (ie: the CU of the IAB host node).
  • the nodes through which the information sent by the UE passes constitute a routing path, and how to improve the information transmission efficiency in the routing path needs to be solved at present.
  • the data packet sent from one UE needs to be sent to the user plane node of the core network through the nodes in the routing path, and then the user plane node will pass the data packet through the node.
  • a node in the routing path sends to another UE. That is to say, the transmission of the existing data packets needs to be processed by the core network nodes, and the transmission path of the data packets in this way is long, resulting in a large delay. How to reduce the transmission delay of the data packets and improve the information transmission efficiency in the routing path is the second problem to be solved by the embodiments of the present application.
  • an embodiment of the present application provides a wireless communication method. As shown in FIG. 5 , the method includes the following steps:
  • Step 501 the first node receives the identification information of the second node from the access network node.
  • the first node is a node accessed by the first UE
  • the second node is a node accessed by the second UE.
  • Step 502 the first node sends the first data packet to the second UE through the second node.
  • the first data packet carries first information and second information, the first information includes data or signaling from the first UE, and the second information includes one or more of the following: the access stratum identifier of the second UE, the first Identification information of the transmission channel, where the first transmission channel is a channel for transmitting the first information between the second UE and the second node.
  • the second information is carried in a backhaul adaptation protocol (backhaul adaptation protocol, BAP) layer header field of the first data packet.
  • BAP backhaul adaptation protocol
  • the first node may obtain the identification information of the node accessed by the second UE from the access network node, and then the first node may send a data packet to the second UE through the second node.
  • the transmission of the data packet does not need to be processed by the core network node, which can shorten the routing path of the data packet and reduce the transmission delay of the data packet, thereby improving the information transmission efficiency in the routing path.
  • the first node may send the first data packet to the third node, and then the third node sends the first data packet to the second UE through the second node, and the third node is the first data packet.
  • An intermediate node between the node and the second node for example, the third node and the second node may be directly connected, or there are other intermediate nodes between the third node and the second node.
  • FIG. 6 which is a schematic diagram of a routing path corresponding to this mode.
  • the first node may send the first data packet to the second node through the interface between the first node and the second node (such as a Uu interface or a sidelink interface), and then The second node sends the first data packet to the second UE.
  • the interface between the first node and the second node such as a Uu interface or a sidelink interface
  • the second node sends the first data packet to the second UE.
  • FIG. 7 is a schematic diagram of a routing path corresponding to this mode.
  • the first node receives the second data packet from the first UE through the second transmission channel
  • the second data packet carries the first information and the application layer identifier of the second UE
  • the second transmission channel is a channel for transmitting the first information between the first UE and the first node, and then the first node obtains the access layer identification of the second UE according to the application layer identification of the second UE, and then generates the first data according to the second data packet.
  • the application layer identifier of the second UE is carried in a medium access control (medium access control, MAC) layer header field or an RLC layer header field of the second data packet.
  • medium access control medium access control
  • the first node obtains the access layer identifier of the second UE according to the application identifier of the second UE, for example, the first node may send the application layer identifier of the second UE to the access network node, and then the first node receives the access layer identifier from the access network node.
  • the access stratum identity of the second UE of the network access node that is, the access stratum identity of the second UE is determined by the access network node according to the application layer identity of the second UE.
  • the first node obtains the identification information of the first transmission channel from the access network node. For example, if the first node sends quality of service (QoS) information corresponding to the second transmission channel to the access network device, the access network node determines the first transmission channel according to the QoS information corresponding to the second transmission channel.
  • the second transmission channel is a channel for transmitting the first information between the first UE and the first node.
  • the first node before the above step 502, the first node receives first indication information from the access network node, the first indication information instructs the first node to enable the local transfer function, and the first node enables the first indication information according to the first indication information. Functions can be delivered locally.
  • the first node before receiving the first indication information from the access network node, the first node further sends second indication information to the access network node, where the second indication information indicates that the first node supports the local transfer function.
  • the first node and the second node are both IAB nodes
  • the access network node is the IAB host node (ie: the CU of the IAB host node).
  • the gNB can adopt the Central Unit (CU)-Distributed Unit (DU) separation architecture, that is: the gNB consists of one gNB - CU and one or more gNB-DUs. Among them, the gNB-CU and the gNB-DU are connected through the F1 interface, and the gNB-CU and the fifth generation (5th generation, 5G) core network are connected through the NG interface. As shown in FIG. 8 , it is an architecture diagram of the separation of gNB-CU and gNB-DU in NR.
  • CU Central Unit
  • DU Distributed Unit
  • the gNB is a node that provides NR user plane and control plane transmission for user equipment (User Equipment, UE), and the gNB includes one or more cells.
  • the gNB is connected to the 5G core network (5G core, 5GC) through the NG interface, and is connected to other gNBs through the Xn interface.
  • the Xn-C interface is used for the transmission of control plane signaling between two gNBs
  • the Xn-U interface is used for the transmission of user plane data between the two gNBs.
  • the interface between the gNB and the UE is called the Uu interface.
  • the communication interface between the UE and the base station (eg, gNB, eNB) or the DU accessing the IAB node may be called an air interface.
  • gNB-CU is a logical node, gNB-CU includes the radio resource control (Radio Resource Control, RRC) layer of gNB, service data adaptation protocol (Service Data Adaptation Protocol, SDAP) layer and Packet Data Convergence Protocol (Packet Data Convergence Protocol) , PDCP) layer, used to control one or more gNB-DUs.
  • RRC Radio Resource Control
  • SDAP Service Data Adaptation Protocol
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • PDCP Packet Data Convergence Protocol
  • gNB-DU is a logical node, and gNB-DU includes the radio link control (Radio Link Control, RLC) layer, medium access control (medium access control, MAC) layer and physical layer (Physical layer, PHY) layer of gNB.
  • RLC Radio Link Control
  • MAC medium access control
  • PHY Physical layer
  • the UE accesses the gNB-CU through the gNB-DU, that is, the PHY/MAC/RLC layer functions equivalent to the UE are located on the gNB-DU, and the PDCP/SDAP/RRC layer functions equivalent to the UE are located on the gNB-CU.
  • FIG. 9 it is a schematic diagram of the control plane protocol stack under the gNB adopting the CU-DU separation architecture.
  • the gNB-DU encapsulates the RRC message generated by the UE in an F1 Application Protocol (F1AP) message and sends it to the gNB-CU.
  • F1AP F1 Application Protocol
  • the gNB-CU encapsulates the RRC message in the F1AP message and sends it to the gNB-DU.
  • the gNB-DU extracts the RRC message from the F1AP message and maps it to the signaling radio bearer corresponding to the Uu interface. bearer, SRB) (SRB0/SRB1/SRB2) and sent to the UE.
  • SRB signaling radio bearer
  • FIG. 10 it is a schematic diagram of the user plane protocol stack under the gNB adopting the CU-DU separation architecture.
  • the gNB-DU maps the UE data packets received from the Uu interface Data Radio Bearer (DRB) to the corresponding General Packet Radio Service (GPRS)
  • the tunneling protocol (GPRS Tunneling Protocol, GTP) is sent to the gNB-CU in the tunnel.
  • the gNB-CU maps the UE data packet to the corresponding GTP tunnel and sends it to the gNB-DU.
  • the gNB-DU extracts the UE data packet from the GTP tunnel and maps the UE data packet to the DRB corresponding to the Uu interface. sent to the UE.
  • IAB node IAB node
  • IAB donor IAB host node, or host IAB node
  • IAB donor can be a gNB, or an upgraded gNB.
  • IAB donor consists of IAB donor-CU (donor-CU for short) and IAB donor-DU (donor-DU for short)
  • IAB node consists of IAB node-MT (abbreviated as IAB-DU).
  • IAB-DU IAB node-MT
  • IAB-DU IAB node-DU
  • IAB node-MT can also be called IAB node-UE (abbreviated as IAB-UE).
  • donor-DU the function of donor-DU is similar to that of gNB-DU
  • donor-CU the function of donor-CU is similar to that of gNB-CU.
  • the IAB-DU is similar in function to the gNB-DU and is used to provide access services to its child nodes, where the child nodes of the IAB-DU can be UEs or other IAB nodes.
  • IAB-MT has the function of UE to provide data backhaul to its child nodes.
  • the IAB node can be further divided into the access IAB node and the intermediate IAB node, namely: the IAB node accessed by the UE is called the access IAB node, and the IAB node on the path between the access IAB node and the IAB donor is called the intermediate IAB node. .
  • IAB node2 As shown in Figure 11, if the UE accesses IAB node2, then the IAB node2 is called the access IAB node of the UE (or the parent node of the UE), the UE is called the child node of the IAB node2, and the link between the UE and the IAB node2 is called for the access link.
  • IAB node1 is called an intermediate IAB node, the parent node of IAB node1 is IAB donor (the child node of IAB donor is IAB node1), and the child node of IAB node1 is IAB node2 (the parent node of IAB node2 is IAB node1).
  • the link between IAB node1 and IAB node2, and the link between IAB node1 and IAB donor are called backhaul links.
  • the PHY layer, MAC layer and RLC layer equivalent to the UE are located on the access IAB node (ie: IAB2-DU), and the PDCP layer, SDAP layer and RRC layer equivalent to the UE are located on the donor-CU.
  • IAB nodes all adopt the architecture of L2 data forwarding.
  • FIG. 12 it is a schematic diagram of a control plane protocol stack for two-hop data backhaul.
  • An F1 interface is established between the access IAB node (ie: IAB2-DU) and the IAB donor (ie: donor-CU).
  • the IAB donor ie: donor-CU.
  • the F1-C interface is established between the IAB2-DU and the donor CU-CP.
  • the RRC message of the UE is encapsulated and transmitted in the F1AP message of the F1-C interface.
  • FIG. 13 it is a schematic diagram of a user plane protocol stack for two-hop data backhaul.
  • the IAB donor adopts the CP-UP separation architecture
  • an F1-U interface is established between the IAB2-DU and the donor CU-UP
  • a GTP tunnel per UE bearer is established on the F1-U interface. That is to say, each UE DRB established on the interface between the UE and the IAB2-DU corresponds to a separate GTP tunnel on the interface between the IAB2-DU and the donor CU-UP.
  • FIG. 14 it is a schematic diagram of data transmission in the two-hop data backhaul.
  • Multiple UE DRBs are established on the interface link between the UE and the IAB node2 to transmit different services of the UE.
  • Multiple backhaul RLC channels (BH RLC CH) are established on the backhaul link between IAB node2 and IAB node1 to transmit backhaul of different services of the UE.
  • multiple BH RLC CHs are also established on the backhaul link between IAB node1 and IAB donor.
  • a GTP tunnel per UE bearer is established between the IAB node2 and the IAB donor CU, and each GTP tunnel corresponds to the UE DRB on the interface between the UE and the IAB node2 one-to-one.
  • the donor-CU maps the UE PDCP protocol data unit (protocol data unit, PDU) to the corresponding GTP tunnel, and determines the target Internet protocol (internet protocol, IP) address of the UE data packet (that is, the IP address of the IAB node2 ), further encapsulate the UE data packet into an IP packet, and mark the corresponding differentiated services code point (Differentiated Services Code Point, DSCP) or flow label (flow label) in the IP header field, and fill in the target IP of the IP packet After the address, it is sent to the donor-DU through IP routing.
  • DSCP is used to identify the type of service in Internet Protocol version 4 (Internet Protocol version 4, IPv4)
  • the flow label is used to identify the type of service in Internet Protocol version 6 (Internet Protocol version 6, IPv6).
  • the donor-DU maps the received UE IP packet to the corresponding BH RLC CH according to the DSCP or flow label and the target IP address carried in the IP header, and according to the mapping relationship 1 configured by the donor-CU, and sends it to the IAB node1.
  • the mapping relationship 1 configured by the donor-CU for the donor-DU includes: the mapping relationship between the parameter and the BH RLC CH, and the parameter is composed of one or more of the following combinations, including: DSCP, flow label, and target IP address.
  • the IAB node1 maps the received UE IP packet to the corresponding BH RLC CH according to the mapping relationship 2 configured by the donor-CU and sends it to the IAB node2.
  • the mapping relationship 2 configured by the donor-CU for the IAB node1 includes: the mapping relationship between the ingress BH RLC CH (ingress BH RLC CH) and the egress BH RLC CH (egress BH RLC CH).
  • the ingress BH RLC CH is the BH RLC CH between IAB node1 and IAB donor DU
  • the egress BH RLC CH is the BH RLC CH between IAB node1 and IAB node2.
  • IAB node2 sends the received UE IP packet to the GTP layer for analysis, extracts the UE PDCP PDU from the GTP tunnel, and maps the UE PDCP PDU to the mapping relationship between the GTP tunnel and the UE DRB configured by the donor-CU. It is sent to the UE on the corresponding UE DRB.
  • the UE maps the UE PDCP PDU to the corresponding UE DRB and sends it to the IAB node2.
  • IAB node2 maps the UE PDCP PDU to the corresponding GTP tunnel according to the mapping relationship between the GTP tunnel configured by the donor-CU and the UE DRB. Then, according to the mapping relationship 3 configured by the donor-CU, IAB node2 further encapsulates the UE data packet into an IP packet, maps it to the corresponding BH RLC CH, and sends it to IAB node1.
  • the mapping relationship 3 configured by the donor-CU includes: the mapping relationship between the GTP tunnel (ie: GTP TEID and IP address) and the BH RLC CH, and the IP address is the IP address of the donor-CU.
  • IAB node1 maps the received UE IP packet to the corresponding BH RLC CH according to the mapping relationship 4 configured by the donor-CU and sends it to the donor-DU.
  • the mapping relationship 4 configured by the donor-CU for the IAB node1 includes: the mapping relationship between the ingress BH RLC CH (ingress BH RLC CH) and the egress BH RLC CH (egress BH RLC CH).
  • the ingress BH RLC CH is the BH RLC CH between IAB node2 and IAB node1
  • the egress BH RLC CH is the BH RLC CH between IAB node1 and IAB donor DU.
  • the donor-DU further routes the UE IP packet to the donor-CU according to the target IP address in the UE IP packet header (ie: the IP address of the donor-CU).
  • the donor-CU sends the IP packet to the GTP layer for analysis, it extracts the UE PDCP PDU from the GTP tunnel.
  • IAB node supports two networking methods, including spanning tree (ST) networking (refer to (a) of Figure 15) and directed acyclic graph (DAG) networking (Refer to (b) of FIG. 15 ).
  • ST spanning tree
  • DAG directed acyclic graph
  • the ST networking mode supports multi-hop, and each IAB node has only one parent node.
  • the DAG networking mode supports multi-hop and multi-connection.
  • Each IAB node can have one or two parent nodes (as shown in (a), (b) and (c) of Figure 16), but can only be connected to one IAB donor (as shown in (b) and (c) of Figure 16, subject to the constraint that one IAB-DU can only be connected to one donor-CU).
  • each IAB node includes two roles: child node and parent node.
  • IAB node1 is the child node of IAB donor and the parent node of IAB node2
  • IAB node2 is the child node of IAB node1 and the parent node of IAB node3
  • IAB node3 is the child node of IAB node2 and also the UE's parent node. parent node.
  • IAB-MT receives data or signaling and then sends it to the co-site IAB-DU for sending.
  • the IAB-DU receives the data or signaling and sends it to the co-site IAB-MT for sending.
  • IAB-node2 for downlink (DL) transmission, after IAB-MT2 receives DL data/signaling from IAB-DU1, IAB-MT2 sends it to the co-site IAB-DU2 through the internal interface, and the IAB-DU2 is sent to IAB-MT3; for uplink (UL) transmission, after IAB-DU2 receives UL data/signaling from IAB-MT3, IAB-DU2 is sent to the co-site IAB-MT2 through the internal interface, and the IAB - MT2 sends to IAB-DU1.
  • DL downlink
  • IAB-MT2 receives DL data/signaling from IAB-DU1
  • IAB-DU2 for uplink (UL) transmission, after IAB-DU2 receives UL data/signaling from IAB-MT3, IAB-DU2 is sent to the co-site IAB-MT2 through the internal interface, and the IAB - MT2 sends to IAB-DU1.
  • R16 IAB adopts the routing and bearer mapping method controlled by the IAB donor centrally.
  • a new protocol layer is introduced, namely: the backhaul adaptation protocol (BAP) layer, as shown in Figure 12 and Figure 13 above, the BAP layer is mainly used for Routing and bearer mapping for data/signaling transmission on the backhaul link.
  • BAP backhaul adaptation protocol
  • Routing refers to the need to determine the transmission path before data/signaling is transmitted, that is: through which next-hop node the data/signaling is transmitted to the target node.
  • Routing ID ⁇ -> BAP of the next hop node
  • Routing ID includes the BAP address of the target node and the path ID (path ID).
  • Donor-DU configures the mapping relationship of DSCP/flow label+IP address of access IAB node ⁇ ->Routing ID for donor-DU. That is: after the donor-DU receives the DL IP packet from the donor-CU, it determines the corresponding DL IP packet according to the DSCP/flow label value and the target IP address carried in the IP packet header field, and according to the above mapping relationship configured by the donor-CU. Routing ID, and then look up the routing table according to the Routing ID to determine the next hop node for data/signaling transmission, and carry the determined Routing ID in the BAP layer, and send it to the next hop together with the data/signaling node.
  • the intermediate IAB node receives the DL IP packet from the previous hop node, checks the routing table according to the Routing ID carried in the BAP layer, and determines the next hop node for data/signaling transmission.
  • Access IAB node For data transmission, donor-CU configures the mapping relationship of GTP FTEID ⁇ ->Routing ID for accessing IAB node; for signaling transmission, donor-CU configures signaling type for accessing IAB node Indicates the mapping relationship of ⁇ ->Routing ID, where the signaling type indication is used to indicate Non-UE associated F1AP, UE-associated F1AP. That is: after the access IAB node receives the UL IP packet from the UE, it determines the Routing ID corresponding to the data/signaling transmission according to the above mapping relationship configured by the donor-CU, and then checks the routing table according to the Routing ID to determine the data/signaling transmission. The next hop node, and carry the determined Routing ID in the BAP layer, and send it to the next hop node together with the data/signaling.
  • the intermediate IAB node receives the DL IP packet from the previous hop node, checks the routing table according to the Routing ID carried in the BAP layer, and determines the next hop node for data/signaling transmission.
  • Bearer mapping means that data/signaling is mapped to the corresponding transmission channel and sent to the next-hop node, that is, before the data/signaling is sent to the next-hop node, it is necessary to determine which transmission the data/signaling is mapped to channel (eg: BH RLC CH).
  • donor-CU needs to configure bearer mapping for donor-DU, intermediate IAB node and access IAB node respectively.
  • bearer mapping As shown in Figure 12 and Figure 13, it specifically includes:
  • Donor-DU configures the mapping relationship of DSCP/flow label+IP address of access IAB node ⁇ ->egress BH RLC CH ID for donor-DU. That is: after the donor-DU receives the DL IP packet from the donor-CU, according to the DSCP/flow label value and the target IP address carried in the IP packet header field, and according to the above mapping relationship configured by the donor-CU, it is determined that the DL IP needs to be Which corresponding egress BH RLC CH the packet is mapped to and sent to the next hop node.
  • Intermediate IAB node Donor-CU configures the mapping relationship of ingress BH RLC CH ID ⁇ ->egress BH RLC CH ID for the intermediate IAB node. That is: after the intermediate IAB node receives the DL IP packet sent by the previous hop node from the ingress BH RLC CH, it determines which corresponding egress BH RLC CH the DL IP packet needs to be mapped to according to the above mapping relationship configured by the donor-CU sent to the next hop node.
  • Donor-CU For data transmission, Donor-CU configures the mapping relationship of GTE FTEID ⁇ ->egress BH RLC CH ID for access to IAB node; for signaling transmission, Donor-CU configures for access to IAB node
  • the F1AP type indicates the mapping relationship of ⁇ -> egress BH RLC CH, where the F1AP type indication is used to indicate the Non-UE associated F1AP message and the UE-associated F1AP message. That is: after the access IAB node receives the UL IP packet from the Donor-CU, according to the above mapping relationship configured by the Donor-CU, it is determined to which corresponding egress BH RLC CH the UL IP packet needs to be mapped and sent to the next hop node .
  • Intermediate IAB node Donor-CU configures the mapping relationship of ingress BH RLC CH ID ⁇ ->egress BH RLC CH ID for the intermediate IAB node. That is: after the intermediate IAB node receives the DL IP packet sent by the previous hop node from the ingress BH RLC CH, it determines which corresponding egress BH RLC CH the DL IP packet needs to be mapped to according to the above mapping relationship configured by the donor-CU sent to the next hop node.
  • R16 IAB only supports ST and DAG networking
  • the rerouting mechanism is only limited to radio link failure (RLF) scenarios.
  • RLF radio link failure
  • the IAB-node1 After receiving the RLF indication information, if the IAB-node1 works in the dual-connection mode, the IAB-node1 will trigger the re-routing mechanism to reroute the UL data originally sent to the IAB-donor through IAB-node2 to the IAB -Send on node3, that is: send these UL data to IAB-donor through IAB-node3.
  • the existing technology only considers two simple networking forms, spanning tree and directed acyclic graph, and there is no direct communication between two peer nodes, and since an IAB node has at most two parent nodes, the rerouting mechanism is simple , that is, there is at most one candidate path available for rerouting, and there is no candidate path selection problem.
  • mesh networking is a multi-point-to-multi-point peer-to-peer network, that is, direct communication between two peer nodes is added, ensuring that any two adjacent nodes can directly communicate with each other.
  • Communication has the advantages of self-organizing network, self-healing, flexible routing, etc., which can greatly reduce the cost and complexity of network deployment, and is a trend of future network deployment.
  • two adjacent nodes can communicate directly.
  • the IAB node discovers the link RLF, there may be multiple candidate paths that can be used for rerouting.
  • the IAB node cannot know these The link quality and load conditions of the candidate paths make it impossible to select an appropriate path for rerouting.
  • the prior art does not support local switch.
  • two adjacent nodes can communicate directly, which increases the possibility of implementing local switch for data/signaling, and greatly reduces the delay of data/signaling transmission.
  • the embodiments of the present application mainly solve two problems:
  • the embodiments of this application mainly consider the IAB mesh networking scenario.
  • peer nodes for example: IAB node1 and IAB node2, IAB node3 and IAB node4, IAB node4 and IAB node5, IAB node6 and IAB node7 .
  • IAB node2 can further route DL data to IAB node6 through multiple candidate paths, which is further sent to UE by IAB node6, or IAB node4 can pass through multiple candidate paths
  • the UL data is further routed to the Donor-CU.
  • UE1 connected to IAB node6 communicates with UE2 connected to IAB node7 through local switch mode. That is, the local switch path between UE1 and UE2 is: UE1 ⁇ ->IAB node6 ⁇ ->IAB node7 ⁇ ->UE2.
  • FIG. 19 and FIG. 20 involved in the above-mentioned scenario 1 and scenario 2 of the embodiment of the present application are only for illustrating specific examples of the solutions of the embodiments of the present application, and the specific examples do not constitute the application scenarios of the embodiments of the present application. limited. In practical applications, it can also be applied to other scenarios with the same problem.
  • the first embodiment corresponds to the above-mentioned embodiment corresponding to FIG. 1 , and is used to implement selecting an appropriate rerouting node for a node of a routing path.
  • Donor-CU is abbreviated as donor-CU
  • IAB node1 is abbreviated as IAB1
  • IAB node2 is abbreviated as IAB2, and so on. Repeat.
  • the peer IAB nodes communicate through the Uu interface, which means that the DU of one IAB node and the MT of another IAB node communicate through the Uu interface.
  • the communication between the peer nodes IAB1 and IAB2 can be realized through communication between IAB1-MT and IAB2-DU, or through communication between IAB1-DU and IAB2-MT.
  • IAB2 can also send the DL data of UE1 to IAB6 through other candidate paths, and IAB6 further sends it to UE1.
  • candidate paths include but are not limited to:
  • Candidate path 1 IAB2-DU->IAB1-MT->IAB1-DU->IAB3-MT->IAB3-DU->IAB6-MT;
  • Candidate path 2 IAB2-DU->IAB1-MT->IAB1-DU->IAB3-MT->IAB3-DU->IAB4-MT->IAB4-DU->IAB6-MT;
  • IAB2 does not know the conditions of each candidate path, such as: the quality of each link on the candidate path, the load of each IAB node on the candidate path, etc., therefore, how does IAB2 select a suitable path from multiple candidate paths Rerouting downstream data?
  • IAB2 can learn the hop information of each candidate path and the load of adjacent IAB nodes, so that it can select an appropriate path for rerouting.
  • the methods for the IAB node to learn the hop count information of each candidate path include but are not limited to the following methods 1 to 2:
  • Method 1 When Donor-CU configures the routing table for the IAB node, it adds the number of hops between the next-hop node and the destination node for different routing paths, namely: Routing ID ⁇ ->BAP address of the next-hop node ⁇ -> Hop count, where the Routing ID consists of the BAP address of the target node + the path identifier path ID.
  • the Donor-CU sends the BAP address, Routing ID and hop number information of the next hop node to the IAB node.
  • the hop number information has a corresponding relationship with the BAP address and Routing ID of the next hop node, and is used to indicate the next hop node indicated by the BAP address, and the hop passed through the path indicated by the Routing ID to reach the target node indicated by the Routing ID. number.
  • the Donor-CU configures the routing table for the IAB node
  • the Donor-CU sends the Routing ID and the BAP address of the next hop node to the IAB node, and the Routing ID and the BAP address of the next hop node have a corresponding relationship.
  • the IAB node can reach the target node indicated by the Routing ID through the next hop node indicated by the BAP address through the path indicated by the Routing ID.
  • it can add the next hop node indicated by the BAP address on the basis of the existing routing table, and reach the destination node indicated by the Routing ID through the path indicated by the Routing ID. The number of hops passed.
  • the Donor-CU can add hop count information to the routing table configured for IAB2 (where the target node is IAB6):
  • Candidate path 1 Routing ID1 ⁇ ->BAP address of next hop node IAB1 ⁇ ->2 hops;
  • Candidate path 2 Routing ID2 ⁇ ->BAP address of next hop node IAB1 ⁇ ->3 hops;
  • Candidate path 3 Routing ID3 ⁇ ->BAP address of next hop node IAB5 ⁇ ->3 hops;
  • Candidate path 3 Routing ID4 ⁇ ->BAP address of next hop node IAB5 ⁇ ->2 hops.
  • the Donor-CU configures the IAB node with information on the number of hops passed through the next hop node and the path indicated by the Routing ID to reach the target node indicated by the Routing ID.
  • Donor-CU sends the information of the shortest number of hops to the target node through the next hop node to the IAB node (this method does not need to change the configuration of the routing table)
  • the Donor-CU sends the BAP address of the next hop node, the BAP address of the target node and the shortest hop number information to the IAB node, wherein the shortest hop number information and the BAP address of the next hop node and the information of the target node are
  • the BAP address has a corresponding relationship and is used to indicate the shortest number of hops passed through the next hop node to reach the target node.
  • the Donor-CU sends the following information to IAB2:
  • the above method is applied to the IAB node, that is, the IAB node obtains the hop count information of each candidate path from the Donor-CU.
  • the above method can also be applied to the Donor-DU, that is, the Donor-DU obtains the hop count information of each candidate path from the Donor-CU, so that the Donor-DU can select an appropriate next-hop node for rerouting.
  • the method for an IAB node to learn the load situation of the adjacent IAB node ((the following takes IAB2 to learn the load situation (load/interference information) of the adjacent IAB1 as an example)) methods include but are not limited to the following methods 1 to 5:
  • Method 1 The IAB1-MT reports the load/interference information to the donor-CU through the RRC message, and the donor-CU sends the load/interference information to the IAB2-DU through the F1AP message.
  • the method can be understood as: the IAB node reports the load/interference information to the donor-CU through the RRC message, and the donor-CU sends the load/interference information to the parent node or child node of the IAB node through the F1AP message.
  • Method 2 The IAB1-DU reports the load/interference information to the donor-CU through the F1AP message, and the donor-CU sends the load/interference information to the IAB2-MT through the RRC message.
  • the method can be understood as: the IAB node reports the load/interference information to the donor-CU through the F1AP message, and the donor-CU sends the load/interference information to the parent node or child node of the IAB node through the RRC message.
  • Method 3 The IAB1-MT reports the load/interference information to the donor-CU through the RRC message, and the donor-CU sends the load/interference information to the IAB2-MT through the RRC message.
  • the method can be understood as: the IAB node reports the load/interference information to the donor-CU through the RRC message, and the donor-CU sends the load/interference information to the parent node or child node of the IAB node through the RRC message.
  • Method 4 The IAB1-DU reports the load/interference information to the donor-CU through the F1AP message, and the donor-CU sends the load/interference information to the IAB2-DU through the F1AP message.
  • the method can be understood as: the IAB node reports the load/interference information to the donor-CU through the F1AP message, and the donor-CU sends the load/interference information to the parent node or child node of the IAB node through the F1AP message.
  • Method 5 BAP control PDU is used for transmission between IAB1-DU and IAB2-MT, or between IAB1-MT and IAB2-DU.
  • This method can be understood as: the IAB node sends the load/interference information to the parent node or child node of the IAB node through the BAP control PDU message.
  • IAB2 can also send the DL data of UE1 to IAB6 through other candidate paths, and IAB6 further sends it to UE1.
  • another path may exist:
  • Candidate path a IAB2-DU->IAB1-MT->IAB1-DU->IAB3-MT->IAB4-DU->IAB6-MT.
  • Candidate path b IAB2-DU->IAB5-MT->IAB5-DU->IAB7-MT->IAB6-DU.
  • This candidate path is a change to the existing mechanism.
  • the IAB-MT receives data from the DU of the parent node, it sends the data to the co-site IAB-DU through the internal interface.
  • the IAB-MT (IAB3-MT in path a or IAB7-MT in path b) receives data from the DU of the parent node instead of sending it to the co-site IAB-DU, but Send DUs of other IAB nodes. Therefore, there are changes to the data transmission implementation of the IAB node, that is, after IAB-MT receives DL data from the parent node, it needs to look at the routing information carried in the data. If the routing information can be found in the routing table, the corresponding If it is configured, it will be routed according to the routing table configuration; otherwise, the data will be sent to the co-site IAB-DU through the internal interface.
  • IAB-MT After IAB-MT receives the DL data from the parent node, it needs to look at the routing information carried in the data. If the routing information can find the corresponding configuration in the routing table, it will route according to the routing table configuration; otherwise, it will This data is sent to the co-sited IAB-DU through the internal interface.
  • the above method is applied to the IAB node, that is, the IAB node knows the load situation of the adjacent IAB node.
  • the above method can also be applied to Donor-DU, that is, Donor-DU learns the load situation of adjacent IAB nodes, so that Donor-DU can select an appropriate next-hop node for rerouting.
  • Solution 2 Communication between peer IAB nodes through the sidelink interface
  • the peer IAB nodes communicate through the sidelink interface, which means that the MT of one IAB node and the MT of another IAB node communicate through the sidelink interface, or, the DU of one IAB node and the DU of another IAB node Communication between them is through the sidelink interface.
  • the communication between the peers IAB1 and IAB2 can be realized through communication between IAB1-MT and IAB1-MT, or through communication between IAB1-DU and IAB2-DU.
  • This solution is described by taking DL transmission as an example, and the above solution is also applicable to the scenario of UL transmission, which will not be repeated here.
  • this solution takes the communication between the IAB-MT and the IAB-MT through the sidelink interface as an example for illustration, and this solution is also applicable to the scenario where the IAB-DU and the IAB-DU communicate through the sidelink interface.
  • IAB2 can also send the DL data of UE1 to IAB6 through other candidate paths, and IAB6 further sends it to UE1.
  • one candidate path is: IAB2-MT->IAB1-MT->IAB1-DU->IAB3-MT->IAB3-DU->IAB6-MT. That is: IAB2 and IAB1 communicate through the sidelink interface.
  • the upper half of Figure 23 is the protocol stack for IAB2 to route DL data through IAB4 before RLF occurs on the link between IAB2 and IAB4.
  • the lower half of Figure 23 shows the protocol stack for IAB2 to route DL data through IAB1 after RLF occurs on the link between IAB2 and IAB4, that is, a new peer-to-peer sidelink interface protocol layer is added between IAB2-MT and IAB1-MT.
  • SL PDCP is optional.
  • Method 1 The two IAB-MTs can learn the BAP address information of the peer end through the discovery process.
  • the BAP address information of the opposite end can be obtained between two IAB-MTs through sidelink interface messages.
  • the sidelink interface message may be a discover message, or an RRC setup related message (for example, an RRC setup message, an RRC setup request message, an RRC setup completion message) and the like.
  • Method 2 After the Donor-CU learns that the sidelink interface is established between IAB1 and IAB2, it notifies the BAP address of the opposite end through an RRC message or an F1AP message respectively.
  • the IAB node receives the peer's BAP address information from the Donor-CU through the RRC message or the F1AP message.
  • Donor-CU Since the BAP address of the IAB node is uniformly allocated by Donor-CU, once Donor-CU learns that a sidelink interface is established between IAB1 and IAB2, it can notify IAB2 of the BAP address of IAB1 and IAB1 of the BAP address of IAB2.
  • the BAP address is of IAB node granularity, and the IAB-MT and IAB-DU in an IAB node share the same BAP address.
  • the above method is also applicable between the donor-DU and the IAB node. That is, the communication between the donor-DU and the IAB node is through the sidelink interface.
  • the routing information of each other is exchanged through the sidelink interface (for example, an RRC message of the sidelink interface).
  • Donor-CU will configure a routing table for each IAB node in the network, namely: Routing ID ⁇ ->BAP address of the next hop node, where Routing ID is determined by the BAP address of the target node + path identification path id composition.
  • Routing ID is determined by the BAP address of the target node + path identification path id composition.
  • IAB1-MT sends the BAP address of the target node to IAB2-MT, where the BAP address of the target node includes the BAP address of IAB6.
  • IAB2-MT After IAB2-MT receives it, it can learn that IAB6 can be reached through IAB1, and save the corresponding relationship between the BAP address of the next hop node IAB1 and the BAP address of the target node IAB6. That is, the IAB node can send the BAP address list information (including the BAP addresses of one or more target nodes) of the target nodes reachable by the IAB node to the communication peer IAB node through the sidelink interface.
  • the IAB1-MT may also send the information on the shortest number of hops experienced to reach the target node to the IAB2-MT. That is to say, the IAB node can send the following information to the communication peer IAB node through the sidelink interface, including: the BAP address of the target node reachable by the IAB node, and the information on the shortest number of hops experienced to reach the target node.
  • the above method is also applicable between the donor-DU and the IAB node. That is, the communication between the donor-DU and the IAB node is through the sidelink interface.
  • the Donor-CU sends the mapping relationship between the ingress BH RLC CH and the egress sidelink DRB/RLC CH to the IAB2.
  • the Donor-CU sends the mapping relationship between the BH RLC CH on the Uu interface and the DRB or RLC CH on the sidelink interface to the IAB node.
  • the IAB node may send an indication to the Donor-CU, which is used to indicate that the IAB node supports the sidelink interface.
  • the Donor-CU sends an indication information to the IAB node, and the indication information is used to instruct the IAB node to enable or disable the sidelink interface/transmission function.
  • the donor-DU reports to the donor-CU whether it supports the sidelink interface, and receives from the donor-CU whether the sidelink interface of the donor-DU is enabled or not.
  • the above embodiment mainly solves how the IAB node selects a suitable path for data/signaling rerouting, so that the IAB node can select the optimal path for rerouting in the scenario of multiple candidate paths, so as to ensure the QoS requirements of data/signaling transmission.
  • the second embodiment corresponds to the above-mentioned embodiment corresponding to FIG. 5 , and is used to implement local transfer between nodes.
  • UE1 and UE2 can transmit data through the local switch mode.
  • UE1 accessing IAB6 and UE2 accessing IAB7 as an example to illustrate, UE1 and UE2 conduct data transmission through local switch mode, referring to The point is that the data communicated between UE1 and UE2 is directly realized through the communication between IAB6 and IAB7, and does not need to be forwarded through Donor-CU or core network UPF.
  • the local switch process in the IAB mesh networking scenario is shown in Figure 25, including the following steps:
  • Step 2501 UE1 sends a UL data packet to IAB6, where the UL data packet carries the application layer identifier of UE2.
  • the application layer refers to the IP layer and the layers above the IP layer.
  • This UL data packet needs to be sent to UE2.
  • the application layer of UE1 After the application layer of UE1 generates a data packet sent to UE2, and sends the data packet to the access stratum (AS) of UE1 (ie SDAP layer, PDCP layer, RLC layer, MAC layer, PHY layer) ), sent by the AS layer of UE1 to IAB6 through the air interface.
  • the data packet carries the application layer identifier of UE2.
  • the application layer identifier of the UE2 may be carried in the MAC layer header field or the RLC layer header field.
  • UE1 can perceive the application layer identifier of UE2, but does not perceive the AS layer identifier of UE2.
  • Step 2502 the IAB6 sends an RRC message or an F1AP message to the Donor-CU, and the message carries at least one of the following information: the AS layer identifier of the UE1, the application layer identifier of the UE2, and the QoS information corresponding to the data.
  • the QoS information corresponding to the data may be, for example, the DRB ID of UE1, or a QoS flow identifier (QoS Flow ID, QFI).
  • the AS layer identity of UE1 is the identity of the cell accessed by UE1 (such as Physical Cell Identifier (PCI)) + the unique identity of UE1 in the access cell (such as Cell Radio Network Temporary Identifier, C -RNTI)), or composed of Cell Global Identification (CGI) + UE1's unique identification in the access cell (such as C-RNTI).
  • PCI Physical Cell Identifier
  • C -RNTI Cell Radio Network Temporary Identifier
  • CGI Cell Global Identification
  • Donor-CU learns the AS layer identification of UE2 according to the application layer identification of UE2, and learns the access node identification of UE2 (for example: the BAP address of IAB7), and learns the DRB ID corresponding to UE2 according to the QoS information corresponding to the data . Then send an RRC message or an F1AP message to IAB6, which carries at least one of the following information: the AS layer identifier of UE2, the BAP address of IAB7, the DRB ID of UE2, and the indication information of the enable local switch.
  • the Donor-CU sends the indication information of the enable local switch to the access IAB node, the indication information has a corresponding relationship with the DRB ID (the DRB indicated by the DRB ID is used to transmit the data of UE1), and the indication information is used to indicate Initiate a local switch operation for the data transmitted on the DRB.
  • the indication information is used to indicate Initiate a local switch operation for the data transmitted on the DRB.
  • IAB6 receives the indication information of enable local switch, it can know that the data packet needs to perform the local switch operation. Therefore, when the UL data from UE1 is subsequently received through the same DRB, the local switch operation will be performed.
  • the Donor-CU also sends at least one of the following information to the access IAB node: the AS layer identifier of the UE2, the BAP address information of the access node of the UE2, and the DRB identifier corresponding to the air interface transmission of the data packet in the UE2.
  • the implementation of this step has a premise, that is: the Donor-CU needs to save the UE's application layer identity and the UE's AS layer identity (for example: Physical cell identifier (Physical cell Identifier, PCI) or Cell Global Identification (CGI) ) + the mapping relationship of Cell Radio Network Temporary Identifier (C-RNTI)).
  • PCI Physical cell identifier
  • CGI Cell Global Identification
  • the Donor-CU can learn and save the application layer identifier of the UE and the AS layer of the UE during the process of initiating a service or during the process of establishing a protocol data unit (PDU) session by the UE. logo.
  • PDU protocol data unit
  • Step 2504 IAB6 sends UL data to IAB7 according to the BAP address of IAB7, and the UL data packet carries the AS layer identifier of UE2 and the DRB ID of UE2.
  • IAB6 determines to route the UL data locally according to the indication information of the enable local switch, that is, the UL data is routed to IAB7, which is further sent to UE2 by IAB7.
  • IAB7 receives the UL data packet from IAB6, in order to let IAB7 know which UE the UL data packet is sent to and through which DRB it is sent to the UE, therefore, when IAB6 sends the UL data packet to IAB7, IAB6 carries it in the BAP layer
  • the access IAB node of UE1 sends at least one of the following information to the access IAB node of UE2: the AS layer identifier of UE2, and the DRB identifier corresponding to the air interface transmission of the data packet in UE2.
  • the information can be carried in the BAP layer and sent.
  • Step 2505 the IAB7 sends the UL data packet to the UE2 according to the AS layer identifier of the UE2 and the DRB ID of the UE2.
  • the UE sends the application layer identifier of the communication peer UE to the access IAB node.
  • the application layer identifier of the communication peer UE may be carried in the MAC layer header field or the RLC layer header field.
  • the access IAB node sends at least one of the following information to the Donor-CU: the AS layer identifier of the local UE, the application layer identifier of the peer UE, and the QoS information corresponding to the data.
  • the AS layer identifier of the local UE is composed of the cell identifier PCI accessed by the local UE or CGI+the unique identifier C-RNTI of the local UE in the access cell.
  • the QoS information corresponding to the data is the air interface DRB identifier mapped to the data transmission or the QFI corresponding to the data.
  • the Donor-CU sends the indication information of enable local switch to the access IAB node, the indication information corresponds to the DRB corresponding to the data sent by the local UE, and is used to instruct the data transmitted on the DRB to start the local switch operation.
  • the Donor-CU also sends at least one of the following information to the access IAB node: the AS layer identifier of the peer UE, the BAP address information of the access node of the peer UE, and the data packet corresponding to the air interface transmission of the peer UE.
  • DRB logo The access IAB node carries the following information in the BAP layer: the AS layer identifier of the peer UE, and the DRB identifier corresponding to the air interface transmission of the data packet in the peer UE.
  • This embodiment mainly solves the local switch in the IAB mesh scenario, reduces the time delay of data transmission, and ensures normal data transmission between two communicating UEs.
  • FIG. 26 it is a schematic diagram of a communication apparatus according to an embodiment of the present application.
  • the communication apparatus is used to implement each step corresponding to the first node or the access network node in the above embodiments.
  • the communication apparatus 2600 includes a sending unit 2610 , a receiving unit 2620 and a processing unit 2630 .
  • the communication device is configured to implement the steps corresponding to the first node in the foregoing embodiments:
  • a receiving unit 2620 configured to acquire first information, where the first information includes at least one of the following: load information of at least one next-hop node of the first node, interference information of the at least one next-hop node, the Channel quality between the first node and the at least one next-hop node, information on the number of link hops from the first node to the target node through the at least one next-hop node; the processing unit 2630 is configured to, according to the The first information is used to determine that the data packet is transmitted through the second node, wherein the at least one next-hop node includes the second node.
  • the receiving unit 2620 is further configured to receive the load information of the at least one next-hop node and/or the interference information of the at least one next-hop node from the access network node ; Or, receive the load information of the first next hop node and/or the interference information of the first next hop node from the first next hop node, and the first next hop node is the at least one Any node in a next-hop node.
  • the receiving unit 2620 is further configured to receive the channel quality between the first node and the at least one next-hop node from the access network node; or, the processing The unit 2630 is further configured to automatically determine the channel quality between the first node and the at least one next-hop node.
  • the receiving unit 2620 is further configured to receive the link hop count information from an access network node, where the link hop count information and the routing identifier and the next The identification information of the hop node corresponds, and the routing identification includes the identification information of the target node and the path identification.
  • the receiving unit 2620 is further configured to receive the link hop count information from the access network node, where the link hop count indicated by the link hop count information is the The minimum link hop count for the first node to reach the target node through the next hop node, and the link hop count information corresponds to the identification information of the next hop node and the identification information of the target node.
  • the receiving unit 2620 is further configured to receive the identification information of the first next-hop node from the first next-hop node, where the first next-hop node is the Any one of at least one next-hop node.
  • the receiving unit 2620 configured to receive the identification information of the first next-hop node from the first next-hop node, specifically includes: using the first node to communicate with The sidelink between the first next hop nodes receives the identification information of the first next hop node from the first next hop node.
  • the receiving unit 2620 is further configured to receive, from the first next-hop node, identification information of a target node that can be reached by the first next-hop node.
  • the receiving unit 2620 is further configured to receive the minimum link hop from the first next-hop node to the reachable target node from the first next-hop node number information.
  • the receiving unit 2620 is further configured to receive first indication information from an access network node, where the first indication information instructs the first node to receive the first indication of the data packet a mapping relationship between a bearer and a second bearer through which the first node sends the data packet, the first bearer is a backhaul radio link control channel, and the second bearer is the first node and the second bearer A radio bearer or radio link control channel on the sidelink between at least one next-hop node.
  • the sending unit 2610 is configured to send second indication information to an access network node, where the second indication information indicates that the first node supports a sidelink.
  • the receiving unit 2620 is further configured to receive third indication information from the access network node, where the third indication information indicates enabling the sidelink of the first node road.
  • the first node and the second node are both IAB nodes, and the target node is an IAB host node or an access IAB node; or, the first node is an IAB host node , the second node is an IAB node, and the target node is an access IAB node.
  • the communication device is configured to implement the steps corresponding to the first node in the foregoing embodiments:
  • the receiving unit 2620 is configured to receive second indication information from the access network node, where the second indication information indicates enabling the sidelink of the first node; the processing unit 2630 is configured to receive the second indication according to the second indication information to enable the sidelink of the first node.
  • the sending unit 2610 is configured to send the first indication information to the access network node before the receiving unit 2620 receives the second indication information from the access network node, where the The first indication information indicates that the first node supports sidelinks.
  • the first node is an IAB node
  • the access network node is an IAB host node.
  • the communication device is configured to implement the steps corresponding to the first node in the foregoing embodiments:
  • a receiving unit 2620 configured to receive indication information from an access network node, where the indication information indicates a first bearer for the first node to receive a data packet and a second bearer for the first node to send the data packet
  • the first bearer is the backhaul radio link control channel
  • the second bearer is the side link between the first node and the next hop node of the first node.
  • the processing unit 2630 is configured to send the data packet received from the first bearer to the next hop through the second bearer according to the indication information node.
  • the communication device is configured to implement the steps corresponding to the first node in the foregoing embodiments:
  • a receiving unit 2620 configured to receive identification information of a second node from an access network node, where the first node is a node accessed by the first user equipment UE, and the second node is a node accessed by the second UE;
  • a sending unit 2610 configured to send a first data packet to the second UE through the second node, where the first data packet carries first information and second information, and the first information includes information from the first The data or signaling of the UE, and the second information includes one or more of the following: the access stratum identity of the second UE, and the identity information of the first transmission channel, and the first transmission channel is the second transmission channel.
  • the sending unit 2610 is specifically configured to: send the first data packet to the second node, and the second node is configured to send the first data packet to the the second UE; or, sending the first data packet to a third node, where the third node is configured to send the first data packet to the second UE through the second node, and the first data packet is sent to the second UE through the second node.
  • Three nodes are intermediate nodes between the first node and the second node.
  • the receiving unit 2620 is further configured to receive the second data from the first UE through the second transmission channel before receiving the identification information of the second node from the access network node packet, the second data packet carries the first information and the application layer identifier of the second UE, and the second transmission channel is the transmission between the first UE and the first node. information channel; the processing unit 2630 is configured to acquire the access layer identifier of the second UE according to the application layer identifier of the second UE.
  • the processing unit 2630 is specifically configured to: send the application layer identifier of the second UE to the access network node through the sending unit 2610; receive through the receiving unit 2620 The access stratum identity of the second UE from the access network node.
  • the application layer identifier of the second UE is carried in a medium access control MAC layer header field or a radio link control RLC layer header field of the second data packet.
  • the receiving unit 2620 is further configured to receive the identification information of the first transmission channel from the access network node.
  • the second information is carried in the BAP layer header field of the backhaul adaptation protocol of the first data packet.
  • the receiving unit 2620 is further configured to receive first indication information from the access network node, where the first indication information instructs the first node to enable the local transfer function.
  • the sending unit 2610 is further configured to send a second indication to the access network node before the receiving unit 2620 receives the first indication information from the access network node information, the second indication information indicates that the first node supports the local delivery function.
  • the first node and the second node are both IAB nodes, and the access network node is an IAB host node.
  • the communication device is used to implement the steps corresponding to the access network node in the above embodiments:
  • the receiving unit 2620 is configured to receive the application layer identifier of the second UE from the first node, where the first node is the node accessed by the first UE; the processing unit 2630 is configured to receive the application layer identifier of the second UE according to the first node. , determine the access stratum identity of the second UE; the sending unit 2610 is configured to send the access stratum identity of the second UE and the identity information of the second node to the first node, wherein the second UE The node is a node accessed by the second UE.
  • the sending unit 2610 is further configured to send identification information of a first transmission channel to the first node, where the first transmission channel is the second UE and the A channel for transmitting data packets from the first UE between the second nodes.
  • the sending unit 2610 is further configured to send first indication information to the first node, where the first indication information instructs the first node to enable the local transfer function.
  • the receiving unit 2620 is further configured to receive the second indication from the first node before the sending unit 2610 sends the first indication information to the first node information, the second indication information indicates that the first node supports the local delivery function.
  • both the first node and the second node are IAB nodes.
  • the above-mentioned communication device may also include a storage unit, which is used to store data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or be coupled with the storage unit to implement corresponding methods or functions.
  • the processing unit 2630 may read data or instructions in the storage unit, so that the communication apparatus implements the methods in the above embodiments.
  • each unit in the above communication apparatus can all be implemented in the form of software calling through the processing element; also can all be implemented in the form of hardware; some units can also be implemented in the form of software calling through the processing element, and some units can be implemented in the form of hardware.
  • each unit can be a separately established processing element, or can be integrated in a certain chip of the communication device to realize, in addition, it can also be stored in the memory in the form of a program, which can be called and executed by a certain processing element of the communication device. function of the unit.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • a unit in any of the above communication devices may be one or more integrated circuits configured to implement the above method, such as: one or more application specific integrated circuits (ASICs), or, an or multiple microprocessors (digital singnal processors, DSP), or, one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms.
  • ASICs application specific integrated circuits
  • DSP digital singnal processors
  • FPGA field programmable gate arrays
  • a unit in the communication device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can invoke programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the communication apparatus includes: a processor 2710 and an interface 2730 , and optionally, the communication apparatus further includes a memory 2720 .
  • the interface 2730 is used to enable communication with other devices.
  • the method performed by the first node or the access network node in the above embodiment may be implemented by the processor 2710 calling a program stored in a memory (which may be the memory 2720 in the first node or the access network node, or an external memory) . That is, the first node or the access network node may include a processor 2710, and the processor 2710 executes the method performed by the first node or the access network node in the above method embodiments by invoking the program in the memory.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the first node or access network node may be implemented by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessor DSPs, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.
  • the functions/implementation process of the sending unit 2610, the receiving unit 2620 and the processing unit 2630 in FIG. 26 can be implemented by the processor 2710 in the communication apparatus 2700 shown in FIG. 27 calling the computer executable instructions stored in the memory 2720 .
  • the function/implementation process of the processing unit 2630 in FIG. 26 can be implemented by the processor 2710 in the communication device 2700 shown in FIG. 27 calling the computer-executed instructions stored in the memory 2720, the sending unit 2610 in FIG. 26 and the receiving unit 2610 in FIG.
  • the function/implementation process of the unit 2620 can be realized through the interface 2730 in the communication device 2700 shown in FIG. 27 .
  • the function/implementation process of the sending unit 2610 and the receiving unit 2620 can be invoked by the processor through the program in the memory
  • the instructions are implemented in the driver interface 2730.
  • At least one item (single, species) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple.
  • “Plurality" means two or more, and other quantifiers are similar.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program 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, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.
  • a general-purpose processor may be a microprocessor, or alternatively, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration. accomplish.
  • the steps of the method or algorithm described in the embodiments of this application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • Software units can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or this.
  • RAM Random Access Memory
  • ROM read-only memory
  • EPROM memory read-only memory
  • EEPROM memory electrically erasable programmable read-only memory
  • registers hard disk, removable disk, CD-ROM or this.
  • a storage medium may be coupled to the processor such that the processor may read information from, and store information in, the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and storage medium may be provided in the ASIC.
  • the above-described functions described herein may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on, or transmitted over, a computer-readable medium in the form of one or more instructions or code.
  • Computer-readable media includes computer storage media and communication media that facilitate the transfer of a computer program from one place to another. Storage media can be any available media that a general-purpose or special-purpose computer can access.
  • Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other media in the form of program code that can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly defined as a computer-readable medium, for example, if software is transmitted from a website site, server or other remote source over a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless, and microwave are also included in the definition of computer-readable media.
  • DSL digital subscriber line
  • the discs and magnetic discs include compact discs, laser discs, optical discs, digital versatile discs (English: Digital Versatile Disc, DVD for short), floppy discs and Blu-ray discs. Disks usually reproduce data magnetically, while Discs usually use lasers to optically reproduce data. Combinations of the above can also be included in computer readable media.
  • the functions described in this application may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供无线通信方法、通信装置及通信系统。该方法包括：第一节点获取第一信息，第一信息包括以下至少一种：第一节点的至少一个下一跳节点的负载信息、至少一个下一跳节点的干扰信息、第一节点与至少一个下一跳节点之间的信道质量、第一节点通过至少一个下一跳节点到达目标节点的链路跳数信息；第一节点根据第一信息确定通过第二节点进行数据包的传输，该至少一个下一跳节点包括第二节点。该方案，第一节点基于该第一节点的一个或多个下一跳节点的信息，从该第一节点的下一跳节点中选择一个进行数据包(如数据或信令)的传输的节点。该方法能够实现为第一节点选择一个合适的下一跳节点，可以提高路由路径中的信息传输效率。

Description

无线通信方法、通信装置及通信系统 技术领域
本申请实施例涉及通信技术领域，尤其涉及无线通信方法、通信装置及通信系统。
背景技术
在无线通信中，用户设备(user equipment，UE)之间的通信时，一个UE发送的信息需要经过无线网络中的一个或多个节点的路由转发，到达另一个UE。
UE发送的信息所经过的节点构成一个路由路径，如何提高路由路径中的信息传输效率，是目前需要解决的。
发明内容
本申请实施例提供无线通信方法、通信装置及通信系统，以提高路由路径中的信息传输效率。
第一方面，本申请实施例提供一种无线通信方法，包括：第一节点获取第一信息，所述第一信息包括以下至少一种：所述第一节点的至少一个下一跳节点的负载信息、所述至少一个下一跳节点的干扰信息、所述第一节点与所述至少一个下一跳节点之间的信道质量、所述第一节点通过所述至少一个下一跳节点到达目标节点的链路跳数信息；所述第一节点根据所述第一信息，确定通过第二节点进行数据包的传输，其中，所述至少一个下一跳节点包括所述第二节点。
基于上述方案，第一节点基于该第一节点的一个或多个下一跳节点的信息，从该第一节点的下一跳节点中选择一个进行数据包(如数据或信令)的传输的节点。该方法能够实现为第一节点选择一个合适的下一跳节点，可以提高路由路径中的信息传输效率。
在一种可能的实现方法中，所述第一节点接收来自接入网节点的所述至少一个下一跳节点的负载信息和/或所述至少一个下一跳节点的干扰信息；或者，所述第一节点接收来自第一下一跳节点的所述第一下一跳节点的负载信息和/或所述第一下一跳节点的干扰信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的所述第一节点与所述至少一个下一跳节点之间的信道质量；或者，所述第一节点自行确定所述第一节点与所述至少一个下一跳节点之间的信道质量。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的所述链路跳数信息，其中，所述链路跳数信息与路由标识以及所述下一跳节点的标识信息对应，所述路由标识包括所述目标节点的标识信息和路径标识。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的所述链路跳数信息，其中，所述链路跳数信息指示的链路跳数为所述第一节点通过所述下一跳节点到达所述目标节点的最小链路跳数，所述链路跳数信息与所述下一跳节点的标识信息以及所述目标节点的标识信息对应。
在一种可能的实现方法中，所述第一节点接收来自第一下一跳节点的所述第一下一跳 节点的标识信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
在一种可能的实现方法中，所述第一节点接收来自第一下一跳节点的所述第一下一跳节点的标识信息，包括：
所述第一节点通过所述第一节点与所述第一下一跳节点之间的侧行链路接收来自所述第一下一跳节点的所述第一下一跳节点的标识信息。
在一种可能的实现方法中，所述第一节点接收来自所述第一下一跳节点的所述第一下一跳节点能够到达的目标节点的标识信息。
在一种可能的实现方法中，所述第一节点接收来自所述第一下一跳节点的所述第一下一跳节点到达所述能够到达的目标节点的最小链路跳数信息。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的第一指示信息，所述第一指示信息指示所述第一节点接收所述数据包的第一承载与所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述至少一个下一跳节点之间的侧行链路上的无线承载或无线链路控制信道。
在一种可能的实现方法中，所述第一节点向所述接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持侧行链路。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的第三指示信息，所述第三指示信息指示使能所述第一节点的侧行链路。
在一种可能的实现方法中，所述第一节点和所述第二节点均为IAB节点，所述目标节点为IAB宿主节点或接入IAB节点；或者，所述第一节点为IAB宿主节点，所述第二节点为IAB节点，所述目标节点为接入IAB节点。
第二方面，本申请实施例提供一种无线通信方法，包括：第一节点接收来自接入网节点的第二指示信息，所述第二指示信息指示使能所述第一节点的侧行链路；第一节点根据所述第二指示信息，使能所述第一节点的侧行链路。
基于上述方案，可以使能第一节点的侧行链路，从而第一节点可以通过与其它节点之间的侧行链路接口与其它节点通信，可以提高路由路径中的信息传输效率。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的第二指示信息之前，所述第一节点向所述接入网节点发送第一指示信息，所述第一指示信息指示所述第一节点支持侧行链路。
在一种可能的实现方法中，所述第一节点为IAB节点，所述接入网节点为IAB宿主节点。
第三方面，本申请实施例提供一种无线通信方法，包括：第一节点接收来自接入网节点的指示信息，所述指示信息指示用于所述第一节点接收数据包的第一承载与用于所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述第一节点的下一跳节点之间的侧行链路上的无线承载或无线链路控制信道；所述第一节点根据所述指示信息，将从所述第一承载收到的所述数据包，通过所述第二承载发送至所述下一跳节点。
基于上述方案，第一节点可以快速确定发送数据包的承载，从而可以提高路由路径中的信息传输效率。
第四方面，本申请实施例提供一种无线通信方法，包括：第一节点接收来自接入网节 点的第二节点的标识信息，所述第一节点为第一用户设备UE接入的节点，所述第二节点为第二UE接入的节点；所述第一节点通过所述第二节点向所述第二UE发送第一数据包，所述第一数据包携带第一信息和第二信息，所述第一信息包括来自所述第一UE的数据或信令，所述第二信息包括以下一项或多项：所述第二UE的接入层标识、第一传输通道的标识信息，所述第一传输通道为所述第二UE与所述第二节点之间传输所述第一信息的通道。
基于上述方案，第一节点可以从接入网节点获得与第二UE接入的节点的标识信息，然后第一节点可以通过该第二节点向第二UE发送数据包。相较于现有技术，可以缩短数据包的路由路径，减少数据包的传输时延，从而提高路由路径中的信息传输效率。
在一种可能的实现方法中，所述第一节点通过所述第二节点向所述第二UE发送第一数据包，包括：所述第一节点向所述第二节点发送所述第一数据包，所述第二节点用于将所述第一数据包发送至所述第二UE；或者，所述第一节点向第三节点发送所述第一数据包，所述第三节点用于通过所述第二节点将所述第一数据包发送至所述第二UE，所述第三节点为所述第一节点与所述第二节点之间的中间节点。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的第二节点的标识信息之前，所述第一节点通过第二传输通道接收来自所述第一UE的第二数据包，所述第二数据包携带所述第一信息和所述第二UE的应用层标识，所述第二传输通道为所述第一UE与所述第一节点之间传输所述第一信息的通道；所述第一节点根据所述第二UE的应用层标识，获取所述第二UE的接入层标识。
在一种可能的实现方法中，所述第一节点根据所述第二UE的应用标识，获取所述第二UE的接入层标识，包括：所述第一节点向所述接入网节点发送所述第二UE的应用层标识；
所述第一节点接收来自所述接入网节点的所述第二UE的接入层标识。
在一种可能的实现方法中，所述第二UE的应用层标识携带于所述第二数据包的媒体接入控制MAC层头字段或无线链路控制RLC层头字段中。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的所述第一传输通道的标识信息。
在一种可能的实现方法中，所述第二信息携带于所述第一数据包的回传适配协议BAP层头字段中。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
在一种可能的实现方法中，所述第一节点接收来自所述接入网节点的第一指示信息之前，所述第一节点向所述接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
在一种可能的实现方法中，所述第一节点和所述第二节点均为IAB节点，所述接入网节点为IAB宿主节点。
第五方面，本申请实施例提供一种无线通信方法，包括：接入网节点接收来自第一节点的第二UE的应用层标识，所述第一节点为第一UE接入的节点；所述接入网节点根据所述第二UE的应用层标识，确定所述第二UE的接入层标识；所述接入网节点向所述第一节点发送所述第二UE的接入层标识以及第二节点的标识信息，其中，所述第二节点为 所述第二UE接入的节点。
基于上述方案，第一节点可以从接入网节点获得与第二UE接入的节点的标识信息，然后第一节点可以通过该第二节点向第二UE发送数据包。相较于现有技术，可以缩短数据包的路由路径，减少数据包的传输时延，从而提高路由路径中的信息传输效率。
在一种可能的实现方法中，所述接入网节点向所述第一节点发送第一传输通道的标识信息，其中，所述第一传输通道为所述第二UE与所述第二节点之间传输来自所述第一UE的数据包的通道。
在一种可能的实现方法中，所述接入网节点向所述第一节点发送第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
在一种可能的实现方法中，所述接入网节点向所述第一节点发送所述第一指示信息之前，所述接入网节点接收来自所述第一节点的第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
在一种可能的实现方法中，所述第一节点和所述第二节点均为IAB节点，所述接入网节点为IAB宿主节点。
第六方面，本申请实施例提供一种通信装置，该装置可以是第一节点，还可以是用于第一节点的芯片。该装置具有实现上述第一方面至第四方面的任意可能的实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请实施例提供一种通信装置，该装置可以是接入网节点，还可以是用于接入网节点的芯片。该装置具有实现上述第五方面的任意可能的实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，本申请实施例提供一种通信装置，包括处理器，处理器与存储器耦合，存储器用于存储程序或指令，当程序或指令被处理器执行时，使得该装置实现上述第一方面至第五方面的任意可能的实现方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
第九方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面至第五方面的任意可能的实现方法的各个步骤的单元或手段(means)。
第十方面，本申请实施例提供一种通信装置，包括处理器和接口电路，所述处理器用于控制接口电路与其它装置通信，并执行上述第一方面至第五方面的任意可能的实现方法。该处理器包括一个或多个。
第十一方面，本申请实施例还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述第一方面至第五方面的任意可能的实现方法。
第十二方面，本申请实施例还提供一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面至第五方面的任意可能的实现方法。
第十三方面，本申请实施例还提供一种芯片系统，包括处理器，处理器与存储器耦合，存储器用于存储程序或指令，当程序或指令被处理器执行时，使得该芯片系统实现上述第一方面至第五方面的任意可能的实现方法。该存储器可以位于该芯片系统之内，也可以位于该芯片系统之外。且该处理器包括一个或多个。
第十四方面，本申请实施例还提供一种通信系统，包括用于执行上述第四方面的任意 可能的实现方法的第一节点和用于执行上述第五方面的任意可能的实现方法的接入网节点。
附图说明
图1为本申请实施例提供的一种无线通信方法示意图；
图2为路由路径示意图；
图3为本申请实施例提供的一种无线通信方法示意图；
图4为本申请实施例提供的一种无线通信方法示意图；
图5为本申请实施例提供的一种无线通信方法示意图；
图6为路由路径示意图；
图7为路由路径示意图；
图8为NR中gNB-CU和gNB-DU分离架构图；
图9为gNB采用CU-DU分离架构下的控制面协议栈示意图；
图10为gNB采用CU-DU分离架构下的用户面协议栈示意图；
图11为两跳数据回传场景示意图；
图12为两跳数据回传的控制面协议栈示意图；
图13为两跳数据回传的用户面协议栈示意图；
图14为两跳数据回传中的数据传输示意图；
图15为组网方式示意图；
图16为组网方式示例图；
图17为节点关系示例图；
图18为无线链路失败示例图；
图19为节点通信示意图；
图20为节点通信示意图；
图21为IAB mesh组网场景示意图；
图22为IAB mesh组网场景示意图；
图23为DL数据传输协议栈；
图24为local switch方式进行数据传输示意图；
图25为IAB mesh组网场景下的local switch流程图；
图26为本申请实施例提供的一种通信装置示意图；
图27为本申请实施例提供的一种通信装置示意图。
具体实施方式
如背景技术介绍，UE发送的信息所经过的节点构成一个路由路径，如何提高路由路径中的信息传输效率，是目前需要解决的。其中，在某些情况下，如节点之间的链路异常或节点自身故障等原因，导致路由路径中的某个节点无法将信息正常路由至该节点的下一跳节点或UE，此时该节点需要选择重路由的节点。如何为节点选择合适的重路由的节点，以提高路由路径中的信息传输效率，是本申请实施例所要解决的第一个问题。又或者，在分布式路由场景下，各节点自行决定数据包的下一跳节点，如何为节点选择合适的下一跳 节点也是本申请实施例所要解决的问题，也就是说，无论是数据包的路由还是重路由，如何为节点选择合适的下一跳节点是本申请实施例所要解决的问题。为了方便描述，本申请实施例以数据包的重路由为例进行说明，本申请实施例的方案同样适用于数据包的路由场景，就不再赘述。
为解决上述问题，本申请实施例提供一种无线通信方法，如图1所示，该方法包括以下步骤：
步骤101，第一节点获取第一信息。
第一节点是路由路径中除目标节点之外的任意一个节点。目标节点指的是接收端UE所接入的节点。
其中，该第一信息包括以下至少一种：
1)第一节点的至少一个下一跳节点的负载信息；
一个节点的负载信息可以用来反映该节点的资源占用情况。一般情况下，一个节点的负载越重，该节点的资源占用越多，因此该节点的路由效率越低。因而一般会选择负载相对较轻的节点进行路由。所谓路由指的是为数据包选择合适的传输路径进行传输。
2)第一节点的至少一个下一跳节点的干扰信息；
一个节点的干扰信息可以用于反应该节点的链路质量状况。一般情况下，一个节点的干扰越大，该节点的链路质量越差容易导致丢包。因而一般会选择干扰相对较轻的节点进行路由。
3)第一节点与至少一个下一跳节点之间的信道质量；
第一节点与第一节点的下一跳节点之间的信道质量可以用来反映第一节点与第一节点的下一跳节点之间的信息传输质量。一般情况下，信道质量越好，信息传输质量越好。因而一般会选择信道质量相对较好的节点进行路由。
4)第一节点通过至少一个下一跳节点到达目标节点的链路跳数信息。
链路跳数信息用于表示路由路径中经过的节点数量，每个节点即为一跳。一般地，跳数越少，则传输时延越小，信息可以越快的到达目标节点。因而一般选择链路跳数相对较少的节点进行路由。
步骤102，第一节点根据第一信息，确定通过第二节点进行数据包的传输，其中，该至少一个下一跳节点包括第二节点。
可选的，数据包的传输包括数据包的路由，或者，数据包的重路由。以重路由为例进行说明，基于上述方案，第一节点基于该第一节点的一个或多个下一跳节点的信息，从该第一节点的下一跳节点中选择一个进行数据包(如数据或信令)的重路由的节点。该方法能够实现为第一节点选择一个合适的下一跳节点，可以提高路由路径中的信息传输效率。
示例性地，参考图2，为路由路径示意图。节点1(也称为第一节点)与节点1在路由路径中的下一跳节点(即节点4)之间发生链路故障，则节点1需要选择重路由的下一跳节点。也就是说，数据包的原路径为节点1通过节点4到达目标节点1，一旦节点1和节点4之间的链路发生故障，导致数据包的原路径无法继续进行数据传输，则节点1需要为该数据包选择新的路径进行传输(即重路由)。该示例中，节点1包含3个下一跳节点，即节点2、节点3和节点5，也就是说，节点1可以分别通过节点2或节点3或节点5到 达目标节点1。节点1根据第一信息，选择用于数据包的重路由的下一跳节点是节点3(也称为第二节点)。
下面介绍第一节点获取第一信息的不同实现方法。
需要说明的是，本申请实施例以下描述中，接入网节点是用于对路由路径中的节点进行管理、控制的节点。一个节点的标识信息可以是该节点的地址信息(如回传适配协议(backhaul adaptation protocol，BAP)地址或互联网协议(Internet Protocol，IP)地址等)或该节点的标识(ID)等。
作为一种实现方法，第一节点从接入网节点接收第一节点的至少一个下一跳节点的负载信息和/或至少一个下一跳节点的干扰信息。
作为另一种实现方法，第一节点分别从第一节点的每个下一跳节点，接收该下一跳节点的负载信息和/或该下一跳节点的干扰信息。比如将第一节点的至少一个下一跳节点中的任意一个节点称为第一下一跳节点，则第一节点是从第一下一跳节点接收第一下一跳节点的负载信息和/或第一下一跳节点的干扰信息。
作为一种实现方法，第一节点从接入网节点接收第一节点与第一节点的至少一个下一跳节点之间的信道质量。
作为另一种实现方法，第一节点自行确定第一节点与第一节点的至少一个下一跳节点之间的信道质量。或者理解为，由第一节点测量或计算得到第一节点与第一节点的至少一个下一跳节点之间的信道质量。
作为一种实现方法，第一节点从接入网节点接收第一节点通过至少一个下一跳节点到达目标节点的链路跳数信息，其中，链路跳数信息与路由标识以及下一跳节点的标识信息对应，路由标识包括目标节点的标识信息和路径标识。比如，接入网节点在为第一节点配置路由表时，路由表包括第一节点的下一跳节点的标识信息、第一节点通过下一跳节点到达目标节点的路由标识，以及第一节点通过下一跳节点到达目标节点的链路跳数信息。
作为另一种实现方法，第一节点从接入网节点接收第一节点通过至少一个下一跳节点到达目标节点的链路跳数信息，其中，该链路跳数信息指示的链路跳数为第一节点通过下一跳节点到达目标节点的最小链路跳数，并且，该链路跳数信息与下一跳节点的标识信息以及目标节点的标识信息对应。比如，接入网节点可以通过指示信息，向第一节点指示第一节点通过至少一个下一跳节点到达目标节点的最小链路跳数信息。
作为一种实现方法，第一节点可以从第一节点的每个下一跳节点接收该下一跳节点的标识信息。将第一节点的至少一个下一跳节点中的任意一个节点称为第一下一跳节点，则第一节点可以从第一下一跳节点接收第一下一跳节点的标识信息。比如，第一下一跳节点通过第一下一跳节点与第一节点之间的空口，向第一节点发送第一下一跳节点的标识信息。再比如，第一下一跳节点通过第一下一跳节点与第一节点之间的侧行链路接口，向第一节点发送第一下一跳节点的标识信息。
作为一种实现方法，第一节点可以从第一下一跳节点接收第一下一跳节点能够到达的目标节点的标识信息。也即，第一下一跳节点将第一下一跳节点能够到达的目标节点的标识信息都发送给第一节点，从而后续第一节点需要选择传输(如重路由)的节点时，可以获知该第一下一跳节点是否可以作为候选的下一跳节点。可选的，第一下一跳节点不会将第一下一跳节点到达目标节点的所有链路跳数信息发送给第一节点，而是将第一下一跳节点到达目标节点的最小链路跳数信息发送给第一节点。
作为一种实现方法，第一节点还从接入网节点接收第一指示信息，该第一指示信息指示第一节点接收数据包的第一承载与第一节点发送数据包的第二承载之间的映射关系，第一承载为回传无线链路控制信道(backhaul radio link control channel，BH RLC CH)，第二承载为第一节点与至少一个下一跳节点之间的侧行链路上的无线承载(如数据无线承载或信令无线承载)或无线链路控制信道(radio link control channel，RLC CH)。第一节点根据第一指示信息，可以获知：从第一承载接收的数据包，应当从第二承载发送至该第一节点的下一跳节点。需要说明的是，第一节点与不同的下一跳节点之间的第二承载分别不同。
作为一种实现方法，若第一节点支持侧行链路，则第一节点可以向接入网节点发送第二指示信息，该第二指示信息指示第一节点支持侧行链路，或者指示第一节点支持侧行链路通信的功能，或者指示第一节点支持侧行链路接口。可选的，第一节点可以从接入网节点接收第三指示信息，该第三指示信息指示使能第一节点的侧行链路，从而第一节点可以根据该第三指示信息，使能该第一节点的侧行链路。
当上述无线通信方法应用于接入回传一体化(Integrated Access and Backhaul，IAB)场景时，则上述第一节点和第二节点均为IAB节点，或者，上述第一节点为IAB宿主节点(即：IAB宿主节点的DU)和第二节点为IAB节点，或者，上述第一节点为IAB节点和第二节点为IAB宿主节点(即：IAB宿主节点的DU)，接入网节点是IAB宿主节点(即：IAB宿主节点的CU)。并且，若上述无线通信方法应用于上行传输，则目标节点是IAB宿主节点(即：IAB宿主节点的DU)。若上述无线通信方法应用于下行传输，则目标节点是接入IAB节点。其中，接入节点指的是UE接入的节点。
为解决背景技术中提到的技术问题，参考图3所示，本申请实施例还提供一种无线通信方法，该方法包括以下步骤：
步骤301，第一节点接收来自接入网节点的第二指示信息。
该第二指示信息指示使能第一节点的侧行链路。
步骤302，第一节点根据第二指示信息，使能第一节点的侧行链路。
基于上述方案，可以使能第一节点的侧行链路，从而第一节点可以通过与其它节点之间的侧行链路接口与其它节点通信，可以提高路由路径中的信息传输效率。
可选的，在步骤301之前，第一节点向接入网节点发送第一指示信息，第一指示信息指示第一节点支持侧行链路，或者指示第一节点支持侧行链路通信的功能，或者指示第一节点支持侧行链路接口。
当上述无线通信方法应用于IAB场景时，则上述第一节点为IAB节点，或上述第一节 点为IAB宿主节点(即：IAB宿主节点的DU)，接入网节点是IAB宿主节点(即：IAB宿主节点的CU)。
为解决背景技术中提到的技术问题，参考图4所示，本申请实施例还提供一种无线通信方法，该方法包括以下步骤：
步骤401，第一节点接收来自接入网节点的指示信息。
该指示信息指示用于第一节点接收数据包的第一承载与用于第一节点发送数据包的第二承载之间的映射关系，第一承载为回传无线链路控制信道，第二承载为第一节点与第一节点的下一跳节点之间的侧行链路上的无线承载或无线链路控制信道。
步骤402，第一节点根据指示信息，将从第一承载收到的数据包，通过第二承载发送至下一跳节点。
基于上述方案，第一节点可以快速确定发送数据包的承载，从而可以提高路由路径中的信息传输效率。
当上述无线通信方法应用于IAB场景时，则上述第一节点为IAB节点，接入网节点是IAB宿主节点(即：IAB宿主节点的CU)。
如背景技术介绍，UE发送的信息所经过的节点构成一个路由路径，如何提高路由路径中的信息传输效率，是目前需要解决的。目前，一个UE向另一个UE发送数据包时，从一个UE发送出来的数据包需要先经过路由路径中的节点发送至核心网的用户面节点，然后由该用户面节点再将该数据包经过路由路径中的节点发送至另一个UE。也就是说，现有数据包的传输需要经过核心网节点的处理，该方式数据包传输路径较长，造成时延较大。如何为减少数据包的传输时延，以提高路由路径中的信息传输效率，是本申请实施例所要解决的第二个问题。
为解决该问题，本申请实施例提供一种无线通信方法，如图5所示，该方法包括以下步骤：
步骤501，第一节点接收来自接入网节点的第二节点的标识信息。
该第一节点为第一UE接入的节点，第二节点为第二UE接入的节点。
步骤502，第一节点通过第二节点向第二UE发送第一数据包。
该第一数据包携带第一信息和第二信息，第一信息包括来自第一UE的数据或信令，第二信息包括以下一项或多项：第二UE的接入层标识、第一传输通道的标识信息，第一传输通道为第二UE与第二节点之间传输第一信息的通道。
可选的，第二信息携带于第一数据包的回传适配协议(backhaul adaptation protocol，BAP)层头字段中。基于上述方案，第一节点可以从接入网节点获得与第二UE接入的节点的标识信息，然后第一节点可以通过该第二节点向第二UE发送数据包。相较于现有技术，数据包的传输不需要经过核心网节点的处理，可以缩短数据包的路由路径，减少数据包的传输时延，从而提高路由路径中的信息传输效率。
作为一种实现方法，上述步骤502中，第一节点可以向第三节点发送第一数据包，然后第三节点通过第二节点将第一数据包发送至第二UE，第三节点为第一节点与第二节点之间的中间节点，比如第三节点与第二节点可以直连，或者第三节点与第二节点之间还有 其它中间节点。例如参考图6，为该方式对应的路由路径示意图。
作为另一种实现方法，上述步骤502中，第一节点可以通过第一节点与第二节点之间的接口(如Uu口或侧行链路接口)向第二节点发送第一数据包，然后第二节点将第一数据包发送至第二UE。例如参考图7，为该方式对应的路由路径示意图。
作为一种实现方法，上述步骤501之前，第一节点通过第二传输通道接收来自第一UE的第二数据包，第二数据包携带第一信息和第二UE的应用层标识，第二传输通道为第一UE与第一节点之间传输第一信息的通道，然后第一节点根据第二UE的应用层标识获取第二UE的接入层标识，然后根据第二数据包生成第一数据包。可选的，第二UE的应用层标识携带于第二数据包的媒体接入控制(medium access control，MAC)层头字段或RLC层头字段中。
其中，第一节点根据第二UE的应用标识获取第二UE的接入层标识，比如可以是：第一节点向接入网节点发送第二UE的应用层标识，然后第一节点接收来自接入网节点的第二UE的接入层标识，也即由接入网节点根据第二UE的应用层标识确定第二UE的接入层标识。
作为一种实现方法，上述步骤502之前，第一节点从接入网节点获取第一传输通道的标识信息。比如，第一节点向接入网设备发送第二传输通道对应的服务质量(quality of service，QoS)信息，则接入网节点根据第二传输通道对应的QoS信息，确定第一传输通道。其中，第二传输通道为第一UE与第一节点之间传输第一信息的通道。
作为一种实现方法，上述步骤502之前，第一节点从接入网节点接收第一指示信息，该第一指示信息指示第一节点使能本地传递功能，第一节点根据第一指示信息，使能本地传递功能。可选的，第一节点从接入网节点接收第一指示信息之前，还向接入网节点发送第二指示信息，该第二指示信息指示第一节点支持本地传递功能。
当上述无线通信方法应用于IAB场景时，则上述第一节点和第二节点均为IAB节点，接入网节点是IAB宿主节点(即：IAB宿主节点的CU)。
下面以图1、图3、图4以及图5对应的方案均应用于IAB场景为例，介绍上述各种方案的详细实施方式。
第三代合作伙伴计划(3rd generation partnership project，3GPP)Rel-15NR中，gNB可以采用集中式单元(Central Unit，CU)-分布式单元(Distributed Unit，DU)分离架构，即：gNB由一个gNB-CU以及一个或者多个gNB-DU组成。其中，gNB-CU与gNB-DU之间通过F1接口相连，gNB-CU与第五代(5th generation，5G)核心网之间通过NG接口相连。如图8所示，为NR中gNB-CU和gNB-DU分离架构图。
gNB是为用户设备(User Equipment，UE)提供NR用户面和控制面传输的节点，gNB包含一个或者多个小区。gNB通过NG接口连接到5G核心网(5G core，5GC)，并通过Xn接口与其它gNB相连。其中，Xn-C接口用于两个gNB之间控制面信令的传输，Xn-U 接口用于两个gNB之间用户面数据的传输。gNB与UE之间的接口称为Uu接口。其中，UE与基站(如gNB、eNB)或者接入IAB节点的DU之间的通信接口可以称为空口。
gNB-CU是一个逻辑节点，gNB-CU包含gNB的无线资源控制(Radio Resource Control，RRC)层、业务数据适配协议(Service Data Adaptation Protocol，SDAP)层和分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层，用于控制一个或者多个gNB-DU。
gNB-DU是一个逻辑节点，gNB-DU包含gNB的无线链路控制(Radio Link Control，RLC)层、媒体接入控制(medium access control，MAC)层和物理层(Physical layer，PHY)层。一个gNB-DU支持一个或者多个小区，但一个小区只能属于一个gNB-DU。
UE通过gNB-DU接入gNB-CU，即：与UE对等的PHY/MAC/RLC层功能位于gNB-DU上，与UE对等的PDCP/SDAP/RRC层功能位于gNB-CU上。
如图9所示，为gNB采用CU-DU分离架构下的控制面协议栈示意图。对控制面而言，上行(uplink，UL)方向上，gNB-DU将UE生成的RRC消息封装在F1接口应用协议(F1Application Protocol，F1AP)消息中发送到gNB-CU。下行(downlink，DL)方向上，gNB-CU将RRC消息封装在F1AP消息中发送到gNB-DU，gNB-DU从F1AP消息中提取出RRC消息映射到Uu接口对应的信令无线承载(signalling radio bearer，SRB)(SRB0/SRB1/SRB2)上发送给UE。
如图10所示，为gNB采用CU-DU分离架构下的用户面协议栈示意图。对用户面而言，UL方向上，gNB-DU将从Uu接口数据无线承载(Data Radio Bearer，DRB)上收到的UE数据包映射到对应的通用分组无线服务(General Packet Radio Service，GPRS)隧道协议(GPRSTunnelingProtocol，GTP)隧道中发送到gNB-CU。DL方向上，gNB-CU将UE数据包映射到对应的GTP隧道中发送到gNB-DU，gNB-DU从GTP隧道中提取出UE数据包，并将该UE数据包映射到Uu接口对应的DRB上发送给UE。
3GPP Rel-15 IAB中，引入了IAB node(称为IAB节点)和IAB donor(称为IAB宿主节点，或者宿主IAB节点)两个节点。其中，IAB donor可以是gNB，或者升级后的gNB。
如图11所示，为两跳数据回传场景示意图。其中，回传简称BH。IAB网络采用CU-DU分离架构，即：IAB donor由IAB donor-CU(简称donor-CU)和IAB donor-DU(简称donor-DU)两部分组成，IAB node由IAB node-MT(简称IAB-MT)和IAB node-DU(简称IAB-DU)两部分组成。其中，IAB node-MT又可以称为IAB node-UE(简称IAB-UE)。
对IAB donor而言，donor-DU与gNB-DU的功能类似，donor-CU与gNB-CU的功能类似。
对IAB node而言，IAB-DU与gNB-DU的功能类似，用于为其子节点提供接入服务，其中，IAB-DU的子节点可以是UE，也可以是其他IAB node。IAB-MT具有UE的功能，用于为其子节点提供数据回传。
IAB node进一步又可以分为接入IAB node和中间IAB node，即：UE接入的IAB节点称为接入IAB node，接入IAB node和IAB donor之间路径上的IAB node称为中间IAB node。
如图11所示，UE接入IAB node2，则IAB node2称为UE的接入IAB node(或者UE的父节点)，UE称为IAB node2的子节点，UE和IAB node2之间的链路称为接入链路。IAB  node1称为中间IAB node，IAB node1的父节点为IAB donor(IAB donor的子节点为IAB node1)，IAB node1的子节点为IAB node2(IAB node2的父节点为IAB node1)。IAB node1和IAB node2之间的链路，以及IAB node1和IAB donor之间的链路均称为回传链路。其中，与UE对等的PHY层、MAC层和RLC层位于接入IAB node上(即：IAB2-DU)，而与UE对等的PDCP层、SDAP层和RRC层位于donor-CU上。IAB node均采用L2数据转发的架构。
如图12所示，为两跳数据回传的控制面协议栈示意图。接入IAB node(即：IAB2-DU)和IAB donor(即：donor-CU)之间建立F1接口。具体的，如果IAB donor采用CP-UP分离架构，则IAB2-DU和donor CU-CP之间建立F1-C接口。UE的RRC消息封装在F1-C接口的F1AP消息中传输。
如图13所示，为两跳数据回传的用户面协议栈示意图。如果IAB donor采用CP-UP分离架构，则IAB2-DU和donor CU-UP之间建立F1-U接口，并在该F1-U接口上建立per UE bearer的GTP隧道。也就是说，UE和IAB2-DU之间接口上建立的每一个UE DRB，在IAB2-DU和donor CU-UP之间接口上对应一个单独的GTP隧道。
如图14所示，为两跳数据回传中的数据传输示意图。UE和IAB node2之间接口链路上建立多个UE DRB，用于传输UE不同的业务。IAB node2和IAB node1之间回传链路上建立多个回传RLC信道(BH RLC CH)，用于传输UE不同业务的回传。同理，IAB node1和IAB donor之间回传链路上也建立多个BH RLC CH。IAB node2和IAB donor CU之间建立per UE bearer的GTP隧道，每个GTP隧道与UE和IAB node2之间接口上的UE DRB一一对应。
在下行方向：
1)、donor-CU将UE PDCP协议数据单元(protocol data unit，PDU)映射到对应的GTP隧道上，确定该UE数据包的目标因特网协议(internet protocol，IP)地址(即IAB node2的IP地址)，将该UE数据包进一步封装成IP包，并在IP头字段中打上对应的差分服务代码点(Differentiated Services Code Point，DSCP)或流标签(flow label)，以及填上IP包的目标IP地址后，通过IP路由方式发送到donor-DU。其中，DSCP用于在因特网协议版本4(Internet Protocol version 4，IPv4)中标识业务的类型，flow label用于在因特网协议版本6(Internet Protocol version 6，IPv6)中标识业务的类型。
2)、donor-DU根据IP头中携带的DSCP或flow label以及目标IP地址，并根据donor-CU配置的映射关系1，将收到的UE IP包映射到对应的BH RLC CH上发送给IAB node1。其中，donor-CU为donor-DU配置的映射关系1包括：参数和BH RLC CH的映射关系，该参数由以下一种或者多种组合组成，包括：DSCP、flow label、目标IP地址。
3)、IAB node1根据donor-CU配置的映射关系2，将收到的UE IP包映射到对应的BH RLC CH上发送给IAB node2。其中，donor-CU为IAB node1配置的映射关系2包括：ingress BH RLC CH(入口BH RLC CH)和egress BH RLC CH(出口BH RLC CH)的映射关系。ingress BH RLC CH为IAB node1和IAB donor DU之间的BH RLC CH，egress BH RLC CH为IAB node1和IAB node2之间的BH RLC CH。
4)、IAB node2将收到的UE IP包送到GTP层解析后，从GTP隧道中提取UE PDCP PDU， 并根据donor-CU配置的GTP隧道和UE DRB的映射关系，将UE PDCP PDU映射到对应的UE DRB上发送给UE。
在上行方向：
1)、UE将UE PDCP PDU映射到对应的UE DRB上发送到IAB node2。
2)、IAB node2根据donor-CU配置的GTP隧道和UE DRB的映射关系，将UE PDCP PDU映射到对应的GTP隧道中。然后，IAB node2再根据donor-CU配置的映射关系3，将UE数据包进一步封装成IP包后映射到对应的BH RLC CH上发送给IAB node1。其中，donor-CU配置的映射关系3包括：GTP隧道(即：GTP TEID和IP地址)和BH RLC CH的映射关系，IP地址为donor-CU的IP地址。
3)、IAB node1根据donor-CU配置的映射关系4，将收到的UE IP包映射到对应的BH RLC CH上发送给donor-DU。其中，donor-CU为IAB node1配置的映射关系4包括：ingress BH RLC CH(入口BH RLC CH)和egress BH RLC CH(出口BH RLC CH)的映射关系。ingress BH RLC CH为IAB node2和IAB node1之间的BH RLC CH，egress BH RLC CH为IAB node1和IAB donor DU之间的BH RLC CH。
4)、donor-DU根据UE IP包头中的目标IP地址(即：donor-CU的IP地址)，将UE IP包进一步路由到donor-CU。donor-CU将IP包送到GTP层解析后，从GTP隧道中提取出UE PDCP PDU。
R16中，IAB node支持两种组网方式，包括：生成树(spanning tree，ST)组网方式(参考图15的(a))和有向无环图(directed acyclic graph，DAG)组网方式(参考图15的(b))。
其中，ST组网方式支持多跳，每个IAB节点只有一个父节点。DAG组网方式支持多跳、多连接，每个IAB node可以存在1个或者两个父节点(如图16的(a)、(b)和(c)所示)，但只能连接到一个IAB donor(如图16的(b)和(c)所示，受一个IAB-DU只能连接到一个donor-CU的约束)。
基于上述组网方式，每个IAB node都包括两种角色：子节点和父节点。如图17所示，IAB node1是IAB donor的子节点，也是IAB node2的父节点；IAB node2是IAB node1的子节点，也是IAB node3的父节点；IAB node3是IAB node2的子节点，也是UE的父节点。
对同一个IAB node而言，不管数据还是信令的传输，都是一侧接收后交给另一侧进行发送，如：IAB-MT接收数据或信令后交给共站IAB-DU发送出去，或者，IAB-DU接收数据或信令后交给共站IAB-MT发送出去。具体的，以IAB-node2为例，对下行(DL)传输而言，IAB-MT2从IAB-DU1收到DL数据/信令后，IAB-MT2通过内部接口发送到共站IAB-DU2，由IAB-DU2发送到IAB-MT3；对上行(UL)传输而言，IAB-DU2从IAB-MT3收到UL数据/信令后，IAB-DU2通过内部接口发送到共站IAB-MT2，由IAB-MT2发送到IAB-DU1。
R16 IAB采用IAB donor集中控制的路由和承载映射方式。在现有协议栈的基础上， 新引入了一个协议层，即：回传适配协议(backhaul adaptation protocol，BAP)层，如上图12和图13所示，该BAP层的作用主要是用于回传链路上数据/信令传输的路由和承载映射。
一、路由
路由指的是数据/信令在传输之前需要先确定传输的路径，即：通过哪个下一跳节点将数据/信令传输到目标节点。
R16 IAB中，不论DL路由还是UL路由，donor-CU需要分别给donor-DU、中间IAB node和接入IAB node配置路由表，即：路由标识(Routing ID)<->下一跳节点的BAP地址的映射关系，其中，Routing ID包括目标节点的BAP地址和路径标识(path ID)。
1、下行(DL)路由
donor-DU：donor-CU为donor-DU配置DSCP/flow label+接入IAB node的IP地址<->Routing ID的映射关系。即：donor-DU从donor-CU收到DL IP包后，根据IP包头字段中携带的DSCP/flow label值和目标IP地址，并根据donor-CU配置的上述映射关系，确定该DL IP包对应的路由标识Routing ID，然后再根据Routing ID查路由表，确定数据/信令传输的下一跳节点，并在BAP层中携带该确定的Routing ID，随数据/信令一起发送到下一跳节点。
中间IAB node：中间IAB node从上一跳节点接收DL IP包，根据BAP层中携带的Routing ID查路由表，确定数据/信令传输的下一跳节点。
2、上行(UL)路由
接入IAB node：对数据传输而言，donor-CU为接入IAB node配置GTP FTEID<->Routing ID的映射关系；对信令传输而言，donor-CU为接入IAB node配置信令类型指示<->Routing ID的映射关系，其中，信令类型指示用于指示Non-UE associated F1AP、UE-associated F1AP。即：接入IAB node从UE收到UL IP包后，根据donor-CU配置的上述映射关系确定数据/信令传输对应的Routing ID，然后再根据Routing ID查路由表，确定数据/信令传输的下一跳节点，并在BAP层中携带该确定的Routing ID，随数据/信令一起发送到下一跳节点。
中间IAB node：中间IAB node从上一跳节点接收DL IP包，根据BAP层中携带的Routing ID查路由表，确定数据/信令传输的下一跳节点。
二、承载映射
承载映射指的是数据/信令映射到对应的传输通道上发送到下一跳节点，即：数据/信令在向下一跳节点发送之前，需要先确定该数据/信令映射到哪个传输通道(例如：BH RLC CH)上发送。
R16 IAB中，不论DL映射还是UL映射，donor-CU需要分别给donor-DU、中间IAB node和接入IAB node配置承载映射。如图12和图13所示，具体的包括：
1、DL映射：
donor-DU：donor-CU为donor-DU配置DSCP/flow label+接入IAB node的IP地址<->egress BH RLC CH ID的映射关系。即：donor-DU从donor-CU收到DL IP包后，根据IP包头字段中携带的DSCP/flow label值和目标IP地址，并根据donor-CU配置的上述映射关系，确定需要将该DL IP包映射到哪个对应的egress BH RLC CH上发送给下一跳节点。
中间IAB node：donor-CU为中间IAB node配置ingress BH RLC CH ID<->egress BH  RLC CH ID的映射关系。即：中间IAB node从ingress BH RLC CH上接收到上一跳节点发送的DL IP包后，根据donor-CU配置的上述映射关系，确定需要将该DL IP包映射到哪个对应的egress BH RLC CH上发送给下一跳节点。
2、UL映射
接入IAB node：对数据传输而言，Donor-CU为接入IAB node配置GTE FTEID<->egress BH RLC CH ID的映射关系；对信令传输而言，Donor-CU为接入IAB node配置F1AP类型指示<->egress BH RLC CH的映射关系，其中，F1AP类型指示用于指示Non-UE associated F1AP消息和UE-associated F1AP消息。即：接入IAB node从Donor-CU收到UL IP包后，根据Donor-CU配置的上述映射关系，确定需要将该UL IP包映射到哪个对应的egress BH RLC CH上发送给下一跳节点。
中间IAB node：donor-CU为中间IAB node配置ingress BH RLC CH ID<->egress BH RLC CH ID的映射关系。即：中间IAB node从ingress BH RLC CH上接收到上一跳节点发送的DL IP包后，根据donor-CU配置的上述映射关系，确定需要将该DL IP包映射到哪个对应的egress BH RLC CH上发送给下一跳节点。
由于R16 IAB只支持ST和DAG两种组网方式,重路由机制只限定在无线链路失败(radio link failure，RLF)场景。如图18所示，当IAB-node2检测到与IAB-node4之间的链路发生RLF，并且该链路无法恢复，则IAB-node2向其子节点IAB-node1发送一个RLF指示信息。收到该RLF指示信息后，如果该IAB-node1工作在双连接模式时，则IAB-node1将触发re-routing机制，将原本通过IAB-node2发送到IAB-donor的UL数据，重路由到IAB-node3上发送，即：将这些UL数据通过IAB-node3发送到IAB-donor。
现有技术只考虑了生成树和有向无环图两种简单的组网形式，两个对等节点之间无法直接通信，而且由于一个IAB node最多只有两个父节点，因此重路由机制简单，即：最多也只有一个候选路径可用于重路由，不存在候选路径的选择问题。
随着网络的发展，mesh组网是一种多点对多点的对等网络，即新增了两个对等节点之间的直接通信，保证了任意两个相邻节点之间都可以直接通信，具有自组网、自修复、灵活路由等优点，可以大幅减低网络部署的成本和复杂程度，是未来网络部署的一种趋势。在mesh组网中，相邻两个节点之间都可以直接通信，导致IAB node一旦发现链路RLF之后，可能存在多条候选路径可用于重路由，但是按照现有技术，IAB node无法获知这些候选路径的链路质量、负载情况等，无法从中选择合适的路径来进行重路由。
此外，现有技术不支持本地传递(local switch)。但是在mesh组网中，相邻两个节点之间可以直接通信，增加了数据/信令实现local switch的可能性，极大缩减了数据/信令传输的时延。本申请实施例针对IAB mesh组网场景，主要解决两个问题：
问题1：以重路由为例进行说明，IAB node如何选择合适的路径将数据/信令进行重路由，以保证数据/信令传输的QoS需求？
问题2：如何实现IAB mesh场景下的local switch，以减少数据传输的时延，保证两个通信UE之间的正常数据传输？
本申请实施例主要考虑IAB mesh组网场景。
场景一：
在现有R16 IAB组网场景中，如图19所示，对等节点之间无法直接通信，例如：IAB node1和IAB node2，IAB node3和IAB node4，IAB node4和IAB node5，IAB node6和IAB node7。
在IAB mesh组网场景中，如图20所示，需要新增两个对等节点之间的连接，保证相邻两个节点之间都可以直接通信。比如，新增IAB node1与IAB node2之间的连接，新增IAB node3与IAB node4之间的连接，新增IAB node4与IAB node5之间的连接，新增IAB node6与IAB node7之间的连接。
一旦IAB node4与IAB node2之间的链路发生RLF，则IAB node2可以通过多条候选路径将DL数据进一步路由到IAB node6，由IAB node6进一步发送给UE，或者，IAB node4可以通过多条候选路径将UL数据进一步路由到Donor-CU。
场景二：
在IAB mesh组网场景中，如图20所示，接入IAB node6下面的UE1通过local switch方式，与接入在IAB node7下面的UE2进行通信。也即，UE1与UE2之间的local switch路径为：UE1<->IAB node6<->IAB node7<->UE2。
需要说明的是，本申请实施例上述场景一和场景二中所涉及的图19和图20仅是为了说明本申请实施例方案的具体示例，该具体示例并不构成对本申请实施例应用场景的限定。实际应用中，还可以应用于其它具有相同问题的场景中。
实施例一
该实施例一对应于上述图1对应的实施例，用于实现为路由路径的节点选择合适的重路由节点。
在IAB mesh组网场景中，引入两个对等节点之间的连接，保证相邻两个节点之间都可以直接通信。其中，两个对等节点之间的通信存在两种方案，该实施例中，将Donor-CU简称donor-CU，将IAB node1简称为IAB1，IAB node2简称IAB2，以此类推，这里就不再赘述。
方案一：对等IAB node之间通过Uu接口通信
本方案中，对等IAB node之间通过Uu接口通信，意味着一个IAB node的DU和另一个IAB node的MT之间通过Uu接口通信。如图21所示，对等节点IAB1和IAB2之间的通信，可以通过IAB1-MT和IAB2-DU之间通信来实现，或者，通过IAB1-DU和IAB2-MT之间通信来实现。
本方案以DL传输为例进行说明，上述方案同样适用于UL传输的场景，这里就不再赘述。
以下行数据传输为例，如果IAB2-DU和IAB4-MT之间的链路发生RLF，则IAB2还可以通过其他候选路径将UE1的DL数据发送IAB6，由IAB6进一步发送到UE1。其中，候选路径包括但不限于：
候选路径1：IAB2-DU->IAB1-MT->IAB1-DU->IAB3-MT->IAB3-DU->IAB6-MT；
候选路径2：IAB2-DU->IAB1-MT->IAB1-DU->IAB3-MT->IAB3-DU->IAB4-MT->IAB4-DU->IAB6-MT；
候选路径3：IAB2-DU->IAB5-MT->IAB5-DU->IAB4-MT->IAB4-DU->IAB7-MT->IAB7-DU->IAB6-MT；
候选路径4：IAB2-DU->IAB5-MT->IAB5-DU->IAB7-MT->IAB7-DU->IAB6-MT；
……
由于IAB2并不知道每条候选路径的情况，例如：候选路径上各链路的质量情况、候选路径上各IAB node的负载情况等，因此，IAB2如何从多条候选路径中选择一条合适的路径对下行数据进行重路由？
为了解决上述问题，IAB2可以获知各候选路径的跳数信息以及相邻IAB node的负载情况，从而可以选择合适的路径进行重路由。
其中，IAB node获知各候选路径的跳数信息的方法包括但不限于以下方法1至方法2：
方法1：Donor-CU为IAB node配置路由表时，针对不同路由路径新增通过下一跳节点到达目标节点之间经过的跳数信息，即：Routing ID<->下一跳节点的BAP地址<->跳数，其中，Routing ID由目标节点的BAP地址+路径标识path ID组成。
也即，Donor-CU向IAB节点发送下一跳节点的BAP地址、Routing ID和跳数信息。其中，跳数信息与下一跳节点的BAP地址和Routing ID具有对应关系，用于指示通过BAP地址指示的下一跳节点，经过Routing ID指示的路径到达Routing ID指示的目标节点所经过的跳数。可选的，通过路由表配置下一跳节点的BAP地址、Routing ID和跳数信息。
现有技术中，Donor-CU为IAB node配置路由表时，Donor-CU向IAB node发送Routing ID和下一跳节点的BAP地址，并且Routing ID和下一跳节点的BAP地址具有对应关系，用于指示该IAB node可以通过该BAP地址指示的下一跳节点，经过Routing ID指示的路径到达Routing ID指示的目标节点。为了让IAB node获知各候选路径的跳数信息，可以在现有路由表的基础上，新增通过该BAP地址指示的下一跳节点，经过Routing ID指示的路径到达Routing ID指示的目标节点所经过的跳数信息。
以图21的IAB2为例，Donor-CU可以在为IAB2配置的路由表中新增跳数信息(其中目标节点为IAB6)：
候选路径1：Routing ID1<->下一跳节点IAB1的BAP地址<->2跳；
候选路径2：Routing ID2<->下一跳节点IAB1的BAP地址<->3跳；
候选路径3：Routing ID3<->下一跳节点IAB5的BAP地址<->3跳；
候选路径3：Routing ID4<->下一跳节点IAB5的BAP地址<->2跳。
即：Donor-CU向IAB node配置通过下一跳节点，经过Routing ID指示的路径到达Routing ID指示的目标节点所经过的跳数信息。
方法2：Donor-CU向IAB node发送通过下一跳节点到达目标节点的最短跳数信息(该方法不需要改变路由表的配置)
也即，该方法由Donor-CU向IAB node发送下一跳节点的BAP地址、目标节点的BAP地址和最短跳数信息，其中，最短跳数信息与下一跳节点的BAP地址和目标节点的BAP地址具有对应关系，用于指示通过下一跳节点到达目标节点所经过的最短跳数。
以图21的IAB2为例，Donor-CU向IAB2发送以下信息：
下一跳节点IAB1的BAP地址<->目标节点IAB6的BAP地址<->2跳；
下一跳节点IAB5的BAP地址<->目标节点IAB6的BAP地址<->2跳。
值得注意的是，上述方法应用于IAB node，即：IAB node从Donor-CU获取各候选路径的跳数信息。可选的，上述方法还可以应用于Donor-DU，即：Donor-DU从Donor-CU获取各候选路径的跳数信息，以便于Donor-DU选择合适的下一跳节点进行重路由。
其中，一个IAB node获知相邻IAB node的负载情况((以下以IAB2获知相邻的IAB1的负载情况(负载/干扰信息)为例))的方法包括但不限于以下方法1至方法5：
方法1：IAB1-MT通过RRC消息向donor-CU上报负载/干扰信息，donor-CU再通过F1AP消息将该负载/干扰信息发送到IAB2-DU。
该方法可以理解为：IAB node通过RRC消息向donor-CU上报负载/干扰信息，donor-CU再通过F1AP消息将该负载/干扰信息发送到该IAB节点的父节点或子节点。
方法2：IAB1-DU通过F1AP消息向donor-CU上报负载/干扰信息，donor-CU再通过RRC消息将该负载/干扰信息发送到IAB2-MT。
该方法可以理解为：IAB node通过F1AP消息向donor-CU上报负载/干扰信息，donor-CU再通过RRC消息将该负载/干扰信息发送到该IAB节点的父节点或子节点。
方法3：IAB1-MT通过RRC消息向donor-CU上报负载/干扰信息，donor-CU再通过RRC消息将该负载/干扰信息发送到IAB2-MT。
该方法可以理解为：IAB node通过RRC消息向donor-CU上报负载/干扰信息，donor-CU再通过RRC消息将该负载/干扰信息发送到该IAB节点的父节点或子节点。
方法4：IAB1-DU通过F1AP消息向donor-CU上报负载/干扰信息，donor-CU再通过F1AP消息将该负载/干扰信息发送到IAB2-DU。
该方法可以理解为：IAB node通过F1AP消息向donor-CU上报负载/干扰信息，donor-CU再通过F1AP消息将该负载/干扰信息发送到该IAB节点的父节点或子节点。
方法5：IAB1-DU和IAB2-MT，或者IAB1-MT和IAB2-DU之间通过BAP control PDU进行传输。
该方法可以理解为：IAB node通过BAP control PDU消息将负载/干扰信息发送到该IAB节点的父节点或子节点。
此外，在IAB mesh组网场景下，如果IAB2-DU和IAB4-MT之间的链路发生RLF，则IAB2还可以通过其他候选路径将UE1的DL数据发送IAB6，由IAB6进一步发送到UE1。除了上述列举的候选路径之外，还可能存在另一种路径：
候选路径a：IAB2-DU->IAB1-MT->IAB1-DU->IAB3-MT->IAB4-DU->IAB6-MT。
候选路径b：IAB2-DU->IAB5-MT->IAB5-DU->IAB7-MT->IAB6-DU。
该候选路径对现有机制有改变。按照现有技术中的描述，对DL而言，IAB-MT从父节点的DU接收到数据后，通过内部接口发送给共站IAB-DU。而候选路径a和候选路径b 中，IAB-MT(路径a中的IAB3-MT或者路径b中的IAB7-MT)从父节点的DU接收到数据后不是发送给共站IAB-DU，而是发送其他IAB node的DU。因此，对IAB node的数据传输实现存在改变，即：IAB-MT从父节点接收到DL数据后，需要先看该数据中携带的路由信息，如果该路由信息可以在路由表中可以找到对应的配置，则按照路由表配置来进行路由；否则，将该数据通过内部接口发送到共站IAB-DU。
因此，IAB-MT从父节点接收到DL数据后，需要先看该数据中携带的路由信息，如果该路由信息可以在路由表中找到对应的配置，则按照路由表配置进行路由；否则，将该数据通过内部接口发送到共站IAB-DU。
值得注意的是，上述方法应用于IAB node，即：IAB node获知相邻IAB node的负载情况。可选的，上述方法还可以应用于Donor-DU，即：Donor-DU获知相邻IAB node的负载情况，以便于Donor-DU选择合适的下一跳节点进行重路由。
方案二：对等IAB node之间通过sidelink接口通信
本方案中，对等IAB node之间通过sidelink接口通信，意味着一个IAB node的MT和另一个IAB node的MT之间通过sidelink接口通信，或者，一个IAB node的DU和另一个IAB node的DU之间通过sidelink接口通信。如图22所示，对等IAB1和IAB2之间的通信，可以通过IAB1-MT和IAB1-MT之间通信来实现，或者，通过IAB1-DU和IAB2-DU之间通信来实现。
本方案以DL传输为例进行说明，上述方案同样适用于UL传输的场景，这里就不再赘述。此外，本方案中以IAB-MT和IAB-MT之间通过sidelink接口通信为例进行说明，该方案同样适用于IAB-DU和IAB-DU之间通过sidelink接口通信的场景。
以下行数据传输为例，如果IAB2-DU和IAB4-MT之间的链路发生RLF，则IAB2还可以通过其他候选路径将UE1的DL数据发送IAB6，由IAB6进一步发送到UE1。其中，一条候选路径为：IAB2-MT->IAB1-MT->IAB1-DU->IAB3-MT->IAB3-DU->IAB6-MT。即：IAB2和IAB1之间通过sidelink接口进行通信。
具体的DL数据传输协议栈如图23所示：
图23的上半图是IAB2和IAB4之间链路发生RLF之前，IAB2通过IAB4路由DL数据的协议栈。
图23的下半图是IAB2和IAB4之间链路发生RLF之后，IAB2通过IAB1路由DL数据的协议栈，即在IAB2-MT和IAB1-MT之间新增对等的sidelink接口协议层，其中SL PDCP为可选存在。
一旦IAB2通过sidelink接口与IAB1进行通信，以下几个关键技术需要解决。
关键技术1：为了保证数据的正常路由，sidelink接口两端的IAB node如何获知对方的BAP地址信息？
方法1：两个IAB-MT可以通过发现(discovery)流程来获知对端的BAP地址信息。
也就是说，两个IAB-MT之间可以通过sidelink接口消息来获知对端的BAP地址信息。作为一种实现方式，该sidelink接口消息可以是discover消息，或者，RRC建立相关消息(比如可以是RRC建立消息、RRC建立请求消息、RRC建立完成消息)等。
方法2：Donor-CU获知IAB1和IAB2之间建立sidelink接口后，分别通过RRC消息 或者F1AP消息通知对端的BAP地址。
也即，IAB node通过RRC消息或者F1AP消息从Donor-CU接收对端的BAP地址信息。
由于IAB node的BAP地址由Donor-CU统一分配，一旦Donor-CU获知IAB1和IAB2之间建立sidelink接口后，就可以将IAB1的BAP地址通知IAB2，将IAB2的BAP地址通知IAB1。
需要说明的是，BAP地址是IAB node粒度的，一个IAB node内的IAB-MT和IAB-DU共用同一个BAP地址。
值得注意的是，上述方法同样适用于donor-DU和IAB node之间。即：donor-DU和IAB node之间通过sidelink接口通信。
关键技术2：为了保证数据的正常路由，如何配置IAB-MT的sidelink链路的路由信息？
IAB1-MT和IAB2-MT之间建立sidelink接口后，通过该sidelink接口(例如：sidelink接口的RRC消息)交互彼此的路由信息。
具体的，沿用现有R16 IAB机制，Donor-CU会为网络中每个IAB node配置路由表，即：Routing ID<->下一跳节点的BAP地址，其中，Routing ID由目标节点的BAP地址+路径标识path id组成。通过配置该路由表，可以使得每个IAB node获知通过哪个下一跳节点可以到达哪个目标节点。
一旦IAB1-MT和IAB2-MT之间建立sidelink接口后，IAB1-MT和IAB2-MT通过sidelink接口交互各自的路由信息。例如：IAB1-MT向IAB2-MT发送目标节点的BAP地址，该目标节点的BAP地址包括IAB6的BAP地址。IAB2-MT收到后，就可以获知通过IAB1可以到达IAB6，并保存下一跳节点IAB1的BAP地址和目标节点IAB6的BAP地址的对应关系。也就是说，IAB节点可以通过sidelink接口将该IAB节点可到达的目标节点的BAP地址列表信息(包括一个或者多个目标节点的BAP地址)发送到通信对端IAB节点。
可选的，为了帮助IAB2进行最优候选路径的选择，IAB1-MT还可以向IAB2-MT发送达到该目标节点所经历的最短跳数信息。也就是说，IAB节点可以通过sidelink接口向通信对端IAB节点发送以下信息，包括：该IAB节点可到达的目标节点的BAP地址，以及到达该目标节点所经历的最短跳数信息。
值得注意的是，上述方法同样适用于donor-DU和IAB node之间。即：donor-DU和IAB node之间通过sidelink接口通信。
关键技术3：为了实现数据传输的QoS保障，如何配置IAB-MT的sidelink链路的承载映射？
以下行数据传输为例，IAB1-MT和IAB2-MT之间建立sidelink接口后，IAB2通过BH RLC CH从Donor-DU2收到DL数据包后，根据确定的路由，需要通过sidelink接口发送到IAB1。为了实现该DL数据传输的QoS保障，DL数据包需要映射到sidelink接口上对应的DRB或者BH RLC CH上传输。
具体的，Donor-CU向IAB2发送ingress BH RLC CH和egress sidelink DRB/RLC CH的映射关系。
也即，Donor-CU向IAB node发送Uu接口上的BH RLC CH和sidelink接口上的DRB或者RLC CH的映射关系。
关键技术4：Donor-CU如何获知IAB node支持sidelink接口，是否需要为IAB node配置sidelink接口的路由和承载映射？
IAB node可以向Donor-CU发送一个指示信息，该指示信息用于指示IAB node支持sidelink接口。Donor-CU根据IAB node的指示信息，向IAB node发送一个指示信息，该指示信息用于指示IAB node使能(enable)或者使不能(disable)sidelink接口/传输功能。
值得注意的是，上述方法同样适用于donor-DU，即：donor-DU向donor-CU上报其是否支持sidelink接口的能力，以及从donor-CU接收是否使能donor-DU的sidelink接口的指示信息。
上述实施例，主要解决IAB node如何选择合适的路径进行数据/信令的重路由，使得IAB node在多候选路径场景下可以选择最优路径进行重路由，保证数据/信令传输的QoS需求。
实施例二
该实施例二对应于上述图5对应的实施例，用于实现节点之间进行本地传递。
参考图24，IAB mesh组网场景下，UE1和UE2可以通过local switch方式进行数据传输，以UE1接入IAB6，UE2接入IAB7为例进行说明，UE1与UE2通过local switch方式进行数据传输，指的是UE1和UE2通信的数据直接通过IAB6和IAB7的通信来实现，而不需要通过Donor-CU，或者核心网UPF等转发。
IAB mesh组网场景下的local switch流程如图25所示，包括以下步骤：
步骤2501，UE1向IAB6发送UL数据包，该UL数据包中携带UE2的应用层标识。
其中，应用层指的是IP层以及IP层以上的层。
该UL数据包需要发送到UE2。
比如，UE1的应用层生成向UE2发送的数据包后，并将该数据包发送到UE1的接入层(access stratum，AS)(也即SDAP层，PDCP层，RLC层，MAC层，PHY层)，由UE1的AS层通过空口向IAB6发送。该数据包携带UE2的应用层标识。
可选的，该UE2的应用层标识可以携带在MAC层头字段或者RLC层头字段中。
需要说明的是，UE1可以感知UE2的应用层标识，但不感知UE2的AS层标识。
步骤2502，IAB6向Donor-CU发送RRC消息或者F1AP消息，该消息中携带以下至少一种信息：UE1的AS层标识、UE2的应用层标识、数据对应的QoS信息。
其中，数据对应的QoS信息例如可以是UE1的DRB ID，或者QoS流标识(QoS Flow ID，QFI)。UE1的AS层标识由UE1接入的小区标识(如物理小区标识(Physical cell Identifier，PCI))+UE1在接入小区内的唯一标识(如小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI))组成，或者由小区全局标识(Cell Global Identification，CGI)+UE1在接入小区内的唯一标识(如C-RNTI)组成。
步骤2503，Donor-CU根据UE2的应用层标识获知UE2的AS层标识，并获知UE2的接入节点标识(例如：IAB7的BAP地址)，并根据该数据对应的QoS信息获知UE2对应的DRB ID。然后向IAB6发送RRC消息或者F1AP消息，该消息中携带以下至少一种信息：UE2的AS层标识、IAB7的BAP地址、UE2的DRB ID、enable local switch的指示信息。
可选的，Donor-CU向接入IAB node发送enable local switch的指示信息，该指示信息与DRB ID(该DRB ID指示的DRB用于传输UE1的数据)具有对应关系，该指示信息用于指示对该DRB上传输的数据启动local switch操作。例如：IAB6收到enable local switch的指示信息后，就可以知道该数据包需要执行local switch操作，因此后续通过相同的DRB收到来自UE1的UL数据时，都将执行local switch操作。
可选的，Donor-CU还向接入IAB node发送以下至少一种信息：UE2的AS层标识、UE2的接入节点BAP地址信息、该数据包在UE2空口传输对应的DRB标识。该步骤的实现有个前提，即：Donor-CU上需要保存UE的应用层标识和UE的AS层标识(例如：物理小区标识(Physical cell Identifier，PCI)或者小区全局标识(Cell Global Identification，CGI)+小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI))的映射关系。例如：UE随机接入网络之后，Donor-CU可以在UE发起业务过程中或者在UE建立协议数据单元(protocol data unit，PDU)会话过程中，获知并保存UE的应用层标识和UE的AS层标识。
步骤2504，IAB6根据IAB7的BAP地址，向IAB7发送UL数据，该UL数据包携带UE2的AS层标识以及UE2的DRB ID。
比如：IAB6根据enable local switch的指示信息，确定将UL数据进行本地路由，即：UL数据路由到IAB7，由IAB7进一步发送给UE2。IAB7从IAB6收到UL数据包后，为了让IAB7知道该UL数据包是发送给哪个UE，以及通过哪个DRB发送给该UE，因此，IAB6向IAB7发送UL数据包时，IAB6在BAP层中携带UE2的AS层标识以及UE2的DRB ID，其中，UE2的DRB ID指的是该数据包在UE2和IAB7之间传输对应的DRB标识。也就是说，UE1的接入IAB节点向UE2的接入IAB节点发送以下至少一种信息：UE2的AS层标识、该数据包在UE2空口传输对应的DRB标识。可选的，该信息可以携带在BAP层中发送。
步骤2505，IAB7根据UE2的AS层标识以及UE2的DRB ID，向UE2发送UL数据包。
基于该方案，UE向接入IAB node发送通信对端UE的应用层标识。可选的，该通信对端UE的应用层标识可以携带在MAC层头字段或者RLC层头字段中。接入IAB node向Donor-CU发送以下至少一种信息：本端UE的AS层标识、对端UE的应用层标识、数据对应的QoS信息。其中，本端UE的AS层标识由本端UE接入的小区标识PCI或者CGI+本端UE在接入小区内的唯一标识C-RNTI组成。数据对应的QoS信息为该数据传输映射的空口DRB标识或者该数据对应的QFI。Donor-CU向接入IAB node发送enable local switch的指示信息，该指示信息与本端UE发送数据对应的DRB对应，用于指示该DRB上传输的数据启动local switch操作。可选的，Donor-CU还向接入IAB node发送以下至少一种信 息：对端UE的AS层标识、对端UE的接入节点BAP地址信息、该数据包在对端UE空口传输对应的DRB标识。接入IAB node在BAP层携带以下信息：对端UE的AS层标识、该数据包在对端UE空口传输对应的DRB标识。
该实施例主要解决IAB mesh场景下的local switch，减少了数据传输的时延，保证两个通信UE之间的正常数据传输。
参考图26，为本申请实施例提供的一种通信装置示意图。该通信装置用于实现上述各实施例中对应第一节点或接入网节点的各个步骤，如图26所示，该通信装置2600包括发送单元2610、接收单元2620和处理单元2630。
在第一个实施例中，该通信装置用于实现上述各实施例中对应第一节点的各个步骤：
接收单元2620，用于获取第一信息，所述第一信息包括以下至少一种：第一节点的至少一个下一跳节点的负载信息、所述至少一个下一跳节点的干扰信息、所述第一节点与所述至少一个下一跳节点之间的信道质量、所述第一节点通过所述至少一个下一跳节点到达目标节点的链路跳数信息；处理单元2630，用于根据所述第一信息，确定通过第二节点进行数据包的传输，其中，所述至少一个下一跳节点包括所述第二节点。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自接入网节点的所述至少一个下一跳节点的负载信息和/或所述至少一个下一跳节点的干扰信息；或者，接收来自第一下一跳节点的所述第一下一跳节点的负载信息和/或所述第一下一跳节点的干扰信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自接入网节点的所述第一节点与所述至少一个下一跳节点之间的信道质量；或者，所述处理单元2630，还用于自行确定所述第一节点与所述至少一个下一跳节点之间的信道质量。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自接入网节点的所述链路跳数信息，其中，所述链路跳数信息与路由标识以及所述下一跳节点的标识信息对应，所述路由标识包括所述目标节点的标识信息和路径标识。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自接入网节点的所述链路跳数信息，其中，所述链路跳数信息指示的链路跳数为所述第一节点通过所述下一跳节点到达所述目标节点的最小链路跳数，所述链路跳数信息与所述下一跳节点的标识信息以及所述目标节点的标识信息对应。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自第一下一跳节点的所述第一下一跳节点的标识信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
在一种可能的实现方法中，所述接收单元2620，用于接收来自第一下一跳节点的所述第一下一跳节点的标识信息，具体包括：用于通过所述第一节点与所述第一下一跳节点之间的侧行链路接收来自所述第一下一跳节点的所述第一下一跳节点的标识信息。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自所述第一下一跳节点的所述第一下一跳节点能够到达的目标节点的标识信息。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自所述第一下一跳节点的所述第一下一跳节点到达所述能够到达的目标节点的最小链路跳数信息。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自接入网节点的第一指 示信息，所述第一指示信息指示所述第一节点接收所述数据包的第一承载与所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述至少一个下一跳节点之间的侧行链路上的无线承载或无线链路控制信道。
在一种可能的实现方法中，发送单元2610，用于向接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持侧行链路。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自所述接入网节点的第三指示信息，所述第三指示信息指示使能所述第一节点的侧行链路。
在一种可能的实现方法中，所述第一节点和所述第二节点均为IAB节点，所述目标节点为IAB宿主节点或接入IAB节点；或者，所述第一节点为IAB宿主节点，所述第二节点为IAB节点，所述目标节点为接入IAB节点。
在第二个实施例中，该通信装置用于实现上述各实施例中对应第一节点的各个步骤：
接收单元2620，用于接收来自接入网节点的第二指示信息，所述第二指示信息指示使能所述第一节点的侧行链路；处理单元2630，用于根据所述第二指示信息，使能第一节点的侧行链路。
在一种可能的实现方法中，发送单元2610，用于在所述接收单元2620接收来自所述接入网节点的第二指示信息之前，向所述接入网节点发送第一指示信息，所述第一指示信息指示所述第一节点支持侧行链路。
在一种可能的实现方法中，所述第一节点为IAB节点，所述接入网节点为IAB宿主节点。
在第三个实施例中，该通信装置用于实现上述各实施例中对应第一节点的各个步骤：
接收单元2620，用于接收来自接入网节点的指示信息，所述指示信息指示用于第一节点接收数据包的第一承载与用于所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述第一节点的下一跳节点之间的侧行链路上的无线承载或无线链路控制信道；处理单元2630，用于根据所述指示信息，将从所述第一承载收到的所述数据包，通过所述第二承载发送至所述下一跳节点。
在第四个实施例中，该通信装置用于实现上述各实施例中对应第一节点的各个步骤：
接收单元2620，用于接收来自接入网节点的第二节点的标识信息，所述第一节点为第一用户设备UE接入的节点，所述第二节点为第二UE接入的节点；发送单元2610，用于通过所述第二节点向所述第二UE发送第一数据包，所述第一数据包携带第一信息和第二信息，所述第一信息包括来自所述第一UE的数据或信令，所述第二信息包括以下一项或多项：所述第二UE的接入层标识、第一传输通道的标识信息，所述第一传输通道为所述第二UE与所述第二节点之间传输所述第一信息的通道。
在一种可能的实现方法中，所述发送单元2610，具体用于：向所述第二节点发送所述第一数据包，所述第二节点用于将所述第一数据包发送至所述第二UE；或者，向第三节点发送所述第一数据包，所述第三节点用于通过所述第二节点将所述第一数据包发送至所 述第二UE，所述第三节点为所述第一节点与所述第二节点之间的中间节点。
在一种可能的实现方法中，所述接收单元2620，还用于在接收来自接入网节点的第二节点的标识信息之前，通过第二传输通道接收来自所述第一UE的第二数据包，所述第二数据包携带所述第一信息和所述第二UE的应用层标识，所述第二传输通道为所述第一UE与所述第一节点之间传输所述第一信息的通道；处理单元2630，用于根据所述第二UE的应用层标识，获取所述第二UE的接入层标识。
在一种可能的实现方法中，所述处理单元2630，具体用于：通过所述发送单元2610向所述接入网节点发送所述第二UE的应用层标识；通过所述接收单元2620接收来自所述接入网节点的所述第二UE的接入层标识。
在一种可能的实现方法中，所述第二UE的应用层标识携带于所述第二数据包的媒体接入控制MAC层头字段或无线链路控制RLC层头字段中。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自所述接入网节点的所述第一传输通道的标识信息。
在一种可能的实现方法中，所述第二信息携带于所述第一数据包的回传适配协议BAP层头字段中。
在一种可能的实现方法中，所述接收单元2620，还用于接收来自所述接入网节点的第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
在一种可能的实现方法中，所述发送单元2610，还用于在所述接收2620单元接收来自所述接入网节点的第一指示信息之前，向所述接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
在一种可能的实现方法中，所述第一节点和所述第二节点均为IAB节点，所述接入网节点为IAB宿主节点。
在第五个实施例中，该通信装置用于实现上述各实施例中对应接入网节点的各个步骤：
接收单元2620，用于接收来自第一节点的第二UE的应用层标识，所述第一节点为第一UE接入的节点；处理单元2630，用于根据所述第二UE的应用层标识，确定所述第二UE的接入层标识；发送单元2610，用于向所述第一节点发送所述第二UE的接入层标识以及第二节点的标识信息，其中，所述第二节点为所述第二UE接入的节点。
在一种可能的实现方法中，所述发送单元2610，还用于向所述第一节点发送第一传输通道的标识信息，其中，所述第一传输通道为所述第二UE与所述第二节点之间传输来自所述第一UE的数据包的通道。
在一种可能的实现方法中，所述发送单元2610，还用于向所述第一节点发送第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
在一种可能的实现方法中，所述接收单元2620，还用于在所述发送单元2610向所述第一节点发送所述第一指示信息之前，接收来自所述第一节点的第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
在一种可能的实现方法中，所述第一节点和所述第二节点均为IAB节点。
可选地，上述通信装置还可以包括存储单元，该存储单元用于存储数据或者指令(也可以称为代码或者程序)，上述各个单元可以和存储单元交互或者耦合，以实现对应的方 法或者功能。例如，处理单元2630可以读取存储单元中的数据或者指令，使得通信装置实现上述实施例中的方法。
应理解以上通信装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且通信装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在通信装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由通信装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一通信装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当通信装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(central processing unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
参考图27，为本申请实施例提供的一种通信装置示意图，用于实现以上实施例中第一节点或接入网节点的操作。如图27所示，该通信装置包括：处理器2710和接口2730，可选地，该通信装置还包括存储器2720。接口2730用于实现与其他设备进行通信。
以上实施例中第一节点或接入网节点执行的方法可以通过处理器2710调用存储器(可以是第一节点或接入网节点中的存储器2720，也可以是外部存储器)中存储的程序来实现。即，第一节点或接入网节点可以包括处理器2710，该处理器2710通过调用存储器中的程序，以执行以上方法实施例中第一节点或接入网节点执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。第一节点或接入网节点可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
具体的，图26中的发送单元2610、接收单元2620和处理单元2630的功能/实现过程可以通过图27所示的通信装置2700中的处理器2710调用存储器2720中存储的计算机可执行指令来实现。或者，图26中的处理单元2630的功能/实现过程可以通过图27所示的通信装置2700中的处理器2710调用存储器2720中存储的计算机执行指令来实现，图26中的发送单元2610和接收单元2620的功能/实现过程可以通过图27中所示的通信装置2700中的接口2730来实现，示例性的，发送单元2610和接收单元2620的功能/实现过程可以通过处理器调用存储器中的程序指令以驱动接口2730来实现。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述 方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”、“任意一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(英文：Digital Versatile Disc，简称：DVD)、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。本申请说明书的上述描述可以使得本领域技术任何可以利用或实现本申请的内容，任何基于所公开内容的修改都应该被认为是本领域显而易见的，本申请所描述的基本原则可以应用到其它变形中而不偏离本申请的发明本质和范围。因此，本申请所公开的内容不仅仅局限于所描述的实施例和设计，还可以扩展到与本申请原则和所公开的新特征一致的最大范围。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (71)

  1. 一种无线通信方法，其特征在于，包括：
    第一节点获取第一信息，所述第一信息包括以下至少一种：所述第一节点的至少一个下一跳节点的负载信息、所述至少一个下一跳节点的干扰信息、所述第一节点与所述至少一个下一跳节点之间的信道质量、所述第一节点通过所述至少一个下一跳节点到达目标节点的链路跳数信息；
    所述第一节点根据所述第一信息，确定通过第二节点进行数据包的传输，其中，所述至少一个下一跳节点包括所述第二节点。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    所述第一节点接收来自接入网节点的所述至少一个下一跳节点的负载信息和/或所述至少一个下一跳节点的干扰信息；或者，
    所述第一节点接收来自第一下一跳节点的所述第一下一跳节点的负载信息和/或所述第一下一跳节点的干扰信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
  3. 如权利要求1或2所述的方法，其特征在于，还包括：
    所述第一节点接收来自接入网节点的所述第一节点与所述至少一个下一跳节点之间的信道质量；或者，
    所述第一节点自行确定所述第一节点与所述至少一个下一跳节点之间的信道质量。
  4. 如权利要求1至3任一项所述的方法，其特征在于，还包括：
    所述第一节点接收来自接入网节点的所述链路跳数信息，其中，所述链路跳数信息与路由标识以及所述下一跳节点的标识信息对应，所述路由标识包括所述目标节点的标识信息和路径标识。
  5. 如权利要求1至3任一项所述的方法，其特征在于，还包括：
    所述第一节点接收来自接入网节点的所述链路跳数信息，其中，所述链路跳数信息指示的链路跳数为所述第一节点通过所述下一跳节点到达所述目标节点的最小链路跳数，所述链路跳数信息与所述下一跳节点的标识信息以及所述目标节点的标识信息对应。
  6. 如权利要求1所述的方法，其特征在于，还包括：
    所述第一节点接收来自第一下一跳节点的所述第一下一跳节点的标识信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
  7. 如权利要求6所述的方法，其特征在于，所述第一节点接收来自第一下一跳节点的所述第一下一跳节点的标识信息，包括：
    所述第一节点通过所述第一节点与所述第一下一跳节点之间的侧行链路接收来自所述第一下一跳节点的所述第一下一跳节点的标识信息。
  8. 如权利要求6或7所述的方法，其特征在于，还包括：
    所述第一节点接收来自所述第一下一跳节点的所述第一下一跳节点能够到达的目标节点的标识信息。
  9. 如权利要求8所述的方法，其特征在于，还包括：
    所述第一节点接收来自所述第一下一跳节点的所述第一下一跳节点到达所述能够到达的目标节点的最小链路跳数信息。
  10. 如权利要求6至9任一项所述的方法，其特征在于，还包括：
    所述第一节点接收来自接入网节点的第一指示信息，所述第一指示信息指示所述第一节点接收所述数据包的第一承载与所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述至少一个下一跳节点之间的侧行链路上的无线承载或无线链路控制信道。
  11. 如权利要求6至10任一项所述的方法，其特征在于，还包括：
    所述第一节点向接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持侧行链路。
  12. 如权利要求11所述的方法，其特征在于，还包括：
    所述第一节点接收来自接入网节点的第三指示信息，所述第三指示信息指示使能所述第一节点的侧行链路。
  13. 如权利要求1至12任一项所述的方法，其特征在于，所述第一节点和所述第二节点均为IAB节点，所述目标节点为IAB宿主节点或接入IAB节点；或者，
    所述第一节点为IAB宿主节点，所述第二节点为IAB节点，所述目标节点为接入IAB节点。
  14. 一种无线通信方法，其特征在于，包括：
    第一节点接收来自接入网节点的第二指示信息，所述第二指示信息指示使能所述第一节点的侧行链路；
    第一节点根据所述第二指示信息，使能所述第一节点的侧行链路。
  15. 如权利要求14所述的方法，其特征在于，所述第一节点接收来自所述接入网节点的第二指示信息之前，所述方法还包括：
    所述第一节点向所述接入网节点发送第一指示信息，所述第一指示信息指示所述第一节点支持侧行链路。
  16. 如权利要求14或15所述的方法，其特征在于，所述第一节点为IAB节点，所述接入网节点为IAB宿主节点。
  17. 一种无线通信方法，其特征在于，包括：
    第一节点接收来自接入网节点的指示信息，所述指示信息指示用于所述第一节点接收数据包的第一承载与用于所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述第一节点的下一跳节点之间的侧行链路上的无线承载或无线链路控制信道；
    所述第一节点根据所述指示信息，将从所述第一承载收到的所述数据包，通过所述第二承载发送至所述下一跳节点。
  18. 一种无线通信方法，其特征在于，包括：
    第一节点接收来自接入网节点的第二节点的标识信息，所述第一节点为第一用户设备UE接入的节点，所述第二节点为第二UE接入的节点；
    所述第一节点通过所述第二节点向所述第二UE发送第一数据包，所述第一数据包携带第一信息和第二信息，所述第一信息包括来自所述第一UE的数据或信令，所述第二信息包括以下一项或多项：所述第二UE的接入层标识、第一传输通道的标识信息，所述第一传输通道为所述第二UE与所述第二节点之间传输所述第一信息的通道。
  19. 如权利要求18所述的方法，其特征在于，所述第一节点通过所述第二节点向所 述第二UE发送第一数据包，包括：
    所述第一节点向所述第二节点发送所述第一数据包，所述第二节点用于将所述第一数据包发送至所述第二UE；或者，
    所述第一节点向第三节点发送所述第一数据包，所述第三节点用于通过所述第二节点将所述第一数据包发送至所述第二UE，所述第三节点为所述第一节点与所述第二节点之间的中间节点。
  20. 如权利要求18或19所述的方法，其特征在于，所述第一节点接收来自接入网节点的第二节点的标识信息之前，还包括：
    所述第一节点通过第二传输通道接收来自所述第一UE的第二数据包，所述第二数据包携带所述第一信息和所述第二UE的应用层标识，所述第二传输通道为所述第一UE与所述第一节点之间传输所述第一信息的通道；
    所述第一节点根据所述第二UE的应用层标识，获取所述第二UE的接入层标识。
  21. 如权利要求20所述的方法，其特征在于，所述第一节点根据所述第二UE的应用标识，获取所述第二UE的接入层标识，包括：
    所述第一节点向所述接入网节点发送所述第二UE的应用层标识；
    所述第一节点接收来自所述接入网节点的所述第二UE的接入层标识。
  22. 如权利要求20或21所述的方法，其特征在于，所述第二UE的应用层标识携带于所述第二数据包的媒体接入控制MAC层头字段或无线链路控制RLC层头字段中。
  23. 如权利要求18至22任一项所述的方法，其特征在于，还包括：
    所述第一节点接收来自所述接入网节点的所述第一传输通道的标识信息。
  24. 如权利要求18至23任一项所述的方法，其特征在于，所述第二信息携带于所述第一数据包的回传适配协议BAP层头字段中。
  25. 如权利要求18至24任一项所述的方法，其特征在于，还包括：
    所述第一节点接收来自所述接入网节点的第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
  26. 如权利要求25所述的方法，其特征在于，所述第一节点接收来自所述接入网节点的第一指示信息之前，还包括：
    所述第一节点向所述接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
  27. 如权利要求18至26任一项所述的方法，其特征在于，所述第一节点和所述第二节点均为IAB节点，所述接入网节点为IAB宿主节点。
  28. 一种无线通信方法，其特征在于，包括：
    接入网节点接收来自第一节点的第二UE的应用层标识，所述第一节点为第一UE接入的节点；
    所述接入网节点根据所述第二UE的应用层标识，确定所述第二UE的接入层标识；
    所述接入网节点向所述第一节点发送所述第二UE的接入层标识以及第二节点的标识信息，其中，所述第二节点为所述第二UE接入的节点。
  29. 如权利要求28所述的方法，其特征在于，还包括：
    所述接入网节点向所述第一节点发送第一传输通道的标识信息，其中，所述第一传输通道为所述第二UE与所述第二节点之间传输来自所述第一UE的数据包的通道。
  30. 如权利要求28或29所述的方法，其特征在于，还包括：
    所述接入网节点向所述第一节点发送第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
  31. 如权利要求30所述的方法，其特征在于，所述接入网节点向所述第一节点发送所述第一指示信息之前，还包括：
    所述接入网节点接收来自所述第一节点的第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
  32. 如权利要求28至31任一项所述的方法，其特征在于，所述第一节点和所述第二节点均为IAB节点，所述接入网节点为IAB宿主节点。
  33. 一种通信装置，其特征在于，包括：
    接收单元，用于获取第一信息，所述第一信息包括以下至少一种：第一节点的至少一个下一跳节点的负载信息、所述至少一个下一跳节点的干扰信息、所述第一节点与所述至少一个下一跳节点之间的信道质量、所述第一节点通过所述至少一个下一跳节点到达目标节点的链路跳数信息；
    处理单元，用于根据所述第一信息，确定通过第二节点进行数据包的传输，其中，所述至少一个下一跳节点包括所述第二节点。
  34. 如权利要求33所述的装置，其特征在于，所述接收单元，还用于：
    接收来自接入网节点的所述至少一个下一跳节点的负载信息和/或所述至少一个下一跳节点的干扰信息；或者，
    接收来自第一下一跳节点的所述第一下一跳节点的负载信息和/或所述第一下一跳节点的干扰信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
  35. 如权利要求33或34所述的装置，其特征在于，所述接收单元，还用于接收来自接入网节点的所述第一节点与所述至少一个下一跳节点之间的信道质量；或者，
    所述处理单元，还用于自行确定所述第一节点与所述至少一个下一跳节点之间的信道质量。
  36. 如权利要求33至35任一项所述的装置，其特征在于，所述接收单元，还用于接收来自接入网节点的所述链路跳数信息，其中，所述链路跳数信息与路由标识以及所述下一跳节点的标识信息对应，所述路由标识包括所述目标节点的标识信息和路径标识。
  37. 如权利要求33至35任一项所述的装置，其特征在于，所述接收单元，还用于接收来自接入网节点的所述链路跳数信息，其中，所述链路跳数信息指示的链路跳数为所述第一节点通过所述下一跳节点到达所述目标节点的最小链路跳数，所述链路跳数信息与所述下一跳节点的标识信息以及所述目标节点的标识信息对应。
  38. 如权利要求33所述的装置，其特征在于，所述接收单元，还用于接收来自第一下一跳节点的所述第一下一跳节点的标识信息，所述第一下一跳节点为所述至少一个下一跳节点中的任意一个节点。
  39. 如权利要求38所述的装置，其特征在于，所述接收单元，用于接收来自第一下一跳节点的所述第一下一跳节点的标识信息，具体包括：
    用于通过所述第一节点与所述第一下一跳节点之间的侧行链路接收来自所述第一下一跳节点的所述第一下一跳节点的标识信息。
  40. 如权利要求38或39所述的装置，其特征在于，所述接收单元，还用于接收来自 所述第一下一跳节点的所述第一下一跳节点能够到达的目标节点的标识信息。
  41. 如权利要求40所述的装置，其特征在于，所述接收单元，还用于接收来自所述第一下一跳节点的所述第一下一跳节点到达所述能够到达的目标节点的最小链路跳数信息。
  42. 如权利要求38至41任一项所述的装置，其特征在于，所述接收单元，还用于接收来自接入网节点的第一指示信息，所述第一指示信息指示所述第一节点接收所述数据包的第一承载与所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述至少一个下一跳节点之间的侧行链路上的无线承载或无线链路控制信道。
  43. 如权利要求38至42任一项所述的装置，其特征在于，所述装置还包括发送单元，用于向接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持侧行链路。
  44. 如权利要求43所述的装置，其特征在于，所述接收单元，还用于接收来自所述接入网节点的第三指示信息，所述第三指示信息指示使能所述第一节点的侧行链路。
  45. 如权利要求33至44任一项所述的装置，其特征在于，所述第一节点和所述第二节点均为IAB节点，所述目标节点为IAB宿主节点或接入IAB节点；或者，
    所述第一节点为IAB宿主节点，所述第二节点为IAB节点，所述目标节点为接入IAB节点。
  46. 一种通信装置，其特征在于，包括：
    接收单元，用于接收来自接入网节点的第二指示信息，所述第二指示信息指示使能所述第一节点的侧行链路；
    处理单元，用于根据所述第二指示信息，使能第一节点的侧行链路。
  47. 如权利要求46所述的装置，其特征在于，所述装置还包括发送单元，用于在所述接收单元接收来自所述接入网节点的第二指示信息之前，向所述接入网节点发送第一指示信息，所述第一指示信息指示所述第一节点支持侧行链路。
  48. 如权利要求46或47所述的装置，其特征在于，所述第一节点为IAB节点，所述接入网节点为IAB宿主节点。
  49. 一种通信装置，其特征在于，包括：
    接收单元，用于接收来自接入网节点的指示信息，所述指示信息指示用于第一节点接收数据包的第一承载与用于所述第一节点发送所述数据包的第二承载之间的映射关系，所述第一承载为回传无线链路控制信道，所述第二承载为所述第一节点与所述第一节点的下一跳节点之间的侧行链路上的无线承载或无线链路控制信道；
    处理单元，用于根据所述指示信息，将从所述第一承载收到的所述数据包，通过所述第二承载发送至所述下一跳节点。
  50. 一种通信装置，用于第一节点，其特征在于，包括：
    接收单元，用于接收来自接入网节点的第二节点的标识信息，所述第一节点为第一用户设备UE接入的节点，所述第二节点为第二UE接入的节点；
    发送单元，用于通过所述第二节点向所述第二UE发送第一数据包，所述第一数据包携带第一信息和第二信息，所述第一信息包括来自所述第一UE的数据或信令，所述第二信息包括以下一项或多项：所述第二UE的接入层标识、第一传输通道的标识信息，所述第一传输通道为所述第二UE与所述第二节点之间传输所述第一信息的通道。
  51. 如权利要求50所述的装置，其特征在于，所述发送单元，具体用于：
    向所述第二节点发送所述第一数据包，所述第二节点用于将所述第一数据包发送至所述第二UE；或者，
    向第三节点发送所述第一数据包，所述第三节点用于通过所述第二节点将所述第一数据包发送至所述第二UE，所述第三节点为所述第一节点与所述第二节点之间的中间节点。
  52. 如权利要求50或51所述的装置，其特征在于，所述接收单元，还用于在接收来自接入网节点的第二节点的标识信息之前，通过第二传输通道接收来自所述第一UE的第二数据包，所述第二数据包携带所述第一信息和所述第二UE的应用层标识，所述第二传输通道为所述第一UE与所述第一节点之间传输所述第一信息的通道；
    所述装置还包括处理单元，用于根据所述第二UE的应用层标识，获取所述第二UE的接入层标识。
  53. 如权利要求52所述的装置，其特征在于，所述处理单元，具体用于：
    通过所述发送单元向所述接入网节点发送所述第二UE的应用层标识；
    通过所述接收单元接收来自所述接入网节点的所述第二UE的接入层标识。
  54. 如权利要求52或53所述的装置，其特征在于，所述第二UE的应用层标识携带于所述第二数据包的媒体接入控制MAC层头字段或无线链路控制RLC层头字段中。
  55. 如权利要求50至54任一项所述的装置，其特征在于，所述接收单元，还用于接收来自所述接入网节点的所述第一传输通道的标识信息。
  56. 如权利要求50至55任一项所述的装置，其特征在于，所述第二信息携带于所述第一数据包的回传适配协议BAP层头字段中。
  57. 如权利要求50至56任一项所述的装置，其特征在于，所述接收单元，还用于接收来自所述接入网节点的第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
  58. 如权利要求57所述的装置，其特征在于，所述发送单元，还用于在所述接收单元接收来自所述接入网节点的第一指示信息之前，向所述接入网节点发送第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
  59. 如权利要求50至58任一项所述的装置，其特征在于，所述第一节点和所述第二节点均为IAB节点，所述接入网节点为IAB宿主节点。
  60. 一种通信装置，其特征在于，包括：
    接收单元，用于接收来自第一节点的第二UE的应用层标识，所述第一节点为第一UE接入的节点；
    处理单元，用于根据所述第二UE的应用层标识，确定所述第二UE的接入层标识；
    发送单元，用于向所述第一节点发送所述第二UE的接入层标识以及第二节点的标识信息，其中，所述第二节点为所述第二UE接入的节点。
  61. 如权利要求60所述的装置，其特征在于，所述发送单元，还用于向所述第一节点发送第一传输通道的标识信息，其中，所述第一传输通道为所述第二UE与所述第二节点之间传输来自所述第一UE的数据包的通道。
  62. 如权利要求60或61所述的装置，其特征在于，所述发送单元，还用于向所述第一节点发送第一指示信息，所述第一指示信息指示所述第一节点使能本地传递功能。
  63. 如权利要求62所述的装置，其特征在于，所述接收单元，还用于在所述发送单 元向所述第一节点发送所述第一指示信息之前，接收来自所述第一节点的第二指示信息，所述第二指示信息指示所述第一节点支持本地传递功能。
  64. 如权利要求60至63任一项所述的装置，其特征在于，所述第一节点和所述第二节点均为IAB节点。
  65. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求1至27任一项所述的方法。
  66. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求28至32任一项所述的方法。
  67. 一种通信装置，其特征在于，用于执行权利要求1至27任一项所述的方法。
  68. 一种通信装置，其特征在于，用于执行权利要求28至32任一项所述的方法。
  69. 一种通信系统，其特征在于，包括如权利要求50至59中任一项所述的通信装置，和如权利要求60至64中任一项所述的通信装置。
  70. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1至32任一项所述的方法。
  71. 一种计算机程序产品，其特征在于，所述计算机程序产品包括指令，当所述指令被运行时，实现如权利要求1至32中任一项所述的方法。
PCT/CN2021/073856 2021-01-26 2021-01-26 无线通信方法、通信装置及通信系统 WO2022160108A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180088406.8A CN116711379A (zh) 2021-01-26 2021-01-26 无线通信方法、通信装置及通信系统
PCT/CN2021/073856 WO2022160108A1 (zh) 2021-01-26 2021-01-26 无线通信方法、通信装置及通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/073856 WO2022160108A1 (zh) 2021-01-26 2021-01-26 无线通信方法、通信装置及通信系统

Publications (1)

Publication Number Publication Date
WO2022160108A1 true WO2022160108A1 (zh) 2022-08-04

Family

ID=82652967

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/073856 WO2022160108A1 (zh) 2021-01-26 2021-01-26 无线通信方法、通信装置及通信系统

Country Status (2)

Country Link
CN (1) CN116711379A (zh)
WO (1) WO2022160108A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230027099A1 (en) * 2021-07-26 2023-01-26 Qualcomm Incorporated Architecture for integrated access and backhaul with sidelink
WO2024148579A1 (zh) * 2023-01-12 2024-07-18 华为技术有限公司 通信方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107231669A (zh) * 2016-03-23 2017-10-03 中兴通讯股份有限公司 一种数据传输装置方法和装置
CN107615844A (zh) * 2015-04-17 2018-01-19 松下电器（美国）知识产权公司 在侧行链路控制时段期间的多邻近服务组通信
CN109219102A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种数据转发方法和装置
CN110475382A (zh) * 2018-05-11 2019-11-19 电信科学技术研究院有限公司 无线回程节点的承载映射方法、无线回程节点和施主基站
WO2020195221A1 (en) * 2019-03-28 2020-10-01 Mitsubishi Electric Corporation Method, computer software and computer-readable non-transient recording medium of dynamic attribution of an admission control to an integrated access and backhaul node

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107615844A (zh) * 2015-04-17 2018-01-19 松下电器（美国）知识产权公司 在侧行链路控制时段期间的多邻近服务组通信
CN107231669A (zh) * 2016-03-23 2017-10-03 中兴通讯股份有限公司 一种数据传输装置方法和装置
CN109219102A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种数据转发方法和装置
CN110475382A (zh) * 2018-05-11 2019-11-19 电信科学技术研究院有限公司 无线回程节点的承载映射方法、无线回程节点和施主基站
WO2020195221A1 (en) * 2019-03-28 2020-10-01 Mitsubishi Electric Corporation Method, computer software and computer-readable non-transient recording medium of dynamic attribution of an admission control to an integrated access and backhaul node

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230027099A1 (en) * 2021-07-26 2023-01-26 Qualcomm Incorporated Architecture for integrated access and backhaul with sidelink
WO2024148579A1 (zh) * 2023-01-12 2024-07-18 华为技术有限公司 通信方法及装置

Also Published As

Publication number Publication date
CN116711379A (zh) 2023-09-05

Similar Documents

Publication Publication Date Title
JP7378433B2 (ja) データパケットの送信方法、受信方法及び装置ならびにデータパケットの伝送システム
CN110636583B (zh) 路径变更方法及装置
CN110351024B (zh) 数据传输方法和装置
EP3764732B1 (en) Packet transmission methods and apparatus using two network tunnels
WO2019214747A1 (zh) 一种配置方法、数据传输方法和装置
JP7503625B2 (ja) ルーティングおよびベアラマッピング構成のための方法およびデバイス
WO2021027860A1 (zh) 路由方法、bsr的生成方法、装置和存储介质
US9893986B2 (en) Label distribution method and device
CN111865802B (zh) 一种通信方法及装置
WO2019137504A1 (zh) 节点和通信方法
WO2021232841A1 (zh) 通信方法和装置
WO2022160108A1 (zh) 无线通信方法、通信装置及通信系统
WO2020192654A1 (zh) 配置无线链路控制rlc承载的方法和装置
JP2020156088A (ja) パケット伝送方法及び装置
WO2021062803A1 (zh) 一种数据包传输方法及装置
US20230388894A1 (en) Method and apparatus for packet rerouting
WO2016101263A1 (zh) 通信方法和网元设备
CN117527686A (zh) 通信方法、设备及系统
WO2023068255A1 (ja) 通信制御方法及び境界ｉａｂノード
WO2022156785A1 (zh) 一种通信方法及通信装置
WO2022006907A1 (zh) 通信方法及装置
WO2021087924A1 (zh) 一种通信方法及装置
JP7506835B2 (ja) 通信制御方法、中継ノード、セルラ通信システム、チップセット、及びプログラム
US20240022965A1 (en) Traffic transmission schemes in wireless communications
WO2023068257A1 (ja) 通信制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21921728

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180088406.8

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21921728

Country of ref document: EP

Kind code of ref document: A1