A communication method and related equipment

Abstract

This application provides a communication method and related equipment. The method includes: a CU of a first IAB host determining the QoS attribute corresponding to an F1 application protocol (F1AP) message, wherein the F1 interface is the communication interface between the CU of the first IAB host and the DU of an IAB node. Then, the CU of the first IAB host sends the F1AP message and the corresponding QoS attribute to the DU of a second IAB host. This method ensures the transmission of the F1AP message even if the DU of the first IAB host cannot forward the F1AP message from the CU of the first IAB host.

Description

[0001] This application claims priority to PCT International Application filed on October 22, 2020, with application number PCT / CN2020 / 123008 and entitled "A Communication Method and Related Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a communication method and related equipment. Background Technology

[0003] Integrated access and backhaul (IAB) technology is an important part of fifth-generation mobile communication technology (5G).

[0004] On the one hand, since the Distributed Unit (DU) of an IAB node and the Central Unit (CU) of the IAB host are wirelessly connected, an IAB node can choose to switch between different IAB hosts. To reduce the impact on data transmission to child nodes during IAB node switching, the IAB node generally needs to obtain its configuration information under the target IAB host in advance to establish (or re-establish) the F1 connection between the IAB node and the target IAB host. For example, the CU of the target IAB host first transmits the configuration information of the IAB node under the target IAB host to the CU of the source IAB host, and the CU of the source IAB host then transmits the configuration information to the IAB node. Because this process involves the CU of the source IAB host, it results in a significant delay in the transmission of the configuration information.

[0005] On the other hand, in multi-connection or dual-connection scenarios, where an IAB node is simultaneously connected to the first IAB host and the second IAB host, if the DU of the first IAB host cannot forward the data sent by the CU of the first IAB host, it will cause the data transmission between the first IAB host and the IAB node to be interrupted, thereby affecting the user experience. Summary of the Invention

[0006] In view of this, this application provides a communication method and related equipment that can reduce data transmission latency and data transmission interruption.

[0007] Firstly, this application provides a communication method, which may include: a CU of a first IAB host determining the Quality of Service (QoS) attribute corresponding to an F1 application protocol (F1AP) message, or the Quality of Service (QoS) attribute corresponding to user plane data, wherein the F1 interface is the communication interface between the CU of the first IAB host and the Distributed Unit (DU) of the IAB node. Then, the CU of the first IAB host sends the F1AP message and the QoS attribute corresponding to the F1AP message to the DU of a second IAB host, or sends the user plane data and the QoS attribute corresponding to the user plane data to the DU of the second IAB host.

[0008] The exemplary beneficial effects of this method include: enabling the DU of the second IAB host to forward F1AP messages or user plane data from the CU of the first IAB host, thereby reducing data transmission interruptions caused by the DU's inability to forward F1AP messages or user plane data from the CU of the first IAB host. Furthermore, since the link between the CU of the first IAB host and the DU of the second IAB host is utilized, it does not need to pass through the CU of the second IAB host, thus reducing data transmission latency.

[0009] In one possible design, the CU of the first IAB host can determine the QoS attribute corresponding to the F1AP message based on the correspondence between F1AP message type and QoS attribute. Alternatively, the CU of the first IAB host can determine the QoS attribute corresponding to the user plane data based on the correspondence between user plane data and QoS attribute.

[0010] The correspondence is obtained from the CU of the second IAB host.

[0011] The exemplary beneficial effects of this design include: enabling the second IAB Donor-DU to correctly route F1AP messages or user plane data from the first IAB Donor-CU, and / or perform bearer mapping, according to the mapping relationship between QoS attributes and routing configurations configured for the second IAB Donor-DU by the second IAB Donor-CU, and / or the mapping relationship between QoS attributes and bearer configurations.

[0012] In one possible design, the method includes: the CU of the first IAB host sending an IFAP message type indication and a QoS attribute to the CU of the second IAB host, wherein the IFAP message type indication and the QoS attribute have a corresponding relationship. Alternatively, the CU of the first IAB host may send a user plane data indication and a QoS attribute to the CU of the second IAB host, wherein the user plane data indication and the QoS attribute have a corresponding relationship.

[0013] The exemplary beneficial effects of this design include: since the second IAB Donor-CU can resend the mapping relationship between QoS attributes and routing configuration, and / or the mapping relationship between QoS attributes and bearer configuration, to the second IAB Donor-DU based on the mapping relationship between the received F1AP message type indication and the QoS attribute or the mapping relationship between the user plane data indication and the QoS attribute, the second IAB Donor-DU can perform routing and / or bearer mapping on F1AP messages or user plane data from the first IAB Donor-CU based on the new mapping relationship between QoS attributes and routing configuration, and / or the mapping relationship between QoS attributes and bearer configuration.

[0014] In one possible design, the method includes: the CU of the first IAB host sending the F1AP message or user plane data to the IAB node through a first transport network layer association (TNLA) between the CU of the first IAB host and the DU of the IAB node, wherein the first TNLA corresponds to an Internet Protocol (IP) address assigned to the IAB node by the first IAB host. Alternatively, the CU of the first IAB host sending the F1AP message or user plane data to the IAB node through a second TNLA between the CU of the first IAB host and the DU of the IAB node, wherein the second TNLA corresponds to an IP address assigned to the IAB node by the second IAB host.

[0015] Exemplary benefits of this design include enabling F1AP messages or user plane data generated by the first IAB donor-CU to be sent to the IAB node via the second IAB donor-DU through the TNLA between the first IAB donor-CU and the IAB-DU.

[0016] In one possible design, the method includes: the CU of the first IAB host receiving an IP address assigned to the IAB node by the second IAB host from the CU of the second IAB host. The CU of the first IAB host sends the F1AP message or user plane data to the IAB node through a second transport network layer association (TNLA) between the CU of the first IAB host and the DU of the IAB node, including: the CU of the first IAB host using the IP address assigned to the IAB node by the second IAB host to send the F1AP message or user plane data to the IAB node through the second TNLA.

[0017] Exemplary benefits of this design include enabling the first IAB donor-CU to send and receive data via the second TNLA using the IP address assigned to the IAB node by the second IAB host.

[0018] Secondly, this application provides a communication method, which may include: a CU of a second integrated access backhaul (IAB) host sending an F1AP message type indication and a QoS attribute to a CU of a first IAB host, wherein the F1AP message type indication and the QoS attribute have a corresponding relationship, and this correspondence is used to determine the QoS attribute corresponding to the F1AP message of the first IAB host CU, wherein the F1 interface is a communication interface between the CU of the first IAB host and the distributed unit (DU) of the IAB node. Alternatively, a centralized unit CU of the second integrated access backhaul (IAB) host sending a user plane data indication and a QoS attribute to a CU of the first IAB host, wherein the user plane data indication and the QoS attribute have a corresponding relationship, and this correspondence is used to determine the QoS attribute corresponding to the user plane data of the first IAB host CU.

[0019] In one possible design, the method includes: the CU of the second IAB host sending the IP address assigned by the second IAB host to the CU of the first IAB host for the IAB node, the IP address being used for the transmission of the F1AP message or the user plane data.

[0020] Thirdly, this application provides a communication method, which may include: a centralized unit (CU) of a second IAB host receiving an F1AP message type indication and a QoS attribute from a CU of a first IAB host, wherein the F1AP message type indication and the QoS attribute have a corresponding relationship, wherein the F1 interface is a communication interface between the CU of the first IAB host and the DU of the IAB node. Alternatively, the CU of the second IAB host receives a user plane data indication and a QoS attribute from the CU of the first IAB host, wherein the user plane data indication and the QoS attribute have a corresponding relationship.

[0021] The CU of the second IAB host sends the routing configuration and bearer configuration corresponding to the QoS attribute to the DU of the second IAB host according to the correspondence.

[0022] In one possible design, the method includes: the CU of the second IAB host sending to the DU of the second IAB host the IP address assigned to the IAB node by the first IAB host and the Bakhaul Adaptation Protocol (BAP) address assigned to the IAB node by the second IAB host, wherein the IP address and the BAP address have a correspondence, and this correspondence is used to determine the BAP address of the target node corresponding to the F1AP message. The F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

[0023] Fourthly, this application provides a communication method, which may include: a distributed unit (DU) of a second IAB host receiving an F1AP message and a QoS attribute corresponding to the F1AP message from a CU of a first IAB host, or receiving user plane data and a QoS attribute corresponding to the user plane data from a CU of the first IAB host, wherein the F1 interface is a communication interface between the CU of the first IAB host and the DU of the IAB node.

[0024] The DU of the second IAB host can perform routing and bearer mapping for the F1AP message or user plane data based on the routing and bearer configuration corresponding to the QoS attribute.

[0025] In one possible design, the method includes the DU of the second IAB host receiving an IP address assigned to the IAB node by the first IAB host and a BAP address assigned to the IAB node by the second IAB host from the CU of the second IAB host, wherein the IP address and the BAP address have a corresponding relationship.

[0026] The DU of the second IAB host can determine the BAP address of the target node corresponding to the F1AP message or the user plane data based on the correspondence. The F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

[0027] Fifthly, this application provides a communication method, which may include: an IAB node using an IP address assigned to it by a second IAB host to establish a first TNLA between the CU of the first IAB host and the DU of the IAB node. Subsequently, the IAB node receives F1AP messages or user plane data from the CU of the first IAB host through the first TNLA, wherein the F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

[0028] In the first to third aspects and any of the possible designs described above, the F1AP message type includes user equipment related types and non-user equipment related types.

[0029] In the first to third aspects and any possible design described above, the user plane data indicates the identifier or IP address of the General Packet Radio Service User Plane Tunneling Protocol tunnel of the F1 interface.

[0030] In the first to fifth aspects and any of their possible designs, the QoS attribute is a differentiated services code point (DSCP) and / or a flow label.

[0031] In the first to fifth aspects and any of the possible designs described above, the F1AP message carries the configuration information of the DU of the IAB node under the first IAB host.

[0032] Sixthly, this application provides a communication method, which may include: an IAB node obtaining configuration information of its DU under a target IAB host, and activating the configuration information after the IAB node's mobile termination (MT) switches from the source IAB host to the target IAB host.

[0033] The exemplary beneficial effects of this method include: during the handover process of the IAB node in the MT part, the configuration information of the DU of the IAB node under the target IAB host is not effective, so that the resources of the MT of the IAB node and the resources of the DU of the IAB node can be coordinated and allocated.

[0034] In one possible design, the IAB node can receive the configuration information of its distributed unit (DU) under the target IAB host from the target IAB host.

[0035] The exemplary benefits of this design include: reducing the establishment process of the F1 interface and improving switching efficiency.

[0036] In one possible design, the method further includes: the IAB node receiving second information from the target IAB host, the second information being used to activate the configuration information. The IAB node activating the configuration information includes: the IAB node activating the configuration information based on the second information.

[0037] The exemplary benefits of this design include the ability for the target IAB host to flexibly control the activation of the configuration information.

[0038] In one possible design, the method further includes: the IAB node receiving at least one configuration information from the network management device. The IAB node obtaining the configuration information of its DU under the target IAB host includes: the IAB node determining the configuration information from the at least one configuration information.

[0039] In one possible design, the method includes: the IAB node sending a request message to the target IAB host for establishing an F1 interface, the request message including the configuration information of the IAB node's DU under the target IAB host; and the IAB node receiving a response message from the target IAB host regarding the request message.

[0040] In one possible design, the method includes: the IAB node using the IP address assigned to it by the target IAB host to establish a first transport network layer association (TNLA) between the CU of the target IAB host and the DU of the IAB node. The IAB node sends a request to the target IAB host to establish an F1 interface, including: the IAB node sending the request to the target IAB host via the first TNLA. The IAB node receives a response to the request from the target IAB host, including: the IAB node receiving the response from the target IAB host via the first TNLA.

[0041] In one possible design, before the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the method includes: the IAB node using the IP address allocated to it by the source IAB host to establish a second transport network layer association (TNLA) between the CU of the target IAB host and the DU of the IAB node. The IAB node sends a request to the target IAB host to establish an F1 interface, including: the IAB node sending the request to the target IAB host through the second TNLA. The IAB node receives a response to the request from the target IAB host, including: the IAB node receiving the response to the request from the target IAB host through the second TNLA.

[0042] In one possible design, before the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the method includes: the IAB node using the IP address assigned to it by the source IAB host to establish a second transport network layer association (TNLA) between the CU of the target IAB host and the DU of the IAB node. The IAB node then sends a request to the target IAB host to establish an F1 interface, including: the IAB node sending the request to the target IAB host via the second TNLA.

[0043] In one possible design, after the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the method includes: the IAB node using the IP address allocated to it by the target IAB host to establish a first TNLA between the CU of the target IAB host and the DU of the IAB node. The IAB node receives response information from the target IAB host regarding the request, including: the IAB node receiving the response information from the target IAB host via the first TNLA.

[0044] In one possible design, the method includes: if the IAB node receives a response message from the target IAB host before the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the response message is used to deactivate the configuration information of the DU of the IAB node under the target IAB host.

