Node in a communication network and method thereof

Abstract

The invention provides a node in a communication system and a method thereof. The method comprises the following steps: receiving a first configuration message from a second node; and transmitting a first configuration completion message to the third node, in which, before receiving the first configuration message from the second node, the first request message is transmitted from the second node to the third node, and the first response message is transmitted from the third node to the second node.

Description

[0001] This application is a divisional application of the patent application with application number 202011206163.7, titled "Node in a communication network and method thereof", filed on November 02, 2020. TECHNICAL FIELD

[0002] The present application relates to the field of wireless communication technology, in particular to a mechanism for user equipment switching in a multi-hop network and a device and method for interacting user-related context between a centralized unit and a distributed unit of a base station. BACKGROUND

[0003] In the study of NR (New Radio access) network Release 16, in order to extend the coverage of the network, the IAB (Integrated Access and Backhaul) topic is proposed, and the main purpose of this topic is to build a multi-hop network architecture. Figure 1A schematic architecture of a multi-hop network is shown, in which a network architecture including one anchor node (IAB donor), two relay nodes (IAB nodes) is given. Users in the multi-hop network can access the network through the anchor node or the distributed unit of the anchor node or the relay nodes, such as users 1 / 2 / 3 access the relay network through the distributed unit of the anchor node, the distributed unit part of relay node 1, the distributed unit part of relay node 2, respectively. The anchor node can be a standalone base station or a base station composed of a central unit (IAB-donor central unit) and a distributed unit (IAB-donor distributed unit). The relay node includes a mobile terminal part and a distributed unit part, wherein the mobile terminal part is used for communication with the upper node of the relay node (such as the mobile terminal part of relay node 1 is used for communication with the anchor node or the distributed unit of the anchor node, and the mobile terminal part of relay node 2 is used for communication with the distributed unit part of relay node 1), and the distributed unit part is used for communication with the lower node of the relay node (such as the distributed unit part of relay node 1 is used for communication with user 2, and can also be used for communication with the mobile terminal part of relay node 2). The mobile terminal part of the relay node can be regarded as a user accessing the network, and thus has the function of a normal user (non-relay node) (such as the mobile terminal part can establish a signaling radio bearer (SRB) with the upper node to send radio resource control (RRC) messages, and can also establish a data radio bearer (DRB) to send data). The central unit of the anchor node includes a protocol stack of a service control plane, including a radio resource control (RRC) protocol layer and a packet data convergence protocol (PDCP) layer; and a protocol stack of a service user plane, including a service data adaptation protocol (SDAP) layer and a PDCP layer. The distributed unit of the anchor node or the distributed unit part of the relay node includes a protocol stack of a service control plane and a user plane, including a radio link control (RLC) protocol layer, a medium access control (MAC) protocol layer, and a physical layer (PHY). The interface between the central unit of the anchor node and the distributed unit of the anchor node, and the interface between the central unit of the anchor node and the distributed unit part of the relay node are F1 interfaces (see 3GPP TS 38.473).

[0004] In a relay network, the link between a relay node and an anchor node or a distributed unit of an anchor node, or between relay nodes is a backhaul link, on which one or more different backhaul link channels are established, such as Figure 1 Backhaul Link Channel 1 and Backhaul Link Channel 2 in FIG. 1, where Backhaul Link Channel 1 is between an anchor node and a relay node 1, and Backhaul Link Channel 2 is between relay node 1 and relay node 2. An example of a backhaul link channel is a Backhaul Link RLC channel. In a relay network, each backhaul link channel is used to transmit data packets belonging to the same user or different users. The data packets can be data packets of a user data radio bearer (DRB), data packets of a user signaling radio bearer (SRB), data packets of a control plane on an F1 interface, data packets of a user plane on an F1 interface, or data packets of a non-F1 interface (such as Internet Protocol Security (IPSec) data packets, Stream Control Transmission Protocol (SCTP) data packets, Operation Administration and Maintenance (OAM) data packets, etc.).

[0005] To realize the transmission of user data in a multi-hop relay network, 3GPP defines a new protocol layer, Backhaul Adaptation Protocol Layer (BAP), which is configured in a distributed unit of an anchor node and a relay node (such as a mobile terminal part of a relay node and / or a distributed unit part of a relay node), above the RLC layer, and its main functions are data packet routing and data packet mapping. Data packet routing refers to transmitting a received data packet to a correct next-hop node so that the data packet can be received by a destination receiving node. The destination receiving node can be a relay node, an anchor node, a distributed 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 a data packet of control signaling of an F1 interface that needs to be received by a distributed unit part of the relay node, or a data packet of a user accessing the relay node, etc. Data packet mapping refers to transmitting a data packet by a correct backhaul link channel.

[0006] A new address information (e.g. BAP address) is defined for a node in the relay network (e.g. a relay node, or a distributed unit of an anchor node, or a centralized unit of an anchor node, or an anchor node), which can be used to indicate a node in the relay network and to route a data packet in the relay network. If a BAP address of a node (e.g. a relay node, or a distributed unit of an anchor node, or a centralized unit of an anchor node, or an anchor node) is contained in a data packet, it indicates that the destination receiving node of the data packet is the node, or the source sending node of the data packet is the node. Meanwhile, there can be multiple transmission paths between an anchor node (or a centralized unit of an anchor node, or a distributed unit of an anchor node) and a relay node, and a path identifier (Path ID) is defined to indicate different transmission paths. Different Path IDs indicate different paths to the same node. The Path ID of a data packet can also be contained in the data packet. When a node in the relay network receives a data packet, it determines the next hop node of the data packet according to the BAP address and / or Path ID contained in the data packet, thereby completing the routing of the data packet.

[0007] The above information is presented as background information only to assist with an understanding of the present application. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present application. SUMMARY

[0008] TECHNICAL PROBLEM

[0009] The current research assumes that the anchor nodes connected by the relay node will not change, but in the actual network, the anchor nodes connected by the relay node will change due to some reasons (e.g. load balancing, relay node movement, etc.), i.e. the relay node will migrate (or switch) between different anchor nodes. In the present application, the migration and switching of the relay node are not distinguished and are used interchangeably. In the migration process, the users accessing the relay node will also be affected. The conventional technology cannot well support the migration of the relay node, and the main problem is how to update the configuration of the users served by the relay node in the migration process of the relay node, and how to reduce the signaling overhead in the process of updating the configuration.

[0010] The solution of the conventional technology is that in the migration process of the relay node, the connection between all users and the relay node is disconnected, and then each user starts the re-establishment process to re-establish the connection with the network.

[0011] SOLUTION

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

[0013] According to another aspect of the present application, there is provided a method performed by a second node in a communication system, 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 a first node, wherein the first configuration complete message is sent from the first node to the third node after the first configuration message is sent to the first node.

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

[0015] In the method of the present application, the first request message can be a handover request message for the first node, and at least can include 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 can be a handover response message for the first node, and at least can include 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 can be used to provide configuration information required for the first node to migrate and / or after migration, and at least can include one of third user configuration information, third mapping relationship information, third backhaul link channel configuration information, and third address related information.

[0016] In the method of the present application, the first user configuration information, the second user configuration information, and the third user configuration information are configuration information of users served by the first node, and at least can include one of an identity of the user and user's radio bearer related information, respectively.

[0017] In the method of the present application, the information related to the radio bearer of the user can include at least one of the following: an identifier of the user, an identifier of the radio bearer of the user, information related to a quality of service (QoS) of the radio bearer, configuration information of the radio bearer serving the user, information related to a QoS satisfied by the relay node, information related to a QoS satisfied by a non-relay node, information related to a tunnel for uplink data, information related to a tunnel for downlink data, information related to data forwarding, first tunnel information, and second tunnel information.

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

[0019] According to another aspect of the present application, 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 transmitting a first configuration response message to the fourth node.

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

[0021] In the method of the present application, the first configuration request message can be used to update configuration of the first node, and can include at least one of fifth information related to an address, fifth user configuration information, and fifth mapping relationship information; and the first configuration response message can be used to acknowledge the first configuration request message, and can include at least one of sixth user configuration information and sixth mapping relationship information.

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

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

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

[0025] According to another aspect of the present application, 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.

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

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

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

[0029] According to another aspect of the present application, 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.

[0030] In the method of the present application, the fifth configuration request message can be used to update configuration information of data served by the first node to the fifth node, and can comprise at least one of eighth user configuration information and third control signaling related information; and the fifth configuration response message can be used to feed back a result of configuration update, and can comprise at least one of ninth user configuration information and fourth control signaling related information.

[0031] According to still another aspect of the present application, there are also provided nodes for performing one of the above methods, comprising an anchor node and a relay node.

[0032] Technical Effects

[0033] One technical effect of the present application is that, by interacting user configuration information during or after migration of the relay node, and further updating user configuration information at the relay node, continuous service is provided to users, and signaling interaction is reduced.

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

[0035] The above and other aspects, features, and advantages of certain embodiments of the application will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0036] Figure 1 Schematic architecture for a multi-hop network.

[0037] Figure 2 Example of migration of a relay node according to an embodiment of the application.

[0038] Figure 3 Example of method for data transmission after migration of a relay node according to an embodiment of the application.

[0039] Figure 4 Example of migration procedure of a relay node according to an embodiment of the application.

[0040] Figure 5 Example of configuration update procedure of a relay node according to an embodiment of the application.

[0041] Figure 6 Example of configuration interaction procedure of a relay node according to an embodiment of the application.

[0042] Figure 7 Another example of configuration interaction procedure of a relay node according to an embodiment of the application.

[0043] Figure 8 Example of migration and configuration update procedure of a relay node according to an embodiment of the application.

[0044] Figure 9 Example of migration and configuration interaction procedure of a relay node according to an embodiment of the application.

[0045] Figure 10 Another example of migration and configuration interaction procedure of a relay node according to an embodiment of the application.

[0046] Figure 11 Block diagram of an anchor node according to an embodiment of the application.

[0047] Figure 12 Block diagram of a relay node according to an embodiment of the application. DETAILED DESCRIPTION

[0048] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present application as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be taken as illustrations only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the application. In addition, descriptions of well-known functions and constructions can be omitted for clarity and conciseness.

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

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

[0051] Further, the detailed description of embodiments of the present application is mainly based on a wireless communication system of a multi-hop network, particularly a relay network, but the subject matter of the present application can be applied to other communication systems having a similar technical background and channel form with slight modifications without departing from the scope of the present application, and can be determined by those skilled in the art.

[0052] The advantages and features of the present application and the means for achieving them will become apparent by referring to various embodiments described below in detail in connection with the accompanying drawings. However, the present application is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to completely disclose the present application and to inform those skilled in the art of the scope of the present application, and the present application is defined only by the scope of the appended claims. Throughout the specification, like or similar components are designated by like or similar reference numerals.

[0053] Here, it will be understood that each of the steps in the flowchart illustrations, and combinations of steps in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer- usable or computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block or blocks.

[0054] Also, each block in the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions or steps noted in the blocks can occur out of the order noted in the flowchart. For example, two blocks shown in succession can in fact be executed substantially concurrently or the steps can sometimes be executed in the reverse order, depending upon the functionality involved. In some cases, multitasking and parallel processing can be advantageous.

[0055] As used herein, a "unit" or "module" refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), that performs a predetermined function. However, a "unit" or "module" is not limited to software or hardware, and can be configured of a storage medium that stores computer-executable instructions or a processor that executes the computer-executable instructions. Therefore, a "unit" or "module" includes, for example, a software element, an object-oriented software element, a class element or a task element, a process, a function, an attribute, a procedure, a subroutine, a segment of a program code, a driver, firmware, a microcode, a circuit, data, a database, a data structure, a table, an array, and a parameter. Elements and functions provided by a "unit" or a "module" can be either integrated into a lesser number of elements "units" or "modules" or divided into a larger number of elements "units" or "modules." The "unit" or "module" can be implemented with a central processing unit (CPU) that reproduces one or more functions of the "unit" or "module" within the device or a secure multimedia card.

[0056] Aspects of the application, as generally described herein, and in the drawings, can be arranged, substituted, combined, separated, and designed in various different configurations, all of which are contemplated herein. Additionally, the features illustrated in each drawing can be used in combination with features illustrated in other drawings. Thus, the drawings are not to be considered as limiting the scope of the application as described herein. Figure 1 Generally, it is contemplated that the functions of the various embodiments can be implemented, at least in part, by software stored in and executed by one or more general purpose or special purpose programmable microprocessors, microcontrollers, digital signal processors or other components. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, "software" is intended to encompass not only the machine-readable instructions specifically listed herein, but also the machine-readable instructions that, when executed, will cause a machine to perform the functions described herein. Additionally, the features of the application are not limited to any particular programming language or type of code. For example, testability features of the application can be implemented using software written in C, Java, Python, Ruby, Perl, JavaScript, etc.

[0057] It will be understood that, although the terms "first", "second", etc. can be used herein to describe various elements, components, and / or parts, these elements, components, and / or parts should not be limited by these terms. These terms are only used to distinguish one element, component, and / or part from another element, component, and / or part. Thus, a first element, component, and / or part discussed below could be termed a second element, component, and / or part without departing from the teachings of the present application.

[0058] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. It will be understood that the use of the terms "including," "comprising," or "having" in the specification and claims herein are not intended to exclude other components, steps, features, integers, or groups thereof, but are intended to recite only that the claimed steps, features, integers, or groups thereof are present. It will be further understood that the use of the terms "first," "second," "third," etc., herein do not connote ranking of importance, but are used only to distinguish one element from another.

[0059] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0060] 1. Constituent of the Invention

[0061] The present application generally contains three aspects: a migration procedure of a relay node; a configuration update procedure of a relay node; and a configuration interaction procedure of a relay node. The present application is not limited to the above three aspects, and includes any step in the example methods of the three aspects and any combination thereof.

[0062] 2. Embodiment of the Invention

[0063] The message names in the present application are only examples, and other message names can also be used.

[0064] The "first", "second", and the like included in the message or information name used in the present application are used to describe different messages or information, and do not indicate the order in which the messages or information are sent.

[0065] The detailed description of the steps irrelevant to the present application is omitted in the present application.

[0066] The migration of the relay node considered in the present application can also be regarded as the handover of the relay node.

[0067] Figure 2 An example of the migration of the relay node according to the embodiment of the present application. As shown in Figure 2 , before the migration of the relay node 3, the relay node 3 accesses the network (for example, is connected to the source anchor node) through the relay node 1; and after the migration, the relay node 3 accesses the network (for example, is connected to the target anchor node) through the relay node 2. In Figure 2 , the relay node 1 and the relay node 2 are connected to different anchor nodes, respectively. More specifically, the relay node 1 is connected to the source anchor node, and the relay node 2 is connected to the target anchor node. It should be noted that, in order to simplify the description, in Figure 2 , before the migration, there is only one relay node 1 between the relay node 3 and the source anchor node, but in an actual network, the relay node 3 can be directly connected to the source anchor node, or can be connected to the source anchor node through one or more relay nodes, and similarly, after the migration, the relay node 3 can be directly connected to the target anchor node, or can be connected to the target anchor node through one or more relay nodes.

[0068] For the convenience of description, the following description of the present application takes the network shown in Figure 2 as an example, but the application range of the mechanism in the present application is not limited to the network shown in Figure 2 .

[0069] In the migration process of the relay node, different migration mechanisms result in different methods of transmitting data by the relay node after the migration. Figure 3 An example of the method of transmitting data after the migration of the relay node according to the embodiment of the present application. The present application considers the following three methods to transmit the data of the relay node:

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

[0071] Upstream: distributed unit part of relay node 3 → relay node 2 → distributed unit of target anchor node → centralized unit of target anchor node

[0072] Downstream: centralized unit of target anchor node → distributed unit of target anchor node → relay node 2 → distributed unit part of relay node 3

[0073] In this method, the users served by the relay node also need to be migrated to the target anchor node, so that the interaction of the configuration related to each user needs to be performed between the source anchor node and the target anchor node during the migration. After the migration is completed, the relay node is controlled by the target anchor node, and the backhaul link channel (such as the F1 interface) serving the relay node is also controlled by the target anchor node. Figure 3 In (a), the backhaul link channel between the relay node 3 and the relay node 2, the backhaul link channel between the relay node 2 and the distributed unit of the target anchor node, and the transmission path of the relay node and the target anchor node are also controlled by the target anchor node. The beneficial effect of this method is that the data transmission of the relay node after migration is completely controlled by the target anchor node. However, this method needs to complete the migration of all users accessing the relay node during the migration, which will introduce too much signaling interaction and increase the time delay of user migration.

[0074] (2) Method two: after migration, the distributed unit part of the relay node still maintains the connection with the centralized unit of the source anchor node, as shown in (b), the data (such as the data of the users served by the distributed unit part of the relay node 3, the data generated by the distributed unit part of the relay node 3 (such as F1AP signaling)) of the distributed unit part of the relay node 3 has a transmission path as follows: Figure 3

[0075] Upstream: distributed unit part of relay node 3 → relay node 2 → distributed unit of target anchor node → centralized unit of source anchor node

[0076] Downstream: centralized unit of source anchor node → distributed unit of target anchor node → relay node 2 → distributed unit part of relay node 3

[0077] ​In this method, only the mobile terminal part of the relay node is switched, and the distributed unit part of the relay node still maintains the connection with the centralized unit of the source anchor node, so that the user accessing the relay node still maintains the connection with the source anchor node. The beneficial effect of this is that the interaction of the configuration information related to the user during the migration is reduced, and the configuration update for each user is also reduced, thereby reducing the signaling interaction. On the other hand, the data of the distributed unit part of the relay node is carried by the backhaul link channel between the relay node 3 and the relay node 2 and the backhaul link channel between the relay node 2 and the distributed unit of the target anchor node, and the configuration of these channels is controlled by the target anchor node, and the transmission path of the data of the distributed unit part of the relay node is also controlled by the target anchor node, so the method needs the source anchor node to provide the configuration information related to the transmission of the data of the distributed unit part of the relay node to the target anchor node, thereby helping the target anchor node to configure the backhaul link channel and the transmission path; and the target anchor node needs to provide the configuration information related to the data transmission to the source anchor node, thereby helping the source anchor node to perform data transmission and configuration according to the configuration of the target anchor node. In this way, after the relay node completes the migration, the source anchor node and the target anchor node need to maintain the signaling interaction, and then perform the configuration related to the data transmission of the distributed unit part of the relay node.

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

