WO2020164557A1 - 一种通信方法及相关装置 - Google Patents

一种通信方法及相关装置 Download PDF

Info

Publication number
WO2020164557A1
WO2020164557A1 PCT/CN2020/075147 CN2020075147W WO2020164557A1 WO 2020164557 A1 WO2020164557 A1 WO 2020164557A1 CN 2020075147 W CN2020075147 W CN 2020075147W WO 2020164557 A1 WO2020164557 A1 WO 2020164557A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
data packet
network node
layer
node
Prior art date
Application number
PCT/CN2020/075147
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 EP20756292.7A priority Critical patent/EP3917105A4/en
Priority to BR112021016053-1A priority patent/BR112021016053A2/pt
Publication of WO2020164557A1 publication Critical patent/WO2020164557A1/zh
Priority to US17/401,587 priority patent/US20210377840A1/en

Links

Images

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • 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/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and related devices.
  • a transmission path may include at least a section of wireless backhaul link and a section of wireless access link.
  • Adaptation layer which is referred to as the Adaptation layer in this article for convenience of presentation.
  • the current communication standard does not define a process for processing data packets on the Adapt layer on the wireless backhaul link, and improper data packet processing procedures will make the data packets unable to be correctly transmitted on the wireless backhaul link.
  • the embodiments of the present application provide a communication method and related devices to enable data packets to be correctly transmitted on the wireless backhaul link.
  • a communication method including: a first entity in an adaptation layer entity of a network node receives a data packet including an adaptation layer header and an adaptation layer payload submitted from a protocol layer entity of a lower protocol layer; The first entity judges whether the network node is the destination node of the data packet routing at the adaptation layer, and processes the data packet according to the judgment result.
  • the first entity is located on the receiving side of the network node.
  • the network node determines whether the network node is the destination node of the adaptation layer routing will directly affect the processing of subsequent data packets. Therefore, the network node processes the data packet according to the judgment result of whether it is the destination node of the data packet routing in the adaptation layer, can process the data packet correctly, and prevent errors in the processing of the data packet.
  • the judgment result is: the network node is the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node transfers the data
  • the adaptation layer load in the packet is delivered to the second entity, which is the protocol layer entity of the protocol layer of the F1 interface or the protocol layer entity of the upper protocol layer of the adaptation layer.
  • the network node when the network node is the destination node of the data packet routing at the adaptation layer, for example, when the network node is the access IAB node or the host node or Donor-DU, the next hop of the data packet There is no adaptation layer in the node. Therefore, the network node can deliver the adaptation layer load to the second entity, thereby avoiding the problem that the next hop node of the data packet cannot parse the data packet.
  • the judgment result is: the network node is the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node pairs the data
  • the adaptation layer load in the packet is decompressed, and the decompressed adaptation layer load is delivered to the second entity.
  • the network node when the network node is the destination node of the data packet routing in the adaptation layer, for example, when the network node is the access IAB node or the host node or Donor-DU, the next hop of the data packet There is no adaptation layer in the node. If header compression is performed on the adaptation layer load of the packet in the IAB network, the network node also needs to decompress the adaptation layer load to prevent the next hop node of the packet from being unable to The problem of decompression header compression at the adaptation layer of the data packet.
  • the judgment result is: the network node is the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node pairs the data The packet is de-headed and compressed, and the adaptation layer payload in the de-headed compressed data packet is delivered to the second entity.
  • the network node when the network node is the destination node of the data packet routing at the adaptation layer, for example, when the network node is the access IAB node or the host node or Donor-DU, the next hop of the data packet There is no adaptation layer in the node. If header compression is performed on the data packet in the IAB network, the network node also needs to decompress the data packet, so as to prevent the next hop node of the data packet from being unable to decompress the data packet and unable to decompress the data packet. Problem parsing data packets.
  • the judgment result is: the network node is the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node transfers the data The packet is stored in the buffer of the adaptation layer.
  • the first entity of the network node stores the data packet in the buffer of the adaptation layer. In order to carry out further processing, so as to ensure the correct processing of the data packet.
  • the judgment result is: the network node is not the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node transfers the data
  • the packet is delivered to a third entity, which is a protocol layer entity of the protocol layer of the wireless backhaul interface or a protocol layer entity of the lower protocol layer of the adaptation layer.
  • the third entity in the first aspect is located on the sending side of the network node.
  • This possible implementation is in the case that the network node is not the destination node of the data packet routing at the adaptation layer, for example, when the network node is an intermediate IAB node, since there is an adaptation layer in the next hop node of the data packet, ,
  • the network node can directly submit the data packet to the third entity without removing the adaptation layer header.
  • the next hop node of the data packet can forward the data packet at the adaptation layer or perform other tasks according to the adaptation layer header in the data packet. Processing to ensure the correct transmission of data packets.
  • the judgment result is: the network node is not the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node transfers the data
  • a third entity which is the protocol layer entity of the protocol layer of the wireless backhaul interface or the protocol layer of the lower layer of the adaptation layer. Layer entity.
  • This possible implementation is in the case that the network node is not the destination node of the data packet routing at the adaptation layer, for example, when the network node is an intermediate IAB node, since there is an adaptation layer in the next hop node of the data packet, When the network node sends the adaptation layer load, it also needs to submit the information in the adaptation layer header to the third entity.
  • the next hop node of the data packet can forward the data at the adaptation layer according to the information in the adaptation layer header. Packets or other processing to ensure the correct transmission of data packets.
  • the judgment result is: the network node is not the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node pairs the data
  • the adaptation layer load in the packet is decompressed, and the decompressed adaptation layer load and the information in the adaptation layer header in the data packet are submitted to a third entity, which is the wireless backhaul interface
  • This possible implementation method when the network node is not the destination node of the data packet routing at the adaptation layer, for example, when the network node is an intermediate IAB node, if the header compression method is hop-by-hop header compression, the upper part of the data packet The one-hop node performs header compression on the adaptation layer load of the data packet, and the first entity of the network node also needs to de-header the adaptation layer load.
  • the judgment result is: the network node is not the destination node of the data packet routing at the adaptation layer, and the first entity of the network node processes the data packet according to the judgment result, including: the first entity of the network node pairs the data
  • the packet is de-headed and compressed, and the adaptation layer load in the de-header-compressed data packet and the information in the adaptation-layer header in the de-header-compressed data packet are submitted to a third entity, which is a wireless backhaul
  • This possible implementation method when the network node is not the destination node of the data packet routing at the adaptation layer, for example, when the network node is an intermediate IAB node, if the header compression method is hop-by-hop header compression, the upper part of the data packet The one-hop node compresses the header of the data packet, and the first entity of the network node also needs to decompress the header of the data packet.
  • the data packet is a data PDU of the adaptation layer.
  • the data packet is a control PDU of the adaptation layer.
  • the method further includes one or more of the following: the first entity of the network node determines the next hop node of the data packet, and the first entity of the network node submits to the third entity for instructions One-hop node information; or, the first entity of the network node submits the identification of the first service differentiation channel to the third entity, and the first service differentiation channel is the service differentiation channel from which the data packet received by the first entity comes; , The service differentiation channel is a logical channel or an RLC channel or an RLC bearer; or, the first entity of the network node determines the second service differentiation channel for delivering the data packet to the next hop node of the data packet; the first entity of the network node sends the third The entity submits the identification of the second service differentiated channel; where the second service differentiated channel is a service differentiated channel through which the third entity sends data packets, and the service differentiated channel is a logical channel or an RLC channel or an RLC bearer.
  • the first entity of the network node may also submit the next hop node and/or the second service differentiation channel of the data packet to the third entity, or be used to determine the next hop node and/or of the data packet
  • the information of the second service differentiated channel that is, the identifier of the first service differentiated channel
  • the first entity of the network node judges whether the network node is the destination node of the data packet routing at the adaptation layer, including: the first entity of the network node judges whether the data packet is routed at the adaptation layer according to the The routing information, whether the adaptation layer header in the data packet contains routing information, and whether the data packet is one or more of the control PDUs determines whether the network node is the destination node of the data packet routing at the adaptation layer.
  • This possible implementation provides multiple methods for judging whether a network node is the destination node of the adaptation layer routing, so that this application can be applied to different scenarios.
  • a network node including: an acquiring unit configured to receive a data packet including an adaptation layer header and an adaptation layer payload delivered from a protocol layer entity of a lower protocol layer of the adaptation layer of the network node; The judgment unit is used to judge whether the network node is the destination node of the data packet routing at the adaptation layer; the processing unit is used to process the data packet according to the judgment result.
  • the network node of the second aspect is used to execute the method provided in the first aspect. Therefore, the beneficial effects of the network node provided in the second aspect can be referred to the method provided in the first aspect, which is not repeated here.
  • a communication method including: a third entity of a network node receives a data packet from a first entity, the first entity and the third entity are both adaptation layer entities; the third entity of the network node passes through the second entity
  • the service differentiation channel delivers the data packet to the fourth entity; among them, the fourth entity is the protocol layer entity of the lower protocol layer of the adaptation layer, the second service differentiation channel corresponds to the next hop node of the data packet, and the service differentiation channel is logical Channel or RLC channel or RLC bearer.
  • the first entity of the network node is located on the receiving side of the network node, and the third entity of the network node is located on the transmitting side of the network node.
  • the third entity of the network node delivers the data packet to the fourth entity through the second service differentiated channel corresponding to the next hop node of the data packet, which can ensure that the data packet is correctly transmitted to the downstream of the data packet.
  • One-hop node One-hop node.
  • the method when the data packet is a data packet including an adaptation layer load, the method further includes: a third entity of the network node adds an adaptation layer header to the data packet; and the third entity of the network node The entity delivers the data packet to the fourth entity through the second service differentiation channel, including: the third entity of the network node delivers the data packet with the adaptation layer header added to the fourth entity through the second service differentiation channel.
  • the third entity of the network node may add an adaptation layer header to the data packet, so that subsequent nodes can forward the data packet or perform other processing according to the information in the adaptation layer header.
  • the method further includes one or more of the following: the third entity of the network node determines the next hop node for the data packet; or the third entity of the network node determines the second service for the data packet Distinguish the channel.
  • the third entity of the network node can determine the next hop node and/or the second service differentiated channel for delivering the data packet, so as to ensure that the third entity correctly delivers the data packet to the lower protocol layer.
  • the third entity of the network node determines the second service differentiation channel for the data packet, including: the third entity of the network node determines the second service differentiation channel according to the first service differentiation channel, and the first service differentiation channel
  • the channel is the service differentiation channel from which the data packet received by the first entity comes.
  • the third entity of the network node determines the second service differentiation channel for the data packet, including: the third entity of the network node determines the RB of the terminal according to the identity of the terminal to which the data packet belongs, or One or more of the correspondences between the service differentiation channels determine the second service differentiation channel.
  • the third entity of the network node determines the second service differentiation channel for the data packet, including: the third entity of the network node determines the second service differentiation channel according to the QoS label carried in the data packet, and the relationship between the QoS label and the service differentiation channel The corresponding relationship between the two determines the second service differentiation channel.
  • the third entity of the network node determines the second service differentiation channel for the data packet, including: the third entity of the network node receives the identifier of the second service differentiation channel from the first entity; The three entities determine the second service differentiation channel according to the identifier of the second service differentiation channel.
  • the third aspect provides a variety of methods for determining the differentiated channels of the second service, so that the method can be flexibly applied to different scenarios.
  • the third entity of the network node determines the next hop node for the data packet, including: the third entity of the network node receives information indicating the next hop node from the first entity; The third entity determines the next hop node according to the information used to indicate the next hop node.
  • the method before the third entity of the network node adds an adaptation layer header to the data packet, the method further includes: the third entity of the network node performs header compression on the data packet.
  • the third entity of the network node can reduce the header overhead of the data packet in the wireless backhaul link transmission process by performing header compression on the data packet, and reduce air interface resource consumption.
  • the method further includes: the third entity of the network node performs header compression on the data packet after the adaptation layer header is added; the third entity of the network node adds the adaptation through the second service differentiation channel
  • the data packet after the layer header is delivered to the fourth entity, including: the third entity of the network node will add the adaptation layer header through the second service differentiation channel and deliver the data packet compressed by the header to the fourth entity.
  • the third entity of the network node can reduce the header overhead of the data packet in the wireless backhaul link transmission process by performing header compression on the data packet, and reduce air interface resource consumption.
  • a network node including: an acquisition unit, configured to receive a data packet from a first entity in the adaptation layer entity; and a delivery unit, configured to deliver the data packet to the fourth entity through a second service differentiation channel Entity; where the fourth entity is a protocol layer entity of the lower protocol layer of the adaptation layer, the second service differentiation channel corresponds to the next hop node of the data packet, and the service differentiation channel is a logical channel or an RLC channel or an RLC bearer.
  • the network node of the fourth aspect is used to implement the method provided by the third aspect. Therefore, the beneficial effects of the network node provided in the fourth aspect can be referred to the method provided in the third aspect, which will not be repeated here.
  • a communication method including: a first entity of a network node receives a data packet from a fifth entity and adds an adaptation layer header to the data packet; wherein, the fifth entity is the protocol layer of the protocol layer of the F1 interface
  • the entity or the protocol layer entity of the upper protocol layer of the adaptation layer the first entity is the adaptation layer entity
  • the data packet is the data packet including the adaptation layer load; the first entity of the network node will add the adaptation layer through the third service differentiation channel.
  • the data packet after the configuration layer header is delivered to the sixth entity.
  • the sixth entity is the protocol layer entity of the lower protocol layer of the adaptation layer.
  • the third service differentiation channel corresponds to the next hop node of the data packet, and the service differentiation channel is a logical channel Or RLC channel or RLC bearer.
  • the first entity of the network node delivers the data packet to the sixth entity through the third service differentiated channel corresponding to the next hop node of the data packet, which can ensure that the data packet is correctly transmitted to the downstream of the data packet.
  • One-hop node One-hop node.
  • the method further includes one or more of the following: the first entity of the network node determines the next hop node of the data packet; or the first entity of the network node determines the third service differentiation channel.
  • the first entity of the network node can determine the next hop node and/or the third service differentiated channel for delivering the data packet, so as to ensure that the first entity correctly delivers the data packet to the lower protocol layer.
  • the method before the first entity of the network node adds an adaptation layer header to the data packet, the method further includes: the first entity of the network node performs header compression on the data packet.
  • the first entity of the network node can reduce the header overhead of the data packet during the transmission of the wireless backhaul link and reduce the consumption of air interface resources by performing header compression on the data packet.
  • the method further includes: the first entity of the network node performs header compression on the data packet after adding the adaptation layer header; the first entity of the network node adds the adaptation through the third service differentiation channel
  • the data packet after the layer header is delivered to the sixth entity, including: the first entity of the network node delivers the data packet with the adaptation layer header added and header compressed to the sixth entity through the third service differentiation channel.
  • the first entity of the network node can reduce the header overhead of the data packet during the transmission of the wireless backhaul link and reduce the consumption of air interface resources by performing header compression on the data packet.
  • a network node including: an acquisition unit for receiving data packets from a fifth entity, the fifth entity being a protocol layer entity of the protocol layer of the F1 interface or a protocol layer of the upper protocol layer of the adaptation layer Entity, the data packet is a data packet including the adaptation layer payload; the adding unit is used to add an adaptation layer header to the data packet; the delivery unit is used to deliver the data packet with the adaptation layer header added through the third service differentiation channel
  • the sixth entity is a protocol layer entity of the lower protocol layer of the adaptation layer
  • the third service differentiation channel corresponds to the next hop node of the data packet
  • the service differentiation channel is a logical channel or an RLC channel or an RLC bearer.
  • the network node of the sixth aspect is used to implement the method provided by the fifth aspect. Therefore, the beneficial effects of the network node provided in the sixth aspect can be referred to the method provided in the fifth aspect, which will not be repeated here.
  • a method for reconstruction of an adaptation layer which includes: an upper protocol layer of an adaptation layer of a network node sends adaptation layer reconstruction indication information to an adaptation layer of the network node; and adaptation of the network node
  • the layer receives the adaptation layer reconstruction indication information from the upper protocol layer; the adaptation layer of the network node reconstructs the adaptation layer according to the adaptation layer reconstruction indication information.
  • the method provided by the seventh aspect can rebuild the Adapt layer of the network node when the IAB network topology changes to provide guarantee for lossless data transmission, avoid the problem of packet loss due to changes in the wireless backhaul link topology, and improve data transmission Reliability.
  • the adaptation layer of the network node reconstructs the adaptation layer according to the adaptation layer reconstruction instruction information, including: the adaptation layer of the network node configures a new adaptation layer according to the adaptation layer reconstruction instruction information One or more of a routing and forwarding table or a new bearing mapping relationship.
  • the method further includes: the adaptation layer of the network node sends the data in the new adaptation layer routing and forwarding table according to the configured new adaptation layer routing and forwarding table The next hop node retransmits the unsuccessfully sent data packet.
  • This possible implementation can avoid packet loss by the terminal by retransmitting the unsuccessfully sent data packet.
  • a network node including: a sending unit, configured to send adaptation layer reconstruction instruction information to an adaptation layer of the network node; and a receiving unit, configured to receive adaptation layer reconstruction information from an upper protocol layer of the adaptation layer Configuration layer reconstruction instruction information; a reconstruction unit for reconstructing the adaptation layer according to the adaptation layer reconstruction indication information.
  • the sending unit is located in an upper protocol layer of the adaptation layer of the network node
  • the receiving unit and the reconstruction unit are located in the adaptation layer of the network node.
  • the reconstruction unit is specifically configured to configure one or more of a new adaptation layer routing and forwarding table or a new bearer mapping relationship according to the adaptation layer reconstruction instruction information.
  • the sending unit is further configured to: according to the configured new adaptation layer routing and forwarding table, retransmit to the next hop node in the new adaptation layer routing and forwarding table Packets that were not sent successfully.
  • the network node of the eighth aspect is used to implement the method provided by the seventh aspect. Therefore, the beneficial effects of the network node provided by the eighth aspect can be referred to the method provided by the seventh aspect, which will not be repeated here.
  • a network node including a processor.
  • the processor is connected to the memory, the memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, so as to implement any one of the methods provided in the first aspect, the third aspect, the fifth aspect, or the seventh aspect.
  • the memory and the processor can be integrated together or can be independent devices. In the latter case, the memory can be located in the network node or outside the network node.
  • the processor includes a logic circuit and an input interface and/or an output interface.
  • the output interface is used to execute the sending action in the corresponding method
  • the input interface is used to execute the receiving action in the corresponding method.
  • the network node further includes a communication interface and a communication bus, and the processor, memory, and communication interface are connected through the communication bus.
  • the communication interface is used to perform the sending and receiving actions in the corresponding method.
  • the communication interface may also be called a transceiver.
  • the communication interface includes a transmitter and a receiver. In this case, the transmitter is used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.
  • the network node exists in the form of a chip product.
  • a computer-readable storage medium including instructions, which when run on a computer, cause the computer to execute any one of the first aspect, the third aspect, the fifth aspect, or the seventh aspect method.
  • a computer program product containing instructions is provided.
  • the instructions run on a computer, the computer executes any of the methods provided in the first, third, fifth or seventh aspects .
  • a system chip is provided, the system chip is applied in a network node, the system chip includes: at least one processor, and related program instructions are executed in the at least one processor to execute the first aspect,
  • the third aspect any one of the methods provided in the fifth or seventh aspect.
  • a thirteenth aspect provides a communication system, including: one or more of the network nodes provided in the second aspect, the fourth aspect, the sixth aspect, or the eighth aspect.
  • Figure 1 is a schematic diagram of an IAB networking scenario provided by an embodiment of the application.
  • Figure 2 is a schematic diagram of nodes in a transmission path provided by an embodiment of the application.
  • 3 to 5 are schematic diagrams of a protocol stack architecture provided by embodiments of the application.
  • FIG. 6 is a schematic diagram of an adaptation layer data packet type provided by an embodiment of this application.
  • FIGS 7 to 9 are schematic diagrams of the correspondence between an adaptation layer entity and an RLC layer entity provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of a format of a status report of an adaptation layer provided by an embodiment of this application.
  • FIG. 11 is a flowchart of a communication method provided by an embodiment of this application.
  • FIG. 12 is a schematic diagram of an implementation manner for processing data packets provided by an embodiment of the application.
  • FIG. 16 is a flowchart of a method for reconstruction of an adaptation layer provided by an embodiment of this application.
  • Figures 17 to 19 are schematic diagrams of the composition of a network node provided by an embodiment of this application.
  • FIG. 20 and FIG. 21 are respectively schematic diagrams of the hardware structure of a network node provided by an embodiment of the application.
  • words such as “first” and “second” are used to distinguish the same items or similar items with substantially the same function and effect. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and order of execution, and words such as “first” and “second” do not limit the difference.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems.
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency-division multiple access
  • the term "system” can be replaced with "network”.
  • the OFDMA system can implement wireless technologies such as evolved universal terrestrial radio access (E-UTRA) and ultra mobile broadband (UMB).
  • E-UTRA is an evolved version of the Universal Mobile Telecommunications System (UMTS).
  • UMTS Universal Mobile Telecommunications System
  • 3rd generation partnership project (3GPP) uses the new version of E-UTRA in long term evolution (LTE) and various versions based on LTE evolution.
  • a fifth-generation (5th-generation, 5G) network using a new radio (NR) is a next-generation communication system under study.
  • the communication system may also be applicable to future-oriented communication technologies, all of which are applicable to the technical solutions provided in the embodiments of the present application.
  • the network elements involved in this application include terminals and wireless backhaul nodes.
  • the terminal in the embodiments of the present application may also be called user equipment (UE), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile equipment, user terminal, wireless communication equipment, User agent or user device.
  • the terminal can also be a station (ST) in a wireless local area network (WLAN), a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, or a wireless local loop (wireless local loop, WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication function, computing device or other processing device connected to wireless modem, vehicle-mounted device, wearable device ( It can also be called a wearable smart device).
  • the terminal may also be a terminal in a next-generation communication system, for example, a terminal in a 5G network or a terminal in an evolved public land mobile network (public land mobile network, PLMN for short).
  • PLMN public land mobile network
  • the wireless backhaul node is used to provide wireless backhaul services for nodes (for example, terminals) that wirelessly access the wireless backhaul node.
  • the wireless backhaul service refers to the data and/or signaling backhaul service provided through the wireless backhaul link.
  • EPS evolved packet system
  • 4G fourth generation
  • the network node that executes the method provided in the embodiment of the present application can be replaced with a network node in the EPS network.
  • the wireless backhaul node in the following may be a wireless backhaul node in a 5G network, for example, a wireless backhaul node in a 5G network It may be called an IAB node, and of course it may have other names, which are not specifically limited in the embodiment of the present application.
  • the wireless backhaul node in the following may be a wireless backhaul node in the EPS network.
  • the wireless backhaul node in the EPS network may be called a relay. Node (relay node, RN for short).
  • both the access link (AL for short) and the backhaul link (BL for short) in the IAB scenario adopt wireless transmission solutions.
  • the IAB node can provide wireless access services for the terminal, and is connected to a donor node through a wireless backhaul link to transmit the user's business data.
  • the donor node may be a donor base station.
  • the host node in the 5G network can be referred to as IAB donor (IAB donor) or DgNB (ie donor gNodeB) for short.
  • the host node can be a complete entity, it can also be a centralized unit (centralized unit, referred to as CU) (herein referred to as the host CU (Donor-CU), or simply referred to as CU) and distributed unit (abbreviated as CU) DU) (herein referred to as the host DU (Donor-DU)) separated form, that is, the host node is composed of Donor-CU and Donor-DU.
  • the host node is composed of Donor-CU and Donor-DU as an example to illustrate the method provided in the embodiments of the present application.
  • the Donor-CU can also be a form in which the user plane (UP) (referred to as CU-UP in this article) and the control plane (CP for short) (referred to as CU-CP in this article) are separated, namely Donor-CU is composed of CU-CP and CU-UP.
  • UP user plane
  • CP control plane
  • the IAB node is connected to the core network via a wired link via the host node.
  • the IAB node is connected to the core network (5G core, 5GC for short) of the 5G network via the host node through a wired link.
  • the IAB node is connected to the evolved packet core (EPC) via the evolved NodeB (eNB) on the control plane, and via the host node and the eNB on the user plane. Connect to EPC.
  • EPC evolved packet core
  • eNB evolved NodeB
  • the IAB network supports multi-hop IAB nodes and multi-connection IAB node networking. Therefore, there may be multiple transmission paths between the terminal and the host node.
  • On a transmission path there is a certain hierarchical relationship between IAB nodes, as well as between IAB nodes and host nodes serving the IAB nodes, and each IAB node regards the node providing the backhaul service as its parent node.
  • each IAB node can be regarded as a child node of its parent node.
  • the parent node of IAB node 1 is the host node
  • IAB node 1 is the parent node of IAB node 2 and IAB node 3
  • IAB node 2 and IAB node 3 are both the parent node of IAB node 4.
  • the parent node of IAB node 5 is IAB node 3.
  • the uplink data packet of the terminal can be transmitted to the host node through one or more IAB nodes, and then sent by the host node to the mobile gateway device (for example, the user plane function (UPF) network element in the 5G network), and downlink The data packet will be received by the host node from the mobile gateway device, and then sent to the terminal via one or more IAB nodes.
  • the mobile gateway device for example, the user plane function (UPF) network element in the 5G network
  • terminal 1 and the host node There are two available transmission paths for the transmission of data packets between terminal 1 and the host node, namely: terminal 1 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ host node, terminal 1 ⁇ IAB node 4 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ host node.
  • terminal 2 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ host node There are three available transmission paths for data packet transmission between terminal 2 and host node, namely: terminal 2 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ host node, terminal 2 ⁇ IAB node 4 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ host node, terminal 2 ⁇ IAB node 5 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ host node.
  • a transmission path between a terminal and a host node may include one or more IAB nodes.
  • Each IAB node needs to maintain a wireless backhaul link facing the parent node, as well as a wireless link with the child node. If an IAB node is a node accessed by a terminal, there is a wireless access link between the IAB node and a child node (that is, a terminal). If an IAB node is a node that provides backhaul services for other IAB nodes, there is a wireless backhaul link between the IAB node and its child nodes (that is, other IAB nodes). Exemplarily, referring to Fig.
  • Terminal 1 accesses IAB node 4 through wireless access link
  • IAB node 4 accesses IAB node 3 through wireless backhaul link
  • IAB node 3 accesses IAB node 1 through wireless backhaul link
  • IAB node 1 through wireless backhaul
  • the transmission link is connected to the host node.
  • the IAB node may be a customer premise equipment (customer premises equipment, CPE for short), a residential gateway (residential gateway, RG for short) and other equipment.
  • CPE customer premises equipment
  • RG residential gateway
  • the method provided in the embodiment of the present application can also be applied to a home access scenario.
  • the host node is composed of IAB nodes under another host node Dual connections are terminal services, etc., which are not listed here.
  • Link Refers to the path between two adjacent nodes in a transmission path.
  • the last hop node of a node refers to the last node in the transmission path containing the node that received the data packet before the node.
  • the last hop node of a node may also be called the last hop node of the data packet.
  • the next hop node of a node refers to the node in the transmission path containing the node that receives the data packet first after the node.
  • the next hop node of the node may also be called the next hop node of the data packet.
  • the entry link of a node refers to the link between the node and the previous hop node of the node, and can also be called the previous hop link of the node.
  • the exit link of a node refers to the link between the node and the next hop node of the node, and can also be called the next hop link of the node.
  • the access IAB node in the embodiment of the present application refers to the IAB node accessed by the terminal, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services for other IAB nodes (for example, access IAB nodes or other intermediate IAB nodes).
  • IAB node 4 is the access IAB node, and IAB node 3 and IAB node 1 are in the middle IAB node.
  • IAB node 3 provides backhaul service for IAB node 4, and IAB node 1 provides backhaul service for IAB node 3.
  • an IAB node is an IAB node.
  • it is an intermediate IAB node. Therefore, whether an IAB node specifically accesses an IAB node or an intermediate IAB node is not fixed and needs to be determined according to specific application scenarios.
  • the IAB node may have the role of a mobile terminal (MT for short) and the role of a DU.
  • MT mobile terminal
  • DU a mobile terminal
  • the terminal is connected to the host node through the IAB node 2 and the IAB node 1.
  • IAB node 1 and IAB node 2 both include a DU part and an MT part.
  • the DU part of IAB node 2 provides access services for the terminal.
  • the DU part of IAB node 1 provides access services for the MT part of IAB node 2.
  • Donor-DU provides access services for the MT part of IAB node 1.
  • the intermediate IAB node has the same protocol stack on the user plane and the control plane. Among them, the MT part and the DU part of the intermediate IAB node may not share the Adapt layer, such as (a) in FIG. 3. The MT part and the DU part of the intermediate IAB node can also share the Adapt layer, such as (b) in FIG. 3.
  • the protocol stacks for accessing IAB nodes are different in the user plane and the control plane. Refer to Figure 3 (c) and Figure 3 (d) respectively.
  • the user plane protocol stack architecture of each node can be seen in Figure 4 (a) or Figure 5 (a), and the control plane protocol stack architecture of each node can be seen in Figure 4 (B) in or (b) in Figure 5.
  • the MT part and the DU part of the intermediate IAB node do not share the Adapt layer as an example for drawing.
  • the MT part and the DU part of the intermediate IAB node share the Adapt layer as an example for drawing.
  • each protocol layer in Figure 3 to Figure 5 is: packet data convergence protocol (packet data convergence protocol, referred to as PDCP) layer, general packet radio service tunneling protocol user plane (general packet radio service tunneling protocol user plane, referred to as GTP) -U) layer, user datagram protocol (UDP) layer, internet protocol (IP) layer, L2 layer (layer 2), L1 layer (layer1), wireless link control ( Radio link control (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, radio resource control (RRC) layer, F1 application protocol (F1) Application protocol (F1AP for short) layer and stream control transmission protocol (SCTP for short) layer.
  • the L2 layer is a link layer.
  • the L2 layer may be a data link layer in an open systems interconnection (OSI) reference model.
  • the L1 layer may be a physical layer.
  • the L1 layer may be a physical layer in the OSI reference model.
  • Figures 4 and 5 show the Donor-DU and Donor-CU protocol layers. If the host node is an entity with complete functions, the host node can retain the protocol stack of the Donor-DU and Donor-CU to the external node interface, without the need for a protocol layer on the internal interface between the Donor-DU and the Donor-CU.
  • Donor-DU In the IAB node-oriented protocol stack architecture, above the IP layer, it can also include the UDP layer and GTP-U layer equivalent to the UDP layer and GTP-U layer in the protocol stack architecture of the DU part in the IAB node. U layer.
  • the F1 interface refers to the logical interface between the IAB node (such as the DU part of the IAB node) and the host node (or Donor-CU or Donor-DU).
  • the F1 interface can also be called the F1* interface, which supports user plane and control surface.
  • the protocol layer of the F1 interface refers to the communication protocol layer on the F1 interface.
  • the user plane protocol layer of the F1 interface may include one or more of the IP layer, the UDP layer, and the GTP-U layer.
  • the user plane protocol layer of the F1 interface further includes a PDCP layer and/or an IP security (IP Security, referred to as IPsec) layer.
  • IP Security IP Security, referred to as IPsec
  • control plane protocol layer of the F1 interface may include one or more of the IP layer, the F1AP layer, and the SCTP layer.
  • control plane protocol layer of the F1 interface further includes one or more of the PDCP layer, the IPsec layer, and the datagram transport layer security (DTLS) layer.
  • DTLS datagram transport layer security
  • the wireless backhaul interface refers to a logical interface between IAB nodes or between an IAB node and a host node (or Donor-DU).
  • the protocol layer of the wireless backhaul interface refers to the communication protocol layer on the wireless backhaul interface.
  • the protocol layer of the wireless backhaul interface includes one or more of the following protocol layers: Adapt layer, RLC layer, MAC layer, and PHY layer.
  • the user plane protocol layer of the F1 interface of the IAB node includes the GTP-U layer, the UDP layer, and the IP layer.
  • the GTP-U layer and UDP layer of the IAB node are equal to Donor-CU
  • the IP layer is equal to Donor-DU.
  • the Donor-DU is the proxy node of the F1 interface between the Donor-CU and the IAB node, and the GTP-U, UDP, and IP layers of the IAB node are equivalent to the Donor-DU.
  • the user plane protocol layer of the F1 interface may also include an IPsec layer and/or a PDCP layer.
  • the IPsec layer or PDCP layer is located above the IP layer and below the GTP-U layer.
  • the control plane protocol layer of the IAB node on the F1 interface includes the F1AP layer, the SCTP layer, and the IP layer.
  • the F1AP layer and SCTP layer of the IAB node are equal to Donor-CU
  • the IP layer is equal to Donor-DU.
  • the Donor-DU is a proxy node of the F1 interface between the Donor-CU and the IAB node, and the F1AP, SCTP, and IP layers of the IAB node are equivalent to the Donor-DU.
  • control plane protocol layer of the F1 interface may also include one or more of the IPsec layer, the PDCP layer, and the DTLS layer.
  • the IPsec layer, PDCP layer, or DTLS layer is located above the IP layer and below the F1AP layer.
  • the sending-side protocol stack of a node refers to the protocol stack facing the next-hop node in the node
  • the receiving-side protocol stack of a node refers to the protocol stack facing the previous-hop node in the node.
  • the terminal-oriented protocol stack in the DU part of the access IAB node is the receiving-side protocol stack, which faces the host node or Donor-CU.
  • the protocol stack is the sending-side protocol stack
  • the protocol stack of the MT part connected to the IAB node is the sending-side protocol stack
  • the protocol stack of the DU part of the middle IAB node is the receiving-side protocol stack
  • the protocol stack of the MT part of the middle IAB node is the sending Side protocol stack
  • the IAB node-oriented protocol stack in Donor-DU is the receiving side protocol stack
  • the Donor-CU-oriented protocol stack in Donor-DU is the sending side protocol stack.
  • the terminal-oriented protocol stack in the DU part of the access IAB node is the sending-side protocol stack
  • the protocol stack facing the host node or Donor-CU is the receiving-side protocol stack
  • the protocol stack of the MT part of the access IAB node It is the receiving side protocol stack
  • the protocol stack of the DU part of the intermediate IAB node is the sending side protocol stack
  • the protocol stack of the MT part of the intermediate IAB node is the receiving side protocol stack
  • the protocol stack facing the IAB node in the Donor-DU is the sending side Protocol stack
  • Donor-CU-oriented protocol stack in Donor-DU is the receiving side protocol stack.
  • the protocol stack on the receiving side includes an Adapt layer entity
  • the protocol stack on the transmitting side also includes an Adapt layer entity.
  • the transmitting side protocol stack is referred to as the transmitting side
  • the receiving side protocol stack is referred to as the receiving side.
  • the upper and lower relationship of the protocol layer is defined as: in the process of a node sending data, the protocol layer that processes the data packet first is above the protocol layer that processes the data packet later, that is, the data is processed first.
  • the protocol layer where the packet is processed can be considered as the upper layer of the protocol layer that processes the data packet later; or, in the process of receiving data by a node, the protocol layer that processes the data packet first then processes the data packet Below the protocol layer, that is, the protocol layer that processes the data packet first can be considered as the lower protocol layer of the protocol layer that processes the data packet later.
  • the Adapt layer is the upper protocol layer of the RLC layer, the MAC layer, and the PHY layer, and the RLC layer, the MAC layer, and the PHY layer are the lower protocol layers of the Adapt layer.
  • the sending-side protocol stack can be considered as the lower-layer protocol stack of the receiving-side protocol stack.
  • the Adapt layer of the MT part that is, the sending side
  • the Adapt layer of the DU part that is, the receiving side
  • the Adapt layer of the MT part is the lower protocol layer of the IP layer of the DU part.
  • the Adapt layer of the MT part It is the lower protocol layer of the IP layer of the DU part.
  • RLC channel RLC channel
  • RLC bearer RLC bearer
  • logical channel logical channel, LCH for short
  • the RLC channel refers to the channel between the RLC layer and the upper protocol layer (for example, the Adapt layer).
  • the logical channel refers to the channel between the RLC layer and the lower protocol layer (for example, the MAC layer).
  • the logical channel may also be referred to as a MAC logical channel.
  • the RLC bearer refers to the RLC layer entity and the MAC logical channel.
  • the configuration of the radio bearer (RB for short) of the terminal corresponds to the configuration of the high-level (for example, PDCP layer) part and the low-layer (for example, RLC layer and MAC layer) part.
  • the configuration of the RLC bearer refers to the low layer corresponding to the RB Part of the configuration specifically includes the configuration of the RLC layer entity and the MAC logical channel.
  • the RLC bearer of the IAB node on the wireless backhaul link refers to the RLC layer and the MAC logical channel part.
  • the RLC channel on the wireless backhaul link can refer to the channel between the RLC layer and the PDCP layer, or Refers to the channel between the RLC layer and the Adapt layer, depending on the upper protocol layer of the RLC layer.
  • the RLC channel is the channel between the RLC layer and the Adapt layer as an example.
  • the RLC channel of the IAB node on the wireless backhaul link has a one-to-one correspondence with the RLC layer entity, and the RLC channel also has a one-to-one correspondence with the RLC bearer. For details, refer to FIG. 7 for understanding.
  • the RB of the terminal may be a data radio bearer (DRB for short), or a signaling radio bearer (SRB for short).
  • DRB data radio bearer
  • SRB signaling radio bearer
  • the RLC channel, RLC bearer, and logical channel are collectively referred to as service differentiated channels in the following.
  • the service differentiation channel in the following can be replaced with any one of the RLC channel, the RLC bearer, and the logical channel.
  • Service data unit service data unit, SDU for short
  • protocol data unit protocol data unit
  • the data units exchanged between peer-to-peer protocol layer entities between different nodes are PDUs.
  • a protocol layer transfers the PDU of the protocol layer to the lower protocol layer through the service access point (SAP) (also called service interface) provided to the protocol layer by the adjacent lower protocol layer, and
  • SAP service access point
  • the lower protocol layer indirectly completes the exchange of the PDU of the protocol layer, and the PDU of the protocol layer is used as the SDU of the lower protocol layer.
  • the data packet may be considered as the SDU of the protocol layer. If the data packet received by the protocol layer includes the protocol layer header of the protocol layer, the data packet can be regarded as the PDU of the protocol layer. For example, for the Adapt layer, if the data packet received by the Adapt layer does not include the Adapt layer header, the data packet can be considered as the SDU of the Adapt layer. If the data packet received by the Adapt layer includes the Adapt layer header, the data The packet can be regarded as the PDU of the Adapt layer.
  • the PDU of the Adapt layer can be divided into a control PDU (control PDU) of the Adapt layer and a data PDU (data PDU) of the Adapt layer.
  • the payload of the Adapt layer includes user plane data and/or control plane signaling.
  • the Adapt layer payload in the control PDU of the Adapt layer includes Adapt layer feedback information, for example, flow control feedback information, header compression feedback information, or other feedback information or control information generated by the Adapt layer.
  • the Adapt layer control PDU containing the header compression feedback information may be called a header compression status report.
  • the Adapt layer control PDU containing the flow control feedback information can be called a flow control status report.
  • the data packets of the Adapt layer can be of two types, which are respectively denoted as the first type data packet and the second type data packet.
  • the first type data packet refers to a data packet including an Adapt layer header and an Adapt layer payload.
  • the second type of data packet refers to a data packet including an Adapt layer payload.
  • the first type of data packet can also be called Adapt PDU.
  • the Adapt layer payload can be the control information or feedback information generated by the Adapt SDU or Adapt layer.
  • the Adapt layer header can contain routing information (also called Adapt layer routing related information), and/or RB related information of the terminal to which the data packet belongs, and can also contain Adapt PDU type indication information, which is used for Adapt PDU type indication information. It indicates whether the type of Adapt PDU is control PDU or data PDU.
  • the routing information may be: the identifier of the destination node of the Adapt layer route, or the identifier of the cell served by the destination node of the Adapt layer route, or the identifier of the Adapt layer transmission path.
  • the destination node of the Adapt layer route refers to the last node of the Adapt layer route.
  • the destination node of the Adapt layer routing can be the access IAB node.
  • the destination node of the Adapt layer routing can be Donor-DU.
  • each IAB node may be the destination node of the Adapt layer routing.
  • the RB-related information of the terminal to which the data packet belongs can be: the identity of the terminal + the identity of the RB of the terminal (for example, UE bearer specific ID), or it can be a "GTP" pointing to the RB of the terminal TEID+IP address".
  • GTP TEID refers to the tunnel endpoint identifier (tunnel endpoint identifier, TEID for short) of the GTP tunnel.
  • the Adapt layer has at least one of the following capabilities: adding routing information (Routing info) that can be recognized by the wireless backhaul node to the data packet, performing routing based on the routing information recognized by the wireless backhaul node, and Add identification information related to the quality of service (QoS) requirements that can be identified by the wireless backhaul node to the data packet, perform QoS mapping for the data packet on the multi-segment link including the wireless backhaul node, and perform the data
  • the packet adds data packet type indication information and sends flow control feedback information to nodes with flow control capabilities.
  • the name of the protocol layer with these capabilities is not necessarily the Adapt layer, and those skilled in the art can understand that any protocol layer with these capabilities can be understood as the Adapt layer in the embodiments of the application.
  • the routing information that can be recognized by the wireless backhaul node may be the identification of the terminal, the identification of the IAB node that the terminal accesses, the identification of the host node, the identification of Donor-DU, the identification of Donor-CU, the identification of the transmission path One or more of the information such as identification.
  • the QoS mapping on the multi-segment link may be: in the wireless backhaul link, based on the identification of the RB of the terminal carried in the data packet, execute the RLC bearer or RLC channel or logic from the RB of the terminal to the wireless backhaul link.
  • Channel mapping based on the correspondence between any two or more of the RB, RLC bearer, RLC channel and logical channel of the ingress link and egress link, perform the RB or RLC bearer or RLC from the ingress link Channel or logical channel, RB or RLC bearer or RLC channel or logical channel mapping to the egress link.
  • the data packet type indication information may be used to indicate that the content encapsulated in the Adapt layer contains any one or more of the following types: user plane data of the terminal, RRC message of the terminal, RRC message of the IAB node, IAB node Control layer application messages (such as F1AP messages) on the interface with the host node (or Donor-CU or CU-CP), flow control feedback messages generated by IAB nodes, header compression feedback messages generated by IAB nodes, and Adapt layer data PDU, Adapt layer control PDU, etc.
  • IAB node Control layer application messages such as F1AP messages
  • the identification information related to the QoS requirements may be the QoS flow identifier (QFI) of the terminal, the RB identifier of the terminal, the differentiated services code point (DSCP), and the Internet Protocol version 6 (internet Protocol version 6, referred to as IPv6), the flow label in the header of the IP data packet, etc.
  • QFI QoS flow identifier
  • DSCP differentiated services code point
  • IPv6 Internet Protocol version 6
  • a node with flow control capability may be a host node, Donor-DU, Donor-CU, parent node of an IAB node, etc., nodes that provide backhaul services for the IAB node.
  • the content of the flow control feedback information can include one or more of the following information: the cache status and load level of the IAB node, and the status of a certain link of the IAB node (such as link blockage or link recovery ( resume) or link quality information, etc.), including the bandwidth and transmission delay of a certain link of the IAB node, the data packet sequence number lost by the IAB node, and the data packet sequence number that the IAB node has successfully sent to the terminal or its child nodes.
  • the function of the Adapt layer can also be extended by the functions of any layer (for example, RLC layer, MAC layer, PDCP layer, etc.) or any number of layers included in layer 2, without additional protocol Floor.
  • any layer for example, RLC layer, MAC layer, PDCP layer, etc.
  • any number of layers included in layer 2 without additional protocol Floor.
  • one Adapt layer may include multiple Adapt layer entities, and one RLC layer may also include multiple RLC layer entities.
  • the number of Adapt layer entities included in the Adapt layer can be any of the following cases 1 to 3:
  • the Adapt layer contains an Adapt layer entity.
  • the Adapt layer entity corresponds to N (N is an integer greater than 0) RLC layer entities, there are N RLC channels between the Adapt layer entity and the N RLC layer entities, and the N RLC channels correspond to N Each RLC layer entity has a one-to-one correspondence.
  • the intermediate IAB node if the MT part and the DU part of the intermediate IAB node share the Adapt layer, see Figure 8.
  • Some of the N RLC layer entities are the RLC layer entities included in the RLC layer of the MT part of the intermediate IAB node.
  • the other part of the RLC layer entities are RLC layer entities included in the RLC layer of the DU part of the intermediate IAB node.
  • the Adapt layer of a node (denoted as node A, for example, node A can be an IAB node, a host node, or Donor-DU) contains M (M is an integer greater than 0) Adapt layer entities and M Adapt The layer entity has a one-to-one correspondence with M nodes, and the M nodes are one or more nodes that communicate with node A.
  • the node communicating with the network node is the node where the receiving side corresponding to the sending side of the network node is located.
  • one Adapt layer entity corresponds to one node.
  • the correspondence between an Adapt layer entity and an RLC layer entity can be seen in Figure 7.
  • the Adapt layer includes N Adapt layer entities, and the N Adapt layer entities have a one-to-one correspondence with the N RLC layer entities.
  • an RLC channel between an Adapt layer entity and a corresponding RLC layer entity.
  • one RLC channel or one logical channel or one RLC bearer corresponds to one Adapt layer entity.
  • the route selection in the embodiment of the present application is used to select the next hop node for the data packet.
  • the bearer mapping in the embodiment of the present application may also be referred to as QoS mapping.
  • the bearer mapping is used to select the RLC bearer or RLC channel or logical channel for sending data packets.
  • the downlink data packet sent to the terminal will pass through the GTP-U layer, UDP layer, and UDP layer of Donor-CU.
  • the IP data packet is obtained, which is transmitted through the wired link between Donor-CU and Donor-DU, and then sent by the Donor-DU on the wireless backhaul link to the IAB node (ie IAB node 2).
  • the IAB node 2 At the IAB node 2, the IP header, UDP header, and GTP-U header in the data packet will be stripped off, and then the IAB node 2 will send the PDCP PDU of the terminal to the terminal through the wireless access link.
  • the network node in the embodiment of the present application may perform header compression and de-header compression on the data packet of the terminal. Through header compression and de-header compression, the header overhead of data packets in the wireless backhaul link transmission process can be reduced, and the air interface resource consumption can be reduced.
  • Header compression refers to compressing the protocol layer header of a data packet (for example, an IP data packet). Decompressing the header refers to decompressing the compressed protocol layer header.
  • the header compressed during header compression may be one or more of an Adapt layer header, an IP layer header, a UDP layer header, an SCTP layer header, and a GTP-U layer header.
  • header compression methods there may be two header compression methods, namely end-to-end header compression and hop-by-hop header compression.
  • the two header compression methods are respectively introduced below.
  • End-to-end header compression a header compression method that only performs header compression on the sending side of the access IAB node or the sending side of the host node (or Donor-DU).
  • the decompressed node is the receiving side of the host node (or Donor-DU).
  • the decompressed node is the receiving side of the access IAB node.
  • Hop-by-hop header compression A header compression method in which the host node (or Donor-DU) and the sending side of each IAB node perform header compression. When header compression is performed on the sending side of a node, the decompressed node is the receiving side of the next hop node of the node.
  • the network node serving as the receiving node of the wireless backhaul link is to access the IAB node, the host node or the Donor-DU, and perform the header compression operation. If the header compression method is hop-by-hop header compression, each network node as the receiving node of the wireless backhaul link performs the header compression operation.
  • Figure 10 shows the format of a status report with header compression, where the meaning of each field is:
  • Data/control (data/control, D/C for short): This field is used to identify the PDU type of the Adapt PDU (that is, the header compressed status report), whether it is a data PDU or a control PDU. For example, this field may have 1 bit, a value of 0 for this bit indicates that the Adapt PDU is a control PDU, and a value of 1 for this bit indicates that the Adapt PDU is a data PDU.
  • Control information type is used to indicate the type of status report.
  • the type of status report can be header compression status report, flow control status report, etc.
  • this field may further include header compression mode indication information, which is used to indicate the header compression mode corresponding to the header compression status report.
  • the control information type includes at least two bits, one bit is used to indicate the control information type, and the other bit is used to indicate the header compression mode.
  • the bits included in the control information type include at least three values, one value indicates that the status report is a flow control status report, and the other value indicates that the status report is a header compression method that is header-by-hop header compression.
  • the status report of header compression Another value indicates that the status report is the status report of header compression with end-to-end header compression.
  • This field is used to indicate the routing information of the Adapt PDU.
  • the routing information may include the identifier of the destination node that receives the Adapt PDU, and may also include the identifier of the source node that sends the Adapt PDU.
  • this field is an optional field. For example, in the hop-by-hop header compression mode, the Adapt control PDU carrying header compression feedback information may not need this field.
  • This field is the identifier of a certain RB pointing to a certain terminal, and is used to indicate the RB of the terminal corresponding to the Adapt PDU.
  • This field is an optional field. For example, when the header compression configuration of the Adapt layer is specific to an IAB node instead of the terminal RB, the Adapt control PDU carrying header compression feedback information may not need this field.
  • Reserved (reserved) field This field is a reserved bit, which can be used for byte alignment of Adapt layer header information.
  • Header compression feedback information the content of this field is the specific header compression feedback content (for example, robust header compression (ROHC) feedback).
  • ROI robust header compression
  • Embodiment 1 In order to ensure that data packets are correctly transmitted on the wireless backhaul link, the embodiments of this application provide the communication methods shown in Embodiment 1, Embodiment 2 and Embodiment 3. The following describes Embodiment 1, Embodiment 2 and The third embodiment is described.
  • the network node may be an IAB node or a host node or a Donor-DU.
  • the embodiment of the present application provides a communication method. As shown in FIG. 11, the method includes:
  • a first entity of a network node receives a data packet submitted from a protocol layer entity of a lower protocol layer, and the first entity is an Adapt layer entity.
  • the data packet is a first type data packet
  • the first type data packet is a data packet including an Adapt layer header and an Adapt layer payload.
  • the data packet received by the first entity of the network node is an Adapt PDU.
  • the first entity of the network node is located on the receiving side.
  • the Adapt layer on the receiving side of the network node may include one or more Adapt layer entities, and the first entity of the network node may be any Adapt layer entity among them. More specifically, if the network node is an intermediate IAB node that shares an Adapt layer, the first entity is an Adapt layer entity shared by the sending side and the receiving side of the intermediate IAB node.
  • the lower protocol layer of the Adapt layer may be the RLC layer
  • the protocol layer entity of the lower protocol layer may be the RLC layer entity
  • the first entity of the network node judges whether the network node is the destination node of the data packet routing at the Adapt layer.
  • the first entity of the network node processes the data packet according to the judgment result.
  • the network node processes the data packet according to the judgment result of whether it is the destination node of the data packet routing at the Adapt layer, which can correctly process the data packet and prevent errors in the processing of the data packet.
  • step 1102 includes: the first entity of the network node according to the routing information in the Adapt layer header in the data packet, whether the Adapt layer header in the data packet contains routing information, and whether the data packet is a control PDU One or more of these determine whether the network node is the destination node of the data packet routing at the Adapt layer.
  • step 1102 may be implemented in any one of the following manners 1 to 3.
  • Manner 1 The first entity of the network node judges whether the network node is the destination node of the data packet routing at the Adapt layer according to the routing information in the Adapt layer header in the data packet.
  • the routing information is the identification of the destination node of the Adapt layer routing.
  • the identifier of the destination node carried in the Adapt layer header of the data packet is the identifier of the network node
  • the first entity of the network node can determine that it is the destination node of the Adapt layer routing. Otherwise, the first entity of the network node may determine that it is not the destination node of the Adapt layer routing.
  • the routing information is the identity of the cell served by the destination node of the Adapt layer routing.
  • the identity of the cell carried in the Adapt layer header of the data packet is the identity of the cell served by the network node
  • the first entity of the network node can determine that it is the destination node of the Adapt layer routing. Otherwise, the first entity of the network node may determine that it is not the destination node of the Adapt layer routing.
  • the routing information is the transmission path identifier of the Adapt layer routing.
  • the first entity of the network node can determine that it is the destination node of the Adapt layer route. Otherwise, the first entity of the network node may determine that it is not the destination node of the Adapt layer routing.
  • the routing information is the identification of the terminal.
  • the first entity of the network node can determine that it is the destination node of the Adapt layer routing. Otherwise, the first entity of the network node may determine that it is not the destination node of the Adapt layer routing.
  • Manner 2 The first entity of the network node judges whether the network node is the destination node of the data packet routing at the Adapt layer according to whether the Adapt layer header in the data packet contains routing information.
  • the last hop node of the destination node of the Adapt layer route will remove the routing information in the Adapt layer header.
  • the first entity of the network node receives the Adapt PDU submitted by the protocol layer entity of the lower protocol layer, if the Adapt layer header of the Adapt PDU does not include the routing information field, the first entity of the network node determines that it is The destination node of Adapt PDU routing at the Adapt layer, otherwise, the first entity of the network node judges that it is not the destination node of Adapt PDU routing at the Adapt layer.
  • the Adapt layer header of the upstream Adapt PDU may not carry routing information, and each IAB node is unique
  • the parent node can forward the upstream Adapt PDU, that is, a default routing method is adopted.
  • the network node is an IAB node
  • the Adapt layer of the network node receives the uplink Adapt PDU submitted by the protocol layer entity of the lower protocol layer
  • if the Adapt layer header of the uplink Adapt PDU does not include the routing information field It is judged that it is not the destination node of the Adapt layer routing.
  • the network node is the host node or Donor-DU
  • the Adapt layer of the network node receives the uplink Adapt PDU submitted by the protocol layer entity of the lower protocol layer
  • the Adapt layer header of the uplink Adapt PDU does not include the routing information field, it will judge itself It is the destination node of Adapt layer routing.
  • Manner 3 The first entity of the network node judges whether the network node is the destination node of the data packet routing at the Adapt layer according to whether the data packet is a control PDU.
  • the IAB network supports hop-by-hop adaptation layer status reports (for example, downstream flow control status reports, header compression status reports, etc.) feedback scenarios.
  • each IAB that receives the Adapt layer status report The nodes are the destination nodes of the Adapt layer status report. Since the Adapt layer status report is a control PDU, this type of control PDU may not carry routing information.
  • the first entity of the network node can also determine whether the network node is the destination node of the Adapt PDU routing at the Adapt layer according to the PDU type of the Adapt PDU. When the Adapt PDU is a control PDU, the first entity of the network node determines that it is the destination node of the Adapt PDU routing at the Adapt layer. Otherwise, the first entity of the network node then judges whether it is the destination node of the Adapt layer routing according to the aforementioned method 1 or method 2.
  • the Adapt layer header of the Adapt PDU may include a PDU type indication identifier, which is used to indicate whether the Adapt PDU type is a data PDU or a control PDU.
  • the first entity of the network node may determine whether the Adapt PDU is a control PDU according to the identifier.
  • step 1102 there are two judgment results in step 1102, one judgment result is yes (that is, the network node is the destination node of the data packet routing in the Adapt layer), and the other judgment result is no (that is, the network node is not the data packet in the Adapt layer. The destination node of the route).
  • the implementation of step 1103 is also different, which will be introduced separately below.
  • step 1103 can be implemented in any of the following implementation manners 1 to 4.
  • the specific implementation method can be determined according to the applicable scenarios of the implementation method.
  • Implementation mode 1 The first entity of the network node submits the Adapt layer payload in the data packet to the second entity, and the second entity is the protocol layer entity of the protocol layer of the F1 interface or the protocol layer entity of the upper protocol layer of the Adapt layer.
  • the applicable scenario of the implementation method 1 header compression is not performed on the data packet in the IAB network.
  • the first entity of the network node may remove the Adapt layer header of the received data packet to obtain the Adapt layer payload, and then submit the Adapt layer payload to the second entity.
  • Implementation mode 2 The first entity of the network node decompresses the Adapt layer payload in the data packet, and delivers the decompressed Adapt layer payload to the second entity.
  • the first entity of the network node can remove the Adapt layer header of the received data packet to obtain the Adapt layer load, decompress the Adapt layer load, and then compress the header after decompression.
  • the layer load is delivered to the second entity.
  • Implementation mode 3 The first entity of the network node de-compresses the data packet, and delivers the Adapt layer payload in the de-header-compressed data packet to the second entity.
  • header compression is performed on the data packet in the IAB network, and the compressed protocol layer header includes the Adapt layer header.
  • the first entity of the network node can decompress the received data packet, and then remove the Adapt layer header of the decompressed data packet to obtain the Adapt layer load, and the Adapt layer load Submit to the second entity.
  • the network node may be an access IAB node or a host node or a Donor-DU.
  • the second entity may be a protocol layer entity of the IP layer.
  • the data packet is a data PDU.
  • Implementation manner 4 The first entity of the network node stores the data packet in the buffer of the Adapt layer.
  • Applicable scenarios for implementation mode 4 any scenario.
  • the data packet is a data PDU or a control PDU.
  • the network node may also perform actions in any one of implementation manners 1 to 3. At this time, the network node may be an access IAB node or a host node or a Donor-DU.
  • the first entity of the network node stores the data packet in the buffer of the Adapt layer, and then processes the Adapt layer load in the data packet by itself.
  • the network node may be an intermediate IAB node.
  • the data packet is a data PDU or a control PDU.
  • the network node is an intermediate IAB node.
  • step 1103 may be implemented in any of the following implementation manners 5 to 10. The specific implementation method can be determined according to the applicable scenarios of the implementation method.
  • Implementation mode 5 The first entity of the network node delivers the data packet to the third entity, which is a protocol layer entity of the protocol layer of the wireless backhaul interface or a protocol layer entity of the lower protocol layer of the Adapt layer.
  • the third entity is located on the sending side of the network node. If the network node is an intermediate IAB node sharing the Adapt layer, the third entity is the lower protocol layer of the Adapt layer entity on the sending side of the network node (for example, an RLC layer entity), if the network node is an intermediate IAB node that does not share the Adapt layer , The third entity is the Adapt layer entity on the sending side of the network node.
  • the first entity of the network node submits the Adapt layer payload in the data packet and the information in the Adapt layer header in the data packet to the third entity, which is the protocol layer entity of the protocol layer of the wireless backhaul interface Or the protocol layer entity of the lower protocol layer of the Adapt layer.
  • the first entity of the network node can remove the Adapt layer header of the received data packet to obtain the Adapt layer payload, and then transfer the Adapt layer payload and the information in the Adapt layer header in the data packet to Submitted by a third entity.
  • the first entity of the network node decompresses the Adapt layer payload in the data packet, and submits the decompressed Adapt layer payload and the information in the Adapt layer header in the data packet to the third entity.
  • the third entity is a protocol layer entity of the protocol layer of the wireless backhaul interface or a protocol layer entity of the lower protocol layer of the Adapt layer.
  • the header compression method is hop-by-hop header compression, and the previous hop node of the network node performs header compression on the Adapt layer payload in the data packet.
  • the first entity of the network node can remove the Adapt layer header of the received data packet to obtain the Adapt layer load, decompress the Adapt layer load, and then decompress the header after decompression.
  • the layer payload and the information in the Adapt layer header in the data packet are submitted to the third entity.
  • the first entity of the network node decompresses the data packet, and transfers the Adapt layer payload in the decompressed data packet and the information in the Adapt layer header in the decompressed data packet to the third
  • the third entity is the protocol layer entity of the protocol layer of the wireless backhaul interface or the protocol layer entity of the lower protocol layer of the Adapt layer.
  • the header compression method is hop-by-hop header compression
  • the previous hop node of the network node performs header compression on the data packet
  • the compressed protocol layer header includes the Adapt layer header
  • the first entity of the network node can de-compress the received data packet, and then remove the Adapt layer header in the de-header-compressed data packet to obtain the Adapt layer payload.
  • the layer payload and the information in the Adapt layer header in the data packet are submitted to the third entity.
  • the third entity is located on the sending side of the network node.
  • the network node is an intermediate IAB node that does not share the Adapt layer, and the third entity is an Adapt layer entity on the sending side of the network node.
  • the information in the Adapt layer header submitted by the first entity of the network node to the third entity may be all the information in the Adapt layer header or part of the information in the Adapt layer header.
  • the information included in the Adapt layer header can be referred to above, and will not be repeated here.
  • Implementation mode 9 The first entity of the network node first decompresses the data packet header (the de header compression algorithm used corresponds to the header compression algorithm used by the previous hop node), and then performs header compression on the data packet (using the The header compression algorithm corresponds to the header decompression algorithm adopted by the next hop node), and then the header compressed data packet is delivered to the third entity.
  • the de header compression algorithm used corresponds to the header compression algorithm used by the previous hop node
  • the header compression algorithm corresponds to the header decompression algorithm adopted by the next hop node
  • the header compression method is hop-by-hop header compression
  • the previous hop node of the network node performs header compression on the data packet
  • the compressed protocol layer header includes the Adapt layer header
  • the first entity of the network node first decompresses the Adapt layer load in the data packet (the de header compression algorithm used corresponds to the header compression algorithm used by the previous hop node), and then loads the Adapt layer Perform header compression (the used header compression algorithm corresponds to the decompression algorithm used by the next hop node), and then add an Adapt layer header to the header-compressed Adapt layer payload and submit it to the third entity.
  • the de header compression algorithm used corresponds to the header compression algorithm used by the previous hop node
  • the Adapt layer Perform header compression the used header compression algorithm corresponds to the decompression algorithm used by the next hop node
  • the header compression method is hop-by-hop header compression, and the previous hop node of the network node performs header compression on the Adapt layer payload in the data packet.
  • the third entity is located on the sending side of the network node.
  • the network node is an intermediate IAB node sharing the Adapt layer
  • the third entity is an RLC layer entity on the sending side of the network node.
  • the compression algorithm adopted between the network node and the previous hop node of the data packet and the compression algorithm adopted between the network node and the next hop node of the data packet may be the same or different.
  • the first entity of the network node can perform different processing on the data packet and submit it to the corresponding protocol layer to ensure the transmission of the uplink service and the downlink service in the IAB network.
  • the Adapt layer header of the data packet includes a header compression mode indication field, and the header compression mode indication field is used to indicate the header compression mode adopted by the previous hop node of the data packet.
  • the first entity of the network node may determine whether to decompress the header of the data packet according to the header compression mode indication field.
  • the header compression method is end-to-end header compression
  • the network node when the network node is an access IAB node or a host node or a Donor-DU, the network node decompresses the header of the data packet.
  • the header compression method is hop-by-hop header compression, no matter what kind of node the network node is, the data packet will be decompressed.
  • the header compression mode indication field corresponds to the terminal (or the RB of the terminal), that is, the indication field is only used to configure the data packet corresponding to a certain terminal (or a certain RB of a certain terminal) on the wireless backhaul link
  • the header compression method the network node may decompress the data packet only when the data packet is a data packet of the certain terminal (or a certain RB of a certain terminal).
  • the specific decompression depends on the network node Type and method of header compression.
  • the access IAB node, the host node (or Donor-DU), and the intermediate IAB node can be considered as different types of network nodes.
  • the header compression mode indication field corresponds to a certain IAB node, that is, the indication field is used to configure the header compression mode of the data packet sent to the certain IAB node.
  • the network node may decompress the data packet only when the data packet is sent to the certain IAB node. Whether to decompress the header or not depends on the type of the network node and the method of header compression.
  • the header compression mode indication field can have two values. For example, 0 and 1, where 0 means no header compression is used, 1 means header compression is used; or, 0 means end-to-end header compression, and 1 means hop-by-hop header compression.
  • the header compression mode indication field can also have at least three values. For example, 00, 01, 11, where 00 means no header compression is used, 01 means end-to-end header compression is used, and 11 means hop-by-hop header compression is used.
  • the above method may further include: 11) the first entity of the network node sends the network node to the network The last hop node of the node sends a header compression status report.
  • the status report of header compression is used for status feedback of header compression
  • the status report of header compression is a control PDU of the Adapt layer.
  • One format of the header compression status report can be seen in Figure 10, and it can also be in other formats.
  • the decompression end can send ROHC feedback (feedback) to ensure that the context status of the header compression end and the decompression end are synchronized.
  • ROHC feedback is the payload in the header compression status report. The specific information that needs to be included in the header compression status report can be found in the ROHC protocol.
  • the method provided in Embodiment 1 further includes: 21) The first entity of the network node judges the PDU type of the data packet, and the PDU type of the data packet is a data PDU or a control PDU.
  • the first entity of the network node may not perform steps 1102 and 1103, but directly store the data packet in the buffer of the Adapt layer, and process the data packet by itself. Adapt layer load.
  • the first entity of the network node may determine the PDU type of the data packet according to the PDU type indication information carried in the Adapt layer header of the data packet.
  • the PDU type indication information may be carried in the D/C field in the Adapt layer header of the data packet.
  • the intermediate IAB node needs to perform routing selection in order to determine the next hop node of the data packet, and also needs to perform bearer mapping to determine the service differentiation channel used when sending the data packet .
  • the above method further includes any one or more of the following methods 1 to 3.
  • Method 1 The first entity of the network node determines the next hop node of the data packet, and the first entity of the network node submits information for indicating the next hop node to the third entity.
  • the information used to indicate the next hop node may be the identifier of the next hop node.
  • the first entity of the network node can determine the next hop node of the data packet through routing.
  • the first entity of the network node can select an appropriate next hop node according to the routing information in the Adapt layer header in the data packet and the preset routing rules.
  • the routing rule can be pre-configured in the network node by the host node or Donor-CU, or can be generated by the network node itself.
  • the routing information in the Adapt layer header may be the identification of the destination node of the Adapt layer routing
  • the preset routing rule may be a forwarding table configured in the network node, and the forwarding table at least contains the identification of the destination node, and The identifier of the next hop node corresponding to the identifier of the target node.
  • the process of routing selection by the first entity of the network node may include: according to the identifier of the destination node carried in the Adapt layer header, corresponding the identifier of the next hop node corresponding to the identifier of the destination node in the forwarding table The node is determined as the next hop node of the data packet.
  • the identifier of one destination node may correspond to the identifiers of multiple next-hop nodes.
  • there may be further selection rules in the forwarding table for example, different next hop nodes may correspond to different bearers of the terminal), so that the network node can use more additional information (for example, the Adapt layer).
  • the identifier of the bearer of the terminal in the header selects the next hop node of the data packet from the identifiers of the multiple next hop nodes corresponding to the identifier of the destination node.
  • routing selection In addition to the implementation of routing selection shown in the examples of this application, there may also be other implementations of routing selection, which are not limited in this application.
  • the first entity of the network node submits the identification of the first service differentiation channel to the third entity, the first service differentiation channel is the service differentiation channel from which the data packet received by the first entity comes, and the service differentiation channel is the logical channel Or RLC channel or RLC bearer.
  • the identifier of the first service differentiation channel may be used by the third entity to determine the next hop node and/or the second service differentiation channel, and the second service differentiation channel is a service differentiation channel for the third entity to send data packets.
  • Method 3 The first entity of the network node determines the second service differentiated channel for delivering the data packet to the next hop node of the data packet; the first entity of the network node submits the identifier of the second service differentiated channel to the third entity.
  • the first entity of the network node may determine the second service differentiation channel through bearer mapping.
  • the method for the first entity of the network node to perform bearer mapping is similar to the method 1 to the method 3 in the second embodiment, which can be understood with reference to the second embodiment, and will not be repeated here.
  • routing and bearer mapping are performed by the Adapt layer entity (ie, the first entity) shared by the sending side and the receiving side of the intermediate IAB node.
  • the method for the Adapt layer entity to perform route selection can be referred to the relevant description of the above method 1.
  • the method for the Adapt layer entity to perform bearer mapping is similar to the method one to the method three in the second embodiment, and can be understood with reference to the second embodiment. Repeat it again.
  • the intermediate IAB node does not share the Adapt layer.
  • Table 1 Whether the transmitting side and the receiving side in the intermediate IAB node perform routing and bearer mapping depends on the specific implementation. For example, there can be three types shown in Table 1. Example.
  • Example 1 the applicable scenario of Example 1 is: the sending side of the network node has only one Adapt layer entity (that is, the above case 1).
  • Example 2 The applicable scenario of Example 2 is: the sending side of the network node has only one Adapt layer entity (that is, the above case 1); or the sending side of the network node includes multiple Adapt layer entities, and each Adapt layer entity communicates with the network node One of the nodes (that is, case 2 above).
  • Example 3 The applicable scenario of Example 3 is: the sending side of the network node has only one Adapt layer entity (that is, the above case 1); or, the sending side of the network node includes multiple Adapt layer entities, and each Adapt layer entity corresponds to the network node communication Or, the sending side of the network node includes multiple Adapt layer entities, and one Adapt layer entity corresponds to one RLC layer entity (that is, case 3 above).
  • Example 1 Example 2 or Example 3 may also be other scenarios, which are not limited.
  • the network node is an intermediate IAB node, and the DU part and the MT part of the intermediate IAB node do not share the Adapt layer.
  • the second embodiment provides a communication method, as shown in FIG. 13, including:
  • a third entity of a network node receives a data packet from a first entity, and both the first entity and the third entity are Adapt layer entities.
  • the first entity of the network node is located on the receiving side of the network node, and the third entity of the network node is located on the transmitting side of the network node.
  • the data packet may be a data packet submitted by the first entity of the network node to the third entity in Embodiment 1.
  • the data packet may be a first type data packet or a second type data packet.
  • the first type of data packet refers to a data packet including an Adapt layer header and an Adapt layer payload.
  • the second type of data packet refers to a data packet including an Adapt layer payload.
  • the third entity of the network node delivers the data packet to the fourth entity through the second service differentiation channel.
  • the fourth entity is a protocol layer entity of the lower protocol layer of the Adapt layer, for example, an RLC layer entity.
  • the second service differentiation channel corresponds to the next hop node of the data packet (that is, the second service differentiation channel is one of the multiple service differentiation channels leading to the next hop node of the data packet), and the service differentiation channel is logical Channel or RLC channel or RLC bearer.
  • the third entity of the network node delivers the data packet to the fourth entity through the second service differentiated channel corresponding to the next hop node of the data packet, which can ensure that the data packet is correctly transmitted to the downstream of the data packet.
  • One-hop node One-hop node.
  • the method further includes: 11) a third entity of the network node adds an Adapt layer header to the data packet.
  • step 1302 includes: the third entity of the network node delivers the data packet with the Adapt layer header added to the fourth entity through the second service differentiated channel.
  • the information required by the third entity to add the Adapt layer header may be sent by the first entity to the third entity together with the Adapt layer payload.
  • the above method further includes: the third entity of the network node receives the information in the Adapt layer from the first entity.
  • the third entity of the network node may add an Adapt layer header to the data packet.
  • the data packet is the first type of data packet (ie, Adapt PDU)
  • the Adapt PDU since the Adapt PDU has an Adapt layer header, the third entity of the network node may not add an Adapt layer header to the data packet.
  • the method further includes one or more of the following: 21) the third entity of the network node determines the next hop node for the data packet; or, 31) the third entity of the network node determines the second service distinction for the data packet aisle.
  • the third entity of the network node may determine the next hop node of the data packet through routing.
  • the third entity of the network node may determine the second service differentiation channel through bearer mapping. Whether the third entity of the network node performs routing and bearer mapping is related to the actions performed by the first entity. See Table 1 for details. I won't repeat them here. Exemplarily, referring to (a) and (b) in FIG. 14, FIG. 14 shows two possible processes for the third entity to process a data packet.
  • Step 21) can be implemented by way 1 or way 2 below.
  • Manner 2 The third entity of the network node receives information for indicating the next hop node from the first entity, and the third entity of the network node determines the next hop node according to the information for indicating the next hop node.
  • the information used to indicate the next hop node may be the identifier of the next hop node.
  • Step 31) can be implemented in any one of the following modes 1 to 4.
  • Manner 1 The third entity of the network node determines the second service differentiation channel according to the first service differentiation channel.
  • the third entity of the network node may determine the second service differentiation channel according to the correspondence between the service differentiation channel of the ingress link and the service differentiation channel of the egress link.
  • a service differentiation channel of an ingress link may correspond to one or more service differentiation channels of an egress link.
  • the method further includes: the third entity of the network node receives the identifier of the first service differentiation channel from the first entity.
  • the third entity of the network node may determine the first service differentiated channel according to the identifier of the first service differentiated channel.
  • the third entity of the network node may determine that the service differentiated channel corresponding to the first service differentiated channel is the second service differentiated channel. In this case, there can be a one-to-one correspondence between the service differentiation channel of the ingress link and the service differentiation channel of the egress link. The third entity of the network node may determine the second service differentiation channel according to the corresponding relationship and the identification of the first service differentiation channel.
  • the service differentiation channel corresponding to the first service differentiation channel is configured through the network or the host node or Donor-CU or CU-CP.
  • the service differentiation channel of one ingress link corresponds to the service differentiation channels of multiple egress links.
  • the service differentiation channel of the egress link may correspond to the next hop node of the data packet one-to-one.
  • the third entity of the network node may determine the second service differentiation channel according to the first service differentiation channel and the next hop node of the data packet.
  • the correspondence between the service differentiation channel of the ingress link and the service differentiation channel of the egress link, the service differentiation channel of the egress link and the next hop node of the data packet can be found in Table 2.
  • the first network node The three entities may determine the second service differentiation channel according to the identification of the first service differentiation channel and the corresponding relationship.
  • the third entity of the network node determines the second service differentiation channel according to one or more of the identification of the RB of the terminal to which the data packet belongs, or the correspondence between the RB of the terminal and the service differentiation channel.
  • the Adapt layer header of the data packet may include the identification of the RB of the terminal to which the data packet belongs, and the third entity may determine that the corresponding service differentiation channel is the next one according to the identification of the RB included in the Adapt layer header.
  • the service differentiated channel for the hop node to send the data packet (that is, the second service differentiated channel).
  • the identification of the RB of the terminal corresponds to multiple service differentiation channels
  • the third entity of the network node selects the service differentiation channel corresponding to the next hop node of the data packet as the second service differentiation channel.
  • the corresponding relationship between the RB of the terminal and the service differentiated channel may be that the host node or Donor-CU or CU-CP is pre-configured in the network node, or it may be generated by the network node itself.
  • Manner 3 The third entity of the network node determines the second service differentiation channel according to the QoS label carried in the data packet and the corresponding relationship between the QoS label and the service differentiation channel.
  • the QoS label carried in the data packet corresponds to multiple service differentiated channels
  • the third entity of the network node selects the service differentiated channel corresponding to the next hop node of the data packet as the second service differentiated channel.
  • the corresponding relationship between the QoS label and the service differentiation channel may be that the host node or Donor-CU or CU-CP is pre-configured in the network node, or may be generated by the network node itself.
  • the QoS label is used to indicate the QoS requirements of the data packet.
  • the QoS label can specifically be a differentiated services code point (DSCP), a flow label in an IPv6 data packet, or a QoS requirement for a service corresponding to the data packet. QoS ID, etc.
  • Manner 4 The third entity of the network node receives the identifier of the second service differentiated channel from the first entity, and the third entity of the network node determines the second service differentiated channel according to the identifier of the second service differentiated channel.
  • the method further includes: network The third entity of the node performs header compression on the data packet. Or, after the third entity of the network node adds the Adapt layer header to the data packet, the third entity of the network node performs header compression on the data packet after adding the Adapt layer header.
  • the third entity of the network node passes the second The service differentiated channel submits the data packet with the Adapt layer header added to the fourth entity, including: the third entity of the network node will add the Adapt layer header through the second service differentiated channel and submit the data packet compressed by the header to the fourth entity .
  • the network node can perform header compression through a configured header compression algorithm.
  • the sending side may use ROHC to perform header compression.
  • the sending side of a node performs header compression and the header compression method adopted can be configured by the host node or Donor-CU or CU-CP.
  • the Donor-CU may carry the indication information for configuring the header compression mode and/or the header compression compression algorithm in the configuration information sent to the network node.
  • the header compression mode indication field sent by the Donor-CU to the network node can be carried in the F1AP message sent by the Donor-CU to the network node, or, when the protocol layer supported by the network node includes the RRC layer, it can be carried in the Donor-CU In the RRC message to the network node (for example, the network node is an intermediate IAB node, the MT part of the intermediate IAB node supports the RRC protocol layer, and the Donor-CU sends the RRC message to the MT part of the intermediate IAB node).
  • the Adapt layer header added by the third entity of the network node includes a header compression mode indication field, and the header compression mode indication field is used to indicate the header compression mode adopted by the third entity of the network node.
  • the next hop node of the data packet determines whether to decompress the data packet according to the instruction information.
  • header compression mode indication field please refer to the content of the relevant part of the first embodiment, which will not be repeated here.
  • the network node is an access IAB node, and the data packet is an uplink data packet; or, the network node is a host node or Donor-DU, and the data packet is a downlink data packet.
  • the third embodiment provides a communication method, as shown in FIG. 15, including:
  • a first entity of a network node receives a data packet from a fifth entity.
  • the fifth entity is a protocol layer entity of the protocol layer of the F1 interface or a protocol layer entity of the upper protocol layer of the Adapt layer.
  • the first entity is an Adapt layer entity.
  • the packet is a second type data packet, and the second type data packet is a data packet including an Adapt layer payload.
  • the first entity of the network node is located on the sending side of the network node.
  • the fifth entity may be a protocol layer entity of the IP layer.
  • the first entity of the network node adds an Adapt layer header to the data packet.
  • the first entity of the network node adds the information required by the Adapt layer header, which may be sent to the first entity by the fifth entity together with the data packet.
  • the first entity of the network node delivers the data packet with the Adapt layer header added to the sixth entity through the third service differentiation channel.
  • the sixth entity is the protocol layer entity of the lower protocol layer of the Adapt layer.
  • the third service differentiation channel is The next hop node of the data packet corresponds (that is, the third service differentiation channel is one of the multiple service differentiation channels leading to the next hop node of the data packet), and the service differentiation channel is a logical channel or an RLC channel or RLC Bearer.
  • the sixth entity may be an RLC layer entity.
  • the first entity of the network node delivers the data packet to the sixth entity through the third service differentiated channel corresponding to the next hop node of the data packet, which can ensure that the data packet is correctly transmitted to the downstream of the data packet.
  • One-hop node One-hop node.
  • the method further includes one or more of the following: 11) the first entity of the network node determines the next hop node of the data packet; or, 21) the first entity of the network node determines the third service differentiation channel.
  • Step 11) the first entity of the network node can determine the next hop node of the data packet through routing.
  • Step 21) the first entity of the network node may determine the third service differentiation channel through the bearer mapping.
  • routing and bearer mapping can be performed in the fifth entity.
  • step 11) can be implemented by a method similar to the method 1 in the second embodiment (not described here), or the identifier of the next hop node can be received from the fifth entity, and the next hop node can be determined according to the identity of the next hop node.
  • One-hop node can be implemented by a method similar to the method 1 in the second embodiment (not described here), or the identifier of the next hop node can be received from the fifth entity, and the next hop node can be determined according to the identity of the next hop node.
  • One-hop node can be implemented by a method similar to the method 1 in the second embodiment (not described here), or the identifier of the next hop node can be received from the fifth entity, and the next hop node can be determined according to the identity of the next hop node.
  • One-hop node can be implemented by a method similar to the method 1 in the second embodiment (not described here), or the identifier of the next hop node can be received from the fifth entity, and the next hop node can be determined according
  • Step 21) can be implemented by a method similar to mode 2 or mode 3 in the second embodiment (not repeat here), or it can receive the identifier of the third service differentiation channel from the fifth entity, and distinguish the channel according to the third service The identifier determines the third service differentiation channel.
  • the method further includes: the first entity of the network node performs header compression on the data packet.
  • the method further includes: the first entity of the network node performs header compression on the data packet after the Adapt layer header is added.
  • step 1503 includes: the first entity of the network node submits the data packet with the header of the Adapt layer added and header compressed to the sixth entity through the third service differentiation channel.
  • the network node can perform header compression through a configured header compression algorithm.
  • the sending side may use the ROHC protocol to perform header compression.
  • the Donor-CU may carry the indication information for configuring the header compression mode and/or the header compression compression algorithm in the configuration information sent to the network node (for example, the access IAB node or the Donor-DU).
  • the configuration information sent by the Donor-CU to the Donor-DU can be carried in the F1AP message from the Donor-CU to the Donor-DU.
  • the configuration information sent by the Donor-CU to the access IAB node can be carried in the F1AP message of the Donor-CU to the DU part of the access IAB node, or it can be carried in the RRC message of the Donor-CU to the MT part of the access IAB node in.
  • the Adapt layer header added by the first entity of the network node includes a header compression mode indication field, and the header compression mode indication field is used to indicate the header compression mode adopted by the first entity of the network node.
  • the next hop node of the data packet determines whether to decompress the data packet according to the instruction information.
  • header compression mode indication field please refer to the content of the relevant part of the first embodiment, which will not be repeated here.
  • header compression or decompression methods in the first to third embodiments may not be coupled with other methods in the corresponding embodiments, that is, they can be executed independently.
  • the IAB node can select a new parent node to establish a connection. For example, in the IAB network shown in Figure 1, if the wireless backhaul link between IAB node 5 and IAB node 2 has a radio link failure, IAB node 5 can select IAB node 4 as the new The parent node establishes a wireless backhaul link.
  • the Adapt layer of the IAB node also needs to be re-established.
  • the fourth embodiment provides an Adapt layer reconstruction method, as shown in FIG. 16, including:
  • the upper protocol layer of the Adapt layer of the network node sends Adapt layer reconstruction instruction information to the Adapt layer of the network node.
  • step 1601 the upper protocol layer of the Adapt layer of the network node triggers the Adapt layer reconstruction.
  • the RRC layer of the MT part of the IAB node triggers the Adapt layer reconstruction of the MT part.
  • the MT part of the IAB node receives the RRC message sent by the Donor-CU.
  • the RRC message contains the indication information (for example, Adapt-reestablish) of the Adapt layer reconstruction.
  • the RRC layer of the MT part of the IAB node is based on the Adapt layer reconstruction indication.
  • the information triggers the reconstruction of the Adapt layer in the MT part, or triggers the reconstruction of the Adapt layer in the DU part of the IAB node.
  • the F1AP layer of the Donor-DU triggers the reconstruction of the Adapt layer of the Donor-DU.
  • the Donor-DU receives the F1AP message sent by the Donor-CU, and the F1AP message contains the indication information of the Adapt layer reconstruction, and the Donor-DU triggers the Adapt layer reconstruction of the Donor-DU according to the indication information of the Adapt layer reconstruction.
  • the F1AP layer of the DU part of the IAB node triggers the reconstruction of the Adapt layer of the DU/MT part of the IAB node.
  • the DU part of the IAB node receives the F1AP message sent by the Donor-CU, which contains the indication information of the Adapt layer reconstruction.
  • the DU/MT part of the IAB node triggers the DU/MT part of the IAB node according to the indication information of the Adapt layer reconstruction.
  • Adapt layer reconstruction is another example, the F1AP layer of the DU part of the IAB node receives the F1AP message sent by the Donor-CU, which contains the indication information of the Adapt layer reconstruction.
  • the Adapt layer of the network node receives the Adapt layer reconstruction instruction information from the upper protocol layer, and reconstructs the Adapt layer according to the Adapt layer reconstruction instruction information.
  • step 1602 may include: the Adapt layer of the network node configures a new Adapt layer routing and forwarding table and/or a new bearer mapping relationship according to the Adapt layer reconstruction instruction information.
  • the new Adapt layer routing and forwarding table may include a new uplink Adapt layer routing and forwarding table and/or a new downlink Adapt layer routing and forwarding table.
  • the new bearer mapping relationship may refer to the new mapping relationship between the terminal's RB and the service differentiation channel of the new egress link, the new mapping relationship between the service differentiation channel of the ingress link and the service differentiation channel of the new egress link, etc.
  • the method further includes: the Adapt layer of the network node retransmits the unsuccessfully sent data packet to the next hop node in the new Adapt layer routing and forwarding table according to the configured new Adapt layer routing and forwarding table, thereby avoiding The terminal is losing packets.
  • the unsuccessfully sent data packet can be a data packet in the Adapt layer cache of the network node, or the Adapt layer of the network node has been submitted to the lower protocol layer, and then sent back to the Adapt layer by the lower protocol layer The data packet (the data packet can be a data packet that the lower protocol layer has not successfully sent).
  • the Adapt layer receives a successful transmission indication for a certain data packet (Adapt PDU or Adapt SDU or RLC SDU) from the lower protocol layer (for example, the RLC layer), then the Adapt layer may The data packet is discarded according to the instruction, thereby clearing the buffer space.
  • Adapt PDU or Adapt SDU or RLC SDU Adapt PDU or Adapt SDU or RLC SDU
  • This optional method allows the Adapt layer to effectively perform cache management and discard data packets that have no cache value when the Adapt layer has a cache.
  • the RLC layer entity on the sending side of the network node may, after receiving the RLC status report fed back by the receiving side of the node communicating with the network node, according to the data packet Acknowledge (ACK) information indicated in the RLC status report,
  • the upper protocol layer namely the Adapt layer, sends an acknowledgment of a successful transmission indication, and the Adapt layer discards the data packet according to the indication and clears the buffer space.
  • the method provided in the fourth embodiment can rebuild the Adapt layer of the network node when the IAB network topology changes to provide guarantee for data lossless transmission, avoid the problem of packet loss due to changes in the wireless backhaul link topology, and improve data transmission Reliability.
  • a network node includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the network nodes into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the embodiment of the present application also provides a network node (denoted as network node 170), as shown in FIG. 17, including:
  • the obtaining unit 1701 is configured to receive a data packet submitted from a protocol layer entity of the lower protocol layer of the adaptation layer of the network node, the data packet being a first type data packet, and the first type data packet including an adaptation Data packets of the header and the load of the adaptation layer;
  • the judging unit 1702 is configured to judge whether the network node is the destination node of the data packet routing at the adaptation layer;
  • the processing unit 1703 is configured to process the data packet according to the judgment result.
  • the judgment result is: the network node is the destination node of the data packet routing at the adaptation layer;
  • the processing unit 1703 is specifically configured to deliver the adaptation layer payload in the data packet to a second entity, which is a protocol layer entity of the protocol layer of the F1 interface or an upper layer protocol layer of the adaptation layer Protocol layer entity.
  • the judgment result is: the network node is the destination node of the data packet routing at the adaptation layer;
  • the processing unit 1703 is specifically configured to store the data packet in the buffer of the adaptation layer.
  • the judgment result is: the network node is not the destination node of the data packet routing at the adaptation layer;
  • the processing unit 1703 is specifically configured to deliver the data packet to a third entity, and the third entity is a protocol layer entity of the protocol layer of the wireless backhaul interface or a protocol layer entity of the lower protocol layer of the adaptation layer.
  • the judgment result is: the network node is not the destination node of the data packet routing at the adaptation layer;
  • the processing unit 1703 is specifically configured to submit the adaptation layer payload in the data packet and the information in the adaptation layer header in the data packet to a third entity, which is a wireless backhaul interface
  • a third entity which is a wireless backhaul interface
  • the data packet is a data PDU of the adaptation layer.
  • the data packet is a control PDU of the adaptation layer.
  • the network node further includes a determining unit 1704, the determining unit 1704 is configured to determine the next hop node of the data packet, and the processing unit 1703 is further configured to send a message to the third The entity submits information for indicating the next hop node; and/or,
  • the processing unit 1703 is further configured to submit the identification of the first service differentiation channel to the third entity, where the first service differentiation channel is the service differentiation from which the data packet received by the obtaining unit 1701 comes Channel; where the service differentiation channel is a logical channel or an RLC channel or an RLC bearer; and/or,
  • the network node further includes a determining unit 1704, the determining unit 1704 is configured to determine a second service differentiation channel for delivering the data packet to the next hop node of the data packet, and the processing unit 1703, It is also used to deliver the identification of the second service differentiation channel to the third entity; wherein, the second service differentiation channel is the service differentiation channel through which the third entity sends the data packet, and the service differentiation channel is logical Channel or RLC channel or RLC bearer.
  • the judging unit 1702 is specifically configured to determine the routing information in the adaptation layer header in the data packet, whether the adaptation layer header in the data packet contains routing information, and the data packet Whether it is one or more of the control PDUs, it is determined whether the network node is the destination node of the data packet routing at the adaptation layer.
  • the obtaining unit 1701, the judging unit 1702, the processing unit 1703, and the determining unit 1704 may be located in the first entity of the network node, and the first entity is an adaptation layer entity.
  • the embodiment of the present application also provides a network node (denoted as network node 180), as shown in FIG. 18, including:
  • the obtaining unit 1801 is configured to receive a data packet from a first entity, where the first entity is an adaptation layer entity;
  • the delivery unit 1802 is configured to deliver the data packet to the fourth entity through the second service differentiation channel;
  • the fourth entity is a protocol layer entity of the lower protocol layer of the adaptation layer, the second service differentiation channel corresponds to the next hop node of the data packet, and the service differentiation channel is a logical channel or an RLC channel or RLC Bearer.
  • the second type of data packet is a data packet including an adaptation layer payload.
  • the network node further includes:
  • the adding unit 1803 is configured to add an adaptation layer header to the data packet
  • the delivery unit 1802 is specifically configured to deliver the data packet with the adaptation layer header added to the fourth entity through the second service differentiation channel.
  • the network node further includes: a determining unit 1804;
  • the determining unit 1804 is configured to determine the next hop node for the data packet; and/or,
  • the determining unit 1804 is configured to determine the second service differentiation channel for the data packet.
  • the determining unit 1804 is specifically configured to: determine the second service differentiation channel according to the first service differentiation channel, where the first service differentiation channel is the data packet received by the first entity The business distinguishes the channel from.
  • the determining unit 1804 is specifically configured to determine the second RB according to the identity of the RB of the terminal to which the data packet belongs, and/or the correspondence between the RB of the terminal and the service differentiation channel The business distinguishes the channel.
  • the determining unit 1804 is specifically configured to determine the second service differentiation channel according to the QoS label carried in the data packet and the corresponding relationship between the QoS label and the service differentiation channel.
  • the determining unit 1804 is specifically configured to determine the second service differentiation channel according to the identifier of the second service differentiation channel received from the first entity.
  • the determining unit 1804 is specifically configured to determine the next hop node according to the information used to indicate the next hop node received from the first entity.
  • the acquiring unit 1801, the adding unit 1803, the submitting unit 1802, and the determining unit 1804 may be located in a third entity of the network node, and the third entity is an adaptation layer entity.
  • the embodiment of the present application also provides a network node (denoted as network node 190), as shown in FIG. 19, including:
  • the acquiring unit 1901 is configured to receive a data packet from a fifth entity, the fifth entity being a protocol layer entity of the protocol layer of the F1 interface or a protocol layer entity of the upper protocol layer of the adaptation layer, and the data packet is of the second type A data packet, the second type of data packet is a data packet including an adaptation layer payload;
  • the adding unit 1902 is configured to add an adaptation layer header to the data packet
  • the delivery unit 1903 is configured to deliver the data packet with the adaptation layer header added to the sixth entity through the third service differentiation channel.
  • the sixth entity is a protocol layer entity of the lower protocol layer of the adaptation layer.
  • the third service differentiation channel corresponds to the next hop node of the data packet, and the service differentiation channel is a logical channel or an RLC channel or an RLC bearer.
  • the network node further includes: a determining unit 1904;
  • the determining unit 1904 is configured to determine the next hop node of the data packet; and/or,
  • the determining unit 1904 is configured to determine the third service differentiation channel.
  • the acquiring unit 1901, the adding unit 1902, the submitting unit 1903, and the determining unit 1904 may be located in the first entity of the network node, and the first entity is an adaptation layer entity.
  • the aforementioned network node 170, network node 180, and network node 190 may be network devices, or may be chips in the network devices.
  • the units in FIG. 17, FIG. 18, and FIG. 19 may also be referred to as modules.
  • the processing unit may be referred to as a processing module.
  • the name of each unit may not be the name shown in the figure.
  • the unit that receives the data packet may also be called the receiving unit (for example, the acquiring unit 1701 may be called the receiving unit 1701), and the unit that delivers the data packet may also be called the sending unit (for example, the delivering unit 1903 may be called the sending unit 1903).
  • a unit that performs other actions may be referred to as a processing unit (for example, the determining unit 1904 may be referred to as a processing unit 1904), depending on how the modules are divided.
  • each unit in Fig. 17, Fig. 18 and Fig. 19 is implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer readable storage medium.
  • the technical solutions of the embodiments of the present application essentially or the part that contributes to the prior art or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage
  • the medium includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • Storage media for storing computer software products include: U disk, mobile hard disk, read-only memory (read-only memory, referred to as ROM), random access memory (random access memory, referred to as RAM), magnetic disks or optical disks, etc.
  • the medium of the program code include: U disk, mobile hard disk, read-only memory (read-only memory, referred to as ROM), random access memory (random access memory, referred to as RAM), magnetic disks or optical disks, etc.
  • the embodiment of the present application also provides a schematic diagram of the hardware structure of a network node (denoted as network node 200). See FIG. 20 or FIG. 21.
  • the network node 200 includes a processor 2001, and optionally, also includes a connection with the processor 2001.
  • the memory 2002 includes a processor 2001, and optionally, also includes a connection with the processor 2001.
  • the processor 2001 can be a general-purpose central processing unit (central processing unit, CPU for short), microprocessor, application-specific integrated circuit (ASIC for short), or one or more programs used to control the program of this application Implementation of integrated circuits.
  • the processor 2001 may also include multiple CPUs, and the processor 2001 may be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, or processing cores for processing data (for example, computer program instructions).
  • the memory 2002 can be ROM or other types of static storage devices that can store static information and instructions, RAM, or other types of dynamic storage devices that can store information and instructions, or it can be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory).
  • read-only memory EEPROM for short
  • compact disc read-only memory CD-ROM for short
  • optical disc storage including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.
  • the embodiments of this application do not impose any limitation on this.
  • the memory 2002 may exist independently or be integrated with the processor 2001. Wherein, the memory 2002 may contain computer program code.
  • the processor 2001 is configured to execute the computer program code stored in the memory 2002, so as to implement the method provided in the embodiment of the present application.
  • the network node 200 further includes a transceiver 2003.
  • the processor 2001, the memory 2002 and the transceiver 2003 are connected by a bus.
  • the transceiver 2003 is used to communicate with other communication devices or other protocol layers in a network node.
  • the transceiver 2003 may include a transmitter and a receiver.
  • the device in the transceiver 2003 for implementing the receiving function (for example, receiving the data packet submitted by the upper protocol layer) can be regarded as a receiver, and the receiver is used to perform the receiving steps in the embodiment of the present application.
  • the device used in the transceiver 2003 to implement the sending function (for example, submitting data packets to other protocol layers) can be regarded as a transmitter, and the transmitter is used to perform the sending or submitting steps in the embodiment of the present application.
  • the schematic structural diagram shown in FIG. 20 may be used to illustrate the structure of the network node involved in the foregoing embodiment.
  • the processor 2001 is used to control and manage the actions of the network node.
  • the processor 2001 is used to support the network node to execute the steps in FIG. 10 to FIG. 16, and/or the network in other processes described in the embodiments of the present application.
  • the action performed by the node is performed by the node.
  • the processor 2001 can communicate with other communication devices or other protocol layers in the network node through the transceiver 2003 (in this case, when the network node executes the method shown in Embodiment 1 or Embodiment 3, the transceiver 2003 may be located in the first In the entity, when the network node executes the method shown in the second embodiment, the transceiver 2003 may be located in the third entity).
  • the memory 2002 is used to store program codes and data of the terminal.
  • the processor 2001 includes a logic circuit and an input interface and/or an output interface. Among them, the output interface is used to execute the sending or submitting action in the corresponding method, and the input interface is used to execute the receiving action in the corresponding method.
  • FIG. 21 The schematic structural diagram shown in FIG. 21 may be used to illustrate the structure of the network node involved in the foregoing embodiment.
  • the processor 2001 is used to control and manage the actions of the network node.
  • the processor 2001 is used to support the network node to execute the steps in FIG. 10 to FIG. 16, and/or the network in other processes described in the embodiments of the present application.
  • the action performed by the node is performed by the node.
  • the processor 2001 may communicate with other communication devices or other protocol layers in the network node through the input interface and/or output interface (in this case, when the network node executes the method shown in Embodiment 1 or Embodiment 3, the input interface and /Or the output interface may be located in the first entity, and when the network node executes the method shown in the second embodiment, the input interface and/or the output interface may be located in the third entity).
  • the memory 2002 is used to store program codes and data of the terminal.
  • the embodiments of the present application also provide a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute any of the above methods.
  • the embodiments of the present application also provide a computer program product containing instructions, which when run on a computer, cause the computer to execute any of the above methods.
  • the embodiment of the present application also provides a system chip, which is applied in a network node, the system chip includes: at least one processor, and related program instructions are executed in the at least one processor to execute the above-mentioned embodiments. Any one of the methods.
  • An embodiment of the present application also provides a communication system, including: one or more network nodes of the network nodes provided in the foregoing embodiment.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it may be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions can be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, digital subscriber line (digital subscriber line, referred to as DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or may include one or more data storage devices such as a server or a data center that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请提供了一种通信方法及相关装置。在该方法中，网络节点的适配层实体在接收到下层协议层的协议层实体递交的数据包时，可以根据自身是否为数据包在适配层路由的目的节点，对数据包进行不同的处理；在接收到上层协议层递交的数据包时，通过合适的与数据包的下一跳节点对应的业务区分通道，将数据包递交给下层协议层，从而使得数据包正确的传输至数据包的下一跳节点，从而保证数据包在IAB网络中正确传输。

Description

一种通信方法及相关装置
本申请要求于2019年02月15日提交国家知识产权局、申请号为201910118003.8、申请名称为“一种通信方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及相关装置。
背景技术
在包含接入回传一体化(integrated access and backhaul，简称IAB)节点的网络中，存在多跳和多连接场景，即多个节点(例如，多个IAB节点)可以同时为终端服务、且终端可以通过多跳IAB节点传输数据包。也就是说，一条传输路径可以包括至少一段无线回传链路和一段无线接入链路。在当前的通信标准讨论中，提出了在无线回传链路引入适配层(即Adaptation layer，为表述便利，本文中简称为Adapt层)。然而，目前的通信标准中并没有定义无线回传链路上的Adapt层处理数据包的流程，而不当的数据包处理流程会使得数据包无法在无线回传链路上正确传输。
发明内容
本申请实施例提供了一种通信方法及相关装置，用于使得数据包正确的在无线回传链路上进行传输。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供了一种通信方法，包括：网络节点的适配层实体中的第一实体接收从下层协议层的协议层实体递交的包括适配层头和适配层载荷的数据包，第一实体判断网络节点是否为数据包在适配层路由的目的节点，并根据判断结果处理数据包。
其中，第一实体位于网络节点的接收侧。
第一方面提供的方法，由于网络节点是否为适配层路由的目的节点会直接影响到后续数据包的处理过程。因此，网络节点根据自身是否为数据包在适配层路由的目的节点的判断结果处理数据包，可以正确的处理数据包，防止数据包的处理过程出错。
在一种可能的实现方式中，判断结果为：网络节点为数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体将数据包中的适配层载荷向第二实体递交，第二实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体。
该种可能的实现方式，在网络节点为数据包在适配层路由的目的节点的情况下，例如，网络节点为接入IAB节点或宿主节点或Donor-DU时，由于数据包的下一跳节点中已经没有适配层。因此，网络节点可以将适配层载荷向第二实体递交，从而避免数据包的下一跳节点无法解析数据包的问题。
在一种可能的实现方式中，判断结果为：网络节点为数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体对数据包中的适配层载荷进行解头压缩，并将解头压缩后的适配层载荷向第二实体递交。
该种可能的实现方式，在网络节点为数据包在适配层路由的目的节点的情况下，例如， 网络节点为接入IAB节点或宿主节点或Donor-DU时，由于数据包的下一跳节点中已经没有适配层，若IAB网络中对数据包的适配层载荷进行头压缩，则网络节点还需要对适配层载荷进行解头压缩，从而避免数据包的下一跳节点无法对数据包的适配层载荷解头压缩的问题。
在一种可能的实现方式中，判断结果为：网络节点为数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体对数据包进行解头压缩，并将解头压缩后的数据包中的适配层载荷向第二实体递交。
该种可能的实现方式，在网络节点为数据包在适配层路由的目的节点的情况下，例如，网络节点为接入IAB节点或宿主节点或Donor-DU时，由于数据包的下一跳节点中已经没有适配层，若IAB网络中对数据包进行头压缩，则网络节点还需要对数据包进行解头压缩，从而避免数据包的下一跳节点无法对数据包解头压缩以及无法解析数据包的问题。
在一种可能的实现方式中，判断结果为：网络节点为数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体将数据包存储到适配层的缓存中。
该种可能的实现方式，若数据包为控制PDU，由于网络节点需要根据该控制PDU获取控制PDU中包含的信息，因此，网络节点的第一实体将数据包存储到适配层的缓存中，以便进行进一步的处理，从而保证数据包的正确处理。
在一种可能的实现方式中，判断结果为：网络节点不是数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体将数据包向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
其中，第一方面中的第三实体位于网络节点的发送侧。
该种可能的实现方式，在网络节点不是数据包在适配层路由的目的节点的情况下，例如，网络节点为中间IAB节点时，由于数据包的下一跳节点中有适配层，因此，网络节点可以直接将数据包向第三实体递交，而不用移除适配层头，数据包的下一跳节点可以根据数据包中的适配层头在适配层转发数据包或作其他处理，保证数据包的正确传输。
在一种可能的实现方式中，判断结果为：网络节点不是数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体将数据包中的适配层载荷和数据包中的适配层头中的信息向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
该种可能的实现方式，在网络节点不是数据包在适配层路由的目的节点的情况下，例如，网络节点为中间IAB节点时，由于数据包的下一跳节点中有适配层，因此，网络节点在发送适配层载荷的同时，还需要将适配层头中的信息向第三实体递交，数据包的下一跳节点可以根据适配层头中的信息在适配层转发数据包或作其他处理，保证数据包的正确传输。
在一种可能的实现方式中，判断结果为：网络节点不是数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体对数据包中的适配层载荷进行解头压缩，并将解头压缩后的适配层载荷和数据包中的适配层头中的信息向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或适配层的下层协 议层的协议层实体。
该种可能的实现方式，在网络节点不是数据包在适配层路由的目的节点的情况下，例如，网络节点为中间IAB节点时，若头压缩方式为逐跳头压缩，则数据包的上一跳节点对数据包的适配层载荷进行头压缩，那么网络节点的第一实体也需要对适配层载荷进行解头压缩。
在一种可能的实现方式中，判断结果为：网络节点不是数据包在适配层路由的目的节点，网络节点的第一实体根据判断结果处理数据包，包括：网络节点的第一实体对数据包进行解头压缩，并将解头压缩后的数据包中的适配层载荷和解头压缩后的数据包中的适配层头中的信息向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
该种可能的实现方式，在网络节点不是数据包在适配层路由的目的节点的情况下，例如，网络节点为中间IAB节点时，若头压缩方式为逐跳头压缩，则数据包的上一跳节点对数据包进行头压缩，那么网络节点的第一实体也需要对数据包进行解头压缩。
在一种可能的实现方式中，数据包为适配层的数据PDU。
在一种可能的实现方式中，数据包为适配层的控制PDU。
在一种可能的实现方式中，该方法还包括以下一项或多项：网络节点的第一实体确定数据包的下一跳节点，网络节点的第一实体向第三实体递交用于指示下一跳节点的信息；或，网络节点的第一实体将第一业务区分通道的标识向第三实体递交，第一业务区分通道为第一实体接收到的数据包所来自的业务区分通道；其中，业务区分通道为逻辑信道或RLC信道或RLC承载；或，网络节点的第一实体确定向数据包的下一跳节点递交数据包的第二业务区分通道；网络节点的第一实体向第三实体递交第二业务区分通道的标识；其中，第二业务区分通道为第三实体发送数据包的业务区分通道，业务区分通道为逻辑信道或RLC信道或RLC承载。
该种可能的实现方式，网络节点的第一实体还可以向第三实体递交数据包的下一跳节点和/或第二业务区分通道，或用于确定数据包的下一跳节点和/或第二业务区分通道的信息(即第一业务区分通道的标识)，从而保证第三实体正确的向下层协议层递交数据包。
在一种可能的实现方式中，网络节点的第一实体判断网络节点是否为数据包在适配层路由的目的节点，包括：网络节点的第一实体根据数据包中的适配层头中的路由信息、数据包中的适配层头中是否包含路由信息，以及数据包是否为控制PDU中的一种或多种判断网络节点是否为数据包在适配层路由的目的节点。
该种可能的实现方式，提供了多种判断网络节点是否为适配层路由的目的节点的方法，从而使得本申请可以应用于不同的场景。
第二方面，提供了一种网络节点，包括：获取单元，用于接收从网络节点的适配层的下层协议层的协议层实体递交的包括适配层头和适配层载荷的数据包；判断单元，用于判断网络节点是否为数据包在适配层路由的目的节点；处理单元，用于根据判断结果处理数据包。
由于第二方面的网络节点用于执行第一方面提供的方法。因此，第二方面提供的网络节点的有益效果可参见第一方面所提供的方法，在此不再赘述。
第三方面，提供了一种通信方法，包括：网络节点的第三实体从第一实体接收数据包， 第一实体和第三实体均为适配层实体；网络节点的第三实体通过第二业务区分通道将数据包递交给第四实体；其中，第四实体为适配层的下层协议层的协议层实体，第二业务区分通道与数据包的下一跳节点对应，业务区分通道为逻辑信道或RLC信道或RLC承载。
其中，网络节点的第一实体位于网络节点的接收侧，网络节点的第三实体位于网络节点的发送侧。
第三方面提供的方法，网络节点的第三实体通过与数据包的下一跳节点对应的第二业务区分通道将数据包递交给第四实体，可以保证数据包正确的传输至数据包的下一跳节点。
在一种可能的实现方式中，在数据包为包括适配层载荷的数据包的情况下，该方法还包括：网络节点的第三实体为数据包添加适配层头；网络节点的第三实体通过第二业务区分通道将数据包递交给第四实体，包括：网络节点的第三实体通过第二业务区分通道将添加适配层头后的数据包递交给第四实体。
该种可能的实现方式，网络节点的第三实体可以为数据包添加适配层头，以便后续节点根据适配层头中的信息转发数据包或作其他处理。
在一种可能的实现方式中，该方法还包括以下一项或多项：网络节点的第三实体为数据包确定下一跳节点；或，网络节点的第三实体为数据包确定第二业务区分通道。
该种可能的实现方式中，网络节点的第三实体可以确定递交数据包的下一跳节点和/或第二业务区分通道，从而保证第三实体正确的向下层协议层递交数据包。
在一种可能的实现方式中，网络节点的第三实体为数据包确定第二业务区分通道，包括：网络节点的第三实体根据第一业务区分通道确定第二业务区分通道，第一业务区分通道为第一实体接收到的数据包所来自的业务区分通道。
在一种可能的实现方式中，网络节点的第三实体为数据包确定第二业务区分通道，包括：网络节点的第三实体根据数据包所属的终端的RB的标识，或，终端的RB与业务区分通道之间的对应关系中的一个或多个确定第二业务区分通道。
在一种可能的实现方式中，网络节点的第三实体为数据包确定第二业务区分通道，包括：网络节点的第三实体根据数据包中携带的QoS标签，以及QoS标签与业务区分通道之间的对应关系确定第二业务区分通道。
在一种可能的实现方式中，网络节点的第三实体为数据包确定第二业务区分通道，包括：网络节点的第三实体从第一实体接收第二业务区分通道的标识；网络节点的第三实体根据第二业务区分通道的标识确定第二业务区分通道。
第三方面中提供了多种确定第二业务区分通道的方法，从而使得该方法可以灵活的适用不同的场景。
在一种可能的实现方式中，网络节点的第三实体为数据包确定下一跳节点，包括：网络节点的第三实体从第一实体接收用于指示下一跳节点的信息；网络节点的第三实体根据用于指示下一跳节点的信息确定下一跳节点。
在一种可能的实现方式中，在网络节点的第三实体为数据包添加适配层头之前，该方法还包括：网络节点的第三实体对数据包进行头压缩。该种可能的实现方式，网络节点的第三实体通过对数据包进行头压缩，可以降低数据包在无线回传链路传输过程中的头开销，减少空口资源消耗。
在一种可能的实现方式中，该方法还包括：网络节点的第三实体对添加适配层头后的 数据包进行头压缩；网络节点的第三实体通过第二业务区分通道将添加适配层头后的数据包递交给第四实体，包括：网络节点的第三实体通过第二业务区分通道将添加适配层头并通过头压缩后的数据包递交给第四实体。该种可能的实现方式，网络节点的第三实体通过对数据包进行头压缩，可以降低数据包在无线回传链路传输过程中的头开销，减少空口资源消耗。
第四方面，提供了一种网络节点，包括：获取单元，用于从适配层实体中的第一实体接收数据包；递交单元，用于通过第二业务区分通道将数据包递交给第四实体；其中，第四实体为适配层的下层协议层的协议层实体，第二业务区分通道与数据包的下一跳节点对应，业务区分通道为逻辑信道或RLC信道或RLC承载。
由于第四方面的网络节点用于执行第三方面提供的方法。因此，第四方面提供的网络节点的有益效果可参见第三方面所提供的方法，在此不再赘述。
第五方面，提供了一种通信方法，包括：网络节点的第一实体从第五实体接收数据包并为数据包添加适配层头；其中，第五实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体，第一实体为适配层实体，数据包为包括适配层载荷的数据包；网络节点的第一实体通过第三业务区分通道将添加适配层头后的数据包递交给第六实体，第六实体为适配层的下层协议层的协议层实体，第三业务区分通道与数据包的下一跳节点对应，业务区分通道为逻辑信道或RLC信道或RLC承载。
第五方面提供的方法，网络节点的第一实体通过与数据包的下一跳节点对应的第三业务区分通道将数据包递交给第六实体，可以保证数据包正确的传输至数据包的下一跳节点。
在一种可能的实现方式中，该方法还包括以下一项或多项：网络节点的第一实体确定数据包的下一跳节点；或，网络节点的第一实体确定第三业务区分通道。
该种可能的实现方式中，网络节点的第一实体可以确定递交数据包的下一跳节点和/或第三业务区分通道，从而保证第一实体正确的向下层协议层递交数据包。
在一种可能的实现方式中，在网络节点的第一实体为数据包添加适配层头之前，该方法还包括：网络节点的第一实体对数据包进行头压缩。该种可能的实现方式，网络节点的第一实体通过对数据包进行头压缩，可以降低数据包在无线回传链路传输过程中的头开销，减少空口资源消耗。
在一种可能的实现方式中，该方法还包括：网络节点的第一实体对添加适配层头之后的数据包进行头压缩；网络节点的第一实体通过第三业务区分通道将添加适配层头后的数据包递交给第六实体，包括：网络节点的第一实体通过第三业务区分通道将添加适配层头并进行头压缩后的数据包递交给第六实体。该种可能的实现方式，网络节点的第一实体通过对数据包进行头压缩，可以降低数据包在无线回传链路传输过程中的头开销，减少空口资源消耗。
第六方面，提供了一种网络节点，包括：获取单元，用于从第五实体接收数据包，第五实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体，数据包为包括适配层载荷的数据包；添加单元，用于为数据包添加适配层头；递交单元，用于通过第三业务区分通道将添加适配层头后的数据包递交给第六实体，第六实体为适配层的下层协议层的协议层实体，第三业务区分通道与数据包的下一跳节点对应，业务区分通道为逻辑信道或RLC信道或RLC承载。
由于第六方面的网络节点用于执行第五方面提供的方法。因此，第六方面提供的网络节点的有益效果可参见第五方面所提供的方法，在此不再赘述。
第七方面，提供了一种适配层重建方法，包括：网络节点的适配层的上层协议层向所述网络节点的适配层发送适配层重建指示信息；所述网络节点的适配层从上层协议层接收适配层重建指示信息；所述网络节点的适配层根据适配层重建指示信息重建适配层。
第七方面提供的方法，在IAB网络拓扑发送变化时，可以重建网络节点的Adapt层，为数据无损传输提供保障，可以避免由于无线回传链路拓扑变化而导致丢包的问题，提高数据传输的可靠性。
在一种可能的实现方式中，所述网络节点的适配层根据适配层重建指示信息重建适配层，包括：所述网络节点的适配层根据适配层重建指示信息配置新的适配层路由转发表或新的承载映射关系中的一个或多个。
在一种可能的实现方式中，所述方法还包括：所述网络节点的适配层根据配置的所述新的适配层路由转发表，向所述新的适配层路由转发表中的下一跳节点重传未成功发送的数据包。该种可能的实现方式，通过重传未成功发送的数据包，可以避免终端丢包。
第八方面，提供了一种网络节点，包括：发送单元，用于向所述网络节点的适配层发送适配层重建指示信息；接收单元，用于从适配层的上层协议层接收适配层重建指示信息；重建单元，用于根据适配层重建指示信息重建适配层。
在一种可能的实现方式中，所述发送单元位于所述网络节点的适配层的上层协议层中，所述接收单元和所述重建单元位于所述网络节点的适配层中。
在一种可能的实现方式中，所述重建单元具体用于：根据适配层重建指示信息配置新的适配层路由转发表或新的承载映射关系中的一个或多个。
在一种可能的实现方式中，所述发送单元还用于：根据配置的所述新的适配层路由转发表，向所述新的适配层路由转发表中的下一跳节点重传未成功发送的数据包。
由于第八方面的网络节点用于执行第七方面提供的方法。因此，第八方面提供的网络节点的有益效果可参见第七方面所提供的方法，在此不再赘述。
第九方面，提供了一种网络节点，包括：处理器。处理器与存储器连接，存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，从而实现第一方面，第三方面，第五方面或第七方面中提供的任意一种方法。其中，存储器和处理器可以集成在一起，也可以为独立的器件。若为后者，存储器可以位于网络节点内，也可以位于网络节点外。
在一种可能的实现方式中，处理器包括逻辑电路以及输入接口和/或输出接口。其中，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。
在一种可能的实现方式中，网络节点还包括通信接口和通信总线，处理器、存储器和通信接口通过通信总线连接。通信接口用于执行相应方法中的收发的动作。通信接口也可以称为收发器。可选的，通信接口包括发送器和接收器，该情况下，发送器用于执行相应方法中的发送的动作，接收器用于执行相应方法中的接收的动作。
在一种可能的实现方式中，网络节点以芯片的产品形态存在。
第十方面，提供了一种计算机可读存储介质，包括指令，当该指令在计算机上运行时，使得计算机执行第一方面，第三方面，第五方面或第七方面中提供的任意一种方法。
第十一方面，提供了一种包含指令的计算机程序产品，当该指令在计算机上运行时，使得计算机执行第一方面，第三方面，第五方面或第七方面中提供的任意一种方法。
第十二方面，提供了一种系统芯片，该系统芯片应用在网络节点中，该系统芯片包括：至少一个处理器，涉及的程序指令在该至少一个处理器中执行，以执行第一方面，第三方面，第五方面或第七方面中提供的任意一种方法。
第十三方面，提供了一种通信系统，包括：第二方面，第四方面，第六方面或第八方面提供的网络节点中的一个或多个网络节点。
第九方面至第十三方面中的任一种实现方式所带来的技术效果可参见第一方面、第三方面、第五方面和第七方面中对应实现方式所带来的技术效果，此处不再赘述。
其中，需要说明的是，上述各个方面中的任意一个方面的各种可能的实现方式，在方案不矛盾的前提下，均可以进行组合。
附图说明
图1为本申请实施例提供的一种IAB组网场景示意图；
图2为本申请实施例提供的一条传输路径中的节点的示意图；
图3至图5分别为本申请实施例提供的一种协议栈架构示意图；
图6为本申请实施例提供的一种适配层数据包类型的示意图；
图7至图9分别为本申请实施例提供的一种适配层实体和RLC层实体之间的对应关系示意图；
图10为本申请实施例提供的一种适配层的状态报告的格式示意图；
图11为本申请实施例提供的一种通信方法的流程图；
图12为本申请实施例提供的一种处理数据包的实现方式的示意图；
图13至图15分别为本申请实施例提供的一种通信方法的流程图；
图16为本申请实施例提供的一种适配层重建的方法流程图；
图17至图19分别为本申请实施例提供的一种网络节点的组成示意图；
图20和图21分别为本申请实施例提供的一种网络节点的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B。本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例的技术方案可以应用于各种通信系统。例如：正交频分多址(orthogonal frequency-division multiple access，简称OFDMA)、单载波频分多址(single carrier frequency-division multiple access，简称SC-FDMA)和其它系统等。术语“系统”可以和“网络”相互替换。OFDMA系统可以实现诸如演进通用无线陆地接入(evolved universal terrestrial radio access，简称E-UTRA)、超级移动宽带(ultra mobile broadband，简称UMB) 等无线技术。E-UTRA是通用移动通信系统(universal mobile telecommunications system，简称UMTS)演进版本。第三代合作伙伴计划(3rd generation partnership project，简称3GPP)在长期演进(long term evolution，简称LTE)和基于LTE演进的各种版本是使用E-UTRA的新版本。采用新空口(new radio，简称NR)的第五代(5th-generation，简称5G)网络是正在研究当中的下一代通信系统。此外，通信系统还可以适用于面向未来的通信技术，都适用本申请实施例提供的技术方案。
本申请涉及的网元包括终端和无线回传节点。
本申请实施例中的终端还可以称为用户设备(user equipment，简称UE)、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。终端还可以是无线局域网(wireless local area networks，简称WLAN)中的站点(station，简称ST)，可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，简称SIP)电话、无线本地环路(wireless local loop，简称WLL)站、个人数字处理(personal digital assistant，简称PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备(也可以称为穿戴式智能设备)。终端还可以为下一代通信系统中的终端，例如，5G网络中的终端或者未来演进的公共陆地移动网络(public land mobile network，简称PLMN)中的终端。
无线回传节点用于为无线接入无线回传节点的节点(例如，终端)提供无线回传服务。其中，无线回传服务是指通过无线回传链路提供的数据和/或信令回传服务。
本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。本申请实施例中以提供的方法应用于NR系统或5G网络中为例进行说明。但是需要说明的是，本申请实施例提供的方法也可以应用于其他网络中，比如，可以应用在演进分组系统(evolved packet system，简称EPS)网络(即通常所说的第四代(4th generation，简称4G)网络)中。相应的，当本申请实施例提供的方法应用在EPS网络中时，执行本申请实施例提供的方法的网络节点替换为EPS网络中的网络节点即可。例如，当本申请实施例提供的方法应用在5G网络或NR系统中时，下文中的无线回传节点可以为5G网络中的无线回传节点，示例性的，5G网络中的无线回传节点可以称为IAB节点，当然也可以有其他名称，本申请实施例对此不作具体限定。当本申请实施例提供的方法应用在EPS网络中时，下文中的无线回传节点可以为EPS网络中的无线回传节点，示例性的，EPS网络中的无线回传节点可以称为中继节点(relay node，简称RN)。
随着虚拟现实(virtual reality，简称VR)、增强现实(augmented reality，简称AR)以及物联网等技术的发展，未来网络中将会有越来越多的终端，网络数据的使用量也会不断攀升。为了配合越来越多的终端以及市场极速增长的网络数据使用量，目前对5G网络的容量提出了更高的要求。在热点区域，为满足5G网络的超高容量需求，利用高频小站组网愈发流行。高频载波传播特性较差，受遮挡衰减严重，覆盖范围不广，故而在热点区域需要大量密集部署小站。这些小站可以为IAB节点。
为了设计灵活便利的接入和回传方案，IAB场景中的接入链路(access link，简称AL)和回传链路(backhaul link，简称BL)均采用无线传输方案。
在包含IAB节点的网络(以下简称IAB网络)中，IAB节点可以为终端提供无线接入服务，并通过无线回传链路连接到宿主节点(donor node)传输用户的业务数据。示例性的，宿主节点可以为宿主基站。宿主节点在5G网络中可以简称为IAB宿主(IAB donor)或DgNB(即donor gNodeB)。宿主节点可以是一个完整的实体，还可以是集中式单元(centralized unit，简称CU)(本文中简称为宿主CU(Donor-CU)，也可以简称为CU)和分布式单元(distributed unit，简称DU)(本文中简称为宿主DU(Donor-DU))分离的形态，即宿主节点由Donor-CU和Donor-DU组成。本申请实施例中以及附图中均以宿主节点由Donor-CU和Donor-DU组成为例对本申请实施例提供的方法作示例性说明。
其中，Donor-CU还可以是用户面(User plane，简称UP)(本文中简称为CU-UP)和控制面(Control plane，简称CP)(本文中简称为CU-CP)分离的形态，即Donor-CU由CU-CP和CU-UP组成。
IAB节点经宿主节点通过有线链路连接到核心网。例如，在独立组网的5G网络架构下，IAB节点经宿主节点通过有线链路连接到5G网络的核心网(5G core，简称5GC)。在非独立组网的5G网络架构下，IAB节点在控制面经演进型基站(evolved NodeB，简称eNB)连接到演进分组核心网(evolved packet core，简称EPC)，在用户面经宿主节点以及eNB连接到EPC。
为了保证业务传输的可靠性，IAB网络支持多跳IAB节点和多连接IAB节点组网。因此，在终端和宿主节点之间可能存在多条传输路径。在一条传输路径上，IAB节点之间，以及IAB节点和为IAB节点服务的宿主节点有确定的层级关系，每个IAB节点将为其提供回传服务的节点视为父节点。相应地，每个IAB节点可视为其父节点的子节点。
示例性的，参见图1，IAB节点1的父节点为宿主节点，IAB节点1又为IAB节点2和IAB节点3的父节点，IAB节点2和IAB节点3均为IAB节点4的父节点，IAB节点5的父节点为IAB节点3。终端的上行数据包可以经一个或多个IAB节点传输至宿主节点后，再由宿主节点发送至移动网关设备(例如5G网络中的用户面功能(user plane function，简称UPF)网元)，下行数据包将由宿主节点从移动网关设备处接收后，再经一个或多个IAB节点发送至终端。终端1和宿主节点之间数据包的传输有两条可用的传输路径，分别为：终端1→IAB节点4→IAB节点3→IAB节点1→宿主节点，终端1→IAB节点4→IAB节点2→IAB节点1→宿主节点。终端2和宿主节点之间数据包的传输有三条可用的传输路径，分别为：终端2→IAB节点4→IAB节点3→IAB节点1→宿主节点，终端2→IAB节点4→IAB节点2→IAB节点1→宿主节点，终端2→IAB节点5→IAB节点2→IAB节点1→宿主节点。
可以理解的是，在IAB网络中，终端和宿主节点之间的一条传输路径上，可以包含一个或多个IAB节点。每个IAB节点需要维护面向父节点的无线回传链路，还需要维护和子节点的无线链路。若一个IAB节点是终端接入的节点，该IAB节点和子节点(即终端)之间是无线接入链路。若一个IAB节点是为其他IAB节点提供回传服务的节点，该IAB节点和子节点(即其他IAB节点)之间是无线回传链路。示例性的，参见图1，在传输路径“终端1→IAB节点4→IAB节点3→IAB节点1→宿主节点”中。终端1通过无线接入链路接入IAB节点4，IAB节点4通过无线回传链路接入IAB节点3，IAB节点3通过无线回传链路接入IAB节点1，IAB节点1通过无线回传链路接入宿主节点。
示例性的，IAB节点可以是用户驻地设备(customer premises equipment，简称CPE)、 家庭网关(residential gateway，简称RG)等设备。该情况下，本申请实施例提供的方法还可以应用于家庭连接(home access)的场景中。
上述IAB组网场景仅仅是示例性的，在多跳和多连接结合的IAB场景中，IAB组网场景还有更多其他的可能性，例如，宿主节点和另一宿主节点下的IAB节点组成双连接为终端服务等，此处不再一一列举。
为了使得本申请实施例更加的清楚，以下对与本申请实施例相关的部分内容以及概念在此处作统一介绍。
1、链路、节点的上一跳节点、节点的下一跳节点、节点的入口链路(ingress link)、节点的出口链路(egress link)
链路：是指一条传输路径中的两个相邻节点之间的路径。
节点的上一跳节点：是指在包含该节点的传输路径中的、在该节点之前最后一个接收到数据包的节点。节点的上一跳节点也可以称为数据包的上一跳节点。
节点的下一跳节点：是指在包含该节点的传输路径中的、在该节点之后第一个接收到数据包的节点。节点的下一跳节点也可以称为数据包的下一跳节点。
节点的入口链路：是指该节点与该节点的上一跳节点之间的链路，也可以称为节点的上一跳链路。
节点的出口链路：是指该节点与该节点的下一跳节点之间的链路，也可以称为节点的下一跳链路。
2、接入IAB节点、中间IAB节点
本申请实施例中的接入IAB节点是指终端接入的IAB节点，中间IAB节点是指为其他IAB节点(例如，接入IAB节点或其他中间IAB节点)提供无线回传服务的IAB节点。
示例性的，参见图1，在传输路径“终端1→IAB节点4→IAB节点3→IAB节点1→宿主节点”中，IAB节点4为接入IAB节点，IAB节点3和IAB节点1为中间IAB节点。IAB节点3为IAB节点4提供回传服务，IAB节点1为IAB节点3提供回传服务。
需要说明的是，一个IAB节点针对接入该IAB节点的终端而言，是接入IAB节点。针对接入其他IAB节点的终端而言，是中间IAB节点。因此，一个IAB节点具体是接入IAB节点还是中间IAB节点，并不是固定的，需要根据具体的应用场景确定。
3、IAB节点的组成
IAB节点可以具有移动终端(mobile terminal，简称MT)的角色以及DU的角色。当IAB节点面向其父节点时，可以被看做是终端。此时，IAB节点扮演MT的角色。当IAB节点面向其子节点(子节点可能是终端或另一IAB节点的终端部分)时，可以被看做是网络设备。此时，IAB节点扮演DU的角色。因此，可以认为IAB节点由MT部分和DU部分组成。一个IAB节点可以通过MT部分与该IAB节点的至少一个父节点之间建立回传连接。一个IAB节点的DU部分可以为终端或其他IAB节点的MT部分提供接入服务。
示例性的，参见图2，终端通过IAB节点2和IAB节点1连接到宿主节点。其中，IAB节点1和IAB节点2均包括DU部分和MT部分。IAB节点2的DU部分为终端提供接入服务。IAB节点1的DU部分为IAB节点2的MT部分提供接入服务。Donor-DU为IAB节点1的MT部分提供接入服务。
4、中间IAB节点、接入IAB节点、Donor-DU、Donor-CU以及终端的协议栈架构
中间IAB节点在用户面和控制面的协议栈相同。其中，中间IAB节点的MT部分和DU部分可以不共用Adapt层，例如图3中的(a)。中间IAB节点的MT部分和DU部分也可以共用Adapt层，例如图3中的(b)。
接入IAB节点在用户面和控制面的协议栈不同，可分别参见图3中的(c)和图3中的(d)。
示例性的，基于图3所示的示例，各个节点的用户面协议栈架构可参见图4中的(a)或图5中的(a)，各个节点的控制面协议栈架构可参见图4中的(b)或图5中的(b)。其中，图4中以中间IAB节点的MT部分和DU部分不共用Adapt层为例进行绘制。图5中以中间IAB节点的MT部分和DU部分共用Adapt层为例进行绘制。
其中，图3至图5中各个协议层的含义为：分组数据汇聚协议(packet data convergence protocol，简称PDCP)层、通用分组无线服务隧道协议用户面(general packet radio service tunneling protocol user plane，简称GTP-U)层、用户数据报协议(user datagram protocol，简称UDP)层、网络互连协议(internet protocol，简称IP)层、L2层(layer 2)、L1层(layer1)、无线链路控制(radio link control，简称RLC)层、媒介接入控制(medium access control，简称MAC)层、物理(physical，简称PHY)层、无线资源控制(radio resource control，简称RRC)层、F1应用协议(F1 application protocol，简称F1AP)层、流控制传输协议(stream control transmission protocol，简称SCTP)层。其中，L2层为链路层，示例性的，L2层可以为开放式通信系统互联(open systems interconnection，简称OSI)参考模型中的数据链路层。L1层可以为物理层，示例性的，L1层可以为OSI参考模型中的物理层。
需要说明的是，图4和图5中均以宿主节点由Donor-DU和Donor-CU组成为例进行绘制。因此，图4和图5中示出了Donor-DU和Donor-CU的协议层。若宿主节点是功能完整的实体，则宿主节点保留Donor-DU和Donor-CU对外部节点接口的协议栈即可，无需Donor-DU和Donor-CU之间内部接口上的协议层。
另外，需要说明的是，不论是控制面的协议栈架构还是用户面的协议栈架构，在Donor-DU为Donor-CU和IAB节点之间的F1接口的代理(proxy)节点时，Donor-DU中面向IAB节点的协议栈架构中，在IP层之上，还可以包括与接入IAB节点中的DU部分的协议栈架构中的UDP层和GTP-U层分别对等的UDP层和GTP-U层。
5、F1接口的协议层、无线回传接口的协议层
其中，F1接口是指IAB节点(例如IAB节点的DU部分)和宿主节点(或Donor-CU或Donor-DU)之间的逻辑接口，F1接口也可以称为F1*接口，支持用户面以及控制面。F1接口的协议层是指在F1接口上的通信协议层。
示例性的，F1接口的用户面协议层可以包括IP层、UDP层和GTP-U层中的一个或多个。可选的，F1接口的用户面协议层还包括PDCP层和/或IP安全(IP Security，简称IPsec)层。
示例性的，F1接口的控制面协议层可以包括IP层、F1AP层和SCTP层中的一个或多个。可选的，F1接口的控制面协议层还包括PDCP层、IPsec层和数据报文传输层安全(datagram transport layer security，简称DTLS)层中的一个或多个。
无线回传接口是指IAB节点之间或IAB节点与宿主节点(或Donor-DU)之间的逻辑接口。无线回传接口的协议层是指在无线回传接口上的通信协议层。无线回传接口的协议层包括以下协议层中的一个或多个：Adapt层、RLC层、MAC层和PHY层。
示例性的，IAB节点在F1接口的用户面协议层包括GTP-U层、UDP层和IP层。在一种 情况下，参见图4中的(a)和图5中的(a)，IAB节点的GTP-U层和UDP层与Donor-CU对等，IP层与Donor-DU对等。另一种情况下，Donor-DU为Donor-CU和IAB节点之间的F1接口的代理节点，IAB节点的GTP-U层、UDP层和IP层与Donor-DU对等。需要说明的是，若考虑对F1接口进行安全保护，则F1接口的用户面协议层还可以包含IPsec层和/或PDCP层。在一种可能的实现方式中，IPsec层或PDCP层位于IP层之上GTP-U层之下。
示例性的，IAB节点在F1接口的控制面协议层包括F1AP层、SCTP层和IP层。在一种情况下，参见图4中的(b)和图5中的(b)，IAB节点的F1AP层和SCTP层与Donor-CU对等，IP层与Donor-DU对等。另一种情况下，Donor-DU为Donor-CU和IAB节点之间的F1接口的代理节点，IAB节点的F1AP层、SCTP层和IP层与Donor-DU对等。需要说明的是，若考虑对F1接口进行安全保护，则F1接口的控制面协议层还可以包含IPsec层、PDCP层和DTLS层中的一个或多个。在一种可能的实现方式中，IPsec层、PDCP层或DTLS层位于IP层之上F1AP层之下。
可以理解的是，当在F1接口的协议层中引入安全保护的协议层，则图3至图5中的部分节点的协议栈架构会发生变化，具体可参考文字进行理解。本申请实施例图3至图5中所示的IAB网络中的各个节点的协议栈架构仅仅是一种示例，本申请实施例提供的方法并不依赖于该示例，而是通过该示例使得本申请实施例提供的方法更加的容易理解。
6、发送侧协议栈、接收侧协议栈
本申请实施例中的一个节点的发送侧协议栈是指该节点中的面向下一跳节点的协议栈，一个节点的接收侧协议栈是指该节点中的面向上一跳节点的协议栈。
示例性的，在图4和图5所示的协议栈架构中，针对上行传输，接入IAB节点的DU部分中的面向终端的协议栈为接收侧协议栈，面向宿主节点或Donor-CU的协议栈为发送侧协议栈，接入IAB节点的MT部分的协议栈为发送侧协议栈，中间IAB节点的DU部分的协议栈为接收侧协议栈，中间IAB节点的MT部分的协议栈为发送侧协议栈，Donor-DU中的面向IAB节点的协议栈为接收侧协议栈，Donor-DU中的面向Donor-CU的协议栈为发送侧协议栈。针对下行传输，接入IAB节点的DU部分中的面向终端的协议栈为发送侧协议栈，面向宿主节点或Donor-CU的协议栈为接收侧协议栈，接入IAB节点的MT部分的协议栈为接收侧协议栈，中间IAB节点的DU部分的协议栈为发送侧协议栈，中间IAB节点的MT部分的协议栈为接收侧协议栈，Donor-DU中的面向IAB节点的协议栈为发送侧协议栈，Donor-DU中的面向Donor-CU的协议栈为接收侧协议栈。
需要说明的是，针对共用Adapt层的中间IAB节点，接收侧协议栈中包括Adapt层实体，发送侧协议栈中也包括Adapt层实体。
以下将发送侧协议栈简称为发送侧，将接收侧协议栈简称为接收侧。
7、上层协议层、下层协议层
本申请实施例中，将协议层的上下关系定义为：在一个节点发送数据的过程中，先对数据包进行处理的协议层在后对数据包进行处理的协议层之上，即先对数据包进行处理的协议层可以认为是后对数据包进行处理的协议层的上层协议层；或者，在一个节点接收数据的过程中，先对数据包进行处理的协议层在后对数据包进行处理的协议层之下，即先对数据包进行处理的协议层可以认为是后对数据包进行处理的协议层的下层协议层。
示例性的，参见图3，在中间IAB节点的协议栈中，Adapt层为RLC层、MAC层和PHY 层的上层协议层，RLC层、MAC层和PHY层为Adapt层的下层协议层。另外，需要说明的是，在本申请实施例中，针对一个节点，发送侧协议栈可以认为是接收侧协议栈的下层协议栈。例如，针对中间IAB节点的上行数据包，MT部分(即发送侧)的Adapt层为DU部分(即接收侧)的Adapt层的下层协议层。
需要说明的是，针对接入IAB节点的下行数据包，由于接入IAB节点的MT部分的协议层和DU部分中的面向宿主节点或Donor-CU的协议栈均为接收侧协议栈，因此，MT部分的Adapt层为DU部分的IP层的下层协议层。针对接入IAB节点的上行数据包，由于接入IAB节点的MT部分的协议层和DU部分中的面向宿主节点或Donor-CU的协议栈均为发送侧协议栈，因此，MT部分的Adapt层为DU部分的IP层的下层协议层。
8、RLC信道(RLC channel)、RLC承载(RLC bearer)、逻辑信道(logical channel，简称LCH)
RLC信道是指RLC层和上层协议层(例如，Adapt层)之间的信道。逻辑信道是指RLC层和下层协议层(例如，MAC层)之间的信道。逻辑信道也可以称为MAC逻辑信道。RLC承载是指RLC层实体和MAC逻辑信道。
目前，终端的无线承载(radio bearer，简称RB)的配置对应有高层(例如，PDCP层)部分和低层(例如，RLC层和MAC层)部分的配置，RLC承载的配置是指RB对应的低层部分的配置，具体包括RLC层实体和MAC逻辑信道的配置。本文中，IAB节点在无线回传链路上的RLC承载是指RLC层和MAC逻辑信道部分，在无线回传链路上的RLC信道可以是指RLC层和PDCP层之间的信道，也可以是指RLC层和Adapt层之间的信道，具体视RLC层的上层协议层而定。下文中以RLC信道为RLC层和Adapt层之间的信道为例进行说明。IAB节点在无线回传链路上的RLC信道与RLC层实体一一对应，RLC信道也与RLC承载一一对应，具体可参见图7进行理解。
其中，终端的RB可以为数据无线承载(data radio bearer，简称DRB)，也可以为信令无线承载(signalling radio bearer，简称SRB)。
为了方便描述，下文中将RLC信道、RLC承载和逻辑信道统称为业务区分通道。也就是说，下文中的业务区分通道可以替换为RLC信道、RLC承载和逻辑信道中的任意一个。
9、业务数据单元(service data unit，简称SDU)、协议数据单元(protocol data unit，简称PDU)
在通信网络中，不同节点之间的对等协议层实体间交换的数据单元为PDU。一个协议层将该协议层的PDU通过由相邻的下层协议层提供给该协议层的服务接入点(service access point，简称SAP)(也可以称为服务接口)传递给下层协议层，并由下层协议层间接完成该协议层的PDU的交换，该协议层的PDU是作为下层协议层的SDU的。
示例性的，针对某个协议层，如果该协议层接收到的数据包中不包括该协议层的协议层头，则该数据包可以认为是该协议层的SDU。如果该协议层接收到的数据包中包括该协议层的协议层头，则该数据包可以认为是该协议层的PDU。例如，针对Adapt层，如果Adapt层接收到的数据包中不包括Adapt层头，则该数据包可以认为是Adapt层的SDU，如果Adapt层接收到的数据包中包括Adapt层头，则该数据包可以认为是Adapt层的PDU。
其中，Adapt层的PDU可以分为Adapt层的控制PDU(control PDU)和Adapt层的数据PDU(data PDU)。Adapt层的数据PDU中，Adapt层载荷中包括用户面数据和/或控制面信令。 Adapt层的控制PDU中的Adapt层载荷中包括Adapt层反馈信息，例如，流控反馈信息、头压缩反馈信息或其他由Adapt层产生的反馈信息或控制信息。其中，包含头压缩反馈信息的Adapt层控制PDU可以称为头压缩的状态报告。包含流控反馈信息的Adapt层控制PDU可以称为流控的状态报告。
10、Adapt层的数据包的组成
Adapt层的数据包可以有两种类型，分别记为第一类型数据包和第二类型数据包。
其中，参见图6，第一类型数据包是指包括Adapt层头和Adapt层载荷的数据包。第二类型数据包是指包括Adapt层载荷的数据包。第一类型数据包也可以称为Adapt PDU。Adapt层载荷可以为Adapt SDU或Adapt层生成的控制信息或反馈信息等。
Adapt层头中，可以包含路由信息(也可以称为Adapt层路由相关信息)，和/或，数据包所属的终端的RB相关信息，还可以包含Adapt PDU类型指示信息，Adapt PDU类型指示信息用于指示Adapt PDU的类型是控制PDU还是数据PDU。
路由信息可以为：Adapt层路由的目的节点的标识，或者，Adapt层路由的目的节点服务的小区的标识，或者，Adapt层传输路径的标识。其中，Adapt层路由的目的节点是指Adapt层路由的最后一个节点。
针对数据PDU，下行传输中，Adapt层路由的目的节点可以是接入IAB节点。上行传输中，Adapt层路由的目的节点可以是Donor-DU。
针对控制PDU，每个IAB节点都可能是Adapt层路由的目的节点。
数据包所属的终端的RB相关信息(也可以称为UE承载信息)可以为：终端的标识+终端的RB的标识(例如，UE bearer specific ID)，或者，可以是指向终端的RB的“GTP TEID+IP地址”。其中，GTP TEID是指GTP隧道的隧道端点标识(tunnel endpoint identifier，简称TEID)。
11、Adapt层
Adapt层具备以下能力中的至少一种：为数据包添加能被无线回传节点识别出的路由信息(Routing info)、基于所述能被无线回传节点识别出的路由信息执行路由选择、为数据包添加能被无线回传节点识别出的与服务质量(quality of service，简称QoS)需求相关的标识信息、为数据包执行在包含无线回传节点的多段链路上的QoS映射、为数据包添加数据包类型指示信息、向具有流量控制能力的节点发送流控反馈信息。需要说明的是，具备这些能力的协议层的名称不一定为Adapt层，本领域技术人员可以理解，只要具备这些能力的协议层均可以理解为本申请实施例中的Adapt层。
其中，所述能被无线回传节点识别出的路由信息可以是终端的标识，终端接入的IAB节点的标识，宿主节点的标识，Donor-DU的标识，Donor-CU的标识，传输路径的标识等信息中的一种或多种。
所述多段链路上的QoS映射可以为：在无线回传链路中基于数据包携带的终端的RB的标识，执行从终端的RB到无线回传链路上的RLC承载或RLC信道或逻辑信道的映射；基于入口链路和出口链路的RB、RLC承载、RLC信道和逻辑信道中的任意两个或更多个之间的对应关系，执行从入口链路的RB或RLC承载或RLC信道或逻辑信道，到出口链路的RB或RLC承载或RLC信道或逻辑信道的映射。
所述数据包类型指示信息可以用于指示Adapt层中封装的内容包含的是以下类型中的 任一种或多种：终端的用户面数据、终端的RRC消息、IAB节点的RRC消息、IAB节点与宿主节点(或Donor-CU或CU-CP)之间接口上的控制层应用消息(例如F1AP消息)、IAB节点生成的流控反馈消息、IAB节点生成的头压缩反馈消息、Adapt层的数据PDU、Adapt层的控制PDU等。
与QoS需求相关的标识信息可以为终端的QoS流的标识(Qos flow identifier，简称QFI)，终端的RB的标识，差分服务代码点(differentiated services code point，简称DSCP)，互联网协议版本6(internet protocol version 6，简称IPv6)的IP数据包的包头中的流标签(flow label)等。
示例性的，具有流量控制能力的节点可以为宿主节点、Donor-DU、Donor-CU、IAB节点的父节点等为IAB节点提供回传服务的节点。流控反馈信息的内容可包含如下信息中的一种或多种：IAB节点的缓存状态、负载程度，包含IAB节点的某段链路的状态(如链路阻塞(blockage)或链路恢复(resume)或链路质量信息等)，包含IAB节点的某段链路的带宽、传输时延，IAB节点丢失的数据包序号，IAB节点已经成功向终端或其子节点发送的数据包序号等。
另外，一种可能的情况，Adapt层的功能还可以通过在层2包含的任意一个层(例如，RLC层、MAC层、PDCP层等)或任意多个层的功能上扩展，无需额外的协议层。
12、Adapt层实体、RLC层实体
需要说明的是，一个Adapt层可以包括多个Adapt层实体，一个RLC层也可以包括多个RLC层实体。
其中，Adapt层包含的Adapt层实体的个数可以为以下情况1至情况3中的任意一种情况：
情况1、Adapt层包含一个Adapt层实体。
该情况下，参见图7，Adapt层实体与N(N为大于0的整数)个RLC层实体对应，Adapt层实体与N个RLC层实体之间存在N个RLC信道，N个RLC信道与N个RLC层实体一一对应。
针对中间IAB节点，若中间IAB节点的MT部分和DU部分共用Adapt层时，参见图8，N个RLC层实体中一部分RLC层实体为中间IAB节点的MT部分的RLC层包含的RLC层实体，另一部分RLC层实体为中间IAB节点的DU部分的RLC层包含的RLC层实体。
情况2、一个节点(记为节点A，示例性的，节点A可以为IAB节点、宿主节点或Donor-DU)的Adapt层包含M(M为大于0的整数)个Adapt层实体，M个Adapt层实体与M个节点一一对应，M个节点为与节点A通信的一个或多个节点。
其中，本申请实施例中的与网络节点(例如，节点A)通信的节点为网络节点的发送侧所对应的接收侧所在的节点。
该情况下，一个Adapt层实体对应一个节点。一个Adapt层实体与RLC层实体之间的对应关系可参见图7。
情况3、Adapt层包含N个Adapt层实体，N个Adapt层实体与N个RLC层实体一一对应。
该情况下，参见图9，一个Adapt层实体与对应的RLC层实体之间为一个RLC信道。在情况3下，一个RLC信道或一个逻辑信道或一个RLC承载对应一个Adapt层实体。
13、路由选择、承载映射
本申请实施例中的路由选择用于为数据包选择下一跳节点。
本申请实施例中的承载映射也可以称为QoS映射。承载映射用于选择发送数据包的RLC承载或RLC信道或逻辑信道。
14、头压缩、解头压缩
参见图4中的(a)和图5中的(a)，发往终端的下行数据包(例如发给终端的用户面PDCP PDU)，会经Donor-CU的GTP-U层、UDP层和IP层的封装处理后，得到IP数据包，经过Donor-CU和Donor-DU之间的有线链路传输，然后由Donor-DU在无线回传链路上发送至终端接入的IAB节点(即IAB节点2)。在IAB节点2处，数据包中的IP头、UDP头以及GTP-U头才会被剥除，然后IAB节点2会将终端的PDCP PDU通过无线接入链路发送给终端。由此可见，在无线回传链路上传输的数据包会有较重的头开销。为了降低数据包在无线回传链路上传输的头开销，本申请实施例中网络节点可以对终端的数据包进行头压缩和解头压缩。通过头压缩和解头压缩，可以降低数据包在无线回传链路传输过程中的头开销，减少空口资源消耗。
头压缩是指对数据包(例如，IP数据包)的协议层头进行压缩。解头压缩是指对压缩后的协议层头解压缩。示例性的，头压缩时所压缩的头可以为Adapt层头、IP层头、UDP层头、SCTP层头和GTP-U层头中的一个或多个。
在本申请实施例中，头压缩的方式可以有两种，分别为端到端头压缩和逐跳头压缩，以下分别对这两种头压缩方式进行介绍。
端到端头压缩：一种仅在接入IAB节点的发送侧或宿主节点(或Donor-DU)的发送侧进行头压缩的头压缩方式。当在接入IAB节点的发送侧进行头压缩时，解压缩的节点为宿主节点(或Donor-DU)的接收侧。当在宿主节点(或Donor-DU)的发送侧进行头压缩时，解压缩的节点为接入IAB节点的接收侧。
逐跳头压缩：一种在宿主节点(或Donor-DU)和每个IAB节点的发送侧都进行头压缩的头压缩方式。当在一个节点的发送侧进行头压缩时，解压缩的节点为该节点的下一跳节点的接收侧。
需要说明的是，若头压缩方式为端到端头压缩，则作为无线回传链路接收节点的网络节点为接入IAB节点或宿主节点或Donor-DU时，执行解头压缩的操作。若头压缩方式为逐跳头压缩，则每个作为无线回传链路接收节点的网络节点执行解头压缩的操作。
15、头压缩的状态报告的格式
示例性的，参见图10。图10示出了一种头压缩的状态报告的格式，其中的各个字段的含义为：
数据/控制(data/control，简称D/C)：该字段用于标识Adapt PDU(即头压缩的状态报告)的PDU类型，为数据PDU还是控制PDU。例如，该字段可以有1个bit，该bit取值为0表示Adapt PDU为控制PDU，该bit取值为1表示Adapt PDU为数据PDU。
控制信息类型：控制信息类型用于指示状态报告的类型，状态报告的类型可以为头压缩的状态报告，流控的状态报告等。当IAB网络既支持端到端头压缩，又支持逐跳的头压缩时，该字段还可以进一步包含头压缩方式指示信息，该指示信息用于指示头压缩的状态报告对应的头压缩方式。示例性的，一种可能的实现方式，控制信息类型至少包括两个bit，一个bit用于指示控制信息类型，另一个bit用于指示头压缩方式。另一种可能的实现方式，控制信息类型包括的bit至少包括三个取值，一个取值表明状态报告为流控的状态报告， 一个取值表明状态报告为头压缩方式为逐跳头压缩的头压缩的状态报告，另一个取值表明状态报告为头压缩方式为端到端头压缩的头压缩的状态报告。
路由信息：该字段用于表明Adapt PDU的路由信息。例如，路由信息可以包含接收该Adapt PDU的目的节点的标识，还可以包含发送该Adapt PDU的源节点的标识。对于Adapt控制PDU，该字段为可选字段，例如，在逐跳的头压缩方式中，携带头压缩反馈信息的Adapt控制PDU可以无需该字段。
终端的RB的信息：该字段为指向某个特定终端的某个RB的标识，用于表明Adapt PDU所对应的终端的RB。该字段为可选字段，例如，当Adapt层的头压缩配置是特定于一个IAB节点，而非终端的RB的情况下，携带头压缩反馈信息的Adapt控制PDU可以无需该字段。
预留(reserved)字段：该字段为保留比特，可用于Adapt层头信息的字节对齐。
头压缩反馈信息：该字段内容即具体的头压缩反馈内容(例如，鲁棒头压缩(robust header compression，简称ROHC)反馈)。
为了保证数据包正确的在无线回传链路上进行传输，本申请实施例提供了实施例一、实施例二和实施例三所示的通信方法，以下分别对实施例一、实施例二和实施例三进行描述。
实施例一
该实施例中，网络节点可以为IAB节点或宿主节点或Donor-DU。
本申请实施例提供了一种通信方法，如图11所示，该方法包括：
1101、网络节点的第一实体接收从下层协议层的协议层实体递交的数据包，第一实体为Adapt层实体。
其中，数据包为第一类型数据包，第一类型数据包为包括Adapt层头和Adapt层载荷的数据包。也就是说，网络节点的第一实体接收到的数据包为Adapt PDU。
其中，网络节点的第一实体位于接收侧。网络节点的接收侧的Adapt层可以包括一个或多个Adapt层实体，网络节点的第一实体可以为其中的任意一个Adapt层实体。比较特殊的是，若网络节点为共用Adapt层的中间IAB节点，则第一实体为位于中间IAB节点的发送侧和接收侧共用的Adapt层实体。
示例性的，Adapt层的下层协议层可以为RLC层，则下层协议层的协议层实体可以为RLC层实体。
1102、网络节点的第一实体判断网络节点是否为数据包在Adapt层路由的目的节点。
1103、网络节点的第一实体根据判断结果处理数据包。
实施例一提供的方法，由于网络节点是否为Adapt层路由的目的节点会直接影响到后续数据包的处理过程。因此，实施例一提供的方法，网络节点根据自身是否为数据包在Adapt层路由的目的节点的判断结果处理数据包，可以正确的处理数据包，防止数据包的处理过程出错。
可选的，步骤1102具体实现时包括：网络节点的第一实体根据数据包中的Adapt层头中的路由信息、数据包中的Adapt层头中是否包含路由信息，以及数据包是否为控制PDU中的一种或多种判断网络节点是否为数据包在Adapt层路由的目的节点。
示例性的，步骤1102可以通过以下方式一至方式三中的任意一种方式实现。
方式一、网络节点的第一实体根据数据包中的Adapt层头中的路由信息判断网络节点是否为数据包在Adapt层路由的目的节点。
方式一的第一种可能的实现方式，路由信息为Adapt层路由的目的节点的标识。该情况下，若数据包的Adapt层头中携带的目的节点的标识为网络节点的标识，则网络节点的第一实体可确定自身为Adapt层路由的目的节点。否则，网络节点的第一实体可确定自身不是Adapt层路由的目的节点。
方式一的第二种可能的实现方式，路由信息为Adapt层路由的目的节点服务的小区的标识。该情况下，若数据包的Adapt层头中携带的小区的标识为网络节点服务的小区的标识，则网络节点的第一实体可确定自身为Adapt层路由的目的节点。否则，网络节点的第一实体可确定自身不是Adapt层路由的目的节点。
方式一的第三种可能的实现方式，路由信息为Adapt层路由的传输路径标识。该情况下，若数据包的Adapt层头携带的传输路径标识指向的传输路径中的最后一个节点为网络节点，则网络节点的第一实体可确定自身为Adapt层路由的目的节点。否则，网络节点的第一实体可确定自身不是Adapt层路由的目的节点。
方式一的第四种可能的实现方式，路由信息为终端的标识。该情况下，若数据包的Adapt层头中携带的终端的标识为网络节点服务的终端的标识，则网络节点的第一实体可确定自身为Adapt层路由的目的节点。否则，网络节点的第一实体可确定自身不是Adapt层路由的目的节点。
方式二、网络节点的第一实体根据数据包中的Adapt层头中是否包含路由信息判断网络节点是否为数据包在Adapt层路由的目的节点。
第一种情况，Adapt层路由的目的节点的上一跳节点，会移除Adapt层头中的路由信息。该情况下，若网络节点的第一实体接收到下层协议层的协议层实体递交的Adapt PDU时，若Adapt PDU的Adapt层头中不包括路由信息字段，则网络节点的第一实体判断自身为Adapt PDU在Adapt层路由的目的节点，否则，网络节点的第一实体判断自身不是Adapt PDU在Adapt层路由的目的节点。
第二种情况，对于树形(spanning tree)拓扑的IAB网络，即每个IAB节点只有一个父节点的IAB网络，上行Adapt PDU的Adapt层头中可以不携带路由信息，每个IAB节点向唯一的父节点转发上行Adapt PDU即可，即采用一种缺省(default)路由的方式。
在第二种情况下，若网络节点为IAB节点，网络节点的Adapt层接收到下层协议层的协议层实体递交的上行Adapt PDU时，若上行Adapt PDU的Adapt层头中不包括路由信息字段，则判断自身不是Adapt层路由的目的节点。若网络节点为宿主节点或Donor-DU，网络节点的Adapt层接收到下层协议层的协议层实体递交的上行Adapt PDU时，若上行Adapt PDU的Adapt层头中不包括路由信息字段，则判断自身是Adapt层路由的目的节点。
方式三、网络节点的第一实体根据数据包是否为控制PDU判断网络节点是否为数据包在Adapt层路由的目的节点。
需要说明的是，IAB网络中支持逐跳的Adapt层状态报告(例如，下行流控的状态报告，头压缩的状态报告等)反馈的场景，该情况下，每个接收Adapt层状态报告的IAB节点都是该Adapt层状态报告的目的节点。由于Adapt层状态报告为控制PDU，这类控制PDU可以不携带路由信息。此时，网络节点的第一实体还可以根据Adapt PDU的PDU类型来 判断网络节点是否为Adapt PDU在Adapt层路由的目的节点。当Adapt PDU为控制PDU时，网络节点的第一实体判断自身为Adapt PDU在Adapt层路由的目的节点。否则，网络节点的第一实体再根据前述方式一或方式二判断自身是否为Adapt层路由的目的节点。
其中，Adapt PDU的Adapt层头中可以包含PDU类型指示标识，该标识用于指示Adapt PDU类型是数据PDU还是控制PDU。该情况下，网络节点的第一实体可以根据该标识确定Adapt PDU是否为控制PDU。
其中，步骤1102的判断结果有两种，一种判断结果为是(即网络节点为数据包在Adapt层路由的目的节点)，另一种判断结果为否(即网络节点不是数据包在Adapt层路由的目的节点)。针对不同的判断结果，步骤1103的实现方式也不同，以下分别进行介绍。
情况一、判断结果为是
当判断结果为是时，参见图12，步骤1103可以通过以下实现方式1至实现方式4中的任意一种方式实现。具体采用哪种实现方式可以根据实现方式适用的场景确定。
实现方式1、网络节点的第一实体将数据包中的Adapt层载荷向第二实体递交，第二实体为F1接口的协议层的协议层实体或Adapt层的上层协议层的协议层实体。
实现方式1的适用场景：IAB网络中不对数据包进行头压缩。
实现方式1在具体实现时，网络节点的第一实体可以将接收到的数据包的Adapt层头移除，得到Adapt层载荷，再将Adapt层载荷向第二实体递交。
实现方式2、网络节点的第一实体对数据包中的Adapt层载荷进行解头压缩，并将解头压缩后的Adapt层载荷向第二实体递交。
实现方式2的适用场景：IAB网络中对数据包中的Adapt层载荷进行了头压缩。
实现方式2在具体实现时，网络节点的第一实体可以将接收到的数据包的Adapt层头移除，得到Adapt层载荷，对Adapt层载荷进行解头压缩，再将解头压缩后的Adapt层载荷向第二实体递交。
实现方式3、网络节点的第一实体对数据包进行解头压缩，并将解头压缩后的数据包中的Adapt层载荷向第二实体递交。
实现方式3的适用场景：IAB网络中对数据包进行头压缩，所压缩的协议层头中包括Adapt层头。
实现方式3在具体实现时，网络节点的第一实体可以将接收到的数据包进行解头压缩，再移除解头压缩后的数据包的Adapt层头，得到Adapt层载荷，将Adapt层载荷向第二实体递交。
在实现方式1至实现方式3中，网络节点可以为接入IAB节点或宿主节点或Donor-DU。该情况下，示例性的，第二实体可以为IP层的协议层实体。
在实现方式1至实现方式3中，数据包为数据PDU。
实现方式4、网络节点的第一实体将数据包存储到Adapt层的缓存中。
实现方式4的适用场景：任何场景。
在实现方式4中，数据包为数据PDU或控制PDU。
当数据包为数据PDU时，网络节点的第一实体将数据包存储到Adapt层的缓存中之后，网络节点还可以执行实现方式1至实现方式3中的任意一种实现方式中的动作。此时，网络节点可以为接入IAB节点或宿主节点或Donor-DU。
当数据包为控制PDU时，网络节点的第一实体将数据包存储到Adapt层的缓存中之后，自行处理数据包中的Adapt层载荷。此时，网络节点可以为中间IAB节点。
情况二、判断结果为否
在情况二下，数据包为数据PDU或控制PDU。网络节点为中间IAB节点。参见图12，步骤1103可以通过以下实现方式5至实现方式10中的任意一种方式实现。具体采用哪种实现方式可以根据实现方式适用的场景确定。
实现方式5、网络节点的第一实体将数据包向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或Adapt层的下层协议层的协议层实体。
实现方式5的适用场景：IAB网络中不对数据包进行头压缩，或者，头压缩方式为端到端头压缩。
实现方式5中，第三实体位于网络节点的发送侧。若网络节点为共用Adapt层的中间IAB节点，则第三实体为网络节点的发送侧的Adapt层实体的下层协议层(例如，RLC层实体)，若网络节点为不共用Adapt层的中间IAB节点，则第三实体为网络节点的发送侧的Adapt层实体。
实现方式6、网络节点的第一实体将数据包中的Adapt层载荷和数据包中的Adapt层头中的信息向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或Adapt层的下层协议层的协议层实体。
实现方式6的适用场景：IAB网络中不对数据包进行头压缩，或者，头压缩方式为端到端头压缩。
实现方式6在具体实现时，网络节点的第一实体可以将接收到的数据包的Adapt层头移除，得到Adapt层载荷，再将Adapt层载荷和数据包中的Adapt层头中的信息向第三实体递交。
实现方式7、网络节点的第一实体对数据包中的Adapt层载荷进行解头压缩，并将解头压缩后的Adapt层载荷和数据包中的Adapt层头中的信息向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或Adapt层的下层协议层的协议层实体。
实现方式7的适用场景：头压缩方式为逐跳头压缩，网络节点的上一跳节点对数据包中的Adapt层载荷进行了头压缩。
实现方式7在具体实现时，网络节点的第一实体可以将接收到的数据包的Adapt层头移除，得到Adapt层载荷，将Adapt层载荷进行解头压缩，再将解头压缩后的Adapt层载荷和数据包中的Adapt层头中的信息向第三实体递交。
实现方式8、网络节点的第一实体对数据包进行解头压缩，并将解头压缩后的数据包中的Adapt层载荷和解头压缩后的数据包中的Adapt层头中的信息向第三实体递交，第三实体为无线回传接口的协议层的协议层实体或Adapt层的下层协议层的协议层实体。
实现方式8的适用场景：头压缩方式为逐跳头压缩，网络节点的上一跳节点对数据包进行头压缩，所压缩的协议层头中包括Adapt层头。
实现方式8在具体实现时，网络节点的第一实体可以将接收到的数据包进行解头压缩，再将解头压缩后的数据包中的Adapt层头移除，得到Adapt层载荷，将Adapt层载荷和数据包中的Adapt层头中的信息向第三实体递交。
在实现方式6至实现方式8中，第三实体位于网络节点的发送侧。网络节点为不共用 Adapt层的中间IAB节点，第三实体为网络节点的发送侧的Adapt层实体。
在实现方式6至实现方式8中，网络节点的第一实体向第三实体递交的Adapt层头中的信息可以为Adapt层头中的全部信息，也可以为Adapt层头中的部分信息。Adapt层头中包括的信息可参见上文，在此不再赘述。
实现方式9、网络节点的第一实体先对数据包进行解头压缩(采用的解头压缩的算法对应于上一跳节点采用的头压缩的算法)，再对数据包进行头压缩(采用的头压缩的算法对应于下一跳节点采用的解头压缩的算法)，然后将头压缩后的数据包递交给第三实体。
实现方式9的适用场景：头压缩方式为逐跳头压缩，网络节点的上一跳节点对数据包进行头压缩，所压缩的协议层头中包括Adapt层头。
实现方式10、网络节点的第一实体先对数据包中的Adapt层载荷进行解头压缩(采用的解头压缩的算法对应于上一跳节点采用的头压缩的算法)，再对Adapt层载荷进行头压缩(采用的头压缩的算法对应于下一跳节点采用的解压缩的算法)，然后为头压缩后的Adapt层载荷添加Adapt层头后递交给第三实体。
实现方式10的适用场景：头压缩方式为逐跳头压缩，网络节点的上一跳节点对数据包中的Adapt层载荷进行了头压缩。
在实现方式9和实现方式10中，第三实体位于网络节点的发送侧。网络节点为共用Adapt层的中间IAB节点，第三实体为网络节点的发送侧的RLC层实体。网络节点和数据包的上一跳节点之间采用的压缩算法与网络节点和数据包的下一跳节点之间采用的压缩算法可以相同，也可以不同。通过上述多种实现方式，针对不同的场景，网络节点的第一实体可以对数据包执行不同的处理，并递交到相应的协议层，以保障IAB网络中的上行业务和下行业务的传输。
可选的，数据包的Adapt层头中包含头压缩方式指示字段，头压缩方式指示字段用于指示数据包的上一跳节点采用的头压缩方式。该情况下，网络节点的第一实体可以根据头压缩方式指示字段确定是否对数据包解头压缩。
具体的，若头压缩方式为端到端头压缩，则当网络节点为接入IAB节点或宿主节点或Donor-DU时，网络节点对数据包解头压缩。若头压缩方式为逐跳头压缩，不论网络节点为哪种节点，都对数据包解头压缩。
可选的，头压缩方式指示字段与终端(或终端的RB)对应，即该指示字段仅用于配置某个终端(或某个终端的某个RB)对应的数据包在无线回传链路的头压缩方式。该情况下，网络节点在数据包为该某个终端(或某个终端的某个RB)的数据包时，才可能对数据包进行解头压缩，具体是否解头压缩还取决于网络节点的类型和头压缩的方式。在本申请实施例中，接入IAB节点、宿主节点(或Donor-DU)和中间IAB节点可以认为是不同类型的网络节点。
可选的，头压缩方式指示字段与某个IAB节点对应，即该指示字段用于配置发送到该某个IAB节点的数据包的头压缩方式。该情况下，网络节点在数据包为发送到该某个IAB节点的数据包时，才可能对数据包进行解头压缩，具体是否解头压缩还取决于网络节点的类型和头压缩的方式。
示例性的，头压缩方式指示字段可以有两个取值。例如，0和1，其中0表示不采用头压缩，1表示采用头压缩；或者，0表示端到端头压缩方式，1表示逐跳的头压缩方式。 头压缩方式指示字段也可以有至少三个取值。例如，00，01，11，其中00表示不采用头压缩，01表示采用端到端头压缩，11表示采用逐跳的头压缩。
在网络节点的第一实体对数据包或Adapt层载荷解头压缩的情况下，为了保证头压缩端和解头压缩端的上下文状态同步，上述方法还可以包括：11)网络节点的第一实体向网络节点的上一跳节点发送头压缩的状态报告。
其中，头压缩的状态报告用于对头压缩进行状态反馈，头压缩的状态报告为Adapt层的控制PDU。头压缩的状态报告的一种格式可参见图10，也可以为其他格式。若头压缩端采用ROHC协议执行头压缩，则解头压缩端可以通过发送ROHC feedback(反馈)来保证头压缩端和解头压缩端的上下文状态同步。其中，ROHC feedback即头压缩的状态报告中的载荷。头压缩的状态报告中具体需要包含的信息可以参见ROHC协议的规定。
可选的，在步骤1102之前，实施例一提供的方法还包括：21)网络节点的第一实体判断数据包的PDU类型，数据包的PDU类型为数据PDU或控制PDU。该情况下，若数据包的PDU类型为控制PDU，网络节点的第一实体也可以不执行步骤1102和步骤1103，而直接将数据包存储到Adapt层的缓存中，并自行处理数据包中的Adapt层载荷。
步骤21)在具体实现时，网络节点的第一实体可以根据数据包的Adapt层头中携带的PDU类型指示信息确定数据包的PDU类型。示例性的，PDU类型指示信息可以携带在数据包的Adapt层头中的D/C域中。
需要说明的是，在网络节点为中间IAB节点时，中间IAB节点需要进行路由选择，以便确定数据包的下一跳节点，还需要进行承载映射，以便确定发送数据包时所采用的业务区分通道。该情况下，可选的，上述方法还包括以下方法1至方法3中的任意一种或多种方法。
方法1、网络节点的第一实体确定数据包的下一跳节点，网络节点的第一实体向第三实体递交用于指示下一跳节点的信息。
其中，用于指示下一跳节点的信息可以为下一跳节点的标识。
在方法1中，网络节点的第一实体可以通过路由选择确定数据包的下一跳节点。在进行路由选择时，网络节点的第一实体可以根据数据包中的Adapt层头中的路由信息，以及预先设置的路由规则，选择合适的下一跳节点。其中，路由规则可以是宿主节点或Donor-CU预先配置在网络节点中，也可以由网络节点自行生成。
示例性的，Adapt层头中的路由信息可以为Adapt层路由的目的节点的标识，预先设置的路由规则可以为配置在网络节点中的转发表，转发表中至少包含该目的节点的标识，以及对应于该目标节点的标识的下一跳节点的标识。该情况下，网络节点的第一实体进行路由选择的过程可以包括：根据Adapt层头中携带的目的节点的标识，将转发表中的与目的节点的标识对应的下一跳节点的标识对应的节点，确定为数据包的下一跳节点。
可选的，在转发表中，一个目的节点的标识可以对应多个下一跳节点的标识。该情况下，在转发表中还可以有进一步的选择规则(例如，不同的下一跳节点可分别对应于终端的不同的承载)，以供网络节点根据更多的额外信息(例如，Adapt层头中的终端的承载的标识)从目的节点的标识对应的多个下一跳节点的标识中选择出数据包的下一跳节点。
除了本申请示例中示出的路由选择的实现方式之外，路由选择还可以有其他实现方式，本申请中不作限定。
方法2、网络节点的第一实体将第一业务区分通道的标识向第三实体递交，第一业务区分通道为第一实体接收到的数据包所来自的业务区分通道，业务区分通道为逻辑信道或RLC信道或RLC承载。
其中，第一业务区分通道的标识可以用于第三实体确定下一跳节点和/或第二业务区分通道，第二业务区分通道为第三实体发送数据包的业务区分通道。
方法3、网络节点的第一实体确定向数据包的下一跳节点递交数据包的第二业务区分通道；网络节点的第一实体向第三实体递交第二业务区分通道的标识。
在方法3中，网络节点的第一实体可以通过承载映射确定第二业务区分通道。网络节点的第一实体进行承载映射的方法与实施例二中的方式一至方式三类似，可参考实施例二进行理解，在此不再赘述。
在中间IAB节点共用Adapt层的情况下，路由选择和承载映射由中间IAB节点的发送侧和接收侧共用的Adapt层实体(即第一实体)执行。该Adapt层实体进行路由选择的方法可参见上述方法1的相关描述，该Adapt层实体进行承载映射的方法与实施例二中的方式一至方式三类似，可参考实施例二进行理解，在此不再赘述。
在中间IAB节点不共用Adapt层的情况下，参见表1，中间IAB节点中的发送侧和接收侧是否执行路由选择和承载映射取决于具体实现，例如，可以有表1中所示的三种示例。
表1
Figure PCTCN2020075147-appb-000001
其中，示例1所适用的场景为：网络节点的发送侧只有一个Adapt层实体(即上述情况1)。
示例2所适用的场景为：网络节点的发送侧只有一个Adapt层实体(即上述情况1)；或者，网络节点的发送侧中包括多个Adapt层实体，每个Adapt层实体对应与网络节点通信的一个节点(即上述情况2)。
示例3所适用的场景为：网络节点的发送侧只有一个Adapt层实体(即上述情况1)；或者，网络节点的发送侧中包括多个Adapt层实体，每个Adapt层实体对应与网络节点通信的一个节点(即上述情况2)；或者，网络节点的发送侧中包括多个Adapt层实体，一个Adapt层实体对应一个RLC层实体(即上述情况3)。
此处的适用场景仅仅为示例，在具体实现时，示例1、示例2或示例3所适用的场景还可以为其他场景，不作限定。
实施例二
该实施例中，网络节点为中间IAB节点、且中间IAB节点的DU部分和MT部分不共用Adapt层。实施例二提供了一种通信方法，如图13所示，包括：
1301、网络节点的第三实体从第一实体接收数据包，第一实体和第三实体均为Adapt层实体。
其中，网络节点的第一实体位于网络节点的接收侧，网络节点的第三实体位于网络节点的发送侧。该数据包可以为实施例一中的网络节点的第一实体向第三实体递交的数据包， 该数据包可以为第一类型数据包，也可以为第二类型数据包。第一类型数据包是指包括Adapt层头和Adapt层载荷的数据包。第二类型数据包是指包括Adapt层载荷的数据包。
1302、网络节点的第三实体通过第二业务区分通道将数据包递交给第四实体。
其中，第四实体为Adapt层的下层协议层的协议层实体，例如，RLC层实体。第二业务区分通道与数据包的下一跳节点对应(即第二业务区分通道为通往数据包的下一跳节点的多个业务区分通道中的一个业务区分通道)，业务区分通道为逻辑信道或RLC信道或RLC承载。
实施例二提供的方法，网络节点的第三实体通过与数据包的下一跳节点对应的第二业务区分通道将数据包递交给第四实体，可以保证数据包正确的传输至数据包的下一跳节点。
可选的，在数据包为第二类型数据包的情况下，该方法还包括：11)网络节点的第三实体为数据包添加Adapt层头。该情况下，步骤1302包括：网络节点的第三实体通过第二业务区分通道将添加Adapt层头后的数据包递交给第四实体。
需要说明的是，第三实体添加Adapt层头所需要的信息可以和Adapt层载荷一起，由第一实体发送给第三实体。该情况下，上述方法还包括：网络节点的第三实体从第一实体接收Adapt层中的信息。
需要说明的是，当数据包为第二类型数据包时，由于第二类型数据包没有Adapt层头。因此，网络节点的第三实体可以为数据包添加Adapt层头。当数据包为第一类型数据包(即Adapt PDU)时，由于Adapt PDU有Adapt层头，因此，网络节点的第三实体可以不为数据包添加Adapt层头。
可选的，该方法还包括以下一项或多项：21)网络节点的第三实体为数据包确定下一跳节点；或，31)网络节点的第三实体为数据包确定第二业务区分通道。
步骤21)在具体实现时，网络节点的第三实体可以通过路由选择确定数据包的下一跳节点。步骤31)在具体实现时，网络节点的第三实体可以通过承载映射确定第二业务区分通道。网络节点的第三实体是否执行路由选择和承载映射，与第一实体执行的动作相关。具体可参见表1。此处不再赘述。示例性的，参见图14中的(a)和(b)，图14示出了第三实体处理数据包的两种可能的流程。
步骤21)可以通过以下方式1或方式2实现。
方式1、自行确定
方式1的具体实现可以参见实施例一中的方法1，在此不再赘述。
方式2、网络节点的第三实体从第一实体接收用于指示下一跳节点的信息，网络节点的第三实体根据用于指示下一跳节点的信息确定下一跳节点。
其中，用于指示下一跳节点的信息可以为下一跳节点的标识。
步骤31)可以通过以下方式一至方式四中的任意一种方式实现。
方式一、网络节点的第三实体根据第一业务区分通道确定第二业务区分通道。
方式一在具体实现时，网络节点的第三实体可以根据入口链路的业务区分通道和出口链路的业务区分通道之间的对应关系确定第二业务区分通道。其中，一个入口链路的业务区分通道可以对应一个或多个出口链路的业务区分通道。
可选的，在方式一中，该方法还包括：网络节点的第三实体从第一实体接收第一业务区分通道的标识。网络节点的第三实体可以根据第一业务区分通道的标识确定第一业务区 分通道。
方式一的第一种可能的实现方式，网络节点的第三实体可以确定第一业务区分通道对应的业务区分通道为第二业务区分通道。该情况下，入口链路的业务区分通道和出口链路的业务区分通道之间可以一一对应。网络节点的第三实体可以根据该对应关系和第一业务区分通道的标识确定第二业务区分通道。
在第一种可能的实现方式，可选的，第一业务区分通道对应的业务区分通道通过网络或宿主节点或Donor-CU或CU-CP配置。
方式一的第二种可能的实现方式，一个入口链路的业务区分通道对应多个出口链路的业务区分通道。该情况下，出口链路的业务区分通道可以与数据包的下一跳节点一一对应。则网络节点的第三实体可以根据第一业务区分通道和数据包的下一跳节点，确定第二业务区分通道。示例性的，入口链路的业务区分通道与出口链路的业务区分通道、出口链路的业务区分通道与数据包的下一跳节点之间的对应关系可参见表2，则网络节点的第三实体可以根据第一业务区分通道的标识和该对应关系确定第二业务区分通道。
表2
Figure PCTCN2020075147-appb-000002
方式二、网络节点的第三实体根据数据包所属的终端的RB的标识，或，终端的RB与业务区分通道之间的对应关系中的一个或多个确定第二业务区分通道。
方式二在具体实现时，数据包的Adapt层头中可以包括数据包所属的终端的RB的标识，第三实体可以根据Adapt层头中包括的RB的标识确定对应的业务区分通道为向下一跳节点发送数据包的业务区分通道(即第二业务区分通道)。
可选的，终端的RB的标识对应多个业务区分通道，网络节点的第三实体选择与数据包的下一跳节点对应的业务区分通道作为第二业务区分通道。
其中，终端的RB与业务区分通道之间的对应关系可以是宿主节点或Donor-CU或CU-CP预先配置在网络节点中，也可以由网络节点自行生成。
方式三、网络节点的第三实体根据数据包中携带的QoS标签，以及QoS标签与业务区分通道之间的对应关系确定第二业务区分通道。
可选的，数据包中携带的QoS标签对应多个业务区分通道，网络节点的第三实体选择与数据包的下一跳节点对应的业务区分通道作为第二业务区分通道。
其中，QoS标签与业务区分通道之间的对应关系可以是宿主节点或Donor-CU或CU-CP预先配置在网络节点中，也可以由网络节点自行生成。QoS标签用于表明数据包的QoS需求，QoS标签具体可以是差分服务代码点(differentiated services code point，简称 DSCP)、IPv6数据包中的流标签(flow label)或表征数据包对应业务的QoS需求的QoS ID等。
方式四、网络节点的第三实体从第一实体接收第二业务区分通道的标识，网络节点的第三实体根据第二业务区分通道的标识确定第二业务区分通道。
在网络节点需要进行头压缩的情况下(此时，头压缩方式为逐跳头压缩)，可选的，在网络节点的第三实体为数据包添加Adapt层头之前，该方法还包括：网络节点的第三实体对数据包进行头压缩。或者，在网络节点的第三实体为数据包添加Adapt层头之后，网络节点的第三实体对添加Adapt层头后的数据包进行头压缩，该情况下，网络节点的第三实体通过第二业务区分通道将添加Adapt层头后的数据包递交给第四实体，包括：网络节点的第三实体通过第二业务区分通道将添加Adapt层头并通过头压缩后的数据包递交给第四实体。
其中，网络节点可以通过配置的头压缩算法执行头压缩。示例性的，发送侧可以采用ROHC执行头压缩。
由于头压缩的方式有两种，因此，一个节点的发送侧是否执行头压缩以及采用的头压缩方式可以由宿主节点或Donor-CU或CU-CP配置。例如，Donor-CU可以在发送给网络节点的配置信息中，携带用于配置头压缩方式的指示信息和/或头压缩的压缩算法。
其中，Donor-CU发送给网络节点的头压缩方式指示字段，可以携带在Donor-CU给网络节点的F1AP消息中，或者，在网络节点支持的协议层包括RRC层时，可以携带在Donor-CU给网络节点的RRC消息中(例如，网络节点为中间IAB节点，中间IAB节点的MT部分支持RRC协议层，Donor-CU给中间IAB节点的MT部分发送RRC消息)。
该情况下，可选的，网络节点的第三实体添加的Adapt层头中包含头压缩方式指示字段，头压缩方式指示字段用于指示网络节点的第三实体采用的头压缩方式。该情况下，数据包的下一跳节点根据该指示信息确定是否对数据包解头压缩。
关于头压缩方式指示字段的其他描述可参见实施例一的相关部分的内容，此处不再赘述。
实施例三
该实施例中，网络节点为接入IAB节点，数据包为上行数据包；或，网络节点为宿主节点或Donor-DU，数据包为下行数据包。
实施例三提供了一种通信方法，如图15所示，包括：
1501、网络节点的第一实体从第五实体接收数据包，第五实体为F1接口的协议层的协议层实体或Adapt层的上层协议层的协议层实体，第一实体为Adapt层实体，数据包为第二类型数据包，第二类型数据包为包括Adapt层载荷的数据包。
其中，网络节点的第一实体位于网络节点的发送侧。示例性的，第五实体可以为IP层的协议层实体。
1502、网络节点的第一实体为数据包添加Adapt层头。
步骤1502在具体实现时，网络节点的第一实体添加Adapt层头所需要的信息，可以和数据包一起，由第五实体发送给第一实体。
1503、网络节点的第一实体通过第三业务区分通道将添加Adapt层头后的数据包递交给第六实体，第六实体为Adapt层的下层协议层的协议层实体，第三业务区分通道与数据 包的下一跳节点对应(即第三业务区分通道为通往数据包的下一跳节点的多个业务区分通道中的一个业务区分通道)，业务区分通道为逻辑信道或RLC信道或RLC承载。
示例性的，第六实体可以为RLC层实体。
实施例三提供的方法，网络节点的第一实体通过与数据包的下一跳节点对应的第三业务区分通道将数据包递交给第六实体，可以保证数据包正确的传输至数据包的下一跳节点。
可选的，该方法还包括以下一项或多项：11)网络节点的第一实体确定数据包的下一跳节点；或，21)网络节点的第一实体确定第三业务区分通道。
步骤11)在具体实现时，网络节点的第一实体可以通过路由选择确定数据包的下一跳节点。步骤21)在具体实现时，网络节点的第一实体可以通过承载映射确定第三业务区分通道。
需要说明的是，在网络节点的第一实体仅为数据包添加Adapt层头时，路由选择和承载映射可以在第五实体执行。
其中，步骤11)可以通过与实施例二中的方式1类似的方法实现(在此不再赘述)，也可以从第五实体接收下一跳节点的标识，根据下一跳节点的标识确定下一跳节点。
步骤21)可以通过与实施例二中的方式二或方式三类似的方法实现(在此不再赘述)，也可以从第五实体接收第三业务区分通道的标识，根据第三业务区分通道的标识确定第三业务区分通道。
在网络节点需要进行头压缩的情况下，第一种可能的实现方式，在步骤1502之前，该方法还包括：网络节点的第一实体对数据包进行头压缩。第二种可能的实现方式，在步骤1503之前，该方法还包括：网络节点的第一实体对添加Adapt层头之后的数据包进行头压缩。基于第二种可能的实现方式，步骤1503包括：网络节点的第一实体通过第三业务区分通道将添加Adapt层头并进行头压缩后的数据包递交给第六实体。
其中，网络节点可以通过配置的头压缩算法执行头压缩。示例性的，发送侧可以采用ROHC协议执行头压缩。
由于头压缩的方式有两种，因此，一个节点的发送侧是否执行头压缩以及采用的头压缩方式可以由宿主节点或Donor-CU或CU-CP配置。例如，Donor-CU可以在发送给网络节点(例如，接入IAB节点或Donor-DU)的配置信息中，携带用于配置头压缩方式的指示信息和/或头压缩的压缩算法。
其中，Donor-CU发给Donor-DU的配置信息，可以携带在Donor-CU给Donor-DU的F1AP消息中。Donor-CU发送给接入IAB节点的配置信息，可以携带在Donor-CU给接入IAB节点的DU部分的F1AP消息中，或者，携带在Donor-CU给接入IAB节点的MT部分的RRC消息中。
可选的，网络节点的第一实体添加的Adapt层头中包含头压缩方式指示字段，头压缩方式指示字段用于指示网络节点的第一实体采用的头压缩方式。该情况下，数据包的下一跳节点根据该指示信息确定是否对数据包解头压缩。
关于头压缩方式指示字段的其他描述可参见实施例一的相关部分的内容，此处不再赘述。
需要说明的是，实施例一至实施例三中的头压缩或解头压缩的方法可以不与相应实施例的其他方法耦合，即可以独立执行。
实施例四
考虑到IAB网络可能会发生拓扑更新，IAB节点可以选择新的父节点建立连接。例如，图1所示的IAB网络中，若IAB节点5和IAB节点2之间的无线回传链路发生无线链路失败(radio link failure)，则IAB节点5可以选择IAB节点4作为新的父节点，建立无线回传链路。在IAB网络拓扑发生变化时，IAB节点的Adapt层也需要重建(re-establishment)。为此，实施例四提供了一种Adapt层重建方法，如图16所示，包括：
1601、网络节点的Adapt层的上层协议层向网络节点的Adapt层发送Adapt层重建指示信息。
步骤1601在具体实现时，网络节点的Adapt层的上层协议层触发Adapt层重建。
例如，在IAB节点的MT部分包括RRC层的情况下，IAB节点的MT部分的RRC层触发MT部分的Adapt层重建。具体可以是IAB节点的MT部分收到Donor-CU发送的RRC消息，RRC消息中包含Adapt层重建的指示信息(例如，Adapt-reestablish)，IAB节点的MT部分的RRC层根据Adapt层重建的指示信息触发MT部分的Adapt层重建，或者，触发该IAB节点DU部分的Adapt层重建。
再例如，在Donor-DU的面向IAB节点的协议栈中包括F1AP层的情况下，Donor-DU的F1AP层触发Donor-DU的Adapt层重建。具体可以是Donor-DU收到Donor-CU发送的F1AP消息，F1AP消息中包含Adapt层重建的指示信息，Donor-DU根据Adapt层重建的指示信息触发Donor-DU的Adapt层重建。
再例如，IAB节点的DU部分的F1AP层触发IAB节点的DU/MT部分的Adapt层重建。具体可以是IAB节点的DU部分收到Donor-CU发送的F1AP消息，其中包含Adapt层重建的指示信息，IAB节点的DU/MT部分根据Adapt层重建的指示信息触发IAB节点的DU/MT部分的Adapt层重建。
1602、网络节点的Adapt层从上层协议层接收Adapt层重建指示信息，并根据Adapt层重建指示信息重建Adapt层。
步骤1602在具体实现时，可以包括：网络节点的Adapt层根据Adapt层重建指示信息配置新的Adapt层路由转发表和/或新的承载映射关系。
其中，新的Adapt层路由转发表可以包括新的上行Adapt层路由转发表和/或新的下行Adapt层路由转发表。新的承载映射关系可以是指终端的RB与新出口链路的业务区分通道的新的映射关系，入口链路的业务区分通道与新出口链路的业务区分通道的新的映射关系等。
可选的，该方法还包括：网络节点的Adapt层根据配置的新的Adapt层路由转发表，向新的Adapt层路由转发表中的下一跳节点重传未成功发送的数据包，从而避免终端丢包。可选的，该未成功发送的数据包，可以是网络节点的Adapt层缓存中的数据包，也可以是网络节点的Adapt层已经向下层协议层递交，再由下层协议层传回给Adapt层的数据包(该数据包可以为下层协议层未成功发送的数据包)。
网络节点是否成功接收到数据包可以通过网络节点的Adapt层的低层(lower layer)指示。可选的，针对网络节点的发送侧，Adapt层从下层协议层(例如，RLC层)收到针对某个数据包(Adapt PDU或Adapt SDU或RLC SDU)的确认成功发送指示，则Adapt层 可以根据该指示丢弃该数据包，从而清理缓存空间。
该可选的方法，在Adapt层有缓存的情况下，可以让Adapt层有效进行缓存管理，丢弃无缓存价值的数据包。例如，网络节点的发送侧的RLC层实体可以在收到与网络节点通信的节点的接收侧反馈的RLC状态报告后，根据RLC状态报告中指示的数据包肯定确认(Acknowledge，简称ACK)信息，向上层协议层即Adapt层发送确认成功发送指示，Adapt层根据该指示丢弃数据包，清理缓存空间。
实施例四提供的方法，在IAB网络拓扑发送变化时，可以重建网络节点的Adapt层，为数据无损传输提供保障，可以避免由于无线回传链路拓扑变化而导致丢包的问题，提高数据传输的可靠性。
本申请实施例一至实施例四中的各种可选的方法的有益效果可参见发明内容部分。
上述主要从方法角度对本申请实施例的方案进行了介绍。可以理解的是，网络节点为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对网络节点进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
本申请实施例还提供了一种网络节点(记为网络节点170)，如图17所示，包括：
获取单元1701，用于接收从所述网络节点的适配层的下层协议层的协议层实体递交的数据包，所述数据包为第一类型数据包，所述第一类型数据包为包括适配层头和适配层载荷的数据包；
判断单元1702，用于判断所述网络节点是否为所述数据包在适配层路由的目的节点；
处理单元1703，用于根据判断结果处理所述数据包。
可选的，所述判断结果为：所述网络节点为所述数据包在适配层路由的目的节点；
所述处理单元1703，具体用于将所述数据包中的适配层载荷向第二实体递交，所述第二实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体。
可选的，所述判断结果为：所述网络节点为所述数据包在适配层路由的目的节点；
所述处理单元1703，具体用于将所述数据包存储到适配层的缓存中。
可选的，所述判断结果为：所述网络节点不是所述数据包在适配层路由的目的节点；
所述处理单元1703，具体用于将所述数据包向第三实体递交，所述第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
可选的，所述判断结果为：所述网络节点不是所述数据包在适配层路由的目的节点；
所述处理单元1703，具体用于将所述数据包中的适配层载荷和所述数据包中的适配层头中的信息向第三实体递交，所述第三实体为无线回传接口的协议层的协议层实体或适配 层的下层协议层的协议层实体。
可选的，所述数据包为适配层的数据PDU。
可选的，所述数据包为适配层的控制PDU。
可选的，参见图17，所述网络节点还包括确定单元1704，所述确定单元1704用于确定所述数据包的下一跳节点，所述处理单元1703，还用于向所述第三实体递交用于指示所述下一跳节点的信息；和/或，
所述处理单元1703，还用于将第一业务区分通道的标识向所述第三实体递交，所述第一业务区分通道为所述获取单元1701接收到的所述数据包所来自的业务区分通道；其中，业务区分通道为逻辑信道或RLC信道或RLC承载；和/或，
参见图17，所述网络节点还包括确定单元1704，所述确定单元1704用于确定向所述数据包的下一跳节点递交所述数据包的第二业务区分通道，所述处理单元1703，还用于向所述第三实体递交所述第二业务区分通道的标识；其中，所述第二业务区分通道为所述第三实体发送所述数据包的业务区分通道，业务区分通道为逻辑信道或RLC信道或RLC承载。
可选的，所述判断单元1702，具体用于根据所述数据包中的适配层头中的路由信息、所述数据包中的适配层头中是否包含路由信息，以及所述数据包是否为控制PDU中的一种或多种判断所述网络节点是否为所述数据包在适配层路由的目的节点。
可选的，获取单元1701、判断单元1702、处理单元1703和确定单元1704可以位于网络节点的第一实体中，第一实体为适配层实体。
本申请实施例还提供了一种网络节点(记为网络节点180)，如图18所示，包括：
获取单元1801，用于从第一实体接收数据包，所述第一实体为适配层实体；
递交单元1802，用于通过第二业务区分通道将所述数据包递交给第四实体；
其中，所述第四实体为适配层的下层协议层的协议层实体，所述第二业务区分通道与所述数据包的下一跳节点对应，业务区分通道为逻辑信道或RLC信道或RLC承载。
可选的，第二类型数据包为包括适配层载荷的数据包，在所述数据包为所述第二类型数据包的情况下，参见图18，所述网络节点还包括：
添加单元1803，用于为所述数据包添加适配层头；
所述递交单元1802，具体用于通过所述第二业务区分通道将添加适配层头后的所述数据包递交给第四实体。
可选的，参见图18，所述网络节点还包括：确定单元1804；
所述确定单元1804，用于为所述数据包确定下一跳节点；和/或，
所述确定单元1804，用于为所述数据包确定所述第二业务区分通道。
可选的，所述确定单元1804，具体用于：根据第一业务区分通道确定所述第二业务区分通道，所述第一业务区分通道为所述第一实体接收到的所述数据包所来自的业务区分通道。
可选的，所述确定单元1804，具体用于：根据所述数据包所属的终端的RB的标识，和/或，所述终端的RB与业务区分通道之间的对应关系确定所述第二业务区分通道。
可选的，所述确定单元1804，具体用于：根据所述数据包中携带的QoS标签，以及QoS标签与业务区分通道之间的对应关系确定所述第二业务区分通道。
可选的，所述确定单元1804，具体用于：根据从所述第一实体接收到的所述第二业务区分通道的标识确定所述第二业务区分通道。
可选的，所述确定单元1804，具体用于：根据从所述第一实体接收到的所述用于指示所述下一跳节点的信息确定所述下一跳节点。
可选的，获取单元1801、添加单元1803、递交单元1802和确定单元1804可以位于网络节点的第三实体中，第三实体为适配层实体。
本申请实施例还提供了一种网络节点(记为网络节点190)，如图19所示，包括：
获取单元1901，用于从第五实体接收数据包，所述第五实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体，所述数据包为第二类型数据包，所述第二类型数据包为包括适配层载荷的数据包；
添加单元1902，用于为所述数据包添加适配层头；
递交单元1903，用于通过第三业务区分通道将添加适配层头后的所述数据包递交给第六实体，所述第六实体为适配层的下层协议层的协议层实体，所述第三业务区分通道与所述数据包的下一跳节点对应，业务区分通道为逻辑信道或RLC信道或RLC承载。
可选的，所述网络节点还包括：确定单元1904；
所述确定单元1904，用于确定所述数据包的下一跳节点；和/或，
所述确定单元1904，用于确定所述第三业务区分通道。
可选的，获取单元1901、添加单元1902、递交单元1903和确定单元1904可以位于网络节点的第一实体中，第一实体为适配层实体。
上述网络节点170、网络节点180和网络节点190可以为网络设备，也可以为网络设备内的芯片。
图17、图18和图19中的单元也可以称为模块，例如，处理单元可以称为处理模块。另外，在图17、图18和图19所示的实施例中，各个单元的名称也可以不是图中所示的名称。例如，接收数据包的单元也可以称为接收单元(例如，获取单元1701可以称为接收单元1701)，递交数据包的单元也可以称为发送单元(例如，递交单元1903可以称为发送单元1903)，执行其他动作的单元可以称为处理单元(例如，确定单元1904可以称为处理单元1904)，具体取决于模块的划分方式。
图17、图18和图19中的各个单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。存储计算机软件产品的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，简称ROM)、随机存取存储器(random access memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例还提供了一种网络节点(记为网络节点200)的硬件结构示意图，参见图20或图21，该网络节点200包括处理器2001，可选的，还包括与处理器2001连接的存储器2002。
处理器2001可以是一个通用中央处理器(central processing unit，简称CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，简称ASIC)，或者一个或多个用于控制本申请方案程序执行的集成电路。处理器2001也可以包括多个CPU，并且处理器2001可以是一个单核(single-CPU)处理器，也可以是多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路或用于处理数据(例如计算机程序指令)的处理核。
存储器2002可以是ROM或可存储静态信息和指令的其他类型的静态存储设备、RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，简称EEPROM)、只读光盘(compact disc read-only memory，简称CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，本申请实施例对此不作任何限制。存储器2002可以是独立存在，也可以和处理器2001集成在一起。其中，存储器2002中可以包含计算机程序代码。处理器2001用于执行存储器2002中存储的计算机程序代码，从而实现本申请实施例提供的方法。
在第一种可能的实现方式中，参见图20，网络节点200还包括收发器2003。处理器2001、存储器2002和收发器2003通过总线相连接。收发器2003用于与其他通信设备或网络节点中的其他协议层通信。可选的，收发器2003可以包括发射机和接收机。收发器2003中用于实现接收功能(例如，接收上层协议层递交的数据包)的器件可以视为接收机，接收机用于执行本申请实施例中的接收的步骤。收发器2003中用于实现发送功能(例如，向其他协议层递交数据包)的器件可以视为发射机，发射机用于执行本申请实施例中的发送或递交的步骤。
基于第一种可能的实现方式，图20所示的结构示意图可以用于示意上述实施例中所涉及的网络节点的结构。处理器2001用于对网络节点的动作进行控制管理，例如，处理器2001用于支持网络节点执行图10至图16中的步骤，和/或本申请实施例中所描述的其他过程中的网络节点执行的动作。处理器2001可以通过收发器2003与其他通信设备或网络节点中的其他协议层通信(该情况下，当网络节点执行实施例一或实施例三所示的方法时，收发器2003可以位于第一实体中，当网络节点执行实施例二所示的方法时，收发器2003可以位于第三实体中)。存储器2002用于存储终端的程序代码和数据。
在第二种可能的实现方式中，处理器2001包括逻辑电路以及输入接口和/或输出接口。其中，输出接口用于执行相应方法中的发送或递交的动作，输入接口用于执行相应方法中的接收的动作。
基于第二种可能的实现方式，参见图21，图21所示的结构示意图可以用于示意上述实施例中所涉及的网络节点的结构。处理器2001用于对网络节点的动作进行控制管理，例如，处理器2001用于支持网络节点执行图10至图16中的步骤，和/或本申请实施例中所描述的其他过程中的网络节点执行的动作。处理器2001可以通过输入接口和/或输出接口与其他通信设备或网络节点中的其他协议层通信(该情况下，当网络节点执行实施例一或实施例三所示的方法时，输入接口和/或输出接口可以位于第一实体中，当网络节点执行实施例二所示的方法时，输入接口和/或输出接口可以位于第三实体中)。存储器2002用于 存储终端的程序代码和数据。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种系统芯片，该系统芯片应用在网络节点中，该系统芯片包括：至少一个处理器，涉及的程序指令在该至少一个处理器中执行，以执行上述实施例提供的任意一种方法。
本申请实施例还提供了一种通信系统，包括：上述实施例提供的网络节点中的一个或多个网络节点。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，简称DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，简称SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (42)

  1. 一种通信方法，其特征在于，包括：
    网络节点的第一实体接收从下层协议层的协议层实体递交的数据包，所述第一实体为适配层实体，所述数据包为第一类型数据包，所述第一类型数据包为包括适配层头和适配层载荷的数据包；
    所述网络节点的第一实体判断所述网络节点是否为所述数据包在适配层路由的目的节点；
    所述网络节点的第一实体根据判断结果处理所述数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述判断结果为：所述网络节点为所述数据包在适配层路由的目的节点，所述网络节点的第一实体根据判断结果处理所述数据包，包括：
    所述网络节点的第一实体将所述数据包中的适配层载荷向第二实体递交，所述第二实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体。
  3. 根据权利要求1所述的方法，其特征在于，所述判断结果为：所述网络节点为所述数据包在适配层路由的目的节点，所述网络节点的第一实体根据判断结果处理所述数据包，包括：
    所述网络节点的第一实体将所述数据包存储到适配层的缓存中。
  4. 根据权利要求1所述的方法，其特征在于，所述判断结果为：所述网络节点不是所述数据包在适配层路由的目的节点，所述网络节点的第一实体根据判断结果处理所述数据包，包括：
    所述网络节点的第一实体将所述数据包向第三实体递交，所述第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
  5. 根据权利要求1所述的方法，其特征在于，所述判断结果为：所述网络节点不是所述数据包在适配层路由的目的节点，所述网络节点的第一实体根据判断结果处理所述数据包，包括：
    所述网络节点的第一实体将所述数据包中的适配层载荷和所述数据包中的适配层头中的信息向第三实体递交，所述第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
  6. 根据权利要求2-5任一项所述的方法，其特征在于，所述数据包为适配层的数据协议数据单元PDU。
  7. 根据权利要求3-5任一项所述的方法，其特征在于，所述数据包为适配层的控制PDU。
  8. 根据权利要求4-7任一项所述的方法，其特征在于，所述方法还包括以下一项或多项：
    所述网络节点的第一实体确定所述数据包的下一跳节点，所述网络节点的第一实体向第三实体递交用于指示所述下一跳节点的信息；或，
    所述网络节点的第一实体将第一业务区分通道的标识向所述第三实体递交，所述第一业务区分通道为所述第一实体接收到的所述数据包所来自的业务区分通道；其中，所述业务区分通道为逻辑信道或无线链路控制RLC信道或RLC承载；或，
    所述网络节点的第一实体确定向所述数据包的下一跳节点递交所述数据包的第二业务区分通道；所述网络节点的第一实体向所述第三实体递交所述第二业务区分通道的标识；其中，所述第二业务区分通道为所述第三实体发送所述数据包的业务区分通道，所述业务区分通道为逻辑信道或RLC信道或RLC承载。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述网络节点的第一实体判断所述网络节点是否为所述数据包在适配层路由的目的节点，包括：
    所述网络节点的第一实体根据所述数据包中的适配层头中的路由信息、所述数据包中的适配层头中是否包含路由信息，以及所述数据包是否为控制PDU中的一种或多种判断所述网络节点是否为所述数据包在适配层路由的目的节点。
  10. 根据权利要求1-8任一项所述的方法，其特征在于，所述网络节点的第一实体判断所述网络节点是否为所述数据包在适配层路由的目的节点，包括：
    当所述数据包的适配层头中携带的目的节点的标识为所述网络节点的标识时，所述网络节点的第一实体确定所述网络节点为所述数据包在适配层路由的目的节点；或者，
    当所述数据包的适配层头中携带的目的节点的标识不是所述网络节点的标识时，所述网络节点的第一实体确定所述网络节点不是所述数据包在适配层路由的目的节点。
  11. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述网络节点的第一实体根据所述数据包的适配层头中携带的PDU类型指示信息确定所述数据包的PDU类型，所述PDU类型指示信息用于指示所述数据包的PDU类型，所述数据包的PDU类型为数据PDU或控制PDU；
    所述网络节点的第一实体判断所述网络节点是否为所述数据包在适配层路由的目的节点，包括：在所述网络节点的第一实体确定所述数据包的PDU类型为数据PDU的情况下，所述网络节点的第一实体判断所述网络节点是否为所述数据包在适配层路由的目的节点。
  12. 一种通信方法，其特征在于，包括：
    网络节点的第三实体从第一实体接收数据包，所述第一实体和所述第三实体均为适配层实体；
    所述网络节点的第三实体通过第二业务区分通道将所述数据包递交给第四实体；
    其中，所述第四实体为适配层的下层协议层的协议层实体，所述第二业务区分通道与所述数据包的下一跳节点对应，所述业务区分通道为逻辑信道或无线链路控制RLC信道或RLC承载。
  13. 根据权利要求12所述的方法，其特征在于，第二类型数据包为包括适配层载荷的数据包，在所述数据包为所述第二类型数据包的情况下，所述方法还包括：
    所述网络节点的第三实体为所述数据包添加适配层头；
    所述网络节点的第三实体通过第二业务区分通道将所述数据包递交给第四实体，包括：所述网络节点的第三实体通过所述第二业务区分通道将添加适配层头后的所述数据包递交给第四实体。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括以下一项或多项：
    所述网络节点的第三实体为所述数据包确定下一跳节点；或，
    所述网络节点的第三实体为所述数据包确定所述第二业务区分通道。
  15. 根据权利要求14所述的方法，其特征在于，所述网络节点的第三实体为所述数据包确定所述第二业务区分通道，包括：
    所述网络节点的第三实体根据第一业务区分通道确定所述第二业务区分通道，所述第一业务区分通道为所述第一实体接收到的所述数据包所来自的业务区分通道。
  16. 根据权利要求14所述的方法，其特征在于，所述网络节点的第三实体为所述数据包确定所述第二业务区分通道，包括：
    所述网络节点的第三实体根据所述数据包所属的终端的无线承载RB的标识，或，所述终端的RB与业务区分通道之间的对应关系中的一个或多个确定所述第二业务区分通道。
  17. 根据权利要求14所述的方法，其特征在于，所述网络节点的第三实体为所述数据包确定所述第二业务区分通道，包括：
    所述网络节点的第三实体根据所述数据包中携带的服务质量QoS标签，以及QoS标签与业务区分通道之间的对应关系确定所述第二业务区分通道。
  18. 根据权利要求14所述的方法，其特征在于，所述网络节点的第三实体为所述数据包确定所述第二业务区分通道，包括：
    所述网络节点的第三实体从所述第一实体接收所述第二业务区分通道的标识；
    所述网络节点的第三实体根据所述第二业务区分通道的标识确定所述第二业务区分通道。
  19. 根据权利要求14-18任一项所述的方法，其特征在于，所述网络节点的第三实体为所述数据包确定下一跳节点，包括：
    所述网络节点的第三实体从所述第一实体接收用于指示所述下一跳节点的信息；
    所述网络节点的第三实体根据所述用于指示所述下一跳节点的信息确定所述下一跳节点。
  20. 一种通信方法，其特征在于，包括：
    网络节点的第一实体从第五实体接收数据包，所述第五实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体，所述第一实体为适配层实体，所述数据包为第二类型数据包，所述第二类型数据包为包括适配层载荷的数据包；
    所述网络节点的第一实体为所述数据包添加适配层头；
    所述网络节点的第一实体通过第三业务区分通道将添加适配层头后的所述数据包递交给第六实体，所述第六实体为适配层的下层协议层的协议层实体，所述第三业务区分通道与所述数据包的下一跳节点对应，所述业务区分通道为逻辑信道或无线链路控制RLC信道或RLC承载。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括以下一项或多项：
    所述网络节点的第一实体确定所述数据包的下一跳节点；或，
    所述网络节点的第一实体确定所述第三业务区分通道。
  22. 一种网络节点，其特征在于，包括：
    获取单元，用于接收从所述网络节点的适配层的下层协议层的协议层实体递交的数据包，所述数据包为第一类型数据包，所述第一类型数据包为包括适配层头和适配 层载荷的数据包；
    判断单元，用于判断所述网络节点是否为所述数据包在适配层路由的目的节点；
    处理单元，用于根据判断结果处理所述数据包。
  23. 根据权利要求22所述的网络节点，其特征在于，所述判断结果为：所述网络节点为所述数据包在适配层路由的目的节点；
    所述处理单元，具体用于将所述数据包中的适配层载荷向第二实体递交，所述第二实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体。
  24. 根据权利要求22所述的网络节点，其特征在于，所述判断结果为：所述网络节点不是所述数据包在适配层路由的目的节点；
    所述处理单元，具体用于将所述数据包向第三实体递交，所述第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
  25. 根据权利要求22所述的网络节点，其特征在于，所述判断结果为：所述网络节点不是所述数据包在适配层路由的目的节点；
    所述处理单元，具体用于将所述数据包中的适配层载荷和所述数据包中的适配层头中的信息向第三实体递交，所述第三实体为无线回传接口的协议层的协议层实体或适配层的下层协议层的协议层实体。
  26. 根据权利要求23-25任一项所述的网络节点，其特征在于，所述数据包为适配层的数据协议数据单元PDU。
  27. 根据权利要求24或25所述的网络节点，其特征在于，所述数据包为适配层的控制PDU。
  28. 根据权利要求22-27任一项所述的网络节点，其特征在于，
    所述判断单元，具体用于当所述数据包的适配层头中携带的目的节点的标识为所述网络节点的标识时，确定所述网络节点为所述数据包在适配层路由的目的节点；或者，当所述数据包的适配层头中携带的目的节点的标识不是所述网络节点的标识时，确定所述网络节点不是所述数据包在适配层路由的目的节点。
  29. 根据权利要求26所述的网络节点，其特征在于，所述网络节点还包括：确定单元；
    所述确定单元，用于根据所述数据包的适配层头中携带的PDU类型指示信息确定所述数据包的PDU类型，所述PDU类型指示信息用于指示所述数据包的PDU类型，所述数据包的PDU类型为数据PDU或控制PDU；
    所述判断单元，具体用于：在所述确定单元确定所述数据包的PDU类型为数据PDU的情况下，判断所述网络节点是否为所述数据包在适配层路由的目的节点。
  30. 一种网络节点，其特征在于，包括：
    获取单元，用于从第一实体接收数据包，所述第一实体为适配层实体；
    递交单元，用于通过第二业务区分通道将所述数据包递交给第四实体；
    其中，所述第四实体为适配层的下层协议层的协议层实体，所述第二业务区分通道与所述数据包的下一跳节点对应，所述业务区分通道为逻辑信道或无线链路控制RLC信道或RLC承载。
  31. 根据权利要求30所述的网络节点，其特征在于，第二类型数据包为包括适配 层载荷的数据包，在所述数据包为所述第二类型数据包的情况下；
    所述网络节点还包括：添加单元，用于为所述数据包添加适配层头；
    所述递交单元，具体用于通过所述第二业务区分通道将添加适配层头后的所述数据包递交给第四实体。
  32. 根据权利要求30或31所述的网络节点，其特征在于，所述网络节点还包括：确定单元；
    所述确定单元，用于为所述数据包确定下一跳节点；和/或，
    所述确定单元，用于为所述数据包确定所述第二业务区分通道。
  33. 根据权利要求32所述的网络节点，其特征在于，
    所述确定单元，具体用于根据第一业务区分通道确定所述第二业务区分通道，所述第一业务区分通道为所述第一实体接收到的所述数据包所来自的业务区分通道。
  34. 根据权利要求32或33所述的网络节点，其特征在于，
    所述确定单元，具体用于根据从所述第一实体接收到的用于指示所述下一跳节点的信息确定所述下一跳节点。
  35. 一种网络节点，其特征在于，包括：
    获取单元，用于从第五实体接收数据包，所述第五实体为F1接口的协议层的协议层实体或适配层的上层协议层的协议层实体，所述数据包为第二类型数据包，所述第二类型数据包为包括适配层载荷的数据包；
    添加单元，用于为所述数据包添加适配层头；
    递交单元，用于通过第三业务区分通道将添加适配层头后的所述数据包递交给第六实体，所述第六实体为适配层的下层协议层的协议层实体，所述第三业务区分通道与所述数据包的下一跳节点对应，所述业务区分通道为逻辑信道或无线链路控制RLC信道或RLC承载。
  36. 根据权利要求35所述的网络节点，其特征在于，所述网络节点还包括：确定单元；所述确定单元还用于执行以下一项或多项：
    确定所述数据包的下一跳节点；或，
    确定所述第三业务区分通道。
  37. 一种网络节点，其特征在于，包括：处理器；
    所述处理器与存储器连接，所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述网络节点实现如权利要求1-11中的任一项所述的方法；或者，实现如权利要求12-19中的任一项所述的方法；或者，实现如权利要求20或21所述的方法。
  38. 一种网络节点，其特征在于，所述网络节点用于执行权利要求1-11中的任一项所述的方法；或者，执行权利要求12-19中的任一项所述的方法；或者，执行权利要求20或21所述的方法。
  39. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1-11中的任一项所述的方法；或者，实现如权利要求12-19中的任一项所述的方法；或者，实现如权利要求20或21所述的方法。
  40. 一种系统芯片，其特征在于，所述系统芯片应用在网络节点中，所述系统芯 片包括：
    至少一个处理器，涉及的程序指令在所述至少一个处理器中执行，以执行如权利要求1-11中的任一项所述的方法；或者，实现如权利要求12-19中的任一项所述的方法；或者，实现如权利要求20或21所述的方法。
  41. 一种计算机程序产品，其特征在于，包含指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1-11中的任一项所述的方法；或者，实现如权利要求12-19中的任一项所述的方法；或者，实现如权利要求20或21所述的方法。
  42. 一种通信系统，其特征在于，包括：如权利要求22-29任一项所述的网络节点，如权利要求30-34任一项所述的网络节点，或，如权利要求35或36所述的网络节点中的一个或多个网络节点。
PCT/CN2020/075147 2019-02-15 2020-02-13 一种通信方法及相关装置 WO2020164557A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20756292.7A EP3917105A4 (en) 2019-02-15 2020-02-13 COMMUNICATION PROCESS AND ASSOCIATED MECHANISM
BR112021016053-1A BR112021016053A2 (pt) 2019-02-15 2020-02-13 Método de comunicação e aparelho relacionado
US17/401,587 US20210377840A1 (en) 2019-02-15 2021-08-13 Communication Method And Related Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910118003.8A CN111585938B (zh) 2019-02-15 2019-02-15 一种通信方法及相关装置
CN201910118003.8 2019-02-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/401,587 Continuation US20210377840A1 (en) 2019-02-15 2021-08-13 Communication Method And Related Apparatus

Publications (1)

Publication Number Publication Date
WO2020164557A1 true WO2020164557A1 (zh) 2020-08-20

Family

ID=72045146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075147 WO2020164557A1 (zh) 2019-02-15 2020-02-13 一种通信方法及相关装置

Country Status (5)

Country Link
US (1) US20210377840A1 (zh)
EP (1) EP3917105A4 (zh)
CN (2) CN113645189B (zh)
BR (1) BR112021016053A2 (zh)
WO (1) WO2020164557A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020176537A1 (en) * 2019-02-25 2020-09-03 Apple Inc. Uplink (ul) retransmission and radio link failure (rlf) recovery in a multi-hop relay network
CN115150338A (zh) * 2021-03-29 2022-10-04 华为技术有限公司 报文流量控制的方法、装置、设备及计算机可读存储介质
US11832320B2 (en) * 2021-07-07 2023-11-28 Qualcomm Incorporated On-demand connectivity in an integrated access and backhaul network

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180205427A1 (en) * 2017-01-13 2018-07-19 At&T Intellectual Property I, L.P. Cross link interference measurement for wireless communications in 5g or other next generation network

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3224963B2 (ja) * 1994-08-31 2001-11-05 株式会社東芝 ネットワーク接続装置及びパケット転送方法
JP4035803B2 (ja) * 1999-02-19 2008-01-23 富士通株式会社 移動パケット通信システム
CN1156114C (zh) * 2002-04-30 2004-06-30 上海交通大学 波长－时间多波长光标记编码法及基于此编码法的收发机
US7310356B2 (en) * 2002-06-24 2007-12-18 Paradyne Corporation Automatic discovery of network core type
US20040167988A1 (en) * 2002-12-23 2004-08-26 Johan Rune Bridging between a Bluetooth scatternet and an Ethernet LAN
US8699408B2 (en) * 2004-08-25 2014-04-15 Alcatel Lucent Method for controlling transmission over a radio channel between a sending unit and receiving units and equipments for implementing the method
CN102780613B (zh) * 2012-06-19 2015-12-09 瑞斯康达科技发展股份有限公司 一种分布式设备板间通信的方法与装置
CN104869666B (zh) * 2015-04-10 2019-05-21 电信科学技术研究院 数据无线承载配置方法、数据传输方法及设备
CN104993969B (zh) * 2015-07-28 2018-01-16 上海斐讯数据通信技术有限公司 一种异步配置onu方法、系统及olt
WO2018145292A1 (zh) * 2017-02-10 2018-08-16 华为技术有限公司 通信方法、装置和系统
CN108809897A (zh) * 2017-04-28 2018-11-13 中兴通讯股份有限公司 一种中继发现及中继转发方法、设备和存储介质
US10631346B2 (en) * 2017-08-08 2020-04-21 Qualcomm Incorporated Communicating remote and local data in a wireless fronthaul
CN107959631A (zh) * 2017-12-15 2018-04-24 佛山市校友桥网络科技有限公司 一种基于OpenWrt操作系统的6LoWPAN边界路由器的实现方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180205427A1 (en) * 2017-01-13 2018-07-19 At&T Intellectual Property I, L.P. Cross link interference measurement for wireless communications in 5g or other next generation network

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Destination Address and Forwarding Path based Routing for IAB", 3GPP DRAFT; R3-181997, 20 April 2018 (2018-04-20), Sanya, China, pages 1 - 4, XP051417033 *
HUAWEI; HISILICON: "Adaptation layer design", 3GPP DRAFT; R2-1815545, 12 October 2018 (2018-10-12), Chengdu, China, pages 1 - 5, XP051524864 *
See also references of EP3917105A4
ZTE: "Considerations on adaptation layer in IAB", 3GPP DRAFT; R2-1807395, 25 May 2018 (2018-05-25), Busan, Korea, pages 1 - 5, XP051464638 *
ZTE: "Considerations on adaptation layer in IAB", 3GPP DRAFT; R3-182788, 25 May 2018 (2018-05-25), Busan, Korea, pages 1 - 5, XP051526968 *

Also Published As

Publication number Publication date
CN111585938A (zh) 2020-08-25
CN113645189B (zh) 2022-06-28
CN113645189A (zh) 2021-11-12
CN111585938B (zh) 2021-10-22
US20210377840A1 (en) 2021-12-02
EP3917105A4 (en) 2022-03-23
BR112021016053A2 (pt) 2021-10-13
EP3917105A1 (en) 2021-12-01

Similar Documents

Publication Publication Date Title
US11510131B2 (en) Configuration method, data transmission method, and apparatus
US11425600B2 (en) Wireless backhaul data transmission method and apparatus
EP3806542B1 (en) Path changing method and apparatus
WO2019101211A1 (zh) 一种通信方法、通信节点和系统
US20200344843A1 (en) Node and communication method
CN110365609B (zh) 一种数据包分段方法、及装置
WO2020164557A1 (zh) 一种通信方法及相关装置
CN111148163B (zh) 通信方法及装置
CN110603803A (zh) 用于云局域网环境中网络实体之间通信的方法和设备
WO2020063504A1 (zh) 用于无线回传网络的数据传输方法和装置
WO2021062803A1 (zh) 一种数据包传输方法及装置
WO2020082948A1 (zh) 一种数据传输方法及装置
WO2023046878A1 (en) Routing data in an integrated access and backhaul network
WO2021087924A1 (zh) 一种通信方法及装置
US20230370943A1 (en) Communication method and communication apparatus
WO2023286690A1 (ja) 通信制御方法
WO2023011111A1 (zh) 路由方法和通信装置
US20240048486A1 (en) Routing data in an integrated access and backhaul network
GB2605960A (en) Routing data in an integrated access and backhaul network
GB2614050A (en) Methods for use in a process for migrating resources between integrated access and backhaul topologies
WO2022248658A1 (en) Flow control feedback in an integrated access and backhaul network

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: 20756292

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021016053

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2020756292

Country of ref document: EP

Effective date: 20210825

ENP Entry into the national phase

Ref document number: 112021016053

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20210813