[0045] The exemplary benefits of this design include: ensuring that the configuration information of the DU of the IAB node under the target IAB host is not mistakenly activated by the response information of the request information before the IAB-MT completes the handover.

[0046] In one possible design, the method includes: if, after the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the IAB node receives response information from the target IAB host regarding the request information, then the response information is used to activate the configuration information of the DU of the IAB node under the target IAB host.

[0047] The exemplary benefits of this design include: the response information of the request information can be reused to activate the configuration information of the DU of the IAB node under the target IAB host, thereby saving air interface overhead.

[0048] In one possible design, the IAB node activates the configuration information by automatically activating it. Exemplary advantages of this design include: eliminating the need for dedicated activation information, thus saving air interface overhead.

[0049] In one possible design, the method further includes: the IAB node sending first information to the target IAB host, the first information indicating that the configuration information has been activated. An exemplary beneficial effect of this design is that it allows the IAB node to align the activation status of the configuration information with the target IAB host.

[0050] In a seventh aspect, this application provides a communication method, which may include: a target access backhaul integrated IAB host receiving first information from an IAB node, the first information indicating that the configuration information of the distributed unit (DU) of the IAB node under the target IAB host has been activated. The target IAB host determines that the configuration information has been activated based on the first information.

[0051] Eighthly, this application provides a communication method, which may include: a target access backhaul integrated IAB host receiving request information from an IAB node for establishing an F1 interface. Before the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the target IAB host sends the response information to the IAB node, the response information being used to deactivate the configuration information of the DU of the IAB node under the target IAB host. Alternatively, after the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the target IAB host sends the response information to the IAB node, the response information being used to activate the configuration information of the DU of the IAB node under the target IAB host.

[0052] In one possible design, the target IAB host receives a request from an IAB node for establishing an F1 interface. This includes: the target IAB host receiving the request through a second Transport Network Layer Association (TNLA) between its CU and the IAB node's DU, where the second TNLA corresponds to the Internet Protocol (IP) address assigned to the IAB node by the source IAB host. The target IAB host then sends a response to the request to the IAB node, including sending the response through the second TNLA.

[0053] In one possible design, the target IAB host receives a request from an IAB node for establishing an F1 interface. This includes: the target IAB host receiving the request through a first Transport Network Layer Association (TNLA) between its CU and the IAB node's DU, where the first TNLA corresponds to an Internet Protocol (IP) address assigned to the IAB node by the target IAB host. The target IAB host then sends a response to the request to the IAB node, including sending the response through the first TNLA.

[0054] In one possible design, before the MT of the IAB node switches from the source IAB host to the target IAB host, the target IAB host receives a request from the IAB node for establishing an F1 interface. This includes: the target IAB host receiving the request from the IAB node for establishing an F1 interface through a second transport network layer association (TNLA) between the target IAB host's CU and the IAB node's DU, wherein the second TNLA corresponds to the Internet Protocol IP address assigned to the IAB node by the source IAB host.

[0055] In one possible design, after the MT of the IAB node switches from the source IAB host to the target IAB host, the target IAB host sends a response message to the IAB node requesting the information. This response message includes the target IAB host sending the response message to the IAB node requesting the information via a first TNLA between the target IAB host's CU and the IAB node's DU. The first TNLA corresponds to the IP address allocated to the IAB node by the target IAB host.

[0056] Ninthly, this application provides a communication device including a module for performing the methods of the first to eighth aspects and any one of the methods in any design thereof.

[0057] In a tenth aspect, this application provides a communication device including a processor and a memory coupled together, the processor being used to implement the methods of the first to eighth aspects and any one of the designs thereof.

[0058] Eleventhly, this application provides a communication device, including at least one processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or the interface circuit is used to send signals from the processor to other communication devices outside the communication device. The processor implements any one of the methods of the first to eighth aspects and any of their designs through logic circuits or by executing program instructions.

[0059] In one possible design, the device may be a chip or integrated circuit in a node of any of the methods of the first to eighth aspects and any of the designs thereof.

[0060] Optionally, the communication device may also include at least one memory storing the relevant program instructions.

[0061] In a twelfth aspect, this application provides a communication device having the function or operation of implementing any one of the methods in the first to eighth aspects and any of the methods in any design described above. The function or operation can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above-described function or operation, such as a transceiver unit and a processing unit.

[0062] In a thirteenth aspect, this application provides a communication device including at least one processor and a memory, the at least one processor and the memory being coupled together, the memory storing a computer program, the at least one processor executing the computer program to cause the communication device to perform any one of the methods of the first to eighth aspects and any one of the designs thereof.

[0063] In a fourteenth aspect, this application provides a communication device including at least one processor and interface circuitry, wherein a computer program is executed in the at least one processor to cause the communication device to perform any one of the methods of the first to eighth aspects and any one of their designs.

[0064] In a fifteenth aspect, this application provides a computer-readable storage medium storing related program instructions, which, when executed, cause the communication device to implement the methods of the first to eighth aspects and any one of their designs.

[0065] In a sixteenth aspect, this application provides a computer program product comprising program instructions that, when executed, implement the methods of the first to eighth aspects and any one of their designs.

[0066] In a seventeenth aspect, this application also provides a chip for implementing the methods of the first to eighth aspects and any one of the designs thereof.

[0067] In an eighteenth aspect, this application provides a communication system comprising at least one communication device according to aspects nine through fifteen and any of their designs. Attached Figure Description

[0068] The accompanying drawings, which may be included in and form part of the specification, illustrate exemplary embodiments, features, and aspects of the present application together with the specification and serve to explain the principles of the present application. Obviously, the drawings described below are merely some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0069] Figure 1 This is a schematic diagram of a possible communication system according to this application;

[0070] Figure 2 This is a schematic diagram of an IAB host provided in an embodiment of this application;

[0071] Figure 3 This is a schematic diagram of the control plane protocol stack in the IAB network provided in the embodiments of this application;

[0072] Figure 4 This is a schematic diagram of the user plane protocol stack in the IAB network provided in the embodiments of this application;

[0073] Figure 5A This is a schematic diagram of an IAB node switching provided in an embodiment of this application;

[0074] Figure 5B This is a schematic diagram of another IAB node switching provided in an embodiment of this application;

[0075] Figure 6 This is a schematic diagram of a communication method provided in an embodiment of this application;

[0076] Figure 7 This is a schematic diagram of a communication method provided in an embodiment of this application;

[0077] Figure 8 This is a schematic block diagram of a communication device provided in an embodiment of this application;

[0078] Figure 9 This is a schematic block diagram of a communication device provided in an embodiment of this application;

[0079] Figure 10 This is a schematic block diagram of a communication device provided in an embodiment of this application;

[0080] Figure 11 This is a schematic block diagram of a communication device provided in an embodiment of this application;

[0081] Figure 12 This is a schematic block diagram of an apparatus provided in an embodiment of this application. Detailed Implementation

[0082] Compared to fourth-generation mobile communication (4G) or Long Term Evolution (LTE) systems, fifth-generation mobile communication (5G) or New Radio (NR) systems impose more stringent requirements on all aspects of network performance. For example, they demand a 1000-fold increase in capacity, wider coverage, and ultra-high reliability and ultra-low latency. On the one hand, given the abundance of high-frequency carrier resources, the use of high-frequency small cell networks is becoming increasingly popular in hotspot areas to meet the ultra-high capacity demands of 5G. However, high-frequency carriers have poor propagation characteristics, suffer severe attenuation due to obstruction, and have limited coverage, thus requiring a large-scale, dense deployment of small cells. Consequently, providing fiber optic backhaul for these densely deployed small cells is costly and difficult to implement, necessitating an economical and convenient backhaul solution. On the other hand, from the perspective of wide coverage requirements, providing network coverage in remote areas presents significant challenges and costs associated with fiber optic deployment, necessitating the design of flexible and convenient access and backhaul solutions. The wireless backhaul device offers a solution to the two problems mentioned above: both its access link (AL) and backhaul link (BL) employ wireless transmission schemes, reducing fiber optic deployment. The wireless backhaul device can be a relay node (RN), an integrated access backhaul (IAB) node, or any other device providing wireless backhaul functionality; this application is not limited to these. In an IAB network, the IAB node, acting as a wireless backhaul device, provides wireless access services to user equipment (UE). The UE's service data is transmitted from the IAB node to the IAB host, or host base station, via the wireless backhaul link. Using an IAB node allows for shared antennas for access and backhaul, reducing the number of antennas required by the base station.

[0083] The embodiments of this application will now be described with reference to the accompanying drawings, in which features or contents marked with dashed lines can be understood as optional operations or optional structures of the embodiments of this application.

[0084] Figure 1 This is a schematic diagram of a possible communication system provided in this application. The communication system includes a terminal, an IAB node, and an IAB host.

[0085] Figure 1The terminal in this application can be an access terminal device, user unit, user equipment, user station, mobile station, mobile station, remote station, remote terminal device, mobile device, user terminal device, wireless terminal device, user agent, or user device, etc. It can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device, other processing device connected to a wireless modem, in-vehicle device, wearable device (such as smartwatch, smart bracelet, etc.), smart furniture or home appliances, terminal equipment in 5G networks, terminal equipment in future evolved public land mobile networks (PLMNs), or vehicle equipment in vehicle-to-everything (V2X) networks, customer premises equipment (CPE), etc. This application does not limit the specific implementation form of the user equipment.

[0086] Figure 1 An IAB node can consist of a mobile termination (MT) and a distributed unit (DU). When an IAB node faces its parent node, it can be considered a terminal device, i.e., the role of an MT. When an IAB node faces its subordinate devices (which may be another IAB child node or a regular UE), it can be considered a network device, i.e., the role of a DU. It should be understood that... Figure 1 The nodes in this paper are exemplified by IAB nodes, which can be replaced by general relay nodes (RNs). In this application, the MT of an IAB node can be abbreviated as IAB-MT, the DU of an IAB node can be abbreviated as IAB-DU, the CU of the IAB host can be abbreviated as Donor-CU, and the DU of the IAB host can be abbreviated as Donor-DU.

[0087] Figure 1In 5G networks, the IAB donor can be the host base station, often referred to as DgNB (donor gNodeB). The IAB donor can be a single entity or exist as separate entities: a centralized unit (CU) (referred to as Donor-CU or gNB-CU in this application) and a distributed unit (DU) (referred to as Donor-DU or gNB-DU in this application). Figure 2 As shown, the IAB host can be a gNB located in the 5G radio access network (5G RAN). This IAB host can consist of a gNB-CU and a gNB-DU. The gNB-CU and gNB-DU are connected via an F1 interface, which can further include a control plane interface (F1-C) and a user plane interface (F1-U). The CU and the core network are connected via a next-generation (NG) interface. The gNB-CU or Donor-CU can also exist in a separate form, with the user plane (UP) (hereinafter referred to as CU-UP) and control plane (CP) (hereinafter referred to as CU-CP), i.e., the gNB-CU or Donor-CU consists of CU-CP and CU-UP. One gNB-CU can include one gNB-CU-CP and at least one gNB-CU-UP. Alternatively, one Donor-CU can include one Donor-CU-CP and at least one Donor-CU-UP. The Donor-CU and Donor-DU can be connected via a wired connection. In this application, the IAB host to which the IAB node is connected can be simply referred to as the IAB host of the IAB node. The IAB node can directly access the IAB host, or the IAB node can connect to the IAB host through other IAB nodes.

[0088] To ensure the reliability of service transmission, the IAB network supports multi-hop IAB nodes and multi-connection IAB nodes. Therefore, multiple transmission paths may exist between the terminal and the IAB host. On a single path, there is a defined hierarchical relationship between IAB nodes and between IAB nodes and the IAB hosts they connect to. Each IAB node considers the node providing its backhaul service as its parent node. Correspondingly, each IAB node can be considered a child node of its parent node.

[0089] For example, see Figure 1The parent node of IAB node 1 is the IAB host. IAB node 1 is also the parent node of IAB nodes 2 and 3. IAB nodes 2 and 3 are both the parent nodes of IAB node 4. The parent node of IAB node 5 is IAB node 2. Uplink data packets from the terminal can be transmitted to the IAB host via one or more IAB nodes, while downlink data packets will be sent from the IAB host to the terminal via one or more IAB nodes. There are two available paths for data packet transmission between terminal 1 and the IAB host: terminal 1 - IAB node 4 - IAB node 3 - IAB node 1 - IAB host, and terminal 1 - IAB node 4 - IAB node 2 - IAB node 1 - IAB host. There are three available paths for data packet transmission between Terminal 2 and the IAB host: Terminal 2-IAB Node 4-IAB Node 3-IAB Node 1-IAB host, Terminal 2-IAB Node 4-IAB Node 2-IAB Node 1-IAB host, and Terminal 2-IAB Node 5-IAB Node 2-IAB Node 1-IAB host.