[0079] Uplink: Distributed unit part 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

[0080] Downlink: Centralized unit of source anchor node → centralized unit of target anchor node → distributed unit of target anchor node → relay node 2 → distributed unit part of relay node 3

[0081] This method is similar to method two, and the difference is that the data transmission between the distributed unit part of the relay node and the centralized unit of the source anchor node needs to pass through the centralized unit of the target anchor node. The beneficial effect of this method is that the interaction of the configuration information related to the user during the migration is reduced, and the configuration update for each user is also reduced, thereby reducing the signaling interaction. On the other hand, similar to method two, after the relay node completes the migration, the source anchor node and the target anchor node need to maintain the signaling interaction, and then perform the configuration related to the data transmission of the distributed unit of the relay node.

[0082] It is also necessary to point out that, although the embodiments described in the present text are described in the context of the 3GPP LTE system, the present application is not limited to this system, but can be applied to other systems as well. Figure 3 It is also necessary to point out that, although the embodiments described in the present text are described in the context of the 3GPP LTE system, the present application is not limited to this system, but can be applied to other systems as well. Figure 3 It is also necessary to point out that, although the embodiments described in the present text are described in the context of the 3GPP LTE system, the present application is not limited to this system, but can be applied to other systems as well. Figure 4 to Figure 10 It is also necessary to point out that, although the embodiments described in the present text are described in the context of the 3GPP LTE system, the present application is not limited to this system, but can be applied to other systems as well.

[0083] The nodes involved in the present application are as follows:

[0084] First node: relay node, or the distributed unit part of the relay node

[0085] Second node: source node, which can be an anchor node, or the centralized unit of the anchor node, or the control plane part of the centralized unit of the anchor node, or the user plane part of the centralized unit of the anchor node

[0086] Third node: target node, which can be an anchor node, or the centralized unit of the anchor node, or the control plane part of the centralized unit of the anchor node, or the user plane part of the centralized unit of the anchor node

[0087] Fourth node: anchor node, or the centralized unit of the anchor node, or the control plane part of the centralized unit of the anchor node, or the user plane part of the centralized unit of the anchor node; in one embodiment, the fourth node can be the third node described above, or the second node described above, or other nodes

[0088] Fifth node: anchor node, or the centralized unit of the anchor node, or the control plane part of the centralized unit of the anchor node, or the user plane part of the centralized unit of the anchor node; in one embodiment, the fifth node can be the second node described above, or other nodes

[0089] Sixth node: anchor node, or the centralized unit of the anchor node, or the control plane part of the centralized unit of the anchor node, or the user plane part of the centralized unit of the anchor node; in one embodiment, the sixth node can be the third node described above, or other nodes

[0090] The second node and the third node described above can be the same node, or different nodes. The second node and the third node described above can be the same node, or different nodes.

[0091] The key information involved in the present application is as follows:

[0092] Configuration information of a user The user is a user accessing the relay node, and the information at least includes one of the following information:

[0093] The user's identity, such as gNB-CU / DU UE F1AP ID (gNB-Central Unit / Distributed Unit User Equipment F1 Application Protocol Identifier), cell radio network temporary identifier (C-RNTI: Cell-Radio Network Temporary Identifier), UE XnAP ID (User Equipment Xn Application Protocol Identifier)

[0094] The user's radio bearer related information, for a radio bearer (such as data radio bearer DRB, signaling radio bearer SRB), the information at least includes one of the following information:

[0095] The user's identity, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0096] The user's radio bearer identification information, such as UE RB ID, which 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

[0097] The identification information, such as DRB ID, SRB ID

[0098] Quality of Service (QoS) related information of the radio bearer, which contains 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. The specific information can be referred to 3GPP TS 38.473. In one embodiment, the information is the actual QoS information of the radio bearer; in another embodiment, the information is the QoS information that needs to be met by the receiving node, which is different from the above-mentioned "actual QoS information of the radio bearer"

[0099] Configuration information of the service user radio bearer, such as SDAP layer configuration, PDCP layer configuration, RLC layer configuration, configuration information of the logical channel of the radio bearer (such as identification information, priority information of the logical channel), etc. which can be referred to CellGroupConfiguration

[0100] QoS related information of the relay node, which is used to indicate the QoS that the relay node can meet when serving the radio bearer, which is different from the above-mentioned "QoS related information of the radio bearer". The beneficial effect of the information is that the node receiving the information can know the QoS that the relay node can meet when serving the user radio bearer, and determine how to configure other nodes to serve the user radio bearer, so that the relay node and other nodes jointly serve the user radio bearer and meet the QoS requirement of the radio bearer. Another beneficial effect is that the node receiving the information can try to configure the relay node to serve the user radio bearer according to the QoS indicated by the information, so that it is not necessary to modify the configuration information of the relay node when serving the user radio bearer

[0101] QoS information satisfied by the non-relay node, which is used to indicate the QoS information satisfied by other nodes in the network when serving the radio bearer except for the relay node, which is different from the above-mentioned "QoS information of the radio bearer". The beneficial effect of this information is that the node receiving this information can know the QoS required to be satisfied by other nodes except for the relay node when serving the user radio bearer, and determine how to configure other nodes to serve the user's radio bearer, so that the relay node and other nodes jointly serve the user's radio bearer and meet the QoS requirements of the radio bearer. Another beneficial effect is that the node receiving this information can try to configure other nodes to serve the user's radio bearer according to the QoS indicated by this information, so that it is not necessary to modify the configuration information of the relay node when serving the user's radio bearer

[0102] Tunnel-related information of uplink data, which is data sent by the relay node to the anchor node, the tunnel can be one or multiple, and the information indicates the information of the anchor node or the centralized unit of the anchor node or the user plane side of the centralized unit of the anchor node. For one tunnel, the information includes at least one of the following information:

[0103] Tunnel identification information, which can be used to indicate a tunnel, and the identification information is different, indicating that the tunnel indicated by the identification information is different

[0104] Internet Protocol (IP) address

[0105] Tunnel Endpoint Identifier (TEID)

[0106] Routing identification information, which is used to indicate the transmission path of the above-mentioned uplink data (further, the uplink data is transmitted through the above-mentioned tunnel), which includes address information (BAP address) of the receiving node and / or transmission path identification information (path ID), and further, according to the information, the relay node can add the information to the uplink data packet transmitted through the above-mentioned tunnel

[0107] Identity information of the next hop node, which is the node directly receiving the uplink data sent by the relay node (further, the uplink data is sent through the tunnel mentioned above), in other words, the relay node sends the uplink data to the next hop node, and then the next hop node directly or indirectly (through other nodes) sends the uplink data to the destination node of the uplink data. According to the information, the relay node knows to which node the uplink data is sent

[0108] Identity information of the backhaul link channel, which is the backhaul link channel used by the relay node to send the uplink data (further, the uplink data is sent through the tunnel mentioned above) to the next hop node mentioned above. According to the information, the relay node knows which backhaul link channel to use to send the uplink data

[0109] One beneficial effect of including the information is that the receiving node can update the configuration of the uplink tunnel of the user data according to the information, and know the configuration of the uplink data sending, such as the transmission path of the uplink data packet, the information to be added in the uplink data packet, the next hop node receiving the uplink data packet, and the backhaul link channel used to transmit the uplink data packet; another beneficial effect of including the information is that the receiving node can know 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 the information is that the receiving node can configure the uplink tunnel of the wireless bearer served by the relay node according to the received information.

[0110] Tunnel-related information of the downlink data, which is the data sent by the anchor node to the relay node, the tunnel can be one or multiple, and the information indicates the information of the relay node or the distributed unit part of the relay node. For one tunnel, the information at least includes one of the following information:

[0111] Tunnel identity information, which can be used to indicate a tunnel, and different identity information indicates different tunnels

[0112] IP address

[0113] TEID

[0114] Configuration value information of the Differentiated Services Code Point (DSCP) field in the downlink data packet (further, the downlink data packet is sent through the tunnel mentioned above)

[0115] Configuration value information of flow label field in downlink data packet (further, the downlink data packet is sent through the tunnel mentioned above)

[0116] One benefit of including the information is that the receiving node can update the configuration of the downlink tunnel of the user data according to the information, and learn the configuration of the downlink data sending, such as the information (such as the configuration value of DSCP field, the configuration value of flow label field) contained in the downlink data packet; another benefit of including the information is that the receiving node can learn how to send the downlink data to the relay node, such as the address of receiving the downlink data, the information (such as the configuration value of DSCP field, the configuration value of flow label field) required to be contained in the downlink data packet; another benefit of including the information is that the receiving node can configure the downlink tunnel of the wireless bearer served by the relay node according to the received information.

[0117] Data forwarding related information, the data sending refers to that the node 1 (such as the source anchor node, or the centralized unit of the source anchor node, or the user plane part of the centralized unit of the source anchor node) sends the data of the user's wireless bearer to the node 2 (such as the target anchor node, or the centralized unit of the target anchor node, or the user plane part of the centralized unit of the target anchor node), the data forwarding related information can help determine whether the data needs to be sent from the node 1 to the node 2, or help determine which address of the node 2 to send the data to, the sent data can be uplink data or downlink data, and for the uplink data or the downlink data, the information at least includes one of the following information:

[0118] Suggestion of whether the data forwarding is needed

[0119] IP address, which is the address on the side of the node 2

[0120] TEID, which is the TEID on the side of the node 2

[0121] First tunnel information, which indicates the address related information used by the anchor node when receiving the user data from other anchor nodes, in one embodiment, the anchor node also forwards the data to the relay node after receiving the data, and the information at least includes one of the following information:

[0122] Tunnel identification information

[0123] IP address

[0124] TEID

[0125] Second tunnel information, which indicates the address-related information used by the anchor node when receiving user data from the relay node, in one embodiment, the anchor node also forwards the data to other anchor nodes after receiving the data, and the information at least includes one of the following information:

[0126] Tunnel identification information

[0127] IP address

[0128] TEID

[0129] Address-related information required for a relay node The information is the address-related information required by the relay node (or the distributed unit part of the relay node) when communicating with the anchor node (or the centralized unit of the anchor node, or the control plane part of the centralized unit of the anchor node, or the user plane part of the centralized unit of the anchor node), and the information at least includes one of the following information:

[0130] Address-related information on the relay node side, which indicates the address on the relay node side or the distributed unit part of the relay node, and the information at least includes one of the following information:

[0131] Identification information of the address on the relay node side, which is used to indicate the address on the relay node side, and different identification information indicates different addresses on the relay node side

[0132] BAP address information

[0133] IP address information

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

[0135] Port information

[0136] Number information of required addresses, which is used to inform the receiving node of the number of addresses required by the relay node, and after receiving the information, the receiving node provides addresses for the relay node according to the information

[0137] indication information of the use of the address, which indicates the use of the above-mentioned address, and the possible indicated uses are: for sending user-related control signaling (such as UE-associated F1AP (UE-associated F1 Application Protocol)), for sending non-user-related control signaling (such as non-UE-associated F1AP), for sending user-related control information and non-user-related control information, for sending user data, for sending data of control signaling type 1, for sending data of control signaling type 2, for sending data of control signaling type 3, etc.

[0138] identification information of one or more served users, the above-mentioned address at the relay node side can serve one or more users

[0139] identification information of one or more served user radio bearers, such as UE RB ID, which can indicate one radio bearer of a specific user, in other words, the identification information not only indicates one user, but also indicates one radio bearer of the user

[0140] identification information of one or more served radio bearers, such as RB ID

[0141] address-related information of the anchor node side, which indicates the address at the anchor node side, or at the centralized unit side of the anchor node, or at the control plane part of the centralized unit of the anchor node, or at the user plane part of the centralized unit of the anchor node, and the information at least includes one of the following information:

[0142] identification information of the address at the anchor node side, which is used to indicate the address at the anchor node side, and different identification information indicates different addresses at the anchor node side

[0143] BAP address information

[0144] IP address information

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

[0146] port information

[0147] indication information of the use of the address, which indicates the use of the above-mentioned address, and the possible indicated uses are: 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 user-related control information and non-user-related control information, for sending user data, for sending data of control signaling type 1, for sending data of control signaling type 2, for sending data of control signaling type 3, etc.

[0148] identification information of one or more users served by the address on the side of the relay node, which indicates that the above-mentioned address on the side of the relay node serves one or more users

[0149] identification information of one or more radio bearers of the served users, such as UE RB ID, which indicates one radio bearer of one specific user, in other words, the identification information not only indicates one user, but also indicates one radio bearer of the user

[0150] identification information of one or more radio bearers served, such as RB ID

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

[0152] mapping information of the address, which includes at least one of the following information for the mapping of the address:

[0153] identification information of the address on the side of the relay node, which is used to indicate the address on the side of the relay node, and the identification information is different, which indicates that the indicated address on the side of the relay node is different

[0154] information related to the new address on the side of the relay node, which can refer to the above-mentioned “information related to the address on the side of the relay node” Address-related information required for a relay node Address-related information required for a relay node ” in “information related to the address on the side of the relay node”

[0155] information related to the old address on the side of the relay node, which can refer to the above-mentioned “information related to the address on the side of the relay node” Address-related information required for a relay node Address-related information required for a relay node ” in “information related to the address on the side of the relay node”

[0156] The identification information of the address of the anchor node side, which is used to indicate the address of the anchor node side. If the identification information is different, it indicates that the address of the anchor node side indicated thereby is different

[0157] The new anchor node side address related information, the content contained in the information can be referred to the "anchor node side address related information" in the above Configuration information of a user Configuration information of a user "anchor node side address related information"

[0158] The old anchor node side address related information, the content contained in the information can be referred to the "anchor node side address related information" in the above Configuration information of a user Configuration information of a user "anchor node side address related information"

[0159] The tunnel mapping information, for the mapping of a tunnel, the information at least includes one of the following information:

[0160] The identification information of the tunnel of the uplink data, which can be used to indicate which uplink tunnel, if the identification information is different, it indicates that the uplink tunnel indicated thereby is different. In an embodiment, the identification information can remain unchanged when the uplink data tunnel related information is updated. The information can be sent by the anchor node to the relay node when configuring the uplink tunnel of the user, such as the information contained in the UE Context Setup / Modification Request message for each uplink data tunnel

[0161] The new uplink data tunnel related information, the content contained in the information can be referred to the "uplink data tunnel related information" in the above Figure 3 Figure 3 "uplink data tunnel related information"

[0162] The old uplink data tunnel related information, the content contained in the information can be referred to the "uplink data tunnel related information" in the above Mapping-related information Mapping-related information "uplink data tunnel related information"

[0163] identifier information of the downlink data tunnel, which can be used to indicate which downlink tunnel, the identifier information is different, indicating that the downlink tunnel it indicates is different; in an embodiment, the identifier information can remain unchanged when the tunnel-related information of the downlink data is updated. The information can be sent by the relay node to the anchor node when configuring the downlink tunnel of the user, such as the information contained in the UE Context Setup / Modification Response message for each downlink data tunnel

[0164] new tunnel-related information of the downlink data, the content contained in the information can be referred to as "tunnel-related information of the downlink data" in the above Mapping-related information Mapping-related information old tunnel-related information of the downlink data, the content contained in the information can be referred to as "tunnel-related information of the downlink data" in the above

[0165] Mapping-related information Mapping-related information

[0166] In a specific implementation, for a tunnel, the above tunnel mapping-related information can be transmitted in the form of signaling as follows:

[0167] a. identifier information of the uplink data tunnel

[0168] b. old tunnel-related information of the uplink data, such as IP address, and / or TEID

[0169] c. new tunnel-related information of the uplink data, such as IP address, and / or TEID

[0170] d. routing identifier information, in an embodiment, the routing identifier information is the new routing identifier information used when sending the uplink data

[0171] e. identifier information of the next hop node, in an embodiment, the information indicates the identifier information of the new next hop node used when receiving the uplink data

[0172] f. identifier information of the backhaul link channel, in an embodiment, the information indicates the identifier information of the new backhaul link channel used when sending the uplink data

[0173] g. identifier information of the downlink data tunnel

[0174] h. old tunnel-related information of the downlink data, such as IP address, and / or TEID

[0175] i. new tunnel-related information of the downlink data, such as IP address, and / or TEID​​

[0176] In another embodiment, the tunnel mapping related information for a user or a user bearer can be transmitted in a signaling message, which contains at least one of the following information:

[0177] a. user's identification information

[0178] b. user bearer's identification information, such as DRB ID, SRB ID, etc.

[0179] c. one or more tunnel related information, for a tunnel, the information contains at least one of the following information:

[0180] a) tunnel's identification information for uplink data, which can be used to indicate which uplink tunnel is indicated, the tunnel's identification information is different, indicating that the uplink tunnel it indicates is different; in one embodiment, the tunnel's identification information for uplink data can remain unchanged when the tunnel related information for uplink data is updated

[0181] b) tunnel related information for uplink data, such as IP address, and / or TEID

[0182] c) tunnel related information for uplink data, such as IP address, and / or TEID

[0183] d) routing identification information, in one embodiment, the routing identification information is the new routing identification information used when sending uplink data

[0184] e) next hop node's identification information, in one embodiment, the information indicates the new next hop node's identification information used when receiving uplink data

[0185] f) backhaul link channel's identification information, in one embodiment, the information indicates the new backhaul link channel's identification information used when sending uplink data

[0186] g) tunnel's identification information for downlink data, which can be used to indicate which downlink tunnel is indicated, the tunnel's identification information is different, indicating that the downlink tunnel it indicates is different; in one embodiment, the tunnel's identification information for downlink data can remain unchanged when the tunnel related information for downlink data is updated

[0187] h) tunnel related information for downlink data, such as IP address, and / or TEID

[0188] i) tunnel related information for downlink data, such as IP address, and / or TEID

[0189] Mapping information of transport network layer association, for one transport network layer association, the information includes at least one of the following information:

[0190] Information of new anchor node side transport network layer association, the information includes at least one of the following information:

[0191] Identification information of anchor node side transport network layer association, the identification information is used to indicate one anchor node side transport network layer association, and different identification information represents the identification of different anchor node side transport network layer associations

[0192] IP address information

[0193] Port information

[0194] Indication information of the use of new anchor node side transport network layer association, the possible uses include: used for sending user-related control signaling (such as UE-associated F1AP), used for sending non-user-related control signaling (such as non-UE-associated F1AP), used for sending user-related control information and non-user-related control information, used for sending user data, used for sending control signaling type 1 data, used for sending control signaling type 2 data, used for sending control signaling type 3 data, etc.

[0195] Information of old anchor node side transport network layer association, the information includes at least one of the following information:

[0196] Identification information of anchor node side transport network layer association, the identification information is used to indicate one anchor node side transport network layer association, and different identification information represents the identification of different anchor node side transport network layer associations

[0197] IP address information

[0198] Port information

[0199] an indication of the use of the old anchor node side transport network layer association, which can indicate the use for sending UE-associated control signaling (e.g. UE-associated F1AP), for sending non-UE-associated control signaling (e.g. non-UE-associated F1AP), for sending UE-associated control information and non-UE-associated control information, for sending UE data, for sending control signaling type 1 data, for sending control signaling type 2 data, for sending control signaling type 3 data, etc.

[0200] information of the new relay node side transport network layer association, which contains at least one of the following information:

[0201] identification information of the relay node side transport network layer association, which is used to indicate one relay node side transport network layer association, and different identification information represents the identification of different relay node side transport network layer associations

[0202] IP address information

[0203] port information

[0204] an indication of the use of the new relay node side transport network layer association, which can indicate the use for sending UE-associated control signaling (e.g. UE-associated F1AP), for sending non-UE-associated control signaling (e.g. non-UE-associated F1AP), for sending UE-associated control information and non-UE-associated control information, for sending UE data, for sending control signaling type 1 data, for sending control signaling type 2 data, for sending control signaling type 3 data, etc.

[0205] information of the old relay node side transport network layer association, which contains at least one of the following information:

[0206] identification information of the relay node side transport network layer association, which is used to indicate one relay node side transport network layer association, and different identification information represents the identification of different relay node side transport network layer associations

[0207] IP address information

[0208] port information

[0209] Indication information of the usage of the old transmission network layer association at the relay node side, which can indicate the following usages: for transmitting UE-associated control signaling (e.g., UE-associated F1AP), for transmitting non-UE-associated control signaling (e.g., non-UE-associated F1AP), for transmitting UE-associated control information and non-UE-associated control information, for transmitting UE data, for transmitting control signaling type 1 data, for transmitting control signaling type 2 data, for transmitting control signaling type 3 data, etc.

[0210] Mapping information of non-user plane data transmission, for a type of non-user plane data, the information at least includes one of the following information:

[0211] Indication information of the type of non-user plane data, which can indicate the following types: for transmitting UE-associated control signaling (e.g., UE-associated F1AP), for transmitting non-UE-associated control signaling (e.g., non-UE-associated F1AP), for transmitting data of non-F1 interface

[0212] New routing identification information

[0213] Old routing identification information

[0214] Identification information of the new next hop node

[0215] Identification information of the old next hop node

[0216] Identification information of the new backhaul link channel

[0217] Identification information of the old backhaul link channel

[0218] Mapping information of routing identification, for a routing identification mapping, the information at least includes one of the following information:

[0219] New routing identification information

[0220] Old routing identification information

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

[0222] The mapping information of the next hop node, for the mapping of a next hop node, the information at least includes one of the following information:

[0223] The identification information of the new next hop node

[0224] The identification information of the old next hop node

[0225] The next hop node is the node that directly receives the data sent by the relay node. In other words, the relay node sends the data to the next hop node, and then the next hop node directly or indirectly (through other nodes) sends the data to the destination node. According to the information, the relay node knows which node to send the data to

[0226] The mapping information of the backhaul link channel, for the mapping of a backhaul link channel, the information at least includes one of the following information:

[0227] The identification information of the new backhaul link channel

[0228] The identification information of the old backhaul link channel

[0229] The backhaul link channel is used to transmit user data. Applicable information, which indicates the relevant information of the data applicable to the one or more mapping information, at least includes one of the following information:

[0230] The identification information of the user, the user applicable to the one or more mapping information may have one or more, and the information may include the identification information of one or more users

[0231] Information related to the user radio bearer, the user radio bearer applicable to the one or more mapping information may have one or more, and for a radio bearer, the information at least includes one of the following information:

[0232] The identification information of the user

[0233] The identification information of the radio bearer

[0234] Identity information of a user radio bearer, such as UE RB ID, which can indicate a radio bearer of a specific user, in other words, the identity information not only indicates a user, but also indicates a radio bearer of the user

[0235] Tunnel-related information of a user radio bearer, which at least includes one of the following information:

[0236] Tunnel-related information of uplink data, such as IP address, and / or TEID

[0237] Tunnel-related information of downlink data, such as IP address, and / or TEID

[0238] Control signaling-related information, there can be multiple types of control signaling applicable to the one or more mapping information, for a type, the information at least includes one of the following information:

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

[0240] Identity information of a user to which the control signaling belongs

[0241] Exception information, which indicates information related to data not applicable to the one or more mapping information, which at least includes one of the following information:

[0242] Identity information of a user, there can be one or more users not applicable to the one or more mapping information, and the information can include the identity information of one or more users

[0243] Information related to a user radio bearer, there can be one or more user radio bearers not applicable to the one or more mapping information, and for a radio bearer, the information at least includes one of the following information:

[0244] Identity information of a user

[0245] Identity information of a radio bearer

[0246] Identity information of the user radio bearer, such as UE RB ID, which can indicate a specific user radio bearer, in other words, the identity information not only indicates a user, but also indicates a radio bearer of the user

[0247] Tunnel-related information of the user radio bearer, which at least includes one of the following information:

[0248] Tunnel-related information of the uplink data, such as IP address, and / or TEID

[0249] Tunnel-related information of the downlink data, such as IP address, and / or TEID

[0250] Control signaling-related information, which can have multiple types for the control signaling not applicable to one or more of the above mapping information, and for one type, the information at least includes one of the following information:

[0251] Type information of the control signaling, such as user-related control signaling (such as UE-associated F1AP), non-user-related control signaling (such as non-UE-associated F1AP)

[0252] Identity information of the user to which the control signaling belongs

