Communication methods, devices, electronic equipment and computer-readable storage media

By managing user data transmission and storage through communication methods between anchor nodes and relay nodes, the problem of data loss during relay node migration is solved, thus improving network efficiency.

CN114390450BActive Publication Date: 2026-11-17BEIJING SAMSUNG TELECOM R&D CENT +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202110536675.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-10-21
Filing Date
2021-05-17
Publication Date
2026-11-17
Estimated Expiration
2041-05-17

AI Technical Summary

Technical Problem

During relay node migration, the existing communication scheme leads to the loss and duplicate transmission of user data, reducing the efficiency of the relay network.

Method used

By implementing communication methods between anchor nodes and relay nodes, including sending and receiving configuration messages to manage the transmission and storage of user data, data continuity is ensured during migration.

Benefits of technology

This effectively avoids the loss and duplicate transmission of user data, and improves the transmission efficiency of the relay network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114390450B_ABST
    Figure CN114390450B_ABST
Patent Text Reader

Abstract

This application provides a communication method, apparatus, electronic device, and computer-readable storage medium, relating to the field of wireless communication technology. The method, which can be executed by a first node, may include: receiving a first message sent by a second node, the first message being used to configure the first node for the transmission and / or storage of user data packets. Based on the solution provided by this application, one or more problems such as data packet loss, network resource waste, and transmission failure that may occur due to the migration of relay nodes in the network can be effectively mitigated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a communication method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] To meet the increased demand for wireless data communication services since the deployment of 4G (The 4th Generation Mobile Communication Technology) systems, efforts have been made to develop improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE (Long Term Evolution) systems".

[0003] Wireless communication is one of the most successful innovations in modern history. The number of subscribers to wireless communication services has exceeded 5 billion and continues to grow rapidly. The demand for wireless data services is growing rapidly due to the increasing prevalence of smartphones and other mobile data devices (such as tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and businesses. To meet the rapid growth of mobile data services and support new applications and deployments, improving the efficiency and coverage of wireless interfaces is crucial. Summary of the Invention

[0004] In order to at least address one of the shortcomings of the existing technology, this application provides the following technical solution:

[0005] In a first aspect, this application provides a communication method executed by a first node, the method comprising: receiving a first message sent by a second node, the first message being used to configure the first node for the transmission and / or storage of user data packets.

[0006] Secondly, this application provides a communication method executed by a second node, the method comprising: sending a first message, wherein the first message is used to configure the first node for the transmission and / or storage of user data packets.

[0007] Thirdly, this application provides a communication method executed by a first node, the method comprising: receiving a third message, wherein the third message is used to configure the transmission of user data packets corresponding to the first node; and transmitting user data packets according to the third message.

[0008] Fourthly, this application provides a communication method, which is executed by a second node, the method comprising:

[0009] Send a third message, wherein the third message is used to configure the transmission of user data packets corresponding to the first node.

[0010] Fifthly, this application provides a communication method executed by a third node, the method comprising: sending a fourth message, the fourth message being used to indicate the timing of a configuration update and / or a configuration release of the fourth node.

[0011] In a sixth aspect, this application provides a communication method executed by a fourth node, the method comprising: receiving a fourth message sent by a third node, the fourth message being used to indicate the timing of a configuration update and / or a configuration release of the fourth node.

[0012] Seventhly, this application provides a communication method executed by a sixth node, the method comprising:

[0013] Send a fifth message, which includes configuration information about the transmission and / or processing of data packets by the user terminal accessing the seventh node, wherein the transmission configuration information includes configuration information corresponding to the relay node before migration and / or configuration information corresponding to the migration.

[0014] Eighthly, this application provides a communication method executed by a user terminal, the method comprising: receiving a fifth message, the fifth message including configuration information regarding the transmission and / or processing of data packets by the user terminal accessing the seventh node, wherein the transmission configuration information includes configuration information corresponding to the relay node before migration and / or configuration information corresponding to the migration after migration; and performing data packet transmission and / or processing based on the fifth message.

[0015] Corresponding to the method provided in the embodiments of this application, the embodiments of this application also provide a corresponding communication device, which includes a communication module.

[0016] In one aspect, the communication module can be configured to receive a first message sent by a second node, the first message being used to configure the first node for the transmission and / or storage of user data packets.

[0017] On the other hand, the communication module is configured to send a first message, wherein the first message is used to configure the first node for the transmission and / or storage of user data packets.

[0018] On another front, the communication module is configured to receive a third message and transmit user data packets according to the third message, wherein the third message is used to configure the transmission of user data packets corresponding to the first node.

[0019] On the other hand, the communication module is configured to send a third message, wherein the third message is used to configure the transmission of user data packets corresponding to the first node.

[0020] On the other hand, the communication module is configured to send a fourth message, which indicates the timing of configuration update and / or configuration release for the fourth node.

[0021] On another front, the communication module is configured to receive a fourth message sent by a third node, the fourth message being used to indicate the timing of configuration updates and / or configuration releases for the fourth node.

[0022] On the other hand, the communication module is configured to send a fifth message, the fifth message including configuration information about the transmission and / or processing of data packets by the user terminal accessing the seventh node, wherein the transmission configuration information includes configuration information corresponding to the relay node before migration and / or configuration information corresponding to the migration.

[0023] On another front, the communication module is configured to: receive a fifth message and transmit and / or process data packets based on the fifth message, wherein the fifth message includes configuration information regarding the transmission and / or processing of data packets by the user terminal accessing the seventh node, wherein the transmission configuration information includes configuration information corresponding to the relay node before migration and / or configuration information corresponding to the migration.

[0024] The beneficial effects of the technical solutions provided in this application will be described in conjunction with various optional embodiments in the following description, and will not be described again here. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0026] Figure 1 Here is an example of a relay network;

[0027] Figure 2 An example of an exemplary system architecture to which the methods provided in the embodiments of this application are applicable;

[0028] Figure 3a and Figure 3b Here is an example of a base station structure;

[0029] Figure 4a , Figure 4b and Figure 4c Examples of three types of relay node migration;

[0030] Figure 5This is a flowchart example of a communication method according to the first aspect of the present invention;

[0031] Figure 6 This is a flowchart example of a communication method according to the second aspect of the present invention;

[0032] Figure 6 a(1) and Figure 6 a(2) is an example of a communication method according to the second aspect of the present invention;

[0033] Figure 6b Example 1 of a communication method according to the second aspect of the present invention;

[0034] Figure 6c This is a second example of the flow of a communication method according to the second aspect of the present invention;

[0035] Figure 6d Example 3 of the process of a communication method according to the second aspect of the present invention;

[0036] Figure 7 This is a flowchart example of a communication method according to a third aspect of the present invention;

[0037] Figure 8 Example 1 of the process of a communication method according to the fourth aspect of the present invention;

[0038] Figure 9 Example 2 of the process of a communication method according to the fourth aspect of the present invention;

[0039] Figure 10 Example 3 of the process of a communication method according to the fourth aspect of the present invention;

[0040] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0041] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting the invention.

[0042] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this specification means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0043] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0044] Those skilled in the art will understand that the terms "terminal" and "terminal device" as used herein include both devices that receive wireless signals, devices that only possess wireless signal receiver capabilities without transmission capabilities, and devices with receiving and transmitting hardware, devices that have receiving and transmitting hardware capable of bidirectional communication over a bidirectional communication link. Such devices may include: cellular or other communication devices having a single-line display, a multi-line display, or a cellular or other communication device without a multi-line display; PCS (Personal Communications Service) that can combine voice, data processing, fax, and / or data communication capabilities; PDA (Personal Digital Assistant) that may include a radio frequency receiver, pager, Internet / intranet access, web browser, notepad, calendar, and / or GPS (Global Positioning System) receiver; and conventional laptop and / or handheld computers or other devices that have and / or include radio frequency receivers. As used herein, "terminal" or "terminal device" can be portable, transportable, installed in a means of transportation (air, sea, and / or land), or suitable and / or configured to operate locally, and / or in a distributed manner, operating in any other location on Earth and / or in space. "Terminal" or "terminal device" as used herein can also be a communication terminal, an internet access terminal, or a music / video playback terminal, such as a PDA, a MID (Mobile Internet Device), and / or a mobile phone with music / video playback capabilities, or a smart TV, set-top box, etc.

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. The various optional embodiments provided below can be implemented individually or in combination with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0046] In NR (New Radio access) networks, a relay network architecture, namely IAB (Integrated Access and Backhaul) network, has been proposed to extend the network coverage. Figure 1A schematic architecture of a multi-hop relay network (IAB network) is presented. The figure shows a network architecture including an anchor node (e.g., IAB donor / anchor) and two relay nodes (e.g., IAB node). The anchor node can be a standalone base station or a base station composed of an IAB-donor central unit (CU) and an IAB-donor distributed unit (DU). Relay nodes (relay node 1 and relay node 2 shown in the figure) include mobile terminal functions and distributed terminal functions. The mobile terminal function and distributed terminal function of a relay node can also be described as the relay node including a mobile terminal function component (…). Figure 1 The mobile terminal portion and the distribution unit functional portion (described in the text) Figure 1 (The distribution unit portion shown).

[0047] like Figure 1 As shown, users (i.e., user equipment / user terminals / terminal devices) in this multi-hop relay network can access the network through anchor nodes, their distribution units, or relay nodes. For example, users 1 / 2 / 3 can access the relay network through the distribution unit of the anchor node, the distribution unit portion of relay node 1, and the distribution unit portion of relay node 2, respectively. The mobile terminal function portion of a relay node is used to communicate with the upstream node of the relay node (e.g., the mobile terminal portion of relay node 1 is used to communicate with the anchor node or its distribution unit, and the mobile terminal portion of relay node 2 is used to communicate with the distribution unit portion of relay node 1). The distribution unit function portion is used to communicate with the downstream node of the relay node (e.g., the distribution unit portion of relay node 1 is used to communicate with user 2, and can also be used to communicate with the mobile terminal portion of relay node 2).

[0048] In such Figure 1 In the multi-hop relay network shown, the link between the distribution unit portion of relay node 1 and the mobile terminal portion of relay node 2 is used to transmit data for user 3, while the link between the distribution unit of the anchor node and the mobile terminal portion of relay node 1 is used to transmit data for both user 2 and user 3. Such links share a common characteristic: the users served by this link access the network through another distribution unit portion. Such links can be called backhaul links, such as... Figure 1 The backhaul link channel 1 and backhaul link channel 2 are shown in the figure.

[0049] The mobile terminal portion of a relay node can be viewed as a user accessing the network, and therefore it has the functions of a regular user (non-relay node). For example, the mobile terminal portion can establish an SRB (Signaling Radio Bearer) with its upstream node to send RRC (Radio Resource Control) messages, and can also establish a DRB (Data Radio Bearer) to send data.

[0050] The centralized unit of the anchor node includes the following protocol stacks: the service control plane protocol stack includes the Radio Resource Control (RRC) protocol layer and the Packet Data Convergence Protocol (PDCP) layer; the service user plane protocol stack includes the Service Data Adaptation Protocol (SDAP) layer and the PDCP layer. The distribution unit of the anchor node or the distribution unit portion of the relay node includes the following protocol stacks: the service control plane and user plane protocol stacks include the Radio Link Control (RLC) protocol layer, the Medium Access Control (MAC) protocol layer, and the Physical layer (PHY). The interface between the centralized unit and the distribution unit of the anchor node, and between the centralized unit of the anchor node and the distribution unit of the relay node, is the F1 interface (see 3GPP TS38.473).

[0051] In a relay network, relay nodes may migrate, meaning the upstream node they are connected to may change. After migration, user data transmission can continue. However, during migration, communication between the node and the source anchor node (the anchor node before migration) is interrupted, and communication with the target anchor node (the anchor node after migration) resumes only after the migration is complete. This process can lead to user data loss and duplicate transmissions, reducing the efficiency of the relay network. Therefore, existing communication solutions require improvement.

[0052] To better understand and illustrate the various optional implementation schemes provided in this application, the following description, in conjunction with an optional communication network architecture to which this application applies, illustrates the solutions of this application. Those skilled in the art will understand that the network architecture and the structures of the network devices within that architecture, as given below, are illustrative structures to which the solutions provided in this application can be applied. The descriptions of these structures are merely for the purpose of facilitating understanding and illustrating the optional embodiments of this application, and should not constitute a limitation on the various embodiments of this application, nor should they be construed as limiting the scope of this disclosure in any way. The principles of the various optional embodiments of this application can be implemented in any appropriately arranged system or device.