[0090] To ensure proper data transmission between the terminal and the IAB host, the IAB host needs to configure a routing table for each IAB node, that is, configure the next-hop node for different paths. Simultaneously, the IAB host needs to determine the transmission path for data transmission. In other words, a transmission path, called the primary path, is determined before data transmission. Data is routed between the terminal and the IAB host through this primary path, while other paths can be considered backup paths. Backup paths are only used for re-routing when the primary path becomes unavailable, for example, when a link on the primary path experiences an RLF (Recurrent Link Failure). For example, ... Figure 1 As shown, the main data transmission path for Terminal 2 configured by the IAB host is: Terminal 2 - IAB Node 4 - IAB Node 2 - IAB Node 1 - IAB Host. When IAB Node 2 detects an RLF (Radio Link Failure) in the link with IAB Node 1 and the link cannot be restored, IAB Node 2 sends a radio link failure (RLF) indication message to IAB Node 4. Based on this indication message, IAB Node 4 can trigger data re-routing, temporarily transmitting the uplink data received from Terminal 2 through a backup path, namely: Terminal 2 - IAB Node 4 - IAB Node 3 - IAB Node 1 - IAB Host.

[0091] Intermediate IAB nodes on the uplink path from the IAB node to the IAB host can be called upstream nodes of the IAB node. For example... Figure 1In this context, IAB node 1 and IAB node 2 can both be considered upstream IAB nodes of IAB node 5. Intermediate IAB nodes on the downlink path from an IAB node to the terminal can be considered downstream nodes of the IAB node, for example... Figure 1 In IAB Node 2, IAB Node 3, IAB Node 4, and IAB Node 5, they can all be referred to as downstream nodes of IAB Node 1. Downstream nodes include child nodes, child nodes' child nodes (or grandchild nodes), etc. Downstream nodes can be other IAB nodes or endpoints. For example, Figure 1 Terminal 1 can be called a downstream node of IAB node 4, IAB node 4 and IAB node 5 can be called downstream nodes of IAB node 1, and terminal 1 and terminal 2 can be called downstream nodes of IAB node 1.

[0092] It is understandable that in an IAB network, a transmission path between a terminal and the IAB host can contain one or more IAB nodes. Each IAB node needs to maintain a radio backhaul link to its parent node and also maintain radio links to its child nodes. If a child node of an IAB node is a terminal, the link between the IAB node and its child node (i.e., the terminal) is a radio access link. If a child node of an IAB node is another IAB node, the link between the IAB node and its child node (i.e., the other IAB node) is a radio backhaul link. See, for an example... Figure 1 In the path “Terminal 1-IAB Node 4-IAB Node 3-IAB Node 1-IAB Host”, Terminal 1 accesses IAB Node 4 via a wireless access link, IAB Node 4 connects to IAB Node 3 via a wireless backhaul link, IAB Node 3 connects to IAB Node 1 via a wireless backhaul link, and IAB Node 1 connects to IAB Host via a wireless backhaul link.

[0093] The above IAB networking scenarios are merely examples. In IAB scenarios that combine multi-hop and multi-connection, there are many other possibilities for IAB networking, such as an IAB host and an IAB node under another IAB host forming a dual connection to provide terminal services, etc., which will not be listed here.

[0094] In this application's embodiments, the access IAB node refers to the IAB node accessed by the terminal, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services to the terminal or the IAB node. For example, see [link to example]. Figure 1In the path "Terminal 1 - IAB Node 4 - IAB Node 3 - IAB Node 1 - IAB Host", IAB Node 4 is the access IAB node, while IAB Node 3 and IAB Node 1 are intermediate IAB nodes. It's important to note that an IAB node is an access IAB node for the terminal connected to that IAB node. For terminals connecting to other IAB nodes, it is an intermediate IAB node. Therefore, whether an IAB node is a access IAB node or an intermediate IAB node is not fixed and needs to be determined based on the specific application scenario.

[0095] Figure 3 and Figure 4 These are schematic diagrams of the control plane protocol stack and the user plane protocol stack in the IAB network provided in this application embodiment, respectively. The following is a detailed explanation... Figure 3 and Figure 4 Please provide an explanation.

[0096] For control surfaces, such as Figure 3 As shown, a Uu interface is established between terminal 1 and IAB4-DU (referring to the DU of IAB node 4), with peer protocol layers including RLC, MAC, and PHY layers. An F1-C interface is established between IAB4-DU and IAB donor CU 1, with peer protocol layers including the F1 application protocol (F1AP). F1 Application F1 Application Protocol (F1AP) The protocol layers for peering IAB donor DU 1 and IAB donor CU 1 include the Internet Protocol (IP) layer, Layer 2, and Layer 1. Backhaul links (BLs) are established between IAB node 4 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB donor DU 1. The corresponding protocol layers for these links include the Backhaul Adaptation Protocol (BAP) layer, RLC layer, MAC layer, and PHY layer. Additionally, peering RRC and PDCP layers are established between terminal 1 and IAB donor CU 1, and a peering IP layer is established between IAB4-DU and IAB donor DU 1.

[0097] It can be seen that, compared with the control plane protocol stack of a single air interface, the DU accessing the IAB node in the IAB network implements the functions of a gNB-DU (i.e., establishing peer-to-peer RLC, MAC, and PHY layers with the terminal, and establishing peer-to-peer F1AP and SCTP layers with the CU). It can be understood that the DU accessing the IAB node in the IAB network implements the functions of a gNB-DU (single air interface); the IAB donor CU implements the functions of a gNB-CU (single air interface).

[0098] On the control plane, RRC messages are encapsulated in F1AP messages between the access IAB node and the IAB donor CU for transmission. Specifically, in the uplink direction, terminal 1 encapsulates the RRC message in a PDCP protocol data unit (PDU) and sends it to IAB4-DU after processing by the RLC layer, MAC layer, and PHY layer in sequence. IAB4-DU is processed by the PHY layer, MAC layer, and RLC layer in sequence to obtain a PDCP PDU. The PDCP PDU is encapsulated in an F1AP message and processed by the SCTP layer and IP layer in sequence to obtain an IP packet. IAB4-MT (referring to the MT of IAB node 4) sends the IP packet to IAB3-DU after processing by the BAP layer, RLC layer, MAC layer, and PHY layer in sequence. After IAB3-DU is processed sequentially through the PHY, MAC, RLC, and BAP layers to obtain the IP packet, IAB3-MT sends the IP packet to IAB1-DU using a similar operation to IAB4-MT. Similarly, IAB1-MT sends the IP packet to IAB donor DU 1. IAB donor DU 1 parses the IP packet and sends it to IAB donor CU 1. IAB donor CU 1 then processes the IP packet sequentially through the SCTP, F1AP, and PDCP layers to obtain the RRC message. The downlink direction is similar and will not be described further.

[0099] From the user's perspective, such as Figure 4As shown, a Uu interface is established between terminal 1 and IAB4-DU, with corresponding protocol layers including RLC, MAC, and PHY. An F1-U interface is established between IAB4-DU and IAB donor CU 1, with corresponding protocol layers including the General Packet Radio Service Tunneling Protocol for the User Plane (GTP-U) and User Datagram Protocol (UDP). IAB donor DU 1 and IAB donor CU 1 are connected via a wired connection, with corresponding protocol layers including IP, L2, and L1. Backhaul links (BL) are established between IAB node 4 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB donor DU 1, with corresponding protocol layers including BAP, RLC, MAC, and PHY. In addition, a peer-to-peer SDAP layer and PDCP layer are established between terminal 1 and IAB donor CU 1, and a peer-to-peer IP layer is established between IAB4-DU and IAB donor DU 1.

[0100] It can be seen that, compared with the user plane protocol stack of a single air interface, the user plane protocol stack of the IAB access node implements some of the functions of the gNB-DU of the single air interface (i.e., the functions of establishing peer-to-peer RLC, MAC, and PHY layers with the terminal, and the functions of establishing peer-to-peer GTP-U and UDP layers with the IAB donor CU 1). It can be understood that the DU of the IAB access node implements the functions of the gNB-DU of the single air interface; the IAB donor CU implements the functions of the gNB-CU of the single air interface.

[0101] On the user plane, PDCP packets are encapsulated in a GTP-U tunnel between the access IAB node and the IAB donor CU for transmission. The GTP-U tunnel is established on the F1-U interface.

[0102] Figure 3 and Figure 4 by Figure 1The protocol stack in the illustrated IAB scenario is described using an example. It should be noted that an IAB node may have one or more roles, and the IAB node can possess the protocol stack for that one or more roles. Alternatively, an IAB node can have a set of protocol stacks, which can use the protocol layers corresponding to different roles of the IAB node for processing. The following explanation uses an example of an IAB node possessing the protocol stack for one or more roles:

[0103] (1) Protocol stack of a common terminal

[0104] When an IAB node accesses an IAB network, it can act as a regular terminal. In this case, the MT (Mediator) of the IAB node has the protocol stack of a regular terminal, for example... Figure 3 and Figure 4 The protocol stack of terminal 1 consists of the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer. On the control plane, the RRC messages of the IAB node are transmitted encapsulated in the F1AP messages between the parent node of the IAB node and the IAB donor CU. On the user plane, the PDCP data packets of the IAB node are transmitted encapsulated in the GTP-U tunnel between the parent node of the IAB node and the IAB donor CU.

[0105] In addition, after the IAB node is connected to the IAB network, it can still act as a normal terminal, for example, transmitting its own uplink and / or downlink data packets (such as operation, administration and maintenance (OAM) data packets) to the IAB donor, performing measurements through the RRC layer, etc.

[0106] (2) Protocol stack for accessing the IAB node

[0107] After connecting to the IAB network, an IAB node can provide access services to terminals, thus acting as an access IAB node. In this case, the IAB node possesses the protocol stack for accessing the IAB network, for example... Figure 3 and Figure 4 The protocol stack of IABnode 4 in the middle.

[0108] In this scenario, the interface of the IAB node facing its parent node can have two protocol stacks: one is the protocol stack for ordinary terminals, and the other is the protocol stack that provides backhaul services for terminals (i.e., the protocol stack for accessing the IAB node). Optionally, the same protocol layers in these two protocol stacks can be shared; for example, both protocol stacks may correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.

[0109] (3) Protocol stack of intermediate IAB nodes

[0110] After connecting to the IAB network, an IAB node can act as an intermediate IAB node. In this case, the IAB node possesses the protocol stack of an intermediate IAB node, for example... Figure 3 and Figure 4 The protocol stack of IAB node 3 or IAB node 1.

[0111] In this scenario, the interface of the IAB node facing its parent node can have two protocol stacks: one is the protocol stack for ordinary terminals, and the other is the protocol stack that provides backhaul services for child IAB nodes (i.e., the protocol stack of intermediate IAB nodes). Optionally, the same protocol layers in these two protocol stacks can be shared; for example, both protocol stacks may correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.

[0112] Furthermore, an IAB node can simultaneously function as both an access IAB node and an intermediate IAB node. For example, an IAB node might act as an access IAB node for some terminals and as an intermediate IAB node for others. In this case, the IAB node can have three protocol stacks: one for the aforementioned ordinary terminals, one for the access IAB node, and one for the intermediate IAB node. Optionally, the same protocol layers in these three protocol stacks can be shared. For example, all three protocol stacks might correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.

[0113] It should be noted that, Figure 3 and Figure 4 The introduction used IAB networks as an example. Figure 3 and Figure 4 The content also applies to other types of relay networks besides IAB networks. The control plane protocol stack architecture of such relay networks can be found by referring to... Figure 3 The user plane protocol stack architecture of this relay network can be referenced. Figure 4 . Figure 3 and Figure 4 In this context, IAB nodes can be replaced with relays. For example, IAB node 4 can be replaced with relay node 4, IAB node 3 with relay node 3, IAB node 1 with relay node 1, and IAB donor 1 with host base station 1. The host base station has CU and DU protocol stacks. For further details, please refer to [reference needed]. Figure 3 and Figure 4 The description will not be repeated here.

[0114] Figure 5A and Figure 5BThis is a schematic diagram of the two types of IAB node switching provided in this application.

[0115] like Figure 5A As shown, IAB node 3 switches from the source parent node (IAB node 1) to the target parent node (IAB node 2) without changing the IAB host. This switch can be called an intra-donor CU switch or an intra-donor CU migrating switch.

[0116] exist Figure 5A In this context, there can be multiple IAB nodes between IAB node 1 and IAB donor 1, or IAB node 3 can be directly connected to IAB donor 1. Figure 5A In the IAB node, node 1 and / or node 2 may not exist.

[0117] like Figure 5B As shown, IAB node 3 switches from the source parent node (IAB node 1) to the target parent node (IAB node 2) and changes the connected IAB host, that is, switches from the source IAB host (IAB donor 1) to the target IAB host (IAB donor 2). This can be called a cross-IAB host switch or a cross-donor CU switch (inter-donor CU migrating).

[0118] exist Figure 5A and 5B In the IAB donor CU, one, two, or more donor DUs can be connected. Figure 5A Taking the example of an IAB donor CU connected to two donor DUs, Figure 5B This example uses one IAB donor CU connected to one donor DU, but this application does not limit the number of donor DUs connected to an IAB donor CU.

