Node in communication network and method thereof

Abstract

The present invention provides a node in a communication system and a method thereof, the method comprising: receiving a first configuration message from a second node; and sending a first configuration completion message to a third node, wherein before receiving the first configuration message from the second node, a first request message is sent from the second node to the third node, and a first response message is sent from the third node to the second node.

Description

Technical Field

[0001] The present application relates to wireless communication technology, and in particular to a mechanism for user equipment handover in a multi-hop network and a device and method for exchanging user-related contexts between a centralized unit and a distributed unit of a base station. Background Art

[0002] In the research of NR (New Radio access) network Release 16, in order to extend the coverage of the network, the IAB (Integrated Access and Backhaul) project was proposed. The main purpose of this project is to build a multi-hop network architecture. Figure 1The schematic architecture of a multi-hop network is shown, including a network architecture consisting of one anchor node (IABdonor) and two relay nodes (IAB nodes). Users in this multi-hop network can access the network through the anchor node, its distribution unit, or a relay node. For example, users 1, 2, and 3 access the relay network through the anchor node's distribution unit, the distribution unit portion of relay node 1, and the distribution unit portion of relay node 2, respectively. The anchor node can be an independent base station or a base station composed of a centralized unit (CU) and a distributed unit (DU). A relay node includes a mobile terminal portion and a distribution unit portion, wherein the mobile terminal portion is used to communicate with the relay node's upper-level node (e.g., the mobile terminal portion of relay node 1 is used to communicate with the anchor node or the anchor node's distribution unit, and the mobile terminal portion of relay node 2 is used to communicate with the distribution unit portion of relay node 1), and the distribution unit portion is used to communicate with the relay node's lower-level 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). The mobile terminal portion of a relay node can be regarded as a user accessing the network, so it has the functions of an ordinary user (non-relay node) (e.g., the mobile terminal portion can establish a signaling radio bearer (SRB) with its upper-level node to send radio resource control (RRC) messages, and can also establish a data radio bearer (DRB) to send data). The protocol stacks included in the centralized unit of an anchor node include: the service control plane protocol stack, which includes the Radio Resource Control (RRC) protocol layer and the Packet Data Convergence Protocol (PDCP) layer; and the service user plane protocol stack, which includes the Service Data Adaptation Protocol (SDAP) layer and the PDCP layer. The protocol stacks included in the distributed unit of an anchor node or the distributed unit portion of a relay node include: the service control plane and user plane protocol stacks, which include the Radio Link Control (RLC) protocol layer, the Medium Access Control (MAC) protocol layer, and the Physical (PHY) layer. The interface between the centralized unit of an anchor node and the distributed unit of an anchor node, as well as between the centralized unit of an anchor node and the distributed unit portion of a relay node, is the F1 interface (see 3GPP TS 38.473).

[0003] In a relay network, the link between a relay node and an anchor node or a distribution unit of an anchor node, or between relay nodes, is a backhaul link. One or more different backhaul link channels are established on the backhaul link, such as Figure 1 The backhaul link channel 1 and the backhaul link channel 2 in the relay network are as follows: the backhaul link channel 1 is located between the anchor node and the relay node 1, and the backhaul link channel 2 is located between the relay node 1 and the relay node 2. An example of a backhaul link channel is a backhaul link radio link control (RLC) protocol layer channel, i.e., a Backhaul Link RLC channel. In a relay network, each backhaul link channel is used to send data packets belonging to the same user or different users. The data packet can be a data packet of a user data radio bearer (DRB), a data packet of a user signaling radio bearer (SRB), a data packet of the control plane on the F1 interface, a data packet of the user plane on the F1 interface, or a data packet of a non-F1 interface (such as an Internet Protocol Security (IPSec) data packet, a Stream Control Transmission Protocol (SCTP) data packet, an Operation Administration and Maintenance (OAM) data packet, etc.).

[0004] In order to realize the transmission of user data in a multi-hop relay network, 3GPP defines a new protocol layer, namely the Backhaul Adaptation Protocol Layer (BAP). This protocol layer will be configured in the distribution unit of the anchor node and the relay node (such as the mobile terminal part of the relay node and / or the distribution unit part of the relay node), located above the RLC layer. Its main function is to route and map data packets. Data packet routing refers to sending the received data packet to the correct next-hop node so that it can be received by the destination receiving node of the data packet. The destination receiving node can be a relay node, an anchor node, a distribution unit of an anchor node, or a centralized unit of an anchor node. If it is a relay node, it means that the data packet is a data packet of the relay node, such as the control signaling data packet of the F1 interface that the distribution unit part of the relay node needs to receive, the data packet of the user accessing the relay node, etc. Data packet mapping refers to sending the data packet to the correct backhaul link channel.

[0005] A new address information (such as a BAP address) is defined for nodes in a relay network (such as relay nodes, or distribution units of anchor nodes, or centralized units of anchor nodes, or anchor nodes). This address information can be used to identify a node in the relay network and is used for routing data packets within the relay network. If a data packet contains the BAP address of a node (such as a relay node, or distribution unit of an anchor node, or centralized unit of an anchor node, or anchor node), it indicates that the destination receiving node of the data packet is that node, or that the source sending node of the data packet is that node. Furthermore, multiple transmission paths may exist between an anchor node (or centralized unit of an anchor node, or distribution unit of an anchor node) and a relay node. To indicate different transmission paths, a path identifier (Path ID) is also defined. Different path identifiers indicate different paths to the same node. The data packet's path identifier may also be included in the data packet. After a node in the relay network receives a data packet, it determines the next hop node for the data packet based on the BAP address and / or Path ID contained in the data packet, thereby completing the data packet routing.

[0006] The above information is provided as background information only to assist with an understanding of the present invention. No determination has been made, and no assertion is made, as to whether any of the above may be applicable as prior art with respect to the present invention. Summary of the Invention

[0007] Technical issues

[0008] Current research assumes that the anchor node to which the relay node is connected will not change. However, in actual networks, due to certain reasons (such as load balancing, relay node mobility, etc.), the anchor node to which the relay node is connected will change, that is, the relay node will migrate (or switch) between different anchor nodes. In the present invention, the migration and switching of relay nodes are not distinguished and are used interchangeably. During the migration process, users accessing the relay node will also be affected. Traditional technologies cannot well support the migration of relay nodes. The main problems are: how to update the configuration of users served by the relay node during the relay node migration process, and how to reduce the signaling overhead during the configuration update process.

[0009] The solution of traditional technology is: during the relay node migration process, all users are disconnected from the relay node, and then each user starts the reconstruction process to re-establish the connection with the network.

[0010] Solution

[0011] According to one aspect of the present invention, a method performed by a first node in a communication system is provided, comprising: receiving a first configuration message from a second node; and sending a first configuration completion message to a third node, wherein, before receiving the first configuration message from the second node, a first request message is sent from the second node to the third node, and a first response message is sent from the third node to the second node.

[0012] According to another aspect of the present invention, a method performed by a second node in a communication system is provided, comprising: sending a first request message to a third node; receiving a first response message from the third node; and sending a first configuration message to the first node, wherein, after sending the first configuration message to the first node, a first configuration completion message is sent from the first node to the third node.

[0013] According to another aspect of the present invention, a method performed by a third node in a communication system is provided, comprising: receiving a first request message from a second node; sending a first response message to the second node; and receiving a first configuration completion message from the first node, wherein the first configuration message is sent from the second node to the first node before the first configuration completion message is received from the first node.

[0014] In the method of the present invention, the first request message may be a switching request message for the first node, and may include at least one of first user configuration information, first backhaul link channel configuration information, first address-related information, and first configuration information of aggregated data; the first response message may be a switching response message for the first node, and may include at least one of second user configuration information, second mapping relationship information, second backhaul link channel configuration information, and second address-related information; and the first configuration message may be used to provide the configuration information required for the first node to migrate and / or after migration, and may include at least one of third user configuration information, third mapping relationship information, third backhaul link channel configuration information, and third address-related information.

[0015] In the method of the present invention, the first user configuration information, the second user configuration information and the third user configuration information are configuration information of the user served by the first node, and each may include at least one of a user identifier and information related to the user's radio bearer.

[0016] In the method of the present invention, the information related to the user's wireless bearer may include at least one of the following information: user identification, identification information of the user's wireless bearer, identification information, information related to the quality of service QoS of the wireless bearer, configuration information of the wireless bearer serving the user, information related to the QoS satisfied by the relay node, information related to the QoS satisfied by the non-relay node, information related to the tunnel of uplink data, information related to the tunnel of downlink data, information related to data forwarding, first tunnel information and second tunnel information.

[0017] In the method of the present invention, the second mapping relationship information and the third mapping relationship information can reflect the mapping relationship of the information used by the first node before and after the migration occurs, and may include at least one of the following information: address mapping information, tunnel mapping information, routing identifier mapping information, next hop node mapping information, return link channel mapping information, applicable information, and exception information.

[0018] According to another aspect of the present invention, there is provided a method performed by a first node in a communication system, comprising: receiving a first configuration request message from a fourth node; and sending a first configuration response message to the fourth node.

[0019] According to another aspect of the present invention, there is provided a method performed by a fourth node in a communication system, comprising: sending a first configuration request message to a first node; and receiving a first configuration response message from the first node.

[0020] In the method of the present invention, the first configuration request message can be used to update the configuration of the first node, and may include at least one of fifth address-related information, fifth user configuration information, and fifth mapping relationship information; and the first configuration response message can be used to confirm the first configuration request message, and may include at least one of sixth user configuration information and sixth mapping relationship information.

[0021] In the method of the present invention, the fifth user configuration information can be used by the fourth node to provide updated configuration information for each user of the first node respectively, and the fifth mapping relationship information can be used by the first node to update multiple configurations simultaneously.

[0022] In the method of the present invention, the sixth user configuration information can be used by the first node to provide updated configuration information for each user respectively, and the sixth mapping relationship information can be used by the fourth node to update multiple configurations simultaneously.

[0023] According to another aspect of the present invention, there is provided a method performed by a fifth node in a communication system, comprising: sending a third configuration request message to a sixth node; and receiving a third configuration response message from the sixth node.

[0024] According to another aspect of the present invention, there is provided a method performed by a sixth node in a communication system, comprising: receiving a third configuration request message from a fifth node; and sending a third configuration response message to the fifth node.

[0025] In the method of the present invention, the third configuration request message can be used to provide configuration information related to the data served by the first node, and may include at least one of the seventh user configuration information and the information related to the first control signaling; and the third configuration response message can be used to provide configuration information related to the data served by the first node, and may include at least one of the eighth user configuration information, the information related to the second control signaling and the eighth mapping relationship information.

[0026] In the method of the present invention, the sixth node can obtain the configuration information of the data of the user accessing the first node through the seventh user configuration information.

[0027] In the method of the present invention, the eighth mapping relationship information can be used to update configuration information used by the first node when transmitting data. According to another aspect of the present invention, a method performed by a fifth node in a communication system is provided, comprising: receiving a fifth configuration request message from a sixth node; and sending a fifth configuration response message to the sixth node.

[0028] According to another aspect of the present invention, there is provided a method performed by a sixth node in a communication system, comprising: sending a fifth configuration request message to a fifth node; and receiving a fifth configuration response message from the fifth node.

[0029] In the method of the present invention, the fifth configuration request message can be used to update the configuration information of the data serving the first node to the fifth node, and can include at least one of the eighth user configuration information and the information related to the third control signaling; and the fifth configuration response message can be used to feedback the result of the configuration update, and can include at least one of the ninth user configuration information and the information related to the fourth control signaling.

[0030] According to yet another aspect of the present invention, a node for executing one of the above methods is provided, including an anchor node and a relay node.

[0031] Technical Effects

[0032] A technical effect of the present invention is to provide continuous services to users and reduce signaling interactions by exchanging user configuration information during or after relay node migration and then updating the user configuration information at the relay node.

[0033] Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description of various embodiments of the invention, which, taken in conjunction with the annexed drawings, discloses. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The above and other aspects, features and advantages of certain embodiments of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0035] Figure 1 This is a schematic architecture of a multi-hop network.

[0036] Figure 2 This is an example of the migration of a relay node according to an embodiment of the present invention.

[0037] Figure 3 This is an example of a method for transmitting data after a relay node has migrated according to an embodiment of the present invention.

[0038] Figure 4 This is an example of a relay node migration process according to an embodiment of the present invention.

[0039] Figure 5 This is an example of a configuration update process of a relay node according to an embodiment of the present invention.

[0040] Figure 6 This is an example of a configuration interaction process of a relay node according to an embodiment of the present invention.

[0041] Figure 7 This is another example of the configuration interaction process of the relay node according to an embodiment of the present invention.

[0042] Figure 8 This is an example of a relay node migration and configuration update process according to an embodiment of the present invention.

[0043] Figure 9 This is an example of the migration and configuration interaction process of a relay node according to an embodiment of the present invention.

[0044] Figure 10 This is another example of the migration and configuration interaction process of the relay node according to an embodiment of the present invention.

[0045] Figure 11 is a block diagram of an anchor node according to an embodiment of the present invention.

[0046] Figure 12 is a block diagram of a relay node according to an embodiment of the present invention. DETAILED DESCRIPTION

[0047] The following description, with reference to the accompanying drawings, is provided to facilitate a comprehensive understanding of the various embodiments of the present invention as defined by the claims and their equivalents. It includes various specific details to assist in such understanding, but these details are to be regarded as merely illustrative. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present invention. Furthermore, descriptions of well-known functions and configurations may be omitted for clarity and conciseness.

[0048] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the invention. Therefore, it should be understood by those skilled in the art that the following description of various embodiments of the invention is provided for illustration purposes only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents.

[0049] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0050] In addition, the detailed description of the embodiments of the present invention is mainly based on a wireless communication system of a multi-hop network, especially a relay network, but without departing from the scope of the present invention, the subject matter of the present invention can be applied to other communication systems with similar technical backgrounds and channel forms after slight modifications, and can be determined by those skilled in the art.

[0051] The advantages and features of the present invention and the manner in which they are achieved will become apparent by reference to the various embodiments described in detail below in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments set forth below, but may be implemented in a variety of different forms. The following embodiments are provided only to fully disclose the present invention and to inform those skilled in the art of the scope of the present invention, and the present invention is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals designate the same or similar elements.

[0052] Here, it will be understood that each step in the flowchart illustration, as well as the combination of steps in the flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device create a means for implementing the functions specified in the flowchart. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including instruction means for implementing the functions specified in the flowchart. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operations performed on the computer or other programmable device produce a computer-implemented process, such that the instructions executed on the computer or other programmable device provide operations for implementing the functions specified in the flowchart.

[0053] And each block in the flowchart description can represent a module, segment or portion of code, which includes one or more executable instructions for implementing the specified (multiple) logical functions. It should also be noted that in some alternative implementations, the functions or steps marked in the flowchart may not occur in sequence. For example, depending on the functions involved, two steps shown in succession can actually be performed substantially simultaneously, or sometimes the steps can be performed in reverse order. In some cases, multitasking and parallel execution may be advantageous.

[0054] As used herein, "unit" or "module" refers to a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, a "unit" or "module" is not always limited to the meaning of software or hardware. A "unit" or "module" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, a "unit" or "module" for example includes a software element, an object-oriented software element, a class element or a task element, processing, a function, an attribute, a process, a subroutine, a segment of program code, a driver, firmware, microcode, a circuit, data, a database, a data structure, a table, an array and a parameter. The elements and functions provided by a "unit" or "module" can be combined into a smaller number of element "units" or "modules", or divided into a larger number of element "units" or "modules". In addition, an element "unit" or "module" can be implemented to reproduce one or more central processing units (CPUs) in a device or a secure multimedia card.

[0055] The various aspects of the invention as generally described herein and illustrated in the accompanying drawings may be arranged, substituted, combined, separated, and designed in a variety of different configurations, all of which are contemplated herein. In addition, the features shown in each of the accompanying drawings may be used in conjunction with each other unless the context dictates otherwise. Therefore, the accompanying drawings should be considered as Figure 1 The illustrated features are generally considered to be part of one or more general embodiments, and it is understood that not all illustrated features are required for each embodiment.

[0056] It will be understood that although the terms "first," "second," etc. may be used herein to describe different elements, components, and / or parts, these elements, components, and / or parts should not be limited by these terms. These terms are merely used to distinguish one element, component, and / or part from another element, component, and / or part. Thus, the first element, first component, and / or first part discussed below could also be referred to as the second element, second component, and / or second part without departing from the teachings of the present invention.

[0057] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the present invention. It will also be understood that when the words "include" and / or "comprise" are used in this specification, it indicates the presence of the described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements and / or components, and any combination thereof.

[0058] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those skilled in the art to which the present invention belongs. It will also be understood that those terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and should not be interpreted in an idealized or overly formal manner unless explicitly defined as such herein.

[0059] 1. Composition of the Invention

[0060] The present invention generally includes three aspects: a relay node migration process; a relay node configuration update process; and a relay node configuration interaction process. The present invention is not limited to the above three aspects, and includes any steps in the example methods of these three aspects and any combination thereof.

[0061] 2. Embodiments of the invention

[0062] The message names in the present invention are only examples, and other message names may also be used.

[0063] The terms "first", "second", etc. included in the message or information names used in the present invention are used to describe different messages or information, and do not indicate the order in which the messages or information are sent.

[0064] Detailed descriptions of steps not related to the present invention are omitted.

[0065] The migration of the relay node considered in the present invention may also be considered as the switching of the relay node.

[0066] Figure 2 This is an example of the migration of a relay node according to an embodiment of the present invention. Figure 2 As shown, before the relay node 3 migrates, the relay node 3 accesses the network through the relay node 1 (for example, connected to the source anchor node); and after the migration, the relay node 3 accesses the network through the relay node 2 (for example, connected to the target anchor node). Figure 2 In the example, relay node 1 and relay node 2 are connected to different anchor nodes. More specifically, relay node 1 is connected to the source anchor node, while relay node 2 is connected to the target anchor node. Figure 2 In the figure, before migration, there is only one relay node 1 between relay node 3 and the source anchor node. However, in an actual network, relay node 3 can connect to the source anchor node directly or through one or more relay nodes. Similarly, after migration, relay node 3 can connect to the target anchor node directly or through one or more relay nodes.

[0067] For the convenience of explanation, the following description of the present invention is based on Figure 2 The network shown in the figure is taken as an example, but the application scope of the mechanism in the present invention is not limited to Figure 2 The network shown.

[0068] During the relay node migration process, different migration mechanisms result in different methods for relay nodes to transmit data after migration occurs. Figure 3 This is an example of a method for transmitting data after a relay node has been migrated according to an embodiment of the present invention. The present invention considers the following three methods for transmitting data of a relay node:

[0069] (1) Method 1: After migration, the distributed unit of the relay node is connected to the centralized unit of the target anchor node, such as Figure 3 As shown in (a), the transmission path of the data of the distribution unit part of the relay node 3 (such as the data of the users served by the distribution unit part of the relay node 3, and the data generated by the distribution unit part of the relay node 3 (such as F1AP signaling)) is:

[0070] ■ Uplink: Distribution unit of relay node 3 → relay node 2 → distribution unit of target anchor node → centralized unit of target anchor node

[0071] ■ Downlink: Centralized unit of target anchor node → Distributed unit of target anchor node → Relay node 2 → Distributed unit of relay node 3