[0253] Among the above mapping information, the new information can be information used after the configuration update of the relay node, and the old information can be information used before the configuration update of the relay node. The above configuration update of the relay node can 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 migrates from anchor node 1 (which can correspond to the source anchor node in Mapping-related information ) to anchor node 2 (which can correspond to the target anchor node in Mapping-related informationIn another example, the relay node migrates from anchor node 1 to anchor node 2. In this example, the mobile terminal portion of the relay node switches from anchor node 1 to anchor node 2, and the centralized unit (or the control plane portion of the centralized unit, or the user plane portion of the centralized unit) to which the distributed unit portion of the relay node is connected changes from the centralized unit (or the control plane portion of the centralized unit, or the user plane portion of the centralized unit) of anchor node 1 to the centralized unit (or the control plane portion of the centralized unit, or the user plane portion of the centralized unit) of anchor node 2. In another example, the relay node migrates from anchor node 1 to anchor node 2. In this example, the mobile terminal portion of the relay node switches from anchor node 1 to anchor node 2, while the centralized unit (or the control plane portion of the centralized unit, or the user plane portion of the centralized unit) to which the distributed unit portion of the relay node is connected remains the centralized unit (or the control plane portion of the centralized unit, or the user plane portion of the centralized unit) of anchor node 1. The above examples of relay node configuration updates are only possible scenarios, and it is not ruled out that relay node configuration updates may occur in other scenarios according to the above mapping information.

[0254] 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, which 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:

[0255] In one example, the above “ Mapping-related information " provides "information about the address of the new relay node side" (such as the new IP address) and / or "information about 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 about the address of the old relay node side" to the address indicated by the "information about the address of the new relay node side".

[0256] In another example, the above “ Mapping-related information"new anchor node side address related information" (e.g., a new IP address) and / or "old anchor node side address related information" (e.g., an old IP address) is provided in the "anchor node side address related information", and the relay node receiving the information changes data transmitted to the address indicated by the "old anchor node side address related information" to data transmitted to the address indicated by the "new anchor node side address related information", or the relay node receiving the information considers data from the address indicated by the "old anchor node side address related information" as data from the address indicated by the "new anchor node side address related information"

[0257] In another example, the above-described "new uplink data tunnel related information" and / or "old uplink data tunnel related information" is provided in the "uplink data tunnel related information", and the relay node receiving the information changes data transmitted to the tunnel indicated by the "old uplink data tunnel related information" to data transmitted to the tunnel indicated by the "new uplink data tunnel related information" Mapping-related information

[0258] In another example, the above-described "new downlink data tunnel related information" and / or "old downlink data tunnel related information" is provided in the "downlink data tunnel related information", and the relay node receiving the information changes data received from the tunnel indicated by the "old downlink data tunnel related information" to data received from the tunnel indicated by the "new downlink data tunnel related information" Mapping-related information

[0259] In another example, the above-described "new routing identification information" and / or "old routing identification information" is provided in the "routing identification information", and the relay node receiving the information changes data transmitted to the transmission path indicated by the "old routing identification information" to data transmitted to the transmission path indicated by the "new routing identification information"; further, the information added to the data packet by the "old routing identification information" is changed to the information added to the data packet by the "new routing identification information" Mapping-related information

[0260] In another example, the above-described "new next hop node identification information" and / or "old next hop node identification information" is provided in the "next hop node identification information", and the relay node receiving the information changes data transmitted to the node indicated by the "old next hop node identification information" to data transmitted to the node indicated by the "new next hop node identification information" Mapping-related information

[0261] In another example, the above-described "new next hop node identification information" and / or "old next hop node identification information" is provided in the "next hop node identification information", and the relay node receiving the information changes data transmitted to the node indicated by the "old next hop node identification information" to data transmitted to the node indicated by the "new next hop node identification information" Configuration information of a backhaul link channel of a relay node ​​​​" 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".

[0262] Send the above " Configuration information of a user The beneficial effect of " is that the receiving node of the information can Configuration information of aggregated data Configuration information of a user "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 " Configuration information of a backhaul link channel of a relay node " 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 " Figure 4 " 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 " Figure 4 " 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 " Configuration information of a user 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.

[0263] Configuration information of a backhaul link channel of a relay node 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:

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

[0265] For QoS parameter information of the backhaul link channel, see TS38.473

[0266] Configuration information of the service backhaul link channel, such as configuration of the RLC layer, configuration information (such as identification information, priority information of the logical channel of the backhaul link) of the logical channel of the backhaul link channel, etc. can refer to CellGroupConfiguration

[0267] Information related to data carried by the backhaul link channel, the data can be uplink data (data generated by the relay node and sent to the anchor node, such as data of the user plane of the F1 interface generated by the distributed unit part 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), or downlink data (data sent by the anchor node to the relay node, which can be data sent to the distributed unit part of the relay node, or data sent to other nodes but needs to be forwarded by the relay node), or both uplink data and downlink data, the information at least includes one of the following information:

[0268] Information related to the wireless bearer of the user, the data of the wireless bearer of the user is sent through the backhaul link channel. The content contained in the information is described in the above "Information related to the wireless bearer of the user" Address-related information required for a relay node

[0269] Indication information of the type of data, the indicated type can include: non-UE associated F1AP signaling, UE-associated F1AP signaling, different priority control signaling types (such as control signaling type 1, control signaling type 2, control signaling type 3, … further, control signaling type 1 has the highest priority, control signaling type 2 has the second highest priority), non-F1 interface data (non-F1 traffic, such as data of the IPSec protocol, data of the SCTP protocol, data from OAM)

[0270] Routing ID information of data transmission, which is used to indicate the transmission path of the data, including address information (BAP address) of the receiving node and / or transmission path identification information (path ID), further, according to the information, the relay node can add the information to the transmitted data packet

[0271] ​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 the 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.

[0272] Configuration information of a user The 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:

[0273] QoS parameter information of the aggregated data

[0274] The configuration information of the data contained in the aggregated data may belong to different radio bearers of different users or 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 " Mapping-related information "User's radio bearer related information"

[0275] The information of the return link channel used by the mobile terminal part of the relay node to serve the aggregated data can be found in the above " Configuration information of a backhaul link channel of a relay node ”

[0276] 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 of different users for transmission.

[0277] The first aspect of the present invention is a migration process of a relay node. Address-related information required for a relay node FIG. 1 is an example of a migration process of a relay node according to an embodiment of the present invention. Configuration information of a user As shown, the process includes the following steps:

[0278] Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message can be a HANDOVER REQUEST message, which is used to provide the third node with the configuration information related to the first node when it is served by the second node, which helps the third node to generate the configuration to serve the first node. In one embodiment, the HANDOVER REQUEST message is a HANDOVER REQUEST message for the mobile terminal part of the first node, and the content contained in the message can refer to the HANDOVER REQUEST message in TS 38.423. In addition to the information contained in the existing HANDOVER REQUEST message, the HANDOVER REQUEST message can contain at least one of the following information:

[0279] The first user configuration information is the configuration information of one or more users served by the first node before the migration, which can be the users accessing the distributed unit part of the first node, and for each user, the content contained in the information can refer to the above-mentioned "address-related first information" Mapping-related information The first user configuration information is the configuration information of one or more users served by the first node before the migration, which can be the users accessing the distributed unit part of the first node, and for each user, the content contained in the information can refer to the above-mentioned "address-related first information"

[0280] The first backhaul link channel configuration information is the configuration information related to the backhaul link channel served by the mobile terminal part of the first node, which can refer to the above-mentioned "address-related first information" Configuration information of a backhaul link channel of a relay node Address-related information required for a relay node

[0281] The first address-related information is the address-related information required by the first node, which contains the address-related information used by the first node before the migration, i.e. the first node uses the address-related information to perform data transmission with the second node, and the content contained in the information can refer to the above-mentioned "address-related first information" Configuration information of a user Mapping-related information

[0282] The first configuration information of the aggregated data is the configuration information of the aggregated data served by the first node before the migration, and the content contained in the information can refer to the above-mentioned "address-related first information" Figure 3

[0283] ​​​Step 1-2: The third node sends a first response message to the second node. In one embodiment, the first response message can be a handover response message, which is used to provide the second node with the configuration generated by the third node to serve the first node. In one embodiment, the handover response message is a handover response message for the mobile terminal part of the first node, and the content contained in the handover response message can refer to the HANDOVER REQUEST ACKNOWLEDGE message in TS 38.423. In addition to the information contained in the existing HANDOVER REQUEST ACKNOWLEDGE message, the handover response message at least contains one of the following information:

[0284] Second user configuration information, which is the configuration information of one or more users served by the first node after the migration of the distributed unit part of the first node. The content contained in the second user configuration information can refer to the above-mentioned “ Configuration information of a user ”;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;

[0285] Second mapping relationship information, which reflects the mapping relationship of the information used by the first node before and after the migration. The second mapping relationship information is used to update the configuration information used by the first node for data transmission. The content contained in the second mapping relationship information can refer to the above-mentioned “ Address-related information required for a relay node ”. The new information in the second mapping relationship information is the information required to be used by the first node after the migration, and the old information is the information used by the first node before the migration. The beneficial effect of the second mapping relationship information is that it can help the first node to update the configuration information required for the transmission of data (such as data of different users, F1AP signaling, etc.) of the distributed unit part of the first node by using less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data

[0286] Second backhaul link channel configuration information, which is the configuration information related to the backhaul link channel served by the mobile terminal part of the first node after the migration. The content contained in the second backhaul link channel configuration information can refer to the above-mentioned “ Mapping-related information Configuration information of a backhaul link channel of a relay node ”;In one embodiment, the backhaul link channel is a backhaul link channel accepted by the third node after the migration

[0287] Second address-related information, which is the address-related information required by the first node after the migration. The second address-related information is used for data transmission between the first node and the third node. The content contained in the second address-related information can refer to the above-mentioned “ Figure 3 Mapping-related information ”

[0288] Step 1-3: The second node sends a first configuration message to the first node. In one embodiment, the first configuration message can be a migration configuration message, which is used to provide the first node with configuration information required for migration and / or configuration information required after migration to the third node. In one embodiment, the migration configuration message can be an RRCReconfig message in TS 38.331, which contains at least one of the following information in addition to the information contained in the existing RRCReconfig message:

[0289] Third user configuration information, which is configuration information of one or more users served by the distributed unit part of the first node after migration of the first node, the content of which can be found in the above-mentioned “ Mapping-related information ” In one embodiment, the user is a user accepted by the third node after migration of the first node and / or a user not accepted by the third node

[0290] Third mapping relationship information, which reflects the mapping relationship of information used by the first node before and after migration, and is used to update the configuration information used by the first node for data transmission. The content of the information can be found in the above-mentioned “ Figure 3 ”, wherein the new information is information required to be used by the first node after migration, and the old information is information used by the first node before migration. The beneficial effect of the information is that it can help the first node to update the configuration information required for transmitting data (such as data of different users, F1AP signaling, etc.) of the distributed unit part by using less signaling, without using multiple different signaling to update the configuration information required for transmitting different data

[0291] Third 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 after migration, the content of which can be found in the above-mentioned “ Figure 3 Figure 3 ” In one embodiment, the backhaul link channel is a backhaul link channel accepted and / or not accepted by the third node after migration

[0292] Third address-related information, which is address-related information required by the first node after migration, and is used for data transmission between the first node and the third node, the content of which can be found in the above-mentioned “ Figure 3 Figure 3 ”

[0293] Optionally, after step 1-3 and before step 1-4, the process further comprises the process of the mobile terminal part of the first node accessing the third node, such as cell search, random access, etc. Since these processes are not related to the problem to be solved by the present application, they will not be described in detail in the present application.

[0294] Step 1-4: The first node sends a first configuration completion message to the third node. In one embodiment, the first configuration completion message can be a migration configuration completion message, which is used to confirm to the third node that the migration of the first node is completed. In one embodiment, the migration configuration completion message can be the RRCReconfigComplete message in TS38.331, and in addition to the information contained in the existing RRCReconfigComplete message, the migration configuration completion message at least contains one of the following information:

[0295] Fourth user configuration information, which is the configuration information of the users served by the distribution unit part of the first node after the migration of the first node, the content of which can be found in the above-mentioned “ Figure 5 ”;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

[0296] Fourth mapping relationship information, which reflects the mapping relationship of the information used by the first node before and after the migration, and is used to update the configuration information used by the first node side when transmitting data. The content of the information can be found in the above-mentioned “ Figure 5 ”, the new information in the information is the information required to be used by the first node after the migration, and the old information is the information used by the first node before the migration. The beneficial effect of the information is that it can help the third node to update the configuration information required for transmitting the data (such as the data of different users, F1AP signaling, etc.) of the distribution unit part of the first node with less signaling, without using multiple different signaling to update the configuration information required for transmitting different data

[0297] The above-mentioned flow, for the migration method of different relay nodes in Address-related information required for a relay node , will have different implementation manners. In the following embodiments, the specific content of the information contained in each message can be found in the above-mentioned “ Configuration information of a user ”、“ Mapping-related information Configuration information of a user ”、“ Mapping-related information ”、“ Configuration information of a user Address-related information required for a relay node". The procedures involved in the following embodiments are steps 1-1~1-4 described above. The difference between different embodiments is that the information contained in each message will be different. In order to simplify the description of each embodiment and highlight the difference of the information contained in different embodiments, the information contained in each message is not completely listed, and those not listed can be referred to the description in steps 1-1~1-4 described above. In addition, when describing embodiments 1-1-2~1-3-2, only the difference of the information contained in each message from embodiment 1-1-1 is described.

[0298] Embodiment 1-1-1 (based on Mapping-related information (a) Anchor node decides the configuration of relay node

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

[0300] First user configuration information, which contains at least one of the following information:

[0301] User's identity, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0302] User's radio bearer related information, for a radio bearer (such as data radio bearer DRB, signaling radio bearer SRB), the information contains at least one of the following information:

[0303] User's identity, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0304] User radio bearer's identity information, such as UE RB ID

[0305] Identity information, such as DRB ID, SRB ID

[0306] Radio bearer's QoS related information

[0307] Configuration information of the user's radio bearer

[0308] QoS related information satisfied by the relay node, i.e. QoS related information satisfied by the first node

[0309] information about QoS satisfied by the non-relay node, i.e. information about QoS satisfied by the non-first node

[0310] tunnel related information of uplink data, for a tunnel, the information at least includes one of the following: tunnel identification information, IP address, TEID, routing identification information, identification information of next hop node, identification information of backhaul link channel, etc.

[0311] tunnel related information of downlink data, for a tunnel, the information at least includes one of the following: tunnel identification information, IP address, TEID, configuration value information of DSCP field, configuration value information of flow label field

[0312] data forwarding related information, which can be for uplink data and / or downlink data, the information can include "whether data forwarding is needed"

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

[0314] second user configuration information, which at least includes one of the following:

[0315] identification of the user, the identification information is identification information used after the first node migrates to the third node, such as new gNB-CU / DU UE F1AP ID, new C-RNTI, new UE XnAP ID, further, it can also include identification information used before the first node migrates, such as old gNB-CU / DU UE F1AP ID, old C-RNTI, old UE XnAP ID

[0316] wireless bearer related information of the user, for a wireless bearer (such as data radio bearer DRB, signaling radio bearer SRB); in an embodiment, the wireless bearer can be admitted by the third node, or can not be admitted by the third node; the information at least includes one of the following:

[0317] an identity of the user, which is the identity information used by the first node after the migration to the third node, such as new gNB-CU / DU UE F1AP ID, new C-RNTI, new UE XnAP ID, and further possibly including the identity information used by the first node before the migration, such as old gNB-CU / DU UE F1AP ID, old C-RNTI, old UE XnAP ID

[0318] an identity of a user radio bearer, such as UE RB ID

[0319] an identity, such as DRB ID, SRB ID

[0320] configuration information of the service user radio bearer, which in one embodiment is the configuration information generated by the third node

[0321] tunnel-related information of uplink data, which for one tunnel at least includes one of the following: tunnel identity information, IP address, TEID, routing identity information, identity information of the next hop node, identity information of the backhaul link channel, etc.; in one embodiment, the information is updated by the third node and is different from the information in step 1-1 above

[0322] tunnel-related information of downlink data, which for one tunnel at least includes one of the following: tunnel identity information, IP address, TEID, configuration value information of the DSCP field, configuration value information of the flow label field; in one embodiment, the information is updated by the third node and is different from the information in step 1-1 above

[0323] data forwarding-related information, which can be for uplink data and / or downlink data, and which can include IP address (address on the third node side) and / or TEID (TEID on the third node side)

[0324] second mapping relationship information, which reflects the mapping relationship between the information used by the first node before and after the migration, and which is used to update the configuration information used by the first node in data transmission. The content contained in the information can be referred to the above “ Configuration information of a backhaul link channel of a relay node ”, and specifically, the information at least includes one of the following:

[0325] Mapping information of addresses, for a mapping of an address, the information comprises at least one of the following information:

[0326] Identification information of addresses at the relay node side

[0327] Information about addresses at the new relay node side

[0328] Information about addresses at the old relay node side

[0329] Identification information of addresses at the anchor node side

[0330] Information about addresses at the new anchor node side

[0331] Information about addresses at the old anchor node side

[0332] Mapping information of tunnels, for a mapping of a tunnel, the information comprises at least one of the following information:

[0333] Identification information of tunnels for uplink data

[0334] Information about tunnels for new uplink data

[0335] Information about tunnels for old uplink data

[0336] Identification information of tunnels for downlink data

[0337] Information about tunnels for new downlink data

[0338] Information about tunnels for old downlink data

[0339] Mapping information of transport network layer associations, the information comprises at least one of the following information:

[0340] Identification information of transport network layer associations at the anchor node side

[0341] Information about transport network layer associations at the new anchor node side

[0342] Information about transport network layer associations at the old anchor node side

[0343] Identity information associated with the transport network layer on the relay node side

[0344] Information associated with the transport network layer on the new relay node side

[0345] Information associated with the transport network layer on the old relay node side

[0346] Mapping information for non-user plane data transmission

[0347] Mapping information for a routing identity, which includes at least one of the following information for a mapping of a routing identity:

[0348] New routing identity information

[0349] Old routing identity information

[0350] Mapping information for a next hop node, which includes at least one of the following information for a mapping of a next hop node:

[0351] New next hop node identity information

[0352] Old next hop node identity information

[0353] Mapping information for a backhaul link channel, which includes at least one of the following information for a mapping of a backhaul link channel:

[0354] New backhaul link channel identity information

[0355] Old backhaul link channel identity information

[0356] Applicable information

[0357] Exception information

[0358] The above-mentioned switching response message can only contain one of the "second user configuration information" and "second mapping relationship information". If it only contains the "second user configuration information", the third node provides updated configuration information for each user respectively. If it only contains the "second mapping relationship information", the second node can update multiple configurations at the same time (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time) through the information, so as to save signaling overhead.

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

[0360] Third user configuration information, which contains at least one of the following information:

[0361] User identifier, which is the identifier used after the first node is migrated to the third node, such as new gNB-CU / DU UE F1AP ID, new C-RNTI, new UE XnAP ID, and further can include the identifier used before the first node is migrated, such as old gNB-CU / DU UE F1AP ID, old C-RNTI, old UE XnAP ID

[0362] User radio bearer related information, for a radio bearer (such as a data radio bearer DRB, a signaling radio bearer SRB); in an embodiment, the radio bearer can be admitted by the third node, or can not be admitted by the third node; the information contains at least one of the following information:

[0363] User identifier, which is the identifier used after the first node is migrated to the third node, such as new gNB-CU / DU UE F1AP ID, new C-RNTI, new UE XnAP ID, and further can include the identifier used before the first node is migrated, such as old gNB-CU / DU UE F1AP ID, old C-RNTI, old UE XnAP ID

[0364] User radio bearer identifier, such as UE RB ID

[0365] Identifier, such as DRB ID, SRB ID

[0366] Configuration information of a service user radio bearer

[0367] Tunnel-related information of uplink data, for a tunnel, the information at least includes one of the following: tunnel identification information, IP address, TEID, routing identification information, identification information of next hop node, identification information of backhaul link channel, etc.; in an embodiment, the information is updated by the third node, different from the information in step 1-1

[0368] Tunnel-related information of downlink data, for a tunnel, the information at least includes one of the following: tunnel identification information, IP address, TEID, etc.; in an embodiment, the information is updated by the third node, different from the information in step 1-1

[0369] Third mapping relationship information, the information reflects the mapping relationship of the information used by the first node before and after the migration, and the information is used to update the configuration information used by the first node in data transmission. The content contained in the information can be referred to the above "configuration information of a service user radio bearer" Figure 5 ", specifically, the information at least includes one of the following:

[0370] Address mapping information, for an address mapping, the information at least includes one of the following:

[0371] Identification information of the address on the relay node side

[0372] Information related to the address on the new relay node side

[0373] Information related to the address on the old relay node side

[0374] Identification information of the address on the anchor node side

[0375] Information related to the address on the new anchor node side

[0376] Information related to the address on the old anchor node side

[0377] Tunnel mapping information, for a tunnel mapping, the information at least includes one of the following:

[0378] identification information of a tunnel for uplink data

[0379] new tunnel-related information for uplink data

[0380] old tunnel-related information for uplink data

[0381] identification information of a tunnel for downlink data

[0382] new tunnel-related information for downlink data

[0383] old tunnel-related information for downlink data

[0384] mapping information associated with a transport network layer, which includes at least one of the following information:

[0385] identification information of a transport network layer association on the side of an anchor node

[0386] new information of a transport network layer association on the side of an anchor node

[0387] old information of a transport network layer association on the side of an anchor node

[0388] identification information of a transport network layer association on the side of a relay node

[0389] new information of a transport network layer association on the side of a relay node

[0390] old information of a transport network layer association on the side of a relay node

[0391] mapping information for non-user-plane data transmission

[0392] mapping information for a routing identification, which includes at least one of the following information for a mapping of a routing identification:

[0393] new routing identification information

[0394] old routing identification information

[0395] mapping information for a next-hop node, which includes at least one of the following information for a mapping of a next-hop node:

[0396] identification information of the new next-hop node

[0397] identification information of the old next-hop node

[0398] mapping information of the backhaul link channel, for a backhaul link channel, the mapping information at least includes one of the following information:

[0399] identification information of the new backhaul link channel

[0400] identification information of the old backhaul link channel

[0401] applicable information

[0402] exception information

[0403] The above migration configuration message can only include one of the "third user configuration information" and the "third mapping relationship information", if only the "third user configuration information" is included, the second node provides the first node with updated configuration information for each user respectively, if only the "third mapping relationship information" is included, the first node can update multiple configurations at the same time (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time) through the information, so that the signaling overhead can be saved.

[0404] Step 1-4: The first node sends a first configuration completion message to the third node. In an embodiment, the first configuration completion message can be a migration configuration completion message, and the function of the message is to confirm the migration of the first node to the third node.

[0405] Embodiment 1-1-2 (based on Figure 4 (a), the anchor node and the relay node respectively determine the configuration of the relay node)

[0406] Step 1-1: The second node sends a first request message to the third node. In an embodiment, the first request message can be a handover request message, and the information included in the handover request message can refer to step 1-1 in embodiment 1-1-1 above

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

[0408] Second user configuration information, which may not contain "downlink data tunnel related information" for a user radio bearer, and other information can be found in step 1-2 of the above embodiment 1-1-1

[0409] Second mapping relationship information, which may not contain "new relay node side address related information", and / or "old relay node side address related information", and / or "new downlink data tunnel related information", and / or "old downlink data tunnel related information", and other information can be found in step 1-2 of the above embodiment 1-1-1

[0410] The above handover response message can only contain one of "second user configuration information" and "second mapping relationship information". If it only contains "second user configuration information", the third node provides updated configuration information for each user respectively. If it only contains "second mapping relationship information", the second node can update multiple configurations at the same time through this information (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time), which can save signaling overhead.

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

[0412] Third user configuration information, which may not contain "downlink data tunnel related information" for a user radio bearer, and other information can be found in step 1-3 of the above embodiment 1-1-1

[0413] Third mapping relationship information, which may not contain "new relay node side address related information", and / or "old relay node side address related information", and / or "new downlink data tunnel related information", and / or "old downlink data tunnel related information", and other information can be found in step 1-3 of the above embodiment 1-1-1

[0414] The above migration configuration message can only contain one of the "third user configuration information" and "third mapping relationship information". If only the "third user configuration information" is contained, the second node provides the first node with updated configuration information for each user respectively. If only the "third mapping relationship information" is contained, the first node can update multiple configurations simultaneously (such as updating the configurations of data transmission of different users simultaneously, or updating the configurations of signaling transmission simultaneously, or updating the configurations of data transmission and signaling transmission of different users simultaneously) through the information, thereby saving signaling overhead.

[0415] Step 1-4: The first node sends a first configuration completion message to the third node. In an embodiment, the first configuration completion message can be a migration configuration completion message, which is used to confirm to the third node that the migration of the first node is completed. In addition, the message further includes at least one of the following information:

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

[0417] User identifier, which is the identifier used by the first node after migrating to the third node, such as new gNB-CU / DU UE F1AP ID, new C-RNTI, new UE XnAP ID, and further can include the identifier used by the first node before migrating, such as old gNB-CU / DU UE F1AP ID, old C-RNTI, old UE XnAP ID

[0418] User radio bearer related information, for a radio bearer (such as a data radio bearer DRB, a signaling radio bearer SRB); in an embodiment, the radio bearer can be admitted by the third node, and / or not admitted by the third node; the information includes at least one of the following information:

[0419] User identifier, which is the identifier used by the first node after migrating to the third node, such as new gNB-CU / DU UE F1AP ID, new C-RNTI, new UE XnAP ID, and further can include the identifier used by the first node before migrating, such as old gNB-CU / DU UE F1AP ID, old C-RNTI, old UE XnAP ID

[0420] User radio bearer identifier, such as UE RB ID

[0421] identification information, such as DRB ID, SRB ID

[0422] tunnel-related information of downlink data, for a tunnel, the information includes at least one of the following: tunnel identification information, IP address, TEID; in an embodiment, the information is updated by the first node, which is different from the information in step 1-1

[0423] fourth mapping relationship information, which includes at least one of the following:

[0424] address mapping information, for an address mapping, the information includes at least one of the following:

[0425] identification information of the address on the side of the relay node

[0426] new address-related information on the side of the relay node

[0427] old address-related information on the side of the relay node

[0428] tunnel mapping information, for a tunnel mapping, the information includes at least one of the following:

[0429] identification information of the tunnel of downlink data

[0430] new tunnel-related information of downlink data

[0431] old tunnel-related information of downlink data

[0432] applicable information

[0433] exception information

[0434] The above migration configuration completion message can only contain one of the "fourth user configuration information" and the "fourth mapping relationship information". If only the "fourth user configuration information" is contained, the first node provides updated configuration information for each user to the third node respectively. If only the "fourth mapping relationship information" is contained, the third node can update multiple configurations simultaneously (such as updating the configurations of data transmission of different users simultaneously, or updating the configurations of signaling transmission simultaneously, or updating the configurations of data transmission and signaling transmission of different users simultaneously) through the information, thereby saving signaling overhead.

[0435] Embodiment 1-2-1 (based on Figure 6 (b), the anchor node decides the configuration of the relay node)

[0436] Step 1-1: The second node sends a first request message to the third node. In an embodiment, the first request message can be a handover request message, and the information contained in the handover request message can refer to step 1-1 in Embodiment 1-1-1 above.

[0437] Step 1-2: The third node sends a first response message to the second node. In an embodiment, the first response message can be a handover response message, and the handover response message contains at least one of the following information:

[0438] Second user configuration information, for one radio bearer, the information can not contain "configuration information of a served user radio bearer" and / or "data forwarding related information", and other information contained in the information can refer to step 1-2 in Embodiment 1-1-1 above.

[0439] Second mapping relationship information, which can refer to step 1-2 in Embodiment 1-1-1 above.

[0440] The above handover response message can only contain one of the "second user configuration information" and the "second mapping relationship information". If only the "second user configuration information" is contained, the third node provides updated configuration information for each user respectively. If only the "second mapping relationship information" is contained, the second node can update multiple configurations simultaneously (such as updating the configurations of data transmission of different users simultaneously, or updating the configurations of signaling transmission simultaneously, or updating the configurations of data transmission and signaling transmission of different users simultaneously) through the information, thereby saving signaling overhead.

[0441] Step 1-3: The second node sends a first configuration message to the first node. In an embodiment, the first configuration message can be a migration configuration message, and the migration configuration message contains at least one of the following information:

[0442] Third user configuration information, for one radio bearer, the information can not contain "configuration information of serving user radio bearer", other information contained in the information can refer to step 1-3 of embodiment 1-1-1

[0443] Third mapping relationship information, the information contained in the information can refer to step 1-3 of embodiment 1-1-1

[0444] The above migration configuration message can only contain one of "third user configuration information" and "third mapping relationship information", if only "third user configuration information" is contained, the second node provides updated configuration information for each user to the first node respectively, if only "third mapping relationship information" is contained, the first node can update multiple configurations at the same time through the information (such as updating the configuration of data transmission of different users at the same time, or updating the configuration of signaling transmission at the same time, or updating the configuration of data transmission and signaling transmission of different users at the same time), which can save signaling overhead.

[0445] Step 1-4: the first node sends a first configuration completion message to the third node. In an embodiment, the first configuration completion message can be a migration configuration completion message, and the function of the message is to confirm the migration of the first node to the third node.

[0446] Embodiment 1-2-2 (based on Figure 3 (b), the anchor node and the relay node respectively determine the configuration of the relay node)

[0447] Step 1-1: the second node sends a first request message to the third node. In an embodiment, the first request message can be a handover request message, and the information contained in the handover request message can refer to step 1-1 of the above embodiment 1-1-1;

[0448] Step 1-2: the third node sends a first response message to the second node. In an embodiment, the first response message can be a handover response message, and the handover response message contains at least one of the following information:

[0449] The second user configuration information can not include "configuration information of serving user radio bearer" and / or "data forwarding related information" for a user radio bearer; and the "downlink data tunnel related information" can include at least one of the following: tunnel identification information, IP address, TEID, configuration value information of DSCP field, and configuration value information of flow label field. In an embodiment, the configuration value information of DSCP field and the configuration value information of flow label field are updated by the third node and can be different from the information in step 1-1, and the other information is the information received in step 1-1. The other information included in the "second user configuration information" can refer to step 1-2 of embodiment 1-1-1

[0450] The second mapping relationship information can not include "new relay node side address related information", "old relay node side address related information", "new downlink data tunnel related information", and "old downlink data tunnel related information", and the other information can refer to step 1-2 of embodiment 1-1-1

[0451] The handover response message can include only one of the "second user configuration information" and the "second mapping relationship information". If only the "second user configuration information" is included, the third node provides updated configuration information for each user respectively. If only the "second mapping relationship information" is included, the second node can update multiple configurations simultaneously (such as updating data transmission configurations of different users simultaneously, or updating signaling transmission configurations simultaneously, or updating data transmission and signaling transmission configurations of different users simultaneously) through the information, thereby saving signaling overhead.

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

[0453] The third user configuration information can not include "configuration information of serving user radio bearer" and / or "downlink data tunnel related information" for a user radio bearer. The other information included in the third user configuration information can refer to step 1-3 of embodiment 1-1-1

[0454] Third mapping relationship information, which can not contain "new relay node side address related information", and / or "old relay node side address related information", and / or "new downlink data tunnel related information", and / or "old downlink data tunnel related information", and other information can refer to step 1-3 of embodiment 1-1-1 above

[0455] The above migration configuration message can only contain one of "third user configuration information" and "third mapping relationship information". If it only contains "third user configuration information", the second node provides updated configuration information for each user to the first node respectively. If it only contains "third mapping relationship information", the first node can update multiple configurations at the same time through the information (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time), which can save signaling overhead.

[0456] Step 1-4: The first node sends a first configuration completion message to the third node. In an embodiment, the first configuration completion message can be a migration configuration completion message, which is used to confirm to the third node that the migration of the first node is completed. In addition, the message also includes at least one of the following information:

[0457] Fourth user configuration information, which contains information that can be referred to step 1-4 of embodiment 1-1-2 above

[0458] Fourth mapping relationship information, which contains information that can be referred to step 1-4 of embodiment 1-1-2 above

[0459] The above migration configuration completion message can only contain one of "fourth user configuration information" and "fourth mapping relationship information". If it only contains "fourth user configuration information", the first node provides updated configuration information for each user to the third node respectively. If it only contains "fourth mapping relationship information", the third node can update multiple configurations at the same time through the information (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time), which can save signaling overhead.

[0460] Embodiment 1-3-1 (based on Figure 3 (c), the anchor node decides the configuration of the relay node)

[0461] Step 1-1: The second node sends a first request message to the third node. In an embodiment, the first request message can be a handover request message, which contains information that can be referred to step 1-1 of embodiment 1-1-1 above

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

[0463] Second user configuration information, for one user radio bearer, the information can not contain "configuration information of the serving user radio bearer", for "tunnel related information of uplink data", in one embodiment, the tunnel identification information and / or IP address and / or TEID contained in the information can 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 contained in the information can be updated by the third node; for "tunnel related information of downlink data", in one embodiment, the information contained in the information can be updated by the third node, in another embodiment, the information can not contain configuration value information of DSCP field and / or configuration value information of flow label field; in addition, for one user radio bearer, the information can also contain "first tunnel information" and / or "second tunnel information", the effect of receiving "first tunnel information" is that the second node will first send data sent to the first node to the third node according to "first tunnel information", and then send the data to the first node by the third node, and further the third node will update the information in the data packet (such as IP address, TEID, etc.); the effect of receiving "second tunnel information" is that the first node will first send data sent to the second node to the third node according to "second tunnel information", and then send the data to the second node by the third node, and further the third node will update the information in the data packet (such as IP address, TEID, etc.). Other information contained in the "second user configuration information" can be referred to step 1-2 in embodiment 1-1-1 above

[0464] Second mapping relationship information, which can be referred to step 1-2 in embodiment 1-1-1 above

[0465] The above handover response message can only contain one of "second user configuration information" and "second mapping relationship information", if only contains "second user configuration information", the third node provides updated configuration information for each user respectively, if only contains "second mapping relationship information", the second node can update multiple configurations at the same time (such as updating the configuration of data transmission of different users at the same time, or updating the configuration of signaling transmission at the same time, or updating the configuration of data transmission and signaling transmission of different users at the same time) through the information, which can save signaling overhead.

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

[0467] Third user configuration information, for one radio bearer, the information can not contain "configuration information of the service user radio bearer", for "tunnel related information of uplink data", its IP address and / or TEID are updated according to the "second tunnel information" received in 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 backhaul link channel are updated according to the "tunnel related information of uplink data" received in step 1-2, for "tunnel related information of downlink data", it contains the tunnel identification information and / or IP address and / or TEID contained in step 1-2 above; other information contained in the "third user configuration information" can refer to step 1-3 in embodiment 1-1-1 above

[0468] Third mapping relationship information, which contains information as described in step 1-3 of embodiment 1-1-1

[0469] The migration configuration message can only contain one of the "third user configuration information" and "third mapping relationship information", if it only contains the "third user configuration information", the second node provides updated configuration information for each user to the first node respectively, if it only contains the "third mapping relationship information", the first node can update multiple configurations at the same time (such as updating the configuration of data transmission of different users at the same time, or updating the configuration of signaling transmission at the same time, or updating the configuration of data transmission and signaling transmission of different users at the same time) through the information, which can save signaling overhead.

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

[0471] Embodiment 1-3-2 (based on Figure 6 (c), the anchor node and the relay node decide the configuration of the relay node respectively)

[0472] Step 1-1: The second node sends a first request message to the third node. In one embodiment, the first request message can be a handover request message, which contains information as described in step 1-1 of embodiment 1-1-1 above;

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

[0474] Second user configuration information, which can not contain "configuration information of the serving user radio bearer" and / or "downlink data tunnel related information" for one user radio bearer; for "uplink data tunnel related information", in one embodiment, the tunnel identification information and / or IP address and / or TEID contained in the information can be the same as in step 1-1, and the routing identification information and / or next hop node identification information and / or backhaul link channel identification information contained in the information can be updated by the third node; in addition, the information can also contain "first tunnel information" and / or "second tunnel information" for one user radio bearer, 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 send the data to the first node by the third node, and further the third node will 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 send the data to the second node by the third node, and further the third node will update the information in the data packet (such as IP address, TEID, etc.). Other information contained in the "second user configuration information" can be referred to step 1-2 in embodiment 1-1-1 above

[0475] Second mapping relationship information, which can not contain "new relay node side address related information", and / or "old relay node side address related information", and / or "new downlink data tunnel related information", and / or "old downlink data tunnel related information", which can be referred to step 1-2 in embodiment 1-1-1 above

[0476] The above handover response message can only contain one of the "second user configuration information" and the "second mapping relationship information", if only containing the "second user configuration information", the third node provides updated configuration information for each user respectively, if only containing the "second mapping relationship information", the second node can update multiple configurations at the same time (such as updating the data transmission configuration of different users at the same time, or updating the signaling transmission configuration at the same time, or updating the data transmission and signaling transmission configuration of different users at the same time) through the information, which can save signaling overhead.

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

[0478] Third user configuration information, which can not contain "configuration information of a user radio bearer", and / or "downlink tunnel related information" for a radio bearer, and for "uplink tunnel related information", the IP address and / or TEID are updated according to the "second tunnel information" received in 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 backhaul link channel are updated according to the "uplink tunnel related information" received in step 1-2. Other information contained in the third user configuration information can be referred to step 1-3 in embodiment 1-1-1

[0479] Third mapping relationship information, which can not contain "new relay node side address related information", and / or "old relay node side address related information", and / or "new downlink tunnel related information", and / or "old downlink tunnel related information". The information contained in the third mapping relationship information can be referred to step 1-3 in embodiment 1-1-1

[0480] The migration configuration message can only contain one of the "third user configuration information" and "third mapping relationship information". If it only contains the "third user configuration information", the second node provides updated configuration information for each user to the first node respectively. If it only contains the "third mapping relationship information", the first node can update multiple configurations at the same time (such as updating the configuration of data transmission of different users at the same time, or updating the configuration of signaling transmission at the same time, or updating the configuration of data transmission and signaling transmission of different users at the same time) through the information, which can save signaling overhead.

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

[0482] Fourth user configuration information, which contains information that can be referred to step 1-4 in embodiment 1-1-2

[0483] Fourth mapping relationship information, which contains information that can be referred to step 1-4 in embodiment 1-1-2

[0484] The migration configuration completion message can only contain one of the fourth user configuration information and the fourth mapping relationship information. If only the fourth user configuration information is contained, the first node provides updated configuration information for each user to the third node respectively. If only the fourth mapping relationship information is contained, the third node can update multiple configurations at the same time through the information (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time), which can save signaling overhead.

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

[0486] The migration configuration message and the migration configuration completion message can use the existing RRCReconfig message and RRCReconfigComplete to send related information, or use other existing messages or new messages.

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

[0488] The possible beneficial effects of the above process are:

[0489] 1. Complete the migration of the relay node 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 the users served by the distributed unit part of the relay node between different anchor nodes. Unlike traditional technology, the handover of each user in traditional technology needs to perform a separate handover process, but the above process can complete the simultaneous handover of multiple users at the same time;

[0490] 2. In the process of the migration of the relay node, the configuration information of the data required to be transmitted by the distributed unit part of the relay node needs to be updated. According to the above process, the signaling required for updating the configuration information can be effectively reduced. For example, the mapping-related information exchanged in the above process can help the receiving node to update multiple configurations at the same time (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time), thereby saving the signaling overhead.

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

[0492] The second aspect of the present application is a configuration update process of a relay node, Configuration information of a user For an example of the configuration update process of the relay node according to an embodiment of the present application.

[0493] As shown in Configuration information of a user , the process includes the following steps:

[0494] Step 2-1: The fourth node sends a first configuration request message to the first node, which is mainly used for configuration update of the first node. The first configuration request message can contain at least one of the following information:

[0495] Address-related fifth information, which is address-related information provided by the fourth node to the first node, and is used for data transmission between the first node and the fourth node. The content contained in the information can be referred to in the above “ Figure 3 Figure 3 ”

[0496] Fifth user configuration information, the content contained in the information can be referred to in the above “ Mapping-related information ”, in addition, for a user, the information can further contain at least one of the following information:

[0497] Before configuration update, the identification information of the user, such as old gNB-CU UE F1AP ID, and / or old gNB-DU UE F1AP ID

[0498] After configuration update, the identification information of the user, such as new gNB-CU UE F1AP ID, and / or new gNB-DU UE F1AP ID

[0499] Fifth mapping relationship information, which reflects the mapping relationship of information used before and after the configuration update of the first node, and is used to update the configuration information used by the first node for data transmission. The content contained in this information can be referred to in the above "Fifth user configuration information" Configuration information of a user ", and the new information in this information is the information required to be used after the configuration update of the first node, and the old information is the information used before the configuration update of the first node. The beneficial effect of this information is that the configuration information required for the first node to update the transmission of the data of its distributed unit part (such as the data of different users, F1AP signaling, etc.) can be updated with less signaling, without using multiple different signals to update the configuration information required for the transmission of different data

[0500] The above-mentioned first configuration request message can only contain one of the "fifth user configuration information" and the "fifth mapping relationship information". If only the "fifth user configuration information" is contained, the fourth node provides updated configuration information for each user of the first node respectively. If only the "fifth mapping relationship information" is contained, the first node can update multiple configurations at the same time (such as updating the configurations for the data transmission of different users at the same time, or updating the configurations for the signaling transmission at the same time, or updating the configurations for the data transmission and signaling transmission of different users at the same time) through this information. In this way, the signaling overhead can be saved.

[0501] Step 2-2: Optionally, the first node sends a first configuration response message to the fourth node, which is mainly used to confirm the above-mentioned first configuration request message. Further, this message can also be used to notify the first node of the update of the configuration information. This message at least includes one of the following information:

[0502] Sixth user configuration information, the content contained in this information can be referred to in the above "Fifth user configuration information" Figure 6 In addition, for a user, optionally, this information can also contain at least one of the following information:

[0503] Before the configuration update, the identification information of the user, such as old gNB-CU UE F1AP ID, and / or old gNB-DU UE F1AP ID

[0504] After the configuration update, the identification information of the user, such as new gNB-CU UE F1AP ID, and / or new gNB-DU UE F1AP ID

[0505] Sixth mapping relationship information, which reflects the mapping relationship of information used by the first node before and after the configuration update, and is used to update the configuration information used by the first node for data transmission. The content contained in this information can be referred to in the above "0001454 Configuration information of a user ", and the new information in this information is the information required to be used after the configuration update of the first node, and the old information is the information used before the configuration update of the first node. The beneficial effect of this information is that the configuration information required for the first node to update the transmission of the data of its distributed unit part (such as the data of different users, F1AP signaling, etc.) can be updated with less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data

[0506] The above first configuration response message can only contain one of the "sixth user configuration information" and "sixth mapping relationship information". If only the "sixth user configuration information" is contained, the first node provides updated configuration information for each user respectively. If only the "sixth mapping relationship information" is contained, the fourth node can use this information to update multiple configurations at the same time (such as updating the configurations for the transmission of data of different users at the same time, or updating the configurations for the transmission of signaling at the same time, or updating the configurations for the transmission of data of different users and signaling at the same time), which can save signaling overhead.

[0507] The above process has different implementations. In the following embodiments, the specific content of the information contained in each message can be referred to in the above "0001459 Configuration information of a user ", "0001460 Figure 7 ", "0001461 Figure 7 Configuration information of a user ", and "0001463 Figure 3 ". The process involved in the following embodiments is step 2-1~step 2-2. The difference between different embodiments is that the information contained in each message is different. In order to simplify the description of each embodiment and highlight the difference between the information contained in different implementations, the information contained in each message is not completely listed, and those information not listed can be referred to in the description of step 2-1~step 2-2.

[0508] Embodiment 2-1 (update configuration completely determined by anchor node)

[0509] Step 2-1: The fourth node sends a first configuration request message to the first node, which is mainly used for configuration update of the first node. The first configuration request message can contain at least one of the following information:

[0510] Fifth user configuration information, which contains at least one of the following information:

[0511] User's identity information before configuration update, such as old gNB-CU UE F1AP ID, and / or old gNB-DU UE F1AP ID

[0512] User's identity information after configuration update, such as new gNB-CU UE F1AP ID, and / or new gNB-DU UE F1AP ID

[0513] User's radio bearer related information, for a radio bearer (such as data radio bearer DRB, signaling radio bearer SRB), the information at least includes one of the following information:

[0514] User's identity information before configuration update, such as old gNB-CU UE F1AP ID, and / or old gNB-DU UE F1AP ID

[0515] User's identity information after configuration update, such as new gNB-CU UE F1AP ID, and / or new gNB-DU UE F1AP ID

[0516] User's radio bearer identity information, such as UE RB ID

[0517] Identity information, such as DRB ID, SRB ID

[0518] Uplink data tunnel related information, for a tunnel, the information at least includes one of the following information: tunnel identity information, IP address, TEID, routing identity information, next hop node identity information, backhaul link channel identity information, etc.

[0519] Downlink data tunnel related information, for a tunnel, the information at least includes one of the following information: tunnel identity information, IP address, TEID

[0520] Fifth mapping relationship information, the information at least includes one of the following information:

[0521] Address mapping information, for an address mapping, the information at least includes one of the following information:

[0522] Relay node side address identity information

[0523] new relay node side address related information

[0524] old relay node side address related information

[0525] anchor node side address identification information

[0526] new anchor node side address related information

[0527] old anchor node side address related information

[0528] tunnel mapping information, for a tunnel, the information comprises at least one of the following:

[0529] uplink data tunnel identification information

[0530] new uplink data tunnel related information

[0531] old uplink data tunnel related information

[0532] downlink data tunnel identification information

[0533] new downlink data tunnel related information

[0534] old downlink data tunnel related information

[0535] transport network layer association mapping information, for a transport network layer association, the information comprises at least one of the following:

[0536] anchor node side transport network layer association identification information

[0537] new anchor node side transport network layer association information

[0538] old anchor node side transport network layer association information

[0539] relay node side transport network layer association identification information

[0540] new relay node side transport network layer association information

[0541] Information of old transmission network layer association at the relay node side

[0542] Mapping information of non-user plane data transmission

[0543] Mapping information of routing identification, for a mapping of a routing identification, the information includes at least one of the following:

[0544] New routing identification information

[0545] Old routing identification information

[0546] Mapping information of next hop node, for a mapping of a next hop node, the information includes at least one of the following:

[0547] New next hop node identification information

[0548] Old next hop node identification information

[0549] Mapping information of backhaul link channel, for a mapping of a backhaul link channel, the information includes at least one of the following:

[0550] New backhaul link channel identification information

[0551] Old backhaul link channel identification information

[0552] Applicable information

[0553] Exception information

[0554] Step 2-2: Optionally, the first node sends a first configuration response message to the fourth node, which is mainly used for the confirmation of the first configuration request message.

[0555] Embodiment 2-2 (update configuration is determined by anchor node and relay node respectively)

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

[0557] Fifth user configuration information, for one user radio bearer, the information can not contain "downlink data tunnel related information", other information can refer to the step 2-1 in the above embodiment 2-1

[0558] Fifth mapping relationship information, the information can not contain "new relay node side address related information", and / or "old relay node side address related information", and / or "new downlink data tunnel related information", and / or "old downlink data tunnel related information", and / or "new relay node side transport network layer associated information", and / or "old relay node side transport network layer associated information", other information can refer to the step 2-1 in the above embodiment 2-1

[0559] Step 2-2: optionally, the first node sends a first configuration response message to the fourth node, which is mainly used to confirm the above first configuration request message, further, the message can also be used to notify the first node of the update of the configuration information, the message at least includes one of the following information:

[0560] Sixth user configuration information, which at least contains one of the following information:

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

[0562] User identification information after configuration update, such as new gNB-CU UE F1AP ID, and / or new gNB-DU UE F1AP ID

[0563] User radio bearer related information, for one radio bearer (such as data radio bearer DRB, signaling radio bearer SRB), the information at least includes one of the following information:

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

[0565] User identification information after configuration update, such as new gNB-CU UE F1AP ID, and / or new gNB-DU UE F1AP ID

[0566] user radio bearer identification information, such as UE RB ID

[0567] identification information, such as DRB ID, SRB ID

[0568] tunnel-related information for downlink data, for a tunnel, the information including at least one of the following: tunnel identification information, IP address, TEID

[0569] sixth mapping relationship information, the information including at least one of the following:

[0570] address mapping information, for a mapping of an address, the information including at least one of the following:

[0571] relay node side address identification information

[0572] new relay node side address-related information

[0573] old relay node side address-related information

[0574] tunnel mapping information, for a mapping of a tunnel, the information including at least one of the following:

[0575] downlink data tunnel identification information

[0576] new downlink data tunnel-related information

[0577] old downlink data tunnel-related information

[0578] transport network layer association-related mapping information, for a mapping of a transport network layer association, the information including at least one of the following:

[0579] relay node side transport network layer association identification information

[0580] new relay node side transport network layer association information

[0581] old relay node side transport network layer association information

[0582] Applicable information

[0583] Exception information

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

[0585] 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:

[0586] 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:

[0587] Tunnel identification information for uplink data

[0588] Tunnel-related information for old uplink data, such as IP address and / or TEID

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

[0590] Routing identification information

[0591] Next-hop node identification information

[0592] Identification information of the backhaul link channel

[0593] 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:

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

[0595] IP address information

[0596] Port Information

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

[0598] mapping information of the next-hop node, the information including one or more mapping information of the next-hop node, for a mapping of a next-hop node, the information including at least one of the following information:

[0599] identification information of the new next-hop node

[0600] identification information of the old next-hop node

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

[0602] downlink tunnel related information, the information including one or more downlink tunnel related information, for a downlink tunnel, the information including at least one of the following information:

[0603] identification information of the downlink data tunnel

[0604] old downlink data tunnel related information, such as IP address, and / or TEID

[0605] new downlink data tunnel related information, such as IP address, and / or TEID

[0606] address mapping information, the information including one or more address mapping information, for an address, the information including at least one of the following information:

[0607] identification information of the relay node side address

[0608] new relay node side address related information, such as IP address

[0609] old relay node side address related information, such as IP address

[0610] relay node side transport network layer association information, the information including one or more relay node side transport network layer association, for a relay node side transport network layer association, the information including at least one of the following information:

[0611] identification information of the relay node side transport network layer association

[0612] IP address information

[0613] Port information

[0614] Indication information of the use of the transport network layer association at the relay node side

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

[0616] Step 2-1: The fourth node sends a first configuration request message to the first node, which is mainly used for configuration update of the first node, which is for one or more users, or for one or more radio bearers of the user; for a user or a user radio bearer, the first configuration request message can contain at least one of the following information:

[0617] Identity information of the user

[0618] Identity information of the radio bearer of the user, such as DRB ID

[0619] Information related to the uplink tunnel, which includes information related to one or more uplink tunnels of a user or a user radio bearer, and for an uplink tunnel, the information at least includes one of the following information:

[0620] Identity information of the tunnel of the uplink data

[0621] Information related to the old tunnel of the uplink data, such as IP address, and / or TEID

[0622] Information related to the new tunnel of the uplink data, such as IP address, and / or TEID

[0623] Routing identification information

[0624] Identity information of the next hop node

[0625] Identity information of the backhaul link channel

[0626] Information of the transport network layer association at the anchor node side, which includes one or more transport network layer associations at the anchor node side, and for a transport network layer association at the anchor node side, the information at least includes one of the following information:

[0627] Identity information of the transport network layer association at the anchor node side

[0628] IP address information

[0629] Port information

[0630] Indication information of the use of the new anchor node side transport network layer association

[0631] Mapping information of the next hop node, which includes one or more mapping information of a next hop node, for each mapping information, at least one of the following information:

[0632] Identification information of the new next hop node

[0633] Identification information of the old next hop node

[0634] 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 wireless bearers of the user; for a user or a wireless bearer of the user, the message includes at least one of the following information:

[0635] Identification information of the user

[0636] Identification information of the wireless bearer of the user, such as DRB ID

[0637] Information related to the downlink tunnel, which includes one or more information related to the downlink tunnel, for each downlink tunnel, at least one of the following information:

[0638] Identification information of the tunnel of the downlink data

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

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

[0641] Mapping information of the address, which includes one or more mapping information of the address, for each address, at least one of the following information:

[0642] Identification information of the address of the relay node side

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

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

[0645] Information about transport network layer associations on the relay node side, including 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:

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

[0647] IP address information

[0648] Port Information

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

[0650] In the above process, if Figure 3 , 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 Configuration information of a user Step 1-1 in the process.

[0651] 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 UECONTEXT SETUP SETUP / MODIFICATION REQUEST and UECONTEXT SETUP SETUP / MODIFICATION RESPONSE messages, respectively, to transmit relevant information specific to a user, or may use other or newly defined user-associated F1AP messages.

[0652] The possible benefits of the above procedure are: when the configuration information of the data transmitted by the distribution unit part of the relay node needs to be updated, according to the above procedure, the signaling required for updating the configuration information can be effectively reduced. For example, the mapping-related information exchanged in the above procedure can help the receiving node to update multiple configurations at the same time (such as updating the configurations of data transmission of different users at the same time, or updating the configurations of signaling transmission at the same time, or updating the configurations of data transmission and signaling transmission of different users at the same time), thereby saving signaling overhead.

[0653] The third aspect of the present application is a configuration interaction procedure of a relay node, which involves a fifth node, a sixth node and a first node. Figure 8 For example, the configuration interaction procedure of a relay node according to an embodiment of the present application. The procedure is related to the method in (b) and (c) above, in which the source anchor node in the figure corresponds to the fifth node in the procedure, the target anchor node in the figure corresponds to the sixth node in the procedure, and the relay node 3 corresponds to the first node in the procedure. In another embodiment, the fifth node and the sixth node can be two different nodes. Further, the distribution unit part of the first node maintains a connection with the fifth node, and 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 users served by the distribution unit part, the control signaling generated by the distribution unit part, such as F1AP messages) will be transmitted by the backhaul link channel configured by the sixth node and transmitted according to the path configured by the sixth node. Figure 8 Figure 9 As shown in (b) and (c) above, the configuration interaction procedure of the relay node includes the following steps:

[0654] As shown in (b) and (c) above, the configuration interaction procedure of the relay node includes the following steps: Figure 9

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

[0656] The seventh user configuration information is for the user accessing the first node (the distribution unit part of the first node), and one benefit of sending this information to the sixth node is that the sixth node can obtain the configuration information of the data of the user accessing the first node. The information contained in this information can be referred to in the above “ Figure 10 ”, and specifically includes at least one of the following information:

[0657] ​​An identifier of a user, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID, in one embodiment, the information can contain identifiers of multiple users, then the information can at least include one of the following information:

[0658] gNB-CU UE F1AP ID

[0659] gNB-DU UE F1AP ID

[0660] C-RNTI

[0661] An identifier of a serving cell

[0662] UE XnAP ID, in one embodiment, the ID is assigned by the fifth node

[0663] The above-mentioned identifiers are only examples, and other identifiers are not excluded.

[0664] Information related to a radio bearer of a user, for one radio bearer (such as a data radio bearer DRB, a signaling radio bearer SRB), the radio bearer can be requested to be added, can be requested to be modified, or can be requested to be deleted, the information at least includes one of the following information:

[0665] An identifier of a user, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0666] An identifier of a radio bearer of a user, such as UE RB ID, the information can indicate a radio bearer of a specific user, in other words, the identifier information not only indicates a user, but also indicates a radio bearer of the user