[0119] In addition, Figure 5A and 5B In this context, there can be multiple IAB nodes between IAB node 1 and IAB donor 1, or IAB node 3 can be directly connected to IAB donor 1. Figure 5A In the IAB node, IAB node 1 and / or IAB node 2 may not exist. Figure 5B In the IAB, node 1 may not exist. Similarly, in... Figure 5BIn this context, IAB node 2 and IAB donor 2 can also include multiple IAB nodes, or IAB node 3 can be directly connected to IAB donor 2. Figure 5B IAB node 2 may not exist.

[0120] Additionally, the child nodes of the IAB node (such as...) Figure 5A Alternatively, IAB node 4) in 5B can switch along with the IAB node, that is, also switch from the source IAB host to the target IAB host. The method provided in this application is applicable to the switching of the IAB node, and also applicable to the scenario where the downstream nodes of the IAB node switch along with the IAB node. The switching IAB node in this application can refer to the IAB node whose switching is triggered by the source IAB host.

[0121] Figure 6 The diagram illustrates a communication method according to an embodiment of this application. The communication method 600 includes:

[0122] S601: The CU (first IAB donor-CU) of the first IAB host determines the quality of service (QoS) attribute corresponding to the F1 interface application protocol F1AP message, and / or the QoS attribute corresponding to the user plane data.

[0123] In this embodiment, the F1AP message refers to the message on the F1 interface control plane between the first IAB donor-CU and the IAB-DU of the IAB node. The user plane data in this embodiment can refer to the data on the F1 interface user plane between the first IAB donor-CU and the IAB-DU of the IAB node.

[0124] The F1AP message can be categorized into several types, including a first type and a second type. The first type of F1AP message is primarily used for F1 interface context management and RRC message transmission. Here, "context" can refer to either the IAB node's context or the terminal device's context. "RRC message" can refer to messages between the IAB-MT's RRC layer and the IAB donor-CU's RRC layer, or between the terminal device's RRC layer and the IAB donor-CU's RRC layer. The second type of F1AP message is primarily used for F1 interface management, such as F1 interface establishment, reset, and configuration updates. For example, the first type can be called "UE-associated," and the second type can be called "Non-UE-associated." Different types of F1AP messages can have different priorities, which can be reflected through QoS attributes. These QoS attribute values ​​can include differentiated services code points (DSCP) and / or flow labels. Different types of F1AP messages correspond to different DSCP or flow label values.

[0125] In order to distinguish the priority of F1AP messages sent to the IAB-DU, after the first IAB Donor-CU generates an F1AP message, it needs to determine the QoS attribute corresponding to the F1AP message, that is, the QoS attribute corresponding to the F1AP message type to which the F1AP message belongs.

[0126] The user plane data can include data from terminal devices or data from IAB nodes, such as data from network management devices used to configure IAB nodes. Different user plane data have different QoS requirements and can have different priorities. For example, this priority can be reflected by QoS attributes, such as assigning different DSCP or flow label values ​​to user plane data with different QoS requirements. Similarly, to distinguish the priority of user plane data sent to the IAB-DU, the first IAB Donor-CU needs to determine the QoS attributes corresponding to the user plane data after generating it. The user plane data can be identified by user plane data indicators. These indicators can be identifiers of GTP-U tunnels, such as GTP tunnel endpoint identifiers (TEID) and / or IP addresses.

[0127] S602: The first IAB Donor-CU sends the F1AP message and the QoS attribute corresponding to the F1AP message to the DU (second IAB Donor-DU) of the second IAB host, and / or the first IAB Donor-CU sends the user plane data and the QoS attribute corresponding to the user plane data to the second IAB Donor-DU.

[0128] For example, after determining the QoS attribute corresponding to the F1AP message, the first IAB Donor-CU can encapsulate the F1AP message in an Internet Protocol (IP) packet, carry the QoS attribute corresponding to the F1AP message in the IP header of the IP packet, and then send the IP packet to the second IAB Donor-DU via IP routing.

[0129] Similarly, for example, after determining the QoS attribute corresponding to the user plane data, the first IAB Donor-CU can encapsulate the user plane data in an IP packet, carry the QoS attribute corresponding to the user plane data in the IP header of the IP packet, and send the IP packet to the second IAB Donor-DU through IP routing.

[0130] For example, the source IP address of the IP packet can be the IP address of the first IAB Donor-CU, and the destination IP address of the IP packet can be the IP address of the IAB node. The IP address of the IAB node can be assigned to the IAB node by the first IAB Donor-CU, or it can be assigned to the IAB node by the second IAB Donor-CU.

[0131] After receiving the IP packet, the second IAB Donor-DU routes and / or maps the F1AP message within the IP packet according to the QoS attributes in the IP header, so as to further send it to the IAB node. For example, the second IAB Donor-DU determines the routing configuration corresponding to the IP packet based on the internally stored mapping between QoS attributes and routing configurations, as well as the QoS attributes in the IP packet, and then routes the F1AP message within the IP packet according to the routing configuration. For example, the second IAB Donor-DU determines the bearer configuration corresponding to the IP packet based on the internally stored mapping between QoS attributes and bearer configurations, as well as the QoS attributes in the IP packet, and then maps the F1AP message within the IP packet according to the bearer configuration. The routing configuration may include a BAP routing identity (BAP routing ID) and / or the BAP address of the next-hop node. The bearer configuration may include a backhaul RLC channel identity (BH RLC CH ID).

[0132] The mapping between QoS attributes and routing configurations stored internally in the second IAB Donor-DU, and / or the mapping between QoS attributes and bearer configurations stored internally, can be configured by the CU (second IAB Donor-CU) of the second IAB host to the second IAB Donor-DU.

[0133] In order for the second IAB Donor-DU to correctly route and / or map F1AP messages or user plane data from the first IAB Donor-CU, the communication method 600 may further include S603:

[0134] S603: The first IAB Donor-CU obtains from the second IAB Donor-CU the correspondence between at least one F1AP message type and at least one QoS attribute, and / or the correspondence between at least one user plane data and at least one QoS attribute.

[0135] The second IAB Donor-CU can send at least one F1AP message type indication to the first IAB Donor-CU a correspondence between at least one QoS attribute and at least one QoS attribute, and / or a correspondence between at least one user plane data indication and at least one QoS attribute, so that the first IAB Donor-CU obtains the correspondence between at least one F1AP message type and at least one QoS attribute, and / or the correspondence between at least one user plane data and at least one QoS attribute.

[0136] For example, the correspondence between at least one F1AP message type indication and at least one QoS attribute can be shown in Table 1:

[0137] Table 1

[0138] F1AP message type indication QoS attributes Type 1 Attribute 1 Type II Attribute 2 …… …… Type X Attribute X

[0139] It should be noted that Table 1 only shows one possible correspondence between F1AP message type indication and QoS attributes. This correspondence can be one-to-one, many-to-one, one-to-many, or many-to-many; this embodiment does not limit this. The first type of F1AP message and the second type of F1AP message in Table 1 can be indicated by different F1AP message type indications. This F1AP message type indication can occupy N bits of indication information. For example, different F1AP message types can be indicated by the value of an indication information occupying 1 bit; if the F1AP message type indication value is 0, it indicates the first type of F1AP; if the F1AP message type indication value is 1, it indicates the second type of F1AP. The different QoS attributes in Table 1 can be represented by different DSCP values ​​and / or flow label values.

[0140] Similarly, the correspondence between at least one user plane data indicator and at least one QoS attribute can be understood by referring to the correspondence between at least one F1AP message type indicator and at least one QoS attribute or by referring to Table 1.

[0141] S603 enables the first IAB Donor-CU to determine the QoS attribute corresponding to the F1AP message based on the correspondence between the F1AP message type indication and the QoS attribute sent by the second IAB Donor-CU and the type of the F1AP message generated by the first IAB Donor-CU.

[0142] Similarly, the first IAB Donor-CU can determine the QoS attribute corresponding to the user plane data based on the correspondence between the user plane data indication sent by the second IAB Donor-CU and the user plane data indication corresponding to the user plane data generated by the first IAB Donor-CU. In this way, the second IAB Donor-DU can correctly route and / or map the F1AP messages or user plane data from the first IAB Donor-CU according to the correspondence between the QoS attributes and routing configuration configured by the second IAB Donor-CU, and / or the correspondence between the QoS attributes and bearer configuration.

[0143] Optionally, in order to enable the second IAB Donor-DU to correctly route and / or bearer map FIAP messages or user plane data from the first IAB Donor-CU, the communication method 600 may further include S604:

[0144] S604: The first IAB Donor-CU sends to the second IAB Donor-CU a correspondence between at least one F1AP message type and at least one QoS attribute, and / or a correspondence between at least one user plane data and at least one QoS attribute.

[0145] Upon receiving the mapping between the F1AP message type indication and QoS attributes sent by the first IAB Donor-CU, the second IAB Donor-CU can send the mapping between QoS attributes and routing configurations to the second IAB Donor-DU. This allows the second IAB Donor-DU to route F1AP messages from the first IAB Donor-CU according to the new mapping between QoS attributes and routing configurations.

[0146] Upon receiving the mapping between the F1AP message type indication and QoS attributes sent by the first IAB Donor-CU, the second IAB Donor-CU can send the mapping between QoS attributes and bearer configurations to the second IAB Donor-DU. This allows the second IAB Donor-DU to perform bearer mapping on F1AP messages from the first IAB Donor-CU based on the new mapping between QoS attributes and bearer configurations.

[0147] Upon receiving the mapping between user plane data indication and QoS attributes sent by the first IAB Donor-CU, the second IAB Donor-CU can send the mapping between QoS attributes and routing configurations to the second IAB Donor-DU. This allows the second IAB Donor-DU to route user plane data from the first IAB Donor-CU according to the new mapping between QoS attributes and routing configurations.

[0148] The second IAB Donor-CU, upon receiving the mapping between user plane data indication and QoS attributes from the first IAB Donor-CU, can send the mapping between QoS attributes and bearer configurations to the second IAB Donor-DU. This allows the second IAB Donor-DU to perform bearer mapping on the user plane data from the first IAB Donor-CU based on the new mapping between QoS attributes and bearer configurations.

[0149] In this embodiment of the application, S603 and S604 are executed selectively, that is, in order for the second IAB Donor-DU to correctly route and / or map the F1AP message or user plane data from the first IAB Donor-CU, it is not necessary to execute both operations.

[0150] Optionally, in order to enable the F1AP message or user plane data generated by the first IAB donor-CU to be sent to the IAB node via the second IAB donor-DU through the F1 interface between the first IAB donor-CU and the IAB-DU, the communication method 600 may further include S605 or S606:

[0151] S605: The IAB node uses the IP address assigned to the IAB node (or the IAB node's IAB-DU) by the first IAB donor (donor-CU or donor-DU) to establish a first transport network layer association (TNLA) between the first IAB donor-CU and the IAB node's IAB-DU.

[0152] The IAB node establishes a first TNLA between the first IAB donor-CU and the IAB-DU of the IAB node. The first TNLA corresponds to the IP address assigned by the first IAB donor (IAB donor-CU or IAB donor-DU) to the IAB node (or the IAB node's IAB-DU).

[0153] The transport network layer may include Figure 3 and Figure 4 The transport network layer may include IP, UDP, and SCTP layers, and may also include other protocol layers. This application does not limit which specific protocol layers are included in the transport network layer. The transport network layer association is just a name for the association, and the association may also have other names. This application does not limit this.

[0154] For example, the transport protocol stack at this time can Figure 3 or Figure 4 The term "IAB donor CU 1" can be understood by replacing it with "IABdonor CU 2". Specifically, "IAB donor DU 1" and "IAB donor CU 1" constitute one IAB Donor, and "IABdonor DU 2" and "IAB donor CU 2" constitute another IAB Donor.

[0155] For example, when the first IAB donor-CU sends an IP packet carrying the F1AP message or user plane data to the IAB node (or the IAB node's IAB-DU) through the first TNLA, the source IP address of the IP packet can be set to the IP address of the first IAB donor-CU, and the destination IP address can be set to the IP address allocated by the first IAB donor (donor-CU or donor-DU) to the IAB node (or the IAB node's IAB-DU).

[0156] Optionally, in S605, to enable the second IAB donor-DU to correctly determine the target node (i.e., the IAB node) of the F1AP message or user plane data, the second IAB donor-CU needs to determine the correspondence between the IP address of the IAB node (or the IAB node's IAB-DU) and the BAP address of the IAB node, and send the determined correspondence to the second IAB donor-DU. The IP address of the IAB node (or the IAB node's IAB-DU) is assigned by the first IAB donor (IAB donor-CU or IAB donor-DU), and the BAP address of the IAB node is assigned by the second IAB donor-CU. Furthermore, the IP address assigned by the first IAB donor (IAB donor-CU or IAB donor-DU) to the IAB node (or the IAB node's IAB-DU) can be sent by the first IAB donor to the second IAB donor.

[0157] For example, when the second IAB donor-DU receives an IP packet carrying the F1AP message or user plane data, since the destination IP address of the IP packet is the IP address allocated by the first IAB donor (IAB donor-CU or IAB donor-DU) to the IAB node (or the IAB node's IAB-DU), the second IAB donor-DU can determine the BAP address allocated by the second IAB donor-CU to the IAB node based on the correspondence between the IP address allocated by the first IAB donor (IAB donor-CU or IAB donor-DU) to the IAB node (or the IAB node's IAB-DU) and the BAP address allocated by the second IAB donor-CU to the IAB node, and finally send the F1AP message or user plane data to the IAB node corresponding to the BAP address.

[0158] S606: The IAB node uses the IP address assigned to the IAB node (or the IAB node's IAB-DU) by the second IAB donor (donor-CU or donor-DU) to establish a second TNLA between the first IAB donor-CU and the IAB node's IAB-DU.

[0159] The IAB node establishes a second TNLA between the first IAB donor-CU and the IAB node's IAB-DU. The second TNLA and the second IAB donor (donor-CU or donor-DU) correspond to the IP address assigned to the IAB node (or the IAB node's IAB-DU).

[0160] For example, the second IAB donor-CU can send the IP address assigned by the second IAB donor (donor-CU or donor-DU) to the IAB node (or the IAB node's IAB-DU) to the first IAB donor-CU. This allows the first IAB donor-CU to use the IP address to send and receive data via the second TNLA. For instance, the sender of the IP packet can be identified based on the IP address and the source IP address of the IP packet received via the second TNLA. As another example, when the first IAB donor-CU sends an IP packet carrying the F1AP message or user plane data to the IAB node (or the IAB node's IAB-DU) via the second TNLA, the source IP address of the IP packet can be set to the IP address of the first IAB donor-CU, and the destination IP address can be set to the IP address assigned by the second IAB donor (donor-CU or donor-DU) to the IAB node (or the IAB node's IAB-DU).

[0161] The method described in this application can be applied to scenarios where an IAB node undergoes inter-donor CU migrating; that is, the IAB node in this application embodiment can be a switching IAB node (such as...). Figure 5B (IAB node3 in the IAB) or switch the downstream node of the IAB node (e.g., Figure 5B In the IAB node4, the first IAB donor can be the target IAB host (e.g., node4). Figure 5B The second IAB donor can be the source IAB host (e.g., IAB donor 2). Figure 5B (IABdonor1 in the example). There can be one or more parent nodes between an IAB node and the source IAB donor, or the IAB node may be directly connected to the source IAB donor. Similarly, there can be one or more parent nodes between an IAB node and the target IAB donor, or the IAB node may be directly connected to the target IAB donor. The FIAP message in this embodiment can carry the configuration information of the IAB node's DU under the target IAB host. Thus, through the method of this embodiment, the IAB node can quickly obtain the configuration information under the target IAB host, thereby quickly switching from the source IAB host to the target IAB host.

[0162] The method described in this application embodiment can also be applied to dual connectivity (DC) or multi-connectivity (MC) scenarios, where the IAB node is simultaneously connected to a first IAB host and a second IAB host. For example, the IAB node's IAB-DU has F1 interfaces with both the first and second IAB donor-CUs. When data between the IAB node and the first IAB host cannot be sent to the IAB node via the path between them, it can be sent to the IAB node via the second IAB host. For example, the path from the first IAB donor-CU to the IAB node via the first IAB donor-DU can be called the primary path. The path from the first IAB donor-CU to the IAB node via the second IAB donor-DU can be called the backup path. The primary path and backup path can be referenced... Figure 1 The relevant descriptions in the corresponding embodiments should be understood. Thus, the method of this embodiment can increase the reliability of data transmission from the IAB node and reduce the occurrence of data interruptions.

[0163] Additionally, for uplink transmission of F1AP messages or user plane data of the IAB node, the following method can be used:

[0164] The second donor-DU receives the IP packet from the IAB node. This IP packet includes an F1AP message or user plane data, and its destination address is the IP address of the first donor-CU. The second donor-DU can then send the F1AP message or user plane data to the first donor-CU via IP routing. To enable the IAB node's F1AP message or user plane data to be sent to the IAB node via the F1 interface between the first IAB donor-CU and the IAB-DU, and then via the second IAB donor-DU, this method can include S605 or S606.

[0165] Furthermore, S605 or S606 in the embodiments of this application can be used as a separate embodiment to establish a communication connection between the first IAB donor-CU and the IAB-DU of the IAB node via the second IAB donor-DU, so as to facilitate the subsequent transmission of FIAP messages or user plane data. S605 or S606 can also be combined with S601 to S602 to form an embodiment, so that FIAP messages or user plane data can be transmitted between the first IAB donor-CU and the IAB-DU of the IAB node via the second IAB donor-DU.

[0166] Figure 7 The diagram illustrates a communication method according to an embodiment of this application. The communication method 700 includes:

[0167] S701: The IAB node obtains the configuration information of its IAB-DU under the target IAB host.

[0168] The IAB node can be Figure 5B The configuration information of this IAB node under the target IABdonor refers to the configuration information that the IAB-DU of this IAB node needs to use when it connects to the target IAB host.

[0169] The configuration information of the IAB node under the target IAB donor may include at least one of the following: IAB-DU identifier (ID), IAB-DU name, cell information of the cell served by the IAB node under the target IAB donor, synchronization signal and PBCH (synchronization signal and physical broadcast channel block, SSB) configuration transmitted by the DU of the IAB node, system information transmitted by the DU of the IAB node, public land mobile network identifier list (PLMN Id List), Single Network Slice Selection Assistance Information list (sNSSAIList), PCI, tracking area code (TAC), gNB ID length, uplink and downlink frequency points, and IP address of the IAB node.

[0170] The SSB configuration may include SSB frequency, SSB period, SSB carrier spacing, SSB offset, or SSB duration. For example, the cell served by the IAB node may be a cell served by the IAB node's DU or a cell deployed by the IAB node's DU. The cell information of the cell served by the IAB node under the target IAB donor may include at least one of the following: physical cell identifier (…). Physical Cell Identifier (PCI) Physical Cell Identifier (PCI) The cell identifier (PCI) consists of the base station identifier and the cell local identifier. The cell global identifier (CGI) consists of the public land mobile network identifier (PLMNId), the base station identifier, and the cell local identifier (cellLocalId).

[0171] An IAB node can obtain the configuration information of its IAB-DU under the target IAB host through either of the following two methods:

[0172] Implementation Method 1: The IAB node can obtain the configuration information of the IAB-DU under the target IAB host from the target IAB donor. For example, the target IAB donor can use method 600 to send the configuration information of the IAB-DU under the target IAB host to the IAB node. For example, in Implementation Method 1, the configuration information of the IAB node under the target IAB donor may also include indication information of whether the cell is activated.

[0173] In implementation method 1, since the configuration information of the IAB-DU under the target IAB donor is configured by the target IABdonor, that is, both the target IAB donor and the IAB node already know the configuration information of the IAB-DU under the target IAB donor. Therefore, the target IAB donor and the IAB node do not need to trigger the F1 interface establishment process between the target IABdonor-CU and the IAB-DU to exchange the configuration information of the IAB-DU under the target IAB donor. This reduces the F1 interface establishment process and improves the switching efficiency.

[0174] Implementation Method 2: The IAB node can receive at least one configuration information from the network management device. The IAB node determines the configuration information of the IAB-DU under the target IAB host from this at least one configuration information. For example, the network management device can determine the candidate IAB host for the IAB node based on the IAB node's location information and / or information about the IAB node's neighboring cells. The candidate IAB host can be at least one IAB host surrounding the IAB node. For each candidate IAB host, the network management device generates the configuration information of the IAB node under that candidate IAB host. As shown in Table 2:

[0175] Table 2:

[0176] Candidate IAB host 1 Configuration Information 1 Candidate IAB host 2 Configuration Information 2 …… …… Candidate IAB host X Configuration Information X

[0177] The network management device can send the configuration information corresponding to X (X is a positive integer greater than or equal to 1) candidate IAB hosts to the IAB node. The IAB node can then determine its configuration information under the candidate IAB host from the X configuration information based on the target IAB host.

[0178] In implementation method 2, since the target IAB donor-CU does not know the configuration information of the IAB-DU under the target IAB host, it is necessary to trigger the F1 interface establishment process between the target IAB donor-CU and the IAB-DU to exchange the configuration information of the IAB-DU under the target IAB donor.

[0179] For example, the network management device can be an operation, administration, and maintenance (OAM) element. The network management device may include an element management system (EMS) or a network management system (NMS). The network management device can be a functional network element located in the 5G core network (5GCore, 5GC), or it can be a functional network element deployed in the backbone network behind the 5G core network. This application does not limit the specific deployment location of the network management device.

[0180] S702: After the IAB-MT of the IAB node switches from the source IAB donor to the target IAB donor, the IAB node activates the configuration information of the IAB-DU under the target IAB donor.

[0181] The IAB node activating the configuration information of the IAB-DU under the target IAB donor can refer to the IAB node activating at least one cell in the configuration information of the IAB-DU under the target IAB donor. Activating a cell can mean making the relevant configuration of that cell effective, such as the cell identifier or CGI.

[0182] This method ensures that during the handover process of the IAB node's MT (Mean Transmission Unit), the configuration information of the IAB node's DU (Dedicated User Unit) under the target IAB host is not applied. This reduces the likelihood of resource allocation inconsistencies between the IAB node's MT and DU when the MT is still connected to the source IAB donor. For example, since the resources of IAB-MT and IAB-DU are uniformly configured by the source IAB host, during the handover process of IAB-MT, the resources of IAB-MT are configured by the source IAB host. If the configuration information of the IAB node's DU under the target IAB host were applied at this time, it would result in the resources of IAB-MT being configured by the source IAB host while the resources of IAB-DU are configured by the target IAB host, potentially leading to resource allocation inconsistencies between IAB-MT and IAB-DU.

[0183] After the IAB-MT of this IAB node switches from the source IAB donor to the target IAB donor, the configuration information can be activated using either of the following two methods:

[0184] Method 1: The IAB node automatically activates the configuration information of the IAB-DU under the target IAB donor. For example, the IAB node can automatically activate the configuration information of the IAB-DU under the target IAB donor after the IAB-MT successfully connects to the target IAB donor. For example, in Method 1, the IAB node can automatically activate the configuration information of the IAB-DU under the target IAB donor (activate the cell of the IAB-DU under the target IAB donor) based on the indication information of whether the cell is activated in the configuration information of the IAB node under the target IAB donor, after the IAB-MT successfully connects to the target IAB donor.

[0185] In method 1, in order to inform the target IAB donor that the configuration information of the IAB-DU under the target IAB donor has been activated, optionally, method 1 includes S703:

[0186] S703: The IAB node sends a first message to the target IAB donor, the first message indicating that the configuration information of the IAB-DU under the target IAB donor has been activated.

[0187] Method 2 can be further divided into the following two cases:

[0188] (1) When the IAB node obtains the configuration information of the IAB-DU under the target IAB host from the target IAB donor, method 2 includes S704:

[0189] S704: The IAB node receives second information from the target IAB donor, which is used to activate the configuration information.

[0190] After receiving the second information, the IAB node then activates the configuration information of the IAB-DU under the target IAB donor. Activating the configuration information of the IAB-DU under the target IAB donor can be considered as activating the cell-specific configuration information of the IAB-DU under the target IAB donor.

[0191] For example, if the configuration information of the IAB node under the target IAB donor does not include indication information on whether a cell is activated, the second information may include indication information indicating the activation of at least one cell in the configuration information of the IAB-DU under the target IAB donor.

[0192] For example, if the configuration information of the IAB node under the target IAB donor includes an indication of whether the cell is activated, the IAB node can activate the configuration information of the IAB-DU under the target IAB donor after receiving the second information, based on the indication of whether the cell is activated.

[0193] This second piece of information can be carried in a configuration update message sent by the target IAB donor (or the target IAB donor-CU) to the IAB node, such as the GNB-CU CONFIGURATION UPDATE message. The GNB-CU CONFIGURATION UPDATE message can be understood by referring to section 9.2.1.10 of 3GPP TS 38.473V16.1.0. Alternatively, this second piece of information can be carried in a configuration update confirmation message sent by the target IAB donor (or the target IAB donor-CU) to the IAB node, such as the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message. The GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message can be understood by referring to section 9.2.1.8 of 3GPP TS 38.473V16.1.0.

[0194] (2) When the IAB node determines the configuration information of the IAB-DU under the target IAB host from at least one configuration information from the network management device, method 2 includes S705 and S706:

[0195] S705: The IAB node sends a request to the target IAB donor to establish (or re-establish) the F1 interface. The request includes the configuration information of the IAB-DU under the target IAB donor.

[0196] The F1 interface refers to the communication interface between the IAB node's IAB-DU and the target IAB donor's IAB donor-CU.

[0197] For example, the configuration information of the IAB node under the candidate IAB donor may also include indication information as to whether the cell needs to be activated.

[0198] For example, the IAB node can send the request information for establishing (or re-establishing) the F1 interface to the target IAB donor via a first TNLA or a second TNLA. The first TNLA is established between the target IAB donor-CU and the IAB-DU using the IP address allocated to the IAB node (or IAB-DU) by the target IAB donor (donor-CU or donor-DU). The second TNLA is established between the target IAB donor-CU and the IAB-DU using the IP address allocated to the IAB node (or IAB-DU) by the source IAB donor (donor-CU or donor-DU).

[0199] S706: The target IAB donor sends the response information to the IAB node regarding the request.

[0200] If, before the IAB-MT of the IAB node switches from the source IAB donor to the target IAB donor, the target IAB donor sends a response to the request information to the IAB node, then this response information is not used to activate the configuration information of the IAB-DU under the target IAB donor. For example, the response information may include an indication not to activate the configuration information of the IAB-DU under the target IAB donor, or the response information may include a deactivation indication to deactivate the configuration information of the IAB-DU under the target IAB donor. Specifically, the deactivation indication may be an indication to deactivate all cells of the IAB-DU under the target IAB donor, or the response information may not include an activation indication to activate all cells of the IAB-DU under the target IAB donor.

[0201] This design ensures that the configuration information of the IAB-DU under the target IAB host will not be mistakenly activated by the response information of the request information before the IAB-MT completes the switchover. Furthermore, after the IAB-MT of the IAB node switches from the source IAB donor to the target IAB donor, the configuration information of the IAB-DU under the target IAB donor can be activated via S704.

[0202] If, after the IAB-MT of the IAB node switches from the source IAB donor to the target IAB donor, the target IAB donor sends a response to the request information to the IAB node, this response information is used to activate the configuration information of the IAB-DU under the target IAB donor. For example, the response information includes activation indication information for activating the configuration information of the IAB-DU under the target IAB donor, or the response information includes activation indication information for activating at least one cell in the configuration information of the IAB-DU under the target IAB donor. Exemplarily, the activation indication information may be generated by the target IAB donor based on the indication information indicating whether activation is required.

[0203] For example, the response information may also include at least one of the following: information for identifying the target IAB donor, the RRC version supported by the target IAB donor-CU, the transport layer address information of the target IAB donor-CU, and the synchronization signal block transmission configuration (STC) of the IAB node's IAB-DU.

[0204] This design allows the response information of the request to be reused to activate the configuration information of the DU of the IAB node under the target IAB host, thereby saving air interface overhead.

[0205] For example, the IAB node can send the request information for establishing (or re-establishing) the F1 interface to the target IAB donor through the first TNLA, and receive the response information of the request information sent by the target IAB donor through the first TNLA.

[0206] Optionally, the IAB node can send the request information for establishing (or re-establishing) the F1 interface to the target IAB donor through the second TNLA, and receive the response information of the request information sent by the target IAB donor through the second TNLA.

[0207] Optionally, the IAB node can send the request information for establishing (or re-establishing) the F1 interface to the target IAB donor through the second TNLA, and receive the response information of the request information sent by the target IAB donor through the first TNLA.

[0208] The first TNLA is established between the target IAB donor-CU and the IAB-DU using the IP address allocated to the IAB node (or IAB-DU) by the target IAB donor (donor-CU or donor-DU). The second TNLA is established between the target IAB donor-CU and the IAB-DU using the IP address allocated to the IAB node (or IAB-DU) by the source IAB donor (donor-CU or donor-DU).

[0209] For example, the target IAB donor and the IAB node may use method 600 to interact with at least one of the above-mentioned request information for establishing (or re-establishing) the F1 interface, the response information of the request information, or the second information.

[0210] Based on the aforementioned similar technical concepts, this application provides a communication device. This device can be any possible design scheme of IAB donor-CU, IAB donor-DU, IABdonor, or IAB node in method 600 or 700 of the foregoing embodiments. The communication device includes at least one corresponding unit in the communication method provided by method 600 or 700 for executing the method steps, operations, or behaviors performed by the IABdonor-CU, IAB donor-DU, IAB donor, or IAB node. The configuration of this at least one unit can have a one-to-one correspondence with the method steps, operations, or behaviors performed by the IAB donor-CU, IAB donor-DU, IAB donor, or IAB node. These units can be implemented by computer programs, by hardware circuits, or by a combination of computer programs and hardware circuits.

[0211] Figure 8 This is a schematic block diagram of a communication device 800 provided in an embodiment of this application. The communication device 800 can be applied to the IAB donor-CU. The structure and function of the communication device 800 will be described in detail below, divided into different designs. Although the module names are the same across different designs, their structures and functions may differ.

[0212] Design 1: The communication device 800 may include a processing module 801 and a sending module 802. The processing module 801 is used to determine the QoS attributes corresponding to an F1 application protocol (F1AP) message, or the QoS attributes corresponding to user plane data, wherein the F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node. The sending module 802 is used to send the F1AP message and its corresponding QoS attributes to the DU of the second IAB host, or to send the user plane data and its corresponding QoS attributes to the DU of the second IAB host.

[0213] Specifically, the processing module 801 is used to determine the QoS attribute corresponding to the F1AP message based on the correspondence between F1AP message type and QoS attribute. This correspondence is obtained by the CU of the first IAB host from the CU of the second IAB host. The processing module 801 is also used to determine the QoS attribute corresponding to the user plane data based on the correspondence between user plane data and QoS attribute. This correspondence is also obtained by the CU of the first IAB host from the CU of the second IAB host.

[0214] Furthermore, the sending module 802 is also used to send an IFAP message type indication and a QoS attribute to the CU of the second IAB host, wherein the IFAP message type indication and the QoS attribute have a corresponding relationship; or, the sending module 802 is also used to send a user plane data indication and a QoS attribute to the CU of the second IAB host, wherein the user plane data indication and the QoS attribute have a corresponding relationship.

[0215] Specifically, the sending module 802 is used to send the F1AP message or user plane data to the IAB node through a first transport network layer association (TNLA) between the CU of the first IAB host and the DU of the IAB node. The first TNLA corresponds to the Internet Protocol IP address allocated to the IAB node by the first IAB host. Alternatively, the sending module 802 is used to send the F1AP message or user plane data to the IAB node through a second transport network layer association (TNLA) between the CU of the first IAB host and the DU of the IAB node. The second TNLA corresponds to the Internet Protocol IP address allocated to the IAB node by the second IAB host.

[0216] The communication device 800 may further include an acquisition module 803, configured to receive an IP address assigned to the IAB node by the second IAB host from the CU of the second IAB host. Further, the processing module 801 uses the IP address assigned to the IAB node by the second IAB host to enable the sending module 802 to send the F1AP message or user plane data to the IAB node via the second TNLA.

[0217] The F1AP message type includes user equipment-related and non-user equipment-related types. The user plane data indicates the identifier or IP address of the GTP-U tunnel for the F1 interface. The QoS attribute is the Differentiated Services Code Point and / or, the Flow Label. The F1AP message carries the configuration information of the IAB node's DU under the first IAB host.

[0218] Design 2: The communication device 800 may include a transmitting module 802. The transmitting module 802 is used to send an F1 application protocol (F1AP) message type indication and a QoS attribute to the CU of the first IAB host. The F1AP message type indication and the QoS attribute have a corresponding relationship, which is used to determine the QoS attribute corresponding to the F1AP message of the CU of the first IAB host. The F1 interface is the communication interface between the CU of the first IAB host and the Distributed Unit (DU) of the IAB node. Alternatively, the transmitting module 802 is used to send a user plane data indication and a QoS attribute to the CU of the first IAB host. The user plane data indication and the QoS attribute have a corresponding relationship, which is used to determine the QoS attribute corresponding to the user plane data of the CU of the first IAB host.

[0219] The sending module 802 is also used to send the IP address allocated by the second IAB host to the IAB node to the CU of the first IAB host. The IP address is used for the transmission of the F1AP message or the user plane data.

[0220] Furthermore, the sending module 802 is also used to send the IP address assigned to the IAB node by the first IAB host and the BAP address assigned to the IAB node by the second IAB host to the DU of the second IAB host. The IP address and the BAP address have a corresponding relationship, which is used to determine the BAP address of the target node corresponding to the F1AP message or user plane data. The F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

[0221] The F1AP message type includes user equipment-related and non-user equipment-related types. The user plane data indicates the identifier or IP address of the GTP-U tunnel for the F1 interface. The QoS attribute is the Differentiated Services Code Point (DSCP) and / or the flow label. The F1AP message carries the configuration information of the IAB node's DU under the first IAB host.

[0222] Design 3: The communication device 800 may include a processing module 801, a sending module 802, and an acquisition module 803. The acquisition module 803 is used to receive an F1 application protocol (F1AP) message type indication and QoS attribute from the CU of the first IAB host, wherein the F1AP message type indication and the QoS attribute have a corresponding relationship. The F1 interface is the communication interface between the CU of the first IAB host and the distributed unit (DU) of the IAB node. Alternatively, the acquisition module 803 is used to receive a user plane data indication and QoS attribute from the CU of the first IAB host, wherein the user plane data indication and the QoS attribute have a corresponding relationship.

[0223] The processing module 801 is used to send the routing configuration and bearer configuration corresponding to the QoS attribute to the DU of the second IAB host according to the correspondence.

[0224] Furthermore, the sending module 802 is also used to send the IP address assigned to the IAB node by the first IAB host and the BAP address assigned to the IAB node by the second IAB host to the DU of the second IAB host. The IP address and the BAP address have a corresponding relationship, which is used to determine the BAP address of the target node corresponding to the F1AP message or user plane data. The F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

[0225] The F1AP message type includes user equipment-related and non-user equipment-related types. The user plane data indicates the identifier or IP address of the GTP-U tunnel for the F1 interface. The QoS attribute is the Differentiated Services Code Point (DSCP) and / or the flow label. The F1AP message carries the configuration information of the IAB node's DU under the first IAB host.

[0226] Figure 9 This is a schematic block diagram of a communication device 900 provided in an embodiment of this application. The communication device 900 can be applied to the IAB donor-DU. The structure and function of the communication device 900 will be described in detail below.

[0227] The communication device 900 may include a processing module 901 and an acquisition module 902. The acquisition module 902 is used to receive the F1 application protocol (F1AP) and the QoS attributes corresponding to the F1AP message from the CU of the first IAB host, or to receive user plane data and the QoS attributes corresponding to the user plane data from the CU of the first IAB host, wherein the F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node;

[0228] The processing module 901 is used to perform routing and bearer mapping on the F1AP message or user plane data according to the routing configuration and bearer configuration corresponding to the QoS attribute.

[0229] Furthermore, the acquisition module 902 is also configured to receive the Internet Protocol IP address assigned to the IAB node by the first IAB host and the BAP address assigned to the IAB node by the second IAB host from the CU of the second IAB host, wherein the IP address and the BAP address have a corresponding relationship. The processing module 901 is also configured to determine the BAP address of the target node corresponding to the F1AP message or the user plane data according to the corresponding relationship; wherein the F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

[0230] The F1AP message type can include user equipment-related and non-user equipment-related types. The user plane data indicates the identifier or IP address of the GTP-U tunnel for the F1 interface. The QoS attribute is the Differentiated Services Code Point and / or, the Flow Label. The F1AP message carries the configuration information of the IAB node's DU under the first IAB host.

[0231] Figure 10 This is a schematic block diagram of a communication device 1000 provided in an embodiment of this application. The communication device 1000 can be applied to an IAB node. The structure and function of the communication device 1000 will be described in detail below, divided into different designs. Although the module names are the same across different designs, their structures and functions may differ.

[0232] Design 1: The communication device 1000 may include a processing module 1001 and an acquisition module 1003. The processing module 1001 is used to establish a first TNLA between the CU of the first IAB host and the DU of the IAB node using the IP address allocated to the IAB node by the second IAB host. The acquisition module 1003 is used to receive F1 application protocol (F1AP) messages or user plane data from the CU of the first IAB host through the first TNLA, where the F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

[0233] The F1AP message type includes user equipment-related and non-user equipment-related types. The user plane data indicates the identifier or IP address of the GTP-U tunnel for the F1 interface. The QoS attribute is the Differentiated Services Code Point and / or, the Flow Label. The F1AP message carries the configuration information of the IAB node's DU under the first IAB host.

[0234] Design 2: The communication device 1000 may include a processing module 1001 and an acquisition module 1003. The acquisition module 1003 is used to obtain the configuration information of the distributed unit (DU) of the IAB node under the target IAB host. The processing module 1001 is used to activate the configuration information after the MT of the IAB node switches from the source IAB host to the target IAB host.

[0235] Specifically, the acquisition module 1003 is used to receive the configuration information from the target IAB host.

[0236] Furthermore, the acquisition module 1003 is also configured to receive second information from the target IAB host, the second information being used to activate the configuration information. The processing module 1001 is specifically configured to activate the configuration information based on the second information.

[0237] Specifically, the acquisition module 1003 is used to receive at least one configuration information from the network management device. The processing module 1001 is further used to enable the acquisition module 1003 to determine the configuration information from the at least one configuration information.

[0238] Additionally, the communication device 1000 may also include a sending module 1002. The sending module 1002 is used to send a request message for establishing an F1 interface to the target IAB host, the request message including the configuration information of the IAB node's DU under the target IAB host. The receiving module 1003 is used to receive response information from the target IAB host regarding the request message.

[0239] Furthermore, the processing module 1001 is also used to establish a first TNLA between the CU of the target IAB host and the DU of the IAB node using the IP address allocated to the IAB node by the target IAB host. The sending module 1002 is specifically used to send the request information for establishing the F1 interface to the target IAB host through the first TNLA. The obtaining module 1003 is specifically used to receive the response information from the target IAB host regarding the request information through the first TNLA.

[0240] Optionally, before the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the processing module 1001 is further configured to establish a second transport network layer association (TNLA) between the CU of the target IAB host and the DU of the IAB node using the IP address allocated to the IAB node by the source IAB host. The sending module 1002 is specifically configured to send the request information for establishing the F1 interface to the target IAB host through the second TNLA. The receiving module 1003 is specifically configured to receive the response information from the target IAB host regarding the request information through the second TNLA.

[0241] For example, before the MT of the IAB node switches from the source IAB host to the target IAB host, the processing module 1001 is further configured to use the IP address allocated to the IAB node by the source IAB host to establish a second transport network layer association (TNLA) between the CU of the target IAB host and the DU of the IAB node. The sending module 1002 is specifically configured to send the request information for establishing the F1 interface to the target IAB host through the second TNLA.

[0242] Furthermore, after the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host, the processing module 1001 is also used to establish a first TNLA between the CU of the target IAB host and the DU of the IAB node using the IP address allocated to the IAB node by the target IAB host. The acquisition module 1003 is specifically used to receive response information from the target IAB host regarding the request information through the first TNLA.

[0243] Specifically, if the acquisition module 1003 receives a response from the target IAB host before the MT of the IAB node switches from the source IAB host to the target IAB host, then the response is used to deactivate the configuration information of the DU of the IAB node under the target IAB host, or...

[0244] If the MT of the IAB node switches from the source IAB host to the target IAB host, and the acquisition module 1003 receives the response information of the request information from the target IAB host, then the response information is used to activate the configuration information of the DU of the IAB node under the target IAB host.

[0245] Specifically, the processing module 1001 is used to automatically activate the configuration information. Furthermore, the sending module 1002 is also used to send first information to the target IAB host, the first information indicating that the configuration information has been activated.

[0246] This application provides a communication device 1100, and the structure and function of the communication device 1100 will be described in detail below. Figure 11 This is a schematic block diagram of a communication device 1100 provided in an embodiment of this application. The communication device 1100 can be applied to IAB donors. The structure and function of the communication device 1100 will be described in detail below, divided into different designs. Although the module names are the same across different designs, their structures and functions may differ.

[0247] Design 1: The communication device 1100 may include a processing module 1001 and an acquisition module 1103. The acquisition module 1103 is used to receive first information from an IAB node, the first information indicating that the configuration information of the distributed unit (DU) of the IAB node under the target IAB host has been activated. The processing module 1001 is used to determine that the configuration information has been activated based on the first information.

[0248] Design 2: The communication device 1100 may include a sending module 1102 and an acquisition module 1103. The acquisition module 1103 is used to receive request information from the IAB node for establishing an F1 interface.

[0249] The sending module 1102 is used to send the response information to the IAB node before the MT of the IAB node switches from the source IAB host to the target IAB host. The response information is used to deactivate the configuration information of the DU of the IAB node under the target IAB host. Alternatively, the sending module 1102 is used to send the response information to the IAB node after the mobile terminal MT of the IAB node switches from the source IAB host to the target IAB host. The response information is used to activate the configuration information of the DU of the IAB node under the target IAB host.

[0250] Specifically, the acquisition module 1103 is used to receive the request information for establishing an F1 interface from the IAB node through the second transport network layer association (TNLA) between the CU of the target IAB host and the DU of the IAB node. The second TNLA corresponds to the IP address allocated to the IAB node by the source IAB host. The sending module 1102 is used to send the response information of the request information to the IAB node through the second TNLA.

[0251] Specifically, the acquisition module 1103 is used to receive the request information for establishing an F1 interface from the IAB node through the first TNLA between the CU of the target IAB host and the DU of the IAB node, where the first TNLA corresponds to the IP address allocated to the IAB node by the target IAB host. The sending module 1102 is used to send the response information of the request information to the IAB node through the first TNLA.

[0252] Specifically, the acquisition module 1103 is used to receive request information from the IAB node for establishing an F1 interface through the second transport network layer association (TNLA) between the CU of the target IAB host and the DU of the IAB node before the MT of the IAB node switches from the source IAB host to the target IAB host. The second TNLA corresponds to the Internet Protocol IP address allocated to the IAB node by the source IAB host.

[0253] Specifically, the sending module 1102 is used to send response information of the request information to the IAB node through the first TNLA between the CU of the target IAB host and the DU of the IAB node after the MT of the IAB node switches from the source IAB host to the target IAB host. The first TNLA corresponds to the IP address allocated to the IAB node by the target IAB host.

[0254] Based on the same technical concept, this application also provides a device 1200, which will be described below with reference to the schematic block diagram of device 1200. Figure 12The structure and function of device 1200 are described in detail below. The device may include at least one processor 1201. Optionally, it may also include an interface circuit 1202. When the relevant program instructions are executed in the at least one processor 1201, the device 1200 may implement the communication methods and any possible designs provided in any of the foregoing embodiments. Alternatively, the processor 1201 may implement the communication methods and any possible designs provided in any of the foregoing embodiments through logic circuits or executable code instructions. The interface circuit 1202 may be used to receive program instructions and transmit them to the processor, or the interface circuit 1202 may be used for device 1200 to communicate and interact with other communication devices, such as exchanging control signaling and / or service data. For example, the interface circuit 1202 may be used to receive signals from other devices besides device 1200 and transmit them to the processor 1201, or to send signals from the processor 1201 to other communication devices besides device 1200. The interface circuit 1202 can be a code and / or data read / write interface circuit, or it can be a signal transmission interface circuit between a communication processor and a transceiver. Optionally, the communication device 1200 may also include at least one memory 1203, which can be used to store the required program instructions and / or data. Optionally, the device 1200 may also include a power supply circuit 1204, which can be used to power the processor 1201. The power supply circuit 1204 may be located on the same chip as the processor 1201, or it may be located on a separate chip. Optionally, the device 1200 may also include a bus 1205, through which the various parts of the device 1200 can be interconnected.

[0255] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc. A general-purpose processor can be a microprocessor, or it can be any conventional processor, etc.

[0256] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), or direct rambus RAM (DR RAM).

[0257] The power supply circuit described in this application includes, but is not limited to, at least one of the following: a power supply line, power supply to an electronic system, a power management chip, a power management processor, or a power management control circuit.

[0258] The transceiver device, interface circuit, or transceiver described in the embodiments of this application may include a separate transmitter and / or a separate receiver, or the transmitter and receiver may be integrated into one unit. The transceiver device, interface circuit, or transceiver can operate under the instruction of a corresponding processor. Optionally, the transmitter may correspond to a transmitter in a physical device, and the receiver may correspond to a receiver in a physical device.

[0259] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0260] In the embodiments of this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0261] Those skilled in the art will recognize that the unit or algorithm operations of the various examples described in conjunction with the embodiments disclosed herein can be implemented in hardware, or in software, or in a combination of both. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0262] In this application, "implemented through software" can refer to a processor reading and executing program instructions stored in memory to implement the functions corresponding to the aforementioned modules or units. Here, a processor refers to a processing circuit capable of executing program instructions, including but not limited to at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., all processing circuits capable of running program instructions. In other embodiments, the processor may also include circuits with other processing functions (such as hardware circuits for hardware acceleration, bus and interface circuits, etc.). The processor can be presented as an integrated chip, for example, as an integrated chip whose processing function only includes executing software instructions, or it can be presented as a system on a chip (SoC), that is, on a single chip, in addition to the processing circuit capable of running program instructions (often referred to as a "core"), it also includes other hardware circuits for implementing specific functions (of course, these hardware circuits can also be implemented separately based on ASICs or FPGAs). Correspondingly, the processing functions, in addition to executing software instructions, may also include various hardware acceleration functions (such as AI calculation, encoding / decoding, compression / decompression, etc.).

[0263] In this application, "implemented in hardware" means that the functions of the above-mentioned modules or units are implemented through hardware processing circuits that do not have program instruction processing capabilities. These hardware processing circuits can be composed of discrete hardware components or integrated circuits. To reduce power consumption and size, integrated circuits are typically used. The hardware processing circuits can include ASICs or programmable logic devices (PLDs); PLDs can include FPGAs, complex programmable logic devices (CPLDs), etc. These hardware processing circuits can be a single packaged semiconductor chip (e.g., packaged as an ASIC); or they can be integrated with other circuits (e.g., CPUs, DSPs) and packaged into a single semiconductor chip. For example, multiple hardware circuits and a CPU can be formed on a silicon substrate and packaged into a single chip, also known as a System-on-a-Chip (SoC). Alternatively, circuits for implementing FPGA functions and a CPU can be formed on a silicon substrate and packaged into a single chip, also known as a System-on-a-Chip (SoPC).

[0264] It should be noted that when this application is implemented through software, hardware, or a combination of both, different software or hardware can be used, and it is not limited to using only one type of software or hardware. For example, one module or unit can be implemented using a CPU, while another module or unit can be implemented using a DSP. Similarly, when implemented using hardware, one module or unit can be implemented using an ASIC, while another module or unit can be implemented using an FPGA. Of course, it is not limited to using the same software (e.g., all through a CPU) or the same hardware (e.g., all through an ASIC) to implement some or all modules or units. Furthermore, those skilled in the art will understand that software is generally more flexible but less performant than hardware, while hardware is the opposite. Therefore, those skilled in the art can choose software, hardware, or a combination of both based on actual needs.

[0265] In the above embodiments, the descriptions of each embodiment have their own emphasis. Parts not described in detail in a particular embodiment can be referred to in the relevant descriptions of other embodiments. The embodiments of this application can be combined, and some technical features in the embodiments can be decoupled from specific embodiments. Combining with existing technology can solve the technical problems involved in the embodiments of this application.

[0266] In this embodiment, the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments in this application, depending on actual needs.

[0267] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0268] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and may include several instructions to cause a computer device, such as a personal computer, server, or network device, or a processor, to execute all or part of the operations of the methods described in the various embodiments of this application. The aforementioned storage medium may include various media capable of storing program code or computer-readable storage media, such as a USB flash drive, portable hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0269] In the description of this application, terms such as "first", "second", "S201" or "S202" are used only for the purpose of distinguishing descriptions and for the convenience of context. The different order numbers themselves do not have specific technical meanings and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying the order of execution of operations.

