WO2022006907A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2022006907A1
WO2022006907A1 PCT/CN2020/101477 CN2020101477W WO2022006907A1 WO 2022006907 A1 WO2022006907 A1 WO 2022006907A1 CN 2020101477 W CN2020101477 W CN 2020101477W WO 2022006907 A1 WO2022006907 A1 WO 2022006907A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
iab
access
standard
node
Prior art date
Application number
PCT/CN2020/101477
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 PCT/CN2020/101477 priority Critical patent/WO2022006907A1/zh
Publication of WO2022006907A1 publication Critical patent/WO2022006907A1/zh

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method and apparatus.
  • IAB node IAB node
  • IAB donor IAB host node, or host IAB node
  • the IAB backhaul link (including the link between the IAB node and the IAB node, and the link between the IAB node and the IAB host node) adopts the new radio (New radio, NR) standard
  • the IAB access link (that is, the link between the user equipment and the IAB node) adopts the Long Term Evolution (Long Term Evolution, LTE) standard or the NR standard.
  • the IAB link can be used in cross-standard scenarios, that is, 4G user equipment (LTE UE) or 5G user equipment (NR UE) using different standards (such as Wireless Local Area Network (WLAN), Bluetooth, purple
  • LTE UE 4G user equipment
  • NR UE 5G user equipment
  • WLAN Wireless Local Area Network
  • the access technology of the bee (zigbee) is connected to the IAB node, and the IAB node accesses the corresponding core network through the NR backhaul link.
  • Embodiments of the present application provide a communication method and apparatus to ensure normal communication between different devices in a cross-standard scenario.
  • an embodiment of the present application provides a communication method, including: a user equipment UE determines first information corresponding to uplink data, where the first information is used to identify a service type corresponding to the uplink data in a first format or bearer; the UE determines the second information according to the first information, where the second information is used to identify the service type or bearer corresponding to the uplink data in the second standard, the second standard and the first standard One standard is different; the UE sends the uplink data by using the air interface technology of the second standard according to the second information.
  • the UE uses the same standard to access the network (for example, both are the first standard, which can be NR or LTE specifically, that is, the LTE UE accesses the network through the LTE standard, and the NR UE accesses the network through the NR standard),
  • the UE sends uplink data by using the air interface technology of the first standard according to the first information.
  • the UE of the first standard accesses the network through the air interface technology of the second standard (for example, the second standard is WLAN, that is, the LTE UE or the NR UE accesses the network through the WLAN standard)
  • the second standard does not recognize the first information and cannot perform QoS guarantee for data transmission
  • the UE cannot use the air interface technology of the second standard to perform QoS guaranteed uplink data transmission according to the first information.
  • the UE of the present application obtains the second information that can be identified by the second standard according to the first information, so that the UE can use the air interface technology of the second standard to send uplink data according to the second information, which ensures the data of the user equipment in the cross-standard access scenario. QoS guarantee of transmission.
  • the first information is one of a data radio bearer identification DRB ID, an evolved universal land-based radio access network radio access bearer identification E-RAB ID, or a quality of service flow identification QFI .
  • the second information is a Differentiated Services Code Point DSCP or a flow label.
  • the first standard is Long Term Evolution LTE or New Wireless NR
  • the second standard is one of wireless local area network WLAN, Bluetooth or Zigbee.
  • the UE determining the second information according to the first information includes: the UE determining the first information according to a configured mapping relationship between the first information and the second information the second information corresponding to the information.
  • the UE receives a radio resource control RRC message from the access and backhaul integrated IAB donor node, where the RRC message carries the first information and the second information, wherein the The first information corresponds to the second information.
  • the UE includes an adaptation layer, and the adaptation layer of the UE sends the second information to a lower layer of the adaptation layer; the UE uses the second information according to the second information
  • Sending the uplink data by the air interface technology of the second standard includes: according to the second information, the lower layer of the adaptation layer sends the uplink data by using the air interface of the second standard.
  • sending the second information by the adaptation layer of the UE to the lower layer of the adaptation layer includes: the adaptation layer sending control information to the lower layer of the adaptation layer, The control information is used to indicate the second information.
  • the adaptation layer of the UE sending the second information to a lower layer of the adaptation layer includes: the adaptation layer adds an adaptation layer header to the uplink data, The adaptation layer header carries the second information; the adaptation layer sends an adaptation layer packet to the lower layer of the adaptation layer, and the adaptation layer packet carries the adaptation layer header.
  • the adaptation layer header also carries the first information.
  • an embodiment of the present application provides a communication method, including: an integrated IAB node for access and backhaul receives a data packet from a user equipment UE, where the data packet carries uplink data, and carries first information and/or first information and/or first information.
  • the first information is used to identify the service type or bearer corresponding to the uplink data in the first mode
  • the second information is used to identify the service type or bearer corresponding to the uplink data in the second mode
  • the second standard is different from the first standard
  • the IAB node is the access IAB node of the UE
  • the IAB node determines the general packet radio service according to the first information or the second information
  • the tunnel identifier of the tunnel protocol GTP tunnel GTP tunnel
  • the IAB node maps the uplink data to the GTP tunnel corresponding to the tunnel identifier and sends it to the IAB host node (or it is understood that the IAB node sends the data mapped to the IAB host node to the IAB host node.
  • the tunnel identifies the uplink data in the corresponding GTP tunnel).
  • the tunnel identifier includes GTP TEID, or GTP TEID and Internet Protocol IP address.
  • the UE sends the uplink data to the access IAB node through the DRB, and then the access IAB node maps the uplink data to the corresponding GTP tunnel according to the mapping relationship between the configured GTP tunnel and the UE DRB.
  • the WLAN air interface of the UE does not send uplink data to the access IAB node through the DRB. Therefore, in the prior art, the access The IAB node cannot determine which GTP tunnel the received uplink data needs to be placed in.
  • the first information can be carried in the data packet, and the mapping relationship between the first information and the tunnel identifier of the GTP tunnel can be configured on the access IAB node, or the second information can be carried in the data packet, and The mapping relationship between the second information and the tunnel identifier of the GTP tunnel is configured on the access IAB node, so that the access IAB node can determine the mapping relationship based on the configured mapping relationship and the first information or the second information obtained from the data packet.
  • This data packet corresponds to the GTP tunnel, so that the uplink data is mapped to the GTP tunnel and sent to the IAB host node, which realizes the correct transmission of the data and ensures the QoS guarantee of user equipment data transmission in the cross-standard access scenario.
  • the first information is one of a data radio bearer identification DRB ID, an evolved universal land-based radio access network radio access bearer identification E-RAB ID, or a quality of service flow identification QFI .
  • the second information is a Differentiated Services Code Point DSCP or a flow label.
  • the first standard is Long Term Evolution LTE or New Wireless NR
  • the second standard is one of wireless local area network WLAN, Bluetooth or Zigbee.
  • the IAB node determines the tunnel identifier of the GTP tunnel according to the first information, including: the IAB node according to the configured mapping relationship between the first information and the tunnel identifier, The tunnel identifier corresponding to the first information is determined.
  • the IAB node receives a radio resource control RRC message or an F1AP message from the IAB host node, where the RRC message or the F1AP message carries the first information and the tunnel identifier, wherein the The first information corresponds to the tunnel identifier.
  • the IAB node determines the tunnel identifier of the GTP tunnel according to the second information, including: mapping the IAB node to the tunnel identifier according to the configured second information relationship, and determine the tunnel identifier corresponding to the second information.
  • the IAB node receives an RRC message or an F1AP message from the IAB host node, where the RRC message or F1AP message carries the second information and the tunnel identifier, wherein the second The information corresponds to the tunnel identifier.
  • an embodiment of the present application provides a communication method, including: an integrated IAB node for access and backhaul receives downlink data sent by an IAB host node through a General Packet Radio Service Tunneling Protocol GTP tunnel, where a tunnel identifier of the GTP tunnel includes GTP TEID or GTP TEID and Internet IP address; the IAB node is the access IAB node of the user equipment UE; the IAB node determines the differentiated services code point DSCP or flow label corresponding to the downlink data; the IAB node according to the the DSCP or the flow label, and send the downlink data to the UE.
  • GTP tunnel General Packet Radio Service Tunneling Protocol
  • the access to the IAB node is to send downlink data to the UE through the DRB.
  • the WLAN air interface accessing the IAB node cannot send downlink data to the UE through the DRB, because the WLAN standard does not recognize the DRB. Therefore, in the above solution of the present application, the access IAB node can obtain the DSCP or flow label corresponding to the downlink data packet, and send the downlink data to the UE according to the DSCP or the flow label. Since the WLAN standard can identify DSCP or flow labels, the downlink data can be sent correctly, and the QoS guarantee of user equipment data transmission in the cross-standard access scenario is ensured.
  • the IAB node determining the DSCP or flow label corresponding to the downlink data includes: the IAB node, according to the tunnel identifier and the mapping relationship between the tunnel identifier and the DSCP, determine the DSCP; or, the IAB node determines the flow label according to the tunnel identifier and the mapping relationship between the tunnel identifier and the flow label.
  • the IAB node receives the tunnel identifier and the DSCP from the IAB host node, where the tunnel identifier corresponds to the DSCP; or, the IAB node receives the tunnel identifier and the DSCP from the IAB host node; The IAB host node receives the tunnel identifier and the flow label, wherein the tunnel identifier corresponds to the flow label.
  • the IAB node determining the DSCP or flow label corresponding to the downlink data includes: the IAB node receiving an adaptation layer packet from the IAB host node, the adaptation layer packet carrying The DSCP or flow label.
  • the IAB node sending the downlink data to the UE includes: the IAB node sending a data packet to the UE, the data packet carrying the downlink data, and carrying the tunnel identifier corresponding to At least one of the data radio bearer identification DRB ID, the evolved general land-based radio access network radio access bearer identification E-RAB ID or the quality of service flow identification QFI.
  • an embodiment of the present application provides a communication method, comprising: a first device receiving at least two data packets from a second device, wherein each data packet carries a GTP sequence number of the General Packet Radio Service Tunneling Protocol GTP layer; The first device reorders the at least two data packets according to the GTP sequence number of the GTP layer; the first device is an integrated IAB node for access and backhaul, and the second device is an IAB host node or, the first device is an IAB host node, and the second device is an IAB node.
  • the IAB node is an access IAB node of the user equipment.
  • the first device receives indication information from the second device, and the indication information is used for Instruct the GTP layer of the first device to enable or disable the reordering function.
  • the first device if the first device is an IAB host node and the second device is an IAB node, the first device sends indication information to the second device, where the indication information is used for Instruct the GTP layer of the second device to enable or disable the reordering function.
  • an embodiment of the present application provides a communication method, comprising: a user equipment UE receiving a service bearer identifier and indication information of the UE from an integrated access and backhaul IAB donor node, where the indication information is used to indicate the The packet data convergence protocol PDCP entity corresponding to the service bearer identifier enables or disables the reordering function; the UE enables or disables the reordering function of the PDCP entity according to the service bearer identifier and the indication information; wherein, the UE For Long Term Evolution LTE UEs, the UEs access the network through a new wireless NR backhaul link.
  • the indication information corresponds to the service bearer identifier
  • the service bearer identifier is a data radio bearer identifier DRB ID.
  • an embodiment of the present application provides a communication method, including: an IAB node determining a type of user equipment UE or a type of a core network to be accessed by the UE; the IAB node is an access IAB node of the UE.
  • the IAB node sends first indication information to the IAB donor node, where the first indication information is used to indicate the type of the UE, or used to indicate the type of the core network to be accessed by the UE, or used to indicate Whether the UE accesses the NR core network, or is used to indicate whether the UE accesses the LTE core network, and the first indication information is used for the IAB donor node to select the access core network for the UE.
  • the problem of how the IAB host node selects the corresponding core network equipment for the UE is solved, so that in the cross-standard access scenario, the IAB host node selects the corresponding core network for the UE according to the received indication information, which can ensure that the UE The normal operation after accessing the network ensures the normal transmission of user equipment data in cross-standard access scenarios.
  • the IAB node determining the type of the UE includes: the IAB node determines the type of the UE according to the frequency of the cell accessed by the UE; or, the IAB node determines the type of the UE from the The UE receives second indication information, where the second indication information is used to indicate the type of the UE.
  • the IAB node determining the type of the core network to be accessed by the UE includes: the IAB node receiving third indication information from the UE, where the third indication information is used for Indicates the type of the core network to be accessed by the UE, or is used to indicate whether the UE accesses the NR core network, or is used to indicate whether the UE accesses the LTE core network.
  • the type of the UE is Long Term Evolution LTE UE or New Radio NR UE.
  • an embodiment of the present application provides a communication method, including: an IAB host node receiving first indication information; and the IAB host node determining an access standard used by an air interface of a user equipment UE according to the first indication information.
  • the IAB donor node can determine the access standard used by the UE air interface according to the received first indication information, so that it can configure different UE configurations according to the known access standard used by the UE air interface.
  • the bearer mapping strategy ensures the normal operation of the UE after accessing the network, and ensures the normal transmission of user equipment data in the cross-standard access scenario.
  • the receiving, by the IAB donor node, the first indication information includes: the IAB donor node receiving a first RRC message from the UE, where the first RRC message carries the first indication information or, the IAB host node receives an F1AP message from an IAB node accessed by the UE, where the F1AP message carries the first indication information.
  • the IAB donor node sends a second RRC message to the UE, where the second RRC message carries second indication information, and the second indication information is used to indicate the IAB donor node
  • An access standard used by the UE over the air interface is determined, and the determined access standard used by the air interface is used for the UE to access the network according to the determined access standard.
  • an embodiment of the present application provides a communication apparatus, and the apparatus may be a user equipment, and may also be a chip used for the user equipment.
  • the apparatus has the function of implementing the first aspect or the fifth aspect, or each possible implementation method of the first aspect, or each possible implementation method of the fifth aspect. This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, where the device may be an IAB node, or a chip for an IAB node.
  • the device has a device for realizing the second aspect or the third aspect or the sixth aspect, or each possible implementation method of the second aspect, or each possible implementation method of the third aspect, or each possible implementation method of the sixth aspect.
  • This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication apparatus, and the apparatus may be a first device or a chip used for the first device.
  • the apparatus has the function of implementing the above-mentioned fourth aspect, or each possible implementation method of the fourth aspect. This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, and the device may be an IAB host node or a chip used for an IAB host node.
  • the device has the function of implementing the seventh aspect or each possible implementation method of the seventh aspect. This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, including a processor and a memory; the memory is used to store computer-executed instructions, and when the device is running, the processor executes the computer-executed instructions stored in the memory, to The apparatus is caused to perform the methods of the first aspect to the seventh aspect, and any method among the possible implementation methods of the first aspect to the seventh aspect.
  • an embodiment of the present application provides a communication device, including the method for performing the above-mentioned first aspect to the seventh aspect, and each step of any method among the possible implementation methods of the first aspect to the seventh aspect units or means.
  • an embodiment of the present application provides a communication device, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the methods of the first to seventh aspects above.
  • the first Any of the possible implementation methods of the aspects to the seventh aspect.
  • the processor includes one or more.
  • an embodiment of the present application provides a communication device, including a processor, which is connected to a memory and used to call a program stored in the memory to execute the methods of the first to seventh aspects. Any of the possible implementation methods of the one aspect to the seventh aspect.
  • the memory may be located within the device or external to the device.
  • the processor includes one or more.
  • the embodiments of the present application further provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the processor causes the processor to execute the above-mentioned first to seventh aspects
  • the method of the aspect is any method among the possible implementation methods of the first aspect to the seventh aspect.
  • an embodiment of the present application further provides a computer program product, the computer product includes a computer program, when the computer program runs, the methods of the first to seventh aspects above, the first to seventh aspects Any of the possible implementations are executed.
  • an embodiment of the present application further provides a chip system, including: a processor configured to execute the methods of the first aspect to the seventh aspect, and one of the possible implementation methods of the first aspect to the seventh aspect any method.
  • Figure 1 is a diagram of the separation architecture of gNB-CU and gNB-DU in NR;
  • Figure 2 is a schematic diagram of a control plane protocol stack under the gNB's CU-DU separation architecture
  • FIG. 3 is a schematic diagram of the user plane protocol stack under the CU-DU separation architecture adopted by the gNB;
  • FIG. 4 is a schematic diagram of a two-hop data return scenario
  • 5 is a schematic diagram of a control plane protocol stack for two-hop data backhaul
  • FIG. 6 is a schematic diagram of a user plane protocol stack for two-hop data backhaul
  • FIG. 7 is a schematic diagram of data transmission in two-hop data return
  • FIG. 8 is a schematic diagram of a home access network
  • FIG. 9 is a schematic diagram of a network architecture to which an embodiment of the present application is applied.
  • Figure 10 is the control plane protocol stack architecture when LTE/NR UE accesses the network through the WLAN standard
  • Fig. 11 is the user plane protocol stack architecture when the LTE/NR UE accesses the network through the WLAN standard;
  • FIG. 12 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • 13 is a schematic diagram of the format design of the adaptation layer
  • FIG. 14 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 15 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 16 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 17 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of yet another communication method provided by an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a communication device according to an embodiment of the present application.
  • FIG. 21 is a schematic diagram of another communication device provided by an embodiment of the present application.
  • FIG. 22 is a schematic diagram of a user equipment according to an embodiment of the present application.
  • the gNB can adopt the Central Unit (CU)-Distributed Unit (DU) separation architecture, that is: the gNB consists of a The gNB-CU and one or more gNB-DUs are composed. Among them, the gNB-CU and the gNB-DU are connected through the F1 interface, and the gNB-CU and the fifth generation (5th generation, 5G) core network are connected through the NG interface. As shown in Figure 1, it is a diagram of the separation architecture of gNB-CU and gNB-DU in NR.
  • CU Central Unit
  • DU Distributed Unit
  • the gNB is a node that provides NR user plane and control plane transmission for user equipment (User Equipment, UE), and the gNB includes one or more cells.
  • the gNB is connected to the 5G core network (5G core, 5GC) through the NG interface, and is connected to other gNBs through the Xn interface.
  • the Xn-C interface is used for the transmission of control plane signaling between two gNBs
  • the Xn-U interface is used for the transmission of user plane data between the two gNBs.
  • the interface between the gNB and the UE is called the Uu interface.
  • the communication interface between the UE and the base station (eg, gNB, eNB) or the DU accessing the IAB node may be called an air interface.
  • gNB-CU is a logical node, gNB-CU includes gNB Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP) layer and Packet Data Convergence Protocol (Packet Data Convergence Protocol) , PDCP) layer, used to control one or more gNB-DUs.
  • RRC Radio Resource Control
  • SDAP Service Data Adaptation Protocol
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • PDCP Packet Data Convergence Protocol
  • gNB-DU is a logical node, and gNB-DU includes the radio link control (Radio Link Control, RLC) layer, medium access control (medium access control, MAC) layer and physical layer (Physical layer, PHY) layer of gNB.
  • RLC Radio Link Control
  • MAC medium access control
  • PHY Physical layer
  • the UE accesses the gNB-CU through the gNB-DU, that is, the PHY/MAC/RLC layer functions equivalent to the UE are located on the gNB-DU, and the PDCP/SDAP/RRC layer functions equivalent to the UE are located on the gNB-CU.
  • FIG. 2 it is a schematic diagram of the control plane protocol stack under the gNB adopting the CU-DU separation architecture.
  • the gNB-DU encapsulates the RRC message generated by the UE in an F1 interface application protocol (F1 Application Protocol, F1AP) message and sends it to the gNB-CU.
  • F1AP Application Protocol
  • the gNB-CU encapsulates the RRC message in the F1AP message and sends it to the gNB-DU.
  • the gNB-DU extracts the RRC message from the F1AP message and maps it to the signaling radio bearer corresponding to the Uu interface. bearer, SRB) (SRB0/SRB1/SRB2) and sent to the UE.
  • SRB signaling radio bearer
  • FIG. 3 it is a schematic diagram of the user plane protocol stack under the CU-DU separation architecture adopted by the gNB.
  • the gNB-DU maps the UE data packets received from the Uu interface Data Radio Bearer (DRB) to the corresponding General Packet Radio Service (GPRS)
  • the tunneling protocol (GPRS Tunneling Protocol, GTP) is sent to the gNB-CU in the tunnel.
  • the gNB-CU maps the UE data packet to the corresponding GTP tunnel and sends it to the gNB-DU.
  • the gNB-DU extracts the UE data packet from the GTP tunnel and maps the UE data packet to the DRB corresponding to the Uu interface. sent to the UE.
  • IAB node IAB node
  • IAB donor IAB host node, or host IAB node
  • IAB donor can be a gNB, or an upgraded gNB.
  • IAB donor consists of IAB donor-CU (donor-CU for short) and IAB donor-DU (donor-DU for short)
  • IAB node consists of IAB node-MT (abbreviated as IAB-DU).
  • IAB-DU IAB node-MT
  • IAB-DU IAB node-DU
  • IAB node-MT can also be called IAB node-UE (abbreviated as IAB-UE).
  • donor-DU the function of donor-DU is similar to that of gNB-DU
  • donor-CU the function of donor-CU is similar to that of gNB-CU.
  • the IAB-DU is similar in function to the gNB-DU and is used to provide access services to its child nodes, where the child nodes of the IAB-DU can be UEs or other IAB nodes.
  • IAB-MT has the function of UE to provide data backhaul to its child nodes.
  • the IAB node can be further divided into the access IAB node and the intermediate IAB node, namely: the IAB node accessed by the UE is called the access IAB node, and the IAB node on the path between the access IAB node and the IAB donor is called the intermediate IAB node. .
  • IAB node2 when the UE accesses IAB node2, the IAB node2 is called the access IABnode of the UE (or the parent node of the UE), the UE is called the child node of the IAB node2, and the link between the UE and the IAB node2 is called access link.
  • IAB node1 is called an intermediate IAB node, the parent node of IAB node1 is IAB donor (the child node of IAB donor is IAB node1), and the child node of IAB node1 is IAB node2 (the parent node of IAB node2 is IAB node1).
  • the link between IAB node1 and IAB node2, and the link between IAB node1 and IAB donor are called backhaul links.
  • the PHY layer, MAC layer and RLC layer equivalent to the UE are located on the access IAB node (ie: IAB2-DU), and the PDCP layer, SDAP layer and RRC layer equivalent to the UE are located on the donor-CU.
  • IAB nodes all adopt the architecture of L2 data forwarding.
  • FIG. 5 it is a schematic diagram of a control plane protocol stack for two-hop data backhaul.
  • An F1 interface is established between the access IAB node (ie: IAB2-DU) and the IAB donor (ie: donor-CU).
  • the IAB donor ie: donor-CU.
  • the F1-C interface is established between the IAB2-DU and the donor CU-CP.
  • the RRC message of the UE is encapsulated and transmitted in the F1AP message of the F1-C interface.
  • FIG. 6 it is a schematic diagram of a user plane protocol stack for two-hop data backhaul.
  • the IAB donor adopts the CP-UP separation architecture
  • an F1-U interface is established between the IAB2-DU and the donor CU-UP
  • a GTP tunnel per UE bearer is established on the F1-U interface. That is to say, each UE DRB established on the interface between the UE and the IAB2-DU corresponds to a separate GTP tunnel on the interface between the IAB2-DU and the donor CU-UP.
  • FIG. 7 it is a schematic diagram of data transmission in the two-hop data backhaul.
  • Multiple UE DRBs are established on the interface link between the UE and the IAB node2 to transmit different services of the UE.
  • Multiple backhaul RLC channels (Backhaul RLC Channel, BH RLC CH) are established on the backhaul link between IAB node2 and IAB node1 to transmit backhaul of different UE services.
  • multiple BH RLC CHs are also established on the backhaul link between IAB node1 and IAB donor.
  • a GTP tunnel per UE bearer is established between the IAB node2 and the IAB donor CU, and each GTP tunnel corresponds to the UE DRB on the interface between the UE and the IAB node2 one-to-one.
  • Donor-CU maps the UE PDCP protocol data unit (protocol data unit, PDU) to the corresponding GTP tunnel, and determines the target Internet protocol (internet protocol, IP) address of the UE data packet (that is, the IP address of the IAB node2 ), further encapsulate the UE data packet into an IP packet, and mark the corresponding differentiated services code point (Differentiated Services Code Point, DSCP) or flow label (flow label) in the IP header field, and fill in the target IP of the IP packet After address, it is sent to Donor-DU through IP routing.
  • DSCP is used to identify the type of service in Internet Protocol version 4 (Internet Protocol version 4, IPv4)
  • the flow label is used to identify the type of service in Internet Protocol version 6 (Internet Protocol version 6, IPv6).
  • the Donor-DU maps the received UE IP packet to the corresponding BH RLC CH according to the DSCP or flow label and the target IP address carried in the IP header and according to the mapping relationship 1 configured by the Donor-CU and sends it to the IAB node1.
  • the mapping relationship 1 configured by the Donor-CU for the Donor-DU includes: the mapping relationship between the parameter and the BH RLC CH, and the parameter is composed of one or more of the following combinations, including: DSCP, flow label, and target IP address.
  • the IAB node1 maps the received UE IP packet to the corresponding BH RLC CH according to the mapping relationship 2 configured by the Donor-CU and sends it to the IAB node2.
  • the mapping relationship 2 configured by Donor-CU for IAB node1 includes: the mapping relationship between ingress BH RLC CH (ingress BH RLC CH) and egress BH RLC CH (egress BH RLC CH).
  • the ingress BH RLC CH is the BH RLC CH between IAB node1 and IAB donor DU
  • the egress BH RLC CH is the BH RLC CH between IAB node1 and IAB node2.
  • IAB node2 sends the received UE IP packet to the GTP layer for analysis, extracts the UE PDCP PDU from the GTP tunnel, and maps the UE PDCP PDU to the mapping relationship between the GTP tunnel and the UE DRB configured by the Donor-CU. It is sent to the UE on the corresponding UE DRB.
  • the UE maps the UE PDCP PDU to the corresponding UE DRB and sends it to the IAB node2.
  • the IAB node2 maps the UE PDCP PDU to the corresponding GTP tunnel according to the mapping relationship between the GTP tunnel configured by the Donor-CU and the UE DRB. Then, according to the mapping relationship 3 configured by Donor-CU, IAB node2 further encapsulates UE data packets into IP packets, maps them to the corresponding BH RLC CH, and sends them to IAB node1.
  • the mapping relationship 3 configured by the Donor-CU includes: the mapping relationship between the GTP tunnel (ie: GTP TEID and IP address) and the BH RLC CH, and the IP address is the IP address of the donor-CU.
  • the IAB node1 maps the received UE IP packet to the corresponding BH RLC CH according to the mapping relationship 4 configured by the Donor-CU and sends it to the Donor-DU.
  • the mapping relationship 4 configured by Donor-CU for IAB node1 includes: the mapping relationship between ingress BH RLC CH (ingress BH RLC CH) and egress BH RLC CH (egress BH RLC CH).
  • the ingress BH RLC CH is the BH RLC CH between IAB node2 and IAB node1
  • the egress BH RLC CH is the BH RLC CH between IAB node1 and IAB donor DU.
  • the Donor-DU further routes the UE IP packet to the Donor-CU according to the target IP address in the UE IP packet header (ie: the IP address of the Donor-CU). After Donor-CU sends the IP packet to the GTP layer for analysis, it extracts the UE PDCP PDU from the GTP tunnel.
  • the access link and the backhaul link use the same access mode, both of which are NR access modes, and do not consider how to implement bearer mapping for UE data transmission in scenarios of different access modes, including: Uplink direction and downlink direction, so as to realize the QoS guarantee of UE service in the whole data transmission process.
  • the non-3GPP includes: WLAN access standard, Bluetooth access standard, zigbee access standard, etc., how to realize UE uplink and Bearer mapping for downlink data transmission, so as to achieve QoS guarantee for UE services in the entire data transmission process.
  • Question 4 In the scenario of different access standards, how to know the access system used by the air interface of the UE.
  • the UE performs uplink bearer mapping, and the Donor-CU configures at least one of the following mapping relationships for the UE:
  • the mapping relationship is DRB ID/E-RAB ID ⁇ ->DSCP/flow label. "/" means or, so you can configure at least one of the following four mapping relationships: a) DRB ID ⁇ ->DSCP, b)DRB ID ⁇ ->flow label, c)E-RAB ID ⁇ - >DSCP, d) E-RAB ID ⁇ ->flow label.
  • E-RAB is Evolved Universal Terrestrial Radio Access Network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN)-Radio Access Bearer.
  • the mapping relationship is DRB ID/QFI ⁇ ->DSCP/flow label. That is, at least one of the following four mapping relationships can be configured: a) DRB ID ⁇ ->DSCP, b)DRB ID ⁇ ->flow label, c)QFI ⁇ ->DSCP, d)QFI ⁇ ->flow label .
  • the quality of service Quality of Service, QoS
  • QoS flow identity QoS flow identity
  • the Donor-CU configures the uplink mapping relationship for the IAB-node, including: DSCP/flow label ⁇ ->GTP TEID. That is, at least one of the following two mapping relationships can be configured: a) DSCP ⁇ ->GTP TEID, b) flow label ⁇ ->GTP TEID.
  • the UE carries the DSCP/flow label corresponding to the uplink data in the adaptation layer, and sends it to the IAB-node together with the uplink data.
  • Donor-CU configures the uplink mapping relationship for IAB-node, including: DRB ID ⁇ ->GTP TEID.
  • the UE carries the DRB ID corresponding to the uplink data in the adaptation layer, and sends it to the IAB-node together with the uplink data.
  • the Donor-CU determines the DSCP/flow label corresponding to the UE service type, and carries the determined DSCP/flow label value in the adaptation layer and sends it to the IAB- node.
  • the UE service type can be represented by DRB ID, E-RAB ID or GTP TEID.
  • the downlink mapping relationship configured by Donor-CU for IAB-node includes: UE service type ⁇ -> DSCP/flow label.
  • mapping relationships can be configured: a) DRB ID ⁇ ->DSCP, b)DRB ID ⁇ ->flow label, c)E-RAB ID ⁇ ->DSCP, d)E-RAB ID ⁇ ->flow label, e)GTP TEID ⁇ ->DSCP, f)GTP TEID ⁇ ->flow label.
  • the reordering function is introduced into the GTP layer between the access IAB-DU and the Donor-CU, or the Donor-CU sends indication information to the UE, where the indication information is used to indicate whether the UE enables the PDCP reordering function.
  • the indication information may be indicated by per DRB.
  • the access IAB-node sends indication information to the Donor-CU through the F1AP message, and the indication information is used to indicate the type of the access UE, or is used to indicate the type of the UE to be accessed to the core network. Or used to indicate whether the UE accesses the LTE core network or is used to indicate whether the UE accesses the NR core network.
  • the UE selects an access mode to access the IAB-node.
  • the UE can send the indication information to the Donor-CU through an RRC message, or the access IAB-node sends the indication to the Donor-CU through an F1AP message information, used to indicate the access standard used by the air interface of the UE.
  • the Donor-CU may further send the determined access standard used by the UE air interface to the UE through an RRC message, so that the UE can update the access standard used by the air interface.
  • the standard used by the UE to access the network may also be called an access standard, and the access technology corresponding to the access standard may also be called an air interface technology or an air interface access technology.
  • the embodiments of the present application can be applied to a scenario of an IAB network, and can also be applied to a scenario of a home access (Home Access) network.
  • a home access Home Access
  • LTE UE or NR UE can access the IAB node through WLAN standard, LTE standard, NR standard, Bluetooth standard, zigbee and other standards.
  • the embodiments of this application are mainly aimed at the improvement when an LTE UE or an NR UE accesses an IAB node through a WLAN standard, a Bluetooth standard, or a zigbee standard.
  • a home access node HAP Home Access Point
  • IAB node in the form of a base station
  • CPE in the form of a UE
  • There are various access standards between the HAP and a home device such as UE
  • UE home device
  • LTE Long Term Evolution
  • NR Universal Terrestrial
  • WLAN Wireless Fidelity
  • Bluetooth Bluetooth
  • zigbee and so on.
  • the communication between the HAP and the UE is performed through a sidelink.
  • the backhaul is carried out between the HAP and the base station through the NR standard.
  • FIG. 8 it is a schematic diagram of a home access network.
  • FIG. 9 it is a schematic diagram of a network architecture to which this embodiment of the present application is applied.
  • LTE UE or NR UE can access to IAB node or HAP through WLAN, LTE, NR, Bluetooth, zigbee and other standards.
  • the embodiments of this application are mainly aimed at the improvement when LTE UE or NR UE accesses to IAB node or HAP through WLAN, Bluetooth, and zigbee.
  • LTE UE accesses the IAB-node (or HAP) through the LTE access standard, and accesses the IAB-donor (or gNB) through the NR backhaul link, and then connects to the evolved packet core network (Evolved) through the S1 interface. Packet Core, EPC).
  • IAB-node or HAP
  • IAB-donor or gNB
  • EPC evolved packet core network
  • NR UE accesses the IAB-node (or HAP) through the NR access standard, and accesses the IAB-donor (or gNB) through the NR backhaul link, and then connects to the 5GC through the NG interface.
  • IAB-node or HAP
  • IAB-donor or gNB
  • LTE UE accesses IAB-node (or HAP) through WLAN access standard, Bluetooth access standard, zigbee access standard, and accesses IAB-donor (or gNB) through NR backhaul link, and then through S1
  • IAB-node or HAP
  • WLAN access standard Wireless Fidelity
  • Bluetooth access standard or zigbee access standard
  • IAB-donor or gNB
  • NR UE accesses IAB-node (or HAP) through WLAN access standard, Bluetooth access standard, zigbee access standard, and accesses IAB-donor (or gNB) through NR backhaul link, and then through NG
  • IAB-node or HAP
  • WLAN access standard Wireless Fidelity
  • Bluetooth access standard or zigbee access standard
  • IAB-donor or gNB
  • the Rel-16IAB architecture can be used for implementation, so no corresponding changes are made in this embodiment of the present application.
  • the LTE UE or NR UE accesses the IAB node through the WLAN standard as an example for description.
  • the implementation method of the LTE UE or NR UE accessing the IAB node through the Bluetooth or zigbee standard is the same as that of the LTE UE.
  • the method for the UE or NR UE to access the IAB node through the WLAN standard is the same, and will not be repeated here.
  • This embodiment is used to solve the above problem 1. Specifically, in the WLAN access mode, the Bluetooth access mode, and the zigbee access mode, how to realize the bearer mapping of the UE uplink and downlink data transmission, so as to realize the UE service in the entire data transmission QoS guarantee in the process.
  • control plane and user plane protocol stack architectures are shown in Figure 10 and Figure 11 respectively.
  • the embodiments of the present application are described by taking a single-hop backhaul link scenario as an example, and the present patent solution is also applicable to a multi-hop backhaul link scenario, which will not be repeated here.
  • the single-hop backhaul link scenario means that the parent node of the access IAB node is the IAB host, that is, there is no intermediate IAB node between the access IAB node and the IAB host.
  • the multi-hop backhaul link scenario means that there is one or more intermediate IAB nodes between the access IAB node and the IAB host. Among them, a scenario where there is one intermediate IAB node may be referred to as a two-hop backhaul link scenario, a scenario where there are two intermediate IAB nodes may be referred to as a three-hop backhaul link scenario, and so on.
  • an adaptation layer is newly introduced between the UE and the access IAB-node, which is used for different radio access technologies (Radio Access Technology, RAT). Selection/adaptation and guarantee of air interface QoS.
  • an adaptation layer is newly introduced between the access IAB-node and the IAB donor (specifically, between the access IAB-DU and the Donor-CU), which is used for the selection/adaptation of different RATs and the return Guarantee of QoS on the transmission link.
  • the uplink bearer mapping on the access link between the UE and the access IAB node is performed by the UE.
  • a communication method is provided in an embodiment of the present application.
  • the method is executed by the UE when it needs to send uplink data.
  • the method includes the following steps:
  • Step 1201 The UE determines first information corresponding to the uplink data, where the first information is used to identify the service type or bearer corresponding to the uplink data in the first standard.
  • the first information may be a DRB ID or an E-RAB ID
  • the first standard is the LTE standard
  • the first information may be a DRB ID or a QFI
  • the first format is an NR format.
  • Step 1202 the UE determines the second information according to the first information, where the second information is used to identify the service type or bearer corresponding to the uplink data under the second standard, and the second standard is different from the first standard.
  • the UE can determine the second information corresponding to the first information according to the configured mapping relationship between the first information and the second information .
  • the UE receives an RRC message (such as an RRC reconfiguration message) from the IAB donor node, and the RRC message carries first information and second information, and the first information corresponds to the second information, so that the UE can obtain the first information and the second information.
  • RRC message such as an RRC reconfiguration message
  • the second information may be a DSCP or a flow label.
  • the second standard is one of WLAN, Bluetooth or zigbee.
  • mapping relationship between the first information and the second information configured by the Donor-CU for the UE is as follows:
  • mapping relationships can be configured for the LTE UE:
  • one PDCP entity uniquely corresponds to one DRB ID, and uniquely corresponds to one E-RAB ID.
  • mapping relationships can be configured for the NR UE:
  • one PDCP entity uniquely corresponds to one DRB ID
  • one QFI uniquely corresponds to one PDCP entity.
  • Step 1203 the UE sends uplink data using the air interface technology of the second standard according to the second information.
  • the UE sends uplink data using the air interface technology of the second standard according to the second information, which can also be understood as the UE performing QoS control according to the second information.
  • the second information may be carried in the uplink data packet.
  • the UE uses the same standard to access the network (for example, both are the first standard, which can be NR or LTE specifically, that is, the LTE UE accesses the network through the LTE standard, and the NR UE accesses the network through the NR standard),
  • the UE sends uplink data by using the air interface technology of the first standard according to the first information.
  • the UE of the first standard accesses the network through the air interface technology of the second standard (for example, the second standard is WLAN, that is, the LTE UE or the NR UE accesses the network through the WLAN standard)
  • the second standard does not recognize the first information and cannot perform QoS guarantee for data transmission
  • the UE cannot use the air interface technology of the second standard to perform QoS guaranteed uplink data transmission according to the first information.
  • the UE of the present application obtains the second information that can be identified by the second standard according to the first information, so that the UE can use the air interface technology of the second standard to send uplink data according to the second information, which ensures the data of the user equipment in the cross-standard access scenario. QoS guarantee of transmission.
  • the UE continues to use the existing mechanism to map the uplink data (ie: IP packet) to the PDCP entity corresponding to the PDCP layer for processing, and obtain processed uplink data (ie: PDCP PDU).
  • the PDCP entity corresponds to the service bearer identifier (such as DRB ID/E-RAB ID/QFI), and the adaptation layer of the UE receives the processed uplink data from the upper layer of the adaptation layer (that is, the PDCP entity of the PDCP layer).
  • the adaptation layer of the UE determines the DSCP/flow label value corresponding to the DRB ID/E-RAB ID/QFI, that is, the adaptation layer of the UE can determine the DSCP/flow label corresponding to the processed uplink data. value.
  • the adaptation layer of the UE sends control information to the lower layer of the adaptation layer (such as WLAN L2 as an example), and the control information is used to indicate the DSCP/flow label value, or it is understood as being used to indicate that the processed uplink data corresponds to DSCP/flow label value.
  • the WLAN L2 of the UE After receiving the DSCP/flow label value indicated by the control information, the WLAN L2 of the UE performs the QoS guarantee of UE services according to the DSCP/flow label according to the existing WLAN mechanism. Specifically, the UE's WLAN L2 uses the existing mechanism to identify UE services and ensure service QoS according to the acquired DSCP/flow label value.
  • the advantage of this is that the upper layer data transmission can shield the underlying access technology, as long as the underlying access technology (for example: WLAN, zigbee, Bluetooth, etc.) can be used to identify UE services through DSCP/flow label.
  • the adaptation layer of the UE receives the uplink data (that is, the PDCP PDU) processed by the upper layer from the upper layer of the adaptation layer (that is, the PDCP entity of the PDCP layer), the PDCP entity and the The service bearer identifier (such as DRB ID/E-RAB ID/QFI) corresponds, and then the UE determines the DSCP/flow label value corresponding to the DRB ID/E-RAB ID/QFI according to the mapping relationship configured by the Donor-CU, that is The adaptation layer of the UE can determine the DSCP/flow label value corresponding to the processed uplink data.
  • the uplink data that is, the PDCP PDU
  • the adaptation layer that is, the PDCP entity of the PDCP layer
  • the service bearer identifier such as DRB ID/E-RAB ID/QFI
  • the adaptation layer of the UE adds an adaptation layer header to the processed uplink data to obtain an adaptation layer packet, where the adaptation layer packet carries the adaptation layer header and the processed uplink data, and the adaptation layer header carries the adaptation layer header and the processed uplink data.
  • DSCP/flow label optional, this adaptation layer header also carries DRB ID/E-RAB ID/QFI.
  • the adaptation layer of the UE sends the adaptation layer packet to the lower layer of the adaptation layer (such as WLAN L2), and the WLAN L2 of the UE extracts the DSCP/flow label value from the received adaptation layer packet according to the existing mechanism. Perform QoS guarantee for UE services.
  • the UE's WLAN L2 uses the existing mechanism to identify UE services and ensure service QoS according to the acquired DSCP/flow label value.
  • the advantage of this is that the upper layer data transmission can shield the underlying access technology, as long as the underlying access technology (for example: WLAN, zigbee, Bluetooth, etc.) can be used to identify UE services through DSCP/flow label.
  • the format design of the adaptation layer is shown in FIG. 13 .
  • R is a reserved field.
  • the Version field occupies 4 bits.
  • the adaptation layer adopts the format design on the left
  • the value of the version field is 6, the adaptation layer adopts the format design on the right.
  • the figure takes the DSCP and DRB ID carried by the adaptation layer packet as an example for description.
  • the DSCP field is fixed to occupy 6 bits from the second byte, and the DSCP field is followed by the 5-bit DRB ID.
  • the adaptation layer adopts the format design on the right the Flow label field is fixed to occupy 20 bits from the 4th bit in the second byte, and the version field is followed by the 5-bit DRB ID.
  • the uplink bearer mapping on the backhaul link between the access IAB node and the Donor-DU is performed by the access IAB node. Specifically, the uplink bearer mapping is performed by accessing the IAB-MT.
  • a communication method is provided in an embodiment of the present application.
  • the method is executed by the access IAB node when it needs to send uplink data.
  • the access IAB node (access IAB node) here is the IAB node accessed by the UE.
  • access IAB node access IAB node
  • the method includes the following steps:
  • Step 1401 the access IAB node receives a data packet from the UE, where the data packet carries uplink data and carries the first information and/or the second information.
  • the first information is used to identify the service type or bearer corresponding to the uplink data in the first mode
  • the second information is used to identify the service type or bearer corresponding to the uplink data in the second mode
  • the second mode is different from the first mode .
  • the first information may be DRB ID or E-RAB ID
  • the second information may be DSCP or flow label
  • the first standard is LTE standard
  • the second standard is WLAN
  • the first information may be DRB ID or QFI
  • the second information may be DSCP or flow label
  • the first standard is NR standard
  • the second standard is WLAN, Bluetooth or zigbee. A sort of.
  • Step 1402 the access IAB node determines the tunnel identifier of the GTP tunnel according to the first information or the second information, where the tunnel identifier includes the GTP TEID, or the GTP TEID and the IP address.
  • the access IAB node can determine the identifier of the GTP tunnel corresponding to the first information according to the mapping relationship between the configured first information and the identifier of the GTP tunnel .
  • the access IAB node can receive an RRC message or an F1AP message from the IAB donor, and the RRC message or F1AP message carries first information and a tunnel identifier, and the first information corresponds to the tunnel identifier, so that the access IAB node can obtain the The mapping relationship between the first information and the tunnel identifier.
  • the access IAB node when the data packet received by the access IAB node from the UE carries the second information, the access IAB node can determine the GTP tunnel corresponding to the second information according to the mapping relationship between the configured second information and the identifier of the GTP tunnel. logo.
  • the access IAB node can receive an RRC message or an F1AP message from the IAB donor, and the RRC message or F1AP message carries the second information and the tunnel identifier, and the second information corresponds to the tunnel identifier, so that the access IAB node can obtain the The mapping relationship between the second information and the tunnel identifier.
  • Step 1403 access the IAB node to map the uplink data to the GTP tunnel corresponding to the tunnel identifier and send it to the IAB donor.
  • the UE sends the uplink data to the access IAB node through the DRB, and then the access IAB node maps the uplink data to the corresponding GTP tunnel according to the mapping relationship between the configured GTP tunnel and the UE DRB.
  • the WLAN air interface of the UE does not send uplink data to the access IAB node through the DRB. Therefore, in the prior art, the access The IAB node cannot determine which GTP tunnel the received uplink data needs to be placed in.
  • the first information can be carried in the data packet, and the mapping relationship between the first information and the tunnel identifier of the GTP tunnel can be configured on the access IAB node, or the second information can be carried in the data packet, and The mapping relationship between the second information and the tunnel identifier of the GTP tunnel is configured on the access IAB node, so that the access IAB node can determine the mapping relationship based on the configured mapping relationship and the first information or the second information obtained from the data packet.
  • This data packet corresponds to the GTP tunnel, so that the uplink data is mapped to the GTP tunnel and sent to the IAB host node, which realizes the correct transmission of the data and ensures the QoS guarantee of user equipment data transmission in the cross-standard access scenario.
  • the UE carries the first information (which may be DRB ID/E-RAB ID/QFI) corresponding to the uplink data in the adaptation layer, and sends it to the access IAB node together with the uplink data.
  • the access IAB node maps the uplink data to the corresponding GTP tunnel according to the uplink mapping relationship configured by the Donor-CU, and then maps it to the corresponding egress BH RLC CH and sends it to the Donor-DU.
  • the uplink mapping relationship configured by Donor-CU includes: DRB ID/E-RAB ID/QFI ⁇ ->tunnel identifier, and tunnel identifier ⁇ ->egress BH RLC CH.
  • the egress BH RLC CH is the backhaul RLC channel between the IAB node and the Donor-DU.
  • the access IAB node learns the DRB ID/E-RAB ID/QFI corresponding to the uplink data according to the DRB ID/E-RAB ID/QFI carried in the adaptation layer, and then according to the DRB ID configured by the Donor-CU /E-RAB ID/QFI ⁇ ->The mapping relationship of tunnel identifier, map the uplink data to the corresponding GTP tunnel, and then according to the mapping relationship of tunnel identifier ⁇ ->egress BH RLC CH configured by Donor-CU, convert the The uplink data mapped to the GTP tunnel is further mapped to the corresponding BH RLC CH and sent to the Donor-DU.
  • the UE carries the second information (which may be DSCP/flow label) corresponding to the uplink data in the adaptation layer, and sends it to the access IAB node together with the uplink data.
  • the access IAB node maps the uplink data to the corresponding GTP tunnel according to the uplink mapping relationship configured by the Donor-CU, and then maps it to the corresponding egress BH RLC CH and sends it to the Donor-DU.
  • the uplink mapping relationship configured by Donor-CU includes: DSCP/flow label ⁇ ->tunnel identifier, and tunnel identifier ⁇ ->egress BH RLC CH.
  • the egress BH RLC CH is the backhaul RLC channel between the IAB node and the Donor-DU.
  • the access IAB node learns the DSCP/flow label corresponding to the upstream data according to the DSCP/flow label carried in the adaptation layer, and then according to the mapping relationship of the DSCP/flow label ⁇ -> tunnel label configured by the Donor-CU , map the uplink data to the corresponding GTP tunnel, and then further map the uplink data mapped to the GTP tunnel to the corresponding egress BH according to the mapping relationship of the tunnel identifier ⁇ -> egress BH RLC CH configured by the Donor-CU Sent to Donor-DU on RLC CH.
  • the above-mentioned mapping relationship may be carried in the RRC message sent by the Donor-CU to the access IAB-MT, or the above-mentioned mapping relationship may be carried in the F1AP message sent by the Donor-CU to the access IAB-DU.
  • the IAB-DU notifies the access IAB-MT of the above mapping relationship through the internal interface.
  • this application takes the example of the parent node accessing the IAB node as the IAB donor.
  • This application is also applicable to the multi-hop scenario, that is, the parent node accessing the IAB node is other IAB nodes. In this scenario, only It is only necessary to replace the Donor-DU in the above scheme 1 and scheme 2 with the DU that accesses the parent node of the IAB node.
  • the downlink bearer mapping on the access link between the UE and the access IAB node is performed by the access IAB node, and specifically, the downlink bearer mapping is performed by the access IAB-DU.
  • a communication method is provided in an embodiment of the present application. This method is executed by the access IAB node when it needs to send downlink data.
  • the access IAB node (access IAB node) here is the IAB node accessed by the UE. For the specific meaning of accessing the IAB node, reference may be made to the foregoing description.
  • the method includes the following steps:
  • Step 1501 access the IAB node to receive the downlink data sent by the IAB donor through the GTP tunnel, and the tunnel identifier of the GTP tunnel includes the GTP TEID or the GTP TEID and an IP address.
  • the access IAB node obtains downlink data from the GTP tunnel
  • the GTP tunnel is the tunnel between the access IAB node and the IAB donor.
  • Step 1502 access the IAB node to determine the DSCP or flow label corresponding to the downlink data.
  • the access IAB node can determine the DSCP or flow label corresponding to the tunnel ID according to the mapping relationship between the tunnel ID of the configured GTP tunnel and the DSCP/flow label.
  • the mapping relationship may be received by the access IAB node from the IAB donor, that is, the access IAB node receives the tunnel ID and DSCP from the IAB donor, or receives the tunnel ID and flow label, where the tunnel ID corresponds to the DSCP. , or the tunnel ID corresponds to the flow label.
  • an access IAB node can also receive an adaptation layer packet from the IAB donor.
  • the adaptation layer packet carries the downlink data and the adaptation layer header, and the adaptation layer header carries the DSCP or flow label.
  • the access IAB node can directly obtain the corresponding DSCP or flow label from the adaptation layer package.
  • Step 1503 the access IAB node sends downlink data to the UE according to DSCP or flow label.
  • the access to the IAB node is to send downlink data to the UE through the DRB.
  • the WLAN air interface accessing the IAB node cannot send downlink data to the UE through the DRB, because the WLAN standard does not recognize the DRB. Therefore, in the above solution of the present application, the access IAB node can obtain the DSCP or flow label corresponding to the downlink data packet, and send the downlink data to the UE according to the DSCP or the flow label. Since the WLAN standard can identify DSCP or flow labels, the downlink data can be sent correctly, and the QoS guarantee of user equipment data transmission in cross-standard access scenarios is ensured.
  • the downlink mapping relationship configured by the Donor-CU for accessing the IAB node includes: tunnel ID ⁇ -> DSCP/flow label.
  • the IAB node uses the existing mechanism of the air interface (such as WLAN) to identify the UE service and guarantee the service QoS according to the obtained DSCP/flow label value.
  • the existing mechanism of the air interface such as WLAN
  • the access IAB node can also carry the DRB ID/E-RAB ID/QFI corresponding to the tunnel ID in the adaptation layer and send it to the downlink data together with the downlink data. UE.
  • Donor-CU determines the downlink mapping relationship between UE service type and DSCP/flow label, and carries the corresponding DSCP/flow label value in the adaptation layer according to the downlink mapping relationship and sends it to the access IAB node together with the downlink data.
  • the UE service type can be represented by DRB ID, E-RAB ID, GTP TEID or GTP TEID+IP address. That is, the above downlink mapping relationship can be: DRB ID ⁇ ->DSCP/flow label, or, E-RAB ID ⁇ ->DSCP/flow label, or, GTP TEID ⁇ ->DSCP/flow label, or, GTP TEID+IP Address ⁇ -> DSCP/flow label.
  • the UE service type can be represented by DRB ID, QFI, GTP TEID or GTP TEID+IP address. That is, the above downlink mapping relationship can be: DRB ID ⁇ ->DSCP/flow label, or, QFI ⁇ ->DSCP/flow label, or, GTP TEID ⁇ ->DSCP/flow label, or, GTP TEID+IP address ⁇ - >DSCP/flow label.
  • the Donor-CU After the Donor-CU determines the mapping relationship between the UE service type and the DSCP/flow label, it carries the corresponding DSCP/flow label value in the adaptation layer and sends it to the access IAB node together with the downlink data.
  • the DSCP/flow label is extracted from the adaptation layer, and the downlink data of the UE is extracted from the GTP tunnel, and the corresponding downlink data of the UE can be obtained.
  • DSCP/flow label and then access to the IAB node (that is, access to the IAB-DU) follows the existing mechanism of the air interface (such as WLAN), and identifies UE services and guarantees service QoS according to the obtained DSCP/flow label value.
  • the adaptation layer accessing the IAB node adds an adaptation layer header to the downlink data to obtain an adaptation layer packet, where the adaptation layer packet carries the adaptation layer header and the downlink data.
  • the dispensing head carries the DSCP/flow label.
  • the adaptation layer that accesses the IAB node sends the adaptation layer packet to the lower layer of the adaptation layer (such as WLAN L2), and the WLAN L2 that accesses the IAB node (that is, the IAB-DU) follows the In the existing mechanism, according to the obtained DSCP/flow label value, the UE service is identified and the QoS guarantee of the UE service is performed.
  • the access IAB node can also carry the DRB ID/E-RAB ID/QFI corresponding to the tunnel identifier in the adaptation layer with the downlink.
  • the data is further sent to the UE.
  • a scenario is designed in which the LTE/NR UE accesses the network through WLAN, Bluetooth, zigbee and other access technologies (that is, the access link adopts WLAN, Bluetooth, zigbee and other access technologies, and the backhaul link adopts NR
  • the uplink and downlink bearer mapping scheme under the access technology ensures the QoS guarantee in the UE uplink data and downlink data transmission process.
  • This embodiment is used to solve the above problem 2, specifically, how to ensure the sequential reception of UE data on the backhaul link under the WLAN, Bluetooth or zigbee standard.
  • the NR system is used between the access IAB node and the Donor-DU.
  • the NR RLC layer cancels the function of delivering data in order, so that the data received by the PDCP layer at the receiving end may be out of order.
  • the WLAN access technology since the WLAN access technology is used between the UE and the access IAB node, and the WLAN access technology uses the First Input First Output (FIFO) mechanism, thus The sequential transmission and reception of UE data on this interface can be guaranteed.
  • the NR access technology since the NR access technology is used between the access IAB node and the Donor-DU, the NR RLC layer cannot guarantee that the data of the UE will be delivered to the upper layer (NR PDCP layer) in order, resulting in the UE data received by the PDCP layer at the receiving end. out of order.
  • Scheme 1 Introduce the reordering function in the GTP layer of the access IAB node and the GTP layer of the Donor-CU.
  • a communication method is provided in an embodiment of the present application. This method is performed by the access IAB node or IAB donor.
  • the access IAB node (access IAB node) here is the IAB node accessed by the UE. For the specific meaning of accessing the IAB node, reference may be made to the foregoing description.
  • the method includes the following steps:
  • Step 1601 the first device receives at least two data packets from the second device, wherein each data packet carries a GTP sequence number of the GTP layer.
  • Step 1602 the first device reorders the at least two data packets received according to the GTP sequence number of the GTP layer.
  • the first device is the access IAB node
  • the second device is the IAB donor
  • the first device is an IAB donor
  • the second device is an access IAB node.
  • the IAB donor may send indication information to the access IAB node, where the indication information is used to instruct the GTP layer of the access IAB node to enable or disable the reordering function. Therefore, the access IAB node can enable or disable the reordering function of the GTP layer according to the indication information.
  • Solution 2 The LTE PDCP layer enables the reordering function.
  • a communication method is provided in an embodiment of the present application.
  • the method is performed by the UE.
  • the method includes the following steps:
  • Step 1701 the UE receives the service bearer identifier and indication information of the UE from the IAB donor, where the indication information is used to instruct the PDCP entity corresponding to the service bearer identifier to enable or disable the reordering function.
  • the UE is an LTE UE, and the UE accesses the network through the NR backhaul link.
  • the indication information corresponds to a service bearer identifier, and optionally, the service bearer identifier is a DRB ID.
  • Step 1702 the UE enables or disables the reordering function of the PDCP entity according to the service bearer identifier and the indication information.
  • the LTE PDCP layer enables the reordering function, and the LTE PDCP layer does not enable the reordering function in other scenarios. Since the LTE RLC layer has the function of sequentially submitting data to the upper LTE PDCP layer, it can ensure that the LTE PDCP layer receives data from the bottom layer (LTE RLC layer) in sequence.
  • the IAB donor for example, Donor-CU
  • the IAB donor learns that the LTE UE accesses the network through the NR backhaul link
  • the IAB donor enables the reordering function of the LTE PDCP layer and instructs the UE to enable the LTE PDCP layer. Reorder function.
  • the IAB donor sends an indication message to the UE, and the indication message is used to indicate whether the UE enables the PDCP reordering function.
  • the indication information is indicated by the per DRB and can be carried in the RRC message and sent.
  • each DRB corresponds to one PDCP entity, and whether to enable the reordering function is indicated for each PDCP entity.
  • This embodiment is used to solve the above problem 3, specifically, how to select access core network equipment for different types of UEs under the WLAN, Bluetooth or zigbee standard.
  • Donor-CU For LTE UE, Donor-CU needs to select LTE core network equipment, such as: control plane equipment (such as mobility management entity (MME)), user plane equipment (such as Serving GateWay, SGW) / Packet Data Network Gateway (PDN Gateway, PGW)).
  • control plane equipment such as mobility management entity (MME)
  • user plane equipment such as Serving GateWay, SGW
  • Packet Data Network Gateway PDN Gateway, PGW
  • NR core network equipment such as: control plane equipment (such as Access and Mobility Management Function (AMF) network element), user plane equipment (such as user user plane function (UPF) network element). Therefore, in the cross-standard access scenario, the Donor-CU needs to identify the type of access UE in order to select the corresponding core network.
  • AMF Access and Mobility Management Function
  • UPF user user plane function
  • a communication method is provided in an embodiment of the present application. This method is performed by the access IAB node.
  • the access IAB node (access IAB node) here is the IAB node accessed by the UE.
  • access IAB node access IAB node
  • the method includes the following steps:
  • Step 1801 the access IAB node determines the type of the UE or the type of the core network to be accessed by the UE.
  • Step 1802 the access IAB node sends first indication information to the IAB donor, where the first indication information is used to indicate the type of the UE, or the type of the core network to be accessed by the UE, or used to indicate whether the UE accesses the NR
  • the core network or used to indicate whether the UE accesses the LTE core network, and the first indication information is used by the IAB donor to select the core network to be accessed for the UE.
  • the accessing IAB node may send the first indication information to the IAB donor through an F1AP message (for example, it may be an Initial UL RRC Message Transfer message).
  • F1AP message for example, it may be an Initial UL RRC Message Transfer message.
  • the first indication information is used to indicate that the type of the UE is NR or LTE.
  • the first indication information is used to indicate that the type of the core network to be accessed by the UE is an NR core network (ie 5GC) or an LTE core network (ie EPC).
  • the first indication information is used to instruct the UE to access the NR core network, or to instruct the UE not to access the NR core network. If the UE is instructed not to access the NR core network, the IAB donor determines that the UE accesses the LTE core network.
  • the first indication information is used to instruct the UE to access the LTE core network, or to instruct the UE not to access the LTE core network. If the UE is instructed not to access the LTE core network, the IAB donor determines that the UE accesses the NR core network.
  • the problem of how the IAB donor selects the corresponding core network equipment for the UE is solved, so that in the cross-standard access scenario, the IAB donor selects the corresponding core network for the UE according to the received instruction information, which can ensure the access of the UE.
  • the normal operation behind the network ensures the normal transmission of user equipment data in cross-standard access scenarios.
  • the access IAB node may determine the type of the UE according to the frequency of the cell accessed by the UE.
  • the access IAB node receives second indication information from the UE, where the second indication information is used to indicate the type of the UE.
  • the accessing IAB node may receive third indication information from the UE, and determine the type of the core network to be accessed by the UE according to the third indication information, where the third indication information is used to indicate that the UE is to be accessed.
  • the type of the accessed core network or used to indicate whether the UE accesses the NR core network, or is used to indicate whether the UE accesses the LTE core network.
  • the embodiments of the present application are applicable to single-hop, two-hop or multi-hop backhaul link scenarios.
  • This embodiment is used to solve the above problem 4. Specifically, how does the IAB donor know the access standard used by the UE in the air interface.
  • the IAB donor needs to identify the access standard (NR, LTE, WLAN, Bluetooth, zigbee, etc.) used by the LTE/NR UE in the air interface, so as to make different bearer mapping decisions.
  • the access standard NR, LTE, WLAN, Bluetooth, zigbee, etc.
  • a communication method is provided in an embodiment of the present application. This method is performed by the IAB donor. The method includes the following steps:
  • Step 1901 the IAB donor receives the first indication information.
  • Step 1902 the IAB donor determines the access standard used by the air interface of the UE according to the first indication information.
  • the IAB donor (for example, Donor-CU) can determine the access standard used by the UE air interface according to the received first indication information, so that different bearers can be configured for the UE according to the learned access standard used by the UE air interface.
  • the mapping strategy ensures the normal operation of the UE after accessing the network, and ensures the normal transmission of user equipment data in the cross-standard access scenario.
  • the specific implementation of the above step 1901 may be, for example: the UE selects a standard to access the IAB node, the access IAB node can learn the standard used by the UE to access, and then carries the first indication information in the F1AP message sent to the IAB donor.
  • the F1AP message may be an Initial UL RRC Message Transfer message.
  • the specific implementation of the above step 1901 may be, for example: the above-mentioned first indication information is not carried by the access IAB node in the F1AP message and sent to the IAB donor, but is carried by the UE.
  • the first indication information It is sent to the IAB donor in an RRC message (for example, it can be an RRC connection establishment complete message).
  • the specific implementation of the above step 1902 may be, for example, that the first indication information is used to indicate the access standard that the UE is using, and the IAB donor agrees that the UE is using the access standard that is being used according to the first indication information.
  • the specific implementation of the above step 1902 may be, for example: the first indication information is used to indicate the access standard that the UE is using, and the IAB donor does not approve the UE to use the access standard that is being used according to the first indication information . Then the IAB donor re-determines an access mode, and sends an RRC message (for example, an RRC Release message or an RRCReconfiguration message) to the UE.
  • the RRC message carries second indication information, and the second indication information is used to instruct the IAB donor to determine the use of the air interface. Therefore, the UE determines the access standard used by the air interface according to the second indication information, and accesses the network according to the access standard used by the UE air interface determined by the IAB donor.
  • the above different embodiments can be used to solve different technical problems in the above-mentioned UE cross-standard access scenario.
  • the above-mentioned different embodiments for solving different technical problems can be implemented in combination with each other.
  • the protection scope of the present application includes not only the individual embodiments, but also the combination solutions between these different embodiments.
  • each network element in the above-mentioned implementation includes corresponding hardware structures and/or software modules for executing each function.
  • the present invention can be implemented in hardware or a combination of hardware and computer software in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.
  • the steps or operations corresponding to the steps or operations implemented by the UE may also be implemented by components (such as chips or circuits) configured in the UE, and the steps or operations corresponding to the steps or operations implemented by the IAB node may also be implemented by the UE.
  • the steps or operations implemented by the IAB host node corresponding to the steps or operations implemented by the components (eg chips or circuits) configured on the IAB node may also be implemented by the components (eg chips or circuits) configured on the IAB host node.
  • FIG. 20 it is a schematic diagram of a communication apparatus according to an embodiment of the present application.
  • the apparatus is used to implement the steps performed by the corresponding user equipment, the IAB node, and the IAB host node in the foregoing embodiments.
  • the apparatus 2000 includes a transceiver unit 2010 and a processing unit 2020 .
  • the communication apparatus 2000 is used for UE:
  • the processing unit 2020 is configured to determine first information corresponding to the uplink data, where the first information is used to identify the service type or bearer corresponding to the uplink data under the first standard; determine the second information according to the first information , the second information is used to identify the service type or bearer corresponding to the uplink data in the second standard, and the second standard is different from the first standard; the transceiver unit 2010 is configured to, according to the second information , and use the air interface technology of the second standard to send the uplink data.
  • the first information is one of a data radio bearer identification DRB ID, an evolved universal land-based radio access network radio access bearer identification E-RAB ID, or a quality of service flow identification QFI .
  • the second information is a Differentiated Services Code Point DSCP or a flow label.
  • the first standard is Long Term Evolution LTE or New Wireless NR
  • the second standard is one of wireless local area network WLAN, Bluetooth or Zigbee.
  • the processing unit 2020 configured to determine the second information according to the first information, specifically includes: according to the configured mapping relationship between the first information and the second information, The second information corresponding to the first information is determined.
  • the transceiver unit 2010 is further configured to receive a radio resource control RRC message from the integrated access and backhaul IAB donor node, where the RRC message carries the first information and the first information Two pieces of information, wherein the first information corresponds to the second information.
  • the apparatus is a UE, the UE includes an adaptation layer, and the transceiver unit 2010 is further configured to send the data to a lower layer of the adaptation layer through the adaptation layer of the UE.
  • the second information; the transceiver unit 2010 is configured to use the air interface technology of the second standard to send the uplink data according to the second information, specifically including: using the lower layer of the adaptation layer according to the first Second information, using the air interface of the second standard to send the uplink data.
  • the transceiver unit 2010 is further configured to send the second information to a lower layer of the adaptation layer through the adaptation layer of the UE, including: using the adaptation layer to send the second information to a lower layer of the adaptation layer.
  • the layer sends control information to a lower layer of the adaptation layer, where the control information is used to indicate the second information.
  • the transceiver unit 2010 is further configured to send the second information to a lower layer of the adaptation layer through the adaptation layer of the UE, including: using the adaptation layer to send the second information to a lower layer of the adaptation layer.
  • the layer adds an adaptation layer header to the uplink data, and the adaptation layer header carries the second information; it is used to send an adaptation layer packet to the lower layer of the adaptation layer through the adaptation layer, and the adaptation layer
  • the matching layer package carries the matching layer header.
  • the adaptation layer header also carries the first information.
  • the communication device 2000 is used to access the IAB node:
  • a transceiver unit 2010, configured to receive a data packet from a user equipment UE, the data packet carrying uplink data, and carrying first information and/or second information, the first information being used to identify that the uplink data is in the first
  • the service type or bearer corresponding to the standard the second information is used to identify the service type or bearer corresponding to the uplink data in the second standard, and the second standard is different from the first standard
  • the data is mapped to the General Packet Radio Service Tunneling Protocol (GTP) tunnel corresponding to the tunnel identifier and sent to the IAB host node;
  • the processing unit 2020 is configured to determine the tunnel identifier according to the first information or the second information;
  • the tunnel identifier includes the GTP TEID, or includes the GTP TEID and the Internet Protocol IP address.
  • the first information is one of a data radio bearer identification DRB ID, an evolved universal land-based radio access network radio access bearer identification E-RAB ID, or a quality of service flow identification QFI .
  • the second information is a Differentiated Services Code Point DSCP or a flow label.
  • the first standard is Long Term Evolution LTE or New Wireless NR
  • the second standard is one of wireless local area network WLAN, Bluetooth or Zigbee.
  • the processing unit 2020 configured to determine the tunnel identifier according to the first information, includes: determining the tunnel identifier according to the configured mapping relationship between the first information and the tunnel identifier. the tunnel identifier corresponding to the first information.
  • the transceiver unit 2010 is further configured to receive a radio resource control RRC message or an F1AP message from the IAB host node, where the RRC message or F1AP message carries the first information and the F1AP message.
  • RRC message or F1AP message carries the first information and the F1AP message.
  • a tunnel identifier wherein the first information corresponds to the tunnel identifier.
  • the processing unit 2020 configured to determine the tunnel identifier according to the second information, includes: a mapping relationship between the configured second information and the tunnel identifier , and determine the tunnel identifier corresponding to the second information.
  • the transceiver unit 2010 is further configured to receive an RRC message or an F1AP message from the IAB host node, where the RRC message or the F1AP message carries the second information and the tunnel identifier, The second information corresponds to the tunnel identifier.
  • the communication device 2000 is used to access the IAB node:
  • the transceiver unit 2010 is used to receive the downlink data sent by the IAB host node through the General Packet Radio Service Tunneling Protocol GTP tunnel, and the tunnel identifier of the GTP tunnel includes the GTP TEID or includes the GTP TEID and the Internet IP address; According to the corresponding downlink data
  • the differentiated services code point DSCP or flow label is used to send the downlink data to the user equipment UE; the processing unit 2020 is configured to determine the DSCP or the flow label corresponding to the downlink data.
  • the processing unit 2020 configured to determine the DSCP or the flow label corresponding to the downlink data, specifically includes: according to the tunnel identifier, and the tunnel identifier and the tunnel identifier The DSCP mapping relationship is used to determine the DSCP; or, it is used to determine the flow label according to the tunnel identifier and the mapping relationship between the tunnel identifier and the flow label.
  • the transceiver unit 2010 is further configured to receive the tunnel identifier and the DSCP from the IAB host node, where the tunnel identifier corresponds to the DSCP;
  • the IAB host node receives the tunnel identifier and the flow label, wherein the tunnel identifier corresponds to the flow label.
  • the processing unit 2020 configured to determine the DSCP or the flow label corresponding to the downlink data, specifically includes: using the transceiver unit 2010 to send the data from the IAB host node An adaptation layer packet is received, and the adaptation layer packet carries the DSCP or flow label.
  • the transceiver unit 2010, configured to send downlink data to the UE specifically includes: sending a data packet to the UE, the data packet carrying the downlink data, and carrying the downlink data to the UE.
  • the communication apparatus 2000 is used for the first device:
  • the transceiver unit 2010 is configured to receive at least two data packets from the second device, wherein each data packet carries a GTP sequence number of the General Packet Radio Service Tunneling Protocol GTP layer; sequence number, for reordering the at least two data packets; the first device is an integrated IAB node for access and backhaul accessed by the UE, and the second device is an IAB host node; or, the first device is an IAB host node, and the second device is an access IAB node.
  • the transceiver unit 2010 is further configured to receive indication information from the second device, The indication information is used to instruct the GTP layer of the first device to enable or disable the reordering function.
  • the transceiver unit 2010 is further configured to send indication information to the second device, the The indication information is used to instruct the GTP layer of the second device to enable or disable the reordering function.
  • the communication apparatus 2000 is used for user equipment:
  • the transceiver unit 2010 is configured to receive the service bearer identifier and indication information of the UE from the access and backhaul integrated IAB host node, where the indication information is used to instruct the packet data convergence protocol PDCP entity corresponding to the service bearer identifier to enable or disable the replay. Sorting function; the processing unit 2020 is configured to enable or disable the reordering function of the PDCP entity according to the service bearer identifier and the indication information; wherein, the UE is a long-term evolution LTE UE, and the UE uses a new wireless The NR backhaul link accesses the network.
  • the indication information corresponds to the service bearer identifier
  • the service bearer identifier is a data radio bearer identifier DRB ID.
  • the communication device 2000 is used to access the IAB node:
  • the processing unit 2020 is configured to determine the type of the user equipment UE or the type of the core network to be accessed by the UE; the transceiver unit 2010 is configured to send first indication information to the IAB host node, where the first indication information is used to indicate the type of the UE, or used to indicate the type of the core network to be accessed by the UE, or used to indicate whether the UE accesses the NR core network, or used to indicate whether the UE accesses the LTE core network, The first indication information is used by the IAB donor node to select a core network for the UE to access.
  • the processing unit 2020 for determining the type of the UE, specifically includes: for determining the type of the UE according to the cell frequency point accessed by the UE; or for determining the type of the UE by
  • the transceiver unit 2010 receives second indication information from the UE, where the second indication information is used to indicate the type of the UE.
  • the processing unit 2020 configured to determine the type of the core network to be accessed by the UE, specifically includes: using the transceiver unit 2010 to receive third indication information from the UE , the third indication information is used to indicate the type of the core network to be accessed by the UE, or used to indicate whether the UE accesses the NR core network, or is used to indicate whether the UE accesses the LTE core network.
  • the type of the UE is Long Term Evolution LTE UE or New Radio NR UE.
  • the communication device 2000 is used for the IAB host node:
  • the transceiver unit 2010 is configured to receive the first indication information; the processing unit 2020 is configured to determine the access standard used by the air interface of the user equipment UE according to the first indication information.
  • the transceiver unit 2010, configured to receive the first indication information specifically includes: being configured to receive a first RRC message from the UE, where the first RRC message carries the first indication information; or, for receiving an F1AP message from the access IAB node of the UE, where the F1AP message carries the first indication information.
  • the transceiver unit 2010 is further configured to send a second RRC message to the UE, where the second RRC message carries second indication information, and the second indication information is used to indicate the
  • the IAB donor node determines the access standard used by the air interface, and the determined access standard used by the air interface is used for the UE to access the network according to the determined access standard.
  • the above-mentioned communication apparatus 2000 may further include a storage unit, which is used to store data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or be coupled with the storage unit to implement corresponding methods or Features.
  • the processing unit 2020 may read data or instructions in the storage unit, so that the communication apparatus implements the methods in the above embodiments.
  • each unit in the above apparatus can be realized in the form of software calling through the processing element; also can all be realized in the form of hardware; some units can also be realized in the form of software calling through the processing element, and some units can be realized in the form of hardware.
  • each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called by a certain processing element of the device and execute the unit's processing.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above method, such as: one or more Application Specific Integrated Circuits (ASICs), or, one or more Multiple microprocessors (digital singnal processors, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA), or a combination of at least two of these integrated circuit forms.
  • ASICs Application Specific Integrated Circuits
  • DSP digital singnal processors
  • FPGA Field Programmable Gate Array
  • FPGA Field Programmable Gate Array
  • a unit in the apparatus can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processors that can invoke programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the above transceiver unit 2010 is an interface circuit of the device, and is used to receive signals from or send signals to other devices.
  • the transceiver unit 2010 is an interface circuit used by the chip to receive signals from other chips or devices, or an interface circuit used to send signals to other chips or devices.
  • the communication apparatus includes: a processor 2110 and an interface 2130 , and optionally, the communication apparatus further includes a memory 2120 .
  • the interface 2130 is used to implement communication with other devices.
  • the method executed by the IAB node or the IAB host node in the above embodiments may be implemented by the processor 2110 calling a program stored in a memory (which may be the memory 2120 in the IAB node or the IAB host node, or an external memory). That is, the IAB node or the IAB host node may include a processor 2110, and the processor 2110 executes the method performed by the IAB node or the IAB host node in the above method embodiments by invoking the program in the memory.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • An IAB node or IAB host node may be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or, one or more microprocessor DSPs, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.
  • the functions/implementation process of the transceiver unit 2010 and the processing unit 2020 in FIG. 20 can be implemented by the processor 2110 in the communication apparatus 2100 shown in FIG. 21 calling computer executable instructions stored in the memory 2120 .
  • the function/implementation process of the processing unit 2020 in FIG. 20 can be implemented by the processor 2110 in the communication device 2100 shown in FIG. 21 calling the computer-executed instructions stored in the memory 2120, and the function of the transceiver unit 2010 in FIG. 20
  • the implementation process can be implemented through the interface 2130 in the communication device 2100 shown in FIG. 21 .
  • FIG. 22 is a schematic structural diagram of a user equipment according to an embodiment of the present application.
  • the user equipment is used to implement the operations of the user equipment in the above embodiments.
  • the user equipment includes: an antenna 2210 , a radio frequency device 2220 , and a signal processing part 2230 .
  • the antenna 2210 is connected to the radio frequency device 2220 .
  • the radio frequency apparatus 2220 receives the information sent by the access device through the antenna 2210, and sends the information sent by the access device to the signal processing part 2230 for processing.
  • the signal processing part 2230 processes the information of the user equipment and sends it to the radio frequency device 2220
  • the radio frequency device 2220 processes the information of the user equipment and sends it to the access device through the antenna 2210.
  • the signal processing part 2230 is used to realize the processing of each communication protocol layer of the data.
  • the signal processing part 2230 may be a subsystem of the user equipment, and the user equipment may also include other subsystems, such as a central processing subsystem, for implementing the processing of the user equipment operating system and the application layer;
  • the system is used to realize the connection with other devices.
  • the signal processing part 2230 may be a separately provided chip.
  • the above devices may be located in the signal processing part 2230 .
  • the signal processing section 2230 may include one or more processing elements 2231, including, for example, a main control CPU and other integrated circuits, and an interface circuit 2233.
  • the signal processing section 2230 may further include a storage element 2232.
  • the storage element 2232 is used to store data and programs, and the programs used to execute the methods performed by the user equipment in the above methods may or may not be stored in the storage element 2232, for example, stored in a memory outside the signal processing part 2230 During use, the signal processing part 2230 loads the program into the cache for use.
  • the interface circuit 2233 is used to communicate with the device.
  • the above device can be located in the signal processing part 2230, and the signal processing part 2230 can be realized by a chip, and the chip includes at least one processing element and an interface circuit, wherein the processing element is used for executing each step of any one of the methods performed by the above user equipment, and the interface Circuits are used to communicate with other devices.
  • the unit for implementing each step in the above method may be implemented in the form of a processing element scheduler.
  • the apparatus includes a processing element and a storage element, and the processing element calls the program stored in the storage element to execute the above method embodiments.
  • the storage element may be a storage element in which the processing element is on the same chip, that is, an on-chip storage element.
  • the program for executing the method performed by the user equipment in the above method may be in a storage element on a different chip from the processing element, ie, an off-chip storage element.
  • the processing element calls or loads the program from the off-chip storage element to the on-chip storage element, so as to call and execute the method performed by the user equipment in the above method embodiments.
  • the unit of the user equipment that implements each step in the above method may be configured as one or more processing elements, and these processing elements are provided on the signal processing part 2230.
  • the processing elements here may be integrated circuits, such as : One or more ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form chips.
  • the units that implement the steps in the above method can be integrated together and implemented in the form of a system-on-a-chip (SOC), and the SOC chip is used to implement the above method.
  • SOC system-on-a-chip
  • At least one processing element and a storage element may be integrated in the chip, and the above method executed by the user equipment may be implemented in the form of a program stored in the storage element being invoked by the processing element; or, at least one integrated circuit may be integrated in the chip for implementing the above user equipment
  • the above apparatus may include at least one processing element and an interface circuit, wherein the at least one processing element is configured to execute any method performed by the user equipment provided in the above method embodiments.
  • the processing element may execute part or all of the steps performed by the user equipment in the first manner: that is, by calling the program stored in the storage element; or in the second manner: that is, combining the instructions with the integrated logic circuit of the hardware in the processor element part or all of the steps performed by the user equipment; of course, part or all of the steps performed by the user equipment may also be performed in combination with the first manner and the second manner.
  • the processing elements here are the same as those described above, and may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as: one or more ASICs, or one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element may be one memory or a collective term for multiple storage elements.
  • At least one item (single, species) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.
  • “Plurality" means two or more, and other quantifiers are similar.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.
  • a general-purpose processor may be a microprocessor, or alternatively, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration. accomplish.
  • the steps of the method or algorithm described in the embodiments of this application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • Software units can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or this.
  • RAM Random Access Memory
  • ROM read-only memory
  • EPROM memory read-only memory
  • EEPROM memory electrically erasable programmable read-only memory
  • registers hard disk, removable disk, CD-ROM or this.
  • a storage medium may be coupled to the processor such that the processor may read information from, and store information in, the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and storage medium may be provided in the ASIC.
  • the above-described functions described herein may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on, or transmitted over, a computer-readable medium in the form of one or more instructions or code.
  • Computer-readable media includes both computer storage media and communication media that facilitate the transfer of a computer program from one place to another. Storage media can be any available media that a general-purpose or special-purpose computer can access.
  • Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other media in the form of program code that can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly defined as a computer-readable medium, for example, if software is transmitted from a website site, server or other remote source over a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless, and microwave are also included in the definition of computer-readable media.
  • DSL digital subscriber line
  • the discs and magnetic discs include compact discs, laser discs, optical discs, digital versatile discs (English: Digital Versatile Disc, DVD for short), floppy discs and Blu-ray discs. Disks usually reproduce data magnetically, while Discs usually use lasers to optically reproduce data. Combinations of the above can also be included in computer readable media.
  • the functions described in this application may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本申请实施例提供通信方法及装置。该方法包括：用户设备UE确定上行数据对应的第一信息，第一信息用于标识上行数据在第一制式下对应的业务类型或承载；UE根据第一信息确定第二信息，第二信息用于标识上行数据在第二制式下对应的业务类型或承载，第二制式与第一制式不同；UE根据第二信息使用第二制式的空口技术发送上行数据。基于该方案UE根据第一信息得到UE在第二制式下能够识别的第二信息，从而UE可以根据第二信息使用第二制式的空口技术发送上行数据，保障了UE跨制式场景下的正常通信。