[0667] An identifier, such as DRB ID, SRB ID

[0668] Information related to QoS of a radio bearer, the information contains configuration information of QoS parameters of a radio bearer; in one embodiment, the information is actual QoS information of a radio bearer; in another embodiment, the information is QoS information that needs to be met by a receiving node, then the QoS information is different from the above-mentioned "actual QoS information of a radio bearer"

[0669] QoS information that the first node is capable of satisfying when serving the radio bearer, which is different from the "QoS information of the radio bearer". The benefit of this information is that a node receiving this information can know the QoS that the first node is capable of satisfying when serving the user's radio bearer, and determine how to configure other nodes to serve the user's radio bearer, so that the first node and other nodes jointly serve the user's radio bearer and satisfy the QoS requirement of the radio bearer. Another benefit is that a node receiving this information can make sure that the first node serves the user's radio bearer according to the QoS indicated by this information, so that there is no need to modify the configuration information of the first node when serving the user's radio bearer

[0670] QoS information that other nodes in the network, except the first node, are required to satisfy when jointly serving the radio bearer, which is different from the "QoS information of the radio bearer". The benefit of this information is that a node receiving this information can know the QoS that other nodes, except the first node, are required to satisfy when serving the user's radio bearer, and determine how to configure other nodes to serve the user's radio bearer, so that the first node and other nodes jointly serve the user's radio bearer and satisfy the QoS requirement of the radio bearer. Another benefit is that a node receiving this information can make sure that other nodes serve the user's radio bearer according to the QoS indicated by this information, so that there is no need to modify the configuration information of the first node when serving the user's radio bearer