[0053] As an example Figure 2 A schematic diagram of a network architecture to which this application applies is shown. As shown in the figure, User Equipment (UE) 201 is a terminal device used to receive / transmit data. Next Generation Radio Access Network (NG-RAN) 202 is a radio access network, including base stations (gNBs or eNBs connected to the 5G core network (5GC, also called ng-gNBs) that provide access to the wireless network interface for the UE. Access and Mobility Management Function (AMF) 203 is responsible for managing the UE's mobility context and security information. User Plane Function (UPF) 204 mainly provides user plane functions. Session Management Function (SMF) 205 is responsible for session management. Data network (DN) 206 includes services such as operator services, Internet access, and third-party services.

[0054] In NR (New Radio) systems, to support network function virtualization and more efficient resource management and scheduling, the base station (gNB) providing the wireless network interface for the UE can be further divided into a centralized unit gNB-CU (gNB central unit) and a distributed unit gNB-DU (gNB distributed unit) (referred to as CU and DU in this embodiment), such as Figure 3aAs shown. The CU has Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocol layers. The DU has Radio Link Control Protocol (RLC), Media Access Control (MAC), and Physical Layer (PHY). The CU and DU share a standardized public interface, F1. The F1 interface is divided into the control plane F1-C interface and the user plane F1-U interface. The transport network layer of the F1-C interface is based on IP (Internet Protocol). To provide more reliable signaling transmission, the SCTP (Stream Control Transmission Protocol) protocol is added on top of IP. The application layer protocol is F1AP (F1 Application Protocol), which can be found in standard 3GPP TS38.473. SCTP can provide reliable application layer message transmission. The transport layer of the F1-U interface is based on the protocol UDP (User Datagram Protocol) / IP. GTP-U (General Packet Radio Service Tunnel Protocol User) is used on top of UDP / IP to carry User Plane Protocol Data Units (PDUs).

[0055] Furthermore, such as Figure 3b As shown, the gNB-CU can include gNB-CU-CP (the control plane portion of the base station's centralized unit) and gNB-CU-UP (the user plane portion of the base station's centralized unit). gNB-CU-CP contains the control plane functions of the base station, featuring RRC and PDCP protocol layers. gNB-CU-UP contains the user plane functions of the base station, featuring SDAP and PDCP protocol layers. The interface between gNB-CU-CP and gNB-CU-UP is a standardized public interface, E1, using the E1AP (E1 Application Protocol), which can be found in standard 3GPP TS38.463. The interface between the control plane portion of the base station's centralized unit and the base station's distributed unit is the F1-C interface, i.e., the F1 control plane interface. The interface between the user plane portion of the base station's centralized unit and the base station's distributed unit is the F1-U interface, i.e., the F1 user plane interface.

[0056] In multi-hop relay networks, a UE can access the network through a base station (anchor node), a base station's distribution unit, or a relay node (such as the distribution unit portion of a relay node). When a UE accesses the network through a relay node, the relay node may migrate, meaning its upstream node changes. However, maintaining user data transmission during migration is a critical issue. The purpose of this application is to address at least one of the problems of user data loss and retransmission that may occur during relay node migration, thereby avoiding or reducing user data loss and duplicate transmissions.

[0057] In the various optional embodiments of this application, it should be noted that the names of various messages, various indication information, and various configuration information mentioned in the various optional embodiments of this application are only illustrative names and are not unique. Other message or information names may also be used. Similarly, the use of terms such as "first" and "second" in the descriptions of various messages and / or information is only used to distinguish messages and / or information and does not constitute other limitations on information and / or messages. For example, the limitations such as "first" and "second" appearing in this application do not limit the order of execution.

[0058] Furthermore, it is understood by those skilled in the art that the solutions provided in the optional embodiments of this application may include other communication steps not described in actual implementation. In the description of the optional embodiments of this application, some other steps or detailed descriptions of some steps may be omitted, and these omitted contents are clear to those skilled in the art. The solutions based on the embodiments of this application are conceivable implementation steps or specific implementation methods of the steps.

[0059] In this embodiment, "uplink" refers to the direction of data transmission from the UE to the network device, such as from the UE to a relay node, or from a relay node to an anchor node. For example, a relay node sending a data packet to an anchor node (or the centralized unit of the anchor node, or the control plane portion of the centralized unit of the anchor node, or the user plane portion of the centralized unit of the anchor node) can be called an uplink data packet. Correspondingly, "downlink" refers to the direction of data transmission from the network device to the UE, such as an anchor node sending data to a relay node, a relay node sending data to its next-level node, or a relay node sending data to the UE. For example, an anchor node (or the centralized unit of the anchor node, or the control plane portion of the centralized unit of the anchor node, or the user plane portion of the centralized unit of the anchor node) sending a data packet to a relay node can be called a downlink data packet.

[0060] by Figure 1Taking the relay network shown as an example, data transmission from relay node 2 to relay node 1, data transmission from relay node 1 to anchor node, and data transmission from users to their corresponding network access nodes (e.g., user 1 accesses the distribution unit of anchor node, and user 2 accesses the distribution unit portion of relay node 1) are all uplink. Data transmission from anchor node, relay node 1, and relay node 2 to their corresponding users, data transmission from anchor node to relay node 1, and data transmission from relay node 1 to relay node 2 are all downlink.

[0061] Furthermore, the descriptions of "child node" and "parent node" in the embodiments of this application are based on the "upward" direction, and are still based on... Figure 1 Taking the network structure shown as an example, the anchor node (or the distribution unit of the anchor node, or the centralized unit of the anchor node, or the control plane portion of the centralized unit of the anchor node, or the user plane portion of the centralized unit of the anchor node) is the parent node of relay node 1 (or the mobile terminal portion of relay node 1, or the distribution unit portion), and relay node 2 (or the mobile terminal portion of relay node 2, or the distribution unit portion) is the child node of relay node 1 (or the mobile terminal portion of relay node 1, or the distribution unit portion). It is understood that this description method is not unique; for example, it can also be described based on "downlink," in which case relay node 2 can serve as the parent node of relay node 1.

[0062] It is understandable that any given relay node may have both child and parent nodes, such as... Figure 1 In the example, relay node 1 has an anchor node as its parent and relay node 2 as its child. Some relay nodes may only have a parent node, such as... Figure 1 Relay node 2 in the system has only one parent node, namely relay node 1.

[0063] In this embodiment of the application, the migration of a relay node refers to a change in the parent node of the relay node. The parent node of a relay node may be an anchor node or another relay node.

[0064] In this embodiment, data transmission (i.e., data packet transmission) during relay node migration is considered. The scenario of relay node migration includes three possible scenarios, which are described below. Figure 4a , 4b The schematic network structure shown in 4c will be explained below, in which, Figure 4a , 4bThe curve to the left of 4c represents the data transmission path before migration, and the curve to the right represents the data transmission path after migration. The one-way arrow in the figure represents the migration of relay node a, that is, relay node a is the relay node that has been migrated, relay node 1 is the parent node of relay node a before migration, and relay node 2 is the parent node of relay node a after migration.

[0065] The first scenario involves the migration of Intra-donor-CU (the interior of the anchor node's centralized unit) / Intra-donor-DU (the interior of the anchor node's distributed unit), where the internal migration occurs when the anchor node's centralized / distributed unit remains unchanged: e.g. Figure 4a As shown, when relay node a migrates, the centralized unit and the distributed unit of the anchor node it is connected to do not change.

[0066] The second scenario: migration of Intra-donor-CU / inter-donor-DU (outside the distribution unit of the anchor node), where external migration refers to changes that have occurred, such as... Figure 4b When relay node a migrates, the lumped cell of the anchor node it is connected to remains unchanged, but the distributed cell of the anchor node it is connected to changes, such as... Figure 4b As shown, the distribution unit of the anchor node connected to relay node a before migration is anchor node distribution unit 1, and the distribution unit of the anchor node connected to after migration is anchor node distribution unit 2.

[0067] The third scenario: migration of the Inter-donor-CU (outside the concentrated element of the anchor node), which indicates a change in the entire anchor node: such as... Figure 4c When relay node a migrates, both the concentrated cell and the distributed cell of the anchor node it connects to change, such as... Figure 4c As shown, the centralized unit of the anchor node connected to relay node a before migration is the centralized unit of anchor node 1, and the distributed unit of the anchor node connected to it is the distributed unit of anchor node 1. The centralized unit of the anchor node connected to relay node a after migration is the centralized unit of anchor node 2, and the distributed unit of the anchor node connected to it is the distributed unit of anchor node 2.

[0068] During the migration process described above, other nodes connected to relay node a (relay nodes b and c) may also migrate. Furthermore, before the relay node migration, the transmission path for user data (i.e., user data packets) is the source path; after the migration, the transmission path is the destination path. In practice, the source and destination paths may share the same nodes. For example, in the path to relay node b, relay node a may be present in both the source and destination paths.

[0069] To facilitate the description and understanding of the embodiments, the technical terms that may be involved in the optional embodiments below will be explained first.

[0070] Nodes that have migrated: This refers to relay nodes in the network whose parent nodes have changed (e.g., node A, meaning the parent node of node A has changed), or nodes whose connection relationships in the network have changed due to the change in the connection of node A, such as child nodes of node A or child nodes of child nodes of node A, etc.

[0071] First Node: This node can be a relay node, a distribution unit functional part of a relay node, a mobile terminal functional part of a relay node, or a distribution unit of an anchor node (this anchor node can be the anchor node connected to before the configuration update or before the migration of the node, or the anchor node connected to after the configuration update or after the migration of the node). In one embodiment, this node can be the node that has migrated, that is, the parent node connected to this node has changed, such as... Figure 4a , Figure 4b and Figure 4c In another embodiment, the node can be a child node of the migrated relay node, which accesses the network through the migrated relay node, and the node is directly or indirectly connected to the migrated relay node (indirect connection means connected to the migrated relay node through one or more nodes), such as... Figure 4a , Figure 4b and Figure 4c In the example, relay nodes b and c are connected. Relay node b is directly connected to relay node a, and relay node c is indirectly connected to relay node a. In another embodiment, the node can be the parent node directly connected to or indirectly connected to the relay node that is migrating (indirect connection refers to a parent node connected through one or more nodes), such as... Figure 4a , Figure 4b and Figure 4c Relay nodes 1 and 2 in the system.

[0072] Second Node: This node is an anchor node, or a centralized unit of an anchor node, or the control plane portion of a centralized unit of an anchor node, or the user plane portion of a centralized unit of an anchor node. When a relay node migrates, the second node can be a node connected before the migration or a node connected after the migration. That is, the second node can be an anchor node connected to the relay node before the migration, or a centralized unit of an anchor node, or the control plane portion of a centralized unit of an anchor node, or the user plane portion of a centralized unit of an anchor node, i.e., an anchor node or a component of an anchor node on the source path. It can also be an anchor node connected to the relay node after the migration, or a centralized unit of an anchor node, or the control plane portion of a centralized unit of an anchor node, or the user plane portion of a centralized unit of an anchor node, i.e., an anchor node or a component of an anchor node on the target path.

[0073] Second node a: This node is an anchor node, or a centralized unit of an anchor node, or the control plane portion of a centralized unit of an anchor node, or the user plane portion of a centralized unit of an anchor node. When a relay node migrates, this second node a is the anchor node connected after the migration. Figure 4c Anchor node 2, or the centralized unit of anchor node 2, or the control surface portion of the centralized unit of anchor node 2, or the user surface portion of the centralized unit of anchor node 2.

[0074] First node a: This node is a child node of the relay node that underwent the migration, such as... Figure 4a , Figure 4b and Figure 4c The relay node is either b or c. This node can be a relay node, a distribution unit function part of a relay node, or a mobile terminal function part of a relay node. This node accesses the network through the relay node that has migrated, and this node is directly or indirectly connected to the relay node that has migrated (indirect connection means being connected to the relay node that has migrated through one or more nodes).

[0075] First node b: The parent node directly or indirectly connected to by the relay node that is migrating (indirect connection refers to a parent node connected through one or more nodes), such as... Figure 4a , Figure 4b and Figure 4c The relay node is either 1 or 2. This node can be a relay node, a distribution unit function of a relay node, or a mobile terminal function of a relay node.

[0076] The third node: This node can be a relay node that has migrated, a child node of the node that has migrated, or a parent node of the node that has migrated. The fourth node is the target receiving node (also called the destination receiving node) of the user data packets corresponding to the third node. Of course, it can also be the distribution unit function part of the node or the mobile terminal function part of the node. As an example, the third node can be the node that has migrated.

[0077] The fourth node: This node is the target receiving node for user data packets corresponding to the third node. The fourth node can be the target receiving node for data packets stored or cached by the third node (data packets cached due to migration). When node migration occurs in the network, some user data packets may not have been sent to the destination receiving node before the migration. These packets could be cached (stored) in the third node, and the destination receiving node corresponding to these packets is this fourth node. As an example, this fourth node can be a child node of the node undergoing migration.

[0078] Fifth node: This node can be the fourth node, or other nodes on the transmission path of the third and fourth nodes.

[0079] It should also be noted that the "node" involved in the embodiments of this application can be a relay node, or the distribution unit functional part of a relay node, or the mobile terminal functional part of a relay node. It can be an anchor node, the central unit of an anchor node, the control plane part of the central unit of an anchor node, or the user plane part of the central unit of an anchor node. It may also be a user terminal. In some application scenarios or in future communication development, the user terminal may also serve as a node in the network.

[0080] In addition, the transmission in the embodiments of this application may include sending and / or receiving, and the "connection" involved in the description of the embodiments of this application may be a direct connection or an indirect connection.

[0081] The following describes various optional embodiments of this application from four aspects, in conjunction with the accompanying drawings. These optional embodiments can be implemented individually or in combination. Furthermore, the user data packets described in the optional embodiments of this application can be uplink data packets or downlink data packets. Although some embodiments may only illustrate uplink or downlink data packets, those skilled in the art will understand that, based on the descriptions using uplink data packets as examples in the optional embodiments of this application, corresponding implementation schemes for uplink data packets can be readily conceived. Similarly, based on the descriptions using downlink data packets as examples in the embodiments, those skilled in the art can also conceive of embodiments corresponding to uplink data packets.

[0082] ■ First aspect: Packet loss avoidance mechanisms in relay networks

[0083] In a relay network, relay nodes may migrate (i.e., their connected parent nodes change). During this process, some data packets on the source path may not be sent to the destination node (i.e., the target receiving node). For example, the destination node may be a migrated relay node, a child node of a migrated relay node, an anchor node directly or indirectly connected to a migrated relay node, a central unit of an anchor node, the control plane portion of a central unit of an anchor node, or the user plane portion of a central unit of an anchor node. This data may be lost due to the migration of the relay node. To avoid data packet loss, embodiments of this application provide a communication method that can be implemented between an anchor node (or a central unit of an anchor node, or the control plane portion of a central unit of an anchor node, or the user plane portion of a central unit of an anchor node) and a relay node. That is, the method is an interaction process between an anchor node and a relay node, and the method can be implemented between the aforementioned first node and second node.

[0084] Figure 5 The diagram shows a flowchart of a communication method provided in an optional embodiment of this application. The method may include steps 1-1 and / or 1-2. Steps 1-1 and 1-2 may be implemented individually or in combination. As an optional embodiment, step 1-1 may be executed first, followed by step 1-2. As another embodiment, step 1-2 may be executed first, followed by step 1-1.

[0085] like Figure 5 As shown, the process of this communication method may include the following steps:

[0086] Step 1-1: The second node sends a first message to the first node (also known as a first configuration message or other names, such as the first message sent after the second node receives the second message (which will be explained in detail later), and this first message can also be called a response message). The purpose of this message is to configure the first node for the transmission and / or storage (or caching) of user data packets. Another purpose of this message is to notify the first node of the enabling of the information sent by the second node (such as enabling the transmission of the information contained in the second message). The transmission can be data transmission (data packet transmission) and / or data reception (data packet reception).

[0087] Based on this optional implementation scheme, the second node can send a first message to the first node, informing the first node of relevant information about data packet transmission and / or storage. The first node can then determine whether to store or cache data packets, and how to transmit them, based on the information in the first message. This avoids the problem that data packets cannot be sent to the destination receiving node on the source path due to the migration of relay nodes on the source path.

[0088] Optionally, the first node may include at least one of the following:

[0089] The relay node that has migrated; the distribution unit portion of the relay node that has migrated; the mobile terminal portion of the relay node that has migrated; the child node of the relay node that has migrated; the distribution unit portion of the child node of the relay node that has migrated; the mobile terminal portion of the child node of the relay node that has migrated; the parent node of the relay node that has migrated; the distribution unit portion of the parent node of the relay node that has migrated; the mobile terminal portion of the parent node of the relay node that has migrated.

[0090] The second node may include at least one of the following:

[0091] Anchor node; centralized unit of anchor node; control plane portion of centralized unit of anchor node; user plane portion of centralized unit of anchor node; wherein, the anchor node here is the anchor node connected to the relay node before migration or the anchor node connected after migration.

[0092] It should be noted that the above process is based on the assumption that the first node has migrated. However, in practice, the above process can also be applied when the first node has not migrated. In this case, the first node may include at least one of the following:

[0093] Relay node; Distribution unit portion of relay node; Mobile terminal portion of relay node; Child node of relay node; Distribution unit portion of child node of relay node; Mobile terminal portion of child node of relay node; Parent node of relay node; Distribution unit portion of parent node of relay node; Mobile terminal portion of parent node of relay node.

[0094] The second node may include at least one of the following:

[0095] Anchor node; centralized element of anchor node; control surface portion of centralized element of anchor node; user surface portion of centralized element of anchor node.

[0096] Optionally, the aforementioned first message may be a first message corresponding to at least one user data packet, and the first message may include at least one of the following:

[0097] The first information is used to indicate whether a fourth information will be sent, wherein the fourth information is used to indicate the data packet transmission status;

[0098] The second piece of information is used to indicate whether to store / cache data packets;

[0099] The third piece of information is used to indicate the transmission address information corresponding to the data packet, that is, the transmission address information related to the data packet;

[0100] The fourth information is used to indicate the data packet transmission status; optionally, the fourth information can be used by the first node to determine the data packets to be transmitted and / or the transmission method of the data packets, such as which data packets to transmit and what transmission rate to use.

[0101] The seventh piece of information is used to indicate node migration event notification information.

[0102] The first piece of information can also be called the data packet transmission status enable information, such as indicating whether the second node will send data packet transmission status information, such as whether it will send or not. Taking the upstream data packet as an example, this information is the upstream data packet transmission status enable information.

[0103] The second information can also be called the indication information for caching (storing) data packets (such as the indication information for caching uplink data packets). The function of this indication information is to indicate whether the first node needs to cache (store) uplink data packets, such as indicating whether caching (storing) is required or not.

[0104] The third information, also known as address-related information, indicates information about the address used to transmit user data.

[0105] The fourth information, also known as Data Delivery Status (DDS), indicates the status of data packets transmitted (received and / or sent) by the second node. In one embodiment, if the fourth information pertains to uplink data packets, it is the uplink data packet delivery status information, such as UL DDS. In another embodiment, if the fourth information pertains to downlink data packets, it is the downlink data packet delivery status information, such as DL DDS.

[0106] It should be noted that when the aforementioned first message contains multiple pieces of information (which can include multiple pieces of information from the first, second, third, fourth, and seventh information, or multiple pieces of information from at least one of the first, second, third, fourth, and seventh information), these multiple pieces of information can be sent together, sent separately, or sent in multiple installments (each time one or more pieces of information can be sent). That is, the multiple pieces of information can be sent synchronously or asynchronously. Optionally, the information in the first message and the information in the second message described below can also be sent interactively. For example, the second node sends information 'a' (one or more pieces of information that the first message can contain) from the first message to the first node, the first node sends information 'b' (one or more pieces of information that the second message can contain) from the second node based on information 'a', and the second node can then send other information from the first message to the first node based on this information.

[0107] Furthermore, the method of indicating the information to be indicated by each message can be explicit or implicit. That is, the information to be indicated can be directly communicated through a message, or it can be implicitly communicated through a pre-agreed method. For example, taking the second message mentioned above as an example, the second message can optionally be a direct indication of whether to cache or not. For example, message "1" represents caching, and message "0" represents not caching. Other methods can also be used to indicate this. For example, if the first message indicates that the fourth message will be sent, it can implicitly indicate that caching should be performed. If the first message indicates that the fourth message will not be sent, it means that caching should be performed implicitly.

[0108] In an optional embodiment of this application, at least one of the first message, fourth message, or seventh message described above is further used to indicate whether to cache data packets.

[0109] In other words, the second piece of information mentioned above may include at least one of the following:

[0110] First information; Fourth information; Cache indication information; Node migration event notification information (Seventh information).

[0111] In other words, the content indicated by one or more of the first, fourth, and seventh messages can be implicitly implemented in a pre-agreed manner to indicate the content to be indicated by the second message. For example, regarding the fourth message, if the first message contains the fourth message, it means that caching is required; if the first message does not contain the fourth message, caching is not required. The caching indication information uses a direct indication method to indicate whether caching is required. The node migration event notification information is used to indicate that a relay node migration will occur on the source path where the first node is located. This information can implicitly indicate whether caching is required. For example, if the first message contains this notification information, it means that caching is required.

[0112] In an optional embodiment of this application, the transmission address related information corresponding to the above-mentioned data packet includes at least one of the following information used by the first node and / or the second node to transmit the data packet: BAP address information, IP address information, and tunnel identification information.

[0113] In other words, the transmission address information corresponding to the above data packet may include at least one of the following:

[0114] Address information used by the first node to transmit data packets; address information used by the second node to transmit data packets; tunnel identification information corresponding to the first node; tunnel identification information corresponding to the second node.

[0115] Among these, the address information can include, but is not limited to, BAP (Backhaul Adaptation Protocol) addresses and IP (Internet Protocol) addresses. Taking the address information used by the first node to transmit data packets as an example, this address information can be the BAP address and / or IP address used by the first node to send / receive data packets. The tunnel identification information mentioned above is TEID (tunnel endpoint identifier), which is the identification information of the tunnel used to transmit data packets.

[0116] In optional embodiments of this application, the fourth information may include at least one of the following:

[0117] The second node expects the following information to be transmitted in the data packet;

[0118] Information relating to at least one first data packet, wherein the first data packet includes at least one of the following:

[0119] Lost data packets; successfully transmitted data packets (also known as successfully transmitted non-retransmitted data packets or successfully transmitted initial data packets); successfully transmitted retransmitted data packets;

[0120] Untransmitted data packets (also known as untransmitted non-retransmitted data packets or untransmitted initial transmission data packets); untransmitted retransmitted data packets.

[0121] The aforementioned transmission expectation information refers to the transmission-related information that the second node expects / desirs when the first node transmits data packets with the second node. Optionally, this transmission expectation information may include, but is not limited to, at least one of the following: expected buffer size (expected amount of transmitted data) and expected transmission rate. Taking the upstream data packet as an example, the aforementioned information related to at least one first data packet may include one or more of the following: information related to lost data packets, information related to successfully received data packets, information related to unsuccessfully received data packets (initial transmission data packets), information related to successfully received retransmission data packets, and information related to unsuccessfully received retransmission data packets.

[0122] In an optional embodiment of this application, the information relating to at least one first data packet includes at least one of the following:

[0123] At least one packet identification information for the first data packet;

[0124] Information on the number of the first data packets transmitted consecutively;

[0125] At least one transmission status indication information for the first data packet.

[0126] The aforementioned data packet identification information uniquely identifies a data packet. Furthermore, this identification information can indicate information about data packets associated with the data packet corresponding to it. For example, the identification information could be the sequence number of the data packet. When transmitted data packets use a sequential numbering method, a data packet's sequence number represents that data packet. Based on this data packet, information about data packets associated with it can also be obtained. For instance, if a data packet's sequence number is the largest sequence number of consecutively numbered data packets, then it can be known that this data packet is the last data packet in a group of data packets. Optionally, the identification information of a data packet could be its PDCP SN (sequence number), NR-U (New Radio Unlicensed) sequence number, etc.

[0127] Optionally, at least one transmission status indication information for the first data packet includes: bitmap information indicating whether the first data packet was lost or successfully received. For a data packet, the aforementioned transmission status indication information refers to indication information characterizing whether the data packet was successfully transmitted. For example, taking a lost data packet as an example, the indication information can indicate whether the data packet was lost. For instance, a bit can be used to indicate a data packet, such as a bit value of "1" indicating that it was lost and "0" indicating that it was not lost.

[0128] In an optional embodiment of this application, the data packet identification information of the at least one first data packet includes at least one of the following:

[0129] The identifier information of the last transmitted data packet in the first data packet (theoretically the last transmitted, that is, if the data packets are sent in order, the last one here refers to the theoretically last one sent in a group of data packets sent in order). Taking the sequence number of the data packet as the identifier information and the data packet as an uplink data packet as an example, the identifier information can be one or more of the following: the termination sequence number of a lost data packet, the termination sequence number of a successfully received data packet, the termination sequence number of a data packet that was not successfully received, the termination sequence number of a successfully received retransmitted data packet, and the termination sequence number of a retransmitted data packet that was not successfully received.

[0130] The identification information of the first (theoretically) transmitted data packet in the first data packet, for example, taking the previous data packet as an example, may include one or more of the following: the starting sequence number of the lost data packet, the starting sequence number of the successfully received data packet, the starting sequence number of the unsuccessfully received data packet, the starting sequence number of the successfully received retransmitted data packet, and the starting sequence number of the unsuccessfully received retransmitted data packet.

[0131] The identifier information of the first (theoretically) transmitted data packet in the first data packet of continuous transmission, such as the smallest sequence number of successfully received data packets in order, the smallest sequence number of unsuccessfully received data packets in order, and the smallest sequence number of retransmitted data packets that were unsuccessfully received in order. For example, taking a series of successfully received data packets (i.e., a group of successfully received data packets with consecutive sequence numbers) as an example, according to the sequence number of the data packets, if the successfully received sequence numbers are data packet 1, data packet 2, and data packet 3, then the identifier information is the sequence number of data packet 1.

[0132] The identification information of the last (theoretically) transmitted data packet in the first data packet of continuous transmission, such as the maximum sequence number of lost data packets, the maximum sequence number of successfully received data packets, and the maximum sequence number of successfully received retransmitted data packets. Taking a lost data packet with consecutive sequence numbers as an example, this identification information could be the maximum sequence number of this group of lost data packets.

[0133] To better understand and explain the information that may be carried in the first message mentioned above, the following explanation will use the upstream data packet as an example to illustrate the information that may be included in the first message.

[0134] Between the first node and the second node, it may be necessary to transmit data packets for multiple radio bearers. For one or more radio bearers, the aforementioned first message includes at least one of the following information:

[0135] ■ Data packet transmission status enable information (corresponding to the first information above). This information indicates whether the second node will send data packet transmission status information, i.e., whether it will send it or not. In an optional embodiment, for uplink data packets, if the second node will send data packet transmission status information (which may be uplink data packet transmission status information) to the first node, then the first node can start caching the uplink data packets it sends; otherwise, the first node does not need to cache the uplink data packets it sends.

[0136] ■ Indication information for caching data packets (corresponding to the second information above). The purpose of this information is to indicate whether the first node needs to cache data packets. If caching is required, or if caching is not required, the cached data packets can be uplink data packets and / or downlink data packets.

[0137] ■ Address-related information (corresponding to the third information above), which indicates information related to the address used to transmit user data, and includes at least one of the following:

[0138] ■ Address information on the second node side (corresponding to the address information used by the second node to transmit data packets), such as BAP address, IP address

[0139] ■ Tunnel identification information on the second node side (corresponding to the tunnel identification information of the second node), such as tunnel endpoint identifier (TEID).

[0140] ■ Address information on the first node side (corresponding to the address information used by the first node to transmit data packets), such as BAP address or IP address. This information must include at least one of the following:

[0141] ◆Old address information, such as old BAP addresses and old IP addresses. These old addresses can be the address information used before the first node configuration update, or the address information used before the first node was migrated.

[0142] ◆ New address information, such as a new BAP address or a new IP address. This new address can be the address information used after the first node's configuration is updated, or it can be the address information used after the first node has migrated. In one embodiment, when the first node retransmits a lost or unsuccessfully received data packet, it updates the address on the first node side contained in the packet with this new address information.

[0143] ■ Tunnel identification information on the first node side (tunnel identification information corresponding to the second node), such as tunnel endpoint identifier (TEID).

[0144] ■ Data packet transmission status (DDS) information (corresponding to the fourth information above). For uplink data packets, this information serves to indicate the status of the second node receiving the uplink data packet, thereby assisting the first node in sending the uplink data packet; this information includes at least one of the following:

[0145] ■ Expected buffer size: This information indicates the amount of data the second node expects to receive. In one embodiment, this data size is the amount of data the second node expects to receive after a certain data packet (e.g., the data packet could be the data packet with the largest sequence number among the sequentially received data packets).

[0146] ■ Expected data rate: This information indicates the expected data transmission rate of the second node.

[0147] ■ Information related to lost data packets, which serves to indicate the lost data packets known to the second node, and includes at least one of the following:

[0148] ◆The starting sequence number of the lost data packet, such as PDCP SN, NR-U sequence number. In one embodiment, the starting sequence number is the smallest sequence number of a group of lost data packets with consecutive sequence numbers. In another embodiment, the starting sequence number is the sequence number of the first lost data packet in a group of data packets.

[0149] ◆The termination sequence number of the lost data packet, such as PDCP SN, NR-U sequence number. In one embodiment, the termination sequence number is the largest sequence number of a group of lost data packets with consecutive sequence numbers. In another embodiment, the termination sequence number is the sequence number of the last lost data packet in a group of data packets.

[0150] ◆ A bitmap indicating whether a data packet was lost. Each bit in this bitmap indicates whether its corresponding data packet was lost; for example, "1" indicates that it was lost, and "0" indicates that it was not lost.

[0151] In one embodiment, the lost data packets may contain multiple sets of data packets with consecutive sequence numbers. For each set of consecutive sequence numbers, at least one of the above information (such as the start sequence number of the lost data packet, the end sequence number of the lost data packet, and bitmap information indicating whether the data packet was lost) can be provided.

[0152] ■ Information related to successfully received data packets. This information indicates that the second node has correctly received the data packets. The data packets can be newly transmitted data packets or retransmitted data packets by the first node. This information includes at least one of the following:

[0153] ◆The maximum sequence number of the successfully received data packets, such as PDCP SN, NR-U sequence number, etc. In one embodiment, the successfully received data packets are a group of successfully received data packets with consecutive sequence numbers.

[0154] ◆The starting sequence number of a successfully received data packet, such as PDCP SN or NR-U sequence number. In one embodiment, the starting sequence number is the smallest sequence number of a group of successfully received data packets with consecutive sequence numbers. In another embodiment, the starting sequence number is the sequence number of the first successfully received data packet in a group of data packets.

[0155] ◆The termination sequence number of a successfully received data packet, such as PDCP SN or NR-U sequence number. In one embodiment, the termination sequence number is the largest sequence number of a group of successfully received data packets with consecutive sequence numbers. In another embodiment, the termination sequence number is the sequence number of the last successfully received data packet in a group of data packets.

[0156] ◆ A bitmap indicating whether a data packet was successfully received. Each bit in this bitmap indicates whether its corresponding data packet was successfully received, such as "1" indicating successful reception and "0" indicating unsuccessful reception, or "1" indicating unsuccessful reception and "0" indicating successful reception.

[0157] In one embodiment, a successfully received data packet may contain multiple sets of data packets with consecutive sequence numbers. For each set of consecutive sequence numbers, at least one of the above information (such as the start sequence number of the successfully received data packet, the end sequence number of the successfully received data packet, and bitmap information indicating whether the data packet was successfully received) can be provided.

[0158] ■ Information related to data packets that were not successfully received. This information indicates that the second node did not receive the data packets correctly. The data packets can be newly transmitted data packets or retransmitted data packets by the first node. This information includes at least one of the following:

[0159] ◆The smallest sequence number of the data packets that were not successfully received in order, such as PDCP SN, NR-U sequence number, etc. In one embodiment, the data packets that were not successfully received in order are a group of data packets that were not successfully received and have consecutive sequence numbers.

[0160] ◆The starting sequence number of the unreceived data packet, such as PDCP SN, NR-U sequence number. In one embodiment, the starting sequence number is the smallest sequence number of a group of unreceived data packets with consecutive sequence numbers. In another embodiment, the starting sequence number is the sequence number of the first unreceived data packet in a group of data packets.

[0161] ◆ The termination sequence number of an unreceived data packet, such as PDCP SN or NR-U sequence number. In one embodiment, the termination sequence number is the largest sequence number of a group of unreceived data packets with consecutive sequence numbers. In another embodiment, the termination sequence number is the sequence number of the last unreceived data packet in a group of data packets.

[0162] ◆ Bitmap information indicating whether a data packet was successfully received. Each bit in the bitmap indicates whether its corresponding data packet was successfully received. For example, "1" indicates unsuccessful reception and "0" indicates successful reception, or "1" indicates successful reception and "0" indicates unsuccessful reception.

[0163] In one embodiment, a data packet that was not successfully received may contain multiple sets of data packets with consecutive sequence numbers. For each set of consecutive sequence numbers, at least one of the above information (such as the start sequence number of the unsuccessfully received data packet, the end sequence number of the unsuccessfully received data packet, and bitmap information indicating whether the data packet was successfully received) can be provided.

[0164] ■ Information related to successfully received retransmitted data packets. This information serves to indicate that the second node has correctly received the retransmitted data packets. This information includes at least one of the following:

[0165] ◆The maximum sequence number of successfully received retransmitted data packets in order, such as PDCP SN, NR-U sequence number, etc. In one embodiment, successfully received retransmitted data packets in order are a group of successfully received retransmitted data packets with consecutive sequence numbers.

[0166] ◆The starting sequence number of a successfully received retransmitted data packet, such as the PDCP SN or NR-U sequence number. In one embodiment, this starting sequence number is the smallest sequence number of a group of successfully received retransmitted data packets with consecutive sequence numbers. In another embodiment, this starting sequence number is the sequence number of the first successfully received retransmitted data packet in a group of retransmitted data packets.

[0167] ◆The termination sequence number of a successfully received retransmitted data packet, such as a PDCP SN or NR-U sequence number. In one embodiment, this termination sequence number is the largest sequence number of a group of successfully received retransmitted data packets with consecutive sequence numbers. In another embodiment, this termination sequence number is the sequence number of the last successfully received retransmitted data packet in a group of retransmitted data packets.

[0168] ◆ A bitmap indicating whether a retransmitted data packet was successfully received. Each bit in this bitmap indicates whether its corresponding retransmitted data packet was successfully received; for example, "1" indicates that the packet was lost, and "0" indicates that it was not lost.

[0169] In one embodiment, a successfully received retransmitted data packet may contain multiple sets of data packets with consecutive sequence numbers. For each set of retransmitted data packets with consecutive sequence numbers, at least one of the above information (such as the start sequence number of the successfully received retransmitted data packet, the end sequence number of the successfully received retransmitted data packet, and bitmap information indicating whether the retransmitted data packet was successfully received) can be provided.

[0170] ■ Information related to retransmitted data packets that were not successfully received. This information serves to indicate that the second node did not receive the retransmitted data packets correctly. This information includes at least one of the following:

[0171] ◆The smallest sequence number of the retransmitted data packets that were not successfully received in order, such as PDCP SN, NR-U sequence number, etc. In one embodiment, the retransmitted data packets that were not successfully received in order are a group of retransmitted data packets that were not successfully received and have consecutive sequence numbers.

[0172] ◆The starting sequence number of the retransmitted data packet that was not successfully received, such as PDCP SN, NR-U sequence number. In one embodiment, the starting sequence number is the smallest sequence number of a group of retransmitted data packets that were not successfully received and have consecutive sequence numbers. In another embodiment, the starting sequence number is the sequence number of the first retransmitted data packet that was not successfully received in a group of retransmitted data packets.

[0173] ◆ The termination sequence number of the unsuccessfully received retransmitted data packet, such as PDCP SN, NR-U sequence number. In one embodiment, the termination sequence number is the largest sequence number of a group of unsuccessfully received retransmitted data packets with consecutive sequence numbers. In another embodiment, the termination sequence number is the sequence number of the last unsuccessfully received retransmitted data packet in a group of retransmitted data packets.

[0174] ◆ Bitmap information indicating whether retransmitted data packets were successfully received. Each bit in the bitmap indicates whether its corresponding retransmitted data packet was successfully received. For example, "1" indicates unsuccessful reception and "0" indicates successful reception, or "0" indicates unsuccessful reception and "1" indicates successful reception.

[0175] In one embodiment, a retransmitted data packet that was not successfully received may contain multiple sets of data packets with consecutive sequence numbers. For each set of retransmitted data packets with consecutive sequence numbers, at least one of the above information (such as the start sequence number of the retransmitted data packet that was not successfully received, the end sequence number of the retransmitted data packet that was not successfully received, and bitmap information indicating whether the retransmitted data packet was successfully received) can be provided.

[0176] After receiving the first message, the first node can transmit and store data. For example, the first node can start caching the data packets it has sent out, and can retransmit lost data packets or data packets that were not successfully received by the second node based on the first message.

[0177] Based on one or more indications carried in the first message, the first node can determine whether it needs to cache data packets, and can also determine the data packets that need to be transmitted based on the first message. For example, the first node can send data packets that the second node has not received to the second node based on the first message.

[0178] As another optional embodiment of the first aspect, the communication method may further include:

[0179] Step 1-2: The first node sends a second message (also called a second configuration message, notification message, or other names; optionally, if the second message is sent based on the receipt of the first message, the second message can also be called a response message) to the second node. This message is used to notify the second node of information about the transmission (sending and / or receiving) and / or storage of user data packets by the first node. That is, the function of this message is to indicate the data transmission and / or storage at the relay node.

[0180] Optionally, with the second node as the execution subject, step 1-2 can be described as: receiving the second message sent by the first node.

[0181] In an optional embodiment of this application, the second message is a response message to the first message, or the first message is a response message to the second message.

[0182] In other words, when implementing the solution provided in this application, step 1-1 can be executed first, followed by step 1-2, or step 1-2 can be executed first, followed by step 1-1. Of course, steps 1-1 and 1-2 can be implemented separately.

[0183] In an optional embodiment of this application, the second message may include at least one of the fifth information and information relating to at least one second data packet.

[0184] The fifth message is used to notify the second node whether it needs to send the fourth message, which indicates the data packet transmission status. Optionally, the fifth message can also be called a polling indication message for data transmission status information, which notifies the second node whether it needs to send data transmission status information to the first node. Optionally, in this case, the first message can be a response to the second message. That is, the first node first sends a polling indication message for uplink data transmission status information to the second node, and then the second node sends a first message back to the first node based on the polling indication message for uplink data transmission status information.

[0185] The aforementioned second data packet may include at least one of the following:

[0186] Data packets that the first node needs to send to the second node; data packets cached (stored) by the first node;

[0187] The data packet received by the first node;

[0188] Retransmit the data packet.

[0189] The retransmitted data packets can be uplink retransmitted data packets and / or downlink retransmitted data packets.

[0190] In an optional embodiment of this application, the information relating to at least one second data packet includes at least one of the following:

[0191] At least one data packet needs to be transmitted from the first node to the second node. Optionally, this information can be used by the second node to feed back fourth information, which is used to indicate the data packet transmission status.

[0192] At least one second data packet identification information, optionally, which is used to indicate to the second node the information of the data packets cached by the first node;

[0193] The number of second data packets can optionally be used to indicate to the second node the information of the data packets cached by the first node;

[0194] At least one indication of whether a second data packet is cached; optionally, this information may indicate to the second node information about the data packets cached by the first node.

[0195] At least one indication information indicating whether a second data packet is a retransmission data packet. Optionally, this information can be used to indicate to the second node whether the data packet corresponding to the indication information is a retransmission data packet, such as to notify the second node whether the data packet it received is a retransmission data packet.

[0196] In other words, taking the upstream data packet as an example, the data packet that at least one first node needs to transmit to the second node can be a data packet that at least one first node needs to retransmit to the second node, such as a lost data packet or a data packet that the second node failed to receive. The data packet identification information can be the sequence number information of the data packet (such as the minimum or maximum sequence number), such as PDCP SN, NR-U sequence number, etc. The indication information of the data packet identification information of at least one second data packet can be the indication information of the minimum sequence number of the second data packet. Taking the data packets buffered by the first node as an example, the number of second data packets refers to the number of data packets buffered by the first node. For a data packet, the above-mentioned indication information of whether it is a retransmitted data packet is used to indicate whether the data packet is a retransmitted data packet. For example, this indication information of a data packet can be indicated by a single bit. If the value of the bit is "1", it indicates that the data packet corresponding to the characteristic bit is a retransmitted data packet; if the value of the characteristic bit is "0", it indicates that the data packet corresponding to the characteristic bit is not a retransmitted data packet.

[0197] In an optional embodiment of this application, the second message is a response to the first message, and the first message includes indication information of the address information used by the first node to transmit data packets; optionally, the address information contained in the data packets that at least one first node needs to transmit (e.g., send) to the second node may include the aforementioned address information. For example, if the first message includes the aforementioned address information on the first node side, the information on the first node side in the data packets sent by the first node to the second node may be the address information on the first node side indicated in the second message.

[0198] To better understand and explain the second message mentioned above, the following detailed explanation will use an upstream data packet as an example. Optionally, this message may include at least one of the following information:

[0199] ■ Data packet, which is the data packet that the first node needs to send to the second node. Optionally, the data packet may also contain the sequence number information of the data packet, such as PDCP SN, NR-U sequence number; in an optional embodiment, the data packet may be a retransmitted data packet (such as a lost data packet indicated in step 1-1, or a data packet that was not successfully received). Optionally, the second message may be a response message to the first message. The first message may contain the address information of the first node. In this case, for the data packet that the first node needs to send to the second node, the first node can update the address information of the first node contained in the data packet to the new address configured in step 1-1 above (see "Address information of the first node" in "Information related to address" included in step 1-1 above).

[0200] ■ Polling indication information for uplink data transmission status (corresponding to the fifth information above). The purpose of this information is to notify the second node whether it needs to send data transmission status information to the first node.

[0201] ■ Information related to cached data packets (corresponding to the information related to at least one cached data packet mentioned above), which is used to indicate information related to data packets cached at the first node, and includes at least one of the following:

[0202] ■ The minimum sequence number of the cached data packets, such as the PDCP SN.

[0203] ■ The minimum sequence number indication information indicates that the sequence number of the data packet contained in the second configuration message is the minimum sequence number among the data packets cached at the first node.

[0204] ■ The maximum sequence number of the cached data packets, such as PDCP SN

[0205] ■ This is a bitmap information indicating the cached data packets. Each bit in the bitmap indicates whether its corresponding data packet has been cached, such as "1" indicating that it has been cached and "0" indicating that it has not been cached.

[0206] ■ Information related to the received data packet (corresponding to the relevant information of the data packet received by at least one of the first nodes mentioned above), wherein the received data packet is a data packet sent by the user (i.e., UE) to the first node, and the information includes at least one of the following:

[0207] ■ Maximum sequence number of data packets: The maximum sequence number of data packets received from the user.

[0208] ■ Retransmission data packet indication information. The purpose of this information is to indicate whether the above "data packet" is a retransmission data packet. If it is, it means that the above "data packet" has been transmitted before. Otherwise, it means that the above "data packet" is being transmitted for the first time.

[0209] As an optional embodiment of this application, after receiving the second message, the second node can determine the storage and transmission status of user data in the first node and decide to send its own data status information. For example, the second node can generate the content in the UL DDS based on the data packets cached at the first node. For example, if a data packet is not cached at the first node, the second node will not notify the first node whether the data packet was lost or not successfully received, even if it has not received the data packet. Another example is that the second node can determine when to send the UL DDS based on the information contained in the second message. For example, the UL DDS will only be sent after the second node has correctly received all data packets before the data packet with the smallest sequence number cached by the first node. Yet another example is that the first message will be sent after the second node receives the polling information in the second message.

[0210] Based on the aforementioned second message, the second node can determine the relevant information of the first node corresponding to at least one second data packet, thereby enabling data interaction with the first node based on the second message. For example, the second message may contain indication information of uplink data packets cached at the first node, and the second node can determine the data cached at the first node based on this indication information, thus knowing that the data packets cached at the first node can be transmitted.

[0211] As described above, steps 1-1 and 1-2 in the above process can be executed independently or sequentially. The first configuration message can be a control plane message (such as an F1AP message, a UE Context Setup / Modification Request message, an RRC message, or a newly defined message), a user plane message (such as an F1-U message, a DL USER DATA message, or a newly defined message), or other messages. The second configuration message can be a control plane message (such as an F1AP message, a UE Context Setup / Modification Response message, an RRC message, or a newly defined message), a user plane message (such as an F1-U message, a DL DATA DELIVERY STATUS message, or a newly defined message), or other messages.

[0212] Furthermore, steps 1-1 and 1-2 above are described using an interaction between the first node and the second node. It is understood that in the above optional embodiments, steps involving interaction between the first node and the second node, such as the second node sending a first message to the first node, or the second node sending a second message to the first node, can be described from either the first node's or the second node's perspective. That is, the description can be based on the first node as the executing entity of each optional implementation scheme, or it can be based on the second node as the executing entity.

[0213] Optionally, with the first node mentioned above as the execution entity, the communication method may include:

[0214] Send a second message, wherein the second message is used to notify the second node of the first node's transmission and / or storage (or caching) of user data packets.

[0215] Optionally, the method may further include: receiving a first message, wherein the first message is used to instruct the first node to transmit and / or store (or cache) user data packets.

[0216] In this context, the first message can be a response to the second message, or the second message can be a response to the first message. That is, it could be that the second node sends the first message to the first node, and the second node, based on the received first message, sends the second message back to the second node; or, the first node sends the second message to the second node, and then the first node receives the first message sent by the second node based on the second message.

[0217] Optionally, with the first node mentioned above as the execution entity, the communication method may include:

[0218] Receive a first message sent by the second node. The first message is used to configure the first node for the transmission and / or storage of user data packets.

[0219] Optionally, the method may further include: sending a second message, wherein the second message is used to notify the second node of information about the transmission and / or storage of user data packets by the first node; the second message is a response message to the first message, or the first message is response information to the second message.

[0220] Optionally, the method may further include:

[0221] The first node configures the transmission and / or storage of user data packets according to the first message; wherein configuring the transmission and / or storage of user data packets according to the first message includes at least one of the following:

[0222] Determine whether to cache the data packet based on the first information;

[0223] Determine whether to cache the data packet based on the second information;

[0224] The transmission address information of the transmitted data packet is determined based on the third information;

[0225] Determine whether to transmit the cached data packet based on the fourth information;

[0226] The decision to cache data packets is made based on the seventh piece of information.

[0227] For a detailed description of the first and second messages, please refer to the previous descriptions of the first and second messages; they will not be repeated here.

[0228] Based on the optional embodiments provided in the first aspect, the solution provided in this application can have at least the following beneficial effects:

[0229] 1. The relay node (first node) can determine whether to cache data packets based on the configuration message (first configuration message).

[0230] 2. The relay node (first node) can determine the data packets to be transmitted based on the configuration message (first configuration message). For example, the first node can transmit data packets that the second node has not received.

[0231] 3. The anchor node (second node) can determine the data packets cached at the relay node (first node), thus knowing that only data packets cached at the relay node can be transmitted.

[0232] To better illustrate the solution provided in the first aspect of this application, the solution is described below with reference to several optional embodiments. It should be understood that the following description is an optional implementation of the solution of this application and should not be construed as a limitation of the solution of this application.

[0233] Example 1: The anchor node decides to send the UL DDS itself. Optionally, Example 1 may include the following steps:

[0234] Step 1-1-1: The second node sends a configuration message (an optional scheme of the first message) to the first node. This message provides the first node with information about the data reception status and includes at least one of the following:

[0235] ■ The first piece of information regarding the data packet transmission status, the contents of which can be found in "Information on Data Packet Transmission Status" in step 1-1 above.

[0236] Step 1-1-2: The first node sends configuration message two (an optional version of the second message) to the second node. This message retransmits the lost or unsuccessfully received data packets indicated in step 1-1-1. The information contained in this message can be found in the "Second Message" section of step 1-2 above. Furthermore, the first node updates the address information on its side in the retransmitted data packets with new address information, which can be configured according to step 1-1-0 as follows:

[0237] Step 1-1-0: The second node sends configuration message three (an optional scheme of the first message) to the first node. This message provides the first node with the configuration for retransmitting data packets, and includes at least one of the following information:

[0238] ■ First information related to the address, the contents of which can be found in “Information related to the address” in step 1-1 above.

[0239] Among them, step 1-1-0 is an optional step, and step 1-1-0 can occur before step 1-1-2.

[0240] Example 2: Anchor node enables IAB node packet caching. This optional example may include the following steps:

[0241] Step 1-2-1: The second node sends configuration message four (an optional scheme of the first message) to the first node. This message provides the first node with the configuration for retransmitting data packets, and includes at least one of the following information:

[0242] ■ First information enabling data packet transmission status, the information contained in which can be found in “Data packet transmission status enabling information” in step 1-1 above.

[0243] ■ First indication information for cached data packets, the information contained in which can be found in “Indication information for cached data packets” in step 1-1 above.

[0244] Step 1-2-2: The first node starts caching the data (i.e., data packets) received from the user, as the first node starts caching data packets according to the "first instruction information for caching data packets" mentioned above.

[0245] Step 1-2-3: The second node sends configuration message five (an optional scheme of the first message) to the first node. This message provides the first node with information about the data reception status and includes at least one of the following:

[0246] ■ The second piece of information regarding the data packet transmission status, the contents of which can be found in the “Information on Data Packet Transmission Status” in step 1-1 above.

[0247] Step 1-2-4: The first node sends configuration message six (an optional version of the second message) to the second node. This message retransmits the lost or unsuccessfully received data packets indicated in step 1-2-3. The information contained in this message can be found in the "Second Message" section of step 1-2 above. Optionally, the first node updates the address information on its side in the retransmitted data packets with new address information, which can be configured according to step 1-2-0 as follows:

[0248] Step 1-2-0: The second node sends configuration message seven (an optional scheme of the first message) to the first node. This message provides the first node with the configuration for retransmitting data packets, and includes at least one of the following information:

[0249] ■ The second piece of information is related to the address, the contents of which can be found in "Information Related to the Address" in step 1-1 above.

[0250] Among them, step 1-2-0 is an optional step, and step 1-2-0 can occur before step 1-2-4.

[0251] Example 3: The anchor node enables the IAB node to cache data packets and sends UL DDS based on the lowest PDCP SN (lowest sequence number). This example may include the following steps:

[0252] Step 1-3-1: The second node sends configuration message eight (an optional scheme of the first message) to the first node. This message provides the first node with configuration for retransmitting data packets, and includes at least one of the following information:

[0253] ■ The second information enabling the data packet transmission status, which can be found in the “Data Packet Transmission Status Enable Information” in step 1-1 above.

[0254] ■ Second indication information for cached data packets, the information contained in which can be found in “Indication information for cached data packets” in step 1-1 above.

[0255] Step 1-3-2: The first node begins caching data received from the user. This step can be that the first node starts caching data packets based on configuration message eight from step 1-3-1. Further, this embodiment may also include the first node sending configuration message nine (an optional second message) to the second node. This message indicates the data packets cached at the first node and includes at least one of the following information:

[0256] ■ First information related to the cached data packets, the contents of which can be found in the “Information related to the cached data packets” included in steps 1-2 above;

[0257] ■ First information related to the received data packet, the contents of which can be found in the "Information related to the received data packet" included in steps 1-2 above.

[0258] Step 1-3-3: The second node sends a configuration message (an optional scheme of the first message) to the first node. This message provides the first node with information about the data reception status and includes at least one of the following:

[0259] ■ The third piece of information regarding the uplink data packet transmission status, the contents of which can be found in "Information on Uplink Data Packet Transmission Status" in step 1-1 above.

[0260] Step 1-3-4: The first node sends configuration message eleven (an optional version of the second message) to the second node. This message retransmits the lost or unsuccessfully received data packets indicated in step 1-3-3. The information contained in this message can be found in the "Second Configuration Message" section of step 1-2 above.

[0261] Furthermore, optionally, the first node will update the address information on its side contained in the retransmitted data packet with new address information, which can be configured according to step 1-3-0 below:

[0262] Step 1-3-0: The second node sends configuration message 12 (an optional version of the first message) to the first node. This message provides the first node with configuration for retransmitting data packets and includes at least one of the following information:

[0263] ■ The second piece of information is related to the address, the contents of which can be found in "Information Related to the Address" in step 1-1 above.

[0264] Among them, step 1-3-0 is an optional step, which can occur before step 1-3-4.

[0265] Example 4: IAB node polls UL DDS. Optionally, this example may include the following steps:

[0266] Step 1-4-1: The first node sends configuration message thirteen (an optional scheme of the second message) to the second node. The purpose of this message is to provide the second node with information related to the cached data packets. This message includes at least one of the following information:

[0267] ■ The first polling indication information for uplink data transmission status information, which can be found in the "polling indication information for uplink data transmission status information" in steps 1-2 above.

[0268] ■ Second information related to cached data packets, the contents of which can be found in the “information related to cached data packets” included in steps 1-2 above;

[0269] ■ Second information related to the received data packet, the contents of which can be found in the "Information related to the received data packet" included in steps 1-2 above.

[0270] Step 1-4-2: The second node sends configuration message fourteen (an optional scheme of the first message) to the first node. The purpose of this message is to provide the first node with information about the data reception status. This message includes at least one of the following information:

[0271] ■ The fourth piece of information regarding the uplink data packet transmission status, the contents of which can be found in "Information on Uplink Data Packet Transmission Status" in step 1-1 above.

[0272] Step 1-4-3: The first node sends configuration message fifteen (an optional version of the second message) to the second node. This message is used to retransmit the lost or unsuccessfully received data packets indicated in step 1-4-2. The information contained in this message can be found in the "Second Configuration Message" in step 1-2 above. Further, optionally, the first node updates the address information on its side in the retransmitted data packets to new address information, which can be configured according to step 1-4-0 as follows:

[0273] Step 1-4-0: The second node sends configuration message sixteen (an optional scheme of the first message) to the first node. This message provides the first node with the configuration for retransmitting data packets, and includes at least one of the following information:

[0274] ■Third information related to the address, the contents of which can be found in "Information related to the address" in step 1-1 above.

[0275] Step 1-4-0 above is an optional step, which can occur before step 1-4-3.

[0276] In practical applications, if a relay node migration results in a change of the connected anchor node, such as migrating from anchor node 1 (or the centralized unit of anchor node 1, or the control plane portion of the centralized unit of anchor node 1, or the user plane portion of the centralized unit of anchor node 1) to anchor node 2 (or the centralized unit of anchor node 2, or the control plane portion of the centralized unit of anchor node 2, or the user plane portion of the centralized unit of anchor node 2), step 1-1 above can occur between anchor node 1 and the first node, or between anchor node 2 and the first node. That is, the second node can be an anchor node directly or indirectly connected to the first node in the source path before the migration, or an anchor node directly or indirectly connected to the first node in the target path after the migration. Similarly, step 1-2 above can occur between anchor node 1 and the first node, or between anchor node 2 and the first node. Furthermore, if the retransmitted data packet from the first node is sent to anchor node 2, then in the optional example of the first aspect above, the communication method may further include steps 1-3, namely, anchor node 2 sends the received retransmitted data packet to anchor node 1. Further, steps 1-4 are included between anchor node 1 and anchor node 2: anchor node 1 sends a third configuration message to anchor node 2. The purpose of this configuration message is to configure the reception of data packets sent by anchor node 2 (which may be retransmitted data packets), i.e., information related to receiving data packets sent by anchor node 2. In other words, anchor node 2 can notify anchor node 1 how to receive data packets. This message may include information about one or more radio bearers. For one or more radio bearers, the message includes at least one of the following information:

[0277] ■ Identification information of the wireless bearer, that is, the identification information of the wireless bearer corresponding to the data packet that anchor node 2 needs to send to anchor node 1.

[0278] ■ Address information on the anchor node 1 side, such as IP address, which is used to receive data packets sent by anchor node 2.

[0279] ■ The identification information of the tunnel on the anchor node 1 side, such as the tunnel endpoint identifier (TEID), is used to inform anchor node 1 that when receiving a data packet sent by anchor node 2, the transmission tunnel of the data packet is the tunnel identifier information on the anchor node 1 side.

[0280] ■ The second aspect: Data packet transmission mechanism in relay networks

[0281] In a relay network, relay nodes may migrate (i.e., their connected parent nodes change). During this process, one or more nodes on the source path (one or more of these nodes may appear on both the source and destination paths) also buffer some data packets that have not been sent to the destination node (i.e., the destination receiving node; for downlink data, the destination node can be a migrated relay node or a child node of a migrated relay node; for uplink data, the destination node can be an anchor node, or a centralized unit of an anchor node, or the control plane portion of a centralized unit of an anchor node, or the user plane portion of a centralized unit of an anchor node). To avoid the source sending node (for downlink data, the source sending node can be an anchor node, or a centralized unit of an anchor node, or the control plane portion of a centralized unit of an anchor node, or the user plane portion of a centralized unit of an anchor node; for uplink data, the source sending node can be a migrated relay node, or a child node of a migrated relay node) retransmitting these data packets, that is, to avoid the source sending node needing to repeatedly transmit these data packets due to relay node migration, and to enable the continued transmission of data packets, that is, to continue sending these data packets to the destination receiving node, the second aspect of the present invention provides a communication method, the purpose / function of which is to configure the transmission of data packets, such as... Figure 6 As shown, the method may include the following steps:

[0282] Step 2-1: The second node sends a third message (also called the first data configuration message or other names) to the first node. The third message is used to configure the transmission of user data packets corresponding to the first node, that is, to configure the transmission of user data.

[0283] With the first node as the execution subject, the method may include:

[0284] The first node receives the third message sent by the second node.

[0285] Optionally, it may also include: the first node transmitting user data packets according to the third message, such as the first node determining the transmission configuration of the data packets according to the third message, and transmitting user data packets based on the determined transmission configuration.

[0286] In an optional embodiment of this application, the user data packet corresponding to the first node may include the user data packet corresponding to the node before the migration (i.e., the user data packet corresponding to the first node before the migration), or the user data packet corresponding to the node before the configuration information of the first node was updated. The user data packet corresponding to the first node may be a data packet to be transmitted by the first node, a data packet received by the first node from other nodes / user terminals, or a data packet to be sent by the first node.

[0287] In one embodiment, the aforementioned user data (i.e., the user data packet addressed by the third message) may be data transmitted via the source path before the configuration update of the first node or before the migration of the first node. Further, optionally, this data (i.e., the data packet) may be cached in the first node. The data packets cached by the first node can be found in the description of the optional embodiments of the first aspect.

[0288] Optionally, the first node in an embodiment of the second aspect may include at least one of the following:

[0289] The relay node that has migrated; the distribution unit portion of the relay node that has migrated; the mobile terminal portion of the relay node that has migrated; the child node of the relay node that has migrated; the distribution unit portion of the child node of the relay node that has migrated; the mobile terminal portion of the child node of the relay node that has migrated; the parent node of the relay node that has migrated; the distribution unit portion of the parent node of the relay node that has migrated; the mobile terminal portion of the parent node of the relay node that has migrated.

[0290] Optionally, the second node in an embodiment of the second aspect may include at least one of the following:

[0291] Anchor node; centralized unit of anchor node; control plane portion of centralized unit of anchor node; user plane portion of centralized unit of anchor node; wherein, the anchor node here may be the anchor node corresponding to the relay node before migration or the anchor node corresponding to the relay node after migration.

[0292] In optional embodiments of this application, the aforementioned third message may include at least one of the following:

[0293] First indication information is used to indicate a third data packet, the third data packet including at least one of a data packet to be transmitted and a data packet not to be transmitted; wherein, the first indication information of the data packet to be transmitted may also be referred to as "configuration information related to the data packet to be transmitted", and the first indication information of the data packet not to be transmitted may also be referred to as "information related to the data packet not to be transmitted".

[0294] The first configuration information is used to indicate the configuration used for transmitting the data packets that need to be transmitted, that is, to indicate the transmission configuration of the data packets that need to be transmitted; the first configuration information can also be called "configuration information related to the transmission of data packets", that is, this information is used to indicate how to transmit the data packets that need to be transmitted, that is, the configuration information used by these data packets.

[0295] The second indication information is used to indicate the update of the information contained in the data packet to be transmitted. This indication information can also be called "information related to the information contained in the data packet". This indication information is used to indicate the update of the data packet content, that is, to indicate the content in the data packet that needs to be updated.

[0296] Information related to the configuration information of the user terminal accessing the first node, also known as "user configuration related information", is used to configure the user, i.e., the UE.

[0297] Optionally, the data packets to be transmitted may include data packets cached in the first node.

[0298] Optionally, the first indication information may include information related to the transmission path of the data packet.

[0299] Optionally, the first configuration information (configuration information related to the transmission of data packets) may include at least one of the following:

[0300] Transmission path configuration information may include path identification information used by the first node to transmit data packets (such as BAP Prouting ID, path ID, etc.), identification information of the previous node, identification information of the backhaul link channel used to receive data packets, identification information of the next hop node, identification information of the backhaul link channel used to send data packets, address information of the source node (source sending node), and address information of the destination node (destination receiving node).

[0301] The indication information for the retained transmission configuration is used to indicate whether the first node retains the configuration before the configuration update or migration (the old configuration) for data transmission. For example, it is used to indicate the configuration that does not need to be updated / retained / not retained. For example, it can contain relevant information about the configuration that does not need to be updated. Such relevant information can be at least one of the following: information contained in the data packet, routing-related information, and data mapping-related information.

[0302] The indication information for the released transmission configuration is used to indicate whether the first node needs to release the configuration before the configuration update or before the migration to transmit data.

[0303] The aforementioned indication information for maintaining the transmission configuration and the indication information for releasing the transmission configuration can also be collectively referred to as "indication information for maintaining the configuration".

[0304] Optionally, the aforementioned second indication information (information relating to the information contained in the data packet) includes at least one of the following:

[0305] The fourth data packet contains information indicating the information contained therein;

[0306] The fifth data packet contains information indicating its contents.

[0307] The fourth data packet refers to the data packet transmitted before the node corresponding to the first node migrates or before the configuration information of the node corresponding to the first node is updated; the fifth data packet refers to the data packet transmitted after the node corresponding to the first node migrates or after the configuration information of the node corresponding to the first node is updated.

[0308] It should be noted that the node corresponding to the first node can be the first node itself, or it can be a related node of the first node, such as the child node or parent node of the first node.

[0309] Optionally, the information related to the configuration information of the user terminal accessing the first node may include at least one of the following:

[0310] User terminal configuration information, also known as user configuration information, is the information used to configure the user terminal.

[0311] The third instruction information is used to indicate the timing of configuring the configuration information of the user terminal, that is, to indicate when to send the above-mentioned "user terminal configuration information" to the user. This third instruction information can also be called "instruction information for delaying the sending of user configuration information".

[0312] To more clearly illustrate the information that the aforementioned third message may contain, each piece of information is described in detail below. Optionally, the aforementioned third message may include at least one of the following information:

[0313] Configuration information related to the transmitted data packets; configuration information related to the transmission of data packets; information related to the information contained in the data packets; information related to data packets that do not need to be transmitted; and information related to user configuration.

[0314] The following explains the information that the third message may contain.

[0315] ■ Configuration information related to the transmitted data packets, which indicates which data packets the first node needs to continue transmitting. In one embodiment, the data packets may be data packets cached by the first node. The configuration information of the data packets indicated by this information includes at least one of the following:

[0316] ■ Routing identification information, such as the BAP routing ID, in one embodiment includes the address information of the destination receiving node (such as the BAP address) and path identification information (such as the path ID).

[0317] ■The purpose is to receive the address information of the receiving node (such as BAP address and / or IP address).

[0318] ■ Path identification information (such as path ID)

[0319] ■ Identification information of the previous hop node, such as the BAP address

[0320] ■ Identification information of the backhaul link channel used to receive data packets (such as ingress BH RLC channelID). Further, this backhaul link channel is the channel on the link between the first node (such as the node that has migrated, or the first node a, or the first node b) and the aforementioned "previous hop node".

[0321] ■Identification information of the next-hop node, such as the BAP address

[0322] ■ Identification information of the backhaul link channel used to send data packets (such as the egress BH RLC channel ID). Further, this backhaul link channel is the channel on the link between the first node and the aforementioned "next-hop node".

[0323] ■ The address information of the source node (such as BAP address and / or IP address).

[0324] ■ Configuration information related to data packet transmission, indicating the configuration information used by the first node when transmitting data packets. In one embodiment, the transmitted data packets are data packets cached by the first node. Further, the transmitted data packets are data transmitted from the source path to the first node before a configuration update or migration of the first node. This configuration information can be used to configure the transmission of all data packets (i.e., all data packets are transmitted using the same configuration) or to configure the transmission of different types of data packets (i.e., different types of data packets are transmitted using different configurations). For a given configuration, this information includes at least one of the following:

[0325] ■ Routing identification information, such as the BAP routing ID, in one embodiment includes the address information of the destination receiving node (such as the BAP address) and path identification information (such as the path ID).

[0326] ■ Identification information of the previous hop node, such as the BAP address

[0327] ■ Identification information of the backhaul link channel used to receive data packets (such as ingress BH RLC channelID). Further, this backhaul link channel is the channel on the link between the first node and the aforementioned "previous hop node".

[0328] ■Identification information of the next-hop node, such as the BAP address

[0329] ■ Identification information of the backhaul link channel used to send data packets (such as the egress BH RLC channel ID). Further, this backhaul link channel is the channel on the link between the first node and the aforementioned "next-hop node".

[0330] ■ Source node address information, such as source IP address information, source BAP address information

[0331] ■ Address information of the destination node (i.e., the target receiving node), such as destination IP address information and destination BAP address information.

[0332] ■ Instructions for maintaining configurations. This information indicates whether the first node should maintain the configuration before the update or migration (the old configuration) for data transfer, i.e., maintain it, or not maintain it (or release it). The configurations that need to be maintained (or not maintained, or released) (such as BAP configurations) include at least one of the following configurations:

[0333] ◆The information contained in the data packet includes at least one of the following:

[0334] ● Routing identification information, such as the BAP routing ID, in one embodiment includes the address information of the destination receiving node (such as the BAP address) and path identification information (such as the path ID).

[0335] ●The destination node's address information (such as BAP address and / or IP address)

[0336] ● Path identification information (such as path ID)

[0337] ● Source node address information (such as BAP address and / or IP address)

[0338] ◆ Routing-related information, which indicates the routing information of data packets at the first node, includes at least one of the following:

[0339] ● Routing identification information, such as the BAP routing ID, in one embodiment includes the address information of the destination receiving node (such as the BAP address) and path identification information (such as the path ID).

[0340] ●The destination node's address information (e.g., BAP address)

[0341] ● Path identification information (such as path ID)

[0342] ●Identification information of the next-hop node, such as the BAP address.

[0343] ◆Information related to data mapping, which indicates the mapping information used for data packets in the first node's transmission. This mapping information indicates how to map data on the node's receive channel to the transmit channel. For example, for a node, this mapping information could indicate how the node should transmit its received data packets. This information includes at least one of the following:

[0344] ●Identification information of the upstream node (for example, if node A sends a data packet and node B receives the data packet, then node A is the upstream node corresponding to node B), such as BAP address, IP address, etc.

[0345] ● Identification information of the backhaul link channel used to receive data packets (such as ingress BH RLC channelID). Further, optionally, the backhaul link channel can be a channel on the link between the first node and the aforementioned "previous hop node".

[0346] ●Identification information of the next-hop node (for example, if node A needs to send a data packet to node B, then node B is the next-hop node of node A), such as BAP address and / or IP address, etc.

[0347] ●Identification information of the backhaul link channel used to send data packets (such as egress BH RLC channel ID (transmission backhaul link radio link layer control protocol channel identifier)). Further, optionally, the backhaul link channel is the channel on the link between the first node and the aforementioned "next-hop node".

[0348] ■ Information relating to the information contained in the data packet, indicating an update to the information contained in the data packet, including at least one of the following:

[0349] ◆Address identification information

[0350] ◆Legacy routing identification information, such as the BAP routing ID, in one embodiment includes the destination node's address (e.g., the BAP address) and path identification information.

[0351] ◆ New routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0352] ◆Old source address (source sending address) information, such as IP address