[0072] In this method, the users served by the relay node need to be migrated to the target anchor node. Thus, the configuration interaction related to each user needs to be carried out between the source anchor node and the target anchor node during the migration process. After the migration is completed, the relay node is controlled by the target anchor node, and the backhaul link channel (such as Figure 3 In (a), the backhaul link channel between relay node 3 and relay node 2, and the backhaul link channel between relay node 2 and the target anchor node's distribution unit, are also controlled by the target anchor node. The transmission path between the relay node and the target anchor node is also controlled by the target anchor node. This method has the beneficial effect of completely controlling the data transmission of the relay node after migration. However, this method requires the migration of all users connected to the relay node during the migration process, which introduces excessive signaling interactions and increases the latency of user migration.

[0073] (2) Method 2: After migration, the distributed unit of the relay node still maintains the connection with the centralized unit of the source anchor node, such as Figure 3 As shown in (b), the transmission path of the data of the distribution unit part of the relay node 3 (such as the data of the users served by the distribution unit part of the relay node 3, and the data generated by the distribution unit part of the relay node 3 (such as F1AP signaling)) is:

[0074] ■ Uplink: Distribution unit of relay node 3 → relay node 2 → distribution unit of target anchor node → centralized unit of source anchor node

[0075] ■ Downlink: Centralized unit of source anchor node → distributed unit of target anchor node → relay node 2 → distributed unit of relay node 3

[0076] In this method, only the mobile terminal portion of the relay node undergoes handover; the distributed unit portion of the relay node remains connected to the centralized unit of the source anchor node. This allows users accessing the relay node to remain connected to the source anchor node. This advantageously reduces the exchange of user-related configuration information during the migration process, reduces configuration updates for each user, and thus reduces signaling interactions. Furthermore, the data of the distributed unit portion of the relay node is carried by the backhaul link channel between relay node 3 and relay node 2, and by the backhaul link channel between relay node 2 and the distributed unit of the target anchor node. The configuration of these channels is controlled by the target anchor node, and the transmission path of the data of the distributed unit portion of the relay node is also controlled by the target anchor node. Therefore, this method requires the source anchor node to provide the target anchor node with configuration information related to the data transmission of the distributed unit portion of the relay node, thereby assisting the target anchor node in configuring the backhaul link channel and transmission path. The target anchor node, in turn, needs to provide the source anchor node with configuration information related to data transmission, thereby assisting the source anchor node in performing data transmission and configuration according to the configuration of the target anchor node. In this way, after the relay node completes migration, the source anchor node and the target anchor node need to maintain signaling interaction, and then perform configuration related to data transmission of the distribution unit part of the relay node.

[0077] (3) Method 3: After migration, the distributed unit of the relay node still maintains the connection with the centralized unit of the source anchor node, such as Figure 3 As shown in (c), the transmission path of the data of the distribution unit part of the relay node 3 (such as the data of the users served by the distribution unit part of the relay node 3, and the data generated by the distribution unit part of the relay node 3 (such as F1AP signaling)) is:

[0078] ■ Uplink: Distributed unit of relay node 3 → relay node 2 → distributed unit of target anchor node → centralized unit of target anchor node → centralized unit of source anchor node

[0079] ■ Downlink: Centralized unit of source anchor node → Centralized unit of target anchor node → Distributed unit of target anchor node → Relay node 2 → Distributed unit of relay node 3

[0080] This method is similar to Method 2, except that data transmission between the relay node's distributed unit and the source anchor node's centralized unit must pass through the target anchor node's centralized unit. This method has the beneficial effect of reducing the exchange of user-related configuration information during the migration process, as well as the number of configuration updates required for each user, thereby reducing signaling interactions. Similarly to Method 2, after the relay node completes migration, signaling interactions must continue between the source and target anchor nodes to configure data transmission within the relay node's distributed unit.

[0081] It should also be noted that although this article combines Figure 3 The following embodiments (including embodiments 1-1-1 to 1-3-2 and embodiments 4-1 to 4-3, etc.) are described. However, due to Figure 3 After the relay node 3 in the example is migrated, the relay node 2 is only a relay node on the message transmission path between the relay node 3 and the target anchor node, and has no special contribution to the update of the configuration information of the user served by the relay node 3. Figures 4 to 10 The steps of each described process only focus on and describe the message transmission between the relay node undergoing migration and the source anchor node and / or the target anchor node, and the description of the relay node 2 is omitted.

[0082] The nodes involved in the present invention are as follows:

[0083] ■First node: relay node, or the distribution unit part of relay node

[0084] ■ Second node: source node, which can be an anchor node, or a centralized unit of an anchor node, or a control plane portion of a centralized unit of an anchor node, or a user plane portion of a centralized unit of an anchor node

[0085] ■ Third node: target node, which can be an anchor node, or a centralized unit of an anchor node, or a control plane portion of a centralized unit of an anchor node, or a user plane portion of a centralized unit of an anchor node

[0086] ■Fourth node: Anchor node, or a centralized unit of an anchor node, or a control plane portion of a centralized unit of an anchor node, or a user plane portion of a centralized unit of an anchor node; in one embodiment, the fourth node may be the third node, the second node, or other nodes

[0087] ■Fifth node: Anchor node, or a centralized unit of an anchor node, or a control plane portion of a centralized unit of an anchor node, or a user plane portion of a centralized unit of an anchor node; in one embodiment, the fifth node may be the second node mentioned above, or other nodes

[0088] ■ Sixth node: Anchor node, or a centralized unit of an anchor node, or a control plane portion of a centralized unit of an anchor node, or a user plane portion of a centralized unit of an anchor node; in one embodiment, the sixth node may be the third node mentioned above, or other nodes

[0089] The second node and the third node may be the same node or different nodes.

[0090] The key information involved in this invention is as follows:

[0091] User configuration information , the user is a user accessing the relay node, and the information includes at least one of the following information:

[0092] User identifiers, such as the gNB-CU / DU UE F1AP ID (gNB-Central Unit / Distributed Unit User Equipment F1 Application Protocol Identifier), the cell-Radio Network Temporary Identifier (C-RNTI), and the UE XnAP ID (User Equipment XnApplication Protocol Identifier).

[0093] Information about the user's radio bearer. For a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB), this information includes at least one of the following:

[0094] ■User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0095] ■ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0096] ■Identification information, such as DRB ID, SRB ID

[0097] ■ Information about the Quality of Service (QoS) of the radio bearer, which includes the configuration information of the QoS parameters of the radio bearer, including but not limited to non-dynamic 5QI descriptor, dynamic 5QI descriptor, allocation and retention priority, GBR QoS Flow Information, etc. For specific information, please refer to 3GPP TS38.473. In one embodiment, this information is the actual QoS information of the radio bearer; in another embodiment, this information is the QoS information that needs to be met by the receiving node, and this QoS information is different from the above-mentioned "actual QoS information of the radio bearer".

[0098] ■Configuration information of the service user radio bearer, such as SDAP layer configuration, PDCP layer configuration, RLC layer configuration, and configuration information of the radio bearer logical channel (such as identification information, logical channel priority information), etc., can be seen in CellGroupConfiguration

[0099] ■Information about the QoS satisfied by the relay node. This information is used to indicate information about the QoS that the relay node can satisfy when serving the wireless bearer. This information is different from the above-mentioned "information about the QoS of the wireless bearer". The beneficial effect of this information is that the node that receives this information can learn the QoS that the relay node can satisfy when serving the user's wireless bearer, and determine how to configure other nodes to serve the user's wireless bearer, so that the relay node and other nodes can jointly serve the user's wireless bearer and meet the QoS requirements of the wireless bearer. Another beneficial effect is that the node that receives this information can try to configure the relay node to serve the user's wireless bearer according to the QoS indicated by this information, thereby eliminating the need to modify the configuration information of the relay node when serving the user's wireless bearer.

[0100] ■Information about the QoS satisfied by non-relay nodes. This information is used to indicate information about the QoS satisfied when other nodes in the network, excluding the relay node, jointly serve the wireless bearer. This information is different from the above-mentioned "information about the QoS of the wireless bearer." The beneficial effect of this information is that the node receiving this information can learn about the QoS that other nodes, excluding the relay node, need to satisfy when serving the user's wireless bearer, and determine how to configure other nodes to serve the user's wireless bearer, so that the relay node and other nodes can jointly serve the user's wireless bearer and meet the QoS requirements of the wireless bearer. Another beneficial effect is that the node receiving this information can try to configure other nodes to serve the user's wireless bearer according to the QoS indicated by this information, without having to modify the configuration information of the relay node when serving the user's wireless bearer.

[0101] Information about uplink data tunnels. This uplink data is data sent from a relay node to an anchor node. The tunnels may be one or more. This information indicates user-side information of the anchor node, its centralized unit, or its centralized unit. For each tunnel, this information includes at least one of the following:

[0102] ◆Tunnel identification information, which can be used to indicate a tunnel. Different identification information indicates different tunnels.

[0103] Internet Protocol (IP) address

[0104] Tunnel Endpoint Identifier (TEID)

[0105] Routing identification information, which is used to indicate the transmission path of the above-mentioned uplink data (further, the uplink data is sent through the above-mentioned tunnel), including the address information of the receiving node (BAP address) and / or the transmission path identification information (path ID). Furthermore, based on this information, the relay node can add this information to the uplink data packet sent through the above-mentioned tunnel

[0106] ◆The identification information of the next hop node. The next hop node is the node that directly receives the uplink data when the relay node sends the uplink data (furthermore, the uplink data is sent through the above tunnel). In other words, the relay node sends the uplink data to the next hop node, which then sends the uplink data directly or indirectly (through other nodes) to the destination node of the uplink data. Based on this information, the relay node knows which node to send the uplink data to.

[0107] ◆ Identification information of the backhaul link channel. The backhaul link channel is the backhaul link channel used by the relay node to send the uplink data (furthermore, the uplink data is sent through the above tunnel) to the above next-hop node. Based on this information, the relay node knows which backhaul link channel to use to send the uplink data.

[0108] One beneficial effect of including this information is that the receiving node can update the configuration of the uplink tunnel of the user data based on the information, and obtain the configuration of the uplink data transmission, such as the transmission path of the uplink data packet, the information to be added in the uplink data packet, the next hop node for receiving the uplink data packet, and the return link channel used to transmit the uplink data packet; another beneficial effect of including this information is that the receiving node can obtain the configuration information of the uplink tunnel of the wireless bearer served by the relay node, thereby helping the receiving node to update the configuration information of the uplink tunnel; another beneficial effect of including this information is that the receiving node can configure the uplink tunnel of the wireless bearer served by the relay node based on the received information.

[0109] Information about downlink data tunnels. Downlink data is data sent from an anchor node to a relay node. The tunnels may be one or more. This information indicates information about the relay node or its distribution unit. For a tunnel, this information includes at least one of the following:

[0110] ◆Tunnel identification information, which can be used to indicate a tunnel. Different identification information indicates different tunnels.

[0111] IP address

[0112] ◆TEID

[0113] The configuration value information of the Differentiated Services Code Point (DSCP) field in the downlink data packet (furthermore, the downlink data packet is sent through the above tunnel)

[0114] The configuration value information of the flowlabel field in the downlink data packet (furthermore, the downlink data packet is sent through the above tunnel)

[0115] One beneficial effect of including this information is that the receiving node can update the configuration of the downlink tunnel of the user data based on the information and obtain the configuration of the downlink data transmission, such as the information contained in the downlink data packet (such as the DSCP field configuration value, the flow label field configuration value); another beneficial effect of including this information is that the receiving node can know how to send downlink data to the relay node, such as the address for receiving downlink data and the information required to be included in the downlink data packet (such as the DSCP field configuration value, the flow label field configuration value); another beneficial effect of including this information is that the receiving node can configure the downlink tunnel of the wireless bearer served by the relay node based on the received information.

[0116] ■ Information related to data forwarding. This data forwarding refers to node 1 (e.g., a source anchor node, a centralized unit of a source anchor node, or the user plane portion of a centralized unit of a source anchor node) sending user radio bearer data to node 2 (e.g., a target anchor node, a centralized unit of a target anchor node, or the user plane portion of a centralized unit of a target anchor node). This information related to data forwarding can help determine whether data needs to be sent from node 1 to node 2, and can also help determine the address of node 2 to which the data is sent. The data to be sent can be uplink data or downlink data. For uplink data or downlink data, this information includes at least one of the following information:

[0117] ◆Suggest whether data forwarding is needed

[0118] ◆IP address, which is the address on the node 2 side

[0119] TEID, which is the TEID of node 2

[0120] ■ First tunnel information, which indicates address-related information used by the anchor node when receiving user data from other anchor nodes. In one embodiment, after receiving the data, the anchor node will also forward it to the relay node. This information includes at least one of the following information:

[0121] ◆Tunnel identification information

[0122] IP address

[0123] ◆TEID

[0124] Second tunnel information, which indicates address-related information used by the anchor node when receiving user data from the relay node. In one embodiment, the anchor node will forward the received data to other anchor nodes. This information includes at least one of the following:

[0125] ◆Tunnel identification information

[0126] IP address

[0127] ◆TEID

[0128] Address-related information required by relay nodes The information is information related to addresses required for communication between a relay node (or a distributed unit portion of a relay node) and an anchor node (or a centralized unit of an anchor node, or a control plane portion of a centralized unit of an anchor node, or a user plane portion of a centralized unit of an anchor node), and includes at least one of the following information:

[0129] ■ Address information on the relay node side. The address indicated by this information may be the address on the relay node side or the distributed unit part of the relay node. This information includes at least one of the following information:

[0130] ■ The identification information of the relay node side address, which is used to indicate the relay node side address. If the identification information is different, it means that the relay node side address it indicates is different.

[0131] ■BAP address information

[0132] IP address information

[0133] ■TEID, such as GTP-TEID (GTP-Tunnel Endpoint Identifier)

[0134] ■Port information

[0135] ■The number of addresses required. This information is used to inform the receiving node: the number of addresses required by the relay node. After receiving this information, the receiving node will provide addresses for the relay node according to this information.

[0136] ■Indication of purpose, which indicates the purpose of the above address. Possible purposes include: sending user-related control signaling (such as UE-associated F1AP (UE-associated F1 Application Protocol)), sending non-user-related control signaling (such as non-UE-associated F1AP), sending user-related control information and non-user-related control information, sending user data, sending control signaling type 1 data, sending control signaling type 2 data, sending control signaling type 3 data, etc.

[0137] ■ Identification information of one or more users served. The address of the relay node may serve one or more users.

[0138] ■ Identification information of one or more user radio bearers served, such as UE RB ID. This information can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0139] ■ Identification information of one or more radio bearers served, such as RB ID

[0140] ■ Information about the address of the anchor node. The address indicated by this information may be on the anchor node side, or on the centralized unit side of the anchor node, or on the control plane portion of the centralized unit of the anchor node, or on the user plane portion of the centralized unit of the anchor node. This information includes at least one of the following information:

[0141] ■ The identification information of the anchor node's address. This identification information is used to indicate the anchor node's address. If the identification information is different, it indicates that the anchor node's address is different.

[0142] ■BAP address information

[0143] IP address information

[0144] ■TEID, such as GTP-TEID (GTP-Tunnel Endpoint Identifier)

[0145] ■Port information

[0146] ■Indication of purpose, which indicates the purpose of the above address. Possible purposes include: sending user-related control signaling (such as UE-associated F1AP), sending non-user-related control signaling (such as non-UE-associated F1AP), sending user-related control information and non-user-related control information, sending user data, sending control signaling type 1 data, sending control signaling type 2 data, sending control signaling type 3 data, etc.

[0147] ■ Identification information of one or more users served. The address of the anchor node mentioned above may serve one or more users.

[0148] ■ Identification information of the radio bearer of one or more users served, such as UE RB ID. This information can indicate a radio bearer of a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer of the user.

[0149] ■ Identification information of one or more radio bearers served, such as RB ID

[0150] Mapping information , which is used to reflect the information update used by the relay node, and includes at least one of the following information:

[0151] ■ Address mapping information. For an address mapping, this information includes at least one of the following:

[0152] ■ The identification information of the relay node side address, which is used to indicate the relay node side address. If the identification information is different, it means that the relay node side address it indicates is different.

[0153] ■ Information about the address of the new relay node. The content of this information can be found in the above “ middle Address-related information required by the relay node "Address information on the relay node side"

[0154] ■ Information about the address of the old relay node. The content of this information can be found in the above “ middle Address-related information required by the relay node "Address information on the relay node side"

[0155] ■ The identification information of the anchor node's address. This identification information is used to indicate the anchor node's address. If the identification information is different, it indicates that the anchor node's address is different.

[0156] ■ Information about the address of the new anchor node. The content of this information can be found in the above “ relay Address-related information required by the node "Anchor node side address information"

[0157] ■ Information about the old anchor node's address. The information contained in this information can be found in the above " relay Address-related information required by the node "Anchor node side address information"

[0158] Tunnel mapping information. For a tunnel mapping, this information includes at least one of the following:

[0159] ■ Identification information of the uplink data tunnel, which can be used to indicate which uplink tunnel. Different identification information indicates different uplink tunnels. In one embodiment, the identification information can remain unchanged when the uplink data tunnel related information is updated. This information can be sent by the anchor node to the relay node when configuring the user's uplink tunnel, such as the information included in the UE Context Setup / Modification Request message for each uplink data tunnel.

[0160] ■ Information about the new uplink data tunnel. The content of this information can be found in the above “ User's Configuration information "Tunnel-related information for uplink data"

[0161] ■ Information about the old uplink data tunnel. The content of this information can be found in the above “ User's Configuration information "Tunnel-related information for uplink data"

[0162] ■ Downlink data tunnel identification information, which can be used to indicate which downlink tunnel. Different identification information indicates different downlink tunnels. In one embodiment, this identification information can remain unchanged when the downlink data tunnel information is updated. This information can be sent by the relay node to the anchor node when configuring the user's downlink tunnel, such as the information included in the UE Context Setup / Modification Response message for each downlink data tunnel.

[0163] ■ Information about the new downlink data tunnel. The content of this information can be found in the above “ User's Configuration information "Information about downlink data tunnels"

[0164] ■ Information about the old downlink data tunnel. The content of this information can be found in the above “ User's Configuration information "Information about downlink data tunnels"

[0165] In a specific implementation, for a tunnel, the tunnel mapping related information may be included in the signaling and transmitted in the following form:

[0166] a. Tunnel identification information for uplink data

[0167] b. Information about the old uplink data tunnel, such as IP address and / or TEID

[0168] c. Information about the new uplink data tunnel, such as IP address and / or TEID

[0169] d. Routing identification information. In one embodiment, the routing identification information is the new routing identification information used when uplink data is sent.

[0170] e. The identification information of the next hop node. In one embodiment, this information indicates the identification information of the new next hop node used when receiving uplink data.

[0171] f. Identification information of the backhaul link channel. In one embodiment, this information indicates the identification information of the new backhaul link channel used when uplink data is sent.

[0172] g. Identification information of the downlink data tunnel

[0173] h. Information about the old downlink data tunnel, such as IP address and / or TEID

[0174] i. Information about the new downlink data tunnel, such as IP address and / or TEID

[0175] In another embodiment, for a user or a user bearer, the tunnel mapping related information may be included in the signaling and transmitted in the following form, where the included information includes at least one of the following information:

[0176] a. User identification information

[0177] b. User bearer identification information, such as DRB ID, SRB ID, etc.;

[0178] c. Information about one or more tunnels. For each tunnel, this information includes at least one of the following:

[0179] a) Identification information of the uplink data tunnel, which can be used to indicate which uplink tunnel. Different identification information indicates different uplink tunnels. In one embodiment, the identification information can remain unchanged when the uplink data tunnel related information is updated.

[0180] b) Tunnel-related information of old uplink data, such as IP address and / or TEID

[0181] c) Information about the new uplink data tunnel, such as IP address and / or TEID

[0182] d) Routing identification information. In one embodiment, the routing identification information is the new routing identification information used when uplink data is sent.

[0183] e) The identification information of the next hop node. In one embodiment, this information indicates the identification information of the new next hop node used when receiving uplink data.

[0184] f) Identification information of the backhaul link channel. In one embodiment, this information indicates the identification information of the new backhaul link channel used when uplink data is sent.

[0185] g) identification information of the downlink data tunnel, which can be used to indicate which downlink tunnel. Different identification information indicates different downlink tunnels. In one embodiment, the identification information can remain unchanged when the downlink data tunnel related information is updated.

[0186] h) Tunnel-related information of old downlink data, such as IP address and / or TEID

[0187] i) Information about the new downlink data tunnel, such as IP address and / or TEID

[0188] Transport network layer association mapping information. For a transport network layer association, this information includes at least one of the following:

[0189] ■ Information associated with the transport network layer on the new anchor node side, which includes at least one of the following:

[0190] ◆The identification information of the transport network layer association on the anchor node side. This identification information is used to indicate the transport network layer association on the anchor node side. Different identification information indicates the identification of the transport network layer association on the anchor node side.

[0191] IP address information

[0192] ◆Port information

[0193] ◆Indication of the purpose of the transport network layer associated with the new anchor node side. Possible purposes include: sending user-related control signaling (such as UE-associated F1AP), sending non-user-related control signaling (such as non-UE-associated F1AP), sending user-related control information and non-user-related control information, sending user data, sending control signaling type 1 data, sending control signaling type 2 data, sending control signaling type 3 data, etc.

[0194] ■ Information related to the transport network layer on the old anchor node side, which includes at least one of the following:

[0195] ◆The identification information of the transport network layer association on the anchor node side. This identification information is used to indicate the transport network layer association on the anchor node side. Different identification information indicates the identification of the transport network layer association on the anchor node side.

[0196] ◆ IP address information

[0197] ◆Port information