[0671] Tunnel information of uplink data, which can be one or multiple, indicating information on the side of the anchor node (or the centralized unit of the anchor node or the user plane part of the centralized unit of the anchor node), and for one tunnel, the information includes at least one of the following information:

[0672] Tunnel identification information

[0673] IP address

[0674] TEID

[0675] Routing identification information, which is used to indicate the transmission path of the uplink data (further, the uplink data is transmitted through the tunnel), including the address information (BAP address) of the receiving node and / or the transmission path identification information (path ID), further, according to the information, the relay node can add the information to the uplink data packet transmitted through the tunnel

[0676] Identification information of the next hop node, which is the node directly receiving the uplink data (further, the uplink data is transmitted through the tunnel) when the relay node transmits the uplink data, in other words, the relay node transmits the uplink data to the next hop node, and then the next hop node directly or indirectly (through other nodes) transmits the uplink data to the destination node of the uplink data. According to the information, the relay node knows which node to transmit the uplink data to

[0677] Identification information of the backhaul link channel, which is the backhaul link channel used by the relay node to transmit the uplink data (further, the uplink data is transmitted through the tunnel) to the next hop node. According to the information, the relay node knows which backhaul link channel to transmit the uplink data

[0678] Tunnel-related information of the downlink data, which may be one or more, the information indicates the information of the relay node or the distributed unit part of the relay node, for one tunnel, the information at least includes one of the following information:

[0679] Tunnel identification information

[0680] IP address

[0681] TEID

[0682] Configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is transmitted through the tunnel)

[0683] Configuration value information of the flow label field in the downlink data packet (further, the downlink data packet is transmitted through the tunnel)

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

[0685] The information sent by the fifth node to the first node, such as the F1AP message, in one embodiment, the information includes the IP packet of the F1AP message; after receiving the information, the sixth node sends the received information to the first node

[0686] Control signaling type information, which indicates the type of the transmitted control signaling, which can be the "information sent by the fifth node to the first node" included in the above-mentioned "first control signaling related information", or one or more control signaling transmitted between the fifth node and the first node; in one embodiment, the information can indicate control signaling type 1, control signaling type 2, etc., and different types 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 can indicate user-related control signaling (UE-associated signaling), or non-user-related control signaling (non-UE-associated signaling), etc.; further, the information included in the above-mentioned "first control signaling related information" is applicable to the control signaling type indicated by the "control signaling type information"

[0687] Destination address information of the received downlink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information on the side of the first node

[0688] Destination address information of the received uplink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information on the side of the fifth node

[0689] Step 3-2: the sixth node sends a third configuration response message to the fifth node, which provides the fifth node with configuration information related to the data served by the relay node (the distributed unit part of the first node), in one embodiment, the configuration information can be obtained by the sixth node after it configures the backhaul link channel and transmission path for the data of the first node, and the message at least includes one of the following information:

[0690] Eighth user configuration information, which is for the user accessing the first node (the distributed unit part of the first node), and the information included in the information can refer to the above-mentioned "seventh user configuration information" Figure 10 ", specifically, at least one of the following information:

[0691] An identifier of a user, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID, In one embodiment, the information can contain identifiers of multiple users, then the information can include at least one of the following information:

[0692] gNB-CU UE F1AP ID

[0693] gNB-DU UE F1AP ID

[0694] C-RNTI

[0695] An identifier of a serving cell

[0696] UE XnAP ID1, In one embodiment, the ID is assigned by the fifth node and is obtained from step 3-1 above

[0697] UE XnAP ID2, In one embodiment, the ID is assigned by the sixth node

[0698] The above identifiers are only examples, and other identifiers are not excluded.

[0699] Information related to a radio bearer of a user, In one embodiment, the radio bearer can be admitted by the sixth node or not admitted by the sixth node; for a radio bearer (such as a data radio bearer DRB, a signaling radio bearer SRB), the information includes at least one of the following information:

[0700] An identifier of a user, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0701] An identifier of a radio bearer of a user, such as UE RB ID, the information can indicate a radio bearer of a specific user, in other words, the identifier information not only indicates a user, but also indicates a radio bearer of the user.

[0702] An identifier, such as DRB ID, SRB ID

[0703] information about the QoS that the sixth node can satisfy, in one embodiment, the information is the QoS that the sixth node can satisfy according to the condition of the network it serves; in another embodiment, the information is the QoS that the sixth node can satisfy after it configures the backhaul link channel and transmission path serving the radio bearer

[0704] tunnel-related information of the uplink data, the tunnel can be one or multiple, the information indicates the information on the side of 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 one tunnel, the information at least includes one of the following information:

[0705] tunnel identification information

[0706] IP address

[0707] TEID

[0708] routing identification information

[0709] identification information of the next hop node

[0710] identification information of the backhaul link channel

[0711] Some or all of the above information is configured by the sixth node, if the above information is also included in step 3-1, it can be different from the information contained in step 3-1

[0712] tunnel-related information of the downlink data, the tunnel can be one or multiple, the information indicates the information on the side of the relay node or the distributed unit part of the relay node, for one tunnel, the information at least includes one of the following information:

[0713] tunnel identification information

[0714] IP address

[0715] TEID

[0716] configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is sent through the above-mentioned tunnel)

[0717] Configuration value information of the flow label field in the downlink data packet (furthermore, the downlink data packet is sent through the above tunnel)

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

[0719] 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.

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

[0721] Tunnel identification information

[0722] IP address

[0723] TEID

[0724] The use of this information is Figure 11 The method of (c) is related to the following: 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, the sixth node may 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”.

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

[0726] Tunnel identification information

[0727] IP address

[0728] TEID

[0729] The use of this information is Figure 11The method of (c) is related to the fact that the first node sends the packet to the sixth node according to the address indicated by the information, and the sixth node, after receiving the packet, sends the packet to the fifth node, and before sending the packet, the sixth node may replace the information contained in the packet with the information contained in the "tunnel-related information of uplink data" described above, for example, replace the IP address in the packet with the IP address contained in the "tunnel-related information of uplink data" described above, so if the "second tunnel information" is contained, the fifth node will send the information to the first node.

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

[0731] The information sent by the first node to the fifth node, such as the F1AP message, in an embodiment, the information contains the IP packet of the F1AP message; the information can be the information sent by the first node to the sixth node

[0732] Control signaling type information, which indicates the type of the transmitted control signaling, which can be the "information sent by the first node to the fifth node" contained in the "second control signaling-related information" described above, or one or more control signaling transmitted between the first node and the fifth node; in an embodiment, the information can indicate control signaling type 1, control signaling type 2, etc., and different types 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 can indicate user-related control signaling (UE-associated signaling), or non-user-related control signaling (non-UE-associated signaling), etc.; further, the information contained in the "second control signaling-related information" described above is applicable to the control signaling type indicated by the "control signaling type information"

[0733] Destination address information of the received downlink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information on the first node side

[0734] Configuration value information of the DSCP field in the packet carrying the control signaling

[0735] Configuration value information of the flow label field in the packet carrying the control signaling

[0736] The destination address information of the received uplink control signaling, such as an IP address, a BAP address, and the like; further, the address information can be address information on the side of the fifth node

[0737] The identification information of the routing, 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), and includes 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); further, according to the information, the first node can add the information to the data packet carrying the control signaling

[0738] The identification information of the next hop node, which is the node directly receiving 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, and then the next hop node directly or indirectly (through other nodes) sends the control signaling to the destination node. According to the information, the first node knows to which node to send the control signaling

[0739] The identification information of the backhaul link channel, which is the backhaul link channel used by the first node to send the control signaling to the above-mentioned next hop node. According to the information, the first node knows which backhaul link channel to use to send the control signaling

[0740] The eighth mapping relationship information, which reflects the mapping relationship before and after the update of the configuration information of the first node, and is used to update the configuration information used by the first node for data transmission. The content contained in the information can be referred to in the above-mentioned “ Figure 4 to Figure 10 ”, the new information in the information is the information required to be used after the update of the configuration of the first node, and the old information is the information used before the update of the configuration of the first node. The beneficial effect of the information is that the configuration information required for the first node to transmit the data (such as the data of different users, F1AP signaling, etc.) of the distribution unit part can be updated by using less signaling, without using multiple different signaling to update the configuration information required for the transmission of different data