[0270] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural. Additionally, the character " / " in this document indicates that the preceding and following related objects have an "or" relationship.

[0271] In this application, "transmission" can include the following three situations: sending data, receiving data, or both sending and receiving data. In this application, "data" can include business data and / or signaling data.

[0272] The terms “comprising” or “having” and any variations thereof in this application are intended to cover a non-exclusive inclusion, such as a process / method that includes a series of steps, or a system / product / equipment that includes a series of units, not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes / methods / products / equipment.

[0273] In the description of this application, "at least one" means one or more. "Including at least one of the following: A, B, C" means that it may include A, or include B, or include C, or include A and B, or include A and C, or include B and C, or include A, B and C.

[0274] The solutions provided in this application are applicable to various communication systems, such as: Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Worldwide Interoperability for Microwave Access (WiMAX), 5th Generation (5G), or New Radio (NR), as well as other network systems that can be used to provide mobile communication services. This application does not limit the scope of these systems.

[0275] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: The centralized unit (CU) of the first integrated access backhaul IAB host determines the QoS attribute corresponding to the F1AP message based on the correspondence between the F1AP message type and the Quality of Service (QoS) attribute of the F1 interface application protocol, and sends the F1AP message and the corresponding QoS attribute to the distributed unit (DU) of the second IAB host. The F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node, and the correspondence is obtained by the CU of the first IAB host from the CU of the second IAB host; or... The centralized unit (CU) of the first integrated access backhaul (IAB) host determines the QoS attribute corresponding to the user plane data based on the correspondence between user plane data and QoS attributes, and sends the user plane data and the corresponding QoS attribute to the distributed unit (DU) of the second IAB host. The correspondence is obtained by the CU of the first IAB host from the CU of the second IAB host.