[0198] ◆Indication of the purpose of the transport network layer on the old anchor node side. Possible purposes include: sending user-related control signaling (such as UE-associated F1AP), sending non-user-related control signaling (such as non-UE-associated F1AP), sending user-related control information and non-user-related control information, sending user data, sending control signaling type 1 data, sending control signaling type 2 data, sending control signaling type 3 data, etc.

[0199] ■ Information related to the transport network layer on the new relay node side, which includes at least one of the following:

[0200] ◆ The identification information of the transport network layer association on the relay node side. This identification information is used to indicate the transport network layer association on the relay node side. Different identification information indicates the identification of the transport network layer association on the relay node side.

[0201] IP address information

[0202] ◆Port information

[0203] ◆Indication of the purpose of the transport network layer associated with the new relay node side. Possible purposes include: sending user-related control signaling (such as UE-associated F1AP), sending non-user-related control signaling (such as non-UE-associated F1AP), sending user-related control information and non-user-related control information, sending user data, sending control signaling type 1 data, sending control signaling type 2 data, sending control signaling type 3 data, etc.

[0204] ■ Information related to the transport network layer on the old relay node side, which includes at least one of the following:

[0205] ◆ The identification information of the transport network layer association on the relay node side. This identification information is used to indicate the transport network layer association on the relay node side. Different identification information indicates the identification of the transport network layer association on the relay node side.

[0206] IP address information

[0207] ◆Port information

[0208] ◆Indication information of the use associated with the transport network layer on the old relay node side, which may indicate the following uses: used to send user-related control signaling (such as UE-associated F1AP), used to send non-user-related control signaling (such as non-UE-associated F1AP), used to send user-related control information and non-user-related control information, used to send user data, used to send control signaling type 1 data, used to send control signaling type 2 data, used to send control signaling type 3 data, etc.

[0209] ■ Mapping information for non-user plane data transmission. For a type of non-user plane data, this information includes at least one of the following:

[0210] ■Indication of the type of non-user plane data. The types that can be indicated by this indication include: for sending user-related control signaling (such as UE-associated F1AP), for sending non-user-related control signaling (such as non-UE-associated F1AP), for sending non-F1 interface data

[0211] ■New routing identification information

[0212] ■Old routing information

[0213] ■ Identification information of the new next-hop node

[0214] ■ Identification information of the old next-hop node

[0215] ■ Identification information of the new backhaul link channel

[0216] ■ Identification information of the old backhaul link channel

[0217] ■ Routing identifier mapping information. For a routing identifier mapping, this information includes at least one of the following:

[0218] ■New routing identification information

[0219] ■Old routing information

[0220] The routing identification information indicates the transmission path of the data, which includes the address information of the receiving node (BAPaddress) and / or the indication information of the data transmission path (path ID). The path identification information can be added to the sent data packet.

[0221] Next-hop node mapping information. For a next-hop node mapping, this information includes at least one of the following:

[0222] ■ Identification information of the new next-hop node

[0223] ■ Identification information of the old next-hop node

[0224] The next hop node is the node that directly receives the data when the relay node sends it. In other words, the relay node sends the data to the next hop node, which then sends it to the destination node directly or indirectly (through other nodes). Based on this information, the relay node knows which node to send the data to.

[0225] ■ Mapping information of the backhaul link channel. For the mapping of a backhaul link channel, this information includes at least one of the following:

[0226] ■ Identification information of the new backhaul link channel

[0227] ■ Identification information of the old backhaul link channel

[0228] ■ The above-mentioned backhaul link channel is used to transmit user data. Applicable information (Applicable information) indicates relevant information about the data applicable to the above-mentioned one or more mapping information, and includes at least one of the following information:

[0229] ■ User identification information, there may be one or more users applicable to the above one or more mapping information. This information may include one or more user identification information.

[0230] ■ Information about user radio bearers. There may be one or more user radio bearers applicable to the one or more mapping information. For each radio bearer, the information includes at least one of the following:

[0231] ◆User identification information

[0232] ◆Radio bearer identification information

[0233] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0234] Information related to the user's radio bearer tunnel, which includes at least one of the following:

[0235] ● Information related to the uplink data tunnel, such as IP address and / or TEID

[0236] ● Information related to the downlink data tunnel, such as IP address and / or TEID

[0237] ■ Information related to control signaling. The control signaling to which the above-mentioned one or more mapping information applies may be of various types. For one type, the information includes at least one of the following:

[0238] ◆Type information of control signaling, such as user-related control signaling (such as UE-associated F1AP) and non-user-related control signaling (such as non-UE-associated F1AP)

[0239] ◆Identification information of the user to which the control signaling belongs

[0240] Exception information, which indicates information about data that is not applicable to the one or more mapping information. This information includes at least one of the following:

[0241] ■ User identification information, which is not applicable to one or more of the above mapping information, may have one or more users. This information may include one or more user identification information.

[0242] ■ Information about user radio bearers. There may be one or more user radio bearers that are not subject to the one or more mapping information above. For each radio bearer, the information includes at least one of the following:

[0243] ◆User identification information

[0244] ◆Radio bearer identification information

[0245] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0246] Information related to the user's radio bearer tunnel, which includes at least one of the following:

[0247] ● Information related to the uplink data tunnel, such as IP address and / or TEID

[0248] ● Information related to the downlink data tunnel, such as IP address and / or TEID

[0249] ■ Information related to control signaling, which is not applicable to one or more of the above mapping information. Control signaling may be of various types. For one type, the information includes at least one of the following:

[0250] ◆Type information of control signaling, such as user-related control signaling (such as UE-associated F1AP) and non-user-related control signaling (such as non-UE-associated F1AP)

[0251] ◆Identification information of the user to which the control signaling belongs

[0252] In the above mapping information, the new information may be the information used after the configuration of the relay node is updated, and the old information may be the information used before the configuration of the relay node is updated. The configuration update of the above relay node may be due to the change of the anchor node (or the centralized unit of the anchor node, or the distributed unit of the anchor node, or the control plane part of the centralized unit of the anchor node) to which the relay node is connected. An example is that the relay node changes from anchor node 1 (which may correspond to Figure 3 The source anchor node in the migration) to anchor node 2 (which can correspond to Figure 3In another example, the relay node migrates from anchor node 1 to anchor node 2. In this example, the mobile terminal part of the relay node is switched from anchor node 1 to anchor node 2, and the centralized unit (or the control plane part of the centralized unit, or the user plane part of the centralized unit) to which the distribution unit part of the relay node is connected is changed from the centralized unit of anchor node 1 (or the control plane part of the centralized unit, or the user plane part of the centralized unit) to the centralized unit of anchor node 2 (or the control plane part of the centralized unit, or the user plane part of the centralized unit); in another example, the relay node migrates from anchor node 1 to anchor node 2. In this example, the mobile terminal part of the relay node is switched from anchor node 1 to anchor node 2, and the centralized unit (or the control plane part of the centralized unit, or the user plane part of the centralized unit) to which the distribution unit part of the relay node is connected is still the centralized unit of anchor node 1 (or the control plane part of the centralized unit, or the user plane part of the centralized unit). The above-mentioned example of the configuration update of the relay node only gives a possible situation, and it does not rule out that the configuration update of the relay node according to the above-mentioned mapping information may also occur in other situations.

[0253] The node that receives the above mapping information will replace the old information with the new information. The replacement of the old and new information will affect the transmission of data. The data may include different control signaling (such as F1AP signaling) and / or data of radio bearers belonging to different users. If the above mapping information contains "applicable information", only the data indicated by the "applicable information" is applicable to the replacement of the old and new information indicated in the mapping information. If the above mapping information contains "exceptional information", the data indicated by the "exceptional information" is not applicable to the replacement of the old and new information indicated in the mapping information. The following are several examples of using mapping information to update relay node configuration:

[0254] ■In one example, the above “ Mapping information " provides "information related to the address of the new relay node side" (such as the new IP address) and / or "information related to the address of the old relay node side" (such as the old IP address). The relay node that receives this information will change the data sent or received through the address indicated by the "information related to the address of the old relay node side" to the address indicated by the "information related to the address of the new relay node side".

[0255] ■In another example, the above “ Mapping information" provides "information related to the address of the new anchor node side" (such as the new IP address) and / or "information related to the address of the old anchor node side" (such as the old IP address). The relay node that receives the information will change the data sent to the address indicated by the "information related to the address of the old anchor node side" to the address indicated by the "information related to the address of the new anchor node side", or the relay node will consider that the data from the address indicated by the "information related to the address of the old anchor node side" is changed to the address indicated by the "information related to the address of the new anchor node side".

[0256] ■In another example, the above “ Mapping information " provides "new uplink data tunnel related information" and / or "old uplink data tunnel related information", and the relay node that receives the information will change the data sent to the tunnel indicated by the "old uplink data tunnel related information" to the tunnel indicated by the "new uplink data tunnel related information".

[0257] ■In another example, the above “ Mapping information " provides "new downlink data tunnel related information" and / or "old downlink data tunnel related information", and the relay node that receives the information will change the data received from the tunnel indicated by the "old downlink data tunnel related information" to the data received from the tunnel indicated by the "new downlink data tunnel related information".

[0258] ■In another example, the above “ Mapping information " provides "new routing identification information" and / or "old routing identification information", and the relay node that receives the information will change the data sent to the transmission path indicated by the "old routing identification information" to the transmission path indicated by the "new routing identification information"; further, the information added to the data packet by the relay node is changed from "old routing identification information" to "new routing identification information".

[0259] ■In another example, the above “ Mapping information " provides the "new next hop node identification information" and / or "old next hop node identification information", and the relay node that receives the information will change the data sent to the node indicated by the "old next hop node identification information" to the node indicated by the "new next hop node identification information".

[0260] ■In another example, the above “ Mapping information" provides "new backhaul link channel identification information" and / or "old backhaul link channel identification information", and the relay node that receives the information will change the data sent by the backhaul link channel indicated by the "old backhaul link channel identification information" to the data sent by the backhaul link channel indicated by the "new backhaul link channel identification information".

[0261] Send the above " Mapping information The beneficial effect of " is that the receiving node of the information can reflect Information about shooting "Simultaneously update the data transmission configuration of multiple users served by the relay node, so that the data transmission configuration of multiple users can be updated through one signaling, without using multiple user-related signaling to update the data transmission configuration of each user separately. For example, when the IP addresses contained in the uplink / downlink tunnel information of multiple users' radio bearers are the same, through this " Mapping information " can update the IP address to a new IP address, thereby simultaneously updating the IP addresses in the uplink / downlink tunnel information of the multiple user wireless bearers; another example is that when the routing identifiers of the data of multiple user wireless bearers are the same, through the " Mapping information " can update the routing identifier to a new routing identifier, thereby updating the routing identifiers of multiple wireless bearer data at the same time; another example is that when the next hop node of the wireless bearer data of multiple users is the same, through the " Mapping information " can update the next hop node to a new next hop node, thereby simultaneously updating the next hop nodes of multiple wireless bearer data; another example is that when the backhaul link channel used to transmit the data of multiple user wireless bearers is the same, through the " Mapping information The backhaul link channel may be updated to a new backhaul link channel, thereby simultaneously updating the backhaul link channel carrying data of multiple radio bearers.

[0262] Configuration information related to the relay node's backhaul link channel The backhaul link channel is the channel served by the mobile terminal portion of the relay node. For a backhaul link channel, the information includes at least one of the following information:

[0263] ■ Identification information of the backhaul link channel, such as the backhaul link channel ID

[0264] ■For QoS parameter information of the backhaul link channel, refer to TS38.473

[0265] ■ Configuration information of the service backhaul link channel, such as RLC layer configuration, configuration information of the logical channel of the backhaul link channel (such as identification information, priority information of the logical channel of the backhaul link), etc., can be seen in CellGroupConfiguration

[0266] ■ Information related to data carried by the backhaul link channel. This data may be uplink data (data generated by the relay node and sent to the anchor node, such as user plane data of the F1 interface generated by the distribution unit of the relay node, or data forwarded by the relay node to the anchor node, such as data received by the relay node from other nodes), downlink data (data sent by the anchor node to the relay node, which may be data sent to the distribution unit of the relay node, or data sent to other nodes but requiring forwarding by the relay node), or both uplink and downlink data. This information may include at least one of the following:

[0267] ■ Information about the user's radio bearer, the data of which is sent via the backhaul link channel. The information contained in this information is as described in the above " User configuration information "User's radio bearer related information"

[0268] ■Information indicating the data type. The indicated types may include: non-UE associated F1AP signaling, UE-associated F1AP signaling, control signaling types of different priorities (such as control signaling type 1, control signaling type 2, control signaling type 3, ... further, control signaling type 1 has the highest priority, and control signaling type 2 has the second highest priority), and non-F1 data (non-F1 traffic, such as IPSec protocol data, SCTP protocol data, and data from OAM).

[0269] ■ Routing ID information for data transmission, which is used to indicate the transmission path of the data. It includes the address information of the receiving node (BAP address) and / or the transmission path identification information (path ID). Furthermore, based on this information, the relay node can add this information to the transmitted data packet.

[0270] ■ The identification information of the next hop node of the data. The next hop node is the node that directly receives the uplink data when the relay node sends data. In other words, the relay node sends the uplink data to the next hop node, which then sends the uplink data directly or indirectly (through other nodes) to the destination node of the uplink data. Based on this information, the relay node knows which node to send the uplink data to.

[0271] Configuration information for aggregated dataThe aggregated data is formed by aggregating data from multiple users or different data from a single user. During transmission, the aggregated data may be transmitted over the same backhaul link channel. The information includes at least one of the following:

[0272] ■QoS parameter information for the aggregated data

[0273] ■ The configuration information of the data contained in the aggregated data. The data contained in the aggregated data may belong to different radio bearers of different users, or may belong to different radio bearers of the same user. For a radio bearer, the information contained in the configuration information can be found in the above " User configuration information "User's radio bearer related information"

[0274] ■ Information about the backhaul link channel used by the mobile terminal portion of the relay node to serve the aggregated data. The information contained in this information can be found in the above “ Configuration information related to the relay node's backhaul link channel ”

[0275] The beneficial effect of transmitting this information is that the receiving node can know how the data is aggregated and transmitted in the relay network, and it also helps the receiving node to aggregate data from different users for transmission.

[0276] The first aspect of the present invention is a migration process of a relay node. Figure 4 FIG. 1 is an example of a relay node migration process according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0277] Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message may be a handover request message, which provides the third node with configuration information related to the first node when being served by the second node. This information helps the third node generate a configuration to serve the first node. In one embodiment, the handover request message is a handover request message for the mobile terminal portion of the first node. The content included can be found in the HANDOVER REQUEST message in TS38.423. In addition to the information included in the existing HANDOVER REQUEST message, the handover request message may include at least one of the following information:

[0278] ■ First user configuration information, which is the configuration information of one or more users served by the first node before migration. The one or more users may be users of the distributed unit part of the first node. For each user, the content of this information can be found in the above " User configuration information ", this configuration information is the configuration information of the first node before migration

[0279] ■ First backhaul link channel configuration information, which is configuration information related to the backhaul link channel served by the mobile terminal part of the first node. This information can be found in the above “ Configuration information related to the backhaul link channel of the relay node interest ”

[0280] ■ The first address-related information, which is the address-related information required by the first node. The information contained in this information is the address-related information used by the first node before migration, that is, the first node uses the address-related information to transmit data with the second node. The content of this information can be found in the above " Relay nodes are required to Information about the address ”

[0281] ■ The first configuration information of the aggregated data, which is the configuration information of the aggregated data served by the first node before migration. The content of this information can be found in the above “ Configuration information for aggregated data ”

[0282] Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message may be a handover response message, which provides the second node with the configuration generated by the third node for serving the first node. In one embodiment, the handover response message is a handover response message for the mobile terminal portion of the first node. For the content contained in the handover response message, see the HANDOVER REQUEST ACKNOWLEDGE message in TS38.423. In addition to the information contained in the existing HANDOVER REQUEST ACKNOWLEDGE message, the handover response message includes at least one of the following information:

[0283] ■ Second user configuration information, which is the configuration information of one or more users served by the first node after migration (its distribution unit part). The content of this information can be found in the above " User configuration information "; In one embodiment, the user is a user accepted by the third node after the migration of the first node, and / or a user not accepted by the third node;

[0284] ■ Second mapping relationship information, which reflects the mapping relationship of information used by the first node before and after the migration occurs. This information is used to update the configuration information used by the first node for data transmission. The content of this information can be found in the above " Mapping information", in which the new information is the information required by the first node after migration, and the old information is the information used by the first node before migration. The beneficial effect of this information is that it can help the first node update the configuration information required for transmitting the data of its distribution unit (such as data of different users, F1AP signaling, etc.) through less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data separately.

[0285] ■ Second backhaul link channel configuration information, which is configuration information related to the backhaul link channel served by the mobile terminal portion of the first node after migration. This information can be found in the above “ The backhaul link channel of the relay node is related to Configuration information In one embodiment, the backhaul link channel is the backhaul link channel accepted by the third node after migration.

[0286] ■ The second address-related information is the address-related information required after the first node migrates. This information is used for data transmission between the first node and the third node. The content of this information can be found in the above " Relay Section Address-related information required by the point ”

[0287] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message may be a migration configuration message, which provides the first node with configuration information required for migration and / or configuration information required after migration to a third node. In one embodiment, the migration configuration message may be an RRCReconfig message in TS 38.331. In addition to the information included in the existing RRCReconfig message, the migration configuration message includes at least one of the following information:

[0288] ■ The third user configuration information, which is the configuration information of one or more users served by the first node after migration (its distribution unit part), can be found in the above " User configuration information In one embodiment, the user is a user accepted by the third node after the migration of the first node, and / or a user not accepted by the third node.

[0289] ■ The third mapping relationship information, which reflects the mapping relationship of the information used by the first node before and after the migration occurs, is used to update the configuration information used by the first node when performing data transmission. The content of this information can be found in the above " Mapping information", in which the new information is the information required by the first node after migration, and the old information is the information used by the first node before migration. The beneficial effect of this information is that it can help the first node update the configuration information required for transmitting the data of its distribution unit (such as data of different users, F1AP signaling, etc.) through less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data separately.

[0290] ■ The third backhaul link channel configuration information is the configuration information related to the backhaul link channel served by the mobile terminal part after the first node migrates. This information can be found in the above “ The backhaul link channel of the relay node is related to Configuration information In one embodiment, the backhaul link channel is a backhaul link channel accepted and / or not accepted by the third node after migration.

[0291] ■ The third information related to the address is the address-related information required after the first node migrates. This information is used for data transmission between the first node and the third node. The content of this information can be found in the above " Relay Section Address-related information required by the point ”

[0292] Optionally, after step 1-3 and before step 1-4, a process of some mobile terminals of the first node accessing the third node is also included, such as cell search, random access, etc. Since these processes are irrelevant to the problem to be solved by the present invention, they will not be described in detail in the present invention.

[0293] Step 1-4: The first node sends a first configuration complete message to the third node. In one embodiment, the first configuration complete message may be a migration configuration complete message, which serves to confirm to the third node that the migration of the first node is complete. In one embodiment, the migration configuration complete message may be an RRCReconfigComplete message in TS 38.331. In addition to the information included in the existing RRCReconfigComplete message, the migration configuration complete message includes at least one of the following information:

[0294] ■ The fourth user configuration information is the configuration information of the users served by the distribution unit of the first node after migration. The content of this information can be found in the above “ User configuration information In one embodiment, the user is a user accepted by the third node after the migration of the first node, and / or a user not accepted by the third node.

[0295] ■ The fourth mapping relationship information, which reflects the mapping relationship of the information used by the first node before and after the migration, is used to update the configuration information used by the first node when performing data transmission. The content of this information can be found in the above " Mapping information ", in which the new information is the information required by the first node after migration, and the old information is the information used by the first node before migration. The beneficial effect of this information is that it can help the third node update the configuration information required for transmitting the data of the distribution unit part of the first node (such as data of different users, F1AP signaling, etc.) through less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data separately.

[0296] The above process is for Figure 3 Different relay node migration methods may have different implementations. In the following embodiments, the specific content of the information contained in each message can be found in the above " User configuration information "," Relay Node Required address-related information "," Mapping information "," Configuration information related to the backhaul link channel of the relay node interest ". The processes involved in the following embodiments are steps 1-1 to 1-4 above. The difference between different embodiments is that the information contained in each message may be different. In order to simplify the description of each embodiment and highlight the differences in information contained in different implementation methods, the information contained in each message is not fully listed. For those unlisted information, please refer to the description in steps 1-1 to 1-4 above. In addition, when describing embodiments 1-1-2 to 1-3-2, only the differences between the information contained in each message and embodiment 1-1-1 are described.