[0741] In the above-mentioned process, after step 3-2, step 3-3 can also be included, 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 sending the received “tunnel related information of uplink data” to the first node for one radio bearer; the information sent to the first node in step 3-3 can be referred to the information received in step 3-2, which will not be described in detail here.

[0742] Before step 3-1, the above flow can also include step 3-0, i.e., a user data configuration interaction flow, in which the fifth node and the first node can interact the configuration information of the data served by the first node, such as the configuration information of the user radio bearer (see the above “ Figure 4 to Figure 10 ”).

[0743] The above flow can be performed for one user, or for multiple users, or for control signaling (i.e., the above step 3-1 and step 3-2 are used to transmit information related to control signaling, see the above first information related to control signaling and second information related to control signaling).

[0744] When the fifth node and the sixth node are two different nodes, the above flow can also include the following implementation:

[0745] The fifth node and the sixth node both serve the first node, such as two different anchor nodes, or the centralized units of two different anchor nodes. The first node (or the mobile terminal part of the first node, or the distributed unit part of the first node) can be served by the two nodes (in an embodiment, the mobile terminal part of the first node is configured with dual connectivity, connected to the fifth node and the sixth node respectively), for example, the data served by the distributed unit part of the first node can be served by the network controlled by the fifth node and / or the sixth node; further, the implementation can also include a seventh node (in an embodiment, the seventh node can also be a relay node), which accesses the network through the first node, and the seventh node can be directly connected to the first node, or 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 distributed unit part of the seventh node) can also be served by the network controlled by the fifth node and / or the sixth node. In this implementation, the interaction flow is as shown in Figure 12 .

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

[0747] The identification information of the first node, in an embodiment, the identification information is the identification information of the mobile terminal part of the first node, such as XnAP UE ID; in another embodiment, the identification information is the identification information of the distributed unit part of the first node, such as gNB-DU ID, BAP address, etc.

[0748] The seventh user configuration information is for the user accessing the first node (the distributed unit part of the first node) or the seventh node (the distributed unit part of the seventh node), and the distributed unit part of the first node or the distributed unit part of the seventh node. An advantage of sending the information to the sixth node is that the sixth node can obtain the configuration information of the user data, and the information contained in the information can be referred to in the above "Description of Embodiments" Figure 12 ", specifically, at least one of the following information:

[0749] The user identifier, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID. In an embodiment, the information can contain identifiers of multiple users, and the information can at least include one of the following information:

[0750] gNB-CU UE F1AP ID

[0751] gNB-DU UE F1AP ID

[0752] C-RNTI

[0753] The identifier of the serving cell

[0754] UE XnAP ID, in an embodiment, the ID is allocated by the fifth node

[0755] The above identifiers are only examples, and other identifiers are not excluded.

[0756] The information related to the user data, in an embodiment, the user data can be the data of one or more radio bearers. For a radio bearer (such as a data radio bearer DRB or a signaling radio bearer SRB), the radio bearer can be requested to be added, modified or deleted. Further, the user data can be the user data served by the first node (such as the data of the user accessing the first node, or the data generated by the first node itself, or the data generated by the distributed unit part of the first node). In addition, the user data can be uplink data, downlink data, or uplink and downlink data. The information at least includes one of the following information:

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

[0758] Information about the QoS of user data, including configuration information of QoS parameters of user data; the content of this configuration information can be found in the above-mentioned “Information about the Quality of Service (QoS) of Radio Bearers”. In one embodiment, this information is the actual QoS information of 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 user data”. Furthermore, the user data can be one or more radio bearers.

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

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

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

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

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

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

[0765] Non-F1 interface data, such as non-F1 data

[0766] BAP layer control data, such as BAP Control PDU

[0767] Information related to the address, in one embodiment, is address association information, which includes IP address information and / or port information. Further, the information is used to serve the control plane data.

[0768] 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

[0769] First data routing related information, the information 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 is the BAP address of the destination receiving node), further, the BAP routing identification information is the information used when transmitting downlink data and / or uplink data. In addition, the information can be the information configured by the fifth node, further, is the information configured by the fifth node for the sixth node to use

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

[0771] User radio bearer identification information, such as UE RB ID, the 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

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

[0773] Downlink data tunnel related information, the tunnel can be one or more, the information indicates the information of the relay node or the distributed unit part of the relay node, in one embodiment, the relay node can be the first node, in another embodiment, the relay node can be the seventh node, for one tunnel, the information at least includes one of the following information:

[0774] Tunnel identification information

[0775] IP address

[0776] TEID

[0777] Configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is transmitted through the above-mentioned tunnel)

[0778] Configuration value information of the flow label field in the downlink data packet (further, the downlink data packet is sent through the tunnel)

[0779] Tunnel-related information of the uplink data, which can be one or multiple, indicating the information on the side of the anchor node (or the centralized unit of the anchor node or the user plane part of the centralized unit of the anchor node), in one embodiment, the anchor node is the fifth node, in another embodiment, the anchor node is the sixth node; for one tunnel, the information at least includes one of the following information:

[0780] Tunnel identification information

[0781] IP address

[0782] TEID

[0783] Routing identification information, which is used to indicate the transmission path of the uplink data (further, the uplink data is sent through the tunnel), including address information (BAP address) of the receiving node and / or transmission path identification information (path ID), further, according to the information, the relay node can add the information to the uplink data packet sent through the tunnel

[0784] Identification information of the next hop node, which is the node directly receiving the uplink data (further, the uplink data is sent through the tunnel) when the relay node sends the uplink data, in other words, the relay node sends the uplink data to the next hop node, and then the next hop node directly or indirectly (through other nodes) sends the uplink data to the destination node of the uplink data. According to the information, the relay node knows to which node to send the uplink data

[0785] Identification information of the backhaul link channel, which is the backhaul link channel used by the relay node to send the uplink data (further, the uplink data is sent through the tunnel) to the next hop node. According to the information, the relay node knows which backhaul link channel to send the uplink data

[0786] Step 3-2: the sixth node sends a third configuration response message to the fifth node, which provides the fifth node with configuration information related to the data served by the relay node (the distributed unit part of the first node, or the distributed unit part of the seventh node), in one embodiment, the configuration information can be obtained by the sixth node after it configures the backhaul link channel and transmission path for the data of the first node (or the data of the seventh node), and the message at least includes one of the following information:

[0787] identification information of the first node, in one embodiment, the identification information is the identification information of the mobile terminal part of the first node, such as XnAP UE ID; in another embodiment, the identification information is the identification information of the distributed unit part of the first node, such as gNB-DU ID, BAP address, etc.

[0788] eighth user configuration information, which is for the user accessing the first node (the distributed unit part of the first node) or the seventh node (the distributed unit part of the seventh node), and can be the distributed unit part of the first node or the distributed unit part of the seventh node, and the information contained in the information can be referred to the above "user configuration information", and specifically, at least includes one of the following information: Figure 4 to Figure 10

[0789] identification of the user, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID, in one embodiment, the information can contain the identification of multiple users, then the information can at least include one of the following information:

[0790] gNB-CU UE F1AP ID

[0791] gNB-DU UE F1AP ID

[0792] C-RNTI

[0793] identification of the serving cell

[0794] UE XnAP ID1, in one embodiment, the ID is allocated by the fifth node, and is obtained from the above step 3-1

[0795] UE XnAP ID2, in one embodiment, the ID is allocated by the sixth node

[0796] ​The above-mentioned identifiers are only examples, and other identifiers can be included.

[0797] Information about user data, in one embodiment, the user data can be data of one or more radio bearers, and the data can be user data that the sixth node is able to serve or user data that the sixth node is not able to serve. Further, the user data can be user data that the first node serves (e.g., data of users accessing the first node, or data generated by the first node itself, or data generated by a distributed unit part of the first node). In addition, the data can be uplink data, or downlink data, or both uplink and downlink data. The information includes at least one of the following:

[0798] Identifier information of the user data, which is used to identify a type of data, such as trafficprofile ID, traffic ID

[0799] Configuration information related to the downlink data packet, which is used to indicate configuration information needed when downlink data transmission is performed, and the information includes at least one of the following:

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

[0801] Configuration value information of the flow label field of the downlink data packet

[0802] second data routing related information, which indicates information required for transmitting the user data (e.g. information required to be carried in the data packet), in an embodiment, the information is BAP routing identification information (in an embodiment, the information includes BAP address information and / or path identification information, further, the BAP address information is a BAP address of a destination receiving node, e.g. a BAP address of the first node or the seventh node, or a BAP address of a non-destination receiving node, e.g. the first node when the data is transmitted to the seventh node), in addition, the information can be the "first data routing related information" received in step 3-1, or information set by the sixth node (e.g. information different from the "first data routing related information", for example, when the sixth node finds that the "first data routing related information" received in step 3-1 has been used by the sixth node for transmission of other data, the sixth node can provide an updated information to the fifth node, i.e. information different from the "first data routing related information"), further, when the fifth node receives the information, the information can be used to configure transmission of the data, e.g. configure transmission of the user data at the first node

[0803] receiving configuration information of the user data, the configuration information is used to indicate configuration information used by the relay node when receiving the user data, in an embodiment, the relay node can be the first node, then the information can be used by the fifth node to configure the first node, the information at least includes one of the following information:

[0804] indication information of a cell group, which is used to indicate a cell group required for receiving the user data, e.g. MCG, SCG, Cell Group ID, in an embodiment, the information can indicate a cell group required for the first node to receive the user data

[0805] identification information of a prior-hop, e.g. gNB-ID, identification information of a cell group, BAP address information, in an embodiment, the prior-hop is a node transmitting data to the first node

[0806] identification information of a backhaul link channel (ingress BH RLC channel) receiving the data, in an embodiment, the backhaul link channel can be a backhaul link channel receiving the data by the first node

[0807] configuration information related to the uplink data packet, which is used to indicate configuration information required for transmitting the uplink data, the information at least includes one of the following information:

[0808] Third data routing related information, which indicates information required to be carried in a data packet when transmitting user 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 can be a BAP address of a 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

[0809] Configuration information for transmitting user data, which is used to indicate the configuration information used by the relay node when transmitting user data, in one embodiment, the relay node can be the first node, and the information can be used by the fifth node to configure the first node, and the information at least includes one of the following information:

[0810] Indication information of a cell group, which is used to indicate a cell group required for transmitting user data, such as MCG, SCG, Cell Group ID, in one embodiment, the information can indicate a cell group required for the first node to transmit user data

[0811] Identification information of a next-hop node (next-hop), such as gNB-ID, identification information of a cell group, BAP address information, in one embodiment, the next-hop node is a node receiving data transmitted by the first node

[0812] Identification information of a backhaul link channel (egress BH RLC channel) used for transmitting data, in one embodiment, the backhaul link channel can be a backhaul link channel used by the first node to transmit data

[0813] Identification of a user, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0814] Identification information of a user radio bearer, such as UE RB ID, which 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.

[0815] Identification information, such as DRB ID, SRB ID

[0816] information about the QoS that the sixth node can satisfy, in one embodiment, the information is the QoS that the sixth node can satisfy according to the condition of the network it serves; in another embodiment, the information is the QoS that the sixth node can satisfy after it configures the backhaul link channel and transmission path serving the radio bearer

[0817] tunnel-related information of the uplink data, the tunnel can be one or multiple, the information indicates the information on the side of 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 one tunnel, the information at least includes one of the following information:

[0818] tunnel identification information

[0819] IP address

[0820] TEID

[0821] routing identification information

[0822] identification information of the next hop node

[0823] identification information of the backhaul link channel

[0824] Some or all of the above information is configured by the sixth node, if the above information is also included in step 3-1, it can be different from the information contained in step 3-1.

[0825] tunnel-related information of the downlink data, the tunnel can be one or multiple, the information indicates the information on the side of the relay node or the distributed unit part of the relay node, for one tunnel, the information at least includes one of the following information:

[0826] tunnel identification information

[0827] IP address

[0828] TEID

[0829] configuration value information of the DSCP field in the downlink data packet (further, the downlink data packet is sent through the above-mentioned tunnel)

[0830] Configuration value information of the flow label field in the downlink data packet (further, the downlink data packet is sent through the above-mentioned tunnel)

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

[0832] After the fifth node receives the information, the fifth node can add the configuration value of the DSCP field and / or the configuration value of the flow label field in the relevant data packet sent to the first node according to the information.

[0833] In the above-mentioned process, after step 3-2, step 3-3 can also be included, that is, the fifth node sends a fourth configuration request message to the first node, the message being used for configuring data sending and / or receiving at the first node, the data being possibly data of the first node (such as data of a user accessing the first node, or data of a distributed unit part 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 part of the seventh node), the message at least including one of the following information:

[0834] Indication information of a cell group, such as MCG, SCG, Cell Group ID, in an embodiment, the information being used for indicating a cell group (such as an ingress cell group) required by the first node to receive user data, the received data possibly also needing to be sent by the first node; in another embodiment, the information being used for indicating a cell group (such as an egress cell group) required by the first node to send user data

[0835] Identification information of a prior-hop, such as gNB-ID, identification information of a cell group, BAP address information, in an embodiment, the prior-hop being a node sending data to the first node, the data possibly also needing to be sent by the first node

[0836] Identification information of an ingress backhaul radio link control channel (ingress BH RLC channel) receiving data, in an embodiment, the backhaul link channel being a backhaul link channel used by the first node to receive data, the received data possibly also needing to be sent by the first node

[0837] Identification information of a next-hop, such as gNB-ID, identification information of a cell group, BAP address information, in an embodiment, the next-hop being a node receiving data sent by the first node

[0838] identification information of a backhaul link channel used for sending the data (egress BH RLC channel), in an embodiment, the backhaul link channel can be a backhaul link channel used by the first node for sending the data

[0839] route identification information contained in the received data, such as ingress BAP routing ID, in an embodiment, the information is BAP routing identification information (in an embodiment, the information includes BAP address information and / or path identification information, further, the BAP address information is a BAP address of a destination receiving node, such as a BAP address of the first node or the seventh node, or a BAP address of a distributed unit part of the fifth node or the sixth node, or a BAP address of a non-destination receiving node, such as the first node when the data is sent to the seventh node), in another embodiment, the information is the “second data route related information” in step 3-2 above

[0840] new routing identification information or routing identification information of the transmitted data, such as a new BAP routing ID or an egress BAP routing ID, which indicates routing identification information that the first node needs to add when transmitting 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, in an embodiment, the information is BAP routing identification information (in an embodiment, the information includes BAP address information and / or path identification information, further, the BAP address information is a BAP address of a destination receiving node, such as a BAP address of the first node or the seventh node, or a BAP address of a distributed unit part of the fifth node or the sixth node, or a BAP address of a non-destination receiving node, such as the first node when the data is transmitted to the seventh node). Further, the information can be used to update information in a received data packet by the first node, in an 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 "received data contained routing identification information" to the "new routing identification information", in another embodiment, the first node can update the routing identification information of a specific data (such as the data is transmitted by the cell group indicated by the "cell group indication information", and / or the data is transmitted by the node indicated by the "prior-hop identification information", and / or the data is received by the channel indicated by the "ingress BH RLC channel identification information") to the "new routing identification information", in another embodiment, the information can be the "first data routing related information" in the above step 3-1, in another embodiment, the information can be the "third data routing related information" in the above step 3-2