Description

通信方法及装置 技术领域
本申请实施例涉及通信技术领域，尤其涉及通信方法及装置。
背景技术
3GPP Rel-15接入回传一体化(Integrated Access and Backhaul，IAB)中，引入了IAB node(称为IAB节点)和IAB donor(称为IAB宿主节点，或者宿主IAB节点)两个节点。
目前，IAB回传链路(包括IAB节点与IAB节点之间的链路，以及IAB节点与IAB宿主节点之间的链路)是采用新无线(New radio，NR)制式，IAB接入链路(即用户设备与IAB节点之间的链路)采用长期演进(Long Term Evolution，LTE)制式或NR制式。
在最新进展中，IAB链路可以用于跨制式场景，即4G用户设备(LTE UE)或者5G用户设备(NR UE)使用不同制式(如无线局域网(Wireless Local Area Network，WLAN)、蓝牙、紫蜂(zigbee))的接入技术接入到IAB节点，由IAB节点通过NR回传链路接入对应的核心网。
在跨制式场景下，如何保证不同设备之间的正常通信，有待解决。
发明内容
本申请实施例提供通信方法及装置，用以保障跨制式场景下，不同设备之间的正常通信。
第一方面，本申请实施例提供一种通信方法，包括：用户设备UE确定上行数据对应的第一信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载；所述UE根据所述第一信息，确定第二信息，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；所述UE根据所述第二信息，使用第二制式的空口技术发送所述上行数据。
在现有技术中，UE采用相同的制式接入网络(比如均为第一制式，具体可以是NR或LTE，即：LTE UE通过LTE制式接入网络，NR UE通过NR制式接入网络)，UE根据第一信息使用第一制式的空口技术发送上行数据。然而在UE跨制式接入的场景下，即第一制式的UE通过第二制式的空口技术接入网络(比如第二制式为WLAN，即：LTE UE或者NR UE通过WLAN制式接入网络)，由于第二制式不识别第一信息，无法进行数据传输的QoS保障，因此,UE无法根据第一信息使用第二制式的空口技术进行QoS保障的上行数据发送。为此，本申请UE根据第一信息得到第二制式能够识别的第二信息，从而UE可以根据第二信息使用第二制式的空口技术发送上行数据，确保了跨制式接入场景下用户设备数据传输的QoS保障。
在一种可能的实现方法中，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
在一种可能的实现方法中，所述第二信息为差分服务代码点DSCP或流标签。
在一种可能的实现方法中，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
在一种可能的实现方法中，所述UE根据第一信息，确定第二信息，包括：所述UE根据配置的所述第一信息与所述第二信息的映射关系，确定所述第一信息对应的所述第二信息。
在一种可能的实现方法中，所述UE从接入回传一体化IAB宿主节点接收无线资源控制RRC消息，所述RRC消息中携带所述第一信息和所述第二信息，其中，所述第一信息和所述第二信息对应。
在一种可能的实现方法中，所述UE包括适配层，所述UE的适配层向所述适配层的下层发送所述第二信息；所述UE根据所述第二信息，使用第二制式的空口技术发送所述上行数据，包括：所述适配层的下层根据所述第二信息，使用第二制式的空口发送所述上行数据。
在一种可能的实现方法中，所述UE的适配层向所述适配层的下层发送所述第二信息，包括：所述适配层向所述适配层的下层发送控制信息，所述控制信息用于指示所述第二信息。
在一种可能的实现方法中，所述UE的适配层向所述适配层的下层发送所述第二信息，包括：所述适配层为所述上行数据添加适配层头，所述适配层头携带所述第二信息；所述适配层向所述适配层的下层发送适配层包，所述适配层包携带所述适配层头。
在一种可能的实现方法中，所述适配层头还携带所述第一信息。
第二方面，本申请实施例提供一种通信方法，包括：接入回传一体化IAB节点接收来自用户设备UE的数据包，所述数据包携带上行数据，以及携带第一信息和/或第二信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；所述IAB节点为所述UE的接入IAB节点；所述IAB节点根据所述第一信息或所述第二信息，确定通用分组无线服务隧道协议GTP隧道的隧道标识；所述IAB节点将所述上行数据映射到所述隧道标识对应的GTP隧道中发送至IAB宿主节点(或者理解为所述IAB节点向IAB宿主节点发送映射到所述隧道标识对应的GTP隧道中的所述上行数据)。其中，所述隧道标识包括GTP TEID，或者GTP TEID和因特网协议IP地址。
现有技术中，UE是将上行数据通过DRB发送至接入IAB节点，然后接入IAB节点根据配置的GTP隧道和UE DRB的映射关系，将上行数据映射到对应的GTP隧道中。然而，在UE跨制式接入的场景下(比如：LTE UE通过WLAN制式接入IAB节点)，UE的WLAN空口并不是将上行数据通过DRB发送至接入IAB节点，因此现有技术中接入IAB节点无法确定接收到的上行数据需要放到哪个GTP隧道。而基于本申请上述方案，可以在数据包中携带第一信息，以及在接入IAB节点上配置第一信息与GTP隧道的隧道标识的映射关系，或者可以在数据包中携带第二信息，以及在接入IAB节点上配置第二信息与GTP隧道的隧道标识的映射关系，从而接入IAB节点可以基于配置的映射关系以及从数据包中获取到的第一信息或第二信息，即可以确定该数据包对应的GTP隧道，从而将上行数据映射到GTP隧道中发送至IAB宿主节点，实现了数据的正确发送，确保了跨制式接入场景下用户设备数据传输的QoS保障。
在一种可能的实现方法中，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
在一种可能的实现方法中，所述第二信息为差分服务代码点DSCP或流标签。
在一种可能的实现方法中，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
在一种可能的实现方法中，所述IAB节点根据所述第一信息，确定GTP隧道的隧道标识，包括：所述IAB节点根据配置的所述第一信息与所述隧道标识的映射关系，确定所述第一信息对应的所述隧道标识。
在一种可能的实现方法中，所述IAB节点从所述IAB宿主节点接收无线资源控制RRC消息或F1AP消息，所述RRC消息或F1AP消息携带所述第一信息和所述隧道标识，其中所述第一信息和所述隧道标识对应。
在一种可能的实现方法中，所述IAB节点根据所述第二信息，确定所述GTP隧道的隧道标识，包括：所述IAB节点根据配置的所述第二信息与所述隧道标识的映射关系，确定所述第二信息对应的所述隧道标识。
在一种可能的实现方法中，所述IAB节点从所述IAB宿主节点接收RRC消息或F1AP消息，所述RRC消息或F1AP消息携带所述第二信息和所述隧道标识，其中所述第二信息与所述隧道标识对应。
第三方面，本申请实施例提供一种通信方法，包括：接入回传一体化IAB节点接收IAB宿主节点通过通用分组无线服务隧道协议GTP隧道发送的下行数据，所述GTP隧道的隧道标识包括GTP TEID或者GTP TEID和因特网IP地址；所述IAB节点为用户设备UE的接入IAB节点；所述IAB节点确定所述下行数据对应的差分服务代码点DSCP或流标签；所述IAB节点根据所述DSCP或所述流标签，向所述UE发送所述下行数据。
现有技术中，接入IAB节点是将下行数据通过DRB发送至UE。然而，在UE跨制式接入的场景下(比如：LTE UE通过WLAN制式接入IAB节点)，接入IAB节点的WLAN空口并不能将下行数据通过DRB发送至UE，因为WLAN制式不识别DRB。为此，本申请上述方案，接入IAB节点可以获取到下行数据包对应的DSCP或流标签，并根据DSCP或流标签向UE发送下行数据。由于WLAN制式能识别DSCP或流标签，从而实现了下行数据的正确发送，确保了跨制式接入场景下用户设备数据传输的QoS保障。
在一种可能的实现方法中，所述IAB节点确定所述下行数据对应的DSCP或流标签，包括：所述IAB节点根据所述隧道标识，以及所述隧道标识与所述DSCP的映射关系，确定所述DSCP；或者，所述IAB节点根据所述隧道标识，以及所述隧道标识与所述流标签的映射关系，确定所述流标签。
在一种可能的实现方法中，所述IAB节点从所述IAB宿主节点接收所述隧道标识和所述DSCP，其中，所述隧道标识与所述DSCP对应；或者，所述IAB节点从所述IAB宿主节点接收所述隧道标识和所述流标签，其中，所述隧道标识与所述流标签对应。
在一种可能的实现方法中，所述IAB节点确定所述下行数据对应的DSCP或流标签，包括：所述IAB节点从所述IAB宿主节点接收适配层包，所述适配层包携带所述DSCP或流标签。
在一种可能的实现方法中，所述IAB节点向UE发送所述下行数据，包括：所述IAB节点向UE发送数据包，所述数据包携带所述下行数据，以及携带所述隧道标识对应的数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的至少一种。
第四方面，本申请实施例提供一种通信方法，包括：第一设备从第二设备接收至少两 个数据包，其中，每个数据包携带一个通用分组无线服务隧道协议GTP层的GTP序号；所述第一设备根据所述GTP层的GTP序号，对所述至少两个数据包进行重排序；所述第一设备是接入回传一体化IAB节点，所述第二设备是IAB宿主节点；或者，所述第一设备是IAB宿主节点，所述第二设备是IAB节点。其中，所述IAB节点为用户设备的接入IAB节点。
基于上述方案，解决了LTE UE接入网络后如何保证回传链路上UE数据的按序接收问题，避免回传链路上数据乱序导致的丢包，保障了跨制式接入场景下用户设备数据的正常传输。
在一种可能的实现方法中，若所述第一设备是IAB节点，所述第二设备是IAB宿主节点，所述第一设备从所述第二设备接收指示信息，所述指示信息用于指示第一设备的GTP层开启或关闭重排序功能。
在一种可能的实现方法中，若所述第一设备是IAB宿主节点，所述第二设备是IAB节点，所述第一设备向所述第二设备发送指示信息，所述指示信息用于指示第二设备的GTP层开启或关闭重排序功能。
第五方面，本申请实施例提供一种通信方法，包括：用户设备UE从接入回传一体化IAB宿主节点接收所述UE的业务承载标识和指示信息，所述指示信息用于指示所述业务承载标识对应的分组数据汇聚协议PDCP实体开启或关闭重排序功能；所述UE根据所述业务承载标识和所述指示信息，开启或关闭所述PDCP实体的重排序功能；其中，所述UE为长期演进LTE UE，所述UE通过新无线NR回传链路接入网络。
基于上述方案，解决了LTE UE接入网络后如何保证回传链路上UE数据的按序接收问题，避免回传链路上数据乱序导致的丢包，保障了跨制式接入场景下用户设备数据的正常传输。
在一种可能的实现方法中，所述指示信息与所述业务承载标识对应，所述业务承载标识为数据无线承载标识DRB ID。
第六方面，本申请实施例提供一种通信方法，包括：IAB节点确定用户设备UE的类型或所述UE待接入的核心网的类型；所述IAB节点为所述UE的接入IAB节点；所述IAB节点向IAB宿主节点发送第一指示信息，所述第一指示信息用于指示所述UE的类型，或用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网，所述第一指示信息用于所述IAB宿主节点为所述UE选择接入的核心网。
基于上述方案，解决了IAB宿主节点如何为UE选择对应的核心网设备的问题，从而使得在跨制式接入场景下IAB宿主节点根据接收到的指示信息为UE选择对应的核心网，可以保证UE接入网络后的正常操作，保障了跨制式接入场景下用户设备数据的正常传输。
在一种可能的实现方法中，所述IAB节点确定UE的类型，包括：所述IAB节点根据所述UE接入的小区频点，确定所述UE的类型；或者，所述IAB节点从所述UE接收第二指示信息，所述第二指示信息用于指示所述UE的类型。
在一种可能的实现方法中，所述IAB节点确定所述UE待接入的核心网的类型，包括：所述IAB节点从所述UE接收第三指示信息，所述第三指示信息用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网。
在一种可能的实现方法中，所述UE的类型为长期演进LTE UE、或新无线NR UE。
第七方面，本申请实施例提供一种通信方法，包括：IAB宿主节点接收第一指示信息；所述IAB宿主节点根据所述第一指示信息，确定用户设备UE空口使用的接入制式。
基于上述方案，在UE跨制式接入场景下，IAB宿主节点可以根据接收到的第一指示信息确定UE空口使用的接入制式，从而可以根据获知的UE空口使用的接入制式为UE配置不同的承载映射策略，保证UE接入网络后的正常操作，保障了跨制式接入场景下用户设备数据的正常传输。
在一种可能的实现方法中，所述IAB宿主节点接收第一指示信息，包括：所述IAB宿主节点从所述UE接收第一RRC消息，所述第一RRC消息携带所述第一指示信息；或者，所述IAB宿主节点从所述UE接入的IAB节点接收F1AP消息，所述F1AP消息携带所述第一指示信息。
在一种可能的实现方法中，所述IAB宿主节点向所述UE发送第二RRC消息，所述第二RRC消息携带第二指示信息，所述第二指示信息用于指示所述IAB宿主节点确定所述UE空口使用的接入制式，所述确定空口使用的接入制式用于所述UE根据确定的接入制式接入网络。
第八方面，本申请实施例提供一种通信装置，该装置可以是用户设备，还可以是用于用户设备的芯片。该装置具有实现上述第一方面或第五方面、或第一方面的各可能的实现方法、或第五方面的各可能的实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，本申请实施例提供一种通信装置，该装置可以是IAB节点，还可以是用于IAB节点的芯片。该装置具有实现上述第二方面或第三方面或第六方面、或第二方面的各可能的实现方法、或第三方面的各可能的实现方法、或第六方面的各可能的实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十方面，本申请实施例提供一种通信装置，该装置可以是第一设备，还可以是用于第一设备的芯片。该装置具有实现上述第四方面、或第四方面的各可能的实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十一方面，本申请实施例提供一种通信装置，该装置可以是IAB宿主节点，还可以是用于IAB宿主节点的芯片。该装置具有实现上述第七方面、或第七方面的各可能的实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十二方面，本申请实施例提供一种通信装置，包括处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第一方面至第七方面的方法，第一方面至第七方面的各可能的实现方法中的任意方法。
第十三方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面至第七方面的方法，第一方面至第七方面的各可能的实现方法中的任意方法的各个步骤的单元或手段(means)。
第十四方面，本申请实施例提供一种通信装置，包括处理器和接口电路，所述处理器 用于通过接口电路与其它装置通信，并执行上述第一方面至第七方面的方法，第一方面至第七方面的各可能的实现方法中的任意方法。该处理器包括一个或多个。
第十五方面，本申请实施例提供一种通信装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行上述第一方面至第七方面的方法，第一方面至第七方面的各可能的实现方法中的任意方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
第十六方面，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得处理器执行上述第一方面至第七方面的方法，第一方面至第七方面的各可能的实现方法中的任意方法。
第十七方面，本申请实施例还提供一种计算机程序产品，该计算机产品包括计算机程序，当计算机程序运行时，使得上述第一方面至第七方面的方法，第一方面至第七方面的各可能的实现方法中的任意方法被执行。
第十八方面，本申请实施例还提供一种芯片系统，包括：处理器，用于执行上述第一方面至第七方面的方法，第一方面至第七方面的各可能的实现方法中的任意方法。
附图说明
图1为NR中gNB-CU和gNB-DU分离架构图；
图2为gNB采用CU-DU分离架构下的控制面协议栈示意图；
图3为gNB采用CU-DU分离架构下的用户面协议栈示意图；
图4为两跳数据回传场景示意图；
图5为两跳数据回传的控制面协议栈示意图；
图6为两跳数据回传的用户面协议栈示意图；
图7为两跳数据回传中的数据传输示意图；
图8为家庭接入网络示意图；
图9为本申请实施例所适用的网络架构示意图；
图10为LTE/NR UE通过WLAN制式接入网络时的控制面协议栈架构；
图11为LTE/NR UE通过WLAN制式接入网络时的用户面协议栈架构；
图12为本申请实施例提供的一种通信方法示意图；
图13为适配层的格式设计示意图；
图14为本申请实施例提供的又一种通信方法示意图；
图15为本申请实施例提供的又一种通信方法示意图；
图16为本申请实施例提供的又一种通信方法示意图；
图17为本申请实施例提供的又一种通信方法示意图；
图18为本申请实施例提供的又一种通信方法示意图；
图19为本申请实施例提供的又一种通信方法示意图；
图20为本申请实施例提供的一种通信装置示意图；
图21为本申请实施例提供的又一种通信装置示意图；
图22为本申请实施例提供的一种用户设备示意图。
具体实施方式
第三代合作伙伴计划(3rd generation partnership project，3GPP)Rel-15 NR中，gNB可以采用集中式单元(Central Unit，CU)-分布式单元(Distributed Unit，DU)分离架构，即：gNB由一个gNB-CU以及一个或者多个gNB-DU组成。其中，gNB-CU与gNB-DU之间通过F1接口相连，gNB-CU与第五代(5th generation，5G)核心网之间通过NG接口相连。如图1所示，为NR中gNB-CU和gNB-DU分离架构图。
gNB是为用户设备(User Equipment，UE)提供NR用户面和控制面传输的节点，gNB包含一个或者多个小区。gNB通过NG接口连接到5G核心网(5G core，5GC)，并通过Xn接口与其它gNB相连。其中，Xn-C接口用于两个gNB之间控制面信令的传输，Xn-U接口用于两个gNB之间用户面数据的传输。gNB与UE之间的接口称为Uu接口。其中，UE与基站(如gNB、eNB)或者接入IAB节点的DU之间的通信接口可以称为空口。
gNB-CU是一个逻辑节点，gNB-CU包含gNB的无线资源控制(Radio Resource Control，RRC)层、业务数据适配协议(Service Data Adaptation Protocol，SDAP)层和分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层，用于控制一个或者多个gNB-DU。
gNB-DU是一个逻辑节点，gNB-DU包含gNB的无线链路控制(Radio Link Control，RLC)层、媒体接入控制(medium access control，MAC)层和物理层(Physical layer，PHY)层。一个gNB-DU支持一个或者多个小区，但一个小区只能属于一个gNB-DU。
UE通过gNB-DU接入gNB-CU，即：与UE对等的PHY/MAC/RLC层功能位于gNB-DU上，与UE对等的PDCP/SDAP/RRC层功能位于gNB-CU上。
如图2所示，为gNB采用CU-DU分离架构下的控制面协议栈示意图。对控制面而言，上行(uplink，UL)方向上，gNB-DU将UE生成的RRC消息封装在F1接口应用协议(F1 Application Protocol，F1AP)消息中发送到gNB-CU。下行(downlink，DL)方向上，gNB-CU将RRC消息封装在F1AP消息中发送到gNB-DU，gNB-DU从F1AP消息中提取出RRC消息映射到Uu接口对应的信令无线承载(signalling radio bearer，SRB)(SRB0/SRB1/SRB2)上发送给UE。
如图3所示，为gNB采用CU-DU分离架构下的用户面协议栈示意图。对用户面而言，UL方向上，gNB-DU将从Uu接口数据无线承载(Data Radio Bearer，DRB)上收到的UE数据包映射到对应的通用分组无线服务(General Packet Radio Service，GPRS)隧道协议(GPRSTunnelingProtocol，GTP)隧道中发送到gNB-CU。DL方向上，gNB-CU将UE数据包映射到对应的GTP隧道中发送到gNB-DU，gNB-DU从GTP隧道中提取出UE数据包，并将该UE数据包映射到Uu接口对应的DRB上发送给UE。
3GPP Rel-15IAB中，引入了IAB node(称为IAB节点)和IAB donor(称为IAB宿主节点，或者宿主IAB节点)两个节点。其中，IAB donor可以是gNB，或者升级后的gNB。
如图4所示，为两跳数据回传场景示意图。其中，回传简称BH。IAB网络采用CU-DU分离架构，即：IAB donor由IAB donor-CU(简称donor-CU)和IAB donor-DU(简称donor-DU)两部分组成，IAB node由IAB node-MT(简称IAB-MT)和IAB node-DU(简称IAB-DU)两部分组成。其中，IAB node-MT又可以称为IAB node-UE(简称IAB-UE)。
对IAB donor而言，donor-DU与gNB-DU的功能类似，donor-CU与gNB-CU的功能 类似。
对IAB node而言，IAB-DU与gNB-DU的功能类似，用于为其子节点提供接入服务，其中，IAB-DU的子节点可以是UE，也可以是其他IAB node。IAB-MT具有UE的功能，用于为其子节点提供数据回传。
IAB node进一步又可以分为接入IAB node和中间IAB node，即：UE接入的IAB节点称为接入IAB node，接入IAB node和IAB donor之间路径上的IAB node称为中间IAB node。
如图4所示，UE接入IAB node2，则IAB node2称为UE的接入IABnode(或者UE的父节点)，UE称为IAB node2的子节点，UE和IAB node2之间的链路称为接入链路。IAB node1称为中间IAB node，IAB node1的父节点为IAB donor(IAB donor的子节点为IAB node1)，IAB node1的子节点为IAB node2(IAB node2的父节点为IAB node1)。IAB node1和IAB node2之间的链路，以及IAB node1和IAB donor之间的链路均称为回传链路。其中，与UE对等的PHY层、MAC层和RLC层位于接入IAB node上(即：IAB2-DU)，而与UE对等的PDCP层、SDAP层和RRC层位于donor-CU上。IAB node均采用L2数据转发的架构。
如图5所示，为两跳数据回传的控制面协议栈示意图。接入IAB node(即：IAB2-DU)和IAB donor(即：donor-CU)之间建立F1接口。具体的，如果IAB donor采用CP-UP分离架构，则IAB2-DU和donor CU-CP之间建立F1-C接口。UE的RRC消息封装在F1-C接口的F1AP消息中传输。
如图6所示，为两跳数据回传的用户面协议栈示意图。如果IAB donor采用CP-UP分离架构，则IAB2-DU和donor CU-UP之间建立F1-U接口，并在该F1-U接口上建立per UE bearer的GTP隧道。也就是说，UE和IAB2-DU之间接口上建立的每一个UE DRB，在IAB2-DU和donor CU-UP之间接口上对应一个单独的GTP隧道。
如图7所示，为两跳数据回传中的数据传输示意图。UE和IAB node2之间接口链路上建立多个UE DRB，用于传输UE不同的业务。IAB node2和IAB node1之间回传链路上建立多个回传RLC信道(Backhaul RLC Channel，BH RLC CH)，用于传输UE不同业务的回传。同理，IAB node1和IAB donor之间回传链路上也建立多个BH RLC CH。IAB node2和IAB donor CU之间建立per UE bearer的GTP隧道，每个GTP隧道与UE和IAB node2之间接口上的UE DRB一一对应。
在下行方向：
1)、Donor-CU将UE PDCP协议数据单元(protocol data unit，PDU)映射到对应的GTP隧道上，确定该UE数据包的目标因特网协议(internet protocol，IP)地址(即IAB node2的IP地址)，将该UE数据包进一步封装成IP包，并在IP头字段中打上对应的差分服务代码点(Differentiated Services Code Point，DSCP)或流标签(flow label)，以及填上IP包的目标IP地址后，通过IP路由方式发送到Donor-DU。其中，DSCP用于在因特网协议版本4(Internet Protocol version 4，IPv4)中标识业务的类型，flow label用于在因特网协议版本6(Internet Protocol version 6，IPv6)中标识业务的类型。
2)、Donor-DU根据IP头中携带的DSCP或flow label以及目标IP地址，并根据Donor-CU配置的映射关系1，将收到的UE IP包映射到对应的BH RLC CH上发送给IAB  node1。其中，Donor-CU为Donor-DU配置的映射关系1包括：参数和BH RLC CH的映射关系，该参数由以下一种或者多种组合组成，包括：DSCP、flow label、目标IP地址。
3)、IAB node1根据Donor-CU配置的映射关系2，将收到的UE IP包映射到对应的BH RLC CH上发送给IAB node2。其中，Donor-CU为IAB node1配置的映射关系2包括：ingress BH RLC CH(入口BH RLC CH)和egress BH RLC CH(出口BH RLC CH)的映射关系。ingress BH RLC CH为IAB node1和IAB donor DU之间的BH RLC CH，egress BH RLC CH为IAB node1和IAB node2之间的BH RLC CH。
4)、IAB node2将收到的UE IP包送到GTP层解析后，从GTP隧道中提取UE PDCP PDU，并根据Donor-CU配置的GTP隧道和UE DRB的映射关系，将UE PDCP PDU映射到对应的UE DRB上发送给UE。
在上行方向：
1)、UE将UE PDCP PDU映射到对应的UE DRB上发送到IAB node2。
2)、IAB node2根据Donor-CU配置的GTP隧道和UE DRB的映射关系，将UE PDCP PDU映射到对应的GTP隧道中。然后，IAB node2再根据Donor-CU配置的映射关系3，将UE数据包进一步封装成IP包后映射到对应的BH RLC CH上发送给IAB node1。其中，Donor-CU配置的映射关系3包括：GTP隧道(即：GTP TEID和IP地址)和BH RLC CH的映射关系,IP地址为donor-CU的IP地址。
3)、IAB node1根据Donor-CU配置的映射关系4，将收到的UE IP包映射到对应的BH RLC CH上发送给Donor-DU。其中，Donor-CU为IAB node1配置的映射关系4包括：ingress BH RLC CH(入口BH RLC CH)和egress BH RLC CH(出口BH RLC CH)的映射关系。ingress BH RLC CH为IAB node2和IAB node1之间的BH RLC CH，egress BH RLC CH为IAB node1和IAB donor DU之间的BH RLC CH。
4)、Donor-DU根据UE IP包头中的目标IP地址(即：Donor-CU的IP地址)，将UE IP包进一步路由到Donor-CU。Donor-CU将IP包送到GTP层解析后，从GTP隧道中提取出UE PDCP PDU。
上述方案中，存在以下问题需要解决：
问题1、现有技术中，接入链路和回传链路使用相同的接入制式，均为NR接入制式，没有考虑在不同接入制式场景下如何实现UE数据传输的承载映射，包括上行方向和下行方向，从而实现UE业务在整个数据传输过程中的QoS保障。
比如，LTE UE或NR UE通过非3GPP(non-3GPP)接入网络的场景下，其中，non-3GPP包括:WLAN接入制式、蓝牙接入制式、zigbee接入制式等，如何实现UE上行和下行数据传输的承载映射，从而实现UE业务在整个数据传输过程中的QoS保障。
问题2、在不同接入制式的场景下，如何保证回传链路上UE数据的按序接收。
问题3、在不同接入制式的场景下，如何为不同类型的UE选择接入的核心网设备。
问题4、在不同接入制式的场景下，如何获知UE空口使用的接入制式。
本申请实施例的发明点主要包括：
第一，为解决上述问题1，改进点主要如下：
1)、UE执行上行承载映射，Donor-CU为UE配置以下至少一种映射关系：
对于LTE UE而言，映射关系为DRB ID/E-RAB ID<->DSCP/flow label。其中“/”是或的意思，因此可以配置以下四种映射关系中的至少一种：a)DRB ID<->DSCP，b)DRB ID<->flow label，c)E-RAB ID<->DSCP，d)E-RAB ID<->flow label。其中，E-RAB是演进的通用陆基无线接入网(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)-无线接入承载(Radio Access Bearer)。
对于NR UE而言，映射关系为DRB ID/QFI<->DSCP/flow label。也即可以配置以下四种映射关系中的至少一种：a)DRB ID<->DSCP，b)DRB ID<->flow label，c)QFI<->DSCP，d)QFI<->flow label。其中，服务质量(Quality of Service，QoS)流标识(QoS flow identity，QFI)。
2)、接入IAB-MT执行上行承载映射，Donor-CU为IAB-node配置上行映射关系，包括：DSCP/flow label<->GTP TEID。也即可以配置以下两种映射关系中的至少一种：a)DSCP<->GTP TEID，b)flow label<->GTP TEID。UE将上行数据对应的DSCP/flow label携带在适配层中，随上行数据一起发送到IAB-node。或者，Donor-CU为IAB-node配置上行映射关系，包括：DRB ID<->GTP TEID。UE将上行数据对应的DRB ID携带在适配层中，随上行数据一起发送到IAB-node。
3)、接入IAB-DU执行下行承载映射，Donor-CU确定UE业务类型对应的DSCP/flow label，并将确定的DSCP/flow label值携带在适配层中随下行数据一起发送到IAB-node。其中，UE业务类型可以通过DRB ID、E-RAB ID或GTP TEID来表示。Donor-CU为IAB-node配置的下行映射关系包括：UE业务类型<->DSCP/flow label。也即可以配置以下六种映射关系中的至少一种：a)DRB ID<->DSCP，b)DRB ID<->flow label，c)E-RAB ID<->DSCP，d)E-RAB ID<->flow label，e)GTP TEID<->DSCP，f)GTP TEID<->flow label。
第二，为解决上述问题2，改进点主要如下：
4)、接入IAB-DU和Donor-CU之间的GTP层引入重排序功能，或者，Donor-CU向UE发送指示信息，该指示信息用于指示UE是否打开PDCP重排序功能。该指示信息可以是per DRB指示的。
第三，为解决上述问题3，改进点主要如下：
5)、UE初始入网过程中，接入IAB-node通过F1AP消息向Donor-CU发送指示信息，该指示信息用于指示接入UE的类型，或者，用于指示UE待接入核心网的类型或用于指示UE是否接入LTE核心网或用于指示UE是否接入NR核心网。
第四，为解决上述问题4，改进点主要如下：
6)、UE选择一种接入制式接入IAB-node，此时，UE可以通过RRC消息向Donor-CU发送指示信息，或者，由接入IAB-node通过F1AP消息向Donor-CU发送该指示信息，用于指示UE空口使用的接入制式。若Donor-CU不接受UE选择的接入制式，则Donor-CU还可以进一步通过RRC消息将其确定的UE空口使用的接入制式发送给UE，以便UE更新空口使用的接入制式。
本申请实施例中，UE接入网络的制式也可以称为接入制式，接入制式对应的接入技术也可以称为空口技术或空口接入技术。
下面结合附图，对上述主要改进点进行具体说明。
一、本申请实施例所针对的应用场景
本申请实施例可以应用于IAB网络的场景，也可以应用于家庭接入(Home Access)网络的场景。
在IAB网络中，LTE UE或NR UE可以通过WLAN制式、LTE制式、NR制式、蓝牙制式、zigbee等制式接入到接入IAB node。本申请实施例主要针对的是LTE UE或NR UE通过WLAN制式、蓝牙制式、zigbee等制式接入到接入IAB node时的改进。
在家庭接入网络中，为了提升室内覆盖性能，家庭接入节点HAP(Home Access Point)可以是以IAB node的形态(基站的形态)或者以CPE的形态(UE的形态)存在。HAP和家庭设备(如UE)之间存在多种接入制式，可以是LTE、NR、WLAN(如无线保真(Wireless Fidelity，WiFi))、蓝牙、zigbee等。或者，HAP和UE之间通过直连链路(sidelink)进行通信。HAP和基站之间通过NR制式进行回传。如图8所示，为家庭接入网络示意图。
二、本申请实施例所适用的网络架构
如图9所示，为本申请实施例所适用的网络架构示意图。其中，LTE UE或NR UE可以通过WLAN、LTE、NR、蓝牙、zigbee等制式接入到IAB node或HAP。本申请实施例主要针对的是LTE UE或NR UE通过WLAN、蓝牙、zigbee接入到接入IAB node或HAP时的改进。
具体说明如下：
1)、LTE UE通过LTE接入制式接入IAB-node(或者HAP)，并通过NR回传链路接入IAB-donor(或者gNB)，再通过S1接口连接到演进的分组核心网络(Evolved Packet Core，EPC)。
2)、NR UE通过NR接入制式接入IAB-node(或者HAP)，并通过NR回传链路接入IAB-donor(或者gNB)，再通过NG接口连接到5GC。
3)、LTE UE通过WLAN接入制式、蓝牙接入制式、zigbee接入制式接入IAB-node(或者HAP)，并通过NR回传链路接入IAB-donor(或者gNB)，再通过S1接口连接到EPC。
4)、NR UE通过WLAN接入制式、蓝牙接入制式、zigbee接入制式接入IAB-node(或者HAP)，并通过NR回传链路接入IAB-donor(或者gNB)，再通过NG接口连接到5GC。
针对上述场景1)，可沿用Rel-16IAB架构来实现，因此本申请实施例不做相应改动。
针对上述场景2)，目前的Rel-16IAB架构已经支持，因此本申请实施例不做相应改动。
针对上述场景3)和4)，本申请实施例将要解决的这两种场景中所存在的上述问题1至问题4。
下面结合附图，对上述场景3)和场景4)中所存在的上述问题1至问题4分别提供的解决方案进行具体说明。
为便于说明，以下实施例中，以LTE UE或NR UE通过WLAN制式接入到IAB node为例进行说明，对于LTE UE或NR UE通过蓝牙或zigbee制式接入到IAB node的实现方 法，与LTE UE或NR UE通过WLAN制式接入到IAB node的方法相同，不再赘述。
实施例一
该实施例用于解决上述问题1，具体的，在WLAN接入制式、蓝牙接入制式、zigbee接入制式下，如何实现UE上行和下行数据传输的承载映射，从而实现UE业务在整个数据传输过程中的QoS保障。
为了支持LTE UE或者NR UE通过WLAN、蓝牙或zigbee制式接入网络，控制面和用户面协议栈架构分别如图10和图11所示。本申请实施例以单跳回传链路场景为例进行说明，本专利方案同样适用多跳回传链路场景，这里不再赘述。
其中，单跳回传链路场景指的是接入IAB节点的父节点就是IAB宿主，即：接入IAB节点和IAB宿主之间不存在中间IAB节点。多跳回传链路场景指的就是接入IAB节点和IAB宿主之间存在1个或者多个中间IAB节点。其中，存在1个中间IAB节点的场景可称为两跳回传链路场景，存在2个中间IAB节点的场景可称为三跳回传链路场景，以此类推。
从图10和图11可以看出，本申请实施例在UE和接入IAB-node之间新引入一个适配层(Adapt层)，用于不同无线接入技术(Radio Access Technology，RAT)的选择/适配以及空口QoS的保障。同理，接入IAB-node和IAB donor之间(具体为接入IAB-DU和Donor-CU之间)新引入一个适配层(Adapt层)，用于不同RAT的选择/适配以及回传链路上QoS的保障。
一、上行承载映射
1、UE和接入IAB node之间接入链路上的上行承载映射
UE和接入IAB node之间接入链路上的上行承载映射由UE来执行。
如图12所示，为本申请实施例提供的一种通信方法。该方法由UE在需要发送上行数据时执行。该方法包括以下步骤：
步骤1201，UE确定上行数据对应的第一信息，第一信息用于标识上行数据在第一制式下对应的业务类型或承载。
比如，针对LTE UE，第一信息可以是DRB ID或E-RAB ID，第一制式是LTE制式。
再比如，针对NR UE，第一信息可以是DRB ID或QFI，第一制式是NR制式。
步骤1202，UE根据第一信息，确定第二信息，第二信息用于标识上行数据在第二制式下对应的业务类型或承载，第二制式与第一制式不同。
比如，UE上配置有第一信息与第二信息之间的映射关系(或对应关系)，则UE可以根据配置的第一信息与第二信息的映射关系，确定第一信息对应的第二信息。作为一种实现方法，UE从IAB宿主节点接收RRC消息(如RRC重配置消息)，该RRC消息中携带第一信息和第二信息，第一信息和第二信息对应，从而UE可以获取到第一信息与第二信息之间的映射关系。
该第二信息可以是DSCP或流标签(flow label)。
该第二制式为WLAN、蓝牙或zigbee中的一种。
因此，Donor-CU为UE配置的第一信息与第二信息的映射关系如下：
对于LTE UE而言，可以为LTE UE配置以下映射关系中的至少一种：
a)DRB ID<->DSCP；
b)DRB ID<->flow label；
c)E-RAB ID<->DSCP；
d)E-RAB ID<->flow label。
其中，针对LTE UE，一个PDCP实体唯一对应一个DRB ID，以及唯一对应一个E-RAB ID。
对于NR UE而言，可以为NR UE配置以下映射关系中的至少一种：
a)DRB ID<->DSCP；
b)DRB ID<->flow label；
c)QFI<->DSCP；
d)QFI<->flow label。
其中，针对NR UE，一个PDCP实体唯一对应一个DRB ID，以及一个QFI唯一对应一个PDCP实体。
步骤1203，UE根据第二信息，使用第二制式的空口技术发送上行数据。
UE根据第二信息使用第二制式的空口技术发送上行数据，也可以理解为UE根据第二信息执行QoS控制，具体的，可以在上行数据包携带第二信息。
在现有技术中，UE采用相同的制式接入网络(比如均为第一制式，具体可以是NR或LTE，即：LTE UE通过LTE制式接入网络，NR UE通过NR制式接入网络)，UE根据第一信息使用第一制式的空口技术发送上行数据。然而在UE跨制式接入的场景下，即第一制式的UE通过第二制式的空口技术接入网络(比如第二制式为WLAN，即：LTE UE或者NR UE通过WLAN制式接入网络)，由于第二制式不识别第一信息，无法进行数据传输的QoS保障，因此,UE无法根据第一信息使用第二制式的空口技术进行QoS保障的上行数据发送。为此，本申请UE根据第一信息得到第二制式能够识别的第二信息，从而UE可以根据第二信息使用第二制式的空口技术发送上行数据，确保了跨制式接入场景下用户设备数据传输的QoS保障。
下面给出上述过程的具体示例。
作为第一种实现方式，UE沿用现有机制，将上行数据(即：IP包)映射到PDCP层对应的PDCP实体进行处理，得到处理后的上行数据(即：PDCP PDU)。其中，该PDCP实体与业务承载标识(如DRB ID/E-RAB ID/QFI)对应，UE的适配层从适配层的上层(即：PDCP层的PDCP实体)收到处理后的上行数据后，根据Donor-CU配置的映射关系，确定DRB ID/E-RAB ID/QFI对应的DSCP/flow label值，也即UE的适配层可以确定该处理后的上行数据对应的DSCP/flow label值。然后，UE的适配层向适配层的下层(如WLAN L2为例)发送控制信息，该控制信息用于指示DSCP/flow label值，或者理解为用于指示该处理后的上行数据对应的DSCP/flow label值。UE的WLAN L2收到控制信息指示的DSCP/flow label值后，按照现有WLAN机制，根据DSCP/flow label执行UE业务的QoS保障。具体的，UE的WLAN L2沿用现有机制，根据获取到的DSCP/flow label值来识别UE业务并进行业务QoS的保障。这样做的好处在于：上层数据传输可以屏蔽底层的接入技术，只要底层接入技术(例如：WLAN、zigbee、蓝牙等)通过DSCP/flow label来识别UE业务的都可以适用。
作为第二种实现方式，UE的适配层从适配层的上层(即：PDCP层的PDCP实体)收到经过上层处理后的上行数据(即：PDCP PDU)后,其中，该PDCP实体与业务承载标识(如DRB ID/E-RAB ID/QFI)对应，然后，UE再根据Donor-CU配置的映射关系，确定DRB ID/E-RAB ID/QFI对应的DSCP/flow label值，也即UE的适配层可以确定该处理后的上行数据对应的DSCP/flow label值。然后，UE的适配层为该处理后的上行数据添加适配层头，得到适配层包，该适配层包携带适配层头和该处理后的上行数据，该适配层头携带DSCP/flow label，可选的，该适配层头还携带DRB ID/E-RAB ID/QFI。然后UE的适配层将适配层包发送到适配层的下层(如WLAN L2)，由UE的WLAN L2按照现有机制从收到的适配层包中提取出DSCP/flow label值后执行UE业务的QoS保障。具体的，UE的WLAN L2沿用现有机制，根据获取到的DSCP/flow label值来识别UE业务并进行业务QoS的保障。这样做的好处在于：上层数据传输可以屏蔽底层的接入技术，只要底层接入技术(例如：WLAN、zigbee、蓝牙等)通过DSCP/flow label来识别UE业务的都可以适用。
针对上述第二种实现方法，作为示例，适配层的格式设计如图13所示。其中，R为预留字段。版本(Version)字段占4比特(bit)。当version字段取值为4时，适配层采用左边的格式设计，当version字段取值为6时，适配层采用右边的格式设计。
图中以适配层包携带DSCP和DRB ID为例进行说明。当适配层采用左边的格式设计时，DSCP字段固定从第二字节开始占6bit，DSCP字段后面紧跟5bit的DRB ID。当适配层采用右边的格式设计时，流标签(Flow label)字段固定从第二字节中的第4bit开始占20bit，version字段后面紧跟5bit的DRB ID。
2、接入IAB node和Donor-DU之间回传链路上的上行承载映射
接入IAB node和Donor-DU之间回传链路上的上行承载映射由接入IAB node来执行。具体的，由接入IAB-MT来执行上行承载映射。
如图14所示，为本申请实施例提供的一种通信方法。该方法由接入IAB节点在需要发送上行数据时执行。这里的接入IAB节点(接入IAB node)，也即UE接入的IAB节点。对于接入IAB节点的具体含义，可参考前述描述。
该方法包括以下步骤：
步骤1401，接入IAB node接收来自UE的数据包，该数据包携带上行数据，以及携带第一信息和/或第二信息。
其中，第一信息用于标识上行数据在第一制式下对应的业务类型或承载，第二信息用于标识上行数据在第二制式下对应的业务类型或承载，第二制式与第一制式不同。
比如，针对LTE UE，第一信息可以是DRB ID或E-RAB ID，该第二信息可以是DSCP或流标签(flow label)，第一制式是LTE制式，第二制式为WLAN、蓝牙或zigbee中的一种。
再比如，针对NR UE，第一信息可以是DRB ID或QFI，该第二信息可以是DSCP或流标签(flow label)，第一制式是NR制式，第二制式为WLAN、蓝牙或zigbee中的一种。
步骤1402，接入IAB node根据第一信息或第二信息，确定GTP隧道的隧道标识，该隧道标识包括GTP TEID，或者GTP TEID和IP地址。
比如，当接入IAB node从UE接收到的数据包携带第一信息，则接入IAB node可以根据配置的第一信息与GTP隧道的标识的映射关系，确定第一信息对应的GTP隧道的标 识。可选的，接入IAB node可以从IAB donor接收RRC消息或F1AP消息，该RRC消息或F1AP消息携带第一信息和隧道标识，该第一信息和隧道标识对应，从而接入IAB node可以获取到第一信息和隧道标识的映射关系。
再比如，当接入IAB node从UE接收到的数据包携带第二信息，则接入IAB node可以根据配置的第二信息与GTP隧道的标识的映射关系，确定第二信息对应的GTP隧道的标识。可选的，接入IAB node可以从IAB donor接收RRC消息或F1AP消息，该RRC消息或F1AP消息携带第二信息和隧道标识，该第二信息和隧道标识对应，从而接入IAB node可以获取到第二信息和隧道标识的映射关系。
步骤1403，接入IAB node将上行数据映射到隧道标识对应的GTP隧道中发送至IAB donor。
现有技术中，UE是将上行数据通过DRB发送至接入IAB节点，然后接入IAB节点根据配置的GTP隧道和UE DRB的映射关系，将上行数据映射到对应的GTP隧道中。然而，在UE跨制式接入的场景下(比如：LTE UE通过WLAN制式接入IAB节点)，UE的WLAN空口并不是将上行数据通过DRB发送至接入IAB节点，因此现有技术中接入IAB节点无法确定接收到的上行数据需要放到哪个GTP隧道。而基于本申请上述方案，可以在数据包中携带第一信息，以及在接入IAB节点上配置第一信息与GTP隧道的隧道标识的映射关系，或者可以在数据包中携带第二信息，以及在接入IAB节点上配置第二信息与GTP隧道的隧道标识的映射关系，从而接入IAB节点可以基于配置的映射关系以及从数据包中获取到的第一信息或第二信息，即可以确定该数据包对应的GTP隧道，从而将上行数据映射到GTP隧道中发送至IAB宿主节点，实现了数据的正确发送，确保了跨制式接入场景下用户设备数据传输的QoS保障。
下面给出上述过程的具体示例。
方案一、UE将上行数据对应的第一信息(可以是DRB ID/E-RAB ID/QFI)携带在适配层中，随上行数据一起发送到接入IAB node。接入IAB node根据Donor-CU配置的上行映射关系，将上行数据映射到对应的GTP隧道中，然后再映射到对应的egress BH RLC CH中发送到Donor-DU。其中，Donor-CU配置的上行映射关系包括：DRB ID/E-RAB ID/QFI<->隧道标识，以及隧道标识<->egress BH RLC CH。egress BH RLC CH是IAB node和Donor-DU之间的回传RLC信道。
也就是说，接入IAB node根据适配层中携带的DRB ID/E-RAB ID/QFI，获知该上行数据对应的DRB ID/E-RAB ID/QFI，然后根据Donor-CU配置的DRB ID/E-RAB ID/QFI<->隧道标识的映射关系，将该上行数据映射到对应的GTP隧道中，然后再根据Donor-CU配置的隧道标识<->egress BH RLC CH的映射关系，将映射到GTP隧道后的上行数据进一步映射到对应的BH RLC CH上发送到Donor-DU。
方案二、UE将上行数据对应的第二信息(可以是DSCP/flow label)携带在适配层中，随上行数据一起发送到接入IAB node。接入IAB node根据Donor-CU配置的上行映射关系，将上行数据映射到对应的GTP隧道中，然后再映射到对应的egress BH RLC CH中发送到Donor-DU。其中，Donor-CU配置的上行映射关系包括：DSCP/flow label<->隧道标识，以及隧道标识<->egress BH RLC CH。egress BH RLC CH是IAB node和Donor-DU之间的回 传RLC信道。
也就是说，接入IAB node根据适配层中携带的DSCP/flow label，获知该上行数据对应的DSCP/flow label，然后根据Donor-CU配置的DSCP/flow label<->隧道标识的映射关系，将该上行数据映射到对应的GTP隧道中，然后再根据Donor-CU配置的隧道标识<->egress BH RLC CH的映射关系，将映射到GTP隧道后的上行数据进一步映射到对应的egress BH RLC CH上发送到Donor-DU。
具体的，上述映射关系可以携带在Donor-CU给接入IAB-MT发送的RRC消息中，或者，上述映射关系可以携带在Donor-CU给接入IAB-DU发送的F1AP消息中，由接入IAB-DU通过内部接口将上述映射关系通知接入IAB-MT。
值得注意的是，本申请以接入IAB node的父节点为IAB donor为例进行说明，本申请同样适用于多跳场景，即接入IAB node的父节点为其他IAB节点，该场景下，只需将上述方案一和方案二中的Donor-DU替换为接入IAB node父节点的DU即可。
二、下行承载映射
1、UE和接入IAB node之间接入链路上的下行承载映射
UE和接入IAB node之间接入链路上的下行承载映射由接入IAB node来执行，具体的，由接入IAB-DU来执行下行承载映射。
如图15所示，为本申请实施例提供的一种通信方法。该方法由接入IAB node在需要发送下行数据时执行。这里的接入IAB节点(接入IAB node)，也即UE接入的IAB节点。对于接入IAB节点的具体含义，可参考前述描述。
该方法包括以下步骤：
步骤1501，接入IAB node接收IAB donor通过GTP隧道发送的下行数据，GTP隧道的隧道标识包括GTP TEID或者GTP TEID和IP地址。
也即，接入IAB node从GTP隧道中获取到下行数据，该GTP隧道为接入IAB node与IAB donor之间的隧道。
步骤1502，接入IAB node确定下行数据对应的DSCP或flow label。
比如，接入IAB node可以根据配置的GTP隧道的隧道标识与DSCP/flow label之间的映射关系，确定隧道标识对应的DSCP或flow label。可选的，该映射关系可以是接入IAB node从IAB donor接收到的，也即接入IAB node从IAB donor接收隧道标识和DSCP，或者接收隧道标识和flow label，其中，隧道标识和DSCP对应，或者，隧道标识和flow label对应。
再比如，接入IAB node还可以从IAB donor接收适配层包，该适配层包携带下行数据和适配层头，适配层头中携带DSCP或flow label。基于该实现方法，接入IAB node可以直接从适配层包中获取到对应的DSCP或flow label。
步骤1503，接入IAB node根据DSCP或flow label，向UE发送下行数据。
现有技术中，接入IAB节点是将下行数据通过DRB发送至UE。然而，在UE跨制式接入的场景下(比如：LTE UE通过WLAN制式接入IAB节点)，接入IAB节点的WLAN空口并不能将下行数据通过DRB发送至UE，因为WLAN制式不识别DRB。为此，本申请上述方案，接入IAB节点可以获取到下行数据包对应的DSCP或流标签，并根据DSCP或流标签向UE发送下行数据。由于WLAN制式能识别DSCP或流标签，从而实现了下行 数据的正确发送，确保了跨制式接入场景下用户设备数据传输的QoS保障。
下面给出上述过程的具体示例。
方案一、Donor-CU为接入IAB node配置的下行映射关系包括：隧道标识<->DSCP/flow label。
该方案中，接入IAB node从GTP隧道中提取出UE的下行数据后，根据Donor-CU配置的隧道标识<->DSCP/flow label的映射关系，确定该UE的下行数据对应的DSCP/flow label，IAB node沿用空口(如WLAN)的现有机制，根据获取到的DSCP/flow label值来识别UE业务并进行业务QoS的保障。
为了让UE能够识别收到的下行数据送到哪个PDCP实体进行处理，接入IAB node还可以将隧道标识对应的DRB ID/E-RAB ID/QFI携带在适配层中随下行数据一起发送到UE。
方案二、Donor-CU决定UE业务类型与DSCP/flow label的下行映射关系，并根据下行映射关系将对应的DSCP/flow label值携带在适配层中随下行数据一起发送到接入IAB node。
对于LTE UE而言，UE业务类型可以通过DRB ID、E-RAB ID、GTP TEID或GTP TEID+IP地址来表示。即上述下行映射关系可以是：DRB ID<->DSCP/flow label，或者，E-RAB ID<->DSCP/flow label，或者，GTP TEID<->DSCP/flow label，或者，GTP TEID+IP地址<->DSCP/flow label。
对于NR UE而言，UE业务类型可以通过DRB ID、QFI、GTP TEID或GTP TEID+IP地址来表示。即上述下行映射关系可以是：DRB ID<->DSCP/flow label，或者，QFI<->DSCP/flow label，或者，GTP TEID<->DSCP/flow label，或者，GTP TEID+IP地址<->DSCP/flow label。
Donor-CU决定UE业务类型与DSCP/flow label的映射关系后，将对应的DSCP/flow label值携带在适配层中随下行数据一起发送到接入IAB node。
该方案中，接入IAB node(即接入IAB-MT)从适配层中提取出DSCP/flow label，并从GTP隧道中提取出UE的下行数据后，可以获知该UE的下行数据对应的DSCP/flow label，然后接入IAB node(即接入IAB-DU)沿用空口(如WLAN)的现有机制，根据获取到的DSCP/flow label值来识别UE业务并进行业务QoS的保障。或者，接入IAB node(即接入IAB-DU)的适配层为下行数据添加适配层头，得到适配层包，该适配层包携带适配层头和该下行数据，该适配层头携带DSCP/flow label。然后接入IAB node(即接入IAB-DU)的适配层将适配层包发送到适配层的下层(如WLAN L2)，由接入IAB node(即IAB-DU)的WLAN L2按照现有机制,根据获取到的DSCP/flow label值来识别UE业务并执行UE业务的QoS保障。可选的，为了让UE能够识别收到的下行数据送到哪个PDCP实体进行处理，接入IAB node还可以将隧道标识对应的DRB ID/E-RAB ID/QFI携带在适配层中随下行数据进一步发送到UE。
基于上述实施例一，设计了LTE/NR UE通过WLAN、蓝牙、zigbee等接入技术接入网络的场景(即接入链路采用WLAN、蓝牙、zigbee等接入技术，回传链路采用NR接入技术)下的上行和下行承载映射方案，确保UE上行数据和下行数据传输过程中的QoS保障。
实施例二
该实施例用于解决上述问题2，具体的，在WLAN、蓝牙或zigbee制式下，如何保证回传链路上UE数据的按序接收。
如图11所示，接入IAB node和Donor-DU之间采用NR制式。不同于LTE RLC层的功能，NR RLC层取消了按序递交数据的功能，从而导致接收端PDCP层收到的数据可能乱序。
以LTE UE通过WLAN接入技术接入网络场景为例，由于UE和接入IAB node之间采用WLAN接入技术，而WLAN接入技术使用先进先出(First Input First Output，FIFO)机制，从而可以保证UE数据在该接口上的按序传输和接收。可是，由于接入IAB node和Donor-DU之间采用NR接入技术，而NR RLC层无法保证按序向上层(NR PDCP层)递交UE的数据，从而导致接收端PDCP层收到的UE数据的乱序。
本申请实施例以单跳回传链路场景为例进行说明，本专利方案同样适用两跳或多跳回传链路场景，这里不再赘述。
为了解决该问题，本申请实施例提供两种不同的解决方案。
方案一、在接入IAB node的GTP层和Donor-CU的GTP层引入重排序功能。
如图16所示，为本申请实施例提供的一种通信方法。该方法由接入IAB node或IAB donor执行。这里的接入IAB节点(接入IAB node)，也即UE接入的IAB节点。对于接入IAB节点的具体含义，可参考前述描述。
该方法包括以下步骤：
步骤1601，第一设备从第二设备接收至少两个数据包，其中，每个数据包携带一个GTP层的GTP序号。
步骤1602，第一设备根据GTP层的GTP序号，对接收到的至少两个数据包进行重排序。
其中，第一设备是接入IAB node，第二设备是IAB donor。或者，第一设备是IAB donor，第二设备是接入IAB node。
基于上述方案，解决了LTE UE接入网络后如何保证回传链路上UE数据的按序接收问题，避免回传链路上数据乱序导致的丢包。
可选的，IAB donor可以向接入IAB node发送指示信息，该指示信息用于指示接入IAB node的GTP层开启或关闭重排序功能。从而，接入IAB node可以根据该指示信息开启或关闭GTP层的重排序功能。
方案二、LTE PDCP层打开重排序功能。
如图17所示，为本申请实施例提供的一种通信方法。该方法由UE执行。该方法包括以下步骤：
步骤1701，UE从IAB donor接收UE的业务承载标识和指示信息，该指示信息用于指示业务承载标识对应的PDCP实体开启或关闭重排序功能。
其中，该UE为LTE UE，该UE通过NR回传链路接入网络。
该指示信息与业务承载标识对应，可选的，该业务承载标识为DRB ID。
步骤1702，UE根据业务承载标识和指示信息，开启或关闭PDCP实体的重排序功能。
在现有机制中，只有切换场景下，LTE PDCP层才打开重排序功能，其他场景下LTE PDCP层不打开重排序功能。由于LTE RLC层具有向上层LTE PDCP层按序递交数据的功能，从而可以保证LTE PDCP层按序从底层(LTE RLC层)接收数据。而在上述方案中，一旦IAB donor(比如可以是Donor-CU)获知LTE UE通过NR回传链路接入网络，则IAB donor打开LTE PDCP层的重排序功能，并指示UE打开LTE PDCP层的重排序功能。也就是说，IAB donor向UE发送一个指示信息，该指示信息用于指示UE是否打开PDCP重排序功能。该指示信息是per DRB指示的，可以携带在RRC消息中发送。其中，每个DRB对应一个PDCP实体，针对每个PDCP实体指示是否开启重排序功能。
基于上述方案，解决了LTE UE接入网络后如何保证回传链路上UE数据的按序接收问题，避免回传链路上数据乱序导致的丢包。
实施例三
该实施例用于解决上述问题3，具体的，在WLAN、蓝牙或zigbee制式下，如何为不同类型的UE选择接入的核心网设备。
对于LTE UE，Donor-CU需要为其选择LTE的核心网设备，例如：控制面设备(如移动性管理实体(mobility management entity，MME))，用户面设备(如服务网关(Serving GateWay，SGW)/分组数据网网关(PDN Gateway，PGW))。对于NR UE，Donor-CU需要为其选择NR的核心网设备，例如：控制面设备(如接入与移动性管理功能(Access and Mobility Management Function，AMF)网元)，用户面设备(如用户面功能(user plane function，UPF)网元)。因此，跨制式接入场景下，Donor-CU需要识别接入UE的类型，以便选择对应的核心网。
如图18所示，为本申请实施例提供的一种通信方法。该方法由接入IAB node执行。这里的接入IAB节点(接入IAB node)，也即UE接入的IAB节点。对于接入IAB节点的具体含义，可参考前述描述。
该方法包括以下步骤：
步骤1801，接入IAB node确定UE的类型或UE待接入的核心网的类型。
步骤1802，接入IAB node向IAB donor发送第一指示信息，第一指示信息用于指示UE的类型，或用于指示UE待接入的核心网的类型，或用于指示UE是否接入NR核心网，或用于指示UE是否接入LTE核心网，第一指示信息用于IAB donor为UE选择接入的核心网。
比如，UE初始入网过程中，接入IAB node可以通过F1AP消息(例如可以是Initial UL RRC Message Transfer消息)向IAB donor发送该第一指示信息。
比如，第一指示信息用于指示UE的类型为NR或LTE。再比如，第一指示信息用于指示UE待接入的核心网的类型为NR核心网(即5GC)或LTE核心网(即EPC)。再比如，第一指示信息用于指示UE接入NR核心网，或指示UE不接入NR核心网。若指示UE不接入NR核心网，则IAB donor确定UE接入LTE核心网。再比如，第一指示信息用于指示UE接入LTE核心网，或指示UE不接入LTE核心网。若指示UE不接入LTE核心 网，则IAB donor确定UE接入NR核心网。
基于上述方案，解决了IAB donor如何为UE选择对应的核心网设备的问题，从而使得在跨制式接入场景下IAB donor根据接收到的指示信息为UE选择对应的核心网，可以保证UE接入网络后的正常操作，保障了跨制式接入场景下用户设备数据的正常传输。
作为一种实现方法，上述步骤1801中，接入IAB node可以根据UE接入的小区频点，确定UE的类型。或者，接入IAB node从UE接收第二指示信息，第二指示信息用于指示UE的类型。
作为一种实现方法，上述步骤1801中，接入IAB node可以从UE接收第三指示信息，根据第三指示信息确定UE待接入的核心网的类型，该第三指示信息用于指示UE待接入的核心网的类型，或用于指示UE是否接入NR核心网，或用于指示UE是否接入LTE核心网。
本申请实施例适用于单跳、两跳或者多跳回传链路场景。
实施例四
该实施例用于解决上述问题4，具体的，IAB donor如何获知UE在空口使用的接入制式。
跨制式接入场景下IAB donor需要识别LTE/NR UE在空口使用的接入制式(NR、LTE、WLAN、蓝牙、zigbee等)，以便进行不同的承载映射判决。
如图19所示，为本申请实施例提供的一种通信方法。该方法由IAB donor执行。该方法包括以下步骤：
步骤1901，IAB donor接收第一指示信息。
步骤1902，IAB donor根据第一指示信息，确定UE空口使用的接入制式。
基于上述方案，IAB donor(比如可以是Donor-CU)可以根据接收到的第一指示信息确定UE空口使用的接入制式，从而可以根据获知的UE空口使用的接入制式为UE配置不同的承载映射策略，保证UE接入网络后的正常操作，保障了跨制式接入场景下用户设备数据的正常传输。
在一种实现方法中，上述步骤1901的具体实现比如可以是：UE选择一种制式接入IAB node，该接入IAB node可以获知UE接入使用的制式，然后将第一指示信息携带于F1AP消息中发送到IAB donor。示例性的，该F1AP消息可以是Initial UL RRC Message Transfer消息。
作为另一种实现方法，上述步骤1901的具体实现比如可以是：上述第一指示信息不是由接入IAB node携带在F1AP消息中发送到IAB donor的，而是由UE将该第一指示信息携带在RRC消息(比如可以是RRC连接建立完成消)中发送到IAB donor。
在一种实现方法中，上述步骤1902的具体实现比如可以是：第一指示信息用于指示UE正在使用的接入制式，IAB donor根据第一指示信息，同意UE使用正在使用的接入制式。
在一种实现方法中，上述步骤1902的具体实现比如可以是：第一指示信息用于指示UE正在使用的接入制式，IAB donor根据第一指示信息，不同意UE使用正在使用的接入制式。则IAB donor重新确定一个接入制式，并向UE发送RRC消息(比如可以是RRC  Release消息或者RRCReconfiguration消息)，该RRC消息携带第二指示信息，该第二指示信息用于指示IAB donor确定空口使用的接入制式，从而UE根据第二指示信息确定空口使用的接入制式，并根据IAB donor确定的UE空口使用的接入制式接入网络。
需要说明的是，以上不同实施例可用于解决上述提到的UE跨制式接入场景下的不同技术问题。在具体实施中，上述用于解决不同技术问题的不同实施例之间可以相互组合实施。本申请的保护范围既包括各个单独实施例，也包括这些不同实施例之间的组合方案。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
可以理解的是，上述各个方法实施例中，对应由UE实现的步骤或者操作，也可以由配置于UE的部件(例如芯片或者电路)实现，对应由IAB节点实现的步骤或者操作，也可以由配置于IAB节点的部件(例如芯片或者电路)实现，对应由IAB宿主节点实现的步骤或者操作，也可以由配置于IAB宿主节点的部件(例如芯片或者电路)实现。
参考图20，为本申请实施例提供的一种通信装置的示意图。该装置用于实现上述各个实施例中对应用户设备、IAB节点、IAB宿主节点所执行的各个步骤，如图20所示，该装置2000包括收发单元2010和处理单元2020。
在第一个实施例中，通信装置2000用于UE：
处理单元2020，用于确定上行数据对应的第一信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载；根据所述第一信息，确定第二信息，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；收发单元2010，用于根据所述第二信息，使用第二制式的空口技术发送所述上行数据。
在一种可能的实现方法中，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
在一种可能的实现方法中，所述第二信息为差分服务代码点DSCP或流标签。
在一种可能的实现方法中，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
在一种可能的实现方法中，所述处理单元2020，用于根据第一信息，确定第二信息，具体包括：用于根据配置的所述第一信息与所述第二信息的映射关系，确定所述第一信息对应的所述第二信息。
在一种可能的实现方法中，所述收发单元2010，还用于从接入回传一体化IAB宿主节点接收无线资源控制RRC消息，所述RRC消息中携带所述第一信息和所述第二信息，其中，所述第一信息和所述第二信息对应。
在一种可能的实现方法中，所述装置为UE，所述UE包括适配层，所述收发单元2010，还用于通过所述UE的适配层向所述适配层的下层发送所述第二信息；所述收发单元2010，用于根据所述第二信息，使用第二制式的空口技术发送所述上行数据，具体包括：用于通过所述适配层的下层根据所述第二信息，使用第二制式的空口发送所述上行数据。
在一种可能的实现方法中，所述收发单元2010，还用于通过所述UE的适配层向所述适配层的下层发送所述第二信息，包括：用于通过所述适配层向所述适配层的下层发送控制信息，所述控制信息用于指示所述第二信息。
在一种可能的实现方法中，所述收发单元2010，还用于通过所述UE的适配层向所述适配层的下层发送所述第二信息，包括：用于通过所述适配层为所述上行数据添加适配层头，所述适配层头携带所述第二信息；用于通过所述适配层向所述适配层的下层发送适配层包，所述适配层包携带所述适配层头。
在一种可能的实现方法中，所述适配层头还携带所述第一信息。
在第二个实施例中，通信装置2000用于接入IAB节点：
收发单元2010，用于接收来自用户设备UE的数据包，所述数据包携带上行数据，以及携带第一信息和/或第二信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；将所述上行数据映射到隧道标识对应的通用分组无线服务隧道协议GTP隧道中发送至IAB宿主节点；处理单元2020，用于根据所述第一信息或所述第二信息，确定所述隧道标识；其中，所述隧道标识包括GTP TEID，或者包括GTP TEID和因特网协议IP地址。
在一种可能的实现方法中，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
在一种可能的实现方法中，所述第二信息为差分服务代码点DSCP或流标签。
在一种可能的实现方法中，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
在一种可能的实现方法中，所述处理单元2020，用于根据所述第一信息，确定隧道标识，包括：用于根据配置的所述第一信息与所述隧道标识的映射关系，确定所述第一信息对应的所述隧道标识。
在一种可能的实现方法中，所述收发单元2010，还用于从所述IAB宿主节点接收无线资源控制RRC消息或F1AP消息，所述RRC消息或F1AP消息携带所述第一信息和所述隧道标识，其中所述第一信息和所述隧道标识对应。
在一种可能的实现方法中，所述处理单元2020，用于根据所述第二信息，确定所述隧道标识，包括：用于根据配置的所述第二信息与所述隧道标识的映射关系，确定所述第二信息对应的所述隧道标识。
在一种可能的实现方法中，所述收发单元2010，还用于从所述IAB宿主节点接收RRC消息或F1AP消息，所述RRC消息或F1AP消息携带所述第二信息和所述隧道标识，其中所述第二信息与所述隧道标识对应。
在第三个实施例中，通信装置2000用于接入IAB节点：
收发单元2010，用于接收IAB宿主节点通过通用分组无线服务隧道协议GTP隧道发送的下行数据，所述GTP隧道的隧道标识包括GTP TEID或者包括GTP TEID和因特网IP地址；根据所述下行数据对应的差分服务代码点DSCP或流标签，向用户设备UE发送所述下行数据；处理单元2020，用于确定所述下行数据对应的所述DSCP或所述流标签。
在一种可能的实现方法中，所述处理单元2020，用于确定所述下行数据对应的所述DSCP或所述流标签，具体包括：用于根据所述隧道标识，以及所述隧道标识与所述DSCP的映射关系，确定所述DSCP；或者，用于根据所述隧道标识，以及所述隧道标识与所述流标签的映射关系，确定所述流标签。
在一种可能的实现方法中，所述收发单元2010，还用于从所述IAB宿主节点接收所述隧道标识和所述DSCP，其中，所述隧道标识与所述DSCP对应；或者，从所述IAB宿主节点接收所述隧道标识和所述流标签，其中，所述隧道标识与所述流标签对应。
在一种可能的实现方法中，所述处理单元2020，用于确定所述下行数据对应的所述DSCP或所述流标签，具体包括：用于通过所述收发单元2010从所述IAB宿主节点接收适配层包，所述适配层包携带所述DSCP或流标签。
在一种可能的实现方法中，所述收发单元2010，用于向UE发送下行数据，具体包括：用于向所述UE发送数据包，所述数据包携带所述下行数据，以及携带所述隧道标识对应的数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI。
在第四个实施例中，通信装置2000用于第一设备：
收发单元2010，用于从第二设备接收至少两个数据包，其中，每个数据包携带一个通用分组无线服务隧道协议GTP层的GTP序号；处理单元2020，用于根据所述GTP层的GTP序号，对所述至少两个数据包进行重排序；所述第一设备是UE接入的接入回传一体化IAB节点，所述第二设备是IAB宿主节点；或者，所述第一设备是IAB宿主节点，所述第二设备是接入IAB节点。
在一种可能的实现方法中，若所述第一设备是接入IAB节点，所述第二设备是IAB宿主节点，所述收发单元2010，还用于从所述第二设备接收指示信息，所述指示信息用于指示第一设备的GTP层开启或关闭重排序功能。
在一种可能的实现方法中，若所述第一设备是IAB宿主节点，所述第二设备是IAB节点，所述收发单元2010，还用于向所述第二设备发送指示信息，所述指示信息用于指示第二设备的GTP层开启或关闭重排序功能。
在第五个实施例中，通信装置2000用于用户设备：
收发单元2010，用于从接入回传一体化IAB宿主节点接收UE的业务承载标识和指示信息，所述指示信息用于指示所述业务承载标识对应的分组数据汇聚协议PDCP实体开启或关闭重排序功能；处理单元2020，用于根据所述业务承载标识和所述指示信息，开启或关闭所述PDCP实体的重排序功能；其中，所述UE为长期演进LTE UE，所述UE通过新无线NR回传链路接入网络。
在一种可能的实现方法中，所述指示信息与所述业务承载标识对应，所述业务承载标识为数据无线承载标识DRB ID。
在第六个实施例中，通信装置2000用于接入IAB节点：
处理单元2020，用于确定用户设备UE的类型或所述UE待接入的核心网的类型；收发单元2010，用于向IAB宿主节点发送第一指示信息，所述第一指示信息用于指示所述UE的类型，或用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网，所述第一指示信息用于所述IAB宿主节点为所述UE选择接入的核心网。
在一种可能的实现方法中，所述处理单元2020，用于确定UE的类型，具体包括：用于根据所述UE接入的小区频点，确定所述UE的类型；或者，用于通过所述收发单元2010从所述UE接收第二指示信息，所述第二指示信息用于指示所述UE的类型。
在一种可能的实现方法中，所述处理单元2020，用于确定所述UE待接入的核心网的类型，具体包括：用于通过所述收发单元2010从所述UE接收第三指示信息，所述第三指示信息用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网。
在一种可能的实现方法中，所述UE的类型为长期演进LTE UE、或新无线NR UE。
在第七个实施例中，通信装置2000用于IAB宿主节点：
收发单元2010，用于接收第一指示信息；处理单元2020，用于根据所述第一指示信息，确定用户设备UE空口使用的接入制式。
在一种可能的实现方法中，所述收发单元2010，用于接收第一指示信息，具体包括：用于从所述UE接收第一RRC消息，所述第一RRC消息携带所述第一指示信息；或者，用于从所述UE的接入IAB节点接收F1AP消息，所述F1AP消息携带所述第一指示信息。
在一种可能的实现方法中，所述收发单元2010，还用于向所述UE发送第二RRC消息，所述第二RRC消息携带第二指示信息，所述第二指示信息用于指示所述IAB宿主节点确定空口使用的接入制式，所述确定空口使用的接入制式用于所述UE根据确定的接入制式接入网络。
可选的，上述通信装置2000还可以包括存储单元，该存储单元用于存储数据或者指令(也可以称为代码或者程序)，上述各个单元可以和存储单元交互或者耦合，以实现对应的方法或者功能。例如，处理单元2020可以读取存储单元中的数据或者指令，使得通信装置实现上述实施例中的方法。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集 成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上收发单元2010是一种该装置的接口电路，用于从其它装置接收信号或向其它装置发送信号。例如，当该装置以芯片的方式实现时，该收发单元2010是该芯片用于从其它芯片或装置接收信号的接口电路，或是用于向其它芯片或装置发送信号的接口电路。
参考图21，为本申请实施例提供的一种通信装置示意图，用于实现以上实施例中IAB节点或IAB宿主节点的操作。如图21所示，该通信装置包括：处理器2110和接口2130，可选的，该通信装置还包括存储器2120。接口2130用于实现与其他设备进行通信。
以上实施例中IAB节点或IAB宿主节点执行的方法可以通过处理器2110调用存储器(可以是IAB节点或IAB宿主节点中的存储器2120，也可以是外部存储器)中存储的程序来实现。即，IAB节点或IAB宿主节点可以包括处理器2110，该处理器2110通过调用存储器中的程序，以执行以上方法实施例中IAB节点或IAB宿主节点执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。IAB节点或IAB宿主节点可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
具体的，图20中的收发单元2010和处理单元2020的功能/实现过程可以通过图21所示的通信装置2100中的处理器2110调用存储器2120中存储的计算机可执行指令来实现。或者，图20中的处理单元2020的功能/实现过程可以通过图21所示的通信装置2100中的处理器2110调用存储器2120中存储的计算机执行指令来实现，图20中的收发单元2010的功能/实现过程可以通过图21中所示的通信装置2100中的接口2130来实现。
参考图22，其为本申请实施例提供的一种用户设备的结构示意图。该用户设备用于实现以上实施例中用户设备的操作。如图22所示，该用户设备包括：天线2210、射频装置2220、信号处理部分2230。天线2210与射频装置2220连接。在下行方向上，射频装置2220通过天线2210接收接入设备发送的信息，将接入设备发送的信息发送给信号处理部分2230进行处理。在上行方向上，信号处理部分2230对用户设备的信息进行处理，并发送给射频装置2220，射频装置2220对用户设备的信息进行处理后经过天线2210发送给接入设备。
信号处理部分2230用于实现对数据各通信协议层的处理。信号处理部分2230可以为该用户设备的一个子系统，则该用户设备还可以包括其它子系统，例如中央处理子系统，用于实现对用户设备操作系统以及应用层的处理；再如，周边子系统用于实现与其它设备的连接。信号处理部分2230可以为单独设置的芯片。可选的，以上的装置可以位于信号处理部分2230。
信号处理部分2230可以包括一个或多个处理元件2231，例如，包括一个主控CPU和 其它集成电路，以及包括接口电路2233。此外，该信号处理部分2230还可以包括存储元件2232。存储元件2232用于存储数据和程序，用于执行以上方法中用户设备所执行的方法的程序可能存储，也可能不存储于该存储元件2232中，例如，存储于信号处理部分2230之外的存储器中，使用时信号处理部分2230加载该程序到缓存中进行使用。接口电路2233用于与装置通信。以上装置可以位于信号处理部分2230，该信号处理部分2230可以通过芯片实现，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上用户设备执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如该装置包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中用户设备执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件。
在另一种实现中，用于执行以上方法中用户设备所执行的方法的程序可以在与处理元件处于不同芯片上的存储元件，即片外存储元件。此时，处理元件从片外存储元件调用或加载程序于片内存储元件上，以调用并执行以上方法实施例中用户设备执行的方法。
在又一种实现中，用户设备实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件设置于信号处理部分2230上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
实现以上方法中各个步骤的单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现，该SOC芯片，用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现以上用户设备执行的方法；或者，该芯片内可以集成至少一个集成电路，用于实现以上用户设备执行的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
可见，以上装置可以包括至少一个处理元件和接口电路，其中至少一个处理元件用于执行以上方法实施例所提供的任一种用户设备执行的方法。处理元件可以以第一种方式：即调用存储元件存储的程序的方式执行用户设备执行的部分或全部步骤；也可以以第二种方式：即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行用户设备执行的部分或全部步骤；当然，也可以结合第一种方式和第二种方式执行用户设备执行的部分或全部步骤。
这里的处理元件同以上描述，可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。存储元件可以是一个存储器，也可以是多个存储元件的统称。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”、“任意一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的 任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒 介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(英文：Digital Versatile Disc，简称：DVD)、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。本申请说明书的上述描述可以使得本领域技术任何可以利用或实现本申请的内容，任何基于所公开内容的修改都应该被认为是本领域显而易见的，本申请所描述的基本原则可以应用到其它变形中而不偏离本申请的发明本质和范围。因此，本申请所公开的内容不仅仅局限于所描述的实施例和设计，还可以扩展到与本申请原则和所公开的新特征一致的最大范围。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (77)

  1. 一种通信方法，其特征在于，包括：
    用户设备UE确定上行数据对应的第一信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载；
    所述UE根据所述第一信息，确定第二信息，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；
    所述UE根据所述第二信息，使用第二制式的空口技术发送所述上行数据。
  2. 如权利要求1所述的方法，其特征在于，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
  3. 如权利要求1或2所述的方法，其特征在于，所述第二信息为差分服务代码点DSCP或流标签。
  4. 如权利要求1-3任一所述的方法，其特征在于，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
  5. 如权利要求1-4任一所述的方法，其特征在于，所述UE根据第一信息，确定第二信息，包括：
    所述UE根据配置的所述第一信息与所述第二信息的映射关系，确定所述第一信息对应的所述第二信息。
  6. 如权利要求5所述的方法，其特征在于，还包括：
    所述UE从接入回传一体化IAB宿主节点接收无线资源控制RRC消息，所述RRC消息中携带所述第一信息和所述第二信息，其中，所述第一信息和所述第二信息对应。
  7. 如权利要求1-6任一所述的方法，其特征在于，所述UE包括适配层，所述方法还包括：
    所述UE的适配层向所述适配层的下层发送所述第二信息；
    所述UE根据所述第二信息，使用第二制式的空口技术发送所述上行数据，包括：
    所述适配层的下层根据所述第二信息，使用第二制式的空口发送所述上行数据。
  8. 如权利要求7所述的方法，其特征在于，所述UE的适配层向所述适配层的下层发送所述第二信息，包括：
    所述适配层向所述适配层的下层发送控制信息，所述控制信息用于指示所述第二信息。
  9. 如权利要求7所述的方法，其特征在于，所述UE的适配层向所述适配层的下层发送所述第二信息，包括：
    所述适配层为所述上行数据添加适配层头，所述适配层头携带所述第二信息；
    所述适配层向所述适配层的下层发送适配层包，所述适配层包携带所述适配层头。
  10. 如权利要求9所述的方法，其特征在于，所述适配层头还携带所述第一信息。
  11. 一种通信方法，其特征在于，包括：
    接入回传一体化IAB节点接收来自用户设备UE的数据包，所述数据包携带上行数据，以及携带第一信息和/或第二信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；
    所述IAB节点根据所述第一信息或所述第二信息，确定通用分组无线服务隧道协议 GTP隧道的隧道标识；
    所述IAB节点向IAB宿主节点发送映射到所述隧道标识对应的GTP隧道中的所述上行数据。
  12. 如权利要求11所述的方法，其特征在于，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
  13. 如权利要求11或12所述的方法，其特征在于，所述第二信息为差分服务代码点DSCP或流标签。
  14. 如权利要求11-13任一所述的方法，其特征在于，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
  15. 如权利要求11-14任一所述的方法，其特征在于，所述IAB节点根据所述第一信息，确定GTP隧道的隧道标识，包括：
    所述IAB节点根据配置的所述第一信息与所述隧道标识的映射关系，确定所述第一信息对应的所述隧道标识。
  16. 如权利要求15所述的方法，其特征在于，还包括：
    所述IAB节点从所述IAB宿主节点接收无线资源控制RRC消息或F1接口应用协议F1AP消息，所述RRC消息或F1AP消息携带所述第一信息和所述隧道标识，其中所述第一信息和所述隧道标识对应。
  17. 如权利要求11-14任一所述的方法，其特征在于，所述IAB节点根据所述第二信息，确定所述GTP隧道的隧道标识，包括：
    所述IAB节点根据配置的所述第二信息与所述隧道标识的映射关系，确定所述第二信息对应的所述隧道标识。
  18. 如权利要求17所述的方法，其特征在于，还包括：
    所述IAB节点从所述IAB宿主节点接收RRC消息或F1AP消息，所述RRC消息或F1AP消息携带所述第二信息和所述隧道标识，其中所述第二信息与所述隧道标识对应。
  19. 一种通信方法，其特征在于，包括：
    接入回传一体化IAB节点接收IAB宿主节点通过通用分组无线服务隧道协议GTP隧道发送的下行数据；
    所述IAB节点确定所述下行数据对应的差分服务代码点DSCP或流标签；
    所述IAB节点根据所述DSCP或所述流标签，向所述UE发送所述下行数据。
  20. 如权利要求19所述的方法，其特征在于，所述IAB节点确定所述下行数据对应的DSCP或流标签，包括：
    所述IAB节点根据所述隧道标识，以及所述隧道标识与所述DSCP的映射关系，确定所述DSCP；或者，
    所述IAB节点根据所述隧道标识，以及所述隧道标识与所述流标签的映射关系，确定所述流标签。
  21. 如权利要求20所述的方法，其特征在于，还包括：
    所述IAB节点从所述IAB宿主节点接收所述隧道标识和所述DSCP，其中，所述隧道标识与所述DSCP对应；或者，
    所述IAB节点从所述IAB宿主节点接收所述隧道标识和所述流标签，其中，所述隧道 标识与所述流标签对应。
  22. 如权利要求19所述的方法，其特征在于，所述IAB节点确定所述下行数据对应的DSCP或流标签，包括：
    所述IAB节点从所述IAB宿主节点接收适配层包，所述适配层包携带所述DSCP或流标签。
  23. 如权利要求19-22任一所述的方法，其特征在于，所述IAB节点向UE发送所述下行数据，包括：
    所述IAB节点向UE发送数据包，所述数据包携带所述下行数据，以及携带所述隧道标识对应的数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的至少一种。
  24. 一种通信方法，其特征在于，包括：
    第一设备从第二设备接收至少两个数据包，其中，每个数据包携带一个通用分组无线服务隧道协议GTP层的GTP序号；
    所述第一设备根据所述GTP层的GTP序号，对所述至少两个数据包进行重排序；
    所述第一设备是接入回传一体化IAB节点，所述第二设备是IAB宿主节点；或者，所述第一设备是IAB宿主节点，所述第二设备是IAB节点。
  25. 如权利要求24所述的方法，其特征在于，若所述第一设备是IAB节点，所述第二设备是IAB宿主节点，所述方法还包括：
    所述第一设备从所述第二设备接收指示信息，所述指示信息用于指示第一设备的GTP层开启或关闭重排序功能。
  26. 如权利要求24所述的方法，其特征在于，若所述第一设备是IAB宿主节点，所述第二设备是IAB节点，所述方法还包括：
    所述第一设备向所述第二设备发送指示信息，所述指示信息用于指示第二设备的GTP层开启或关闭重排序功能。
  27. 一种通信方法，其特征在于，包括：
    用户设备UE从接入回传一体化IAB宿主节点接收所述UE的业务承载标识和指示信息，所述指示信息用于指示所述业务承载标识对应的分组数据汇聚协议PDCP实体开启或关闭重排序功能；
    所述UE根据所述业务承载标识和所述指示信息，开启或关闭所述PDCP实体的重排序功能；
    其中，所述UE为长期演进LTE UE，所述UE通过新无线NR回传链路接入网络。
  28. 如权利要求27所述的方法，其特征在于，所述指示信息与所述业务承载标识对应，所述业务承载标识为数据无线承载标识DRB ID。
  29. 一种通信方法，其特征在于，包括：
    IAB节点确定用户设备UE的类型或所述UE待接入的核心网的类型；
    所述IAB节点向IAB宿主节点发送第一指示信息，所述第一指示信息用于指示所述UE的类型，或用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网，所述第一指示信息用于所述IAB宿主节点为所述UE选择接入的核心网。
  30. 如权利要求29所述的方法，其特征在于，所述IAB节点确定UE的类型，包括：
    所述IAB节点根据所述UE接入的小区频点，确定所述UE的类型；或者，
    所述IAB节点从所述UE接收第二指示信息，所述第二指示信息用于指示所述UE的类型。
  31. 如权利要求29所述的方法，其特征在于，所述IAB节点确定所述UE待接入的核心网的类型，包括：
    所述IAB节点从所述UE接收第三指示信息，所述第三指示信息用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网。
  32. 如权利要求29-31任一所述的方法，其特征在于，所述UE的类型为长期演进LTE UE、或新无线NR UE。
  33. 一种通信方法，其特征在于，包括：
    IAB宿主节点接收第一指示信息；
    所述IAB宿主节点根据所述第一指示信息，确定用户设备UE空口使用的接入制式。
  34. 如权利要求33所述的方法，其特征在于，所述IAB宿主节点接收第一指示信息，包括：
    所述IAB宿主节点从所述UE接收第一RRC消息，所述第一RRC消息携带所述第一指示信息；或者，
    所述IAB宿主节点从所述UE的接入IAB节点接收F1接口应用协议F1AP消息，所述F1AP消息携带所述第一指示信息。
  35. 如权利要求33或34所述的方法，其特征在于，还包括：
    所述IAB宿主节点向所述UE发送第二RRC消息，所述第二RRC消息携带第二指示信息，所述第二指示信息用于指示所述IAB宿主节点确定所述UE空口使用的接入制式，所述确定空口使用的接入制式用于所述UE根据确定的接入制式接入网络。
  36. 一种通信装置，其特征在于，包括：
    处理单元，用于确定上行数据对应的第一信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载；根据所述第一信息，确定第二信息，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；
    收发单元，用于根据所述第二信息，使用第二制式的空口技术发送所述上行数据。
  37. 如权利要求36所述的装置，其特征在于，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
  38. 如权利要求36或37所述的装置，其特征在于，所述第二信息为差分服务代码点DSCP或流标签。
  39. 如权利要求36-38任一所述的装置，其特征在于，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
  40. 如权利要求36-39任一所述的装置，其特征在于，所述处理单元，用于根据第一信息，确定第二信息，具体包括：
    用于根据配置的所述第一信息与所述第二信息的映射关系，确定所述第一信息对应的所述第二信息。
  41. 如权利要求40所述的装置，其特征在于，所述收发单元，还用于从接入回传一体化IAB宿主节点接收无线资源控制RRC消息，所述RRC消息中携带所述第一信息和所述第二信息，其中，所述第一信息和所述第二信息对应。
  42. 如权利要求36-41任一所述的装置，其特征在于，所述装置为UE，所述UE包括适配层，所述收发单元，还用于通过所述UE的适配层向所述适配层的下层发送所述第二信息；
    所述收发单元，用于根据所述第二信息，使用第二制式的空口技术发送所述上行数据，具体包括：用于通过所述适配层的下层根据所述第二信息，使用第二制式的空口发送所述上行数据。
  43. 如权利要求42所述的装置，其特征在于，所述收发单元，还用于通过所述UE的适配层向所述适配层的下层发送所述第二信息，包括：
    用于通过所述适配层向所述适配层的下层发送控制信息，所述控制信息用于指示所述第二信息。
  44. 如权利要求42所述的装置，其特征在于，所述收发单元，还用于通过所述UE的适配层向所述适配层的下层发送所述第二信息，包括：
    用于通过所述适配层为所述上行数据添加适配层头，所述适配层头携带所述第二信息；
    用于通过所述适配层向所述适配层的下层发送适配层包，所述适配层包携带所述适配层头。
  45. 如权利要求44所述的装置，其特征在于，所述适配层头还携带所述第一信息。
  46. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自用户设备UE的数据包，所述数据包携带上行数据，以及携带第一信息和/或第二信息，所述第一信息用于标识所述上行数据在第一制式下对应的业务类型或承载，所述第二信息用于标识所述上行数据在第二制式下对应的业务类型或承载，所述第二制式与所述第一制式不同；向IAB宿主节点发送映射到所述隧道标识对应的通用分组无线服务隧道协议GTP隧道中的所述上行数据。；
    处理单元，用于根据所述第一信息或所述第二信息，确定所述隧道标识。
  47. 如权利要求46所述的装置，其特征在于，所述第一信息为数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的一种。
  48. 如权利要求46或47所述的装置，其特征在于，所述第二信息为差分服务代码点DSCP或流标签。
  49. 如权利要求46-48任一所述的装置，其特征在于，所述第一制式为长期演进LTE或新无线NR，所述第二制式为无线局域网WLAN、蓝牙或紫蜂zigbee中的一种。
  50. 如权利要求46-49任一所述的装置，其特征在于，所述处理单元，用于根据所述第一信息，确定隧道标识，包括：
    用于根据配置的所述第一信息与所述隧道标识的映射关系，确定所述第一信息对应的所述隧道标识。
  51. 如权利要求50所述的装置，其特征在于，所述收发单元，还用于从所述IAB宿主节点接收无线资源控制RRC消息或F1接口应用协议F1AP消息，所述RRC消息或F1AP消息携带所述第一信息和所述隧道标识，其中所述第一信息和所述隧道标识对应。
  52. 如权利要求46-49任一所述的装置，其特征在于，所述处理单元，用于根据所述第二信息，确定所述隧道标识，包括：
    用于根据配置的所述第二信息与所述隧道标识的映射关系，确定所述第二信息对应的所述隧道标识。
  53. 如权利要求52所述的装置，其特征在于，所述收发单元，还用于从所述IAB宿主节点接收RRC消息或F1AP消息，所述RRC消息或F1AP消息携带所述第二信息和所述隧道标识，其中所述第二信息与所述隧道标识对应。
  54. 一种通信装置，其特征在于，包括：
    收发单元，用于接收IAB宿主节点通过通用分组无线服务隧道协议GTP隧道发送的下行数据；根据所述下行数据对应的差分服务代码点DSCP或流标签，向用户设备UE发送所述下行数据；
    处理单元，用于确定所述下行数据对应的所述DSCP或所述流标签。
  55. 如权利要求54所述的装置，其特征在于，所述处理单元，用于确定所述下行数据对应的所述DSCP或所述流标签，具体包括：
    用于根据所述隧道标识，以及所述隧道标识与所述DSCP的映射关系，确定所述DSCP；或者，
    用于根据所述隧道标识，以及所述隧道标识与所述流标签的映射关系，确定所述流标签。
  56. 如权利要求55所述的装置，其特征在于，所述收发单元，还用于从所述IAB宿主节点接收所述隧道标识和所述DSCP，其中，所述隧道标识与所述DSCP对应；或者，从所述IAB宿主节点接收所述隧道标识和所述流标签，其中，所述隧道标识与所述流标签对应。
  57. 如权利要求54所述的装置，其特征在于，所述处理单元，用于确定所述下行数据对应的所述DSCP或所述流标签，具体包括：
    用于通过所述收发单元从所述IAB宿主节点接收适配层包，所述适配层包携带所述DSCP或流标签。
  58. 如权利要求54-57任一所述的装置，其特征在于，所述收发单元，用于向UE发送下行数据，具体包括：用于向所述UE发送数据包，所述数据包携带所述下行数据，以及携带所述隧道标识对应的数据无线承载标识DRB ID、演进的通用陆基无线接入网无线接入承载标识E-RAB ID或服务质量流标识QFI中的至少一种。
  59. 一种通信装置，其特征在于，应用于第一设备，所述装置包括：
    收发单元，用于从第二设备接收至少两个数据包，其中，每个数据包携带一个通用分组无线服务隧道协议GTP层的GTP序号；
    处理单元，用于根据所述GTP层的GTP序号，对所述至少两个数据包进行重排序；
    所述第一设备是接入回传一体化IAB节点，所述第二设备是IAB宿主节点；或者，所述第一设备是IAB宿主节点，所述第二设备是IAB节点。
  60. 如权利要求59所述的装置，其特征在于，若所述第一设备是IAB节点，所述第二设备是IAB宿主节点，所述收发单元，还用于从所述第二设备接收指示信息，所述指示信息用于指示第一设备的GTP层开启或关闭重排序功能。
  61. 如权利要求59所述的装置，其特征在于，若所述第一设备是IAB宿主节点，所 述第二设备是IAB节点，所述收发单元，还用于向所述第二设备发送指示信息，所述指示信息用于指示第二设备的GTP层开启或关闭重排序功能。
  62. 一种通信装置，其特征在于，包括：
    收发单元，用于从接入回传一体化IAB宿主节点接收UE的业务承载标识和指示信息，所述指示信息用于指示所述业务承载标识对应的分组数据汇聚协议PDCP实体开启或关闭重排序功能；
    处理单元，用于根据所述业务承载标识和所述指示信息，开启或关闭所述PDCP实体的重排序功能；
    其中，所述UE为长期演进LTE UE，所述UE通过新无线NR回传链路接入网络。
  63. 如权利要求62所述的装置，其特征在于，所述指示信息与所述业务承载标识对应，所述业务承载标识为数据无线承载标识DRB ID。
  64. 一种通信装置，其特征在于，包括：
    处理单元，用于确定用户设备UE的类型或所述UE待接入的核心网的类型；
    收发单元，用于向IAB宿主节点发送第一指示信息，所述第一指示信息用于指示所述UE的类型，或用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网，所述第一指示信息用于所述IAB宿主节点为所述UE选择接入的核心网。
  65. 如权利要求64所述的装置，其特征在于，所述处理单元，用于确定UE的类型，具体包括：
    用于根据所述UE接入的小区频点，确定所述UE的类型；或者，
    用于通过所述收发单元从所述UE接收第二指示信息，所述第二指示信息用于指示所述UE的类型。
  66. 如权利要求64所述的装置，其特征在于，所述处理单元，用于确定所述UE待接入的核心网的类型，具体包括：
    用于通过所述收发单元从所述UE接收第三指示信息，所述第三指示信息用于指示所述UE待接入的核心网的类型，或用于指示所述UE是否接入NR核心网，或用于指示所述UE是否接入LTE核心网。
  67. 如权利要求64-66任一所述的装置，其特征在于，所述UE的类型为长期演进LTE UE、或新无线NR UE。
  68. 一种通信装置，其特征在于，包括：
    收发单元，用于接收第一指示信息；
    处理单元，用于根据所述第一指示信息，确定用户设备UE空口使用的接入制式。
  69. 如权利要求68所述的装置，其特征在于，所述收发单元，用于接收第一指示信息，具体包括：
    用于从所述UE接收第一RRC消息，所述第一RRC消息携带所述第一指示信息；或者，
    用于从所述UE的接入IAB节点接收F1接口应用协议F1AP消息，所述F1AP消息携带所述第一指示信息。
  70. 如权利要求68或69所述的装置，其特征在于，所述收发单元，还用于向所述UE发送第二RRC消息，所述第二RRC消息携带第二指示信息，所述第二指示信息用于指示 所述IAB宿主节点确定所述UE空口使用的接入制式，所述确定空口使用的接入制式用于所述UE根据确定的接入制式接入网络。
  71. 一种通信装置，其特征在于，包括：通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求1至35任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求1至35任一项所述的方法中，在所述装置进行的消息处理或控制操作。
  72. 一种通信装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述通信装置运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述通信装置执行如权利要求1至35任一项所述的通信方法。
  73. 一种芯片系统，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，使得安装有所述芯片系统的设备执行如利要求1至35任一项所述的通信方法。
  74. 一种通信装置，其特征在于，用于执行权利要求1至35任一项所述的方法。
  75. 一种芯片系统，其特征在于，包括：至少一个处理器和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求1至35任一项所述的方法。
  76. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述权利要求1至35任一项所述的方法。
  77. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1至35任一项所述的方法。