[0297] Example 1-1-1 (based on Figure 3 (a) Anchor nodes determine the configuration of relay nodes)

[0298] Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message may be a handover request message, which may include at least one of the following information:

[0299] ■First user configuration information, which includes at least one of the following information:

[0300] ■User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0301] Information about the user's radio bearer. For a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB), this information includes at least one of the following:

[0302] User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0303] ◆User radio bearer identification information, such as UE RB ID

[0304] ◆Identification information, such as DRB ID, SRB ID

[0305] ◆Related information about QoS of radio bearers

[0306] ◆Configuration information of wireless bearer serving users

[0307] ◆ Information about the QoS satisfied by the relay node, that is, information about the QoS satisfied by the first node

[0308] ◆ Information about the QoS satisfied by non-relay nodes, that is, information about the QoS satisfied by non-first nodes

[0309] Information related to the uplink data tunnel. For a tunnel, the information includes at least one of the following: tunnel identification information, IP address, TEID, routing identification information, next hop node identification information, return link channel identification information, etc.

[0310] Information about the downlink data tunnel. For a tunnel, this information includes at least one of the following: tunnel identification information, IP address, TEID, DSCP domain configuration value information, flow label domain configuration value information

[0311] ◆Information related to data forwarding, which can be for uplink data and / or downlink data, and can include "suggestion on whether data forwarding is required"

[0312] Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message may be a handover response message, which includes at least one of the following information:

[0313] ■ Second user configuration information, which includes at least one of the following information:

[0314] ■User identification information, which is the identification information used after the first node migrates to the third node, such as the new gNB-CU / DU UE F1AP ID, new C-RNTI, and new UE XnAP ID. Furthermore, it may also include the identification information used before the first node migrated, such as the old gNB-CU / DU UE F1AP ID, old C-RNTI, and old UE XnAP ID

[0315] ■ Information related to the user's radio bearer, for a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB)); in one embodiment, the radio bearer may be accepted by the third node or may not be accepted by the third node; the information includes at least one of the following:

[0316] User identification information, which is the identification information used after the first node migrates to the third node, such as the new gNB-CU / DU UE F1AP ID, new C-RNTI, and new UE XnAP ID. Furthermore, it may also include the identification information used before the first node migrated, such as the old gNB-CU / DU UE F1AP ID, old C-RNTI, and old UE XnAP ID.

[0317] ◆User radio bearer identification information, such as UE RB ID

[0318] ◆Identification information, such as DRB ID, SRB ID

[0319] ◆Configuration information of the service user radio bearer. In one embodiment, the configuration information is the configuration information generated by the third node

[0320] Information related to the uplink data tunnel. For a tunnel, the information includes at least one of the following information: tunnel identification information, IP address, TEID, routing identification information, next hop node identification information, backhaul link channel identification information, etc. In one embodiment, the information is updated by the third node and is different from the information in step 1-1 above.

[0321] Information related to the downlink data tunnel. For a tunnel, this information includes at least one of the following information: tunnel identification information, IP address, TEID, DSCP field configuration value information, flow label field configuration value information; in one embodiment, this information is updated by the third node and is different from the information in step 1-1 above.

[0322] Information related to data forwarding, which can be for uplink data and / or downlink data, and can include an IP address (the address on the third node side) and / or a TEID (the TEID on the third node side)

[0323] ■ Second mapping relationship information, which reflects the mapping relationship of information used by the first node before and after the migration occurs. This information is used to update the configuration information used by the first node when performing data transmission. The content of this information can be found in the above " Mapping information Specifically, the information includes at least one of the following:

[0324] ■ Address mapping information. For an address mapping, this information includes at least one of the following:

[0325] ◆ Address identification information on the relay node side

[0326] ◆Information about the address of the new relay node

[0327] ◆Information about the address of the old relay node

[0328] ◆Identification information of the address on the anchor node side

[0329] ◆Information about the address of the new anchor node

[0330] ◆Information about the address of the old anchor node

[0331] Tunnel mapping information. For a tunnel mapping, this information includes at least one of the following:

[0332] ◆Tunnel identification information for uplink data

[0333] ◆New uplink data tunnel related information

[0334] ◆ Information about the old uplink data tunnel

[0335] ◆Tunnel identification information for downlink data

[0336] ◆New downlink data tunnel related information

[0337] ◆ Information about the old downlink data tunnel

[0338] ■Transmission network layer associated mapping information, which includes at least one of the following information:

[0339] ◆Identification information associated with the transport network layer on the anchor node side

[0340] ◆Transmission network layer associated information on the new anchor node side

[0341] ◆Transmission network layer related information on the old anchor node side

[0342] ◆Identification information associated with the transmission network layer on the relay node side

[0343] ◆Transmission network layer related information on the new relay node side

[0344] ◆Transmission network layer related information on the old relay node side

[0345] ■Mapping information for non-user plane data transmission

[0346] ■ Routing identifier mapping information. For a routing identifier mapping, this information includes at least one of the following:

[0347] New routing information

[0348] ◆Old routing identification information

[0349] Next-hop node mapping information. For a next-hop node mapping, this information includes at least one of the following:

[0350] ◆Identification information of the new next-hop node

[0351] ◆The identification information of the old next hop node

[0352] ■ Mapping information of the backhaul link channel. For the mapping of a backhaul link channel, this information includes at least one of the following:

[0353] ◆Identification information of the new backhaul link channel

[0354] ◆Identification information of the old backhaul link channel

[0355] ■Applicable information

[0356] ■Exception information

[0357] The above-mentioned switching response message may include only one of the "second user configuration information" and the "second mapping relationship information". If it only includes the "second user configuration information", the third node will provide updated configuration information for each user respectively. If it only includes the "second mapping relationship information", the second node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0358] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message may be a migration configuration message, which includes at least one of the following information:

[0359] ■ Third user configuration information, which includes at least one of the following information:

[0360] ■User identification information, which is the identification information used after the first node migrates to the third node, such as the new gNB-CU / DU UE F1AP ID, new C-RNTI, and new UE XnAP ID. Furthermore, it may also include the identification information used before the first node migrated, such as the old gNB-CU / DU UE F1AP ID, old C-RNTI, and old UE XnAP ID

[0361] ■ Information related to the user's radio bearer, for a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB)); in one embodiment, the radio bearer may be accepted by the third node or may not be accepted by the third node; the information includes at least one of the following:

[0362] User identification information, which is the identification information used after the first node migrates to the third node, such as the new gNB-CU / DU UE F1AP ID, new C-RNTI, and new UE XnAP ID. Furthermore, it may also include the identification information used before the first node migrated, such as the old gNB-CU / DU UE F1AP ID, old C-RNTI, and old UE XnAP ID.

[0363] ◆User radio bearer identification information, such as UE RB ID

[0364] ◆Identification information, such as DRB ID, SRB ID

[0365] ◆Configuration information of wireless bearer serving users

[0366] Information related to the uplink data tunnel. For a tunnel, the information includes at least one of the following information: tunnel identification information, IP address, TEID, routing identification information, next hop node identification information, backhaul link channel identification information, etc. In one embodiment, the information is updated by the third node and is different from the information in step 1-1 above.

[0367] Information related to the downlink data tunnel. For a tunnel, this information includes at least one of the following information: tunnel identification information, IP address, TEID, etc. In one embodiment, this information is updated by the third node and is different from the information in step 1-1 above.

[0368] ■ The third mapping relationship information, which reflects the mapping relationship of the information used by the first node before and after the migration occurs, is used to update the configuration information used by the first node when performing data transmission. The content of this information can be found in the above " Mapping informationSpecifically, the information includes at least one of the following:

[0369] ■ Address mapping information. For an address mapping, this information includes at least one of the following:

[0370] ◆ Address identification information on the relay node side

[0371] ◆Information about the address of the new relay node

[0372] ◆Information about the address of the old relay node

[0373] ◆Identification information of the address on the anchor node side

[0374] ◆Information about the address of the new anchor node

[0375] ◆Information about the address of the old anchor node

[0376] Tunnel mapping information. For a tunnel mapping, this information includes at least one of the following:

[0377] ◆Tunnel identification information for uplink data

[0378] ◆New uplink data tunnel related information

[0379] ◆ Information about the old uplink data tunnel

[0380] ◆Tunnel identification information for downlink data

[0381] ◆New downlink data tunnel related information

[0382] ◆ Information about the old downlink data tunnel

[0383] ■Transmission network layer associated mapping information, which includes at least one of the following information:

[0384] ◆Identification information associated with the transport network layer on the anchor node side

[0385] ◆Transmission network layer associated information on the new anchor node side

[0386] ◆Transmission network layer related information on the old anchor node side

[0387] ◆Identification information associated with the transmission network layer on the relay node side

[0388] ◆Transmission network layer related information on the new relay node side

[0389] ◆Transmission network layer related information on the old relay node side

[0390] ■Mapping information for non-user plane data transmission

[0391] ■ Routing identifier mapping information. For a routing identifier mapping, this information includes at least one of the following:

[0392] New routing information

[0393] ◆Old routing identification information

[0394] Next-hop node mapping information. For a next-hop node mapping, this information includes at least one of the following:

[0395] ◆Identification information of the new next-hop node

[0396] ◆The identification information of the old next hop node

[0397] ■ Mapping information of the backhaul link channel. For the mapping of a backhaul link channel, this information includes at least one of the following:

[0398] ◆Identification information of the new backhaul link channel

[0399] ◆Identification information of the old backhaul link channel

[0400] ■Applicable information

[0401] ■Exception information

[0402] The above-mentioned migration configuration message may include only one of the "third user configuration information" and the "third mapping relationship information". If it only includes the "third user configuration information", the second node will provide the updated configuration information for each user to the first node respectively. If it only includes the "third mapping relationship information", the first node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0403] Step 1-4: The first node sends a first configuration completion message to the third node. In one embodiment, the first configuration completion message may be a migration configuration completion message, which is used to confirm to the third node that the migration of the first node is complete.

[0404] Example 1-1-2 (based on Figure 3 (a), the anchor node and the relay node respectively determine the configuration of the relay node) Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message may be a handover request message. The information contained in the handover request message can refer to step 1-1 in the above embodiment 1-1-1.

[0405] Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message may be a handover response message, which includes at least one of the following information:

[0406] ■ Second user configuration information. This information may not include "downlink data tunnel related information" for a user radio bearer. For other information included in this information, refer to step 1-2 of the above embodiment 1-1-1.

[0407] ■ Second mapping relationship information, which may not include "information related to the address of the new relay node side", and / or "information related to the address of the old relay node side", and / or "information related to the tunnel of the new downlink data", and / or "information related to the tunnel of the old downlink data". For other information, please refer to step 1-2 of the above embodiment 1-1-1.

[0408] The above-mentioned switching response message may include only one of the "second user configuration information" and the "second mapping relationship information". If it only includes the "second user configuration information", the third node provides updated configuration information for each user separately. If it only includes the "second mapping relationship information", the second node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0409] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message may be a migration configuration message, which includes at least one of the following information:

[0410] ■ Third user configuration information. This information may not include "downlink data tunnel-related information" for a user radio bearer. For other information included in this information, refer to step 1-3 of the above embodiment 1-1-1.

[0411] ■ The third mapping relationship information, which may not include "information related to the address of the new relay node side", and / or "information related to the address of the old relay node side", and / or "information related to the tunnel of the new downlink data", and / or "information related to the tunnel of the old downlink data". For other information, please refer to step 1-3 of the above embodiment 1-1-1.

[0412] The above-mentioned migration configuration message may include only one of the "third user configuration information" and the "third mapping relationship information". If it only includes the "third user configuration information", the second node will provide the updated configuration information for each user to the first node respectively. If it only includes the "third mapping relationship information", the first node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0413] Step 1-4: The first node sends a first configuration completion message to the third node. In one embodiment, the first configuration completion message may be a migration configuration completion message, which confirms to the third node that the migration of the first node is complete. In addition, the message may include at least one of the following information:

[0414] ■ Fourth user configuration information, which includes at least one of the following information:

[0415] ■User identification information, which is the identification information used after the first node migrates to the third node, such as the new gNB-CU / DU UE F1AP ID, new C-RNTI, and new UE XnAP ID. Furthermore, it may also include the identification information used before the first node migrated, such as the old gNB-CU / DU UE F1AP ID, old C-RNTI, and old UE XnAP ID

[0416] ■ Information related to the user's radio bearer, for a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB)); in one embodiment, the radio bearer may be accepted by the third node and / or not accepted by the third node; the information includes at least one of the following information:

[0417] User identification, which is the identification information used after the first node migrates to the third node, such as the new gNB-CU / DU UE F1AP ID, new C-RNTI, and new UE XnAP ID. Furthermore, it may also include the identification information used before the first node migrated, such as the old gNB-CU / DU UE F1AP ID, old C-RNTI, and old UE XnAP ID.

[0418] ◆User radio bearer identification information, such as UE RB ID

[0419] ◆Identification information, such as DRB ID, SRB ID

[0420] Information related to the downlink data tunnel. For a tunnel, the information includes at least one of the following information: tunnel identification information, IP address, TEID; in one embodiment, the information is updated by the first node and is different from the information in step 1-1 above.

[0421] ■ Fourth mapping relationship information, which includes at least one of the following information:

[0422] ■ Address mapping information. For an address mapping, this information includes at least one of the following:

[0423] ◆ Address identification information on the relay node side

[0424] ◆Information about the address of the new relay node

[0425] ◆Information about the address of the old relay node

[0426] Tunnel mapping information. For a tunnel mapping, this information includes at least one of the following:

[0427] ◆Tunnel identification information for downlink data

[0428] ◆New downlink data tunnel related information

[0429] ◆ Information about the old downlink data tunnel

[0430] ■Applicable information

[0431] ■Exception information

[0432] The above-mentioned migration configuration completion message may include only one of the "fourth user configuration information" and the "fourth mapping relationship information". If only the "fourth user configuration information" is included, the first node will provide the updated configuration information for each user to the third node respectively. If only the "fourth mapping relationship information" is included, the third node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0433] Example 1-2-1 (based on Figure 3 (b) Anchor nodes determine the configuration of relay nodes)

[0434] Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message may be a handover request message. The information contained in the handover request message may refer to step 1-1 in the above embodiment 1-1-1.

[0435] Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message may be a handover response message, which includes at least one of the following information:

[0436] ■ Second user configuration information, for a radio bearer, this information may not include "configuration information of the service user radio bearer" and / or "information related to data forwarding". For other information included in this information, please refer to step 1-2 of the above embodiment 1-1-1.

[0437] ■ Second mapping relationship information, for which please refer to step 1-2 of the above embodiment 1-1-1.

[0438] The above-mentioned switching response message may include only one of the "second user configuration information" and the "second mapping relationship information". If it only includes the "second user configuration information", the third node will provide updated configuration information for each user respectively. If it only includes the "second mapping relationship information", the second node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0439] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message may be a migration configuration message, which includes at least one of the following information:

[0440] ■ Third user configuration information, for a radio bearer, this information may not include "configuration information of the service user radio bearer". For other information included in this information, please refer to step 1-3 of embodiment 1-1-1.

[0441] ■ Third mapping relationship information. The information contained in this information can refer to step 1-3 of embodiment 1-1-1.

[0442] The above-mentioned migration configuration message may include only one of the "third user configuration information" and the "third mapping relationship information". If it only includes the "third user configuration information", the second node will provide the updated configuration information for each user to the first node respectively. If it only includes the "third mapping relationship information", the first node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0443] Step 1-4: The first node sends a first configuration completion message to the third node. In one embodiment, the first configuration completion message may be a migration configuration completion message, which is used to confirm to the third node that the migration of the first node is complete.

[0444] Example 1-2-2 (based on Figure 3 (b), anchor nodes and relay nodes respectively determine the configuration of relay nodes)

[0445] Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message may be a handover request message. The information contained in the handover request message may refer to step 1-1 in the above embodiment 1-1-1.

[0446] Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message may be a handover response message, which includes at least one of the following information:

[0447] ■ Second user configuration information, which, for a user radio bearer, may not include "configuration information of the serving user radio bearer" and / or "information related to data forwarding";

[0448] The "downlink data tunnel related information" may include at least one of the following information: tunnel identification information, IP address, TEID, DSCP field configuration value information, flow label field configuration value information; in one embodiment, the DSCP field configuration value information and the flow label field configuration value information are information updated by the third node and may be different from the information in the above step 1-1, while the other information is the information received in step 1-1. For other information included in the "second user configuration information", please refer to step 1-2 of the above embodiment 1-1-1.

[0449] ■ Second mapping relationship information, which may not include "information related to the address of the new relay node side", and / or "information related to the address of the old relay node side", and / or "information related to the tunnel of the new downlink data", and / or "information related to the tunnel of the old downlink data". For other information, please refer to step 1-2 of the above embodiment 1-1-1.

[0450] The above-mentioned switching response message may include only one of the "second user configuration information" and the "second mapping relationship information". If it only includes the "second user configuration information", the third node will provide updated configuration information for each user respectively. If it only includes the "second mapping relationship information", the second node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0451] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message may be a migration configuration message, which includes at least one of the following information:

[0452] ■ Third user configuration information: This information may not include "configuration information of the serving user radio bearer" and / or "information related to the downlink data tunnel" for a user radio bearer. For other information included in this information, please refer to step 1-3 of the above embodiment 1-1-1.

[0453] ■ The third mapping relationship information, which may not include "information related to the address of the new relay node side", and / or "information related to the address of the old relay node side", and / or "information related to the tunnel of the new downlink data", and / or "information related to the tunnel of the old downlink data". For other information, please refer to step 1-3 of the above embodiment 1-1-1.

[0454] The above-mentioned migration configuration message may include only one of the "third user configuration information" and the "third mapping relationship information". If it only includes the "third user configuration information", the second node will provide the updated configuration information for each user to the first node respectively. If it only includes the "third mapping relationship information", the first node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0455] Step 1-4: The first node sends a first configuration completion message to the third node. In one embodiment, the first configuration completion message may be a migration configuration completion message, which confirms to the third node that the migration of the first node is complete. In addition, the message may include at least one of the following information:

[0456] ■ The fourth user configuration information, the information contained in this information can refer to step 1-4 in the above embodiment 1-1-2.

[0457] ■ The fourth mapping relationship information, the information contained in this information can refer to step 1-4 in the above embodiment 1-1-2.

[0458] The above-mentioned migration configuration completion message may include only one of the "fourth user configuration information" and the "fourth mapping relationship information". If only the "fourth user configuration information" is included, the first node will provide the updated configuration information for each user to the third node respectively. If only the "fourth mapping relationship information" is included, the third node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0459] Example 1-3-1 (based on Figure 3 (c) Anchor nodes determine the configuration of relay nodes)

[0460] Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message may be a handover request message. The information contained in the message may refer to step 1-1 in the above embodiment 1-1-1.

[0461] Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message may be a handover response message, which includes at least one of the following information:

[0462] ■ Second user configuration information, for a user radio bearer, this information may not include "configuration information of the service user radio bearer". For "information related to the tunnel of uplink data", in one embodiment, the tunnel identification information and / or IP address and / or TEID included in this information may be the same as those in step 1-1. The routing identification information and / or next hop node identification information and / or return link channel identification information included in this information may be updated by a third node. For "information related to the tunnel of downlink data", in one embodiment, the information included in this information may be updated by a third node. In another embodiment, this information may not include configuration value information of the DSCP field and / or flow Configuration value information of the label field; in addition, for a user wireless bearer, the information may also include "first tunnel information" and / or "second tunnel information". The effect of receiving the "first tunnel information" is that the second node will send the data sent to the first node to the third node according to the "first tunnel information", and then the third node will send it to the first node. The third node will further update the information in the data packet (such as IP address, TEID, etc.); the effect of receiving the "second tunnel information" is that the first node will send the data sent to the second node to the third node according to the "second tunnel information", and then the third node will send it to the second node. The third node will further update the information in the data packet (such as IP address, TEID, etc.). For other information contained in the "second user configuration information", please refer to step 1-2 in the above embodiment 1-1-1.

[0463] ■ Second mapping relationship information, for which please refer to step 1-2 of the above embodiment 1-1-1.

[0464] The above-mentioned switching response message may include only one of the "second user configuration information" and the "second mapping relationship information". If it only includes the "second user configuration information", the third node will provide updated configuration information for each user respectively. If it only includes the "second mapping relationship information", the second node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0465] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message may be a migration configuration message, which includes at least one of the following information:

[0466] ■ The third user configuration information, for a radio bearer, may not include the "configuration information of the service user radio bearer". For the "information related to the tunnel of uplink data", its IP address and / or TEID is updated according to the "second tunnel information" received in the above step 1-2, and the routing identification information and / or the identification information of the next hop node and / or the identification information of the return link channel is updated according to the "information related to the tunnel of uplink data" received in step 1-2. For the "information related to the tunnel of downlink data", it includes the tunnel identification information and / or IP address and / or TEID included in the above step 1-2; for other information included in the "third user configuration information", please refer to step 1-3 in the above embodiment 1-1-1

[0467] ■ Third mapping relationship information. The information contained in this information can refer to step 1-3 of embodiment 1-1-1.

[0468] The above-mentioned migration configuration message may include only one of the "third user configuration information" and the "third mapping relationship information". If it only includes the "third user configuration information", the second node will provide the updated configuration information for each user to the first node respectively. If it only includes the "third mapping relationship information", the first node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0469] Step 1-4: The first node sends a first configuration completion message to the third node. In one embodiment, the first configuration completion message may be a migration configuration completion message, which is used to confirm to the third node that the migration of the first node is complete.

[0470] Example 1-3-2 (based on Figure 3 (c) The anchor node and the relay node each determine the configuration of the relay node.) Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message may be a handover request message, and the information contained in the message may refer to step 1-1 in the above embodiment 1-1-1.

[0471] Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message may be a handover response message, which includes at least one of the following information:

[0472] ■ Second user configuration information, for a user radio bearer, may not include "configuration information of the serving user radio bearer" and / or "information related to the downlink data tunnel." For "information related to the uplink data tunnel," in one embodiment, the tunnel identification information and / or IP address and / or TEID included in this information may be the same as in step 1-1. The routing identification information and / or next-hop node identification information and / or backhaul link channel identification information included in this information may be updated by the third node. In addition, for a user radio bearer, this information may also include "first tunnel information." And / or "second tunnel information", the effect of receiving the "first tunnel information" is that the second node will first send the data sent to the first node to the third node according to the "first tunnel information", and then the third node will send it to the first node. The third node will further update the information in the data packet (such as IP address, TEID, etc.); the effect of receiving the "second tunnel information" is that the first node will first send the data sent to the second node to the third node according to the "second tunnel information", and then the third node will send it to the second node. The third node will further update the information in the data packet (such as IP address, TEID, etc.). For other information contained in the "second user configuration information", please refer to step 1-2 in the above embodiment 1-1-1.

[0473] ■ Second mapping relationship information, which may not include "information related to the address of the new relay node side", and / or "information related to the address of the old relay node side", and / or "information related to the tunnel of the new downlink data", and / or "information related to the tunnel of the old downlink data". For this information, please refer to step 1-2 of the above embodiment 1-1-1.

[0474] The above-mentioned switching response message may include only one of the "second user configuration information" and the "second mapping relationship information". If it only includes the "second user configuration information", the third node will provide updated configuration information for each user respectively. If it only includes the "second mapping relationship information", the second node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0475] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message may be a migration configuration message, which includes at least one of the following information:

[0476] ■ The third user configuration information, for a radio bearer, may not include "configuration information of the service user radio bearer" and / or "information related to the downlink data tunnel"; for "information related to the uplink data tunnel", its IP address and / or TEID is updated according to the "second tunnel information" received in step 1-2 above, and the routing identification information and / or the identification information of the next hop node and / or the identification information of the return link channel is updated according to the "information related to the uplink data tunnel" received in step 1-2. For other information included in the "third user configuration information", please refer to step 1-3 in the above embodiment 1-1-1

[0477] ■ Third mapping relationship information, which may not include "information related to the address of the new relay node side", and / or "information related to the address of the old relay node side", and / or "information related to the tunnel of the new downlink data", and / or "information related to the tunnel of the old downlink data". For the information included in this information, please refer to step 1-3 of embodiment 1-1-1.

[0478] The above-mentioned migration configuration message may include only one of the "third user configuration information" and the "third mapping relationship information". If it only includes the "third user configuration information", the second node will provide the updated configuration information for each user to the first node respectively. If it only includes the "third mapping relationship information", the first node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0479] Step 1-4: The first node sends a first configuration completion message to the third node. In one embodiment, the first configuration completion message may be a migration configuration completion message, which is used to confirm to the third node that the migration of the first node is complete.

[0480] ■ The fourth user configuration information, the information contained in this information can refer to step 1-4 in the above embodiment 1-1-2.

[0481] ■ The fourth mapping relationship information, the information contained in this information can refer to step 1-4 in the above embodiment 1-1-2.

[0482] The above-mentioned migration configuration completion message may include only one of the "fourth user configuration information" and the "fourth mapping relationship information". If only the "fourth user configuration information" is included, the first node will provide the updated configuration information for each user to the third node respectively. If only the "fourth mapping relationship information" is included, the third node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0483] In the above process, the handover request message and the handover response message can respectively use the HANDOVER REQUEST message and HANDOVER REQUEST ACKNOWLEDGE message of the existing Xn interface to send relevant information, or can use other existing messages or new messages (such as IAB node handover (migration) request (IAB node handover (migration) request) and IAB node handover (migration) request acknowledge (IAB node handover (migration) request acknowledgement) message), or other messages.

[0484] The above-mentioned migration configuration message and migration configuration completion message may respectively use the existing RRCReconfig message and RRCReconfigComplete message to send relevant information, or may use other existing messages or new messages.

[0485] In the above process, step 1-1 and step 1-2 can be executed as a separate process, and step 1-3 and step 1-4 can be executed as a separate process.

[0486] Possible beneficial effects of the above process include:

[0487] 1. Complete the migration of relay nodes between different anchor nodes, such as the handover of the mobile terminal part of the relay node between different anchor nodes, and the migration of users served by the distribution unit part of the relay node between different anchor nodes. Unlike traditional technologies, which require a separate handover process for each user, the above process can complete the handover of multiple users simultaneously;

[0488] 2. During relay node migration, the configuration information for the data to be transmitted by the relay node's distribution unit needs to be updated. Based on the above process, the signaling required to update this configuration information can be effectively reduced. For example, the mapping-related information exchanged in the above process can help the receiving node simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration for different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration for different users), saving signaling overhead.

[0489] 3. Maintaining the connection between the distributed unit part of the relay node and the centralized unit of the source anchor node reduces the configuration update for users accessing the relay node and saves signaling overhead.

[0490] The second aspect of the present invention is a configuration update process of a relay node. Figure 5 This is an example of a configuration update process of a relay node according to an embodiment of the present invention.

[0491] like Figure 5 As shown, the process includes the following steps:

[0492] Step 2-1: The fourth node sends a first configuration request message to the first node. The message is mainly used to update the configuration of the first node. The first configuration request message may include at least one of the following information:

[0493] ■ The fifth information related to the address is the address-related information provided by the fourth node to the first node. The information is used for data transmission between the first node and the fourth node. The content of the information can be found in the above “ middle Address-related information required by the relay node ”

[0494] ■Fifth user configuration information, the content of this information can be found in the above " User configuration information In addition, for a user, the information may optionally include at least one of the following information:

[0495] ■User identification information before configuration update, such as old gNB-CU UE F1AP ID and / or old gNB-DUUE F1AP ID

[0496] ■After configuration update, user identification information, such as new gNB-CU UE F1AP ID and / or new gNB-DUUE F1AP ID

[0497] ■ The fifth mapping relationship information, which reflects the mapping relationship between the information used before and after the first node configuration is updated, is used to update the configuration information used by the first node for data transmission. The content of this information can be found in the above " Mapping information", in which the new information is the information required to be used after the first node configuration is updated, and the old information is the information used before the first node configuration is updated. The beneficial effect of this information is that it can help the first node update the configuration information required to transmit the data of its distribution unit (such as data of different users, F1AP signaling, etc.) through less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data separately.

[0498] The above-mentioned first configuration request message may include only one of the "fifth user configuration information" and the "fifth mapping relationship information". If only the "fifth user configuration information" is included, the fourth node will provide updated configuration information for each user of the first node respectively. If only the "fifth mapping relationship information" is included, the first node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0499] Step 2-2: Optionally, the first node sends a first configuration response message to the fourth node. The message is mainly used to confirm the first configuration request message. Furthermore, the message can also be used to notify the first node of the configuration information update. The message includes at least one of the following information:

[0500] ■ Sixth user configuration information, the content of this information can be found in the above " User configuration information In addition, for a user, the information may optionally include at least one of the following information:

[0501] ■User identification information before configuration update, such as old gNB-CU UE F1AP ID and / or old gNB-DUUE F1AP ID

[0502] ■After configuration update, user identification information, such as new gNB-CU UE F1AP ID and / or new gNB-DUUE F1AP ID

[0503] ■ Sixth mapping relationship information, which reflects the mapping relationship between the information used before and after the first node configuration is updated. This information is used to update the configuration information used by the first node for data transmission. The content of this information can be found in the above " Mapping information", in which the new information is the information required to be used after the first node configuration is updated, and the old information is the information used before the first node configuration is updated. The beneficial effect of this information is that it can help the first node update the configuration information required to transmit the data of its distribution unit (such as data of different users, F1AP signaling, etc.) through less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data separately.

[0504] The above-mentioned first configuration response message may include only one of the "sixth user configuration information" and the "sixth mapping relationship information". If only the "sixth user configuration information" is included, the first node will provide updated configuration information for each user respectively. If only the "sixth mapping relationship information" is included, the fourth node can use this information to simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), which can save signaling overhead.

[0505] The above process may be implemented in different ways. In the following embodiments, the specific content of the information contained in each message can be found in the above " User configuration information "," Address-related information required by relay nodes "," Mapping related information interest "," Configuration information related to the relay node's backhaul link channel ". The processes involved in the following embodiments are steps 2-1 to 2-2 above. The difference between different embodiments is that the information contained in each message may be different. In order to simplify the description of each embodiment and highlight the differences in information contained in different implementation methods, the information contained in each message is not fully listed. For those unlisted information, please refer to the description in steps 2-1 to 2-2 above.

[0506] Example 2-1 (update configuration is completely determined by the anchor node)

[0507] Step 2-1: The fourth node sends a first configuration request message to the first node. The message is mainly used to update the configuration of the first node. The first configuration request message may include at least one of the following information:

[0508] ■Fifth user configuration information, which includes at least one of the following information:

[0509] ■User identification information before configuration update, such as old gNB-CU UE F1AP ID and / or old gNB-DUUE F1AP ID

[0510] ■After configuration update, user identification information, such as new gNB-CU UE F1AP ID and / or new gNB-DUUE F1AP ID

[0511] Information about the user's radio bearer. For a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB), this information includes at least one of the following:

[0512] ◆User identification information before configuration update, such as old gNB-CU UE F1AP ID and / or old gNB-DUUE F1AP ID

[0513] After the configuration is updated, the user's identification information, such as new gNB-CU UE F1AP ID and / or new gNB-DUUE F1AP ID

[0514] ◆User radio bearer identification information, such as UE RB ID

[0515] ◆Identification information, such as DRB ID, SRB ID

[0516] Information related to the uplink data tunnel. For a tunnel, the information includes at least one of the following: tunnel identification information, IP address, TEID, routing identification information, next hop node identification information, return link channel identification information, etc.

[0517] ◆ Information about the tunnel of downlink data. For a tunnel, this information includes at least one of the following: tunnel identification information, IP address, TEID

[0518] ■Fifth mapping relationship information, which includes at least one of the following information:

[0519] ■ Address mapping information. For an address mapping, this information includes at least one of the following:

[0520] ◆ Address identification information on the relay node side

[0521] ◆Information about the address of the new relay node

[0522] ◆Information about the address of the old relay node

[0523] ◆Identification information of the address on the anchor node side

[0524] ◆Information about the address of the new anchor node

[0525] ◆Information about the address of the old anchor node

[0526] Tunnel mapping information. For a tunnel mapping, this information includes at least one of the following:

[0527] ◆Tunnel identification information for uplink data

[0528] ◆New uplink data tunnel related information

[0529] ◆ Information about the old uplink data tunnel

[0530] ◆Tunnel identification information for downlink data

[0531] ◆New downlink data tunnel related information

[0532] ◆ Information about the old downlink data tunnel

[0533] ■ Transport network layer association mapping information. For a transport network layer association, this information includes at least one of the following:

[0534] ◆Identification information associated with the transport network layer on the anchor node side

[0535] ◆Transmission network layer associated information on the new anchor node side

[0536] ◆Transmission network layer related information on the old anchor node side

[0537] ◆Identification information associated with the transmission network layer on the relay node side

[0538] ◆Transmission network layer related information on the new relay node side

[0539] ◆Transmission network layer related information on the old relay node side

[0540] ■Mapping information for non-user plane data transmission

[0541] ■ Routing identifier mapping information. For a routing identifier mapping, this information includes at least one of the following:

[0542] New routing information

[0543] ◆Old routing identification information

[0544] Next-hop node mapping information. For a next-hop node mapping, this information includes at least one of the following:

[0545] ◆Identification information of the new next-hop node

[0546] ◆The identification information of the old next hop node

[0547] ■ Mapping information of the backhaul link channel. For the mapping of a backhaul link channel, this information includes at least one of the following:

[0548] ◆Identification information of the new backhaul link channel

[0549] ◆Identification information of the old backhaul link channel

[0550] ■Applicable information

[0551] ■Exception information

[0552] Step 2-2: Optionally, the first node sends a first configuration response message to the fourth node, where the message is mainly used to confirm the first configuration request message.

[0553] Example 2-2 (Update Configuration Determined by Anchor Node and Relay Node Separately)

[0554] Step 2-1: The fourth node sends a first configuration request message to the first node. The message is mainly used to update the configuration of the first node. The first configuration request message may include at least one of the following information:

[0555] ■ Fifth user configuration information: For a user radio bearer, this information may not include "downlink data tunnel related information". For other information, please refer to step 2-1 in the above embodiment 2-1.

[0556] ■Fifth mapping relationship information, which may not include "information related to the address of the new relay node side", and / or "information related to the address of the old relay node side", and / or "information related to the tunnel of the new downlink data", and / or "information related to the tunnel of the old downlink data", and / or "information associated with the transmission network layer of the new relay node side", and / or "information associated with the transmission network layer of the old relay node side". For other information, please refer to step 2-1 of the above embodiment 2-1.

[0557] Step 2-2: Optionally, the first node sends a first configuration response message to the fourth node. The message is mainly used to confirm the first configuration request message. Furthermore, the message can also be used to notify the first node of the configuration information update. The message includes at least one of the following information:

[0558] ■Sixth user configuration information, which includes at least one of the following information:

[0559] ■User identification information before configuration update, such as old gNB-CU UE F1AP ID and / or old gNB-DUUE F1AP ID

[0560] ■After configuration update, user identification information, such as new gNB-CU UE F1AP ID and / or new gNB-DUUE F1AP ID

[0561] Information about the user's radio bearer. For a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB), this information includes at least one of the following:

[0562] ◆User identification information before configuration update, such as old gNB-CU UE F1AP ID and / or old gNB-DUUE F1AP ID

[0563] After the configuration is updated, the user's identification information, such as new gNB-CU UE F1AP ID and / or new gNB-DUUE F1AP ID

[0564] ◆User radio bearer identification information, such as UE RB ID

[0565] ◆Identification information, such as DRB ID, SRB ID

[0566] ◆ Information about the tunnel of downlink data. For a tunnel, this information includes at least one of the following: tunnel identification information, IP address, TEID

[0567] ■Sixth mapping relationship information, which includes at least one of the following information:

[0568] ■ Address mapping information. For an address mapping, this information includes at least one of the following:

[0569] ◆ Address identification information on the relay node side

[0570] ◆Information about the address of the new relay node

[0571] ◆Information about the address of the old relay node

[0572] Tunnel mapping information. For a tunnel mapping, this information includes at least one of the following:

[0573] ◆Tunnel identification information for downlink data

[0574] ◆New downlink data tunnel related information

[0575] ◆ Information about the old downlink data tunnel

[0576] ■ Transport layer network association mapping information. For a transport network layer association, this information includes at least one of the following:

[0577] ◆Identification information associated with the transmission network layer on the relay node side

[0578] ◆Transmission network layer related information on the new relay node side

[0579] ◆Transmission network layer related information on the old relay node side

[0580] ■Applicable information

[0581] ■Exception information

[0582] In one embodiment, an implementation of the above signaling is:

[0583] Step 2-1: The fourth node sends a first configuration request message to the first node. The message is mainly used to update the configuration of the first node. The first configuration request message may include at least one of the following information:

[0584] ■ Information related to uplink tunnels, including information related to one or more uplink tunnels. For an uplink tunnel, the information includes at least one of the following:

[0585] ■ Tunnel identification information for uplink data

[0586] ■ Information about the old uplink data tunnel, such as IP address and / or TEID

[0587] ■ Information about the new uplink data tunnel, such as IP address and / or TEID

[0588] ■Route identification information

[0589] ■Next hop node identification information

[0590] ■ Backhaul link channel identification information

[0591] ■ Information about transport network layer associations on the anchor node side, including one or more transport network layer associations on the anchor node side. For a transport network layer association on the anchor node side, the information includes at least one of the following information:

[0592] ■Identification information associated with the transport network layer on the anchor node side

[0593] IP address information

[0594] ■Port information

[0595] ■Indication of the usage of the transport network layer association on the new anchor node side

[0596] ■ Next-hop node mapping information, which includes one or more such mapping information. For a next-hop node mapping, the information includes at least one of the following information:

[0597] ■ Identification information of the new next-hop node

[0598] ■ Identification information of the old next-hop node

[0599] Step 2-2: Optionally, the first node sends a first configuration response message to the fourth node, where the message includes at least one of the following information:

[0600] ■ Information related to downlink tunnels, including information related to one or more downlink tunnels. For a downlink tunnel, the information includes at least one of the following:

[0601] ■Tunnel identification information for downlink data

[0602] ■ Information about the old downlink data tunnel, such as IP address and / or TEID

[0603] ■ Information about the new downlink data tunnel, such as IP address and / or TEID

[0604] ■ Address mapping information, which includes mapping information of one or more addresses. For an address, the information includes at least one of the following:

[0605] ■ Address identification information on the relay node side

[0606] ■ Information about the address of the new relay node, such as the IP address

[0607] ■ Information about the old relay node's address, such as the IP address

[0608] ■ Information about the transport network layer association on the relay node side, which includes one or more transport network layer associations on the relay node side. For a transport network layer association on the relay node side, the information includes at least one of the following information:

[0609] ■ Identification information associated with the transport network layer on the relay node side

[0610] IP address information

[0611] ■Port information

[0612] ■Indication of the usage of the transport network layer associated with the relay node

[0613] In one embodiment, another implementation of the above signaling is:

[0614] Step 2-1: The fourth node sends a first configuration request message to the first node. The message is mainly used to update the configuration of the first node. The configuration update is performed for one or more users, or for one or more radio bearers of one or more users. For a user or a user radio bearer, the first configuration request message may include at least one of the following information:

[0615] ■User identification information

[0616] ■User's radio bearer identification information, such as DRB ID

[0617] ■ Information related to uplink tunnels, including information related to one or more uplink tunnels of a user or a user radio bearer. For an uplink tunnel, this information includes at least one of the following:

[0618] ■ Tunnel identification information for uplink data

[0619] ■ Information about the old uplink data tunnel, such as IP address and / or TEID

[0620] ■ Information about the new uplink data tunnel, such as IP address and / or TEID

[0621] ■Route identification information

[0622] ■Next hop node identification information

[0623] ■ Backhaul link channel identification information

[0624] ■ Information about transport network layer associations on the anchor node side, including one or more transport network layer associations on the anchor node side. For a transport network layer association on the anchor node side, the information includes at least one of the following information:

[0625] ■Identification information associated with the transport network layer on the anchor node side

[0626] IP address information

[0627] ■Port information

[0628] ■Indication of the usage of the transport network layer association on the new anchor node side

[0629] ■ Next-hop node mapping information, which includes one or more such mapping information. For a next-hop node mapping, the information includes at least one of the following information:

[0630] ■ Identification information of the new next-hop node

[0631] ■ Identification information of the old next-hop node

[0632] Step 2-2: Optionally, the first node sends a first configuration response message to the fourth node. The configuration update is for one or more users, or for one or more radio bearers of users. For a user or a user radio bearer, the message includes at least one of the following information:

[0633] ■User identification information

[0634] ■User's radio bearer identification information, such as DRB ID