2. The method according to claim 1, characterized in that, The CU of the first IAB host sends the F1AP message and the corresponding QoS attributes of the F1AP message to the DU of the second IAB host, including: The CU of the first IAB host encapsulates the F1AP message in an Internet Protocol (IP) packet and sends the IP packet to the DU of the second IAB host, wherein the IP header of the IP packet carries the QoS attribute corresponding to the F1AP message; or, The CU of the first IAB host sends the user plane data and the corresponding QoS attributes to the DU of the second IAB host, including: The CU of the first IAB host encapsulates the user plane data in an Internet Protocol (IP) packet and sends the IP packet to the DU of the second IAB host. The IP header of the IP packet carries the QoS attribute corresponding to the user plane data.

3. The method according to claim 2, characterized in that, The destination IP address of the IP packet is the IP address assigned to the IAB node by the second IAB host.

4. The method according to any one of claims 1-3, characterized in that, The method includes: The CU of the first IAB host sends the F1AP message or user plane data to the IAB node through the second transport network layer association (TNLA) between the CU of the first IAB host and the DU of the IAB node. The second TNLA corresponds to the Internet Protocol IP address allocated to the IAB node by the second IAB host.

5. The method according to claim 4, characterized in that, The method further includes: The CU of the first IAB host receives the IP address assigned to the IAB node by the second IAB host from the CU of the second IAB host. The CU of the first IAB host sends the F1AP message or user plane data to the IAB node through the second transport network layer association (TNLA) between the CU of the first IAB host and the DU of the IAB node, including: The CU of the first IAB host uses the IP address allocated to the IAB node by the second IAB host to send the F1AP message or user plane data to the IAB node through the second TNLA.