[0353] ◆New source address information, such as IP address

[0354] ◆Old destination address information, such as IP address

[0355] ◆ New destination address information, such as IP address

[0356] In the aforementioned information, the old information (such as old routing identifier information, old source address information, and old destination address information) refers to the information contained in the data packets before the first node's configuration update or migration, while the new information (such as new routing identifier information, new source address information, and new destination address information) refers to the information contained in the data packets after the first node's configuration update or migration. The first node can determine the information contained in the data packets to be transmitted based on this information. If the information related to the data packets includes both old and new information, the first node can replace the information corresponding to the old information in the data packets with the corresponding new information; for example, updating the old routing identifier information in the data packets to the new routing identifier information.

[0357] ■ Information relating to data packets that do not need to be transmitted, indicating either data packets that the first node does not need to transmit or data packets that the first node needs to discard, including at least one of the following:

[0358] ■ Indication information for nodes that have not been migrated (or whose configuration has not been updated), such as BAP address, IP address, identification information of relay nodes, identification information of the distribution unit functional part of relay nodes (such as gNB-DU ID), etc. In one embodiment, if the destination receiving node of the data packet is the node indicated by the indication information, then these data packets do not need to be transmitted.

[0359] ■ Indication information for discardable packets (or data packets that do not need to be transmitted), which includes at least one of the following:

[0360] ◆ Routing identification information, such as BAP routing ID, in one embodiment, includes the address of the destination node (such as the BAP address) and path identification information. Accordingly, if the routing identification information is included, the data packet corresponding to the routing identification information can be discarded.

[0361] ◆The destination receiving node's identification information, such as the BAP address, means that data packets corresponding to this identification information can be discarded.

[0362] ◆ Path identification information, such as Path ID, means that packets corresponding to this route identification information can be discarded.

[0363] ■ Information related to user configuration. This information is used to configure the user who is accessing the first node. The user can be a regular user without relay functionality, or a relay node with relay functionality (i.e., a child node of the first node, or a child node of a child node of the first node). This information includes at least one of the following:

[0364] ◆Configure user information, which may be information contained in an RRC message. In one embodiment, the information contains an RRC message (such as an RRC Reconfiguration message), which is used to configure users accessing the first node and will ultimately be sent to the user by the first node. Furthermore, the information may also include an indication to delay the execution of the configuration contained in the information. Upon receiving the indication, the user will not immediately execute the configuration contained in the information after receiving the user configuration information, but will execute it after certain conditions are met (such as the first node notifying the user to execute).

[0365] ◆ An instruction to delay sending user configuration messages is provided. This instruction instructs the first node to delay sending the aforementioned "user configuration information" to the user. In one embodiment, upon receiving this instruction, the first node will send all its cached data packets to the user before sending the "user configuration information." In one example, the cached data packets may be data packets received before the first node's configuration update or migration. In another example, the cached data packets may be the data packets indicated by the aforementioned "configuration information related to the transmitted data packets." In a practical system, after receiving the "user configuration information," the user can update their security-related configurations (such as security keys). However, the security configuration used in the data packets cached by the first node is the configuration before the first node's configuration update or migration. To ensure that the user can correctly receive these data packets, the user needs to adopt the configuration before the first node's configuration update or migration. Therefore, the purpose of this instruction to delay sending user configuration messages is to help the user correctly receive the data packets cached before the first node's configuration update or migration. In another embodiment, when the "configuration user information" is used to configure the child nodes of the first node, the "instruction information for delaying the sending of user configuration messages" means that the first node will send the "configuration user information" to the child nodes after receiving the RRC message configuring the first node (such as the RRCReconfiguration message, which is used to configure the mobile terminal part of the first node and is sent by the second node through the parent node of the first node). In this embodiment, the beneficial effect of delaying the sending of the RRC message configuring the child nodes is that the first node and its child nodes update their configurations at similar times. This ensures that the first node and its child nodes update their configurations at similar times, thereby reducing the continuity of data transmission between the first node and its child nodes and avoiding long interruption times.