[0635] ■ Information related to downlink tunnels, including information related to one or more downlink tunnels. For a downlink tunnel, the information includes at least one of the following:

[0636] ■Tunnel identification information for downlink data

[0637] ■ Information about the old downlink data tunnel, such as IP address and / or TEID

[0638] ■ Information about the new downlink data tunnel, such as IP address and / or TEID

[0639] ■ Address mapping information, which includes mapping information of one or more addresses. For an address, the information includes at least one of the following:

[0640] ■ Address identification information on the relay node side

[0641] ■ Information about the address of the new relay node, such as the IP address

[0642] ■ Information about the old relay node's address, such as the IP address

[0643] ■ Information about the transport network layer association on the relay node side, which includes one or more transport network layer associations on the relay node side. For a transport network layer association on the relay node side, the information includes at least one of the following information:

[0644] ■ Identification information associated with the transport network layer on the relay node side

[0645] IP address information

[0646] ■Port information

[0647] ■Indication of the usage of the transport network layer associated with the relay node

[0648] In the above process, if Figure 5 , before step 2-1, it may also include step 2-0, that is, the other node sends a second configuration request message to the fourth node, the message includes the configuration information of the first node, and the fourth node can be helped to update the configuration information of the first node according to the information. The second configuration request message can refer to the above-mentioned invention Figure 4 Step 1-1 in the process.

[0649] The first configuration request message and the first configuration response message may use the existing gNB-CU CONFIGURATION UPDATE and gNB-CU CONFIGURATION UPDATE ACKNOWLEDGE messages, respectively, to transmit relevant information, or may use a newly defined non-user-associated F1AP message to transmit relevant information. Furthermore, the first configuration request message and the first configuration response message may use the existing UE CONTEXT SETUP SETUP / MODIFICATION REQUEST and UE CONTEXT SETUP SETUP / MODIFICATION RESPONSE messages, respectively, to transmit relevant information for a user, or may use other or newly defined user-associated F1AP messages.

[0650] Possible beneficial effects of the above process include: when the configuration information for data to be transmitted by the distributed unit of the relay node needs to be updated, the above process can effectively reduce the signaling required to update the configuration information. For example, the mapping-related information exchanged in the above process can help the receiving node simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration of different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration of different users), thereby reducing signaling overhead.

[0651] A third aspect of the present invention is a configuration interaction process of a relay node, which involves a fifth node, a sixth node and the first node. Figure 6 This is an example of the configuration interaction process of the relay node according to an embodiment of the present invention. Figure 3 (b) and Figure 3 The method in (c) is related to the method in which the source anchor node in the figure corresponds to the fifth node in the process, the target anchor node corresponds to the sixth node in the process, and the relay node 3 corresponds to the first node in the process. In another embodiment, the fifth node and the sixth node can be two different nodes. Furthermore, the distribution unit part of the first node maintains a connection with the fifth node, while the mobile terminal part of the first node is served by the sixth node. The data of the distribution unit part of the first node (such as the data of the user served by the distribution unit part, the control signaling generated by the distribution unit part, such as the F1AP message) will be transmitted by the backhaul link channel configured by the sixth node, and will be transmitted according to the path configured by the sixth node.

[0652] like Figure 6 As shown, the relay node configuration interaction process includes the following steps:

[0653] Step 3-1: The fifth node sends a third configuration request message to the sixth node. The message is used to provide the sixth node with configuration information related to the data served by the relay node (the distributed unit part of the first node). The message includes at least one of the following information:

[0654] ■ The seventh user configuration information, which is targeted at users accessing the first node (the distributed unit part of the first node), has the beneficial effect of sending this information to the sixth node: the sixth node can learn the configuration information of the data of the user accessing the first node. The information contained in this information can be found in the above " User configuration information Specifically, it shall include at least one of the following information:

[0655] ■ User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID. In one embodiment, this information may include multiple user identifications. This information may include at least one of the following:

[0656] gNB-CU UE F1AP ID

[0657] gNB-DU UE F1AP ID

[0658] C-RNTI

[0659] ◆Service area logo

[0660] ◆UE XnAP ID: In one embodiment, the ID is allocated by the fifth node. The above-mentioned identifier is only an example and does not exclude the inclusion of other identifiers.

[0661] ■ Information about the user's radio bearers. For a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB), the radio bearer may be requested to be added, modified, or deleted. This information includes at least one of the following:

[0662] User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0663] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0664] ◆Identification information, such as DRB ID, SRB ID

[0665] ◆ Information about the QoS of the radio bearer, which includes the configuration information of the QoS parameters of the radio bearer; in one embodiment, this information is the actual QoS information of the radio bearer; in another embodiment, this information is the QoS information that needs to be met by the receiving node, and this QoS information is different from the above-mentioned "actual QoS information of the radio bearer"

[0666] ◆Information about the QoS satisfied by the first node. This information is used to indicate information about the QoS that the first node can satisfy when serving the wireless bearer. This information is different from the above-mentioned "information about the QoS of the wireless bearer". The beneficial effect of this information is that the node that receives this information can learn about the QoS that the first node can satisfy when serving the user's wireless bearer, and determine how to configure other nodes to serve the user's wireless bearer, so that the first node and other nodes can jointly serve the user's wireless bearer and meet the QoS requirements of the wireless bearer. Another beneficial effect is that the node that receives this information can try to ensure that the first node serves the user's wireless bearer in accordance with the QoS indicated by this information, thereby eliminating the need to modify the configuration information of the first node when serving the user's wireless bearer.

[0667] ◆Information about the QoS that is not satisfied by the first node. This information is used to indicate information about the QoS that needs to be satisfied by other nodes in the network when jointly serving the wireless bearer except the first node. This information is different from the above-mentioned "information about the QoS of the wireless bearer". The beneficial effect of this information is that the node that receives this information can learn about the QoS that needs to be satisfied by other nodes except the first node when serving the user's wireless bearer, and determine how to configure other nodes to serve the user's wireless bearer, so that the first node and other nodes can jointly serve the user's wireless bearer and meet the QoS requirements of the wireless bearer. Another beneficial effect is that the node that receives this information can try to configure other nodes to serve the user's wireless bearer according to the QoS indicated by this information, thereby eliminating the need to modify the configuration information of the first node when serving the user's wireless bearer.

[0668] ◆Information about the uplink data tunnel, which may be one or more tunnels.

[0669] The information indicates the information on the anchor node (or the centralized unit of the anchor node or the user plane part of the centralized unit of the anchor node). For a tunnel, the information at least includes:

[0670] One of the following:

[0671] Tunnel identification information

[0672] IP address

[0673] TEID

[0674] Routing identification information, which is used to indicate the transmission path of the uplink data (furthermore, the uplink data is sent through the tunnel), including the address information of the receiving node (BAP address) and / or the transmission path identification information (path ID). Furthermore, based on this information, the relay node can add this information to the uplink data packet sent through the tunnel.

[0675] The identification information of the next-hop node. The next-hop node is the node that directly receives the uplink data when the relay node sends the uplink data (furthermore, the uplink data is sent through the above-mentioned tunnel). In other words, the relay node sends the uplink data to the next-hop node, which then directly or indirectly (through other nodes) sends the uplink data to the destination node. Based on this information, the relay node knows which node to send the uplink data to.

[0676] ● Identification information of the backhaul link channel, which is the backhaul link channel used by the relay node to send the uplink data (furthermore, the uplink data is sent through the above tunnel) to the above next-hop node. Based on this information, the relay node knows which backhaul link channel to use to send the uplink data.

[0677] Information about the downlink data tunnel. The tunnel may be one or more. This information indicates the relay node or the distribution unit of the relay node. For a tunnel, this information includes at least one of the following:

[0678] Tunnel identification information

[0679] IP address

[0680] TEID

[0681] ● The configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is sent through the above tunnel)

[0682] ● The configuration value information of the flow label field in the downlink data packet (furthermore, the downlink data packet is sent through the above tunnel)

[0683] ■ Information related to the first control signaling, which is used to provide information related to the control signaling or control signaling transmission, and includes at least one of the following information:

[0684] ■ The fifth node sends information to the first node, such as an F1AP message. In one embodiment, the information includes an IP packet of the F1AP message. After receiving the information, the sixth node sends the received information to the first node.

[0685] ■Control signaling type information, which indicates the type of control signaling transmitted. The control signaling transmitted may be the “information sent from the fifth node to the first node” contained in the above-mentioned “information related to the first control signaling”, or may be one or more control signalings transmitted between the fifth node and the first node. In one embodiment, the information may indicate control signaling type 1, control signaling type 2, etc., and different types may have different priorities, such as control signaling type 1 has the highest priority, control signaling type 2 has the second highest priority, etc. In another embodiment, the information may indicate user-associated control signaling (UE-associated signaling) or non-UE-associated control signaling (non-UE-associated signaling), etc. Furthermore, the information contained in the above-mentioned “information related to the first control signaling” is applicable to the control signaling type indicated by the “control signaling type information”.

[0686] ■ Receive the destination address information of the downlink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information of the first node side

[0687] ■ Receive the destination address information of the uplink control signaling, such as IP address, BAP address, etc.; further, the address information may be the address information of the fifth node side

[0688] Step 3-2: The sixth node sends a third configuration response message to the fifth node. The message is used to provide the fifth node with configuration information related to the data served by the relay node (the distributed unit portion of the first node). In one embodiment, the configuration information may be obtained by the sixth node after configuring the backhaul link channel and transmission path for the data of the first node. The message includes at least one of the following information:

[0689] ■ The eighth user configuration information, which is targeted at users accessing the first node (the distributed unit part of the first node), can be found in the above “ User configuration information Specifically, it shall include at least one of the following information:

[0690] ■ User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID. In one embodiment, this information may include multiple user identifications. This information may include at least one of the following:

[0691] gNB-CU UE F1AP ID

[0692] gNB-DU UE F1AP ID

[0693] C-RNTI

[0694] ◆Service area logo

[0695] ◆UE XnAP ID1, in one embodiment, this ID is allocated by the fifth node and is obtained from the above step 3-1 ◆UE XnAP ID2, in one embodiment, this ID is allocated by the sixth node The above identifications are only examples and do not exclude the inclusion of other identifications.

[0696] ■ Information about the user's radio bearer. In one embodiment, the radio bearer may be accepted by the sixth node or not accepted by the sixth node. For a radio bearer (such as a data radio bearer (DRB) or a signaling radio bearer (SRB), the information includes at least one of the following:

[0697] User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0698] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0699] ◆Identification information, such as DRB ID, SRB ID

[0700] Information about the QoS that the sixth node can satisfy. In one embodiment, the information is the QoS that the sixth node can satisfy based on the status of the network it serves. In another embodiment, the information is the QoS that the sixth node can satisfy after configuring the backhaul link channel and transmission path that serve the radio bearer.

[0701] Information about uplink data tunnels. The tunnels may be one or more. This information indicates information on the anchor node (or the centralized unit of the anchor node or the user plane portion of the centralized unit of the anchor node). For each tunnel, this information includes at least one of the following:

[0702] Tunnel identification information

[0703] IP address

[0704] TEID

[0705] ●Route identification information

[0706] ●Next hop node identification information

[0707] ● Backhaul link channel identification information

[0708] Part or all of the above information is configured by the sixth node. If step 3-1 also includes the above information, it may be different from the information included in step 3-1.

[0709] Information about the downlink data tunnel. The tunnel may be one or more. This information indicates the relay node or the distribution unit of the relay node. For a tunnel, this information includes at least one of the following:

[0710] Tunnel identification information

[0711] IP address

[0712] TEID

[0713] ● The configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is sent through the above tunnel)

[0714] ● The configuration value information of the flow label field in the downlink data packet (furthermore, the downlink data packet is sent through the above tunnel)

[0715] Part or all of the above information is generated by the sixth node.

[0716] After receiving the information, the fifth node may add the configuration value of the DSCP field and / or the configuration value of the flow label field to the relevant data packet sent to the first node according to the information.

[0717] First tunnel information, which indicates address-related information used by the sixth node to receive user data from the fifth node. In one embodiment, after receiving the data, the sixth node will forward it to the first node. This information includes at least one of the following:

[0718] Tunnel identification information

[0719] IP address

[0720] TEID

[0721] The use of this information is Figure 3 The method of (c) is related to that the fifth node sends a data packet to the sixth node according to the address indicated by the information. After receiving the data packet, the sixth node sends the data packet to the first node. Before sending the data packet, the sixth node may replace the information contained in the data packet with the information contained in the above-mentioned "information related to the tunnel of downlink data", for example, replace the IP address in the data packet with the IP address contained in the above-mentioned "information related to the tunnel of downlink data".

[0722] Second tunnel information, which indicates address-related information used by the sixth node to receive user data from the first node. In one embodiment, the sixth node forwards the received data to the fifth node. This information includes at least one of the following:

[0723] Tunnel identification information

[0724] IP address

[0725] TEID

[0726] The use of this information is Figure 3 The method of (c) is related to the above, that is, the first node sends a data packet to the sixth node according to the address indicated by the information. After receiving the data packet, the sixth node will send the data packet to the fifth node. Before sending the data packet, the sixth node may replace the information contained in the data packet with the information contained in the above "information related to the tunnel of uplink data", for example, replace the IP address in the data packet with the IP address contained in the above "information related to the tunnel of uplink data". Therefore, if the above "second tunnel information" is included, the fifth node will send the information to the first node.

[0727] ■ Information related to the second control signaling, which is used to provide information related to the control signaling or control signaling transmission, and includes at least one of the following information:

[0728] ■ Information sent by the first node to the fifth node, such as an F1AP message, in one embodiment, the information includes an IP packet of the F1AP message; the information may be an IP packet sent by the first node to the sixth node.

[0729] ■Control signaling type information, which indicates the type of control signaling transmitted. The control signaling transmitted may be the "information sent from the first node to the fifth node" contained in the above-mentioned "information related to the second control signaling", or may be one or more control signalings transmitted between the first node and the fifth node. In one embodiment, the information may indicate control signaling type 1, control signaling type 2, etc., and different types may have different priorities, such as control signaling type 1 has the highest priority, control signaling type 2 has the second highest priority, etc. In another embodiment, the information may indicate user-associated control signaling (UE-associated signaling) or non-UE-associated control signaling (non-UE-associated signaling), etc. Furthermore, the information contained in the above-mentioned "information related to the second control signaling" is applicable to the control signaling type indicated by the "control signaling type information".

[0730] ■ Receive the destination address information of the downlink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information of the first node side

[0731] ■Configuration value information of the DSCP field in the data packet carrying control signaling

[0732] ■Configuration value information of the flow label field in the data packet carrying control signaling

[0733] ■ Receive the destination address information of the uplink control signaling, such as IP address, BAP address, etc.; further, the address information may be the address information of the fifth node side

[0734] ■ Route identification information, which is used to indicate the transmission path of the control signaling (in one embodiment, the control signaling is the control signaling sent by the first node), including the address information (BAP address) of the receiving node (such as the distribution unit of the sixth node) and / or the transmission path identification information (path ID). Furthermore, based on this information, the first node can add this information to the data packet carrying the control signaling.

[0735] ■ The identification information of the next hop node. The next hop node is the node that directly receives the control signaling when the first node sends the control signaling. In other words, the first node sends the control signaling to the next hop node, which then sends it directly or indirectly (through other nodes) to the destination node. Based on this information, the first node knows which node to send the control signaling to.

[0736] ■ Identification information of the backhaul link channel, which is the backhaul link channel used by the first node to send control signaling to the next hop node. Based on this information, the first node knows which backhaul link channel to use to send control signaling.

[0737] ■ The eighth mapping relationship information, which reflects the mapping relationship before and after the first node configuration information is updated, is used to update the configuration information used by the first node for data transmission. The content of this information can be found in the above " Mapping information ", in which the new information is the information required to be used after the first node configuration is updated, and the old information is the information used before the first node configuration is updated. The beneficial effect of this information is that it can help the first node update the configuration information required to transmit the data of its distribution unit (such as data of different users, F1AP signaling, etc.) through less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data separately.

[0738] In the above process, step 3-3 may be included after step 3-2, that is, the fifth node sends a fourth configuration request message to the first node, which is used to send part or all of the configuration information received in step 3-2 to the first node, such as for a wireless bearer, sending the received "information related to the tunnel of uplink data" to the first node; the information sent to the first node in step 3-3 can refer to the information received in the above step 3-2, and will not be introduced in detail here.

[0739] In the above process, step 3-0 may be included before step 3-1, i.e., the user data configuration interaction process, in which the fifth node and the first node may exchange configuration information of the data served by the first node, such as the configuration information of the user radio bearer (see the above " User configuration information ”), which helps the fifth node generate the information in the above step 3-1.

[0740] The above process can be performed for only one user, for multiple users, or for control signaling (that is, the above steps 3-1 and 3-2 are used to transmit information related to control signaling, see the above information related to the first control signaling and the information related to the second control signaling).

[0741] When the fifth node and the sixth node are two different nodes, the above process may also include the following implementation methods:

[0742] The fifth node and the sixth node will both serve the first node, such as the fifth node and the sixth node are two different anchor nodes, or centralized units of two different anchor nodes. The first node (or the mobile terminal part of the first node, or the distribution unit part of the first node) can be served by these two nodes (in one embodiment, the mobile terminal part of the first node is configured with dual connections, connected to the fifth node and the sixth node respectively). For another example, the data served by the distribution unit part of the first node will be served by the network controlled by the fifth node and / or the sixth node; further, the embodiment may also include a seventh node (in one embodiment, the seventh node may also be a relay node), which accesses the network through the first node. The seventh node may be directly connected to the first node, or may be connected to the seventh node through one or more nodes; further, the data served by the seventh node (such as the data of the user accessing the seventh node, the data of the seventh node itself, such as the data of the distribution unit part of the seventh node) may also be served by the network controlled by the fifth node and / or the sixth node. In this embodiment, the interaction process is as follows. Figure 6 shown.

[0743] Step 3-1: The fifth node sends a third configuration request message to the sixth node. The message is used to provide the sixth node with configuration information related to data served by the relay node (such as the distributed unit portion of the first node). The message includes at least one of the following information:

[0744] ■ Identification information of the first node. In one embodiment, the identification information is the identification information of the mobile terminal portion of the first node, such as the XnAP UE ID. In another embodiment, the identification information is the identification information of the distributed unit portion of the first node, such as the gNB-DU ID, BAP address, etc.

[0745] ■ The seventh user configuration information, which is targeted at users who access the first node (the distributed unit part of the first node), can also be users who access the seventh node (the distributed unit part of the seventh node), can also be the distributed unit part of the first node, or can also be the distributed unit part of the seventh node. One beneficial effect of sending this information to the sixth node is that the sixth node can learn the configuration information of the user's data. The information contained in this information can be found in the above " User configuration information Specifically, it shall include at least one of the following information:

[0746] ■ User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID. In one embodiment, this information may include multiple user identifications. This information may include at least one of the following:

[0747] gNB-CU UE F1AP ID

[0748] gNB-DU UE F1AP ID

[0749] C-RNTI

[0750] ◆Service area logo

[0751] ◆UE XnAP ID: In one embodiment, the ID is allocated by the fifth node. The above-mentioned identifier is only an example and does not exclude the inclusion of other identifiers.

[0752] ■Information related to user data. In one embodiment, the user data may be data of one or more radio bearers. For a radio bearer (such as a data radio bearer DRB, a signaling radio bearer SRB), the radio bearer may be requested to be added, modified, or deleted. Furthermore, the user data may be user data served by the first node (such as data of users accessing the first node, or data generated by the first node itself, or data generated by the distribution unit of the first node). In addition, the user data may be uplink data, downlink data, or both uplink and downlink data. The information includes at least one of the following information:

[0753] ◆ User data identification information, which is used to identify a type of data, such as traffic profile ID, traffic ID

[0754] ◆ Information about the QoS of user data, which includes configuration information about the QoS parameters of the user data; the content of this configuration information can be found in the above-mentioned “Information about the Quality of Service (QoS) of the Radio Bearer”. In one embodiment, this information is the actual QoS information of the user data; in another embodiment, this information is the QoS information that needs to be met by the receiving node, and this QoS information is different from the above-mentioned “actual QoS information of the user data”. Furthermore, the user data can be one or more radio bearers.

[0755] ◆Indication of the direction of user data transmission, such as uplink or downlink

[0756] ◆Indication of the user data type, which includes at least one of the following types:

[0757] ●User plane data, such as F1-U interface data

[0758] ●Control plane data, such as F1-C interface data

[0759] ●User-related control plane data, such as UE-associated F1-C data

[0760] ● Non-UE-associated control plane data, such as non-UE-associated F1-C data

[0761] ●Non-F1 interface data, such as non-F1 data

[0762] ●BAP layer control data, such as BAP Control PDU

[0763] ◆Information related to the address. In one embodiment, the information is address-related information, which includes IP address information and / or port information. Furthermore, the information is used to serve the control plane data.

[0764] ◆IP address information. In one embodiment, the IP address is the IP address used by the first node and / or the seventh node to receive data. In another embodiment, the IP address is the IP address used by the first node and / or the seventh node to receive data on a tunnel.

[0765] ◆Information related to the first data route, which indicates the information required to be used when transmitting user data (such as the information required to be carried in the data packet). In one embodiment, the information is BAP route identification information (in one embodiment, the information includes BAP address information and / or path identification information. Further, the BAP address information is the BAP address of the destination receiving node). Further, the BAP route identification information is information used when sending downlink data and / or uplink data. In addition, the information can be information configured by the fifth node, and further, it is information required for the fifth node to configure the sixth node.

[0766] User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0767] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0768] ◆Radio bearer identification information, such as DRB ID, SRB ID