PCT/CN2020/101477 2020-07-10 2020-07-10 通信方法及装置 WO2022006907A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/101477 WO2022006907A1 (zh) 2020-07-10 2020-07-10 通信方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/101477 WO2022006907A1 (zh) 2020-07-10 2020-07-10 通信方法及装置

Publications (1)

Publication Number Publication Date
WO2022006907A1 true WO2022006907A1 (zh) 2022-01-13

Family

ID=79553592

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/101477 WO2022006907A1 (zh) 2020-07-10 2020-07-10 通信方法及装置

Country Status (1)

Country Link
WO (1) WO2022006907A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114867071A (zh) * 2022-03-25 2022-08-05 成都中科微信息技术研究院有限公司 一种QoS流与DRB聚合关系建立方法、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351700A (zh) * 2018-04-05 2019-10-18 中兴通讯股份有限公司 一种自接入回传链路的中继转发方法及节点
CN110351024A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 数据传输方法和装置
WO2019216670A1 (en) * 2018-05-09 2019-11-14 Samsung Electronics Co., Ltd. Methods and systems for routing data through iab nodes in 5g communication networks
CN110475351A (zh) * 2018-05-11 2019-11-19 华为技术有限公司 数据处理的方法和设备
CN111148158A (zh) * 2018-11-02 2020-05-12 华为技术有限公司 一种通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351024A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 数据传输方法和装置
CN110351700A (zh) * 2018-04-05 2019-10-18 中兴通讯股份有限公司 一种自接入回传链路的中继转发方法及节点
WO2019216670A1 (en) * 2018-05-09 2019-11-14 Samsung Electronics Co., Ltd. Methods and systems for routing data through iab nodes in 5g communication networks
CN110475351A (zh) * 2018-05-11 2019-11-19 华为技术有限公司 数据处理的方法和设备
CN111148158A (zh) * 2018-11-02 2020-05-12 华为技术有限公司 一种通信方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Email discussion [105#47] [NR_IAB-Core] Bearer Mapping", 3GPP TSG-RAN WG2 MEETING #105BIS R2-1903964, 12 April 2019 (2019-04-12), XP051709629 *
HUAWEI: "Bearer Mapping in Donor-DU and IAB Node", 3GPP TSG-RAN WG3 MEETING #103 R3-190500, 1 March 2018 (2018-03-01), XP051604440 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114867071A (zh) * 2022-03-25 2022-08-05 成都中科微信息技术研究院有限公司 一种QoS流与DRB聚合关系建立方法、电子设备及存储介质

Similar Documents

Publication Publication Date Title
US11924737B2 (en) Method for performing relay forwarding on integrated access and backhaul links, information acquisition method, node, and storage medium
US11510131B2 (en) Configuration method, data transmission method, and apparatus
JP7378433B2 (ja) データパケットの送信方法、受信方法及び装置ならびにデータパケットの伝送システム
US11621916B2 (en) Information transmission method and device in IAB architecture
JP7440562B2 (ja) 情報伝送方法及び装置
JP7039712B2 (ja) ノードおよび通信方法
CN111586886B (zh) 一种无线回传链路的控制方法及装置
WO2019233465A1 (zh) 路径时延信息获取方法及相关设备
WO2022006907A1 (zh) 通信方法及装置
WO2022160108A1 (zh) 无线通信方法、通信装置及通信系统
US20240357469A1 (en) Method for performing relay forwarding on integrated access and backhaul links, information acquisition method, node, and storage medium
US20240357414A1 (en) Communication method and communication apparatus
EP4443977A1 (en) Communication method and communication apparatus
WO2020156316A1 (zh) Iab网络、mac实体和适配实体的执行方法以及通信设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20944221

Country of ref document: EP

Kind code of ref document: A1