[0366] In an optional embodiment of this application, the communication method may further include:

[0367] Step 2-2 (optional step): Receive the response message of the third message (also known as the first data configuration response message), which confirms that the configuration in step 2-1 has been completed.

[0368] Taking the first node as the execution subject, the description of step 2-2 is: sending the response message of the third message.

[0369] Optionally, after receiving the third message sent by the second node, the first node may also send a first data configuration response message to the second node to confirm that the configuration in step 2-1 has been completed, that is, the first node has performed the corresponding configuration / processing based on the third message.

[0370] Optionally, the communication method may also include:

[0371] Step 2-3: The first node performs corresponding processing according to the third message, that is, the first node transmits user data (data packets) according to the configuration in step 2-1, that is, the transmission of user data shown in the figure.

[0372] Based on the optional embodiments provided in the second aspect of this application, the relay node (first node) can determine the transmission method of the data packets received before the configuration update or migration based on the third message sent by the second node, and transmit these data packets to the destination node.

[0373] In the above process, the specific types of the first data configuration message (third message) and the first data configuration response message (fourth message) are not limited in this application embodiment. For example, they can be F1AP messages (such as UE ContextModification Request / Response messages), RRC messages (such as RRCReconfiguration and RRCReconfigurationComplete messages), or other messages.

[0374] It is understandable that step 2-1 above is described with the second node as the execution subject. Similarly, it can also be described with the first node as the execution subject. In this case, the communication method can include:

[0375] Receive a third message, wherein the third message is used to configure the transmission of user data packets corresponding to the first node;

[0376] User data packets are transmitted based on third-party messages.

[0377] Optionally, the communication method may further include: sending a response message of a third message to determine that the corresponding configuration has been completed based on the third message.

[0378] The optional embodiments provided in the second aspect of this application, in the above process, can have different implementation methods for different data packet transmission methods. To better illustrate the solution provided in the second aspect of this application, the solution is described below with reference to several optional embodiments. It should be understood that the following description represents optional implementation methods of the solution of this application and should not be construed as limiting the solution of this application.

[0379] Example 1: Transmitting data packets entirely using the configuration before the configuration update or migration. This example may include the following steps:

[0380] Step 2-1-1: The second node sends a data configuration message (an optional third message) to the first node. This message configures the transmission of user data and includes at least one of the following information:

[0381] ■ First configuration information related to the transmitted data packet, the contents of which can be found in "Configuration Information Related to the Transmitted Data Packet" in step 2-1 above.

[0382] ■ First configuration information related to the transmission of data packets, which includes "instruction information for maintaining configuration" (the configuration to be maintained indicated by this information can be found in the "instruction information for maintaining configuration" in step 2-1 above).

[0383] ■ First information related to data packets that do not need to be transmitted, the contents of which can be found in "Information related to data packets that do not need to be transmitted" in step 2-1 above.

[0384] ■ First information related to user configuration, the contents of which can be found in "Information related to user configuration" in step 2-1 above.

[0385] Step 2-1-2: The first node transmits user data according to the configuration in Step 2-1-1. For example, the first node will continue to transmit data packets cached before the configuration update or migration according to the original configuration.

[0386] Based on this first embodiment, the first node can transmit the data packets it caches according to the configuration of the second node. Optionally, the data packets cached by the first node can be the data packets cached by the first node as described in the optional embodiment of the first aspect of this application.

[0387] Example 2: Transmitting data packets using the configuration before the update or migration, but with changes to the information contained in the data packets (such as changes to the source IP address). This example may include the following steps:

[0388] Step 2-2-1: The second node sends a second data configuration message (an optional third message) to the first node. This message configures the transmission of user data and includes at least one of the following information:

[0389] ■ Second configuration information related to the transmitted data packet, the contents of which can be found in "Configuration Information Related to the Transmitted Data Packet" in step 2-1 above.

[0390] ■ Second configuration information related to the transmission of data packets, which includes "instruction information for maintaining configuration" (the configuration to be maintained indicated by this information can be found in the "instruction information for maintaining configuration" in step 2-1 above).

[0391] ■ First information related to the information contained in the data packet, the information of which can be found in "Information related to the information contained in the data packet" in step 2-1 above.

[0392] ■ Second information relating to data packets that do not need to be transmitted, the contents of which can be found in "Information relating to data packets that do not need to be transmitted" in step 2-1 above.

[0393] ■ Second information related to user configuration, the contents of which can be found in "Information related to user configuration" in step 2-1 above.

[0394] Step 2-2-2: The first node transmits user data according to the configuration in Step 2-2-1. For example, the first node continues to transmit data packets cached before the configuration update or migration according to the original configuration. Furthermore, when sending these data packets, the first node will change the information contained in the data packets (the information to be modified can be found in "First Information Related to the Information Contained in the Data Packet" in Step 2-2-1 above. In one example, the modified information is the source IP address).

[0395] Example 3: Transmitting data packets using a completely new configuration, and transmitting all cached data packets with the same new configuration, without changing the information contained in the data packets. This example may include the following steps:

[0396] Step 2-3-1: The second node sends a data configuration message three (an optional third message) to the first node. This message configures the transmission of user data and includes at least one of the following information:

[0397] ■ Third configuration information related to the transmitted data packet, the contents of which can be found in "Configuration Information Related to the Transmitted Data Packet" in step 2-1 above.

[0398] ■ Third configuration information related to the transmission of data packets, which does not include "instruction information for maintaining configuration" (the configuration to be maintained indicated by this information can be found in the "instruction information for maintaining configuration" in step 2-1 above). In one embodiment, the information contained in this information can be used to configure the transmission of all buffered data packets. In another embodiment, the information contained in this information can be used to configure the transmission of the data packets indicated by the aforementioned "third configuration information related to the transmitted data packets".

[0399] ■Third information related to data packets that do not need to be transmitted; the content of this information can be found in "Information related to data packets that do not need to be transmitted" in step 2-1 above.

[0400] ■Third information related to user configuration, the contents of which can be found in "Information related to user configuration" in step 2-1 above.

[0401] Step 2-3-2: The first node transmits user data according to the configuration in Step 2-3-1. For example, the first node transmits data packets cached before the configuration update or migration using the configuration in Step 2-3-1. This configuration in Step 2-3-1 is used to transmit all cached data packets or the data packets indicated by the "third configuration information related to the transmitted data packets" in Step 2-3-1. Furthermore, the first node does not change the information contained in the data packets when sending them.

[0402] Example 4: Transmitting data packets using a completely new configuration, and transmitting different cached data packets using different new configurations, while keeping the information contained in the data packets unchanged. This example may include the following steps:

[0403] Step 2-4-1: The second node sends a data configuration message four to the first node. This message configures the transmission of user data and includes at least one of the following information:

[0404] ■ Fourth configuration information related to the transmitted data packet, the contents of which can be found in "Configuration Information Related to the Transmitted Data Packet" in step 2-1 above.

[0405] ■ Fourth configuration information related to data packet transmission. This information does not include "instructions for maintaining configuration" (the configuration to be maintained indicated by this information can be found in the "instructions for maintaining configuration" in step 2-1 above). In one embodiment, this information may include multiple new configuration information, each of which is used to transmit a type of data packet.

[0406] ■ Fourth information related to data packets that do not need to be transmitted, the contents of which can be found in "Information related to data packets that do not need to be transmitted" in step 2-1 above.

[0407] ■ The fourth piece of information relates to user configuration. This information can be found in the "Information Related to User Configuration" section of step 2-1 above.

[0408] Step 2-4-2: The first node transmits user data according to the configuration in Step 2-4-1. For example, the first node transmits data packets cached before the configuration update or migration using the configuration in Step 2-4-1. Different types of data packets will be transmitted using different configurations. Furthermore, the first node does not change the information contained in the data packets when sending them.

[0409] Example 5: Transmitting data packets with a completely new configuration, and transmitting all buffered data packets with the same new configuration, while changing the information contained in the data packets. This example may include the following steps:

[0410] Step 2-5-1: The second node sends a data configuration message (optional for the third message) to the first node. This message configures the transmission of user data and includes at least one of the following information:

[0411] ■ Fifth configuration information related to the transmitted data packet, the contents of which can be found in "Configuration Information Related to the Transmitted Data Packet" in step 2-1 above.

[0412] ■ Fifth configuration information related to data packet transmission, which does not include "instruction information for maintaining configuration" (the configuration to be maintained indicated by this information can be found in the "instruction information for maintaining configuration" in step 2-1 above). The information contained in this information can be used to configure the transmission of all buffered data packets. In another embodiment, the information contained in this information can be used to configure the transmission of the data packets indicated by the aforementioned "third configuration information related to the transmitted data packets".

[0413] ■ Secondary information related to the information contained in the data packet, the information of which can be found in "Information related to the information contained in the data packet" in step 2-1 above.

[0414] ■ The fifth piece of information relates to data packets that do not need to be transmitted. The contents of this information can be found in "Information related to data packets that do not need to be transmitted" in step 2-1 above.

[0415] ■ The fifth piece of information related to user configuration, the contents of which can be found in "Information related to user configuration" in step 2-1 above.

[0416] Step 2-5-2: The first node transmits user data according to the configuration in Step 2-5-1. For example, the first node transmits data packets cached before the configuration update or migration using the configuration in Step 2-5-1. This configuration in Step 2-5-1 is used to transmit all cached data packets or the data packets indicated by the "Third Configuration Information Related to the Transmitted Data Packets" in Step 2-5-1. Furthermore, when sending these data packets, the first node modifies the information contained in the data packets (the information to be modified can be found in the "Second Information Related to the Information Contained in the Data Packets" in Step 2-5-1 above).

[0417] Example 6: Transmitting data packets using a completely new configuration, and transmitting different cached data packets using different new configurations, with changes to the information contained in the data packets. This example may include the following steps:

[0418] Step 2-6-1: The second node sends a data configuration message six (an optional third message) to the first node. This message configures the transmission of user data and includes at least one of the following information:

[0419] ■ The sixth configuration information related to the transmitted data packet, the contents of which can be found in "Configuration Information Related to the Transmitted Data Packet" in step 2-1 above.

[0420] ■ The sixth configuration information related to the transmission of data packets does not include "instructions for maintaining the configuration" (the configuration to be maintained indicated by this information can be found in the "instructions for maintaining the configuration" in step 2-1 above). In one embodiment, this information may include multiple new configuration information, each of which is used to transmit a type of data packet.

[0421] ■Third information related to the information contained in the data packet, the information of which can be found in "Information related to the information contained in the data packet" in step 2-1 above.

[0422] ■ The sixth piece of information relates to data packets that do not need to be transmitted. This information can be found in the section on "Information Related to Data Packets That Do Not Need to Be Transmitted" in step 2-1 above.

[0423] ■ The sixth piece of information related to user configuration, the contents of which can be found in "Information related to user configuration" in step 2-1 above.

[0424] Step 2-6-2: The first node transmits user data according to the configuration in Step 2-6-1. For example, the first node transmits data packets cached before the configuration update or migration using the configuration in Step 2-6-1. Different types of data packets will be transmitted using different configurations. Furthermore, when sending these data packets, the first node will modify the information contained in the data packets (the information to be modified can be found in "Third Information Related to the Information Contained in the Data Packets" in Step 2-6-1 above).

[0425] Another technical problem in this regard is that when the parent node of a relay node changes, the network side will update the configuration of the relay node or its child nodes. These updates will involve the data transmission of the relay node or its child nodes, which introduces a lot of signaling overhead to the network and increases the network burden. Figure 6 a(1) serves as an example, illustrating a specific explanation of this technical problem. For example... Figure 6 As shown in a(1), relay node a has undergone a change of parent node (from relay node 1 to relay node 2; relay node 1 and relay node 2 are respectively connected to the centralized unit of anchor node 1 and the centralized unit of anchor node 2). This causes a change in the data transmission between the centralized unit of anchor node 1 and relay nodes a / b / c (or the distributed unit portion of relay nodes a / b / c). Before the migration, the nodes that the centralized unit of anchor node 1 traverses when sending data to relay nodes a / b / c (…) Figure 6 The nodes along the path indicated by the dashed line in a(1) are the distribution unit of anchor node 1 and relay node 1, respectively. The addresses used by relay nodes a / b / c are addresses 1-0 / 2-0 / 3-0 (old address information; as an example, these addresses could be IP addresses). After the migration, the nodes that the centralized unit of anchor node 1 passes through when sending data to relay nodes a / b / c are ( Figure 6The nodes on the path shown by the solid line in a(1) are the distribution unit of anchor node 2 and relay node 2, respectively. Then the addresses used by relay nodes a / b / c are addresses 1-1 / 2-1 / 3-1 (new address information; as an example, these addresses can be IP addresses). The reason for the address change is that the distribution unit of the anchor node in the transmission link has been changed to the distribution unit of anchor node 2. The address used by the relay node accessing this distribution unit needs to be different from that of the relay node accessing the distribution unit of anchor node 1 (the updated address can ensure that the data sent by the centralized unit of anchor node 1 can be routed to the distribution unit of anchor node 2 first). According to the traditional method, in order to ensure the continuation of data transmission after migration, the centralized unit of anchor node 1 or the centralized unit of anchor node 2 needs to update the address information of relay nodes a / b / c through signaling. In addition, other configuration updates are required (such as routing configuration updates, bearer mapping configuration updates, etc.), which will inevitably introduce more signaling overhead. The technical problem that this invention aims to solve is to reduce these signaling overheads, and even after a migration, one or more of the relay nodes a / b / c do not need to be updated in terms of configuration (i.e., they continue to use the configuration before the migration to continue data transmission with the centralized unit of anchor node 1).

[0426] The present invention addresses the above-mentioned technical problems as follows: Figure 6 As shown in a(2). When the centralized unit of anchor node 1 sends data to relay nodes a / b / c, it still uses the new address (such as address 1-1 / 2-1 / 3-1, corresponding to an example in the first related information section below). When the data is routed to the distribution unit of anchor node 2, the distribution unit of anchor node 2 updates the destination address of the data packet (such as updating the data packet with the destination address of address 1-1 / 2-1 / 3-1 to address 1-0 / 2-0 / 3-0 respectively (corresponding to an example in the second related information section below)). In this way, relay nodes a / b / c can continue to use the address used before the migration to receive data packets, such as... Figure 6 As shown by the solid line in a(2), the distribution unit of anchor node 2 performs address translation on the received data packets, converting the destination address of the data packets from the new address 1-1 / 2-1 / 3-1 to the old address 1-0 / 2-0 / 3-0 respectively. According to this solution, signaling interaction between nodes is required, but there is no need to update the configuration of one or more of the relay nodes a / b / c, such as... Figure 6 The interaction process corresponding to the dotted line on the right in a(2) does not require configuration updates in relay nodes a / b / c.

[0427] The process involved in the above method can follow steps 2-1, 2-2 (optional), and 2-3, specifically, as follows: Figure 6b As shown, the processes involved may include:

[0428] Step 2a-1: The second node sends a third message (also called a first data configuration message or other names) to the first node. In one example, the second node is the centralized unit of the anchor node, or the control plane portion of the centralized unit of the anchor node, or the user plane portion of the centralized unit of the anchor node, and the first node is the distribution unit of the anchor node. This third message configures the first node to transmit data packets, which are sent to a relay node (or the distribution unit of the relay node). The destination address of the data packet is the address of the relay node. In one example, the relay node can be the node undergoing migration, or a child node of the migrated relay node (the child node can be directly connected to the migrated relay node, or it can be connected to the migrated relay node through one or more nodes). This third message contains at least one of the following information:

[0429] ■ Configuration information related to the transmitted data packets, the contents of which can be found in the description in step 2-1 above.

[0430] ■ Configuration information related to the transmission of data packets. The contents of this information can be found in the description in step 2-1 above. The "information related to the information contained in the data packet" contained in this information can be used to indicate the update of the information contained in the data packet. This information includes at least one of the following:

[0431] ◆Address identification information

[0432] ◆First routing identification information, such as BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0433] ◆Second routing identification information, such as BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0434] ◆First source address information, such as IP address

[0435] ◆Second source address information, such as IP address

[0436] ◆First destination address information, such as IP address

[0437] ◆Secondary destination address information, such as IP address

[0438] In the aforementioned information, the first related information (such as first route identifier information, first source address information, and first destination address information, e.g., address 1-1 / 2-1 / 3-1 mentioned above) is the information contained in the data packet received by the first node, and the second related information (such as second route identifier information, second source address information, and second destination address information, e.g., address 1-0 / 2-0 / 3-0 mentioned above) is the information contained in the data packet sent by the first node. The first node can update the data packet based on the information contained in this information. For example, if the information related to the information contained in the data packet includes the first related information and the second related information, the first node can replace the information corresponding to the first related information in the data packet with the corresponding second related information. For example, updating the first route identifier information in the data packet to the second route identifier information, updating the first destination address information in the data packet to the second destination address information, and updating the first source address information in the data packet to the second source address information. The beneficial effect of receiving the above information is that the first node can update the information of the data packets it receives, thereby ensuring that these updated data packets can be received by the relay nodes, and these relay nodes do not need to perform configuration updates when receiving data packets, reducing the signaling overhead caused by configuring relay nodes.

[0439] ■ Other information, which can be found in the information described in step 2-1 above.

[0440] Step 2a-2 (optional step): The first node sends a response message to the second node for the third message (also known as the first data configuration response message). This message confirms that the configuration in step 2a-1 has been completed. In addition, when the third message only contains the second related information, the response message for the third message may also include at least one of the following information:

[0441] ■ Address identification information

[0442] ■ First routing identification information, such as BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0443] ■ Second routing identification information, such as BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0444] ■ First source address (source sending address) information, such as IP address

[0445] ■ Second source address information, such as IP address

[0446] ■ First destination address information, such as IP address

[0447] ■Secondary destination address information, such as IP address

[0448] The aforementioned second relevant information is received through step 2a-1, while the first relevant information is information required by other nodes (such as the sixth node described below) when sending data. Thus, the data packet received by the first node will contain the aforementioned first relevant information, and the first node will update the first relevant information contained in the data packet with the aforementioned second relevant information.

[0449] When step 2a-1 includes the second relevant information and step 2a-2 includes the first relevant information, the above process can help the first node determine whether to update the information in the received data packet. For example, when the first node receives a data packet containing the first relevant information, it will update the first relevant information to the second relevant information. The advantage of this is that by updating the data packet information through the first node, it ensures that these updated data packets can be received by the relay nodes, and these relay nodes do not need to perform configuration updates when receiving data packets, reducing the signaling overhead caused by configuring relay nodes.

[0450] Steps 2a-3: The first node performs corresponding processing based on the third message and / or the response message of the third message (i.e. Figure 6b (Data processing in the process), that is, the first node transmits user data (data packets) according to the configuration in step 2a-1 and / or step 2a-2, such as updating the information in the received data packets according to the configuration in step 2a-1 / or step 2a-2.

[0451] Furthermore, when the second node is Figure 6 When anchor node 2 (or the centralized unit of anchor node 2, or the controllable surface portion of the centralized unit of anchor node 2) is in a(2), the above process may further include: the second node sends address update information to anchor node 1 (or the centralized unit of anchor node 1, or the controllable surface portion of the centralized unit of anchor node 1, or the user surface portion of the centralized unit of anchor node 1) in the figure. The purpose of this information is to inform anchor node 1 (or the centralized unit of anchor node 1, or the controllable surface portion of the centralized unit of anchor node 1, or the user surface portion of the centralized unit of anchor node 1) to use the updated information for data transmission. Specifically, it also includes the following steps:

[0452] Step 2a-4: (This step can be after step 2a-2 above) The second node sends a first configuration update message to the sixth node. This message informs the sixth node of the information required for data transmission. The second node and the sixth node are two different anchor nodes (or the centralized unit of the anchor node, or the control plane portion of the centralized unit of the anchor node, or the user plane portion of the centralized unit of the anchor node). The sixth node sends data to a relay node (which can be the node that has migrated or a child node of the migrated node). The second node controls the distribution unit of the anchor node that receives the data sent by the sixth node. In one embodiment, such as... Figure 6 As shown in a(2), the second node is the centralized unit of anchor node 2 (or the control plane portion of the centralized unit of anchor node 2, or the user plane portion of the centralized unit of anchor node 2), and the sixth node is the centralized unit of anchor node 1 (or the control plane portion of the centralized unit of anchor node 1, or the user plane portion of the centralized unit of anchor node 1). The first configuration update message includes at least one of the following information:

[0453] ■ Address identification information

[0454] ■ Second routing identification information, such as BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0455] ■ First routing identification information, such as BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0456] ■Second source address (source sending address) information, such as IP address

[0457] ■ First source address information, such as IP address

[0458] ■Secondary destination address information, such as IP address

[0459] ■ First destination address information, such as IP address

[0460] Upon receiving the above information, the sixth node can use the first routing identifier information and / or the first source address information and / or the first destination address information to transmit data packets. Before receiving the above information, these data packets were transmitted using the second routing identifier information and / or the second source address information and / or the second destination address information. After receiving the above new information, the sixth node uses the first relevant information to transmit data packets.

[0461] Before steps 2a-4, steps 2a-4a may also be included, in which the sixth node sends a first configuration update request message to the second node. The purpose of this message is to provide the second node with information used for data packet transmission, and the message includes at least one of the following information:

[0462] ■ Address identification information

[0463] ■ Second routing identification information, such as BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information.

[0464] ■Second source address (source sending address) information, such as IP address

[0465] ■Secondary destination address information, such as IP address

[0466] The above information is what the sixth node uses in the data packet when sending data to the relay node (which can be the node that has migrated or a child node of the node that has migrated).

[0467] In one embodiment, steps 2a-1 and / or 2a-2 and / or 2a-4a and / or 2a-4 can be performed individually or in combination.

[0468] The third message, the response message to the third message, the first configuration update message, and the first configuration update request message in the above process can be an F1 message or an Xn message, and can be an existing message or a new message.

[0469] The beneficial effects of the above process are as follows: through signaling interaction between the centralized unit (control plane part or user plane part of the centralized unit of the anchor node) and the distributed unit, and / or signaling interaction between the anchor nodes (centralized unit, control plane part or user plane part of the centralized unit of the anchor node), the distributed unit of the anchor node can process data packets, thereby ensuring that these updated data packets can be received by the relay nodes (or the distributed units of the relay nodes), and these relay nodes (or the distributed units of the relay nodes) do not need to perform configuration updates when receiving data packets, reducing the signaling overhead caused by configuring relay nodes. In one example, the above-mentioned relay node (or the distributed unit of the relay node) can be a node that has migrated, or it can be a child node of the relay node that has migrated (the child node can be directly connected to the relay node that has migrated, or it can be connected to the relay node that has migrated through one or more nodes).

[0470] The following is combined with Figure 6The examples in a(2) provide alternative embodiments of the above process, namely Embodiments 7 and 8 below.

[0471] Example 7: The second node notifies the first node to update the address of the data packet, such as... Figure 6c As shown, the following steps may be included:

[0472] Step 2a-1-1: The second node sends a third message to the first node, which includes at least one of the following information:

[0473] ■ Address identification information

[0474] ■ First routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0475] ■ Second routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0476] ■ First source address (source sending address) information, such as IP address, etc. Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0477] ■Second source address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0478] ■ First destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0479] ■Secondary destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0480] Step 2a-2-1: The first node sends a response message for the third message to the second node.

[0481] Step 2a-3-1: The first node processes the information of the received data packet according to the third message (i.e. Figure 6c (data processing in the middle) Figure 6As shown in a(2), the first node will update the address 1-1 / 2-1 / 3-1 contained in the received data packet to the address 1-0 / 2-0 / 3-0.

[0482] Example 8: The second node notifies the first node of the information contained in the data packet, and the first node notifies the second node of the first relevant information required for data packet transmission. This example includes the following steps, such as... Figure 6d :

[0483] Step 2a-1-2: The second node sends a third message to the first node, which includes at least one of the following information:

[0484] ■ Address identification information

[0485] ■ Second routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0486] ■Second source address (source sending address) information, such as IP address, etc. Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0487] ■Secondary destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0488] Step 2a-2-2: The first node sends a response message for the third message to the second node. This response message includes one of the following information:

[0489] ■ Address identification information