[0769] Information about downlink data tunnels. The tunnels may be one or more. This information indicates information about a relay node or a distribution unit of a relay node. In one embodiment, the relay node may be the first node. In another embodiment, the relay node may be the seventh node. For one tunnel, this information includes at least one of the following:

[0770] Tunnel identification information

[0771] IP address

[0772] TEID

[0773] ● The configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is sent through the above tunnel)

[0774] ● The configuration value information of the flow label field in the downlink data packet (furthermore, the downlink data packet is sent through the above tunnel)

[0775] Information related to uplink data tunnels. The tunnels may be one or more. The information indicates information on the anchor node (or the centralized unit of the anchor node or the user plane portion of the centralized unit of the anchor node). In one embodiment, the anchor node is the fifth node, and in another embodiment, the anchor node is the sixth node. For one tunnel, the information includes at least one of the following information:

[0776] Tunnel identification information

[0777] IP address

[0778] TEID

[0779] Routing identification information, which is used to indicate the transmission path of the uplink data (furthermore, the uplink data is sent through the tunnel), including the address information of the receiving node (BAP address) and / or the transmission path identification information (path ID). Furthermore, based on this information, the relay node can add this information to the uplink data packet sent through the tunnel.

[0780] The identification information of the next-hop node. The next-hop node is the node that directly receives the uplink data when the relay node sends the uplink data (furthermore, the uplink data is sent through the above-mentioned tunnel). In other words, the relay node sends the uplink data to the next-hop node, which then directly or indirectly (through other nodes) sends the uplink data to the destination node. Based on this information, the relay node knows which node to send the uplink data to.

[0781] ● Identification information of the backhaul link channel, which is the backhaul link channel used by the relay node to send the uplink data (furthermore, the uplink data is sent through the above tunnel) to the above next-hop node. Based on this information, the relay node knows which backhaul link channel to use to send the uplink data.

[0782] Step 3-2: The sixth node sends a third configuration response message to the fifth node. This message is used to provide the fifth node with configuration information related to the data served by the relay node (the distributed unit portion of the first node, or the distributed unit portion of the seventh node). In one embodiment, this configuration information may be obtained by the sixth node after configuring the backhaul link channel and transmission path for the data of the first node (or the data of the seventh node). The message includes at least one of the following information:

[0783] ■ Identification information of the first node. In one embodiment, the identification information is the identification information of the mobile terminal portion of the first node, such as the XnAP UE ID. In another embodiment, the identification information is the identification information of the distributed unit portion of the first node, such as the gNB-DU ID, BAP address, etc.

[0784] ■ The eighth user configuration information, which is targeted at users who access the first node (the distributed unit part of the first node), can also be users who access the seventh node (the distributed unit part of the seventh node), can also be the distributed unit part of the first node, or can also be the distributed unit part of the seventh node. The information contained in this information can be found in the above " User configuration information Specifically, it shall include at least one of the following information:

[0785] ■ User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID. In one embodiment, this information may include multiple user identifications. This information may include at least one of the following:

[0786] gNB-CU UE F1AP ID

[0787] gNB-DU UE F1AP ID

[0788] C-RNTI

[0789] ◆Service area logo

[0790] ◆UE XnAP ID1, in one embodiment, this ID is assigned by the fifth node and is obtained from step 3-1 above

[0791] ◆UE XnAP ID2. In one embodiment, the ID is allocated by the sixth node. The above-mentioned identifier is only an example and does not exclude the inclusion of other identifiers.

[0792] ■ Information related to user data. In one embodiment, the user data may be data of one or more radio bearers. The data may be user data that can be served by the sixth node, or user data that cannot be served by the sixth node. Furthermore, the user data may be user data served by the first node (such as data of users accessing the first node, or data generated by the first node itself, or data generated by the distribution unit of the first node). In addition, the data may be uplink data, downlink data, or both uplink and downlink data. The information includes at least one of the following:

[0793] ◆ User data identification information, which is used to identify a type of data, such as traffic profile ID, traffic ID

[0794] Configuration information related to downlink data packets, which is used to indicate the configuration information required for downlink data transmission. This information includes at least one of the following:

[0795] ●Configuration value information of the DSCP field of the downlink data packet

[0796] ●Configuration value information of the flow label field of the downstream data packet

[0797] ●Information related to the second data route, which indicates the information required to be used when transmitting user data (such as information required to be carried in a data packet). In one embodiment, the information is BAP route identification information (in one embodiment, the information includes BAP address information and / or path identification information. Further, the BAP address information is the BAP address of the destination receiving node, such as the BAP address of the first node or the seventh node, or the BAP address of a non-destination receiving node. For example, when the data is sent to the seventh node, the non-destination receiving node may be the first node). In addition, the information may be the "information related to the first data route" received in step 3-1, or the information set by the sixth node (such as information different from the above-mentioned "information related to the first data route". For another example, when the sixth node finds that the "information related to the first data route" received in step 3-1 has been used by the sixth node for sending other data, it may provide an update information to the fifth node, i.e., information different from the above-mentioned "information related to the first data route"). Further, after the fifth node receives the information, it may be used to configure the sending of data, such as configuring the sending of user data at the first node.

[0798] Configuration information for receiving user data, where the configuration information indicates configuration information used by the relay node when receiving user data. In one embodiment, the relay node may be the first node, and the information may be used by the fifth node to configure the first node. The information includes at least one of the following information:

[0799] ■ Cell group indication information, which is used to indicate the cell group required to receive user data, such as MCG, SCG, Cell Group ID. In one embodiment, this information can indicate the cell group required for the first node to receive user data.

[0800] ■ Prior-hop node identification information, such as gNB-ID, cell group identification information, and BAP address information. In one embodiment, the prior-hop node is the node that sends data to the first node.

[0801] ■ Identification information of the backhaul link channel (ingress BH RLC channel) for receiving data. In one embodiment, the backhaul link channel may be the backhaul link channel for receiving data at the first node.

[0802] Configuration information related to uplink data packets. This information is used to indicate the configuration information required for uplink data transmission. This information includes at least one of the following:

[0803] ● Information related to the third data route, which indicates the information required to be used when transmitting user data (such as the information required to be carried in the data packet). In one embodiment, the information is BAP routing identification information (in one embodiment, the information includes BAP address information and / or path identification information. Further, the BAP address information can be the BAP address of the destination receiving node). Further, when the fifth node receives the information, it can be used to configure the transmission of data, such as configuring the transmission of user data at the first node.

[0804] Configuration information for sending user data, which is used to indicate configuration information used by the relay node when sending user data. In one embodiment, the relay node may be the first node, and the information may be used by the fifth node to configure the first node. The information includes at least one of the following information:

[0805] ■ Cell group indication information, which is used to indicate the cell group required to send user data, such as MCG, SCG, Cell Group ID. In one embodiment, this information can indicate the cell group required for the first node to send user data.

[0806] ■ Identification information of the next-hop node, such as gNB-ID, cell group identification information, and BAP address information. In one embodiment, the next-hop node is the node that receives the data sent by the first node.

[0807] ■ Identification information of the backhaul link channel (egress BH RLC channel) used to send data. In one embodiment, the backhaul link channel may be the backhaul link channel used by the first node to send data.

[0808] User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0809] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0810] ◆Identification information, such as DRB ID, SRB ID

[0811] Information about the QoS that the sixth node can satisfy. In one embodiment, the information is the QoS that the sixth node can satisfy based on the status of the network it serves. In another embodiment, the information is the QoS that the sixth node can satisfy after configuring the backhaul link channel and transmission path that serve the radio bearer.

[0812] Information about uplink data tunnels. The tunnels may be one or more. This information indicates information on the anchor node (or the centralized unit of the anchor node or the user plane portion of the centralized unit of the anchor node). For each tunnel, this information includes at least one of the following:

[0813] Tunnel identification information

[0814] IP address

[0815] TEID

[0816] ●Route identification information

[0817] ●Next hop node identification information

[0818] ● Backhaul link channel identification information

[0819] Part or all of the above information is configured by the sixth node. If step 3-1 also includes the above information, it may be different from the information included in step 3-1.

[0820] Information about the downlink data tunnel. The tunnel may be one or more. This information indicates the relay node or the distribution unit of the relay node. For a tunnel, this information includes at least one of the following:

[0821] Tunnel identification information

[0822] IP address

[0823] TEID

[0824] ● The configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is sent through the above tunnel)

[0825] ● The configuration value information of the flow label field in the downlink data packet (furthermore, the downlink data packet is sent through the above tunnel)

[0826] Part or all of the above information is generated by the sixth node.

[0827] After receiving the information, the fifth node may add the configuration value of the DSCP field and / or the configuration value of the flow label field to the relevant data packet sent to the first node according to the information.

[0828] In the above process, step 3-2 may further include step 3-3, that is, the fifth node sends a fourth configuration request message to the first node. The message is used to configure data transmission and / or reception at the first node. The data may be data of the first node (such as data of a user accessing the first node, or data of a distributed unit portion of the first node), or data of the seventh node (such as data of a user accessing the seventh node, or data of a distributed unit portion of the seventh node). The message includes at least one of the following information:

[0829] ■ Cell group indication information, such as MCG, SCG, and Cell Group ID. In one embodiment, this information is used to indicate the cell group (such as the ingress cell group) to which the first node receives user data. The received data may also need to be sent by the first node. In another embodiment, this information is used to indicate the cell group (such as the egress cell group) to which the first node sends user data.

[0830] ■ Prior-hop node identification information, such as gNB-ID, cell group identification information, and BAP address information. In one embodiment, the prior-hop node is the node that sends data to the first node, and the data may need to be sent by the first node.

[0831] ■ Identification information of the backhaul link channel (ingress BH RLC channel) for receiving data. In one embodiment, the backhaul link channel may be the backhaul link channel used by the first node to receive data. The received data may also need to be sent by the first node.

[0832] ■ Identification information of the next-hop node, such as gNB-ID, cell group identification information, and BAP address information. In one embodiment, the next-hop node is the node that receives the data sent by the first node.

[0833] ■ Identification information of the backhaul link channel (egress BH RLC channel) used to send data. In one embodiment, the backhaul link channel may be the backhaul link channel used by the first node to send data.

[0834] ■ Routing identification information contained in the received data, such as an ingress BAP routing ID. In one embodiment, this information is BAP routing identification information (in one embodiment, this information includes BAP address information and / or path identification information. Further, the BAP address information is the BAP address of the destination receiving node, such as the BAP address of the first node or the seventh node, or the BAP address of the distribution unit portion of the fifth node or the sixth node, or the BAP address of a non-destination receiving node. For example, when the data is sent to the seventh node, the non-destination receiving node may be the first node). In another embodiment, this information is the "information related to the second data routing" in step 3-2 above.

[0835] ■New routing identification information or routing identification information of the sent data, such as a new BAP routing ID (new BAProuting ID) or an egress BAP routing ID (egress BAP routing ID). This information indicates the routing identification information that the first node needs to add when sending data, or indicates that the first node needs to update the routing identification information contained in the data packet to the routing identification indicated by the information when sending data. In one embodiment, the information is BAP routing identification information (in one embodiment, the information includes BAP address information and / or path identification information. Further, the BAP address information is the BAP address of the destination receiving node, such as the BAP address of the first node or the seventh node, or the BAP address of the distribution unit part of the fifth node or the sixth node, or the BAP address of a non-destination receiving node. For example, when the data is sent to the seventh node, the non-destination receiving node may be the first node). Furthermore, the information can be used to update information in a data packet received by the first node. In one embodiment, the first node can update the routing identification information carried in any received data packet to the "new routing identification information." In another embodiment, the first node can update the routing identification in a received data packet containing the above-mentioned "routing identification information contained in the received data" to the "new routing identification information." In another embodiment, the first node can update the routing identification information of received specific data (such as data sent through the cell group indicated by the above-mentioned "cell group indication information," and / or data sent by the node indicated by the above-mentioned "prior-hop identification information," and / or data received through the channel indicated by the above-mentioned "identification information of the return link channel for receiving data (ingress BH RLC channel)") to the "new routing identification information." In another embodiment, the information can be the "information related to the first data routing" in the above-mentioned step 3-1. In another embodiment, the information can be the "information related to the third data routing" in the above-mentioned step 3-2.

[0836] The third configuration request message and the third configuration response message in the above process may be user-associated messages or non-UE-associated messages. Existing Xn interface messages may be reused, such as the NG-RAN Node configuration update and NG-RAN node configuration update acknowledgment messages in TS38.423, and for example, the S-Node addition / modification request and S-Node addition / modification Response messages (further, the S-Node addition / modification request and S-Node addition / modification Response messages may be for the mobile terminal part of the first node or for the user accessing the first node or the seventh node). New messages may also be defined, such as UE Bearer Context Setup / Modification Request and UE Bearer Context Setup / Modification Response (UE bearer context setup / modification response) message (this newly defined message may be for the mobile terminal part of the first node or for the user accessing the first node or the seventh node), or other messages.

[0837] The fourth configuration request message may be an RRC message (such as an RRCReconfiguration message) or an F1AP message (such as a BAP MAPPING CONFIGURATION message, a BAP mapping configuration message).

[0838] Furthermore, when the above process is used to configure the sixth node to serve one or more users accessing the first node or the seventh node, the above process is different from the S-Node addition / modification process on the existing Xn interface, which is intended to add an auxiliary node for the user or modify the configuration of the auxiliary node. However, in the above process of the present invention, the sixth node is not the user's auxiliary node, and the user is connected to the fifth node. The sixth node only configures the return link channel and transmission path used for user data transmission, and the sixth node does not configure the user's wireless bearer.

[0839] The beneficial effects of the above process include at least: when the relay node migrates, the communication between the relay node and the source node can be maintained, avoiding the interruption of user data transmission and the increase of delay; when the relay node is connected to multiple anchor nodes, user data can be sent through the multiple anchor nodes, sharing the load of the relay node, and allowing the data of the relay node to be transmitted in the networks served by different anchor nodes.

[0840] The third aspect of the present invention also includes another process, namely, the configuration interaction process of the relay node triggered by the sixth node, Figure 7 This is another example of the configuration interaction process of the relay node according to an embodiment of the present invention. Figure 7 As shown, the process includes the following steps:

[0841] Step 4-1: The sixth node sends a fifth configuration request message to the fifth node. The message is used to update the configuration information of the data of the service relay node to the fifth node. The message includes at least one of the following information:

[0842] ■ The eighth user configuration information, which is targeted at users accessing the first node (the distributed unit part of the first node), can be found in the above “ User configuration information Specifically, it shall include at least one of the following information:

[0843] ■ User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID. In one embodiment, this information may include multiple user identifications. This information may include at least one of the following:

[0844] gNB-CU UE F1AP ID

[0845] gNB-DU UE F1AP ID

[0846] C-RNTI

[0847] ◆Service area logo

[0848] ◆UE XnAP ID: In one embodiment, the ID is allocated by the fifth node. The above-mentioned identifier is only an example and does not exclude the inclusion of other identifiers.

[0849] Information about the user's radio bearers. For a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB), the radio bearer may be requested to be modified or deleted (if the request is to be deleted, the fifth node may delete the radio bearer after receiving the request). This information includes at least one of the following:

[0850] User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0851] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0852] ◆Identification information, such as DRB ID, SRB ID

[0853] ◆ Information about the QoS satisfied by the sixth node, which is used to indicate the QoS that the sixth node can satisfy when serving the radio bearer. The beneficial effect of this information is that the node receiving this information can learn the QoS that the sixth node can satisfy when serving the user's radio bearer and determine how to configure the first node to serve the user's radio bearer.

[0854] Information about the uplink data tunnel, which may be one or more tunnels. This information indicates the information on the anchor node (or the centralized unit of the anchor node or the user plane part of the centralized unit of the anchor node). For a tunnel, this information includes at least one of the following information: tunnel identification information, IP address, TEID, routing identification information, next hop node identification information, backhaul link channel identification information, etc.

[0855] Information about the downlink data tunnel, which may be one or more tunnels. This information indicates the information of the relay node or the distribution unit of the relay node. For a tunnel, this information includes at least one of the following: tunnel identification information, IP address, TEID, DSCP field configuration value information, flow label field configuration value information

[0856] ◆Reason information, which indicates the reason for modifying or deleting the radio bearer, such as resource limitation, etc.

[0857] First tunnel information, which indicates address-related information used by the sixth node to receive user data from the fifth node. In one embodiment, after receiving the data, the sixth node will forward it to the first node. This information includes at least one of the following:

[0858] Tunnel identification information

[0859] IP address

[0860] TEID

[0861] The use of this information is Figure 3The method of (c) is related to that the fifth node sends a data packet to the sixth node according to the address indicated by the information. After receiving the data packet, the sixth node sends the data packet to the first node. Before sending the data packet, the sixth node may replace the information contained in the data packet with the information contained in the above-mentioned "information related to the tunnel of downlink data", for example, replace the IP address in the data packet with the IP address contained in the above-mentioned "information related to the tunnel of downlink data".

[0862] Second tunnel information, which indicates address-related information used by the sixth node to receive user data from the first node. In one embodiment, the sixth node forwards the received data to the fifth node. This information includes at least one of the following:

[0863] Tunnel identification information

[0864] IP address

[0865] TEID

[0866] The use of this information is Figure 3 The method of (c) is related to the above, that is, the first node sends a data packet to the sixth node according to the address indicated by the information. After receiving the data packet, the sixth node will send the data packet to the fifth node. Before sending the data packet, the sixth node may replace the information contained in the data packet with the information contained in the above "information related to the tunnel of uplink data", for example, replace the IP address in the data packet with the IP address contained in the above "information related to the tunnel of uplink data". Therefore, if the above "second tunnel information" is included, the fifth node will send the information to the first node.

[0867] ■ Third control signaling-related information, which is used to provide information related to control signaling or control signaling transmission, and includes at least one of the following information:

[0868] ■ Information sent by the first node to the fifth node, such as an F1AP message, in one embodiment, the information includes an IP packet of the F1AP message; the information may be an IP packet sent by the first node to the sixth node.

[0869] ■Control signaling type information, which indicates the type of control signaling transmitted. The control signaling transmitted may be the "information sent from the first node to the fifth node" contained in the above-mentioned "information related to the third control signaling", or may be one or more control signalings transmitted between the first node and the fifth node. In one embodiment, the information may indicate control signaling type 1, control signaling type 2, etc., and different types may have different priorities, such as control signaling type 1 has the highest priority, control signaling type 2 has the second highest priority, etc. In another embodiment, the information may indicate user-associated control signaling (UE-associated signaling) or non-UE-associated control signaling (non-UE-associated signaling), etc. Furthermore, the information contained in the above-mentioned "information related to the third control signaling" is applicable to the control signaling type indicated by the "control signaling type information".

[0870] ■ Receive the destination address information of the downlink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information of the first node side

[0871] ■Configuration value information of the DSCP field in the data packet carrying control signaling

[0872] ■Configuration value information of the flow label field in the data packet carrying control signaling

[0873] ■ Receive the destination address information of the uplink control signaling, such as IP address, BAP address, etc.; further, the address information may be the address information of the fifth node side

[0874] ■ Route identification information, which is used to indicate the transmission path of the control signaling (in one embodiment, the control signaling is the control signaling sent by the first node), including the address information (BAP address) of the receiving node (such as the distribution unit of the sixth node) and / or the transmission path identification information (path ID). Furthermore, based on this information, the first node can add this information to the data packet carrying the control signaling.