6. A communication method, characterized in that, include: The centralized unit (CU) of the second access backhaul integrated IAB host sends at least one F1 interface application protocol F1AP message type and at least one quality of service (QoS) attribute, or at least one user plane data and at least one QoS attribute, to the CU of the first IAB host. Wherein, the F1 interface is the communication interface between the CU of the first IAB host and the distributed unit (DU) of the IAB node; the correspondence between at least one F1AP message type and at least one QoS attribute is used by the CU of the first IAB host to determine the QoS attribute corresponding to the F1AP message sent to the DU of the second IAB host; and the correspondence between at least one user plane data and at least one QoS attribute is used by the CU of the first IAB host to determine the QoS attribute corresponding to the user plane data sent to the DU of the second IAB host.

7. The method according to claim 6, characterized in that, The CU of the second IAB host sends a mapping relationship between at least one F1AP message type and at least one QoS attribute to the CU of the first IAB host, including: The CU of the second IAB host sends an IFAP message type indication and a QoS attribute to the CU of the first IAB host, wherein the IFAP message type indication and the QoS attribute have a corresponding relationship; or, The CU of the second IAB host sends a mapping relationship between at least one user plane data and at least one QoS attribute to the CU of the first IAB host, including: The CU of the second IAB host sends a user plane data indication and a QoS attribute to the CU of the first IAB host, and the user plane data indication and the QoS attribute have a corresponding relationship.

8. The method according to claim 7, characterized in that, The user plane data indicates the identifier or IP address of the General Packet Radio Service User Plane Tunneling Protocol (GTP-U) tunnel for the F1 interface.

9. The method according to any one of claims 6-8, characterized in that, The method further includes: The CU of the second IAB host sends the IP address allocated by the second IAB host to the CU of the first IAB host. The IP address is used for the transmission of the F1AP message or the user plane data.

10. A communication method, characterized in that, include: The distributed unit (DU) of the second integrated access backhaul IAB host receives F1 interface application protocol F1AP messages and the corresponding quality of service (QoS) attributes from the centralized unit (CU) of the first IAB host. The F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node. The QoS attributes are determined according to the correspondence between the F1AP message type and the QoS attributes in the CU of the second IAB host. The DU of the second IAB host performs routing and bearer mapping on the F1AP message or user plane data according to the routing configuration and bearer configuration corresponding to the QoS attribute; or, The distributed unit (DU) of the second integrated access backhaul IAB host receives user plane data and the QoS attributes corresponding to the user plane data from the centralized unit (CU) of the first IAB host. The QoS attributes are determined based on the correspondence between user plane data and QoS attributes in the CU of the second IAB host. The DU of the second IAB host performs routing and bearer mapping on the user plane data according to the routing configuration and bearer configuration corresponding to the QoS attribute.

11. The method according to claim 10, characterized in that, The DU of the second IAB host receives the F1AP message and the QoS attributes corresponding to the F1AP message from the CU of the first IAB host, including: The DU of the second IAB host receives an Internet Protocol (IP) packet from the CU of the first IAB host. The IP packet includes the FIAP message, and the IP header of the IP packet carries the QoS attribute corresponding to the FIAP message; or, The DU of the second IAB host receives user plane data and the corresponding QoS attributes from the CU of the first IAB host, including: The DU of the second IAB host receives Internet Protocol (IP) packets from the CU of the first IAB host. The IP packets include the user plane data, and the IP header of the IP packets carries the QoS attributes corresponding to the user plane data.

12. The method according to claim 11, characterized in that, The destination IP address of the IP packet is the IP address assigned to the IAB node by the DU of the second IAB host.

13. A communication method, characterized in that, include: The access backhaul integrated IAB node uses the Internet Protocol IP address allocated to the IAB node by the second IAB host to establish a first transport network layer association (TNLA) between the centralized unit (CU) of the first IAB host and the distributed unit (DU) of the IAB node. The IAB node receives F1AP messages or user plane data from the CU of the first IAB host through the first TNLA. The F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

14. The method according to claim 13, characterized in that, The IAB node receives F1 interface application protocol F1AP messages or user plane data from the CU of the first IAB host via the first TNLA, including: The IAB node receives an IP packet from the CU of the first IAB host. The IP packet includes the F1AP message or the user plane data. The destination IP address of the IP packet is the IP address assigned to the IAB node by the DU of the second IAB host.

15. The method according to claim 13 or 14, characterized in that, The F1AP message types include user equipment-related types and non-user equipment-related types.

16. The method according to claim 15, characterized in that, The F1AP message type is determined based on the QoS attributes corresponding to the F1AP message, wherein the QoS attributes are Differentiated Service Code Point (DSCP) and / or Flow Label.

17. The method according to claim 13 or 14, characterized in that, The F1AP message carries the configuration information of the DU of the IAB node under the first IAB host.

18. A communication device applied to a centralized unit (CU) of a first integrated access backhaul (IAB) host, characterized in that, include: The processing module is configured to determine the QoS attribute corresponding to the F1AP message based on the correspondence between the F1AP message type and the Quality of Service (QoS) attribute, and to enable the sending module to send the F1AP message and the corresponding QoS attribute to the DU of the second IAB host. The F1 interface is the communication interface between the CU of the first IAB host and the distributed unit (DU) of the IAB node, and the correspondence is obtained by the CU of the first IAB host from the CU of the second IAB host; or... The processing module is configured to determine the QoS attribute corresponding to the user plane data based on the correspondence between user plane data and QoS attributes, and to enable the sending module to send the user plane data and the QoS attribute corresponding to the user plane data to the distributed unit (DU) of the second IAB host, wherein the correspondence is obtained by the CU of the first IAB host from the CU of the second IAB host.

19. The apparatus according to claim 18, characterized in that, The processing module is specifically used to encapsulate the F1AP message in an Internet Protocol (IP) packet, and to cause the sending module to send the IP packet to the DU of the second IAB host, wherein the IP header of the IP packet carries the QoS attribute corresponding to the F1AP message; or, The processing module is specifically used to encapsulate the user plane data in an Internet Protocol (IP) packet, and to enable the sending module to send the IP packet to the DU of the second IAB host, wherein the IP header of the IP packet carries the QoS attribute corresponding to the user plane data.

20. The apparatus according to claim 19, characterized in that, The destination IP address of the IP packet is the IP address assigned to the IAB node by the second IAB host.

21. The apparatus according to any one of claims 18-20, characterized in that, The sending module is specifically used to send the F1AP message or user plane data to the IAB node through the second transport network layer association (TNLA) between the CU of the first IAB host and the DU of the IAB node. The second TNLA corresponds to the Internet Protocol IP address allocated to the IAB node by the second IAB host.

22. The apparatus according to claim 21, characterized in that, The device further includes an acquisition module, which is used to receive the IP address assigned by the second IAB host to the IAB node from the CU of the second IAB host; The processing module uses the IP address allocated to the IAB node by the second IAB host, so that the sending module sends the F1AP message or user plane data to the IAB node through the second TNLA.

23. A communication device applied to a centralized unit (CU) of a second integrated access backhaul (IAB) host, characterized in that, include: The sending module is used to send to the CU of the first IAB host a correspondence between at least one F1 interface application protocol F1AP message type and at least one quality of service (QoS) attribute, or a correspondence between at least one user plane data and at least one QoS attribute. Wherein, the F1 interface is the communication interface between the CU of the first IAB host and the distributed unit (DU) of the IAB node; the correspondence between at least one F1AP message type and at least one QoS attribute is used by the CU of the first IAB host to determine the QoS attribute corresponding to the F1AP message sent to the DU of the second IAB host; and the correspondence between at least one user plane data and at least one QoS attribute is used by the CU of the first IAB host to determine the QoS attribute corresponding to the user plane data sent to the DU of the second IAB host.

24. The apparatus according to claim 23, characterized in that, The sending module is specifically used to send an F1AP message type indication and a QoS attribute to the CU of the first IAB host, wherein the F1AP message type indication and the QoS attribute have a corresponding relationship; or... The sending module is specifically used to send user plane data indication and QoS attributes to the CU of the first IAB host, and the user plane data indication and the QoS attributes have a corresponding relationship.

25. The apparatus according to claim 24, characterized in that, The user plane data indicates the identifier or IP address of the General Packet Radio Service User Plane Tunneling Protocol (GTP-U) tunnel for the F1 interface.

26. The apparatus according to any one of claims 23-25, characterized in that, The sending module is also used to send the IP address allocated by the second IAB host to the IAB node to the CU of the first IAB host. The IP address is used for the transmission of the F1AP message or the user plane data.

27. A communication device applied to a distributed unit (DU) of a second integrated access backhaul (IAB) host, characterized in that, include: The acquisition module is used to receive F1 interface application protocol F1AP messages and the service quality (QoS) attributes corresponding to the F1AP messages from the centralized unit (CU) of the first IAB host, wherein the F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node, and the QoS attributes are determined according to the correspondence between the F1AP message type and the QoS attributes in the CU of the second IAB host. The processing module is used to perform routing and bearer mapping on the F1AP message or user plane data according to the routing configuration and bearer configuration corresponding to the QoS attribute; or, The acquisition module is used to receive user plane data and QoS attributes corresponding to the user plane data from the centralized unit (CU) of the first IAB host. The QoS attributes are determined according to the correspondence between user plane data and QoS attributes in the CU of the second IAB host. The processing module is used to perform routing and bearer mapping on the user plane data according to the routing configuration and bearer configuration corresponding to the QoS attribute.

28. The apparatus according to claim 27, characterized in that, The acquisition module is specifically used to receive Internet Protocol (IP) packets from the CU of the first IAB host, wherein the IP packets include the FIAP message and the IP header of the IP packets carries the QoS attribute corresponding to the FIAP message, or the IP packets include the user plane data and the IP header of the IP packets carries the QoS attribute corresponding to the user plane data.

29. The apparatus according to claim 28, characterized in that, The destination IP address of the IP packet is the IP address assigned to the IAB node by the DU of the second IAB host.

30. A communication device applied to an integrated access and backhaul (IAB) node, characterized in that, include: The processing module is used to establish a first transport network layer association (TNLA) between the centralized unit (CU) of the first IAB host and the distributed unit (DU) of the IAB node using the Internet Protocol IP address allocated to the IAB node by the second access backhaul integrated IAB host. The acquisition module is used to receive F1 interface application protocol F1AP messages or user plane data from the CU of the first IAB host through the first TNLA, wherein the F1 interface is the communication interface between the CU of the first IAB host and the DU of the IAB node.

31. The apparatus according to claim 30, characterized in that, The acquisition module is specifically used to receive IP packets from the CU of the first IAB host. The IP packets include the F1AP message or the user plane data. The destination IP address of the IP packets is the IP address allocated by the DU of the second IAB host to the IAB node.

32. The apparatus according to claim 30 or 31, characterized in that, The F1AP message types include user equipment-related types and non-user equipment-related types.

33. The apparatus according to claim 32, characterized in that, The F1AP message type is determined based on the QoS attributes corresponding to the F1AP message, wherein the QoS attributes are Differentiated Service Code Point (DSCP) and / or Flow Label.

34. The apparatus according to claim 30 or 31, characterized in that, The F1AP message carries the configuration information of the DU of the IAB node under the first IAB host.

35. A communication device, characterized in that, include: At least one processor and interface circuitry, wherein the computer program involved executes in the at least one processor to cause the communication device to perform the method according to any one of claims 1-17.

36. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 17.

37. A computer program product, characterized in that, The computer program product includes the program instructions involved, which, when executed, implement the method as described in any one of claims 1 to 17.

38. A communication system, characterized in that, It includes the communication device as described in any one of claims 18 to 22, the communication device as described in any one of claims 23 to 26, and the communication device as described in any one of claims 27 to 29.

39. The system according to claim 38, characterized in that, The system further includes a communication device as described in any one of claims 30 to 34.

Images