[0490] ■ Second routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0491] ■ First routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0492] ■Second source address (source sending address) information, such as IP address, etc. Figure 6For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0493] ■ First source address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0494] ■Secondary destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0495] ■ First destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0496] Step 2a-3-2: The first node processes the received data packet based on the third message and / or the response message to the third message (i.e. Figure 6d (Data processing in the process). The data packets received by the first node will contain the new information from step 2a-2-2 above (i.e., the first related information, such as address 1-1 / 2-1 / 3-1), and then the first node will update the old information (i.e., the second related information) contained in these data packets with the new information. Figure 6 As shown in a(2), the first node will update the addresses 1-1 / 2-1 / 3-1 contained in the received data packet to addresses 1-0 / 2-0 / 3-0 respectively.

[0497] Furthermore, step 2a-0-2 is included before step 2a-1-2 above, that is...

[0498] Step 2a-0-2: The sixth node sends a first configuration update request message to the second node. The content of this message can be found in steps 2a-4a above. This message serves to inform the relay node of the configuration information used when transmitting data. Specifically, the message includes at least one of the following information:

[0499] ■ Address identification information

[0500] ■ Second routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0501] ■Second source address (source sending address) information, such as IP address, etc. Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0502] ■Secondary destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0503] Following step 2a-2-2, another step 2a-2a-2 may be included, in which the second node sends a first configuration update message to the sixth node. This message informs the sixth node of the information required for data transmission, as described in step 2a-4 above. Specifically, this message includes at least one of the following pieces of information:

[0504] ■ Address identification information

[0505] ■ Second routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0506] ■ First routing identification information, such as the BAP routing ID, in one embodiment includes the address of the destination node (such as the BAP address) and path identification information, to... Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0507] ■Second source address (source sending address) information, such as IP address, etc. Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0508] ■ First source address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0509] ■Secondary destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-0 / 2-0 / 3-0

[0510] ■ First destination address information, such as IP address, Figure 6 For example, in a(2), this information could be address 1-1 / 2-1 / 3-1

[0511] The first relevant information mentioned above was obtained by the second node through step 2a-2-2 above.

[0512] In the above embodiment, it is assumed that the first node has migrated. However, in a real system, this can also be used when the first node has not migrated but a configuration update has occurred. In this case, the first node and the second node are nodes that are not in the migration process. For example, the first node is a relay node, and the second node is an anchor node or a centralized unit of an anchor node, or the control plane portion of the centralized unit of an anchor node, or the user plane portion of the centralized unit of an anchor node.

[0513] ■ Third aspect: Data packet transmission

[0514] In the second aspect of this application, the first node is configured to transmit cached data packets according to the configuration before the configuration update or migration. However, in a real system, these cached data packets are limited, and once these cached data packets have been sent, the configuration before the configuration update or migration (the old configuration) does not need to be maintained. The "instruction information for maintaining the configuration" included in step 2-1 of the second aspect above provides a method for releasing the old configuration, namely, releasing the configuration by sending a first data configuration message.

[0515] To ensure the transmission of data packets and release the old configuration in a timely manner, the third aspect of this invention provides other optional methods. These methods involve a third node (e.g., a migrated node, a parent node directly connected to the migrated node, or a parent node indirectly connected to the migrated node) and a fourth node (e.g., a child node directly connected to the migrated node, or a child node indirectly connected to the migrated node). Other nodes may exist between the third and fourth nodes; that is, the third and fourth nodes can communicate through other nodes. Data packets destined for the fourth node are also buffered at the third node. When the third node migrates, to ensure the fourth node releases the old configuration promptly, the third aspect of this application provides a communication method that can be executed by the third node. This method may include:

[0516] Send a fourth message, which indicates the timing of configuration updates and / or configuration releases for the fourth node, and / or indicates the status of data packets sent to the fourth node.

[0517] Correspondingly, with the fourth node as the execution subject, the method may include: receiving a fourth indication information message sent by the third node, the fourth indication information message being used to indicate the timing of configuration update or configuration release for the fourth node, and / or indicating the status of data packets sent to the fourth node.

[0518] In other words, the third node sends a fourth message to inform the fourth node when the new configuration (i.e., the configuration corresponding to the migrated node) can be used, and / or to inform the fourth node when the old configuration (i.e., the node configuration used before the migration) can be released. This message can be sent directly by the third node to the fourth node, or it can be sent by the third node through other nodes. The specific form of the fourth message is not limited in this embodiment; for example, it can be carried in a data packet (such as in the BAP header), or it can be a pre-agreed information format.

[0519] Optionally, the third node can be a relay node that has migrated, a child node of the node that has migrated, or a parent node of the node that has migrated, and the fourth node can be the target receiving node of the user data packet corresponding to the third node.

[0520] Optionally, the fourth message mentioned above can be a data packet, which may contain at least one of the following:

[0521] The information indicates whether the data packet is the last data packet, to instruct the fourth node to perform a configuration update and / or configuration release, and / or to indicate the status of the data packets sent to the fourth node;

[0522] The information indicates whether the data packet is the first data packet, to instruct the fourth node to perform a configuration update and / or configuration release, and / or to indicate the status of the data packet sent to the fourth node;

[0523] The instruction information corresponding to the data packet is used to instruct the data packet to be transmitted to the fourth node according to the transmission configuration information.

[0524] Optionally, the last data packet mentioned above may be the last data packet transmitted using the old configuration, and the first data packet mentioned above may be the first data packet transmitted using the new configuration.

[0525] The communication method will now be explained with reference to optional embodiments of the third aspect of this application. Similarly, the optional embodiments described below should not be construed as limiting the implementation of the method, but rather as possible implementations of the method.

[0526] As an alternative, such as Figure 7 As shown, the communication method provided in this aspect may include the following steps 3-1 and 3-2:

[0527] Step 3-1: The third node sends a third data packet, the destination receiving node of which is the fourth node. The node receiving the first data packet can be the fourth node, or another node between the third and fourth nodes. Optionally, the data packet contains at least one of the following information:

[0528] ■ The last packet indication information (i.e., an optional form of the fourth message mentioned above) indicates whether the packet is the last packet sent to the fourth node (or the last cached packet, or the last packet received under the old configuration, or the last packet sent using the old configuration).

[0529] ■ The indication information for the first packet (an optional method of the fourth message mentioned above), the purpose of which is to indicate whether the packet is the first packet sent to the fourth node (or the first packet sent using the new configuration).

[0530] ■ The indication information of the transmission configuration used, which informs the receiving node of the third data packet (which may be the fourth node, or the transmission node between the third and fourth nodes) of the configuration information used when sending the data packet, such as indicating the use of the old configuration information or indicating the use of the new configuration information.

[0531] The aforementioned old configuration (old configuration information), or new configuration (new configuration information), or specific information regarding the transmission configuration may include at least one of the following:

[0532] ■Information contained in the data packet

[0533] ■ Information related to routing (i.e., information related to the transmission route corresponding to the data packet)

[0534] ■ Information related to data mapping (see the description of the corresponding information above).

[0535] Optionally, the specific details of the above configuration can be found in the definition / description of step 2-1 above. Step 3-2: The fourth node processes the third data packet sent by the third node.

[0536] In one example, if the indication information contained in the third data packet indicates that the data packet is not the last data packet sent to the fourth node (or the last cached data packet, or the last data packet received under the old configuration, or the last data packet sent using the old configuration) or the first data packet (or the first data packet sent using the new configuration), then the fourth node continues to receive data packets with the old configuration.

[0537] In another example, if the indication information contained in the third data packet indicates that the data packet is the last data packet sent to the fourth node (or the last cached data packet, or the last data packet received under the old configuration, or the last data packet sent using the old configuration) or the first data packet (or the first data packet sent using the new configuration), then the fourth node releases (i.e. will no longer use) the old configuration and transmits data packets using the new configuration.

[0538] If the third data packet is the first data packet sent using the new configuration, the fourth node can still receive the first data packet using the old configuration. After receiving the data packet, the fourth node can use the new configuration and release the old configuration.

[0539] Optionally, when there are one or more other nodes (such as the tenth node) between the third and fourth nodes, the third data packet sent in step 3-1 above will be sent to the tenth node. In this case, the communication method further includes the following steps:

[0540] Step 3-1a: The tenth node receives the third data packet sent by the third node. In one example, if the indication information contained in the third data packet indicates that the data packet is not the last data packet sent to the fourth node (or the last buffered data packet, or the last data packet received under the old configuration, or the last data packet sent using the old configuration) or the first data packet (or the first data packet sent using the new configuration), then the tenth node continues to receive and / or send data packets using the old configuration. In another example, if the indication information contained in the third data packet indicates that the data packet is the last data packet sent to the fourth node (or the last buffered data packet, or the last data packet received under the old configuration, or the last data packet sent using the old configuration) or the first data packet (or the first data packet sent using the new configuration), then the tenth node sends the data packet last (i.e., the last of all packets sent to the fourth node). Furthermore, after sending the third data packet, the tenth node releases the old configuration and transmits data packets using the new configuration. If there are multiple intermediate nodes (i.e., the tenth node mentioned above) between the third and fourth nodes, each intermediate node can perform the above steps 3-1a.

[0541] That is, when the fourth node is the destination receiving node of the third data packet, the fourth node can perform corresponding processing based on the fourth message carried in the third data packet. If the fourth node is not the destination receiving node of the third data packet, the fourth node can perform corresponding processing based on the fourth message carried in the data packet and continue to send the data packet to the destination receiving node so that the destination receiving node can perform corresponding processing based on the information in the data packet (including the fourth message).

[0542] The optional embodiments of the third aspect described above are from the perspective of the fourth message sending node (i.e., the third node). Similarly, when the corresponding scheme is described from the perspective of the receiving node (the fifth node), the communication method may include:

[0543] Receive a fourth message sent by the third node, which indicates the timing of configuration updates and / or configuration releases of the fourth node, and / or indicates the status of data packets sent to the fourth node.

[0544] Optionally, the fifth node can be the fourth node, or the fifth node can be any other node on the transmission path between the third and fourth nodes.

[0545] Optionally, if the fifth node is any other node, the method further includes:

[0546] Send the fourth message to the fourth node.

[0547] Optionally, the method may further include: performing at least one of the following based on the fourth message:

[0548] Data packet transmission; configuration information update (updating the new configuration, i.e. using the new configuration); configuration information release (i.e., releasing the old configuration).

[0549] In the optional embodiments of the third aspect of this application, the third data packet in the above-described process can be a data packet containing a BAP header or other types of data packets. The "indication information of the last packet" in the third data packet can be included in the BAP header or in other fields of the data packet. That is to say, when the fourth message is interacted based on data packets, the specific position of the fourth message in the data packet (i.e., how the data packet carries the message) and the format of the data packet are not limited in the embodiments of this application.

[0550] The above description assumes node migration, but in a real system, the above process can also be used at the third, fourth, and tenth nodes if no migration occurs.

[0551] The optional embodiments provided in the third aspect of this application can have at least the following technical effects:

[0552] Relay nodes (i.e., the fourth node, or the node between the third and third nodes) can correctly receive data packets sent to the node before configuration updates or migrations, and can also release old configurations in a timely manner, thereby avoiding the retransmission of data packets and saving network resources.

[0553] ■ Fourth aspect: Configuring the user (UE) to access the relay node.

[0554] During relay node migration, the anchor node it connects to may change, leading to a change in the security configuration (such as security keys) of the users (i.e., user terminals, UEs) connecting to the relay node. In conventional technologies, once the centralized unit (the centralized unit of the anchor node) to which the user is connected changes, all data packets not sent to the user are transmitted using the new security configuration (such as security keys). However, in a relay network, since the relay node may still cache data packets using the old security configuration (before the relay node migration), in order for the user to correctly receive these data packets (thus avoiding the new anchor node retransmitting these data packets), the user needs to be configured so that the user can receive data packets with the correct security configuration. To achieve this, the second aspect of this application provides an optional method, namely, delaying the sending of RRC messages to the user, and sending "instruction information for delaying the sending of user configuration information" so that the second node can correctly receive data packets. In addition to this optional method, the fourth aspect of this application also provides other methods. In the following method, it is assumed that the anchor node to which the migrated node is connected has migrated from one anchor node (referred to as the source anchor node) to another anchor node (referred to as the destination anchor node). In this process, it is necessary to configure the users accessing the migrated node.

[0555] For the purposes described above, a fourth aspect of this application provides a communication method that can be executed by a sixth node, the method comprising:

[0556] Send a fifth message, which includes configuration information about the transmission and / or processing of data packets by the user terminal accessing the seventh node, wherein the transmission configuration information includes configuration information corresponding to the relay node before migration and / or configuration information corresponding to the migration.

[0557] Optionally, the seventh node includes at least one of the following:

[0558] The relay node that has migrated; the relay node that shares the same anchor node as the relay node that has migrated;

[0559] Optionally, the sixth node includes at least one of the following:

[0560] The seventh node; the anchor node; the centralized unit of the anchor node; the control plane portion of the centralized unit of the anchor node; the user plane portion of the centralized unit of the anchor node; wherein, the anchor node is the anchor node corresponding to the relay node before the migration or the anchor node corresponding to the migration after the migration.

[0561] Optionally, the seventh node can be the anchor node after the migration, that is, the anchor node connected to by the relay node after the migration, and the sixth node can be the relay node that sent the migration.

[0562] In an optional embodiment of this application, the fifth message may include at least one of the following:

[0563] Configuration information corresponding to at least one radio bearer, which may also be referred to as first user configuration information;

[0564] This message is used to notify the user terminal of the configuration information used for the conversion; it can also be called a configuration conversion indication message.

[0565] Configuration information used by user terminals can also be called third-party user configuration information.

[0566] In an optional embodiment of this application, the communication method may further include:

[0567] Send a sixth message to the seventh node. The sixth message is used to request the configuration information of the user terminal that accesses the seventh node.

[0568] A response message to the sixth message is received, the response message including configuration information about the transmission and / or processing of data packets by the user terminal accessing the seventh node.

[0569] The solution provided in the fourth aspect of this application will now be described in conjunction with the selected implementation methods.

[0570] Implementation Method 1: Data packets based on the old configuration and data packets based on the new configuration are transmitted using different DRBs (Data Radio Bearers) and / or LCIDs (Logical Channel IDs). As an optional approach, this method may include the following procedures: Figure 8 As shown:

[0571] Step 4-1-1: The sixth node sends a first user configuration message (an optional scheme of the fifth message) to the user, i.e., the user terminal. This user terminal is a terminal accessing the sixth node. The user terminal can be a regular terminal without relay functionality, or it can be a relay node (i.e., a child node of the first node) with relay functionality. In one embodiment, this message can be sent by the sixth node to the user through one or more intermediate nodes. In another embodiment, the message can be sent by the sixth node to the seventh node, and then by the seventh node to the user (e.g., node N sends it directly to the user, or node N sends it to the user through one or more intermediate nodes). The purpose of this configuration message is to configure the user's reception of data (i.e., data packets). This data may use an old security configuration (the security configuration used before the relay node accessed by the user migrated), or it may use a new security configuration (the security configuration used after the relay node accessed by the user migrated). This message may include configurations for one or more radio bearers. For a radio bearer, the message includes at least one of the following information:

[0572] ■ Identification information of wireless bearers

[0573] ■ Configuration information for the wireless bearer, which includes at least one of the following:

[0574] ◆PDCP Configuration

[0575] ◆RLC Configuration

[0576] ◆Logical Channel Configuration

[0577] ◆Indication information for the first configuration type, which indicates whether the configuration information is an old configuration (such as an old security configuration, or the configuration used before the first node migration) or a new configuration (such as a new security configuration, or the configuration used after the first node migration).

[0578] ◆Indication information for the first user data: This indication information is used to indicate whether the user data served by this configuration uses data packets from the old configuration (such as the old security configuration, or the configuration used before the first node migration) or data packets from the new configuration (such as the new security configuration, or the configuration used after the first node migration).

[0579] For the configuration of PDCP, RLC, and logical channels mentioned above, please refer to TS38.331.

[0580] ■ First configuration information for the wireless bearer, in one embodiment, the first configuration information is for serving data packets using an older configuration, and the configuration information includes at least one of the following:

[0581] ■PDCP Configuration

[0582] ■ RLC (Radio Link Control) Configuration

[0583] ■Logical Channel Configuration

[0584] The configurations for PDCP, RLC, and logical channels described above can be found in the communication standard TS38.331.

[0585] ■Second configuration information for the wireless bearer, in one embodiment, the first configuration information is a data packet used to serve a new configuration, and the configuration information includes at least one of the following:

[0586] ■PDCP Configuration

[0587] ■RLC Configuration

[0588] ■Logical Channel Configuration

[0589] For the configuration of PDCP, RLC, and logical channels mentioned above, please refer to TS38.331.

[0590] ■ Configuration information for the logical channel. This configuration information must include at least the identifier of the logical channel. Other configurations can be found in LogicalChannelConfig in TS38.331 of the table. In addition, this configuration information may also include at least one of the following:

[0591] ◆Indication information for the second configuration type, which indicates whether the configuration information is an old configuration (such as an old security configuration, or the configuration used before the first node migration) or a new configuration (such as a new security configuration, or the configuration used after the first node migration).

[0592] ◆Indication information for the second user data, which indicates whether the user data served by this configuration uses data packets from the old configuration (such as the old security configuration, or the configuration used before the first node migration) or data packets from the new configuration (such as the new security configuration, or the configuration used after the first node migration).

[0593] ■ Configuration information for the first logical channel, which includes at least the identifier of the logical channel. Other configurations can be found in LogicalChannelConfig in TS38.331. In one embodiment, after a user receives a data packet from this first logical channel, the old configuration (such as the old security configuration or the configuration used before the first node migration) will be used to process the data packet.

[0594] ■ Configuration information for the second logical channel, which includes at least the identifier of the logical channel. Other configurations can be found in LogicalChannelConfig in TS38.331. In one embodiment, after a user receives a data packet from the second logical channel, the user will process the data packet using a new configuration (such as a new security configuration or the configuration used after the first node migration).

[0595] In the optional implementation provided in the fourth aspect of this application, the fifth message mentioned above may include configuration information for the user terminal to receive data packets (i.e., the function of this information is to inform the user how to receive data), and may also include configuration information for the user to process data packets after receiving data (the function of this information is to inform the user how to process data, such as the configuration information being about the new security key information that the user terminal will use after the node in the network sends the migration, and the user can use the security key to process the received data packets).

[0596] With the user terminal as the execution entity, the above-mentioned optional embodiments may further include, for example: Figure 8 The diagram includes step 4-1-2: User Processing Data Packets. In this step, the user terminal may determine the configuration used for processing data packets and / or the configuration used for receiving data packets based on the configuration information in step 4-1-1.

[0597] In addition, to configure users, the above implementation method one may also include an interaction process between the destination anchor node / source anchor node and the first node. Optionally, this interaction process may include:

[0598] Step 4-1-1a: The sixth node (which can be the destination anchor node / source anchor node, or the centralized element of the anchor node, the control plane portion of the centralized element, or the user plane portion of the anchor node, corresponding to...) Figure 8 The sixth node (source anchor node / destination anchor node) sends a first configuration request message (sixth message) to the first node. The purpose of this request message is to configure the users accessing the first node (such as the relay node sending the migration). For a user, the configuration request message includes at least one of the following information:

[0599] ■User identification information

[0600] ■ Configuration information of a user's wireless bearer. For a single wireless bearer, this information includes at least one of the following:

[0601] ◆Identification information of wireless bearers

[0602] ◆Information regarding the tunnel on the destination anchor node / source anchor node side, including at least one of the following:

[0603] ● Address information, such as IP address

[0604] ● Tunnel identification information, such as tunnel endpoint ID

[0605] ● Instructions to maintain the old configuration: This information indicates whether to maintain the old configuration (the configuration before the first node migration), such as "maintain" or "do not maintain". If the instruction indicates "maintain", it means that the first node will still transmit data on the old tunnel (the old tunnel established between the first node and the source anchor node before the migration).

[0606] Step 4-1-1b: The first node sends a first configuration request response message (i.e., the response information of the sixth message) to the destination anchor node / source anchor node. The purpose of this response message is to generate the user's configuration based on the configuration in step 4-1-1a. This message includes at least one of the following information:

[0607] ■ Identification information of wireless bearers

[0608] ■ Configuration information for wireless bearer

[0609] ■ First configuration information for wireless bearers

[0610] ■Second configuration information for wireless bearer

[0611] ■ Configuration information of logical channels

[0612] ■ Configuration information of the first logical channel

[0613] ■ Configuration information for the second logical channel

[0614] For details of the above configuration information, please refer to the definition / description in step 4-1-1 above.

[0615] Optionally, steps 4-1-1a and 4-1-1b above may occur before step 4-1-1.

[0616] Optionally, in the implementation scheme including steps 4-1-1a and 4-1-1b, the fifth message can be obtained by the destination anchor node / source anchor node based on the aforementioned sixth information. For example, the destination anchor node / source anchor node extracts some or all of the information from the aforementioned response message to form the fifth message, and then sends it to the user terminal. That is to say, the fifth message sent to the user terminal can be generated by the destination anchor node / source anchor node, or it can be generated by the destination anchor node / source anchor node based on the sixth message sent to the destination anchor node / source anchor node by the relay node to which the user terminal is connected. Optionally, when the destination anchor node / source anchor node sends the fifth message to the user terminal, it can send it directly to the user terminal, or it can send it to the user terminal through the user terminal's relay node.

[0617] In the above process, the first user configuration message can be an RRC message, such as an RRCReconfiguration message, or other types of messages; the first configuration request message and the first configuration request response message can be UEContext Setup / Modification Request and UE Context Setup / Modification Response messages, respectively, or other types of messages.

[0618] The beneficial effects of the above-described implementation method one process can include at least the following:

[0619] 1. Users can determine the configuration used to process user data. For example, for data packets received before the first node migration, the user will use the old configuration to process them, and for data packets received after the first node migration, the user will use the new configuration to process them. This process ensures that users correctly process the data they receive.

[0620] 2. Users can use both the old and new configurations to process data, and the network side can use both the old and new configurations to send data to users, thus improving data transmission efficiency.

[0621] Optionally, in the fourth aspect of this application, method two involves sending a configuration conversion instruction to the user via a fifth message. Optionally, such as... Figure 9 As shown, the process of this method may include:

[0622] Step 4-2-1: The first node (which may be a relay node undergoing migration) sends a second user configuration message to the user. This message indicates the configuration information used by the user to process data, and includes at least one of the following:

[0623] ■ Configuration instructions: These instructions notify the user of the configuration to be changed. For example, they may instruct the user to use a new configuration (such as a new security configuration or the configuration used after the first node migration). Before receiving this instruction, the user will be using the old configuration to process received data packets.

[0624] ■ The configuration information used to process user data includes at least one of the following:

[0625] ■PDCP Configuration

[0626] ■RLC Configuration

[0627] ■Logical Channel Configuration

[0628] The configurations of PDCP, RLC, and logical channel mentioned above can be found in the corresponding descriptions in standard TS38.331.

[0629] Step 4-2-2: The user, i.e. the user terminal, determines the configuration to be used for processing user data based on the information in step 4-2-1.

[0630] In the process of the above-mentioned second implementation method, the second user configuration message can be sent to the user via MAC CE, via RLC packet header, or via other means.

[0631] Implementation Method 3: The source anchor node or the destination anchor node sends configuration information to the user. Optional, such as... Figure 10 As shown, method three may include the following steps.

[0632] Step 4-3-1: The source anchor node or the destination anchor node sends a third-party user configuration message to the user. This message indicates the configuration information used by the user to process the data, and it includes at least one of the following:

[0633] ■ Configuration instructions: These instructions notify the user of the configuration to be changed. For example, they may instruct the user to use a new configuration (such as a new security configuration or the configuration used after the first node migration). Before receiving this instruction, the user will be using the old configuration to process received data packets.

[0634] ■ The configuration information used to process user data includes at least one of the following:

[0635] ◆PDCP Configuration

[0636] ◆RLC Configuration

[0637] ◆Logical Channel Configuration

[0638] The PDCP configuration, RLC configuration, and logical channel configuration mentioned above can be found in step 4-3-2 of TS38.331: The user determines the configuration used to process user data based on the information in step 4-3-1.

[0639] In the process of the above-mentioned implementation method three, the third user configuration message can be an RRC message (such as an RRCReconfiguration message) or other types of messages.

[0640] The solutions of Implementation Method 2 and Implementation Method 3 described above have at least the following beneficial effects:

[0641] Users can determine the configuration for processing user data based on the received configuration information, ensuring the correct receipt of user data.

[0642] Based on the optional embodiments provided in the first, second, third, and fourth aspects of this application, the communication method provided in this application can at least have the following effects:

[0643] A. Based on the invention's content in the first aspect, the beneficial effects include:

[0644] 1. The relay node (first node) can determine whether to cache data packets based on the configuration message (first configuration message);

[0645] 2. The relay node (first node) can determine the data packets to be transmitted based on the configuration message (first configuration message). For example, the first node can transmit data packets that the second node has not received.

[0646] 3. The anchor node (second node) can determine the data packets cached at the relay node (first node), thus knowing that only data packets cached at the relay node can be transmitted.

[0647] B. Based on the invention of the first aspect, the beneficial effects include: the relay node can determine the transmission method of the data packets received before the configuration update or migration, and transmit these data packets to the destination node.

[0648] C. Based on the invention in the first aspect, the beneficial effects include: the relay node can correctly receive data packets sent to the node before configuration updates or migrations, and can also release old configurations in a timely manner, thereby avoiding the retransmission of data packets and saving network resources.

[0649] Based on the fourth aspect of the invention, the beneficial effects are: users can determine the configuration used to process user data, thereby ensuring that users correctly receive user data during relay node migration.

[0650] Based on the same principle as the method provided in the first aspect of the embodiments of this application, the embodiments of this application also provide a communication device, wherein the communication device may be a component of a first node, the device includes a communication module, and the communication module is configured to:

[0651] Receive a first message sent by the second node. The first message is used to configure the first node for the transmission and / or storage of user data packets.

[0652] Optionally, the first message includes at least one of the following:

[0653] The first information indicates whether a fourth information will be sent, where the fourth information indicates the data packet transmission status; the second information indicates whether the data packet is buffered; the third information indicates the transmission address information corresponding to the data packet; the fourth information indicates the data packet transmission status; and the seventh information indicates node migration event notification information.

[0654] Optionally, the above communication module is also configured as follows:

[0655] Based on the first message, configure the transmission and / or storage of user data packets;

[0656] The communication module, in configuring the transmission and / or storage of user data packets according to the first message, can be configured to perform at least one of the following:

[0657] Determine whether data packets need to be cached based on at least one of the first, second, fourth, and seventh pieces of information;

[0658] Based on the third piece of information, determine the transmission address information of the transmitted data packet;

[0659] Based on the fourth piece of information, determine the data packets to be transmitted, and / or the method of transmitting the data packets.

[0660] Optionally, the transmission address information corresponding to the data packet includes at least one of the following information used by the first node and / or the second node to transmit the data packet:

[0661] BAP address information, IP address information, and tunnel identification information.

[0662] Optionally, the fourth piece of information mentioned above includes at least one of the following:

[0663] The second node expects information about the transmission of data packets; information relating to at least one first data packet, wherein the first data packet includes at least one of the following:

[0664] Lost data packets; successfully transmitted data packets; successfully transmitted retransmitted data packets; data packets that were not successfully transmitted; data packets that were not successfully transmitted and retransmitted.

[0665] Optionally, the transmission expectation information includes at least one of the following:

[0666] Expected buffer size; expected transfer rate.

[0667] Optionally, the information relating to at least one first data packet includes at least one of the following:

[0668] At least one packet identification information for the first data packet;

[0669] Information on the number of the first data packets transmitted consecutively;

[0670] At least one transmission status indication information for the first data packet.

[0671] Optionally, the packet identification information of at least one first packet includes at least one of the following:

[0672] The identification information of the last transmitted data packet in the first data packet;

[0673] The identification information of the first transmitted data packet in the first data packet;

[0674] The identification information of the first transmitted data packet in the first continuously transmitted data packet;

[0675] The identification information of the last transmitted data packet in the first continuously transmitted data packet;

[0676] The transmission status indication information of at least one first data packet includes:

[0677] Bitmap information indicating whether the first data packet was lost or successfully received.

[0678] Optionally, the above-mentioned communication device can also be configured as follows:

[0679] Send a second message, wherein the second message is used to notify the second node of information about the transmission and / or storage of user data packets by the first node; the second message is a response message to the first message, or the first message is response information to the second message.

[0680] Optionally, the second message includes at least one of the following:

[0681] The fifth message is used to notify the second node whether it needs to send the fourth message, which is used to indicate the data packet transmission status.

[0682] Information relating to at least one second data packet, wherein the second data packet includes at least one of the following:

[0683] The data packets that the first node needs to send to the second node; the data packets cached by the first node; the data packets received by the first node; and the retransmitted data packets.

[0684] Optionally, the information relating to at least one second data packet includes at least one of the following:

[0685] At least one data packet needs to be transmitted from the first node to the second node;

[0686] At least one second data packet's packet identification information;

[0687] Indication information for at least one second data packet's data packet identification information;

[0688] Information on the number of second data packets;

[0689] Indication information regarding whether at least one second data packet is cached;

[0690] Indication information indicating whether at least one second data packet is a retransmission data packet.

[0691] This application embodiment also provides a communication device, which can be implemented as a component of a second node. The communication device includes a communication module, which can be configured to send a first message, wherein the first message is used to configure the first node to transmit and / or store user data packets.

[0692] Optionally, the communication module can also be configured to receive a second message sent by the first node, wherein the second message is used to notify the second node of the first node's transmission and / or storage of user data packets, wherein the first message is a response message to the second message, or the second message is a response message to the first message.

[0693] Optionally, the above communication module can also be configured to perform at least one of the following:

[0694] The first message is determined based on the second message;

[0695] Based on the second message, information for configuring the first node to transmit and / or store user data packets is sent to the first node.

[0696] This application embodiment also provides a communication device, which can be implemented as a component of a first node. The communication device includes a communication module, which can be configured to: receive a third message, wherein the third message is used to configure the transmission of user data packets corresponding to the first node; and transmit user data packets according to the third message.

[0697] Optionally, the user data packet corresponding to the first node includes the user data packet corresponding to the first node before the node migration, or the user data packet corresponding to the first node before the node configuration information was updated.

[0698] Optionally, the third message includes at least one of the following:

[0699] First indication information is used to indicate a third data packet, the third data packet including at least one of a data packet that needs to be transmitted and a data packet that does not need to be transmitted;

[0700] The first configuration information is used to indicate the transmission configuration of the data packets that need to be transmitted;

[0701] The second instruction information is used to indicate the information contained in the data packet to be transmitted;

[0702] Information related to the configuration information of the user terminal accessing the first node.

[0703] Optionally, the information related to the configuration information of the user terminal accessing the first node includes at least one of the following:

[0704] The configuration information of the user terminal; the third indication information, used to indicate when to configure the configuration information of the user terminal.

[0705] Optionally, the above communication module can also be configured as follows:

[0706] A response message to the third message.

[0707] This application embodiment also provides a communication device, which can be implemented as a component of a second node, wherein the communication device includes a communication module configured to:

[0708] Send a third message, wherein the third message is used to configure the transmission of user data packets corresponding to the first node.

[0709] Optionally, the above communication module can also be configured to receive a response message of the third message.

[0710] This application embodiment also provides a communication device that can be implemented as a component of a third node, wherein the communication device includes a communication module configured to:

[0711] Send a fourth message, which indicates the timing of configuration updates and / or configuration releases for the fourth node.

[0712] Optionally, the fourth message is a data packet containing at least one of the following:

[0713] This information indicates whether the data packet is the last data packet, instructing the fourth node to perform a configuration update and / or configuration release;

[0714] This information indicates whether the data packet is the first data packet, instructing the fourth node to perform a configuration update and / or configuration release;

[0715] The instruction information corresponding to the data packet is used to instruct the data packet to be transmitted to the fourth node according to the transmission configuration information.

[0716] Optionally, the third node is a relay node that has migrated, and the fourth node is the target receiving node for the user data packets corresponding to the third node.

[0717] This application embodiment also provides a communication device that can be implemented as a component of a fourth node, wherein the communication device includes a communication module configured to:

[0718] Receive a fourth message sent by the third node, the fourth message being used to indicate the timing of configuration update and / or configuration release regarding the fourth node.

[0719] Optionally, the third node is a relay node that has migrated, and the fourth node is the target receiving node for the user data packets corresponding to the third node.

[0720] Optionally, the above communication module can also be configured as follows:

[0721] Based on the fourth message, perform at least one of the following:

[0722] Data packet transmission; configuration information update; configuration information release.

[0723] This application embodiment also provides a communication device that can be implemented as a component of a sixth node, wherein the communication device includes a communication module configured to:

[0724] Send a fifth message, which includes configuration information about the transmission and / or processing of data packets by the user terminal accessing the seventh node, wherein the transmission configuration information includes configuration information corresponding to the relay node before migration and / or configuration information corresponding to the migration.

[0725] Optionally, the fifth message includes at least one of the following:

[0726] Configuration information corresponding to at least one radio bearer;

[0727] Information used to notify user terminals of the configuration information used for conversion;

[0728] Configuration information used by user terminals.

[0729] Optionally, the above communication module can also be configured as follows:

[0730] Send a sixth message to the seventh node, the sixth message being used to request configuration information corresponding to the user terminal accessing the seventh node;

[0731] A response message to the sixth message is received, the response message including configuration information about the transmission and / or processing of data packets by the user terminal accessing the seventh node.

[0732] This application embodiment also provides a communication device, which can be implemented as a component of a user terminal. The communication device includes a communication module configured to:

[0733] Receive a fifth message, which includes configuration information for the transmission and / or processing of data packets by the user terminal accessing the seventh node, wherein the transmission configuration information includes configuration information corresponding to the relay node before migration and / or configuration information corresponding to the migration; perform data packet transmission and / or processing based on the fifth message.

[0734] It is understood that the communication device provided in the embodiments of this application is a device corresponding to the method provided in this application. The description of the relevant steps or terms in the device can be referred to the corresponding explanation in the method section above, and will not be repeated here.

[0735] In one alternative embodiment, an electronic device is provided, such as Figure 11 As shown, Figure 11 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0736] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0737] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 11 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0738] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0739] The memory 4003 stores application code that executes the scheme of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the application code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.

[0740] This application provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments.

[0741] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0742] The above description is only a partial embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A communication method executed by a first integrated access and backhaul IAB node, characterized in that, The method includes: Receive a message from the second IAB node, the message including a first Radio Resource Control (RRC) message for the third IAB node, and an indication to retain the first RRC message; Determine whether the conditions for sending the first RRC message are met; If the conditions for sending the first RRC message are met, send the first RRC message to the third IAB node; Among them, the first IAB node is a child node of the migrated IAB node; The second IAB node is the IAB anchor node; The third IAB node is a child node of the first IAB node.

2. The method according to claim 1, characterized in that, The conditions for sending the first RRC message include: the first IAB node receives a second RRC message, the second RRC message including information related to migration.

3. The method according to claim 2, characterized in that, The migration-related information includes at least one of the following: the new network protocol IP address, the routing identifier, and the backhaul radio link control (RLC) channel identifier.

4. The method according to claim 1, characterized in that, The message includes a User Equipment (UE) Context Modification Request message.

5. The method according to any one of claims 1 to 4, characterized in that, The second IAB node is a centralized unit of the IAB anchor node, and the first IAB node is a distributed unit of the IAB.

6. A communication method executed by a second IAB node, characterized in that, The method includes: Generate a message, wherein the message includes a first Radio Resource Control (RRC) message for the third IAB node and an indication to retain the first RRC message; Send the message to the first IAB node, wherein the first IAB node is a child node of the migrated IAB node; Wherein, the first RRC message is sent by the first IAB node to the third IAB node when the conditions for sending the first RRC message are met; The second IAB node is the IAB anchor node; The third IAB node is a child node of the first IAB node.

7. The method according to claim 6, characterized in that, The conditions for sending the first RRC message include: the second RRC message is received by the first IAB node, and the second RRC message includes information related to migration.

8. The method according to claim 7, characterized in that, The migration-related information includes at least one of the following: the new network protocol IP address, the routing identifier, and the backhaul radio link control (RLC) channel identifier.

9. The method according to claim 6, characterized in that, The message includes a User Equipment (UE) Context Modification Request message.

10. The method according to any one of claims 6 to 9, characterized in that, The second IAB node is a centralized unit of the IAB anchor node, and the first IAB node is a distributed unit of the IAB.

11. A first IAB node, characterized in that, The first IAB node includes a transceiver configured to transmit and receive signals, and at least one processor coupled to the transceiver, the at least one processor being configured to perform the method of any one of claims 1-5.

12. A second IAB node, characterized in that, The second IAB node includes a transceiver configured to transmit and receive signals, and at least one processor coupled to the transceiver, the at least one processor being configured to perform the method of any one of claims 6-10.

13. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the method of any one of claims 1-10.

Citation Information

Patent Citations

  • Data packet forwarding method, radio relay node, and communication system

    CN107113250A

  • Transmission Method and Network Device

    CN110326321A