[0841] The third configuration request message and the third configuration response message in the above procedure can be UE-associated messages, or non-UE-associated messages, and can reuse existing messages of the Xn interface, such as the NG-RAN Node configuration update and NG-RAN node configuration update acknowledage messages in TS 38.423, or 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 can be for the mobile terminal part of the first node, or for the user accessing the first node or the seventh node), or can define new messages, such as the UE Bearer Context Setup / Modification Request and UE Bearer Context Setup / Modification Response messages (the new defined messages can 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.

[0842] The fourth configuration request message can be an RRC message (such as the RRCReconfiguration message), or an F1AP message (such as the BAP MAPPING CONFIGURATION message).

[0843] Further, when the above procedure is used to configure the sixth node to serve one or more users accessing the first node or the seventh node, the above procedure is different from the procedure of S-Node addition / modification on the existing Xn interface, which aims to add a secondary node for a user, or modify the configuration of the secondary node, but in the above procedure in the present application, the sixth node is not a secondary node of the user, the user is connected to the fifth node, and the sixth node only configures the backhaul link channel and transmission path used for the transmission of user data, and the sixth node does not configure the wireless bearer of the user.

[0844] The beneficial effects of the above process at least include: 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 time delay; when the relay node is connected to multiple anchor nodes, the user data can be transmitted through the multiple anchor nodes, the load of the relay node can be shared, and the data of the relay node can be transmitted in the network served by different anchor nodes.

[0845] The third aspect of the application further includes another process, i.e., a relay node configuration interaction process triggered by the sixth node, Figure 4 to Figure 10 Another example of the relay node configuration interaction process according to the embodiment of the application is shown in FIG. 6. As shown in the figure, the process includes the following steps: ​

[0846] 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 serving relay node to the fifth node, and the message at least includes one of the following information:

[0847] Eighth user configuration information, the information is for the user accessing the first node (the distributed unit part of the first node), and the information contained in the information can refer to the above-mentioned "user configuration information" ​ ", specifically, at least one of the following information:

[0848] User identifier, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID, in an embodiment, the information can contain the identifiers of multiple users, and the information can at least include one of the following information:

[0849] gNB-CU UE F1AP ID

[0850] gNB-DU UE F1AP ID

[0851] C-RNTI

[0852] Identifier of the serving cell

[0853] UE XnAP ID, in an embodiment, the ID is allocated by the fifth node

[0854] The above identifiers are only examples, and other identifiers are not excluded.

[0855] ​information related to a radio bearer of a user, for a radio bearer (such as a data radio bearer DRB, a signaling radio bearer SRB), the radio bearer can be requested to be modified, or can be requested to be deleted (if it is deleted, the fifth node can delete the radio bearer after receiving the information), the information at least includes one of the following information:

[0856] an identifier of the user, such as a gNB-CU / DU UE F1AP ID, a C-RNTI, a UE XnAP ID

[0857] identifier information of a radio bearer of the user, such as a UE RB ID, the information can indicate a radio bearer of a specific user, in other words, the identifier information not only indicates a user, but also indicates a radio bearer of the user

[0858] identifier information, such as a DRB ID, a SRB ID

[0859] information related to a QoS satisfied by the sixth node, the information is used to indicate information related to a QoS that can be satisfied by the sixth node when serving the radio bearer. The information has the beneficial effect that the node receiving the information can know the QoS that can be satisfied by the sixth node when serving the radio bearer of the user, and determine how to configure the first node to serve the radio bearer of the user

[0860] information related to a tunnel of uplink data, the tunnel can be one or multiple, the information indicates information on the side of the anchor node (or the centralized unit of the anchor node or the user plane part of the centralized unit of the anchor node), and for a tunnel, the information at least includes one of the following information: tunnel identifier information, an IP address, a TEID, routing identifier information, identifier information of a next hop node, identifier information of a backhaul link channel, etc.

[0861] information related to a tunnel of downlink data, the tunnel can be one or multiple, the information indicates information on the side of the relay node or the distributed unit part of the relay node, and for a tunnel, the information at least includes one of the following information: tunnel identifier information, an IP address, a TEID, configuration value information of a DSCP field, configuration value information of a flow label field

[0862] reason information, the information indicates a reason for modifying or deleting the radio bearer, such as resource limitation, etc.

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

[0864] Tunnel identification information

[0865] IP address

[0866] TEID

[0867] The use of this information is ​ The method of (c) is related to the following: 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, the sixth node may 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”.

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

[0869] Tunnel identification information

[0870] IP address

[0871] TEID

[0872] The use of this information is ​ The method of (c) is related to that 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-mentioned "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-mentioned "information related to the tunnel of uplink data". Therefore, if the above-mentioned "second tunnel information" is included, the fifth node will send the information to the first node.

[0873] The third control signaling-related information is used to provide information related to control signaling or control signaling transmission, and includes at least one of the following information:

[0874] The information sent by the first node to the fifth node, such as the F1AP message, in one embodiment, contains the IP packet of the F1AP message; the information can be the information sent by the first node to the sixth node

[0875] Control signaling type information, which indicates the type of the transmitted control signaling, which can be the information sent by the first node to the fifth node contained in the above-mentioned "third control signaling related information", or one or more control signaling transmitted between the first node and the fifth node; in one embodiment, the information can indicate control signaling type 1, control signaling type 2, etc., and different types 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 can indicate user-related control signaling (UE-associated signaling), or non-user-related control signaling (non-UE-associated signaling), etc.; further, the information contained in the above-mentioned "third control signaling related information" is applicable to the control signaling type indicated by the "control signaling type information"

[0876] Destination address information of the received downlink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information on the first node side

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

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

[0879] Destination address information of the received uplink control signaling, such as IP address, BAP address, etc.; further, the address information can be the address information on the fifth node side

[0880] Routing 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), which includes 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), further, according to the information, the first node can add the information to the data packet carrying the control signaling

[0881] Identity information of the next hop node, which is the node directly receiving 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, and then the next hop node sends the control signaling to the destination node directly or indirectly (through other nodes). According to this information, the first node knows to which node to send the control signaling

[0882] Identity information of the backhaul link channel, which is the backhaul link channel used by the first node to send the control signaling to the above-mentioned next hop node. According to this information, the first node knows which backhaul link channel to send the control signaling

[0883]

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

[0885] Ninth user configuration information, which is for the user accessing the first node (the distributed unit part of the first node), and the information contained in the information can be referred to the above-mentioned “ ​ ”, Specifically, at least one of the following information:

[0886] Identity of the user, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID, In an embodiment, the information can contain the identity of multiple users, then the information can at least include one of the following information:

[0887] gNB-CU UE F1AP ID

[0888] gNB-DU UE F1AP ID

[0889] C-RNTI

[0890] Identity of the serving cell

[0891] UE XnAP ID, In an embodiment, the ID is allocated by the fifth node

[0892] The above-mentioned identity is only an example, and other identities are not excluded.

[0893] User's radio bearer related information, for a radio bearer (e.g. data radio bearer DRB, signaling radio bearer SRB), the information can be used to indicate whether the fifth node accepts the request to modify or delete the radio bearer in step 4-1 above, the information includes at least one of the following information:

[0894] User's identity, such as gNB-CU / DU UE F1AP ID, C-RNTI, UE XnAP ID

[0895] User's radio bearer's identity information, such as UE RB ID, the information can indicate a radio bearer of a specific user, in other words, the identity information not only indicates a user, but also indicates a radio bearer of the user.

[0896] Identity information, such as DRB ID, SRB ID

[0897] Cause information, the information indicates the reason for modifying or deleting the radio bearer, such as resource limitation, etc.

[0898] Fourth control signaling related information, the information is used to provide information related to control signaling or control signaling transmission, the information includes at least one of the following information:

[0899] Information sent by the fifth node to the first node, such as F1AP message, in an embodiment, the information contains IP packet of F1AP message; after receiving the information, the sixth node will send the received information to the first node

[0900] Control signaling type information, the information indicates the type of the transmitted control signaling, the transmitted control signaling can be the "information sent by the fifth node to the first node" contained in the above-mentioned "fourth control signaling related information", or one or more control signaling transmitted between the fifth node and the first node; in an embodiment, the information can indicate control signaling type 1, control signaling type 2, etc., and different types 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 can indicate user-related control signaling (UE-associated signaling), or non-user-related control signaling (non-UE-associated signaling), etc.; further, the information contained in the above-mentioned "fourth control signaling related information" is applicable to the control signaling type indicated by the "control signaling type information"

[0901] receiving 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

[0902] receiving 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

[0903] In the above flow, after step 4-2, step 4-3 can also be included, i.e., 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, such as for a radio bearer, sending the received "tunnel related information of uplink data" to the first node; the information sent to the first node in step 4-3 can refer to the information received in step 4-1 above, which will not be described in detail here.

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

[0905] The third configuration request message and the third configuration response message in the above flow can be user-related (UE-associated) messages, or non-user-related (non-UE-associated) messages, which can reuse existing Xn interface messages, such as NG-RAN Node configuration update and NG-RAN node configuration update acknowledgement messages in TS 38.423, or define new messages, such as UE Bearer Context Modification Required Message and UE Bearer Context Modification Confirm messages, or other messages.

[0906] The above procedure is different from the procedure of the S-Node modification required message on the existing Xn interface, which is intended to modify the configuration of the secondary node, but in the above procedure of the present application, the sixth node is not the secondary node of the user, the user is connected to the fifth node, and the sixth node only configures the backhaul link channel and transmission path used for user data transmission, and the sixth node does not configure the wireless bearer of the user.

[0907] The beneficial effects of the above procedure are:

[0908] 1. The relevant configuration information of 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 for the data served by the relay node, facilitate the transmission of the data of the relay node through the network controlled by other anchor nodes, and reduce the load of the network served by the anchor node connected to the relay node.

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

[0910] 3. The data of the first node can be transmitted to the fifth node through the centralized unit of the sixth node, and the data of the fifth node can be transmitted to the first node through the centralized unit of the sixth node; or the data of the first node can be transmitted to the fifth node through the distributed unit of the sixth node, and the data of the fifth node can be transmitted to the first node through the distributed unit of the sixth node, which can avoid migrating the distributed unit of the relay node, reduce the signaling overhead in the migration process of the relay node, and accelerate the migration of the relay node.

[0911] The three aspects of the present application can also be combined with each other, and the following embodiments are given to illustrate:

[0912] Embodiment 4-1 (combination of the first aspect and the second aspect to obtain the migration and configuration update procedure of the relay node), ​ For the example of the migration and configuration update procedure of the relay node according to the embodiment of the present application. As shown in ​ The procedure includes the following steps:

[0913] 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 application;

[0914] 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 application;

[0915] 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 application;

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

[0917] 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 application;

[0918] 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 application.

[0919] Embodiment 4-2 (migration and configuration interaction procedure of relay node obtained by combination of the first aspect and the third aspect), ​ is an example of the migration and configuration interaction procedure of relay node according to an embodiment of the application. As shown in ​ , the procedure includes the following steps:

[0920] 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 application;

[0921] 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 application;

[0922] 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 application;

[0923] Step 4-2-4: The first node sends a migration configuration complete message to the third node, see step 1-4 of the first aspect of the application;

[0924] 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 application;

[0925] 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 application.

[0926] Embodiment 4-3 (migration and configuration interaction procedure of relay node obtained by combination of the first aspect and the third aspect), ​ is another example of the migration and configuration interaction procedure of relay node according to an embodiment of the application. As shown in ​ , the procedure includes the following steps:

[0927] 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 application;

[0928] 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 application;

[0929] 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 application;

[0930] Step 4-3-4: The first node sends a migration configuration complete message to the third node, see step 1-4 of the first aspect of the application;

[0931] 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 application;

[0932] 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 application.

[0933] d. Effects of the application

[0934] Based on the content of the first aspect of the application, the beneficial effects are at least:

[0935] 1. The migration of the relay node between different anchor nodes is completed, such as the handover of the mobile terminal part of the relay node between different anchor nodes, and the migration of the users served by the distributed unit part of the relay node between different anchor nodes. Unlike traditional technologies, the handover of each user in traditional technologies needs to perform a handover process individually, but the above process can complete the handover of multiple users at the same time;

[0936] 2. During the migration of the relay node, the configuration information of the data required to be transmitted by the distributed unit part of the relay node needs to be updated. According to the above process, the signaling required for updating the configuration information can be effectively reduced. For example, the mapping-related information exchanged in the above process can help the receiving node to update multiple configurations at the same time (such as updating the data transmission configuration of different users at the same time, or updating the signaling transmission configuration at the same time, or updating the data transmission and signaling transmission configurations of different users at the same time), thereby saving signaling overhead;

[0937] 3. The connection between the distributed unit part of the relay node and the centralized unit of the source anchor node is maintained, which reduces the configuration update of the users accessing the relay node and saves signaling overhead.

[0938] Based on the content of the second aspect of the application, the beneficial effects are at least:

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

[0940] Based on the summary of the third aspect, the beneficial effects are at least:

[0941] 1. The configuration information related to the data served by the interactive relay node can help the anchor node (the sixth node described above) to configure the backhaul link channel and transmission path required to serve the relay node, facilitate the transmission of the data of the relay node through the network controlled by other anchor nodes, and reduce the load of the network served by the anchor node connected to the relay node.

[0942] 2. The configuration information related to the data served by the interactive relay node can help the anchor node connected to the relay node to configure the transmission of data, such as determining the information required 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 required to be included in the uplink data packet (such as the routing identification information), configuring the transmission of the uplink data packet, such as determining the next hop node and determining the backhaul link channel to be used.

[0943] 3. The data of the first node can be transmitted to the fifth node through the centralized unit of the sixth node, and the data of the fifth node can be transmitted to the first node through the centralized unit of the sixth node; or the data of the first node can be transmitted to the fifth node through the distribution unit of the sixth node, and the data of the fifth node can be transmitted to the first node through the distribution unit of the sixth node, which can avoid the migration of part of the distribution unit of the relay node, reduce the signaling overhead in the migration process of the relay node, and accelerate the migration of the relay node.

[0944] ​ is a block diagram of an anchor node according to an embodiment of the application.

[0945] Reference ​ The anchor node 1100 includes a transceiver 1110, a controller 1120, and a memory 1130. Under the control of the controller 1120 (which can be implemented as a processor), the anchor node 1100 (including the transceiver 1110 and the memory 1130) is configured to perform ​The operations of the anchor node in the illustrated flow or described above, including but 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 transmit and receive signals to and from other network entities, such as another anchor node, a relay node and / or a UE, etc. 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 implementing ​ The operations of the anchor node in the illustrated flow or described above.

[0946] ​ is a block diagram of a relay node according to an embodiment of the present application.

[0947] Reference is made to ​ 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 perform ​ The operations of the relay node in the illustrated flow or described 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 transmit and receive signals to and from other network entities, such as an anchor node, another relay node and / or a UE, etc. 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 implementing ​ The operations of the relay node in the illustrated flow or described above.

[0948] Those skilled in the art can appreciate that the present application can be implemented in other specific forms without changing the technical idea or essential characteristics of the present application. Therefore, it should be understood that the above embodiments are merely examples and are not limiting. The scope of the present application is defined by the appended claims, not 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 application.

[0949] In the above-described embodiments of the present application, all operations and messages can be selectively performed or can be omitted. Also, the operations in each embodiment need not be performed sequentially, and the order of the operations can be changed. The messages need not be delivered in order, and the delivery order of the messages can be changed. Each operation and each message delivery can be independently performed.

[0950] While the present application 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 can be made therein without departing from the spirit and scope of the application as defined by the appended claims and their equivalents.

Claims

1. A method performed by an anchor node in a wireless communication system, comprising: transmitting, to a relay node, a request message for a configuration update related to the anchor node and the relay node; and receiving, from the relay node, a response message for the configuration update in response to the request message, wherein the request message includes uplink tunnel information and backhaul information, and wherein the backhaul information includes identification information of a next hop node, the identification information of the next hop node including backhaul adaptation protocol (BAP) address information. 2.The method of claim 1, wherein the uplink tunnel information includes an internet protocol (IP) address and a tunnel endpoint identifier (TEID) between the anchor node and the relay node. wherein 3.The method of claim 1, wherein the backhaul information includes an identifier of a backhaul link channel related to the relay node and the next hop node. wherein 4.The method of claim 1, wherein the request message includes uplink tunnel address information of the anchor node, and wherein wherein the uplink tunnel address information includes a first IP address of the anchor node before the configuration update and a second IP address of the anchor node after the configuration update. 5.The method of claim 1, wherein the response message includes downlink tunnel address information, and wherein wherein the downlink tunnel address information includes a third IP address of the relay node before the configuration update and a fourth IP address of the relay node after the configuration update. 6.The method of claim 1, wherein the uplink tunnel information corresponds to a plurality of user equipments (UEs) connected to the relay node. wherein 7.A method performed by a relay node in a wireless communication system, comprising: receiving, from an anchor node, a request message for a configuration update related to the anchor node and the relay node; and transmitting, to the anchor node, a response message for the configuration update in response to the request message, wherein the request message includes uplink tunnel information and backhaul information, and wherein the backhaul information includes identification information of a next hop node, the identification information of the next hop node including backhaul adaptation protocol (BAP) address information. 8.The method of claim 7, wherein the uplink tunnel information includes an internet protocol (IP) address and a tunnel endpoint identifier (TEID) between the anchor node and the relay node. 9.The method of claim 7, wherein wherein the backhaul information includes an identifier of a backhaul link channel related to the relay node and the next hop node. 10.The method of claim 7, wherein, wherein the request message includes uplink tunnel address information of the anchor node, and wherein the uplink tunnel address information includes a first IP address of the anchor node before the configuration update and a second IP address of the anchor node after the configuration update. wherein 11.The method of claim 7, wherein the response message includes downlink tunnel address information, and wherein the downlink tunnel address information includes a third IP address of the relay node before the configuration update and a fourth IP address of the relay node after the configuration update. wherein, 12.The method of claim 7, wherein the uplink tunnel information corresponds to a plurality of user equipments (UEs) connected to the relay node. 13.An anchor node in a wireless communication system, comprising: wherein a transceiver; ​ ​ at least one processor communicatively coupled to the transceiver; and a memory communicatively coupled to the at least one processor storing instructions executable by the at least one processor, individually or in any combination, to cause the anchor node to: send, to a relay node, a request message for a configuration update related to the anchor node and the relay node, and receive, from the relay node, a response message for the configuration update in response to the request message, wherein the request message comprises uplink tunnel information and backhaul information, and wherein the backhaul information comprises identification information of a next-hop node, the identification information of the next-hop node comprising backhaul adaptation protocol (BAP) address information.

14. The anchor node of claim 13, wherein the uplink tunnel information comprises an internet protocol (IP) address and a tunnel endpoint identifier (TEID) between the anchor node and the relay node.

15. The anchor node of claim 13, wherein the backhaul information comprises an identifier of a backhaul link channel related to the relay node and the next-hop node.

16. The anchor node of claim 13, wherein the request message comprises uplink tunnel address information of the anchor node, and wherein the uplink tunnel address information comprises a first IP address of the anchor node before the configuration update and a second IP address of the anchor node after the configuration update.

17. The anchor node of claim 13, wherein, the response message comprises downlink tunnel address information, and wherein the downlink tunnel address information comprises a third IP address of the relay node before the configuration update and a fourth IP address of the relay node after the configuration update.

18. The anchor node of claim 13, wherein the uplink tunnel information corresponds to a plurality of user equipments (UEs) connected to the relay node.

19. A relay node in a wireless communication system, comprising: a transceiver; at least one processor communicatively coupled to the transceiver; and a memory communicatively coupled to the at least one processor storing instructions executable by the at least one processor, individually or in any combination, to cause the relay node to: receive, from an anchor node, a request message for a configuration update related to the anchor node and the relay node, and send, to the anchor node, a response message for the configuration update in response to the request message, wherein the request message comprises uplink tunnel information and backhaul information, and wherein the backhaul information comprises identification information of a next-hop node, the identification information of the next-hop node comprising backhaul adaptation protocol (BAP) address information.

20. The relay node of claim 19, wherein the uplink tunnel information comprises an internet protocol (IP) address and a tunnel endpoint identifier (TEID) between the anchor node and the relay node.

21. The relay node of claim 19, wherein the backhaul information comprises an identifier of a backhaul link channel related to the relay node and the next-hop node.

22. The relay node of claim 19, wherein the request message comprises uplink tunnel address information of the anchor node, and The uplink tunnel address information includes a first IP address of the anchor node before the configuration update and a second IP address of the anchor node after the configuration update.

23. The relay node of claim 19, wherein, The response message includes downlink tunnel address information, and The downlink tunnel address information includes a third IP address of the relay node before the configuration update and a fourth IP address of the relay node after the configuration update.

24. The relay node of claim 19, wherein, The uplink tunnel information corresponds to a plurality of user equipments (UEs) connected to the relay node.

Images