[0875] ■ The identification information of the next hop node. The next hop node is the node that directly receives the control signaling when the first node sends the control signaling. In other words, the first node sends the control signaling to the next hop node, which then sends it directly or indirectly (through other nodes) to the destination node. Based on this information, the first node knows which node to send the control signaling to.

[0876] ■ Identification information of the backhaul link channel, which is the backhaul link channel used by the first node to send control signaling to the next hop node. Based on this information, the first node knows which backhaul link channel to use to send control signaling.

[0877] ■

[0878] Step 4-2: The fifth node sends a fifth configuration response message to the sixth node. The message is used to feedback the configuration update result. The message includes at least one of the following information:

[0879] ■ Ninth user configuration information, this information is for users who access the first node (the distribution unit part of the first node), and the information contained in this information can be found in the above " User configuration information Specifically, it shall include at least one of the following information:

[0880] ■ User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID. In one embodiment, this information may include multiple user identifications. This information may include at least one of the following:

[0881] gNB-CU UE F1AP ID

[0882] gNB-DU UE F1AP ID

[0883] C-RNTI

[0884] ◆Service area logo

[0885] ◆UE XnAP ID: In one embodiment, the ID is the ID allocated by the fifth node. The above-mentioned identifier is only an example and does not exclude the inclusion of other identifiers.

[0886] ■ Information about the user's radio bearer. For a radio bearer (e.g., a data radio bearer (DRB) or a signaling radio bearer (SRB), this information may be used to indicate whether the fifth node has accepted the request to modify or delete the radio bearer in step 4-1. This information may include at least one of the following:

[0887] User identification, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0888] ◆ User radio bearer identification information, such as UE RB ID, which can indicate a radio bearer for a specific user. In other words, the identification information not only indicates a user, but also indicates a radio bearer for the user.

[0889] ◆Identification information, such as DRB ID, SRB ID

[0890] ◆Reason information, which indicates the reason for modifying or deleting the radio bearer, such as resource limitation, etc.

[0891] ■ Fourth control signaling-related information, which is used to provide information related to control signaling or control signaling transmission, and includes at least one of the following information:

[0892] ■ The fifth node sends information to the first node, such as an F1AP message. In one embodiment, the information includes an IP packet of the F1AP message. After receiving the information, the sixth node sends the received information to the first node.

[0893] ■Control signaling type information, which indicates the type of control signaling transmitted. The control signaling transmitted may be the “information sent from the fifth node to the first node” contained in the above-mentioned “information related to the fourth control signaling”, or may be one or more control signalings transmitted between the fifth node and the first node. In one embodiment, the information may indicate control signaling type 1, control signaling type 2, etc., and different types may have different priorities, such as control signaling type 1 has the highest priority, control signaling type 2 has the second highest priority, etc. In another embodiment, the information may indicate user-associated control signaling (UE-associated signaling) or non-UE-associated control signaling (non-UE-associated signaling), etc. Furthermore, the information contained in the above-mentioned “information related to the fourth control signaling” is applicable to the control signaling type indicated by the “control signaling type information”.

[0894] ■ Receive the destination address information of the downlink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information of the first node side

[0895] ■ Receive the destination address information of the uplink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information of the fifth node side

[0896] In the above process, after step 4-2, step 4-3 may also be included, that is, the fifth node sends a sixth configuration request message to the first node, which configures the first node according to the configuration information received in step 4-1. For example, for a wireless bearer, the received "information related to the tunnel of uplink data" is sent to the first node; the information sent to the first node in step 4-3 can refer to the information received in the above step 4-1, and will not be introduced in detail here.

[0897] The above process can be performed for only one user, for multiple users, or for control signaling (i.e., the above steps 4-1 and 4-2 are used to transmit information related to control signaling, see the above third control signaling related information and fourth control signaling related information).

[0898] The third configuration request message and the third configuration response message in the above process may be user-associated messages or non-UE-associated messages. They may reuse existing Xn interface messages, such as the NG-RAN Node configuration update and NG-RAN node configuration update acknowledgment messages in TS38.423, or define new messages, such as UE Bearer Context Modification Required Message (UE bearer context modification requirement message) and UE Bearer Context Modification Confirm (UE bearer context modification confirmation) message, or other messages.

[0899] The above process is different from the process of the S-Node modification required message (secondary node modification required message) on the existing Xn interface, which is intended to modify the configuration of the secondary node. However, in the above process in the present invention, the sixth node is not the user's secondary node, and the user is connected to the fifth node. The sixth node only configures the return link channel and transmission path used for user data transmission. The sixth node does not configure the user's wireless bearer.

[0900] The beneficial effects of the above process are:

[0901] 1. The configuration information related to the data served by the interactive relay node can help the anchor node (the sixth node) configure the backhaul link channel and transmission path required to serve the relay node's data, facilitating the transmission of the relay node's data through networks controlled by other anchor nodes, thereby reducing the load on the network served by the anchor node to which the relay node is connected;

[0902] 2. The configuration information related to the data served by the interactive relay node can help the anchor node connected to the relay node configure data transmission, such as determining the information to be included in the downlink data packet (such as the configuration value of the DSCP field and the configuration value of the flow label field), configuring the information to be included in the uplink data packet (such as routing information), and configuring the transmission of uplink data packets, such as determining the next hop node and the return link channel to be used;

[0903] 3. The data of the first node can be sent to the fifth node through the centralized unit of the sixth node, and the data of the fifth node can be sent to the first node through the centralized unit of the sixth node; or the data of the first node can be sent to the fifth node through the distributed unit of the sixth node, and the data of the fifth node can be sent to the first node through the distributed unit of the sixth node. This can avoid migrating the distributed unit of the relay node, reduce the signaling overhead during the migration of the relay node, and accelerate the migration of the relay node.

[0904] The three aspects of the present invention can also be combined with each other, and several embodiments are given below to illustrate:

[0905] Example 4-1 (a process of migrating and updating a relay node by combining the first aspect with the second aspect), Figure 8 FIG. 1 is an example of a relay node migration and configuration update process according to an embodiment of the present invention. Figure 8 As shown, the process includes the following steps:

[0906] Step 4-1-1: The second node sends a handover request message to the third node, see step 1-1 of the first aspect of the present invention;

[0907] Step 4-1-2: The third node sends a handover response message to the second node, see step 1-2 of the first aspect of the present invention;

[0908] Step 4-1-3: The second node sends a migration configuration message to the first node, see step 1-3 of the first aspect of the present invention;

[0909] Step 4-1-4: The first node sends a migration configuration completion message to the third node, see step 1-4 of the first aspect of the present invention;

[0910] Step 4-1-5: The third node sends a first configuration request message to the first node, see step 2-1 of the second aspect of the present invention;

[0911] Step 4-1-6: The first node sends a first configuration response message to the third node, see step 2-2 of the second aspect of the present invention.

[0912] Example 4-2 (the first aspect and the third aspect are combined to obtain the relay node migration and configuration interaction process), Figure 9 FIG. 1 is an example of a relay node migration and configuration interaction process according to an embodiment of the present invention. Figure 9 As shown, the process includes the following steps:

[0913] Step 4-2-1: The second node sends a handover request message to the third node, see step 1-1 of the first aspect of the present invention;

[0914] Step 4-2-2: The third node sends a handover response message to the second node, see step 1-2 of the first aspect of the present invention;

[0915] Step 4-2-3: The second node sends a migration configuration message to the first node, see step 1-3 of the first aspect of the present invention;

[0916] Step 4-2-4: The first node sends a migration configuration completion message to the third node, see step 1-4 of the first aspect of the present invention;

[0917] Step 4-2-5: The second node sends a third configuration request message to the third node, see step 3-1 of the third aspect of the present invention;

[0918] Step 4-2-6: The third node sends a third configuration response message to the second node, see step 3-2 of the third aspect of the present invention.

[0919] Example 4-3 (the first aspect and the third aspect are combined to obtain the relay node migration and configuration interaction process), Figure 10 FIG. 1 is another example of the migration and configuration interaction process of a relay node according to an embodiment of the present invention. Figure 10 As shown, the process includes the following steps:

[0920] Step 4-3-1: The second node sends a handover request message to the third node, see step 1-1 of the first aspect of the present invention;

[0921] Step 4-3-2: The third node sends a handover response message to the second node, see step 1-2 of the first aspect of the present invention;

[0922] Step 4-3-3: The second node sends a migration configuration message to the first node, see step 1-3 of the first aspect of the present invention;

[0923] Step 4-3-4: The first node sends a migration configuration completion message to the third node, see step 1-4 of the first aspect of the present invention;

[0924] Step 4-3-5: The third node sends a fifth configuration request message to the second node, see step 4-1 of the third aspect of the present invention;

[0925] Step 4-3-6: The second node sends a fifth configuration response message to the third node, see step 4-2 of the third aspect of the present invention.

[0926] d. Effects of the invention

[0927] Based on the invention of the first aspect, the beneficial effects include at least:

[0928] 1. Complete the migration of relay nodes between different anchor nodes, such as the handover of the mobile terminal part of the relay node between different anchor nodes, and the migration of users served by the distributed unit part of the relay node between different anchor nodes. Unlike traditional technologies, in which each user's handover process must be executed separately, the above process can complete the handover of multiple users simultaneously;

[0929] 2. During relay node migration, the configuration information for the data to be transmitted by the relay node's distribution unit needs to be updated. Based on the above process, the signaling required to update this configuration information can be effectively reduced. For example, the mapping-related information exchanged in the above process can help the receiving node simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration for different users, or simultaneously updating the signaling transmission configuration, or simultaneously updating the data transmission and signaling transmission configuration for different users), saving signaling overhead.

[0930] 3. Maintaining the connection between the distributed unit part of the relay node and the centralized unit of the source anchor node reduces the configuration update for users accessing the relay node and saves signaling overhead.

[0931] Based on the invention of the second aspect, the beneficial effects include at least:

[0932] When the configuration information for data transmitted by the distribution unit of a relay node needs to be updated, the above process can effectively reduce the signaling required to update the configuration information. For example, the mapping-related information exchanged in the above process can help the receiving node simultaneously update multiple configurations (such as simultaneously updating the data transmission configuration for different users, or simultaneously updating the signaling transmission configuration for different users, or simultaneously updating the data transmission and signaling transmission configuration for different users), thereby saving signaling overhead.

[0933] Based on the invention of the third aspect, the beneficial effects include at least:

[0934] 1. The configuration information related to the data served by the interactive relay node can help the anchor node (the sixth node) configure the backhaul link channel and transmission path required to serve the relay node's data, facilitating the transmission of the relay node's data through networks controlled by other anchor nodes, thereby reducing the load on the network served by the anchor node to which the relay node is connected;

[0935] 2. The configuration information related to the data served by the interactive relay node can help the anchor node connected to the relay node configure data transmission, such as determining the information to be included in the downlink data packet (such as the configuration value of the DSCP field and the configuration value of the flow label field), configuring the information to be included in the uplink data packet (such as routing information), and configuring the transmission of uplink data packets, such as determining the next hop node and the return link channel to be used;

[0936] 3. The data of the first node can be sent to the fifth node through the centralized unit of the sixth node, and the data of the fifth node can be sent to the first node through the centralized unit of the sixth node; or the data of the first node can be sent to the fifth node through the distributed unit of the sixth node, and the data of the fifth node can be sent to the first node through the distributed unit of the sixth node. This can avoid migrating the distributed unit part of the relay node, reduce the signaling overhead during the migration of the relay node, and accelerate the migration of the relay node.

[0937] Figure 11 is a block diagram of an anchor node according to an embodiment of the present invention.

[0938] refer to Figure 11 , the anchor node 1100 includes a transceiver 1110, a controller 1120, and a memory 1130. Under the control of the controller 1120 (which may be implemented as a processor), the anchor node 1100 (including the transceiver 1110 and the memory 1130) is configured to execute Figures 4 to 10 The operations of the anchor node described in the process shown or above include but are not limited to the operations of the source anchor node and the target anchor node. Although the transceiver 1110, the controller 1120 and the memory 1130 are shown as separate entities, they can be implemented as a single entity, such as a single chip. The transceiver 1110, the controller 1120 and the memory 1130 can be electrically connected or coupled to each other. The transceiver 1110 can send signals to other network entities and receive signals from other network entities, such as another anchor node, a relay node and / or a UE. The controller 1120 can be configured to execute instructions stored in the memory 1130 to control the overall operation of the anchor node 1100, thereby achieving Figures 4 to 10 The operations of the anchor node in the process shown or described above.

[0939] Figure 12 is a block diagram of a relay node according to an embodiment of the present invention.

[0940] refer to Figure 12 , the relay node 1200 includes a transceiver 1210, a controller 1220 and a memory 1230. Under the control of the controller 1220 (which can be implemented as a processor), the relay node 1200 (including the transceiver 1210 and the memory 1230) is configured to execute Figures 4 to 10The operations of the relay node described in the flow shown or above. Although the transceiver 1210, the controller 1220, and the memory 1230 are shown as separate entities, they can be implemented as a single entity, such as a single chip. The transceiver 1210, the controller 1220, and the memory 1230 can be electrically connected or coupled to each other. The transceiver 1210 can send signals to and receive signals from other network entities, such as anchor nodes, another relay node, and / or UEs. The controller 1220 can be configured to execute instructions stored in the memory 1230 to control the overall operation of the relay node 1200, thereby performing Figures 4 to 10 The operations of the relay node in the process shown or described above.

[0941] Those skilled in the art will recognize that the present invention can be implemented in other specific forms without changing the technical ideas or basic features of the present invention. Therefore, it should be understood that the above embodiments are merely examples and are not limiting. The scope of the present invention is defined by the appended claims, rather than by the detailed description. Therefore, it should be understood that all modifications or variations derived from the meaning and scope of the appended claims and their equivalents are within the scope of the present invention.

[0942] In the above-described embodiments of the present invention, all operations and messages may be selectively performed or omitted. Furthermore, the operations in each embodiment need not be performed sequentially, and the order of operations may vary. Messages need not be delivered in sequence, and the order of message delivery may vary. Each operation and each message transmission may be performed independently.

[0943] While the invention has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.

Claims

1. A method performed by a first anchor node in a wireless communication system, comprising: Sending a first message to the second anchor node requesting configuration information for migrating the data flow; as well as receiving, in response to the first message, from the second anchor node a second message for providing configuration information for migrating the data flow, The second message includes configuration information related to the downlink data packet, and The configuration information related to the downlink data packet includes a Backhaul Adaptation Protocol (BAP) address of a previous hop node.

2. The method according to claim 1, in, The first message includes at least one of the following: Identification information of the mobile terminal MT part of the first node, Identification information of the data stream, Quality of Service (QoS) information for data flows, Information about network addresses, and Information about the routing identifier.

3. The method according to claim 1, in, The second message further includes at least one of the following: Identification information of the MT part of the first node, Identification information for the data stream, and Configuration information related to uplink data packets.

4. The method according to claim 1, wherein The configuration information related to the downlink data packet also includes at least one of the following: Information about the configuration value of the Differentiated Services Code Point (DSCP) field of the downstream data packet. Information about the configuration value of the flow label field of the downstream data packet, Backhaul Adaptation Protocol (BAP) routing identification information, and Identification information about the ingress backhaul Radio Link Control (RLC) channel.

5. The method according to claim 3, wherein: The configuration information related to the uplink data packet includes at least one of the following: Backhaul Adaptation Protocol (BAP) routing identification information, The next hop node BAP address, and Identification information about the egress backhaul Radio Link Control (RLC) channel.

6. The method of claim 1 , further comprising: A third message providing configuration of data flows served by the first node is sent to the distribution unit DU part of the first node.

7. The method according to claim 6, in, The third message includes at least one of the following: Next hop node BAP address, Routing identification information, Ingress BAP routing identification information, and Egress BAP route identification information.

8. A method performed by a second anchor node in a wireless communication system, comprising: receiving, from the first anchor node, a first message requesting configuration information for migrating a data flow; as well as In response to the first message, sending a second message to the first anchor node for providing configuration information for migrating the data flow, The second message includes configuration information related to the downlink data packet, and The configuration information related to the downlink data packet includes a Backhaul Adaptation Protocol (BAP) address of a previous hop node.

9. The method according to claim 8, in, The first message includes at least one of the following: Identification information of the mobile terminal MT part of the first node, Identification information of the data stream, Quality of Service (QoS) information for data flows, Information about network addresses, and Information about the routing identifier.

10. The method according to claim 8, The configuration information related to the downlink data packet also includes at least one of the following: Information about the configuration value of the Differentiated Services Code Point (DSCP) field of the downstream data packet. Information about the configuration value of the flow label field of the downstream data packet, Backhaul Adaptation Protocol (BAP) routing identification information, and Identification information about the ingress backhaul Radio Link Control (RLC) channel.

11. The method according to claim 8, in, The second message further includes at least one of the following: Identification information of the MT part of the first node, Identification information for the data stream, and Configuration information related to uplink data packets.

12. The method according to claim 11, in, The configuration information related to the uplink data packet includes at least one of the following: Backhaul Adaptation Protocol (BAP) routing identification information, The next hop node BAP address, and Identification information about the egress backhaul Radio Link Control (RLC) channel.

13. A first anchor node in a wireless communication system, comprising: transceiver; as well as at least one processor coupled to the transceiver, Wherein, the at least one processor is configured to control the transceiver to: Sending a first message to the second anchor node requesting configuration information for migrating the data flow; and receiving, in response to the first message, from the second anchor node a second message for providing configuration information for migrating the data flow, The second message includes configuration information related to the downlink data packet, and The configuration information related to the downlink data packet includes a Backhaul Adaptation Protocol (BAP) address of a previous hop node.

14. The first anchor node according to claim 13, in, The first message includes at least one of the following: identification information of the mobile terminal part of the first node, Identification information of the data stream, Quality of Service (QoS) information for data flows, Information about network addresses, and Information about the routing identifier.

15. The first anchor node according to claim 13, in, The second message further includes at least one of the following: Identification information of the MT part of the first node, Identification information for the data stream, and Configuration information related to uplink data packets.

16. The first anchor node according to claim 13, wherein: The configuration information related to the downlink data packet also includes at least one of the following: Information about the configuration value of the DSCP field of the downstream data packet, Information about the configuration value of the flow label field of the downstream data packet, Backhaul Adaptation Protocol (BAP) routing identification information, and Identification information about the ingress backhaul Radio Link Control (RLC) channel.

17. The first anchor node according to claim 15, wherein: The configuration information related to the uplink data packet includes at least one of the following: Backhaul Adaptation Protocol (BAP) routing identification information, The next hop node BAP address, and Identification information about the egress backhaul Radio Link Control (RLC) channel.

18. The first anchor node of claim 13, wherein the at least one processor is further configured to control the transceiver to: A third message providing configuration of a data flow served by the first node is sent to the DU part of the first node.

19. The first anchor node according to claim 18, in, The third message includes at least one of the following: Next hop node BAP address, Routing identification information, Ingress BAP routing identification information, and Egress BAP route identification information.

20. A second anchor node in a wireless communication system, comprising: transceiver; as well as at least one processor coupled to the transceiver, Wherein, the at least one processor is configured to control the transceiver to: receiving, from the first anchor node, a first message requesting configuration information for migrating a data flow; In response to the first message, sending a second message to the first anchor node for providing configuration information for migrating the data flow, The second message includes configuration information related to the downlink data packet, and The configuration information related to the downlink data packet includes a Backhaul Adaptation Protocol (BAP) address of a previous hop node.

21. The second anchor node according to claim 20, in, The first message includes at least one of the following: Identification information of the mobile terminal MT part of the first node, Identification information of the data stream, Quality of Service (QoS) information for data flows, Information about network addresses, and Information about the routing identifier.

22. The second anchor node according to claim 20, in, The configuration information related to the downlink data packet further includes at least one of the following: Information about the configuration value of the Differentiated Services Code Point (DSCP) field of the downstream data packet. Information about the configuration value of the flow label field of the downstream data packet, Backhaul Adaptation Protocol (BAP) routing identification information, and Identification information about the ingress backhaul Radio Link Control (RLC) channel.

23. The second anchor node according to claim 20, in, The second message further includes at least one of the following: Identification information of the MT part of the first node, Identification information for the data stream, and Configuration information related to uplink data packets.

24. The second anchor node according to claim 23, in, The configuration information related to the uplink data packet includes at least one of the following: Backhaul Adaptation Protocol (BAP) routing identification information, The next hop node BAP address, and Identification information about the egress backhaul Radio Link Control (RLC) channel.

Images