Information configuration method, information interaction method and address information updating method

By using signaling interaction and address information updates between network nodes, the problem of the IAB donor DU being unable to distinguish between user radio bearers and incomplete node information in the relay network was solved, thus enabling the correct transmission and routing of user data and reducing signaling overhead.

CN118921713APending Publication Date: 2024-11-08BEIJING SAMSUNG TELECOM R&D CENT +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411197074.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-09-25
Filing Date
2019-11-07
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In an IAB network, the IAB donor DU cannot distinguish between data packets carried by different users, and the nodes in the relay network cannot know the address information of the source sending node and the destination receiving node of the user data, which leads to an increase in signaling overhead.

Method used

Through signaling interaction between network nodes, the attribute indication information of user data is negotiated, and the relevant information of the source sending node and the destination receiving node of user data is exchanged. The address information of the relay node is updated to optimize the GTP-U tunnel and TNL association.

Benefits of technology

This solves the problem that the IAB donor DU cannot distinguish user radio bearers, reduces signaling overhead, and ensures that user data is correctly transmitted and routed in the relay network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921713A_ABST
    Figure CN118921713A_ABST
Patent Text Reader

Abstract

The invention provides an information configuration method, an information interaction method and an address information updating method, the method can be executed by a first node, and the method can comprise the following steps: sending a first configuration request message to a second node; and receiving a first configuration response message sent by the second node based on the first configuration request message. Through the scheme provided by the invention, the problem that the distribution unit of the anchor node cannot distinguish the data packets of different user radio bearers when the data packets received by the distribution unit of the anchor node from different nodes belong to different user radio bearers and have the same access relay node is solved.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with application number "201911083736.9", application date of November 7, 2019, and invention name of "Information configuration method, information interaction method, and address information updating method". Technical Field

[0002] The present application relates to the field of communication technology, and in particular, to an information configuration method, an information interaction method, and an address information updating method. Background Art

[0003] In the NR access (New Radio Access) network or 5G (5th-Generation) network, in order to extend the coverage of the network, the IAB (Integrated Access and Backhaul) project is proposed. The main purpose of this project is to build a multi-hop network architecture. Figure 1 A schematic architecture of a multi-hop network is shown. The figure provides a network architecture including an anchor node (IAB donor) and two relay nodes (IAB nodes). All users (i.e., user devices) ultimately communicate with the anchor node, wherein users N1~Nx communicate with the anchor node through relay node 2 and relay node 1, and users M1~My communicate with the anchor node through relay node 1.

[0004] The anchor node may be composed of an anchor node centralized unit (IAB-donor central unit, or IAB-donor-CU) and an anchor node distributed unit (IAB-donor distributed unit, or IAB-donor-DU), and the interface between the centralized unit and the distributed unit is an F1 interface (see 3GPP TS38.473). The centralized unit includes a protocol stack of a service control plane and a protocol stack of a service user plane, wherein the protocol stack of the service control plane includes a radio resource control (RRC) protocol layer and a packet data convergence protocol (PDCP) layer, and the protocol stack of the service user plane includes a service data adaptation protocol (SDAP) layer and a PDCP layer; the distributed unit includes a protocol stack of a service control plane and a protocol stack of a service user plane, both of which include a radio link control (RLC) protocol layer, a medium access control (MAC) protocol layer and a physical layer (PHY).

[0005] The relay node includes a mobile terminal part and a distribution unit part, wherein the mobile terminal part is used to communicate with the upper level node of the relay node (e.g., mobile terminal 1 is used to communicate with the anchor node or the distribution unit of the anchor node, and mobile terminal 2 is used to communicate with the distribution unit 1 of relay node 1), and the distribution unit part is used to communicate with the lower level node of the relay node (e.g., distribution unit 1 can be used to communicate with mobile terminal 2, and can also be used to communicate with users M1~My, and distribution unit 2 is used to communicate with users N1~Nx). The protocol stack used by the distribution unit part in the relay node when serving the lower level node can be a complete protocol stack, such as a protocol stack including RRC / PDCP / RLC / MAC / PHY used to serve the control plane, and a protocol stack including SDAP / PDCP / RLC / MAC / PHY used to serve the user plane; it can also be a protocol stack including some protocol layers, such as a protocol stack including RLC / MAC / PHY, or a protocol stack including some RLC, MAC and PHY. The protocol stack used by the mobile terminal part in the relay node when communicating with the upper-level node of the relay node can be a complete protocol stack, such as a protocol stack including RRC / PDCP / RLC / MAC / PHY used by the service control plane, and a protocol stack including SDAP / PDCP / RLC / MAC / PHY used by the service user plane; it can also be a protocol stack including some protocol layers, such as a protocol stack including RLC / MAC / PHY, or a protocol stack including part of RLC, MAC and PHY.

[0006] In the entire multi-hop network, Figure 1 In the multi-hop network shown in , the link between the distribution unit 1 and the mobile terminal 2 will be used to send data of users N1~Nx, and the link between the distribution unit of the anchor node and the mobile terminal 1 will be used to send data of users M1~My and users N1~Nx. Such links have a common feature, that is, the users served by the link access the network through another distribution unit (rather than the distribution unit at one end of the link), such as the users served by the link between the distribution unit of the anchor node and the mobile terminal 1 access the network through distribution units 1 and distribution units 2, and the link between distribution unit 1 and mobile terminal 2 is used to serve the users who access the network through distribution unit 2. In the embodiment of the present application, such a link is called a backhaul link.

[0007] In the LTE (Long Term Evolution) / NR network, user data is sent through a radio bearer (RB), which can be a data radio bearer (DRB) or a signaling radio bearer (SRB). Taking the data radio bearer (DRB) as an example, each user's data will be sent through one or more DRBs, and each DRB has corresponding QoS (Quality of Service) parameters. The IAB network will also use this method, but unlike the single-hop network, the user's DRB will be transmitted on the backhaul link. In order to realize the transmission of different DRBs for the same user or different DRBs for different users on the backhaul link, the concept of the backhaul channel is also defined accordingly. An example of a backhaul link channel is the backhaul link radio link control protocol layer channel, i.e., Backhaul RLC channel. The entities at both ends of this channel are served by RLC / MAC / PHY services. Furthermore, a new protocol layer may be defined above RLC (such as Backhual adaptation layer).

[0008] In order to realize the transmission of wireless bearer data in the multi-hop IAB network, Figure 2 A structural diagram of a protocol stack architecture is given. Figure 2The example of implementing the transmission of user plane data through two IAB nodes (IAB-node1 and IAB-node2 shown in the figure) is used for explanation: as shown in the figure, the UE in the figure is a user terminal device, the MT is a mobile terminal of the relay node, and the protocol stack used by the IAB node includes the RLC shown in the figure, Adapt (i.e., adaptation layer, such as backhaul adaptation layer) located above the RLC, IP (Internet Protocol), IPsec (security-related protocol), UDP (User Datagram Protocol, user datagram protocol), and GTP-U (GPRS Tunnel Protocol User, GPRS tunnel transmission protocol-user plane, i.e., GPRS tunnel protocol at the user level); the protocol stack used by the CU of the anchor node (i.e., IAB donor) includes IP, IPsec, UDP, GTP-U, PDCP, and SDAP, and the protocol stack used by the DU of the IAB donor includes RLC, Adapt, and IP. In the schematic diagram, the MAC layer (media access control layer) and the physical layer are also included under the RLC layer. Among them, the schematic diagram also includes Backhaul RLC channel (BH RLC channel shown in the figure), and the protocol layers serving the BH RLC channel include RLC and adaptation layer, as well as MAC layer and physical layer under the RLC layer. IP packets are data packets based on the fourth generation Internet Protocol (IPv4) or the sixth generation Internet Protocol (IPv6), IPsec is a security protocol that provides security guarantee for the transmission of user plane data (transmitted through the F1 user plane interface (F1*-U shown in the figure)), and PDCP and RLC are the protocol stacks adopted by data wireless bearers.

[0009] based on Figure 2 The protocol stack architecture shown in FIG. 1 considers the transmission of downlink data (sent from the IAB donor to the user). The data transmission process is divided into two parts. The first part is the data transmission from the IAB donor to the IAB-node 2 (the IAB node is the user's accessing IAB node (accessing IAB node, access relay node), that is, the user accesses the network through the IAB node. The uplink data is directly sent to the IAB node, and then sent directly by the IAB node or via one or more IAB nodes to the IAB donor. The downlink data is sent directly by the IAB donor or via one or more IABnodes to the IAB node). The second part is the data transmission from the IAB-node 2 to the user. The second part can be sent using the existing air interface technology. The data transmission in the first part includes the following steps:

[0010] Step 1: The IAB donor CU sends data to the IAB donor DU (this example considers that the IAB donor node includes the CU and the DU. If the CU also includes a control plane entity (CU-CP) and a user plane entity (CU-UP), for user plane data, the data is sent from the CU-UP to the IAB donor DU. For control plane data, the data is sent from the CU-CP to the IAB donor DU).

[0011] Step 2: The IAB donor DU processes the received IP packet, which contains information about the radio bearer to which the user data belongs, such as the DSCP (Differentiated Service Code Point) or flow label field, which can be used to indicate the radio bearer to which the user data belongs, the address information of the destination receiving node (such as IP address), etc. Based on this information, the IAB donor DU can determine the user radio bearer to which the received IP packet belongs (i.e., which radio bearer the IP packet belongs to).

[0012] Step 3: The IAB donor DU determines the backhaul link channel used to transmit the received data packet according to the information of the user radio bearer to which the received data packet belongs. Specifically, the data packet received by the IAB donor DU needs to be sent to IAB node 1 via the backhaul link between it and IABnode 1. On the backhaul link, data belonging to different user radio bearers may be sent using different backhaul link channels. Therefore, in this step, the IAB donor DU determines the backhaul link channel to be used according to the user radio bearer to which the data packet belongs, and sends the data to IAB node 1 via the backhaul link channel;

[0013] Step 4: IAB node1 sends the received data to IAB node2 via a suitable backhaul link channel (the backhaul link channel is the backhaul link channel between IAB node1 and IAB node2).

[0014] Through the above four steps, user data can be sent from the IAB donor to the IAB node2. Among them, step 2 gives a key behavior, that is, the IAB donor DU needs to determine the user radio bearer to which the data packet belongs based on the information in the received IP data packet. Currently, when determining the user radio bearer to which the data packet belongs, the information considered is the DSCP or flow label field, and / or the address information of the destination receiving node (such as IP address). The user radio bearer represented by this information is configured to the IAB donor DU by the IAB donor CU (or IAB donor CU-CP). Specifically, the configuration information sent by the IABdonor CU (or IAB donor CU-CP) to the IAB donor DU includes:

[0015] ■ identification information of user radio bearers, such as identification information of radio bearers and / or identification information of users;

[0016] ■DSCP or flow label information;

[0017] ■The identification information of the destination receiving node, such as IAB node ID, IAB node DU ID, etc.;

[0018] ■ Address information of the destination receiving node, such as IP address and / or port information, newly defined address information, etc.

[0019] Based on the above configuration information, the IAB donor DU can determine the user radio bearer to which each IP packet it receives belongs. In the above configuration process, the DSCP or flow label setting for each user radio bearer is determined by the IABdonor CU (or IAB donor CU-CP). For data sent to the same access IAB node (that is, the access IAB node will send the received data directly to the user), if the data belongs to different user radio bearers, the DSCP or flow label value set by the IABdonor CU will be different.

[0020] In the prior art, the setting of DSCP or flow label in the data packet sent to the IAB donor DU is determined by the IAB donor CU, which means that if all data packets are sent to the IABdonor DU via the IAB donor CU, then the IAB donor CU can ensure that the DSCP or flow label values ​​contained in the data packets belonging to different user radio bearers are different. However, in an actual network, the data of the user's radio bearer may be sent to the IAB donor DU through different nodes. In one example, in a dual-connected network (the user is connected to two different base stations, such as base station 1 and base station 2), for the data packets of the same user, some may be sent from base station 1 to the user's access IAB node, and some may be sent from the IAB donor CU of base station 2 to the user's access IAB node. This will cause base station 1 and base station 2 to set the DSCP or flow label in the IP packets belonging to different user radio bearers to the same value, thereby causing the IAB donor DU to be unable to distinguish between different user radio bearers. Summary of the invention

[0021] The purpose of this application is to solve at least one of the defects of the prior art. The solution provided by the embodiment of this application is as follows:

[0022] In a first aspect, an embodiment of the present application provides an information configuration method, which is performed by a first node and includes:

[0023] Sending a first configuration request message to the second node, where the first configuration request message is used to request configuration of service user data;

[0024] A first configuration response message is received, which is sent by the second node based on the first configuration request message, where the first response message is used to respond to the configuration request in the first configuration request message.

[0025] In a second aspect, an embodiment of the present application provides an information configuration method, which is performed by a second node, and the method includes:

[0026] receiving a first configuration request message sent by the first node, where the first configuration request message is used to request configuration of service user data;

[0027] According to the first configuration request message, a first configuration response message is sent to the first node, where the first response message is used to respond to the configuration request in the first configuration request message.

[0028] In a third aspect, an embodiment of the present application provides an information interaction method, which is performed by a fifth node and includes:

[0029] A fourth configuration message is sent to the sixth node, where the fourth configuration message is used for the fifth node and the sixth node to exchange relevant information of a source sending node and / or relevant information of a destination receiving node of user data.

[0030] In a fourth aspect, an embodiment of the present application provides an information interaction method, which is performed by a sixth node and includes:

[0031] The fifth node sends a fourth configuration message, where the fourth configuration message is used for the fifth node and the sixth node to exchange relevant information of a source sending node and / or relevant information of a destination receiving node of user data.

[0032] In a fifth aspect, an embodiment of the present application provides a method for updating address information of a relay node, which method may include any of the following:

[0033] The CU of the anchor node sends a first address update message to the relay node or the DU of the relay node;

[0034] The DU of the anchor node sends an address update notification message to the CU of the anchor node;

[0035] The relay node or the DU of the relay node sends an address update request message to the CU of the anchor node.

[0036] In a sixth aspect, an embodiment of the present application provides a method for updating address information of a relay node, which method may include any of the following:

[0037] The relay node or the DU of the relay node receives a first address update message sent by the CU of the anchor node;

[0038] The CU of the anchor node receives the address update notification message sent by the DU of the anchor node;

[0039] The CU of the anchor node receives the address update request message sent by the relay node or the DU of the relay node.

[0040] In a seventh aspect, an embodiment of the present application provides an information configuration device, which is arranged in a first node, and includes a configuration request sending module and a configuration response receiving module, wherein:

[0041] A configuration request sending module, used to send a first configuration request message to the second node, where the first configuration request message is used to request configuration of service user data;

[0042] The configuration response receiving module is used to receive a first configuration response message sent by the second node based on the first configuration request message, where the first response message is used to respond to the configuration request in the first configuration request message.

[0043] In an eighth aspect, an embodiment of the present application provides an information configuration device, which is arranged in a second node, and includes a configuration request receiving module and a configuration response sending module, wherein:

[0044] A configuration request receiving module, used to receive a first configuration request message sent by a first node, where the first configuration request message is used to request configuration of service user data;

[0045] The configuration response sending module is used to send a first configuration response message to the first node according to the first configuration request message, where the first configuration response message is used to respond to the configuration request in the first configuration request message.

[0046] In a ninth aspect, an embodiment of the present application provides an information interaction device, which is arranged in a fifth node, and includes a configuration message sending module, which is used to:

[0047] A fourth configuration message is sent to the sixth node, where the fourth configuration message is used for the fifth node and the sixth node to exchange relevant information of a source sending node and / or relevant information of a destination receiving node of user data.

[0048] In a tenth aspect, an embodiment of the present application provides an information interaction device, which is arranged in a sixth node, and includes a configuration message receiving module, which is used to:

[0049] A fourth configuration message sent by the fifth node is received, where the fourth configuration message is used for the fifth node and the sixth node to exchange relevant information of a source sending node and / or relevant information of a destination receiving node of user data.

[0050] In an eleventh aspect, an embodiment of the present application provides an address information updating device of a relay node. If the device is set in a CU of an anchor node, the device includes an address update message sending module, and the address update message sending module is used to:

[0051] Sending a first address update message to the relay node or the DU of the relay node;

[0052] If the device is set in the DU of the anchor node, the device includes an address update notification module, and the address update notification module is used to:

[0053] Used to send an address update notification message to the CU of the anchor node;

[0054] If the device is set in a relay node or a DU of the relay node, the device includes an address update request module, and the address update request module is used to:

[0055] Send an address update request message to the CU of the anchor node.

[0056] In a twelfth aspect, an embodiment of the present application provides an address information updating device for a relay node. If the device is set in a relay node or a DU of a relay node, the device includes an address update message receiving module, and the address update message receiving module is used to:

[0057] Receiving a first address update message sent by the CU of the anchor node;

[0058] If the device is set in the CU of the anchor node, the device includes an address update notification receiving module, and the address update notification receiving module is used to:

[0059] Receive an address update notification message sent by the DU of the anchor node;

[0060] If the device is set in the CU of the anchor node, the device includes an address update request receiving module, and the address update request receiving module is used to:

[0061] Receive an address update request message sent by a relay node or a DU of the relay node.

[0062] In the thirteenth aspect, an embodiment of the present application provides an information interaction system, which includes at least one of the devices provided in aspects 7 to twelfth of the embodiments of the present application.

[0063] In a fourteenth aspect, an embodiment of the present application provides a communication network system, which includes the information interaction system provided in the twelfth aspect of the embodiment of the present application.

[0064] In the fifteenth aspect, an embodiment of the present application provides an electronic device, which includes a processor and a memory; wherein a computer program is stored in the memory; and the processor is used to execute the computer program to implement the method provided in any embodiment of the present application.

[0065] In the sixteenth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method provided by any embodiment of the present application is implemented.

[0066] The technical solution provided by this application brings the following beneficial effects:

[0067] Based on the information configuration method or device provided by the present application, the problem that the IAB donor DU cannot distinguish the data packets of different user radio bearers when the data packets received by the IAB donor DU from different nodes belong to different user radio bearers and have the same purpose receiving IAB node is solved;

[0068] Based on the information interaction method or device provided by the present application, the problem that each node serving user data in the relay network cannot obtain the address information of the source sending node and / or the address information of the destination receiving node of the user data is solved;

[0069] The method or device for updating the address information of the relay node provided in the present application solves the problem that when the address of the relay node of the service user changes, updating the GTP-U tunnel or TNL association of the service user will cause a large signaling overhead, and realizes the rapid update of the address information of the GTP-U tunnel and TNL association of the service user on the relay node side. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in describing the embodiments of the present application.

[0071] Figure 1 A schematic diagram of the structure of an IAB network architecture is shown;

[0072] Figure 2 A schematic diagram of a protocol stack architecture is shown;

[0073] Figure 3 An example diagram showing the association of a GTP-U tunnel with a TNL is shown;

[0074] Figure 4 A schematic diagram of a flow chart of an information configuration method provided in an embodiment of the present application is shown;

[0075] Figure 5a and Figure 5b A schematic diagram of a flow chart of an information configuration method provided in Example 1 of the present application is shown;

[0076] Figure 6 A schematic diagram of a flow chart of an information configuration method provided in Example 2 of the present application is shown;

[0077] Figure 7 A flow chart of an information configuration method provided in Example 3 of the present application is shown;

[0078] Figure 8a and Figure 8b A schematic diagram of a flow chart of an information configuration method provided in Example 4 of the present application is shown;

[0079] Fig. 9 A schematic diagram of a flow chart of an information interaction method provided in an embodiment of the present application is shown;

[0080] Fig.10 A flowchart of an address information updating method provided in Example 1 of the present application is shown;

[0081] Fig.11 A flow chart of an address information updating method provided in Example 2 of the present application is shown;

[0082] Fig.12 A flowchart of an address information updating method provided in Example 3 of the present application is shown;

[0083] Fig.13 A schematic diagram of the structure of an information configuration device provided by an embodiment of the present application is shown;

[0084] Fig.14 A schematic diagram showing the structure of an information configuration device provided by another embodiment of the present application is shown;

[0085] Fig.15 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0086] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present invention.

[0087] It will be understood by those skilled in the art that, unless expressly stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we refer to an element as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0088] In the present invention, the sequence number or serial number in the message name is used to indicate the name of the message, and does not represent the execution order.

[0089] In order to better illustrate the solution provided by the embodiment of the present application, the relevant technical terms involved in the embodiment of the present application are first briefly explained below.

[0090] ● Information related to user data attributes (such as Traffic profile (data stream (or transmission data stream) attributes), Data profile (data attributes), etc.) (i.e., information related to user data attributes, for the sake of description, this information can be referred to as information related to data attributes), which includes at least one of the following information:

[0091] ■Indication information of the radio bearer to which the user data belongs, that is, during the transmission of the user data, the indication information of the radio bearer to which the data packet corresponding to the user data belongs, that is, the indication information is used to indicate the radio bearer to which the user data packet belongs.

[0092] Among them, the indication information of the wireless bearer to which the user data belongs can be explicit indication information or implicit indication information. For example, it can be the identifier of the wireless bearer to which the user data belongs, such as DRB ID, SRB ID, etc., or it can be other indication information. For example, if the wireless bearer to which the user data packet belongs is DRB1 (that is, DRB ID=1), the indication information can be 5, and the wireless bearer to which the user data packet belongs is DRB2 (that is, DRB ID=2), the indication information can be 6. Then, if the indication information is 5, it represents DRB1, and if the indication information is 6, it represents DRB2.

[0093] ■Indication information of the user to which the user data belongs, that is, information used to indicate the source UE that sends the user data or the destination UE that receives the user data. The indication information is used to indicate the user to which the user data packet belongs.

[0094] Similarly, the indication information of the user to which the user data belongs can be explicit indication information or implicit indication information. For example, it can be identification information of the user to which the user data belongs, such as UE ID; wherein, for uplink data, the identification information can be identification information of the transmitting UE of the user data packet, i.e., the source UE; and for downlink data, the identification information can be identification information of the receiving UE of the user data packet, i.e., the destination UE; it can also be other indication information, such as if the user to which the user data packet belongs is UE 3 (i.e., UE ID is 3), the indication information can be 2, and if the user to which the user data packet belongs is UE 5 (i.e., UE ID is 5), the indication information can be 3, then the indication information 2 represents UE 3, and the indication information 3 represents UE 5.

[0095] ■Indication information indicating the user and radio bearer to which the user data belongs. The indication information can indicate the user and radio bearer to which the user data belongs. If the indication information is 1, it means that the user data belongs to radio bearer 2 of user 1. If the indication information is 2, it means that the user data belongs to radio bearer 6 of user 3.

[0096] That is, the user to which the user data belongs and the radio bearer to which the user data belongs may be indicated respectively by different information or simultaneously by one piece of information.

[0097] ■Indication information of a backhaul link channel used for transmitting user data, where the indication information can indicate the backhaul link used for sending user data (such as identification information of the backhaul link channel, logical channel identification information of the backhaul link channel).

[0098] ■Indication information of the type of user data, the types that can be indicated by the indication information include, DRB (indicating that the user data contained in the user data packet is the user plane data of the user), SRB (indicating that the user data contained in the user data packet is the control plane data of the user), F1 signaling (information of the F1 interface), if the F1 signaling is divided into different types, the indication information can also be used to indicate different types of F1 signaling (such as F1 signaling associated with the user, F1 signaling not associated with the user, for F1 signaling associated with the user, the indication information can also be used to indicate that the type of F1 signaling is F1 signaling containing RRC messages carried by SRB0, and / or F1 signaling containing RRC messages carried by SRB1 The indication information may also be used to indicate the above-mentioned multiple F1 signaling types (such as the indicated F1 signaling type is "F1 signaling not associated with the user" and "F1 signaling associated with the user including the RRC message carried by SRB0", or "F1 signaling including the RRC message carried by SRB1" and "F1 signaling including the RRC message carried by SRB3", etc.). If the user data packet is further divided into a newly transmitted data packet and a retransmitted data packet, the indication information may also be used to indicate whether the user data packet is a newly transmitted data packet or a retransmitted data packet. The indication information may be displayed information or implicit information.

[0099] ■Relevant information of the target receiving node. In one embodiment, the target receiving node is an access relay node of the user. Further, the target receiving node is used to receive downlink data. In another embodiment, the target receiving node is a centralized unit of the anchor node. Further, the target receiving node is used to receive uplink data. In another embodiment, the target receiving node is a distributed unit of the anchor node. Further, the target receiving node can be used to receive uplink data or downlink data. The relevant information of the target receiving node includes at least one of the following information:

[0100] ■The identification information of the destination receiving node;

[0101] ■The address information of the destination receiving node, such as IP address, or newly defined address, etc.;

[0102] ■Port information of the destination receiving node;

[0103] ■TEID (Tunnel Endpoint ID) of the destination receiving node.

[0104] ■Relevant information of the source sending node, the source sending node may be a centralized unit of an anchor node, or other base stations, or centralized units of other base stations, or other network entities (such as OAM (Operation Administration and Maintenance)), or a user's access relay node. Further, the source sending node may be used to send uplink data or downlink data, and the relevant information may include at least one of the following information:

[0105] ■The identification information of the source sending node;

[0106] ■The address information of the source sending node, such as IP address, or newly defined address, etc.;

[0107] ■Port information of the source sending node;

[0108] ■TEID of the source sending node.

[0109] ■ Information about the user data transmission path, which indicates the path that the user data (it can be understood that the user data is transmitted in the form of data packets) travels from the distribution unit of the source sending node or anchor node to the destination receiving node (access relay node), or indicates the next hop node of the user data. This information includes at least the following information:

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

[0111] ■When data is transmitted in the path, the identification information and / or address information of the nodes passed in sequence. For example, if the nodes passed by a data packet containing user data in sequence are node 1, node 2 and node 3, then the relevant information of the transmission path of the user data will include the identification information and / or address information of node 1, the identification information and / or address information of node 2, and the identification information and / or address information of node 3.

[0112] ■The identification information of the next hop node when data is transmitted on this path

[0113] Each data packet has information related to the corresponding user data packet attribute. If the information related to the user data packet attribute of the data packets is different, the data packets have different user data packet attributes.

[0114] ● User data attribute indication information (for the convenience of description, this information may be referred to as attribute indication information for short). This indication information will be included in each user data packet. Its function is to distinguish user data with different user data attributes. That is, if the indication information included in the received data packets is different, the information related to the user data attributes (see the above-mentioned "information related to user data attributes") corresponding to these data packets is also different. In other words, this indication information is used to represent the attributes (or attribute set) of the user data packet. If the indication information is different, the attributes of the user data packet are different.

[0115] For example, as an illustrative example, assume that the information about the attributes of a type of data packet is: DRB ID is 1, UE ID is 22, and the indication information of the type of user data is DRB, if the "attribute indication information of user data" representing the attributes of this type of data is 1; the information about the attributes of another type of data packet is: DRB ID is 5, UE ID is 22, and the indication information of the type of user data packet is DRB, if the "attribute indication information of user data" representing the attributes of this type of data packet is 2. The indication information 2 in this example represents that the attribute information of the data packet is: DRB ID is 5, UE ID is 22, and the type of user data is DRB. When transmitting a user data packet, if the attribute indication information of the user data contained in the data packet of the user received by a certain node is "1", then the attributes of the data packet are: DRB ID is 1, UE ID is 22, and the type of user data is DRB; if the attribute indication information of the user data contained in the data packet of the user received by a certain node is "2", then the attributes of the data packet are: DRB ID is 5, UE ID is 22, and the type of user data is DRB.

[0116] In one embodiment, the attribute indication information may be identification information indicating a backhaul link channel carrying user data (eg, BH RLC CH ID), or logical channel identification information indicating a backhaul link channel carrying user data (eg, BH RLC CH LCID).

[0117] In one embodiment, the attribute indication information may be a combination of one or more information included in the above-mentioned “information related to data attributes” indicated by it. In another embodiment, the attribute indication information of the user data may be partial content of an information included in the above-mentioned “information related to data attributes” indicated by it. In another embodiment, the attribute indication information of the user data may be redefined indication information indicating user data having different above-mentioned “information related to data attributes”.

[0118] In one embodiment, the attribute indication information may be included in the DSCP field of the IP packet (which may be the complete field of DSCP or a partial field of DSCP). In another embodiment, the indication information may be included in the flow label field of the IP packet (which may be the complete field of flow label or a partial field of flow label). In another embodiment, the indication information may be included in the DSCP+flow label field of the IP packet (which may be the complete field of DSCP+flowlabel or a partial field of DSCP+flow label). In another embodiment, the indication information may be included in other fields of the data packet, such as the header of the PDCP packet, the header of the RLC packet, the header of the adaptation layer, etc.

[0119] In one embodiment, the name used for the indication information in the message is DSCP; in another embodiment, the name used for the indication information in the message is flow label; the indication information may also be other names (such as traffic profile ID).

[0120] In one embodiment, the indication information may also be regarded as a part of the user data attributes, that is, the "attribute indication information of the user data" is one of the information included in the above-mentioned "information related to the user data attributes (such as Traffic profile, Data profile)".

[0121] For example, as an example, for user data carried by user radio bearer 1, the attribute indication information corresponding to the user data is 121. If a data packet includes the indication information 121, the data packet belongs to user radio bearer 1, that is, the user radio bearer used when transmitting the data packet is the user radio bearer corresponding to the identifier 1. In another embodiment, the attribute indication information can be combined with other information to jointly indicate the attribute to which the data packet containing this information belongs. Taking the use of the above-mentioned indication information to distinguish different user radio bearers as an example, the indication information can be combined with the information of the destination receiving node of the data packet (such as the identification information of the destination receiving node, the address information of the destination receiving node, and the destination receiving node can be an access IAB node) to indicate the user radio bearer to which the data packet belongs; the indication information can also be combined with the information of the sending node of the data packet (such as the identification information of the sending node, the address information of the sending node, and the sending node can be the source sending node of the data packet, such as a base station, a centralized unit of the base station, OAM, etc.) to indicate the user radio bearer to which the data packet belongs; the indication information can also be combined with the information of the destination receiving node and the sending node of the data packet (such as the identification information of the destination receiving node, the address information of the destination receiving node, the identification information of the sending node, the address information of the sending node, the destination receiving node can be an access IAB node, and the sending node can be the source sending node of the data packet, such as a base station, a centralized unit of the base station, OAM, etc.) to indicate the user radio bearer to which the data packet belongs.

[0122] ● Related information of the destination receiving node. In one embodiment, the destination receiving node is an access relay node of the user. Further, the destination receiving node is used to receive downlink data. In another embodiment, the destination receiving node is a centralized unit of the anchor node. Further, the destination receiving node is used to receive uplink data. In another embodiment, the destination receiving node is a distributed unit of the anchor node. Further, the destination receiving node can be used to receive uplink data or downlink data. The related information includes at least one of the following information:

[0123] ■The identification information of the destination receiving node;

[0124] ■ Address information of the destination receiving node, such as IP address, and / or newly defined address, etc.;

[0125] ■Port information of the destination receiving node;

[0126] ■TEID (Tunnel Endpoint ID) of the destination receiving node.

[0127] ●Relevant information of the source sending node, the source sending node may be a centralized unit of an anchor node, or other base stations, or centralized units of other base stations, or other network entities (such as OAM), or an access relay node of a user. Further, the source sending node may be used to send uplink data or downlink data, and the relevant information may include at least one of the following information:

[0128] ■The identification information of the source sending node;

[0129] ■ Address information of the source sending node, such as IP address, and / or newly defined address, etc.;

[0130] ■Port information of the source sending node;

[0131] ■TEID of the source sending node.

[0132] ● Information about the user data transmission path, which indicates the path that the user data (it can be understood that the user data is transmitted in the form of data packets) travels from the distribution unit of the source sending node or anchor node to the destination receiving node (access relay node), or indicates the next hop node on the path, and includes at least the following information:

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

[0134] ■The identification information and / or address information of the nodes that the data passes through in sequence when it is transmitted in the path. For example, if the nodes that a data packet containing user data passes through in sequence are node 1, node 2 and node 3, then the relevant information of the transmission path of the user data will include the identification information and / or address information of node 1, the identification information and / or address information of node 2, the identification information and / or address information of node 3, or the identification information and / or address information of the next hop node when the data is transmitted in the path.

[0135] The inventor of the present application has found that the current user data transmission scheme has at least the following problems:

[0136] First, when the IAB donor DU receives data packets from different nodes, different nodes may set the DSCP or flow label in the IP packets belonging to different user radio bearers to the same value, resulting in the IAB donor DU being unable to distinguish different user radio bearers.

[0137] Second aspect: Relay network (access relay node (i.e. the relay node accessed by the user, such as Figure 1 The network (such as the relay node 2) directly accessed by users N1~Nx in the network and the anchor node communicates through other relay nodes Figure 1In the communication between relay node 2 and anchor node directly through relay node 1), each node serving user data cannot obtain relevant information of the source sending node (such as address information, node identification information, and node port information) of the user data packet and relevant information of the destination receiving node (i.e., access relay node) (such as address information, node identification information, and node port information), which is not conducive to allocating attribute indication information to distinguish user data for user data packets.

[0138] Third aspect: When the address of the relay node serving the user changes, updating the GTP-U tunnel or TNL association of the serving user will cause a large signaling overhead. Specifically, in the relay network, the address information of the relay node will change. For example, if the relay node is connected to a new anchor node or a distribution unit of a new anchor node, this address change will cause the user data it serves to be unable to be correctly sent to the relay node. In the existing technology, such as Figure 3 As shown in , the transmission of user data is based on the GTP-U tunnel (tunnel) or TNL association (Transport network layer association) established between the centralized unit of the anchor node and the distributed unit of the relay node. Among them, the GTP-U tunnel is used for user data transmission, and different GTP-U tunnels will be used for different user data attributes (such as data carried by different user radio bearers). A GTP-U tunnel needs to be represented by the address information of the receiving end and / or the address information of the sending end, and the address information includes the IP address and TEID (Tunnel Endpoint identifier). TNL association is used for the transmission of control plane data, and TNL association also needs to be represented by the address information of the receiving end and / or the address information of the sending end, and the address information includes the IP address and / or the port number, such as Figure 3 As shown. It can be seen that the GTP-U tunnel and TNL association are both related to the address information of the relay node (or the distribution unit of the relay node). Therefore, when the address information of the relay node (or the distribution unit of the relay node) changes, the GTP-U tunnel or TNL association used to send user data is no longer available. It is necessary to update the information of the GTP-U tunnel or TNL association on the relay node (or the distribution unit of the relay node) side in order to continue to serve the user. However, this requires that the GTP-U tunnel or each TNL association of each wireless bearer of each user be updated separately, which results in a large signaling overhead. In addition, in the existing mechanism, the relay node is not allowed to initiate a request to update, add, and delete the address information, so that the relay node cannot adjust its address information.

[0139] In order to solve the above technical problems of the prior art, the embodiments of the present application provide an information configuration method, an information interaction method, and an address information updating method.

[0140] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems will be described in detail with reference to the accompanying drawings. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0141] In response to the above-mentioned first problem existing in the prior art, an embodiment of the present application provides an information configuration method, which configures different types of user data packets through signaling interaction between network nodes (the embodiment of the present application is described using the first node and the second node as examples), thereby helping the distribution unit of the anchor node to distinguish different user data types.

[0142] For the information configuration method, the signaling interaction process involves the first node and the second node, and the first node is used as the execution subject of the method, such as Figure 4 As shown in , the method may include the following steps:

[0143] Step 1: Send a first configuration request message to the second node;

[0144] Step 2: Receive a first configuration response message sent by the second node based on the first configuration request message.

[0145] Among them, the first configuration request message is used to request the configuration of the service user data, and the first response message is used to respond to the configuration request in the first configuration request message, that is, the first configuration request message and the first configuration response message are used to negotiate the attribute indication information of the user data between the first node and the second node, and the first configuration response message is a confirmation of the message received in step 1. The indication information of the data attribute is the indication information that can distinguish data packets with different attributes. For a data packet, the relevant attributes of the data packet can be determined according to the indication information of the data attribute contained in it, and the type of the data packet can be uniquely determined according to the relevant attributes of the determined data packet, or according to the relevant attributes and other information of the data packet. In other words, based on the indication information negotiated by the first node and the second node, or based on the indication information and other information in the user data packet, the type of the user data packet (such as the radio bearer to which the user data packet belongs, the F1 signaling to which the user data packet belongs, etc.) can be uniquely determined.

[0146] Based on the scheme of the embodiment of the present application, the first node and the second node realize the negotiation and confirmation of the attribute indication information of the user data through the interaction of the first configuration request message and the first configuration response message. When the nodes in the network transmit the user data (i.e., the user data packet), based on the attribute indication information of the user data negotiated and confirmed in the interaction process, i.e., the attribute indication information, the attribute indication information can be configured, or the type of the user data packet can be determined according to the attribute indication information of the user data carried in the received data packet, or according to the indication information and other information carried in the data packet, or according to the determined type of the user data packet, the user radio bearer or the F1 signaling to which the data packet belongs can be determined, so as to select a suitable return link channel, etc.

[0147] It should be noted that the name of the message involved in the embodiment of the present application (including the above-mentioned user first configuration request message, the first configuration response message, and the messages involved later) is only one optional example, but not the only one. In practical applications, other message names may also be used, such as the message name of the above-mentioned first configuration request message. The message is used to identify the message initiated by the first node to the second node for negotiating and determining the attribute indication information of the user data, so that when the user data packet is transmitted, different types of user data packets can be uniquely distinguished based on the indication information, or based on the indication information and other information carried by the user data packet, that is, the type of a class of data packets can be uniquely determined, but its name is not unique.

[0148] In an optional embodiment of the present application, the first configuration request message carries relevant information of a user data packet that the first node expects or requests to be accepted by the second node, and the first configuration request message includes at least one of the following:

[0149] Information about the attributes of the data;

[0150] Attribute indication information;

[0151] Relevant information of the destination receiving node;

[0152] Relevant information of the source sending node;

[0153] Information about the user data transmission path.

[0154] The user data packet of the type targeted by the first configuration request message will be sent by other base stations (or centralized units of other base stations) or centralized units of anchor nodes and sent to the user's access relay node via the distributed units of the anchor nodes.

[0155] It should be noted that in the embodiment of the present application, other base stations refer to base stations other than the base stations to which the anchor nodes in the embodiment of the present application belong. For example, when the first node and the second node are anchor nodes or parts of anchor nodes (such as CUs of anchor nodes), the other base stations are other base stations of the base stations to which the anchor nodes belong. If only one of the first node and the second node is an anchor node or a part of an anchor node, the other base stations are also other base stations other than the base stations to which the first node or the second node belongs.

[0156] In an optional embodiment of the present application, the first configuration response message carries relevant information of the user data accepted by the second node, and the first configuration response message includes at least one of the following:

[0157] Information about the attributes of the data;

[0158] Attribute indication information;

[0159] Relevant information of the source sending node;

[0160] Relevant information of the destination receiving node;

[0161] Information about the user data transmission path.

[0162] It is understandable that, in actual applications, in order to implement the negotiation of attribute indication information of user data, at least one of the first configuration request message and the first configuration response message includes the attribute indication information of user data. In addition, the first configuration request message and the first configuration response message may not include the attribute indication information of user data at the same time. Of course, in some embodiments, they may also be included at the same time. For example, the first configuration request message carries indication information of the attributes of user data that the first node expects or requests to be accepted by the second node. The first configuration response message may include relevant information of the user data accepted by the second node in addition to the attribute indication information of the user data, such as relevant information of the user data packet accepted by the second node. Of course, in this example, the first configuration response message may also include indication information of the attributes of the user data accepted by the second node.

[0163] It should be noted that the user data accepted by the second node refers to one or some types of data that the second node agrees to serve, that is, the data packets with which attributes the second node agrees to serve. For example, the first configuration request message includes relevant information of two types of user data, specifically, the information related to the user data attributes listed in the previous example is: DRB ID is 1, UE ID is 22, the indication information of the type of user data is DRB, and the indication information of the data attribute is "1" for one type of data, and the information related to the user data attributes is: DRB ID is 5, UE ID is 22, the indication information of the type of user data is DRB, and the indication information of the data attribute is "2" for another type of data; if the information related to the attributes of the data that the second node agrees to serve in these two types of user data is: DRB ID is 1, UE ID is 22, and the indication information of the type of user data is DRB, then the first configuration response message can include information related to the attributes of the type of data agreed by the second node.

[0164] In an optional embodiment of the present application, the first node and the second node may include any of the following:

[0165] The first node is a CU of an anchor node, and the second node is a DU of an anchor node, another base station, or a CU of another base station;

[0166] The first node is a CU-CP of an anchor node, and the second node is a CU-UP of an anchor node, a DU of an anchor node, another base station, or a CU of another base station;

[0167] The first node is other base stations or CUs of other base stations, and the second node is the CU of the anchor node or the CU-CP of the anchor node.

[0168] That is to say, the first configuration request message sent by the first node to the second node may be sent by the centralized unit of the anchor node (or the CU-CP of the anchor node) to the distributed unit of the anchor node, or sent by the centralized unit of the anchor node (or the CU-CP of the anchor node) to other base stations (or centralized units of other base stations), or sent by other base stations (or centralized units of other base stations) to the centralized unit of the anchor node (or the CU-CP of the anchor node), or sent by the control plane part of the centralized unit of the anchor node to the user plane part of the centralized unit of the anchor node.

[0169] Correspondingly, the first configuration response message sent by the second node to the first node may be sent from the distribution unit of the anchor node to the centralized unit of the anchor node (or the CU-CP of the anchor node), or sent from other base stations (or the centralized unit of other base stations) to the centralized unit of the anchor node (or the CU-CP of the anchor node), or sent from the centralized unit of the anchor node (or the CU-CP / CU-UP of the anchor node) to other base stations (or the centralized units of other base stations), or sent from the user plane part of the centralized unit of the anchor node to the control plane part of the centralized unit of the anchor node.

[0170] In an optional embodiment of the present application, the attribute indication information of the user data is configured by any one or more of the following nodes:

[0171] CU of the anchor node;

[0172] CU-CP of anchor node;

[0173] CU-UP of anchor nodes;

[0174] DU of the anchor node;

[0175] Other base stations or CUs of other base stations;

[0176] The source sending node of user data.

[0177] That is, for user data of different users, the attribute indication information of the data may be initially generated by any one or more of the above network nodes. Figure 4 In the information configuration method shown in , in step 1, if the first configuration request message includes attribute indication information of user data, one implementation is that the information is generated, i.e. configured, by the first node, and another implementation is that the information is obtained by the first node from other nodes. Similarly, in step 2, if the first configuration response message includes attribute indication information of user data, one implementation is that the information is generated by the second node, and another implementation is that the information is obtained by the second node from other nodes.

[0178] Optionally, when the first configuration request message includes attribute indication information (configured by the first node or obtained from other nodes), the first configuration response message may include at least information related to user data attributes, so that the first node (such as a centralized unit of an anchor node) can know which attributes of user data are accepted by the distribution unit through this information.

[0179] In an optional embodiment of the present application, the information configuration method may further include:

[0180] receiving a second configuration request message sent by a third node, wherein the second configuration request message is used to request configuration of service user data;

[0181] Based on the second configuration request message, a second configuration response message is sent to the third node, where the second response message is used to respond to the configuration request in the second configuration request message.

[0182] It is understandable that the third node is a network node different from the first node and the second node. For example, in an optional manner, the first node may be a CU of an anchor node, the second node may be a DU of an anchor node, and the third node may be a CU of another base station or another base station.

[0183] That is to say, in actual applications, when the first node and the second node negotiate the attribute indication information of the user data, the first node and the third node may also negotiate the attribute indication information of the user data between them. Among them, the negotiation process between the first node and the second node (referred to as the first process for short) and the negotiation process between the first node and the third node (referred to as the second process for short) may be related or unrelated in time. For example, the second process may be before the first process, the second process and the first process may be performed alternately, or the second process may be after the first process.

[0184] As an example, assuming that the first node is the CU (or CU-CP) of the anchor node, and the second node is the DU (CU-UP) of the anchor node, when the above message interaction is performed between the CU (or CU-CP) of the anchor node itself and the DU (CU-UP), the CU (or CU-CP) of the anchor node can also negotiate the attribute indication information of the user data with other base stations (or CUs of other base stations). Other base stations (CUs of other base stations) obtain the attribute indication information of the user data that the DU can accommodate from the CU by sending the above configuration request information to the first node.

[0185] This is because, in an actual network, some data is sent by other base stations to the distribution unit of the anchor node. In order to include the attribute indication information of the user data in the data packet of these data, it is necessary to notify other base stations (CU of other base stations) so that other base stations (CU of other base stations) can add indication information to each data packet according to this configuration information. For example, when the attribute indication information of the user data is configured by the first node, the first node sends a first configuration request message to the second node so that when the data packet is transmitted, the distribution unit can obtain the attributes of the user data in the data packet according to the indication information contained in the data packet. The first node sends a second response message to other base stations so that other base stations can add attribute indication information to each data packet according to this configuration information.

[0186] Optionally, for one type of user data (such as the user data may be sent by other base stations to the distribution unit of the anchor node), the second configuration request message may include any one of the following information:

[0187] Information about the attributes of the data;

[0188] Relevant information of the source sending node;

[0189] Information about the destination receiving node.

[0190] Based on one or more of this information, other base stations (or CUs of other base stations) can inform the centralized unit (or CU-CP) of the anchor node that other base stations (or CUs of other base stations) request or expect to be served by the anchor node for user data with the user data attributes.

[0191] Optionally, for a type of user data (in one embodiment, the user data may be received by a centralized unit of an anchor node), the second configuration response message may include at least one of the following information:

[0192] Information about the attributes of the data;

[0193] Attribute indication information of user data;

[0194] Information about the destination receiving node.

[0195] The attribute indication information of the user data in the second configuration response message is used to inform other base stations (or CUs of other base stations) of the attribute indication information of the user data configured by the centralized unit (or CU-CP) of the anchor node, or the attribute indication information of the user data learned by the centralized unit (or CU-CP) of the anchor node from the distribution unit (or CU-UP, or other nodes) of the anchor node, or the attribute indication information of the user data received by the distribution unit (or CU-UP) of the anchor node learned by the centralized unit (or CU-CP) of the anchor node from the distribution unit (or CU-UP) of the anchor node. Through the information related to the attributes of the user data and / or the relevant information of the destination receiving node, it informs other base stations (or CUs of other base stations) of the relevant information of the user data targeted by the attribute indication information of the user data.

[0196] In an optional embodiment of the present application, receiving the second configuration request message may be before sending the first configuration request message to the second node, and the user data targeted by the first configuration request message is determined according to the user data targeted by the second configuration request message.

[0197] That is, when the first node sends the first configuration request message after receiving the second configuration request message, the user data requested by the first configuration request message may be determined according to the user data requested in the second configuration request message.

[0198] In an optional embodiment of the present application, if the attribute indication information of the user data is configured by the first node, sending the second configuration response message to the third node may be after receiving the first configuration response message, or may be before sending the first configuration request message to the second node.

[0199] That is to say, when the attribute indication information of the user data is not configured by the second node, the first node can feedback the second configuration response message to other base stations (or CU of other base stations) at an appropriate time according to actual needs or configuration.

[0200] In an optional embodiment of the present application, if the attribute indication information of the user data is configured by the second node, sending the second configuration response message to the third node is after receiving the first configuration response message.

[0201] In this solution, since the attribute indication information of the user data is configured by the second node, the first node feeds back a second configuration response message with the data attribute indication information to the third node only after receiving the data attribute indication information carried in the first configuration response message.

[0202] In an optional embodiment of the present application, if the third node sends the second configuration response message, it is after receiving the first configuration response message, and the second configuration response message is determined based on the first configuration response message.

[0203] In an optional embodiment of the present application, the first configuration response message may be determined by the second node based on the third configuration response message; wherein the third configuration response message may be obtained by the second node in the following manner:

[0204] Sending a third configuration request message to the fourth node;

[0205] A third configuration response message is received, which is returned by the fourth node based on the third configuration request message.

[0206] The third configuration request message is used to request configuration of service user data, and the third response message is used to respond to the configuration request in the third configuration request message.

[0207] Taking the case where the first node is other base stations or CUs of other base stations as an example, in this solution, before the second node (such as the CU of the anchor node, the CU-CP of the anchor node, or the CU-UP of the anchor node, etc.) feeds back the first configuration response message to the first node, it may first send a third configuration request message to the fourth node to negotiate with the fourth node to determine the attribute indication information of the user data accepted by the distribution unit of the anchor node, so that the second node feeds back the first configuration response message to the first node, and the user data targeted in the response message may be the user data accepted by the fourth node, that is, the response message may include relevant information of the user data accepted by the fourth node (such as relevant information about the user data attributes, relevant information about the source sending node, relevant information about the destination receiving node, etc.). Among them, the user data targeted by the third configuration request message may be sent by the first node and sent to the fourth node (such as the relay node accessed by the user) through the second node.

[0208] In the information configuration method provided in the embodiment of the present application, the above-mentioned first configuration request message can be an S-Node Addition / modification request message of the Xn interface, or an SgNB addition / modification request message of the X2 interface, or a UE context setup / modification request message of the F1 interface, or a bearer context setup / modification request message of the E1 interface, or other newly defined messages, which can be configured according to actual needs in actual applications. Correspondingly, the first configuration response message can be an S-Node Addition / modification response message of the Xn interface, or an SgNB addition / modification response message of the X2 interface, or a UE context setup / modification response message of the F1 interface, or a bearer context setup / modification response message of the E1 interface, or other newly defined messages. It can be understood that the interfaces corresponding to the first configuration request message and the first configuration response message are corresponding.

[0209] The information configuration method provided in the embodiment of the present application can help the distribution unit of the anchor node distinguish different types of data by performing the above steps 1 and 2 between the first node and the second node such as the centralized unit of the anchor node and the distributed unit of the anchor node, and / or between other base stations (or centralized units of other base stations) and the centralized unit of the anchor node, so as to transmit different types of data through the appropriate return link channel. The centralized units of other base stations and anchor nodes can set the information in the data packet (such as setting the DSCP and / or flow label fields, etc.) according to the attribute indication information of the user data configured in the above process, and the distributed unit of the anchor node can determine the type of received user data according to the attribute indication information of the user data configured in the above process and / or the relevant information of the source sending node and / or the relevant information of the destination receiving node and / or the relevant information of the user data transmission path.

[0210] For example, taking the case where the first node is a centralized unit of an anchor node and the second node is a distributed unit of an anchor node, in the first configuration request message in step 1 above, assuming that the first type of user data is concerned, the information included in the message includes:

[0211] Information related to user data attributes (such as DRB ID=1, UE ID=1, type indication=DRB), attribute indication information of user data (such as 1), and relevant information of the destination receiving node (such as IP1);

[0212] Assuming that for the second type of user data, the information contained in the message includes:

[0213] Information related to user data attributes (such as DRB ID=2, UE ID=1, type indication=DRB), attribute indication information of user data (such as 2), and relevant information of the destination receiving node (such as IP1).

[0214] Step 2: The second node confirms that both DRB1 and DRB2 requested in step 1 are accepted.

[0215] Assume that in the actual process of data transmission, the distribution unit of the anchor node will receive data packet 1 and data packet 2. In the packet header information of data packet 1, the DSCP / flow label will be set to 1, that is, the attribute indication information of the user data is 1. In the packet header information of the data packet, the DSCP / flow label will be set to 2, that is, the attribute indication information of the user data is 2. In this way, the distribution unit of the anchor node can distinguish the user data type to which the data packet belongs based on the DSCP / flow label, or based on the DSCP / flow label and other information in the data packet.

[0216] Regarding the information configuration method provided in the embodiment of the present application, the method is described below with the second node as the execution subject of the method. Figure 4 As shown in , the information configuration method may include:

[0217] Receiving a first configuration request message sent by a first node;

[0218] According to the first configuration request message, a first configuration response message is sent to the first node.

[0219] Optionally, as can be seen from the foregoing description, the first node and the second node include any of the following:

[0220] The first node is a CU of an anchor node, and the second node is a DU of an anchor node, another base station, or a CU of another base station;

[0221] The first node is a CU-CP of an anchor node, and the second node is a CU-UP of an anchor node, a DU of an anchor node, another base station, or a CU of another base station;

[0222] The first node is other base stations or CUs of other base stations, and the second node is a CU of an anchor node or a CU-CP of an anchor node.

[0223] Optionally, the first configuration request message carries relevant information about user data that the first node expects or requests to be accepted by the second node, and the first configuration request message includes at least one of the following:

[0224] Information about the attributes of the data;

[0225] Attribute indication information of user data;

[0226] Relevant information of the destination receiving node;

[0227] Relevant information of the source sending node;

[0228] Information about the data transmission path;

[0229] The first configuration response message carries relevant information of user data accepted by the second node, and the first configuration response message includes at least one of the following:

[0230] Information about the attributes of the data;

[0231] Attribute indication information of user data;

[0232] Relevant information of the source sending node;

[0233] Relevant information of the destination receiving node;

[0234] Information about the data transfer path.

[0235] Optionally, the method may further include:

[0236] Sending a third configuration request message to the fourth node;

[0237] A third configuration response message is received, which is returned by the fourth node based on the third configuration request message.

[0238] It can be understood that the information configuration method described with the second node as the execution subject is essentially the same technical solution as the information configuration method described with the first node as the execution subject in the previous text, but the solution is described from a different perspective. For the detailed description of the information configuration method described with the second node as the execution subject and the explanation of the solution, reference can be made to the description of the information configuration method with the first node as the execution subject in the previous text, and no further description will be given here.

[0239] In the above information configuration method provided in the embodiment of the present application, in practical applications, the two steps in the method may have different implementation modes. In order to better illustrate the method, the method is further described below in combination with different implementation modes in specific examples.

[0240] Example 1

[0241] In this example, the first node is a centralized unit of an anchor node, the second node is a distributed unit of an anchor node, the third node is another base station or a CU of another base station, and the attribute indication information of the user data is determined and configured by the centralized unit of the anchor node. Figure 5a or Figure 5b As shown in , the signaling interaction process of the information configuration method shown in this example may include:

[0242] Step 1-1: The centralized unit of the anchor node sends the first configuration request information (configuration request message 1-1 shown in the figure) to the distributed unit of the anchor node, for a type of user data (the user data will be sent by other base stations or the centralized unit of the anchor node and sent to the user's access relay node through the distributed unit of the anchor node. This type of data has a specific attribute (profile), and this specific Profile is indicated by the information contained in the configuration request message 1-1). The user data can be a newly added user data, that is, newly added data that needs to be transmitted by the distributed unit, or data that has been transmitted by the distributed unit. In addition to the attribute indication information of the user data, the message can also include at least one of the following information:

[0243] ■Information related to user data attributes

[0244] ■Source sending node related information

[0245] ■Relevant information of the destination receiving node

[0246] ■Related information about the user data transmission path

[0247] Step 1-2: The distribution unit of the anchor node sends first configuration response information (configuration response message 1-2 shown in the figure) corresponding to the request information of step 1-1 to the centralized unit of the anchor node.

[0248] The message in step 1-2 is used to confirm the information received by the distribution unit of the anchor node in step 1-1. Optionally, for a type of user data (in one implementation, the user data is the user data received by the distribution unit of the anchor node), the message may at least include information related to the attributes of the user data.

[0249] Optionally, in the above step 1-1, the first configuration request information may be sent by the control plane part (CU-CP) of the centralized unit of the anchor node to the user plane part (CU-UP) of the centralized unit of the anchor node, and in the above step 1-2, the first configuration response information may be sent by the user plane part (CU-UP) of the centralized unit of the anchor node to the control plane part (CU-CP) of the centralized unit of the anchor node.

[0250] Optionally, the configuration request message 1-1 may also indicate a type of user data that needs to be removed, and the profile of the removed user data may be indicated by one or more information contained in the configuration request message in the above step 1-1, such as information related to user data attributes, attribute indication information of user data, relevant information of the source sending node, relevant information of the destination receiving node, relevant information of the user data transmission path, etc. After receiving the information, the distribution unit of the anchor node may determine how to process the removed user data of this type, such as not transmitting the user data of this type on a return link channel.

[0251] Optionally, when the user data packet is sent by another base station (such as base station 1) or a centralized unit of another base station (such as a centralized unit of base station 1) (such as sent by another base station to a distributed unit of an anchor node), Figure 5b or Figure 5b As shown in , the signaling interaction process in this example also includes the following steps:

[0252] Step a-1: Base station 1 (or the centralized unit of base station 1) sends a second configuration request message (configuration request message a-1 shown in the figure) to the centralized unit of the anchor node. The message may include information related to the type of user data (the user data is sent by other base stations to the distributed unit of the anchor node).

[0253] Step a-2: The centralized unit of the anchor node (or the control plane part of the centralized unit of the anchor node) sends a second configuration response message (configuration response message a-2 shown in the figure) corresponding to the configuration request message in step a-1 to the base station 1 (or the centralized unit of the base station 1). For a type of user data (in one embodiment, the user data is accepted by the centralized unit of the anchor node), the message includes at least one of the following information:

[0254] ■Information related to user data attributes

[0255] ■ User data attribute indication information

[0256] ■Relevant information of the destination receiving node

[0257] Optional, such as Figure 5a As shown in, the above step a-2 can be to send the attribute indication information of the user data negotiated by the centralized unit of the anchor node and the distributed unit of the anchor node in steps 1-1 and 1-2 (the indication information of the attributes of the user data accepted by the distributed unit) to other base stations, and the user data targeted by the attribute indication information of the user data will be sent by other base stations to the distributed unit of the anchor node.

[0258] It should be noted that, in actual applications, the above steps 1-1 / 1-2 and steps a-1 / a-2 can be performed separately or in combination. If they are performed in combination, any execution order can be adopted. One implementation method is step a-1→step 1-1→step 1-2→step a-2 (e.g. Figure 5a Another implementation is step a-1→step a-2→step 1-1→step 1-2 (as shown in Figure 5b ).

[0259] Example 2

[0260] In this example, the first node is a centralized unit of an anchor node, the second node is a distributed unit of an anchor node, the third node is another base station or a CU of another base station, and the attribute indication information of the user data is configured by the distributed unit of the anchor node. Figure 6 As shown in , the signaling interaction process of the information configuration method shown in this example may include:

[0261] Step 2-1: The centralized unit of the anchor node sends the first configuration request information (configuration request message 2-1 shown in the figure) to the distributed unit of the anchor node, for a type of user data (the user data will be sent by other base stations or the centralized unit of the anchor node and sent to the relay node accessed by the user through the distributed unit of the anchor node. This type of data has a specific profile, which is indicated by the information contained in the configuration request message 2-1). The user data can be a newly added user data, that is, newly added data that needs to be transmitted by the distributed unit, or data that has been transmitted by the distributed unit. The message may include at least one of the following information:

[0262] ■Information related to user data attributes

[0263] ■Source sending node related information

[0264] ■Relevant information of the destination receiving node

[0265] ■Related information about the user data transmission path

[0266] Step 2-2: The distribution unit of the anchor node sends a first configuration response message (configuration response message 2-2 shown in the figure) to the centralized unit of the anchor node. For a type of user data (in one implementation, the user data is the user data accepted by the distribution unit of the anchor node), in addition to the attribute indication information of the user data, the message may also include any one of the following information:

[0267] ■Information related to user data attributes

[0268] ■Source sending node related information

[0269] ■Relevant information of the destination receiving node

[0270] ■Related information about the user data transmission path

[0271] Optionally, when the first node is the CU-CP of the anchor node and the second node is the CU-UP of the anchor node, taking the example that the attribute indication information of the user data is configured by the CU-UP of the anchor node, in the above step 2-1, the first configuration request information may be sent by the control plane part (CU-CP) of the centralized unit of the anchor node to the user plane part (CU-UP) of the centralized unit of the anchor node, and in the above step 2-2, the first configuration response information may be sent by the user plane part (CU-UP) of the centralized unit of the anchor node to the control plane part (CU-CP) of the centralized unit of the anchor node.

[0272] Optionally, the configuration request message 2-1 may also indicate a type of user data that needs to be removed, and the profile of the removed user data may be indicated by one or more information contained in the configuration request message in the above step 2-1, such as information related to user data attributes, attribute indication information of user data, relevant information of the source sending node, relevant information of the destination receiving node, relevant information of the user data transmission path, etc. After receiving the information, the distribution unit of the anchor node may determine how to handle the removed user data of this type, such as not transmitting the user data of this type on a return link channel.

[0273] Optionally, when the data packet of the user is sent by another base station (such as base station 1) or a centralized unit of another base station (such as a centralized unit of base station 1) (such as sent by another base station to a distributed unit of an anchor node), Figure 6 As shown in , the signaling interaction process in this example may also include the following steps:

[0274] Step b-1: Base station 1 (or the centralized unit of base station 1) sends a second configuration request message (configuration request message b-1 shown in the figure) to the centralized unit of the anchor node. For a type of user data (in one embodiment, the user data is sent by other base stations to the distributed unit of the anchor node), the message includes at least one of the following information:

[0275] ■Information related to user data attributes

[0276] ■Source sending node related information

[0277] ■Relevant information of the destination receiving node

[0278] Step b-2: The centralized unit of the anchor node sends a second configuration response message (configuration response message b-2 shown in the figure) to the base station 1 (or the centralized unit of the base station 1). For a type of user data (in one embodiment, the user data is accepted by the centralized unit of the anchor node), the message may include at least one of the following information in addition to the attribute indication information of the user data:

[0279] ■Information related to user data attributes

[0280] ■Source sending node related information

[0281] ■Relevant information of the destination receiving node

[0282] Optionally, the above step b-2 may be to send the attribute indication information of the user data determined by the distribution unit of the anchor node in step 2-2 to other base stations, and the user data targeted by the attribute indication information of the user data will be sent by other base stations to the distribution unit of the anchor node.

[0283] It should be noted that in actual applications, according to actual needs, the above steps 2-1 / 2-2 and steps b-1 / b-2 can be performed separately or in combination. If they are performed in combination, any execution order can be adopted. One implementation method is step b-1→step 2-1→step 2-2→step b-2 (such as Figure 6 ).

[0284] Example 3

[0285] In this example, the first node is another base station, the second node is a centralized unit of an anchor node, the fourth node is a distributed unit of an anchor node, and the attribute indication information of the user data is configured by another base station. Figure 7 As shown in , the signaling interaction process of the information configuration method shown in this example may include:

[0286] Step 3-1: Other base stations send the first configuration request information (configuration response message 3-1 shown in the figure) to the centralized unit of the anchor node, for a type of user data (the user data will be sent by other base stations or the centralized unit of the anchor node and sent to the relay node accessed by the user through the distributed unit of the anchor node. This type of data has a specific profile, which is indicated by the information contained in the configuration request message 3-1). The user data can be a newly added user data, that is, newly added data that needs to be transmitted by the distributed unit, or data that has been transmitted by the distributed unit. In addition to the attribute indication information of the user data, the message can also include at least one of the following information:

[0287] ■Information related to user data attributes

[0288] ■Source sending node related information

[0289] ■Relevant information of the destination receiving node

[0290] Considering that the information about the transmission path of the user data packet is generally controlled or distributed by the centralized unit of the anchor node, the request information may not include the information about the transmission path of the user data packet. Of course, if other nodes know the information about the transmission path of the user data packet, the request information may also include the information.

[0291] Step 3-2: The centralized unit of the anchor node sends a first configuration response message (configuration response message 3-2 shown in the figure) to other base stations. The message is used to confirm the information sent in step 3-2. Optionally, for a type of user data (in one embodiment, the user data is user data accepted by the centralized unit of the anchor node), the message may include information related to user data attributes.

[0292] Optionally, the configuration request message 3-1 may also indicate a type of user data that needs to be removed, and the profile of the removed user data may be indicated by one or more information contained in the configuration request message in the above step 3-1, such as information related to user data attributes, attribute indication information of user data, relevant information of the source sending node, relevant information of the destination receiving node, relevant information of the user data transmission path, etc. After receiving the information, the centralized unit of the anchor node may determine how to handle the removed user data of this type, such as configuring (as configured in step c-1) not to transmit the user data of this type on a return link channel.

[0293] Optional, such as Figure 7 As shown in , the following interaction process is also included between the centralized unit of the anchor node and the distributed unit of the anchor node in this example:

[0294] Step c-1: The centralized unit of the anchor node sends a second configuration request message (configuration request message c-1 shown in the figure) to the distributed unit of the anchor node. For a type of user data (the user data will be sent by other base stations or the centralized unit of the anchor node and sent to the relay node accessed by the user through the distributed unit of the anchor node), the message may include at least one of the following information:

[0295] ■Information related to user data attributes

[0296] ■ User data attribute indication information

[0297] ■Source sending node related information

[0298] ■Relevant information of the destination receiving node

[0299] ■Related information about the user data transmission path

[0300] Step c-2: The distribution unit of the anchor node sends a second configuration response message (configuration response message c-2 shown in the figure) to the centralized unit of the anchor node, which is used to confirm the information sent in step c-1. Optionally, for a type of user data (in one implementation, the user data is the user data accepted by the distribution unit of the anchor node), the message may include information related to the attributes of the user data.

[0301] Optionally, the above step c-1 may be a distribution unit that sends the attribute indication information of the user data determined by other base stations in step 3-1 to the anchor node.

[0302] Optionally, in step c-1, the second configuration request information may be sent by the control plane part (CU-CP) of the centralized unit of the anchor node to the user plane part (CU-UP) of the centralized unit of the anchor node, and in the above step c-2, the second configuration response information may be sent by the user plane part (CU-UP) of the centralized unit of the anchor node to the control plane part (CU-CP) of the centralized unit of the anchor node.

[0303] It should be noted that, in actual applications, the above steps 3-1 / 3-2 and steps c-1 / c-2 can be performed separately or in combination. If they are performed in combination, any execution order can be adopted. One implementation method is step 3-1→step c-1→step c-2→step 3-2 (such as Figure 7 ).

[0304] Example 4

[0305] In this example, the first node is a centralized unit of an anchor node, the second node is a distributed unit of an anchor node, the third node is another base station (or a CU of another base station), and the attribute indication information of the user data is configured by the source sending node of the user data packet. Figure 8a or Figure 8b As shown in , the signaling interaction process of the information configuration method shown in this example may include:

[0306] Step 4-1: The centralized unit of the anchor node sends a first configuration request message (configuration request message 4-1 shown in the figure) to the distributed unit of the anchor node, for a type of user data (the user data will be sent by other base stations or the centralized unit of the anchor node and sent to the relay node accessed by the user through the distributed unit of the anchor node. This type of data has a specific profile, which is indicated by the information contained in the configuration request message 4-1). The user data can be a newly added user data, that is, newly added data that needs to be transmitted by the distributed unit, or data that has been transmitted by the distributed unit. The message can include at least one of the following information:

[0307] ■Information related to user data attributes

[0308] ■Attribute indication information of user data. If the source sending node of the user data is the centralized unit of the anchor node, the indication information can be generated by the centralized unit of the anchor node. If the source sending node of the user data is other base stations, the indication information can be generated by other base stations and sent to the centralized unit of the anchor node, such as being sent to the centralized unit of the anchor node through step d-1 mentioned below.

[0309] ■Source sending node related information

[0310] ■Relevant information of the destination receiving node

[0311] ■Related information about the user data transmission path

[0312] Step 4-2: The distribution unit of the anchor node sends a first configuration response message (configuration response message 4-2 shown in the figure) to the centralized unit of the anchor node. The message is used to confirm the information received by the distribution unit of the anchor node in step 4-1. Optionally, for a type of user data (in one embodiment, the user data is user data accepted by the distribution unit of the anchor node), the message may at least include information related to user data attributes.

[0313] Optionally, the configuration request message 4-1 may also indicate a type of user data that needs to be removed, and the profile of the removed user data may be indicated by one or more information contained in the configuration request message in the above step 4-1, such as information related to user data attributes, attribute indication information of user data, relevant information of the source sending node, relevant information of the destination receiving node, relevant information of the user data transmission path, etc. After receiving the information, the distribution unit of the anchor node may determine how to handle the removed user data of this type, such as not transmitting the user data of this type on a return link channel.

[0314] Optionally, in the above step 4-1, the first configuration request information may be sent by the control plane part (CU-CP) of the centralized unit of the anchor node to the user plane part (CU-UP) of the centralized unit of the anchor node, and in the above step 4-2, the first configuration response information may be sent by the user plane part (CU-UP) of the centralized unit of the anchor node to the control plane part (CU-CP) of the centralized unit of the anchor node. Optionally, when the user data is sent by another base station (such as base station 1) or a centralized unit of another base station (such as a centralized unit of base station 1) (such as sent by another base station or a centralized unit of another base station to a distributed unit of the anchor node), such as Figure 8a or Figure 8b As shown in , the signaling interaction process in this example may also include the following steps:

[0315] Step d-1: Base station 1 (or the centralized unit of base station 1) sends a second configuration request message (configuration request message d-1 shown in the figure) to the centralized unit of the anchor node. For a type of user data (the user data will be sent by other base stations and sent to the relay node accessed by the user through the distributed unit of the anchor node), the message includes at least one of the following information:

[0316] ■Information related to user data attributes

[0317] ■ User data attribute indication information

[0318] ■Source sending node related information

[0319] ■Relevant information of the destination receiving node

[0320] Step d-2: The centralized unit of the anchor node sends a second configuration response message (configuration response message d-2 shown in the figure) to the base station 1, which is used to confirm that the message in step d-1 has been received. Optionally, for a type of user data (in an embodiment, the user data is user data accepted by the centralized unit of the anchor node), the message at least includes information related to user data attributes.

[0321] For more specific descriptions of step d-1 and step d-2 in this example, please refer to the corresponding descriptions of step a-1 and step a-2 in the above example 1.

[0322] It should be noted that, in actual applications, the above steps 4-1 / 4-2 and steps d-1 / d-2 can be performed separately or in combination. If they are performed in combination, any execution order can be adopted. One implementation method is step d-1→step 4-1→step 4-2→step d-2 (e.g. Figure 8a Another implementation is step d-1→step d-2→step 4-1→step 4-2 (as shown in Figure 8b shown).

[0323] The effect of the above four examples is that when nodes in the network (such as the centralized unit of the anchor node, or the user plane part CU-CP of the centralized unit of the anchor node, other base stations or centralized units of other base stations) send data, how to add information related to the attributes of the user data in the data packet, and also avoid adding the same information to two data with different attributes. At the same time, the node receiving the data (such as the distributed unit of the anchor node) can also obtain the information contained in the received data packet according to the above configuration information, and send the information to other nodes, and send the data correctly, such as using the configured return link to send the corresponding user data, thereby ensuring the transmission and routing of the user data in the relay network.

[0324] In the embodiment of the first aspect of the present invention, it may be necessary for other base stations or anchor nodes' centralized units (or the control plane part CU-CP of the centralized unit) or the distributed units of the anchor nodes to obtain relevant information about the source sending node and / or the destination receiving node (i.e., the user's access relay node) of the user data. However, each node serving user data in the existing relay network cannot obtain relevant information (such as address information, identification information, port information, etc.) of the source sending node of the user data and relevant information (such as address information, identification information, port information, etc.) of the destination receiving node (access relay node), that is, the problem in the above-mentioned second aspect existing in the prior art. To address this problem, the second aspect of the embodiment of the present application further provides an information interaction method, which obtains relevant information about the source sending node of the user data and / or the relevant information about the destination receiving node through signaling interaction of network nodes. The signaling interaction process of the scheme mainly involves two nodes, which are recorded as the fifth node and the sixth node in the embodiment of the present application for description. The method provided in the embodiment of the present application is described in detail below.

[0325] Fig. 9 A flow chart of an information interaction method provided by an embodiment of the present application is shown in FIG. 1 . The method is described below with the fifth node as the execution subject of the method. Fig. 9 As shown in , the method may include:

[0326] Step 5-1: The fifth node sends a fourth configuration message to the sixth node (the fourth configuration message 5-1 shown in the figure).

[0327] The fourth configuration message is used for the fifth node and the sixth node to exchange relevant information of the source sending node and / or relevant information of the destination receiving node of the user data.

[0328] Based on the method of the embodiment of the present application, the fifth node can send the relevant information of the source sending node and / or the relevant information of the destination receiving node of the user data known by the fifth node to the sixth node by sending node configuration information to the sixth node, so that the sixth node can also obtain the relevant information of the source sending node and / or the relevant information of the destination receiving node of the user data known by the fifth node.

[0329] Optionally, the fifth node and the sixth node may be at least one of the following:

[0330] The fifth node is a CU of the anchor node, and the sixth node is a DU of the anchor node, another base station, or a CU of another base station;

[0331] The fifth node is a CU of another base station or another base station, and the sixth node is a CU of an anchor node;

[0332] The fifth node is the DU of the anchor node, and the sixth node is the CU of the anchor node.

[0333] Optionally, the fourth configuration message may include at least one of the following:

[0334] User identification information;

[0335] Information related to data attributes (i.e. information related to the attributes of user data);

[0336] Relevant information of the source sending node and / or relevant information of the destination receiving node.

[0337] The user identification information is the identification information of the user receiving the user data to be transmitted. For downlink data, the user identification information may be the identification information of the UE receiving the user data. For uplink data, the user identification may be the identification information of the UE sending the user data.

[0338] It is understandable that the relevant information of the source sending node and / or the relevant information of the destination receiving node in the information carried in the fourth configuration message is the relevant information of the node known by the fifth node. For example, the fifth node knows the relevant information of the destination receiving node of the user data to be transmitted, and the node configuration information may include the relevant information of the destination receiving node.

[0339] Optional, such as Fig. 9 As shown in , the fifth node sends a fourth configuration message to the sixth node, which may specifically include:

[0340] Step 5-0: receiving a fourth configuration request message (configuration request message 5-0 shown in the figure) sent by the sixth node;

[0341] Step 5-1: Send a fourth configuration message to a sixth node based on the node configuration request information.

[0342] That is to say, before the fifth node sends the fourth configuration message to the sixth node, it may also receive the fourth configuration request message sent by the sixth node. The sixth node sends the fourth configuration request message to the fifth node to obtain from the fifth node the relevant information of the source sending node and / or the relevant information of the destination receiving node of the user data to be transmitted. After receiving the node configuration request, the fifth node feeds back the corresponding node configuration information to the sixth node, and informs the sixth node of the relevant information of the source sending node and / or the relevant information of the destination receiving node that it knows.

[0343] Optionally, the fourth configuration request message includes at least one of the following:

[0344] User identification information;

[0345] Information about the attributes of the data;

[0346] Information about the source sending node or the destination receiving node.

[0347] The relevant information of the source sending node or the relevant information of the destination receiving node carried in the fourth configuration request message is the relevant information of the source sending node or the relevant information of the destination receiving node of the user data packet to be transmitted known to the sixth node. That is to say, when the sixth node sends the node configuration request information to the fifth node, it can also inform the fifth node of the relevant information of the node (source sending node or destination receiving node) known to it.

[0348] Optionally, the fourth configuration request message and the fourth configuration message may not include relevant information of the same node at the same time, and the same node is a source sending node or a target receiving node.

[0349] Optional, such as Fig. 9 As shown, after the fifth node sends the fourth configuration message to the sixth node, the following may also be included:

[0350] Step 5-3: Receive a configuration confirmation message sent by the sixth node based on the node configuration information, that is, a response message to the fourth configuration message (configuration response message 5-2 shown in the figure).

[0351] After receiving the fourth configuration message sent by the fifth node, the sixth node feeds back configuration confirmation information to the fifth node to confirm that it has received the fourth configuration message sent by the fifth node in step 5-1. The specific form of the confirmation information carried in the configuration confirmation message (i.e., the message used to inform the fifth node that it has received the node configuration information) is not limited in the embodiment of the present application, for example, it can be a form agreed upon between nodes, or a form of confirmation information pre-defined by the system.

[0352] Optionally, the configuration confirmation message includes at least one of the following:

[0353] User identification information;

[0354] Information about the attributes of the data;

[0355] Information about the source sending node or the destination receiving node.

[0356] Similarly, the relevant information of the source sending node or the relevant information of the destination receiving node in the confirmation message is the relevant information of the source sending node or the destination receiving node known by the sixth node.

[0357] Optionally, the fourth configuration message and the configuration confirmation message do not simultaneously include relevant information of the same node, and the same node is a source sending node or a target receiving node.

[0358] In practical applications, the messages used in the process of the information interaction method provided in the above-mentioned embodiments of the present application (such as the fourth configuration request message, the fourth configuration message, and the configuration confirmation message) can be messages of the existing X2 / Xn / F1 interface or newly defined messages.

[0359] The effect of the information interaction method provided in the embodiment of the present application is that each node serving user data can obtain relevant information of the source sending node and / or the destination receiving node (i.e., the access relay node) of the user data, which can facilitate adding different relevant indication information to data packets of different user data, so that the distribution unit of the anchor node can distinguish different types of user data, such as distinguishing different user data based on one or more of the attribute indication information of the user data, information related to the attributes of the user data, relevant information of the source sending node of the user data, and relevant information of the destination receiving node of the user data, and determine how to send the user data based on this information, such as determining the return link channel used to transmit the user data.

[0360] The following describes the information interaction method provided by the embodiment of the present application by taking the sixth node as the execution subject of the information interaction method. Fig. 9 , the information interaction method may include:

[0361] The fifth node sends a fourth configuration message, where the fourth configuration message is used for the fifth node and the sixth node to exchange relevant information of a source sending node and / or relevant information of a destination receiving node of user data.

[0362] Optionally, the fifth node and the sixth node are at least one of the following:

[0363] The fifth node is a CU of the anchor node, and the sixth node is a DU of the anchor node, another base station, or a CU of another base station;

[0364] The fifth node is the CU of other base stations or other base stations, and the sixth node is the CU of the anchor node.

[0365] The fifth node is the DU of the anchor node, and the sixth node is the CU of the anchor node.

[0366] Optionally, the fourth configuration message may include at least one of the following:

[0367] User identification information;

[0368] Information about the attributes of the data;

[0369] Relevant information of the source sending node and / or relevant information of the destination receiving node.

[0370] Optionally, the sending the fourth configuration message to the sixth node may specifically include:

[0371] receiving a fourth configuration request message sent by a sixth node;

[0372] A fourth configuration message is sent to the sixth node based on the node configuration request information.

[0373] Optionally, the fourth configuration request message may include at least one of the following:

[0374] User identification information;

[0375] Information about the attributes of the data;

[0376] Relevant information of the source sending node;

[0377] Information about the destination receiving node.

[0378] Similarly, the information interaction method described with the sixth node as the execution subject is essentially the same technical solution as the information interaction method described with the fifth node as the execution subject in the previous text, but the solution is described from a different perspective. For the detailed description of the information interaction method described with the sixth node as the execution subject and the explanation of the solution, please refer to the description of the information configuration method with the fifth node as the execution subject in the previous text, which will not be repeated here.

[0379] In order to better illustrate the information interaction method provided in the embodiment of the present application, the method is further described below with reference to specific examples.

[0380] Example 1

[0381] In this example, the fifth node is a centralized unit of an anchor node, and the sixth node is a centralized unit of another base station or another base station. The centralized unit of the anchor node knows the relevant information of the destination receiving node, and the centralized unit of the other base station or another base station knows the relevant information of the source sending node. The signaling interaction process of the information interaction method in this example can mainly include the following steps:

[0382] Step 5a-1: The centralized unit of the anchor node sends a fourth configuration message 5a-1 to other base stations (or centralized units of other base stations). In addition to the relevant information of the destination receiving node, the message may also include at least one of the following information:

[0383] ■User identification information

[0384] ■Information related to user data attributes

[0385] Optionally, before step 5a-1, the following steps may also be included:

[0386] Step 5a-0: The other base station (or the centralized unit of the other base station) sends a fourth configuration request message 5a-0 to the centralized unit of the anchor node. In addition to the relevant information of the source sending node, the message may also include at least one of the following information:

[0387] ■User identification information

[0388] ■Information related to user data attributes

[0389] Optionally, after step 5a-1, the following steps may also be included:

[0390] Step 5a-2: The other base station (or the centralized unit of the other base station) sends a node configuration confirmation message 5a-2 to the centralized unit of the anchor node to confirm that the message sent in step 5a-1 has been received. In addition to including information for confirming that the message sent in step 5a-1 has been received, the confirmation message may also optionally include at least one of the following information:

[0391] ■User identification information

[0392] ■Information related to user data attributes

[0393] ■Source sending node related information

[0394] Through the scheme provided in this example, the centralized unit of the anchor node and other base stations (or centralized units of other base stations) complete the interaction of relevant information of the source sending node and / or relevant information of the destination receiving node of the user data, so that the centralized unit of the anchor node and other base stations (or centralized units of other base stations) can obtain relevant information of the source sending node and relevant information of the destination receiving node.

[0395] Example 2

[0396] In this example, the fifth node is a centralized unit of the anchor node, and the sixth node is a distributed unit of the anchor node. The centralized unit of the anchor node knows the relevant information of the source sending node and / or the relevant information of the destination receiving node, and the distributed unit of the anchor node knows the relevant information of the destination receiving node. The signaling interaction process of the information interaction method in this example can mainly include the following steps:

[0397] Step 5b-1: The centralized unit of the anchor node sends a fourth configuration message 5b-1 to the distributed unit of the anchor node. In addition to the relevant information of the source sending node and / or the relevant information of the destination receiving node, the message may also include at least one of the following information:

[0398] ■User identification information

[0399] ■Information related to user data attributes

[0400] Optionally, before step 5b-1, the following steps may also be included:

[0401] Step 5b-0: The distribution unit of the anchor node sends a fourth configuration request message 5b-0 to the central unit of the anchor node. The message includes at least one of the following information:

[0402] ■User identification information

[0403] ■Information related to user data attributes

[0404] ■Relevant information of the destination receiving node

[0405] Optionally, after step 5b-1, the following steps may also be included:

[0406] Step 5b-2: The distributed unit of the anchor node sends a node configuration confirmation message 5b-2 to the centralized unit of the anchor node to confirm that the message sent in step 5b-1 has been received. In addition to including information for confirming that the message sent in step 5b-1 has been received, the confirmation message may also optionally include at least one of the following information:

[0407] ■User identification information

[0408] ■Information related to user data attributes

[0409] ■Relevant information of the destination receiving node

[0410] Among them, it can be understood that, when the fourth configuration request message 5b-0 includes relevant information of the destination receiving node, the fourth configuration message 5b-1 may not need to include relevant information of the destination receiving node, and when the fourth configuration request message 5b-0 does not include relevant information of the destination receiving node, the fourth configuration message 5b-1 may include relevant information of the destination receiving node. Similarly, when the fourth configuration message 5b-1 includes relevant information of the destination receiving node, the node configuration confirmation message 5b-2 may not need to include relevant information of the destination receiving node. That is to say, in the above steps, the relevant information of the destination receiving node will not appear in step 5b-1 and step 5b-0 (or step 5b-2) at the same time.

[0411] Example 3

[0412] In this example, the fifth node is another base station (or a centralized unit of another base station), and the sixth node is a centralized unit of an anchor node. The other base station (or a centralized unit of another base station) knows the relevant information of the source sending node, and the centralized unit of the anchor node knows the relevant information of the destination receiving node. The signaling interaction process of the information interaction method in this example can mainly include the following steps:

[0413] Step 5c-1: The other base station (or the centralized unit of the other base station) sends a fourth configuration message 5c-1 to the centralized unit of the anchor node. In addition to the relevant information of the source sending node, the message may also include at least one of the following information:

[0414] ■User identification information

[0415] ■Information related to user data attributes

[0416] Optionally, before step 5c-1, the following steps may also be included:

[0417] Step 5c-0: The centralized unit of the anchor node sends a fourth configuration request message 5c-0 to other base stations (or centralized units of other base stations). In addition to the relevant information of the destination receiving node, the message may also include at least one of the following information:

[0418] ■User identification information

[0419] ■Information related to user data attributes

[0420] Optionally, after step 5c-1, the following steps may also be included:

[0421] Step 5c-2: The centralized unit of the anchor node sends a node configuration confirmation message 5c-2 to other base stations (or centralized units of other base stations) to confirm that the message sent in step 5c-1 has been received. In addition to including information for confirming that the message sent in step 5c-1 has been received, the confirmation message may also optionally include at least one of the following information:

[0422] ■User identification information

[0423] ■Information related to user data attributes

[0424] ■Relevant information of the destination receiving node

[0425] Example 4

[0426] In this example, the fifth node is a distribution unit of the anchor node, and the sixth node is a centralized unit of the anchor node. The distribution unit of the anchor node knows the relevant information of the destination receiving node, and the centralized unit of the anchor node knows the relevant information of the source sending node. The signaling interaction process of the message interaction method in this example can mainly include the following steps:

[0427] Step 5d-1: The distribution unit of the anchor node sends a fourth configuration message 5d-1 to the central unit of the anchor node. In addition to the relevant information of the destination receiving node, the message also includes at least one of the following information:

[0428] ■User identification information

[0429] ■Information related to user data attributes

[0430] ■Relevant information of the destination receiving node

[0431] Optionally, before step 5d-1, the following steps may also be included:

[0432] Step 5d-0: The centralized unit of the anchor node sends a fourth configuration request message 5d-0 to the distributed unit of the anchor node. In addition to the relevant information of the source sending node, the message may also include at least one of the following information:

[0433] ■User identification information

[0434] ■Information related to user data attributes

[0435] Optionally, after step 5d-1, the method further includes:

[0436] Step 5d-2: The centralized unit of the anchor node sends a node configuration confirmation message 5d-2 to the distributed unit of the anchor node to confirm that the message sent in step 5d-1 has been received. In addition to including information for confirming that the message sent in step 5d-1 has been received, the confirmation message may also optionally include at least one of the following information:

[0437] ■User identification information

[0438] ■Information related to user data attributes

[0439] ■Source sends relevant information of the node.

[0440] A third aspect of the present invention is to provide a method for updating address information of a relay node.

[0441] In response to the problem in the prior art that when the address of the relay node serving the user changes, updating the GTP-U tunnel or TNL association of the serving user will cause large signaling overhead, the third aspect of the present application also provides a mechanism for quickly updating address information, namely, a method for updating the address information of a relay node.

[0442] In addition, it should be noted that the update in the above-mentioned update method provided in the embodiment of the present application may include both updating or modifying the address information and methods such as adding and deleting the address information.

[0443] The above-mentioned relay node address changes may be because the relay node changes the distribution unit of the anchor node to which it is connected (the connection may be a direct connection or a connection through other nodes), or because the relay node changes the concentration unit of the anchor node to which it is connected, or other reasons.

[0444] The increase and decrease of the relay node addresses may be because the relay node needs a new address to communicate with the anchor node, or the existing address is no longer in use, or other reasons may be present.

[0445] The method for updating the address information of the relay node provided in the embodiment of the present application may include any one of the following methods:

[0446] Method 1: The CU of the anchor node sends a first address update message to the relay node or the DU of the relay node;

[0447] Method 2: The DU of the anchor node sends an address update notification message to the CU of the anchor node;

[0448] Method three: the relay node or the DU of the relay node sends an address update request message to the CU of the anchor node.

[0449] Among them, for the above-mentioned method one, the new address information of the relay node or the DU of the relay node is allocated or configured by the centralized unit of the anchor node. Furthermore, the new address may be obtained by the centralized unit of the anchor node from other nodes (such as OAM, the distribution unit of the anchor node, DHCP server, etc.); for method two, the new address information of the relay node or the DU of the relay node is allocated by the distribution unit of the anchor node; for method three, the new address information of the relay node or the DU of the relay node is obtained by itself, such as through OAM configuration or allocation by a DHCP server, and the relay node or the DU of the relay node obtains the new address information from the OAM or DHCP server.

[0450] In an optional embodiment of the present application, the address update message, the address update notification message or the address update request message may be an F1AP (F1 Application Protocol, application protocol of the F1 interface) message, an RRC message, or other messages. The above messages may include at least one of the following information:

[0451] Identification information of the relay node or the DU of the relay node;

[0452] The (old) address information of the relay node or the DU of the relay node before updating, which address information may be IP address information, and / or newly defined address information representing the relay node or the DU of the relay node used when sending or receiving data on the backhaul link (such as the backhaul adaptation layer address (BAPaddress)), and / or port information, and / or information on the prefix length of the IP address, all of which address information is information used before updating; further, when the address information before updating is included in the message, the message may also include indication information of the purpose of the address information, such as indication information for sending control signaling (the indication information indicates that the address indicated by the address information is used for sending control signaling, such as sending control signaling of the F1 interface), or indication information for sending user plane data (the indication information indicates that the address indicated by the address information is used for sending user plane data, such as sending user plane data of the F1 interface), or indication information for sending both control signaling and user plane data.

[0453] The updated (new) address information of the relay node or the DU of the relay node, which address information may be IP address information, and / or newly defined address information representing the relay node or the DU of the relay node used when sending or receiving data on the return link (such as BAP address), and / or port information, and / or information on the prefix length of the IP address, all of which address information is information used after the update; further, when the updated address information is included in the message, the message may also include indication information on the purpose of the address information, such as indication information for sending control signaling (the indication information indicates that the address indicated by the address information is used for sending control signaling, such as sending control signaling of the F1 interface), or indication information for sending user plane data (the indication information indicates that the address indicated by the address information is used for sending user plane data, such as sending user plane data of the F1 interface), or indication information for both sending control signaling and sending user plane data.

[0454] The newly added address information of the relay node or the DU of the relay node, which address information may be IP address information, and / or newly defined address information representing the relay node or the DU of the relay node used when sending or receiving data on the return link (such as BAP address), and / or port information, and / or information on the prefix length of the IP address; further, the information may be included in the first address update message, or in the address update request message, or in the update notification message; further, when the newly added address information is included in the message, the message may also include indication information on the purpose of the address information, such as indication information for sending control signaling (the indication information indicates that the address indicated by the address information is used for sending control signaling, such as sending control signaling of the F1 interface), or indication information for sending user plane data (the indication information indicates that the address indicated by the address information is used for sending user plane data, such as sending user plane data of the F1 interface), or indication information for both sending control signaling and sending user plane data.

[0455] The relay node or the DU of the relay node needs to delete, release or remove address information, which indicates that the relay node or the DU of the relay node no longer communicates with the anchor node or the CU of the anchor node using the address indicated by the information. The address information may be IP address information, and / or newly defined address information (such as BAP address) representing the relay node or the DU of the relay node used when sending or receiving data on the return link, and / or port information, and / or information on the prefix length of the IP address; further, the information may be included in a first address update message, an address update request message, or an update notification message; in one embodiment, if the relay node or the DU of the relay node receives the information, the relay node or the DU of the relay node deletes, releases, or removes the address indicated by the information, and no longer communicates with the anchor node or the CU of the anchor node using the address indicated by the information; in another embodiment, if the anchor node or the CU of the anchor node receives the information, the anchor node or the CU of the anchor node no longer communicates with the relay node or the DU of the relay node using the address indicated by the information; in another embodiment, if the DU of the anchor node receives the information, the DU of the anchor node considers that the relay node or the DU of the relay node no longer communicates with the anchor node or the CU of the anchor node using the address indicated by the information. The old address information of the anchor node (or the centralized unit of the anchor node or the distributed unit of the anchor node), which address information may be IP address information, and / or newly defined address information representing the anchor node or the centralized unit of the anchor node used when sending or receiving data on the return link (such as BAP address), and / or port information, and / or information on the prefix length of the IP address, which address information is the address information used for communicating with the relay node or the DU of the relay node before the update.

[0456] The new address information of the anchor node (or the centralized unit of the anchor node or the distributed unit of the anchor node), which may be IP address information, and / or newly defined address information representing the anchor node or the centralized unit of the anchor node used when sending or receiving data on the return link (such as BAP address), and / or port information, and / or information on the prefix length of the IP address, which is the address information used to communicate with the relay node or the DU of the relay node after the update.

[0457] Newly added address information of the anchor node or the CU of the anchor node, which address information may be IP address information, and / or newly defined address information (such as BAP address) representing the anchor node or the CU of the anchor node used when sending or receiving data on the backhaul link, and / or port information, and / or information on the prefix length of the IP address;

[0458] The address information that the anchor node or the CU of the anchor node needs to delete, release or remove indicates that the anchor node or the CU of the anchor node no longer uses the address indicated by the information to communicate with the relay node or the DU of the relay node. The address information may be IP address information, and / or newly defined address information (such as BAP address) representing the anchor node or the CU of the anchor node used when sending or receiving data on the backhaul link, and / or port information, and / or information on the prefix length of the IP address;

[0459] New path identification information, which can be for a user DRB (the user DRB is the DRB of the user accessing the relay node or the distribution unit of the relay node), or for control signaling (such as part or all of the F1AP signaling of the relay node or the DU of the relay node). The path identification information represents a path for sending data between the anchor node or the centralized unit of the anchor node and the relay node or the distribution unit of the relay node. This information is used after the IP address is updated.

[0460] Indication information for requesting new address information, such as new IP required indication, is used to notify the CU of the anchor node to configure a new address information for the relay node or the DU of the relay node; further, the information may be included only in the address update request message; in one embodiment, if the anchor node or the CU of the anchor node receives the information, the anchor node or the CU of the anchor node deletes, releases or removes the address indicated by the information, and no longer communicates with the relay node or the distribution unit of the relay node using the address indicated by the information; in another embodiment, if the relay node or the relay node receives the information, the relay node or the distribution unit of the relay node no longer communicates with the anchor node or the CU of the anchor node using the address indicated by the information; in another embodiment, if the distribution unit of the anchor node receives the information, the distribution unit of the anchor node considers that the relay node or the distribution unit of the relay node no longer communicates with the anchor node or the CU of the anchor node using the address indicated by the information.

[0461] Indication information of the number of new address information requested, such as IP number, which is used to notify the CU of the anchor node to configure the number of new address information for the relay node or the DU of the relay node; further, the information may be included only in the address update request message; further, the indication information of the number may also indicate the number of address information (such as IP addresses) requested for a specific purpose, and the specific purpose may be used to send control signaling (the indication information of the number indicates the number of address information requested for sending control signaling (such as sending control signaling of the F1 interface)), or for sending user plane data (the indication information of the number indicates the number of address information requested for sending user plane data (such as sending user plane data of the F1 interface)), or for both sending control signaling and sending user plane data;

[0462] The address information requested to be updated is the address information currently being used by the relay node or the DU of the relay node, which may be IP address information, and / or newly defined address information (such as BAP address) representing the anchor node or the CU of the anchor node used when sending or receiving data on the backhaul link, and / or port information, and / or information on the prefix length of the IP address; the address indicated by the address information needs to be updated; further, the information may be included only in the address update request message;

[0463] Request to delete, release or remove address information, the address information is the address information being used by the relay node or the DU of the relay node, which may be IP address information, and / or newly defined address information (such as BAPaddress) representing the anchor node or the CU of the anchor node used when sending or receiving data on the backhaul link, and / or port information, and / or information on the prefix length of the IP address; further, the information may be included only in the address update request message;

[0464] Information related to the address used when establishing an IPSec tunnel, the information including at least one of the following information: 1) address information used by a relay node or a distribution unit side of a relay node when establishing an IPSec tunnel, the address information may be IP address information, and / or port information, and / or information on the prefix length of an IP address; 2) address information used by an anchor node or a centralized unit side of an anchor node when establishing an IPSec tunnel, the address information may be IP address information, and / or port information, and / or information on the prefix length of an IP address.

[0465] In an optional embodiment of the present application, after the relay node or the DU of the relay node receives the first address update message, at least one of the following actions may be included:

[0466] ■The relay node or the distributed unit of the relay node establishes an SCTP association (association) or a transport layer association (Transport Network Layer Association) with the centralized unit of the anchor node. The establishment of this association is to send F1AP messages between the centralized unit of the anchor node and the relay node or the distributed unit of the relay node. Furthermore, after the association is established, the distributed unit configuration update process can also be performed between the relay node or the distributed unit of the relay node and the centralized unit of the anchor node. The process can refer to TS38.473;

[0467] ■Update the downlink address information of the user DRB served by the relay node or the distribution unit of the relay node (the user DRB is the DRB of the user accessing the relay node or the distribution unit of the relay node), such as DL Transport Layer Information (GTP-U tunnel information), which may include IP address information and GTP-TEID information. The address information is the address information on the side of the relay node or the distribution unit of the relay node. The IP address information in the downlink address information may be updated, or the entire downlink address information may be updated;

[0468] ■Update the uplink address information of the user DRB served by the relay node or the distribution unit of the relay node (the user DRB is the DRB of the user accessing the relay node or the distribution unit of the relay node), such as UL Transport Layer Information (GTP-U tunnel information), which may include IP address information and GTP-TEID information. The address information is the address information of the anchor node or the centralized unit of the anchor node. The IP address information in the uplink address information may be updated, or the entire uplink address information may be updated;

[0469] ■The relay node or the distribution unit of the relay node deletes address information. When the first address update message received by the relay node or the distribution unit of the relay node contains the address information that the relay node or the distribution unit of the relay node needs to delete, the relay node or the distribution unit of the relay node can delete the corresponding address information according to the message.

[0470] ■ The relay node or the distribution unit of the relay node adds new address information, which is used by the relay node or the distribution unit of the relay node to communicate with the anchor node or the centralized unit of the anchor node.

[0471] In an optional embodiment of the present application, after the CU of the anchor node sends the first address update message to the relay node or the DU of the relay node, the following may also be included:

[0472] Receive a first address update confirmation message sent by the relay node or the DU of the relay node.

[0473] The first address update confirmation message is used to confirm that the relay node has adopted a new address.

[0474] The first address update message may be an F1AP message (such as a gNB-CU configuration update message, or a new F1AP message), or an RRC message (such as an RRCReconfiguration message, a Handover Command message, or a new RRC message, such as a Transport Layer Address Configuration). The message may be sent to a distribution unit of a relay node, or may be sent to a mobile terminal part of a relay node.

[0475] The effect of the above-mentioned embodiment is that when the address information of the relay node or the DU side of the relay node changes, it can update the downlink address information of the user DRB it serves according to the received first address update message, and / or the uplink address information of the user DRB, and / or the address information of the distributed unit side of the relay node or the relay node when sending control signaling (user-related control signaling UE-associated signaling, or user-irrelevant control signaling non-UE associated signaling) with the anchor node or the centralized unit of the anchor node, and / or the address information of the centralized unit side of the anchor node or the anchor node when sending control signaling (user-related control signaling UE-associated signaling, or user-irrelevant control signaling non-UE associated signaling) with the anchor node or the centralized unit of the anchor node. There is no need for the anchor node or the centralized unit of the anchor node to send an address update message for each user DRB to the relay node or the distributed unit of the relay node as in the existing mechanism, that is, if the relay node or the relay node serves 100 user DRBs, the anchor node or the centralized unit of the anchor node needs to send 100 messages to the relay node or the distributed unit of the relay node to update the address information of each user DRB. The effect of this embodiment is that it saves the signaling overhead of updating the address information when the relay node or the distributed unit of the relay node serves the user DRB.

[0476] Another effect of the above embodiment is that when the relay node or the DU side of the relay node obtains new address information, it can use the new address information to send and receive control plane data or user plane data with the anchor node or the CU of the anchor node. When the relay node or the DU side of the relay node obtains address information to be deleted, it can remove some addresses in use to save resources. In addition, using the address update request message, the relay node or the DU of the relay node can request the CU of the anchor node to update its address information (such as modify, add, delete, etc.).

[0477] Another effect of the above embodiment is that when the relay node or the DU of the relay node obtains information related to the address used to establish the IPSec tunnel, it can use the information to establish the IPSec tunnel with the anchor node or the centralized unit of the anchor node.

[0478] In an optional embodiment of the present application, after the DU of the anchor node sends the address update notification message to the CU of the anchor node, at least one of the following may also be included:

[0479] Receive the update notification confirmation message sent by the CU of the anchor node;

[0480] The CU of the anchor node sends a second address update message to the relay node or the DU of the relay node;

[0481] The CU of the anchor node sends a second address update message to the relay node or the DU of the relay node, and receives a second address update confirmation message sent by the relay node or the DU of the relay node.

[0482] Among them, the update notification confirmation message is used to confirm that the CU of the anchor node has received the updated address information. In addition, the CU of the anchor node may also send a second address update message to the relay node or the DU of the relay node to inform the relay node or the DU of the relay node of the new address information of the relay node or the DU of the relay node. Further, the CU of the anchor node may also receive a second address update confirmation message, which confirmation information is used to confirm that the relay node or the DU of the relay node has adopted the new address information. It should be noted that in an optional embodiment of the present application, the substantive content of the information contained in the second address update message may be the same as the information contained in the above-mentioned first address update message. That is to say, when updating the address information of the relay node or the distribution unit of the relay node, the address update message (corresponding to the first address update message) may be actively sent by the CU of the anchor node to the relay node or the DU of the relay node, and the address update message (corresponding to the second address update message) may also be sent by the CU of the anchor node to the relay node or the DU of the relay node after the CU of the anchor node receives the address update notification message sent by the DU of the anchor node.

[0483] In an optional embodiment of the present application, after the relay node or the DU of the relay node sends the address update request message to the CU of the anchor node, the following may also be included:

[0484] An address update request confirmation message sent by the CU of the anchor node is received, wherein the address update request confirmation message is used to determine that the CU of the anchor node has received the address update request message sent by the relay node or the DU of the relay node to the CU of the anchor node.

[0485] For the above-mentioned method for updating address information provided in the embodiment of the present application, for the above-mentioned method 1, method 2, and method 3, the following describes these three methods from another perspective. Specifically, the method for updating address information provided in the embodiment of the present application may include:

[0486] Mode 4: The relay node or the DU of the relay node receives the first address update message sent by the CU of the anchor node;

[0487] Mode 5: The CU of the anchor node receives the address update notification message sent by the DU of the anchor node;

[0488] Mode six: The CU of the anchor node receives the address update request message sent by the relay node or the DU of the relay node.

[0489] Optionally, the first address update message, the address update notification message or the address update request message may be an F1AP message, an RRC message or other messages. The information included in the above message may refer to the corresponding description in the above text.

[0490] Optionally, for mode 4, after the relay node or the DU of the relay node receives the first address update message, the following may also be included:

[0491] A first address update confirmation message is sent to the CU of the anchor node.

[0492] Optionally, for mode 5, the CU of the anchor node receives the address update notification message sent by the DU of the anchor node, which may also include any of the following items:

[0493] Send an update notification confirmation message to the DU of the anchor node;

[0494] Sending a second address update message to the relay node or the DU of the relay node;

[0495] A second address update message is sent to the relay node or the DU of the relay node, and a second address update confirmation message is received from the relay node or the DU of the relay node.

[0496] Optionally, for mode 6, after the CU of the anchor node receives the address update request message, the following further includes:

[0497] An address update request confirmation message is sent to the relay node or the DU of the relay node.

[0498] It can be understood that the above-mentioned method 4 and method 1 are corresponding descriptions of the same solution from two perspectives, the above-mentioned method 5 and method 2 are corresponding descriptions of the same solution from two perspectives, and the above-mentioned method 6 and method 3 are corresponding descriptions of the same solution from two perspectives. The specific explanations of method 4, method 5 and method 6 can be found in the corresponding descriptions of method 1, method 2 and method 3 in the previous text, and they will not be repeated here.

[0499] In order to better illustrate the method for updating the address information provided in the embodiment of the present application, the method is further described below in conjunction with a specific embodiment.

[0500] Example 1:

[0501] In this example, the above-mentioned method 1 is used as an example for explanation. The new address information of the relay node (or the distribution unit of the relay node) is allocated or configured by the centralized unit of the anchor node, such as Fig.10 As shown in , the address information update process in this example may include:

[0502] Step 6a-1: The centralized unit of the anchor node sends an address update message 6a-1 (i.e., the first address update message) to the relay node (or the distributed unit of the relay node). The message may include at least one of the following information:

[0503] ■ Identification information of the relay node (or the distribution unit of the relay node);

[0504] ■Old address information of the relay node (or the distribution unit of the relay node);

[0505] ■New address information of the relay node (or the distribution unit of the relay node);

[0506] ■Added address information of the relay node or the DU of the relay node;

[0507] ■ Address information that needs to be deleted, released, or removed by the relay node or the DU of the relay node

[0508] ■Old address information of the anchor node (or the centralized unit of the anchor node or the distributed unit of the anchor node)

[0509] ■ New address information of the anchor node (or the centralized unit of the anchor node or the distributed unit of the anchor node)

[0510] ■Added address information of the anchor node or the CU of the anchor node

[0511] ■ Address information of the anchor node or the CU of the anchor node that needs to be deleted, released or removed

[0512] ■Request to delete, release or remove address information

[0513] ■Information about the addresses used when establishing the IPSec tunnel

[0514] For the specific content of the above information included in the address update message 6a-1, please refer to the above description of "address update message, address update notification message or address update request message".

[0515] Optional, such as Fig.10 As shown in, after step 6a-1, the update process may also include step 6a-2: the relay node (or the distributed unit of the relay node) sends an address update confirmation message 6a-2 (i.e. the above-mentioned first address update confirmation message) to the centralized unit of the anchor node, which confirms that the relay node adopts the new address.

[0516] Optionally, before step 6a-1, the update process may also include step 6a-0: the relay node (or the distributed unit of the relay node) sends an address update request message 6a-0 to the centralized unit of the anchor node. The content of the message can refer to the above description of "first address update message, address update notification message or address update request message". In one embodiment, the request message 6a-0 includes one of the following information: 1) identification information of the relay node or the DU of the relay node; 2) indication information of the number of new address information requested; 3) address information requested to be deleted, released or removed.

[0517] In this optional embodiment, the centralized unit of the anchor node may be the one that receives the address update request message 6a-0 sent by the relay node or the distributed unit of the relay node and then sends the address update message 6a-1 to the relay node or the distributed unit of the relay node according to the request message.

[0518] Example 2:

[0519] In this example, the second method is used as an example to illustrate that the new address information of the relay node (or the distribution unit of the relay node) is allocated by the distribution unit of the anchor node, such as Fig.11 As shown in , the address information update process in this example may include:

[0520] Step 6b-1: The distribution unit of the anchor node sends an address update notification message 6b-1 to the centralized unit of the anchor node. The message may include at least one of the following information:

[0521] ■ Identification information of the relay node (or the distribution unit of the relay node);

[0522] ■ old address information of the relay node (or the distribution unit of the relay node), such as the IP address and / or port, or newly defined address information; the specific content of the address information can refer to the above description of “address update message, address update notification message or address update request message”;

[0523] ■ New address information of the relay node (or the distribution unit of the relay node), such as the IP address and / or port, or newly defined address information; the specific content of the address information can refer to the above description of “address update message, address update notification message or address update request message”;

[0524] ■Added address information of relay node or DU of relay node

[0525] ■ Address information that needs to be deleted, released, or removed by the relay node or the DU of the relay node

[0526] ■Request to delete, release or remove address information

[0527] For other information included in the address update notification message 6b-1, please refer to the above description of "the first address update message, the address update notification message or the address update request message".

[0528] Optional, such as Fig.11 As shown in, after step 6b-1, the update process may further include step 6b-2: the centralized unit of the anchor node sends an update notification confirmation message 6b-2 to the distributed unit of the anchor node, the confirmation message is used to confirm that the centralized unit of the anchor node has received the updated address information.

[0529] Optional, such as Fig.11 As shown in , after step 6b-1, the update process may also include step 6b-3: the centralized unit of the anchor node sends an address update message 6b-3 (i.e., a second address update message) to the relay node (or the distributed unit of the relay node). For other information contained in the address update message 6b-3, please refer to the above description of "first address update message, address update notification message, or address update request message". In other words, after the centralized unit of the anchor node learns the updated address information of the relay node (or the distributed unit of the relay node), it can also inform the relay node (or the distributed unit of the relay node) of the information. The specific content of the message can be obtained by referring to the information obtained in step 6a-1 in the above example 1.

[0530] Optional, such as Fig.11As shown in, after step 6b-3, the update process may also include step 6b-4: the relay node (or the distribution unit of the relay node) sends an address update confirmation message 6b-4 to the centralized unit of the anchor node, which confirms that the relay node (or the distribution unit of the relay node) has adopted the new address. The specific content of the message can refer to step 6a-2 in the above example 1.

[0531] Optional, such as Fig.11 As shown in , before step 6b-1, the update process also includes step 6b-0: the centralized unit of the anchor node sends an address update request message 6b-0 to the distributed unit of the anchor node. The content contained in the message can refer to the above description of "first address update message, address update notification message or address update request message". In this optional scheme, the distributed unit of the anchor node may be an address update notification message 6b-1 sent to the centralized unit of the anchor node according to the request message after receiving the address update request message 6b-0 sent by the centralized unit of the anchor node. In one embodiment, the address update request message 6b-0 includes at least one of the following information: 1) identification information of the relay node or the DU of the relay node, 2) indication information of the number of new address information requested, 3) address information of the relay node or the DU of the relay node to be deleted, released or removed, 4) address information requested to be deleted, released or removed.

[0532] Optional, such as Fig.11 As shown in , before step 6b-0, the update process also includes step 6a-0: the relay node (or the distribution unit of the relay node) sends an address update request message 6a-0 to the centralized unit of the anchor node. The content contained in the message can refer to the above description of "first address update message, address update notification message or address update request message". In one embodiment, refer to the address update request message 6a-0 in the above example 1. At this time, the centralized unit of the anchor node can send a corresponding address update request message 6b-0 to the distribution unit of the anchor node after receiving the address update request message 6a-0, and the distribution unit of the anchor node completes the allocation of new address information of the relay node (or the distribution unit of the relay node).

[0533] Example 3:

[0534] In this example, the above-mentioned method 3 is used as an example for explanation. In this example, the new address information of the relay node (or the distribution unit of the relay node) is obtained by the relay node (or the distribution unit of the relay node) itself (such as through OAM configuration, or through DHCP server allocation, etc.) as an example. Fig.12 As shown in , the address information update process in this example may include:

[0535] Step 6c-1: The relay node (or the distributed unit of the relay node) sends an address update request message 6c-1 to the centralized unit of the anchor node. The message may include at least one of the following information:

[0536] ■ Identification information of the relay node (or the distribution unit of the relay node);

[0537] ■ old address information of the relay node (or the distribution unit of the relay node), such as the IP address and / or port, or newly defined address information; the specific content of the address information can refer to the above description of “address update message, address update notification message or address update request message”;

[0538] ■The new address information of the relay node (or the distribution unit of the relay node), such as the IP address and / or port, or the newly defined address information; the specific content of the address information can refer to the above description of “address update message, address update notification message or address update request message”; other information contained in the address update request message 6c-1 can also refer to the above description of “first address update message, address update notification message or address update request message”.

[0539] Optional, such as Fig.12 As shown in, after step 6c-1, the update process may also include step 6c-2: the centralized unit of the anchor node sends an address update request confirmation message 6c-2 to the relay node (or the distributed unit of the relay node), and the message is used to confirm that the centralized unit of the anchor node has received the address update request message 6c-1 sent by the relay node (or the distributed unit of the relay node). In this example, the confirmation message can be specifically used to determine that the centralized unit of the anchor node has received the updated address information.

[0540] According to the above three address information update schemes provided in the embodiments of the present application, the address information on the relay node side of the GTP-U tunnel or TNL association established between the centralized unit of the anchor node and the relay node (or the distributed unit of the relay node) is updated to the new address information. Therefore, there is no need to separately update the GTP-U tunnel or TNL association of each wireless bearer of each user established between the centralized unit of the anchor node and the relay node. Among them, the messages involved in the above update process (such as address update message, address update confirmation message, address update notification message, address update notification confirmation message, address update request message, address update request confirmation message) can be existing F1 interface messages or newly defined messages. The message can be a non-UE associated message, a UE-associated message, or an RRC message; the message can be sent to the distributed unit of the relay node or to the mobile terminal part of the relay node.

[0541] The present application also provides a solution for configuring IPSec tunnel information, which includes the following steps:

[0542] Step 7-1: The anchor node or the centralized unit of the anchor node sends an IPSec tunnel configuration message to the relay node or the distributed unit of the relay node, so that the relay node or the distributed unit of the relay node establishes an IPSec tunnel with the anchor node or the centralized unit of the anchor node according to the content in the IPSec tunnel configuration message. The IPSec tunnel configuration message includes at least one of the following information:

[0543] ■ Identification information of the relay node or the distribution unit of the relay node;

[0544] ■ Address information used by the relay node or the distribution unit side of the relay node when establishing an IPSec tunnel. The address information may be IP address information, and / or port information, and / or information on the prefix length of the IP address;

[0545] ■ Address information used by the anchor node or the centralized unit side of the anchor node when establishing an IPSec tunnel. The address information may be IP address information, and / or port information, and / or IP address prefix length information.

[0546] The IPSec tunnel configuration message may be an F1AP message (such as gNB-CU Configuration Update) or an RRC message. In one implementation, when an F1 interface is established between an anchor node or a centralized unit of an anchor node and a relay node or a distributed unit of a relay node, the anchor node or the centralized unit of an anchor node sends an IPSec tunnel configuration message via an F1AP message; in another implementation, when an F1 interface is not established between an anchor node or a centralized unit of an anchor node and a relay node or a distributed unit of a relay node, the anchor node or the centralized unit of an anchor node sends an IPSec tunnel configuration message via an RRC message.

[0547] The beneficial effect of this example is that the relay node or the distributed unit of the relay node can establish an IPSec tunnel with the anchor node or the centralized unit of the anchor node according to the content of the received IPSec tunnel configuration message, thereby providing security protection for data transmission on the F1 interface.

[0548] Each solution provided in the embodiments of the present application has at least the following beneficial effects:

[0549] 1. Based on the solution provided in the first aspect of the present application, different indication information can be added to data packets of different types of user data to facilitate distinguishing different types of user data;

[0550] 2. Based on the solution provided in the second aspect of the present application, each node serving user data can obtain the address information of the source sending node and the destination receiving node (access relay node) of the user data, which can facilitate adding different indication information to data packets of different types of user data, thereby allowing the distribution unit of the anchor node to distinguish different types of user data.

[0551] 3. Based on the solution provided in the third aspect of the present application, the address information on the relay node side of the GTP-U tunnel or TNL association established between the centralized unit of the anchor node and the relay node (or the distributed unit of the relay node) can be updated to the new address information, without the need to separately update the GTP-U tunnel or TNL association for each wireless bearer of each user established between the centralized unit of the anchor node and the relay node. Another effect is that when the relay node or the DU side of the relay node obtains new address information, it can use the new address information to send and receive control plane data or user plane data with the anchor node or the CU of the anchor node. When the relay node or the DU side of the relay node obtains address information to be deleted, it can remove some addresses in use to save resources. In addition, using the first address update request message, the relay node or the DU of the relay node can request the CU of the anchor node to update its address information (such as modifying, adding, deleting, etc.). Another effect is that an IPSec tunnel is established between the relay node or the distributed unit of the relay node and the anchor node or the centralized unit of the anchor node, thereby providing security protection for data transmission on the F1 interface.

[0552] Corresponding to Figure 4 Based on the same principle as the method shown in , the embodiment of the present application provides an information configuration device, which can be set in the first node, such as Fig.13 As shown, the information configuration device 100 may include a configuration request sending module 110 and a configuration response receiving module 120, wherein:

[0553] A configuration request sending module 110, configured to send a first configuration request message to a second node;

[0554] The configuration response receiving module 120 is configured to receive a first configuration response message sent by the second node based on the first configuration request message.

[0555] Optionally, the first configuration request message is used to negotiate attribute indication information of user data between the first node and the second node;

[0556] The attribute indication information of the user data is configured by any one or more nodes:

[0557] CU of the anchor node;

[0558] CU-CP of anchor node;

[0559] CU-UP of anchor nodes;

[0560] DU of the anchor node;

[0561] Other base stations or CUs of other base stations;

[0562] The source sending node of user data.

[0563] Optionally, the first node and the second node include any of the following:

[0564] The first node is a CU of an anchor node, and the second node is a DU of an anchor node, another base station, or a CU of another base station;

[0565] The first node is a CU-CP of an anchor node, and the second node is a CU-UP of an anchor node, a DU of an anchor node, another base station, or a CU of another base station;

[0566] The first node is other base stations or CUs of other base stations, and the second node is a CU of an anchor node or a CU-CP of an anchor node.

[0567] Optionally, the first configuration request message carries relevant information about user data that the first node expects or requests to be accepted by the second node, and the first configuration request message includes at least one of the following:

[0568] Information about the attributes of the data;

[0569] Attribute indication information of user data;

[0570] Relevant information of the destination receiving node;

[0571] Relevant information of the source sending node;

[0572] Information about the data transmission path;

[0573] The first configuration response message carries relevant information of the user data accepted by the second node. The first configuration response message includes at least one of the following:

[0574] Information about the attributes of the data;

[0575] Attribute indication information of user data;

[0576] Relevant information of the source sending node;

[0577] Relevant information of the destination receiving node;

[0578] Information about the data transfer path.

[0579] Optionally, the information configuration device 100 may further include:

[0580] A configuration request receiving module, configured to receive a second configuration request message sent by a third node;

[0581] The configuration response sending module is used to send a second configuration response message to the third node based on the second configuration request message.

[0582] Optionally, receiving the second configuration request message may be before sending the first configuration request message to the second node, and the user data targeted by the first configuration request message is determined according to the user data targeted by the second configuration request message.

[0583] Optionally, if the attribute indication information of the user data is configured by the first node, sending the second configuration response message to the third node may be after receiving the first configuration response message, or may be before sending the first configuration request message to the second node, or before sending the first configuration request message to the second node.

[0584] Optionally, if the attribute indication information of the user data is configured by the second node, sending the second configuration response message to the third node is after receiving the first configuration response message.

[0585] Optionally, if the second configuration response message is sent to the third node after the first configuration response message is received, the second configuration response message may be determined based on the first configuration response message.

[0586] Optionally, if the attribute indication information of the user data is configured by the first node, the first configuration response message is determined by the second node based on the third configuration response message;

[0587] The third configuration response message is obtained by the second node in the following manner:

[0588] Sending a third configuration request message to the fourth node;

[0589] A third configuration response message is received, which is returned by the fourth node based on the third configuration request message.

[0590] Corresponding to Figure 4 Based on the same principle as the method shown in , the embodiment of the present application provides an information configuration device, which can be set in the second node, such as Fig.14 As shown, the information configuration device 200 may include a configuration request receiving module 210 and a configuration response sending module 220, wherein:

[0591] A configuration request receiving module 210 is configured to receive a first configuration request message sent by a first node;

[0592] The configuration response sending module 220 is configured to send a first configuration response message to the first node according to the first configuration request message.

[0593] Optionally, the information configuration device 200 may further include:

[0594] A configuration request sending module, used to send a third configuration request message to the fourth node;

[0595] The configuration response receiving module is used to receive a third configuration response message returned by the fourth node based on the third configuration request message.

[0596] Corresponding to Fig. 9 Based on the same principle as the method shown in , an embodiment of the present application provides an information interaction device, which can be set in a fifth node, and the device can include a configuration message sending module, which is used to:

[0597] A fourth configuration message is sent to the sixth node, where the message is used for the fifth node and the sixth node to exchange relevant information of a source sending node and / or relevant information of a destination receiving node of user data.

[0598] Optionally, the fifth node and the sixth node are at least one of the following:

[0599] The fifth node is a centralized unit CU of the anchor node, and the sixth node is a distributed unit DU of the anchor node, another base station, or a CU of another base station;

[0600] The fifth node is a CU of another base station or another base station, and the sixth node is a CU of an anchor node;

[0601] The fifth node is the DU of the anchor node, and the sixth node is the CU of the anchor node.

[0602] Optionally, the fourth configuration message includes at least one of the following:

[0603] User identification information;

[0604] Information about the attributes of the data;

[0605] Relevant information of the source sending node and / or relevant information of the destination receiving node.

[0606] Optionally, when the configuration message sending module sends the fourth configuration message to the sixth node, it may be specifically used to:

[0607] receiving a fourth configuration request message sent by a sixth node;

[0608] A fourth configuration message is sent to the sixth node based on the node configuration request information.

[0609] Optionally, the fourth configuration request message includes at least one of the following:

[0610] User identification information;

[0611] Information about the attributes of the data;

[0612] Relevant information of the source sending node;

[0613] Information about the destination receiving node.

[0614] Optionally, the fourth configuration request message and the fourth configuration message do not simultaneously include relevant information of the same node, and the same node is a source sending node or a target receiving node.

[0615] Optionally, the device may further include:

[0616] The configuration confirmation message receiving module is used to receive a fourth configuration confirmation message sent by the sixth node based on the node configuration information after sending the fourth configuration message to the sixth node.

[0617] Optionally, the node configuration confirmation message may include at least one of the following:

[0618] User identification information;

[0619] Information about the attributes of the data;

[0620] Relevant information of the source sending node;

[0621] Information about the destination receiving node.

[0622] Optionally, the fourth configuration message and the node configuration confirmation message do not simultaneously include relevant information of the same node, and the same node is a source sending node or a target receiving node.

[0623] Corresponding to Fig. 9 Based on the same principle as the method shown in , an embodiment of the present application provides an information interaction device, which can be set in the sixth node, and the device can include a configuration message receiving module, and the configuration message receiving module is used to:

[0624] A fourth configuration message sent by the fifth node is received, where the message is used for the fifth node and the sixth node to exchange relevant information of a source sending node and / or relevant information of a destination receiving node of user data.

[0625] Optionally, the fifth node and the sixth node are at least one of the following:

[0626] The fifth node is a centralized unit CU of the anchor node, and the sixth node is a distributed unit DU of the anchor node, another base station, or a CU of another base station;

[0627] The fifth node is a CU of another base station or another base station, and the sixth node is a CU of an anchor node;

[0628] The fifth node is the DU of the anchor node, and the sixth node is the CU of the anchor node.

[0629] Optionally, the fourth configuration message includes at least one of the following:

[0630] User identification information;

[0631] Information about the attributes of the data;

[0632] Relevant information of the source sending node and / or relevant information of the destination receiving node.

[0633] Optionally, the fourth configuration message receiving module is specifically used to:

[0634] a fourth configuration request message sent to a fifth node;

[0635] A fourth configuration message sent by the fifth node based on the node configuration request information is received.

[0636] Optionally, the fourth configuration request message includes at least one of the following:

[0637] User identification information;

[0638] Information about the attributes of the data;

[0639] Relevant information of the source sending node;

[0640] Information about the destination receiving node.

[0641] Optionally, the fourth configuration request message and the fourth configuration message do not simultaneously include relevant information of the same node, and the same node is a source sending node or a target receiving node.

[0642] Based on the same principle as the method for updating the address information of a relay node provided in the embodiment of the present application, the embodiment of the present application provides an address information updating device for a relay node, wherein if the updating device can be set in the CU of the anchor node, the device includes an address update message sending module, and the sending module is used to:

[0643] Sending a first address update message to the relay node or the DU of the relay node;

[0644] If the updating device is set in the DU of the anchor node, the device includes an address update notification module, which is used to:

[0645] Used to send an address update notification message to the CU of the anchor node;

[0646] If the updating device is set in the relay node or the DU of the relay node, the device includes an address update request module, which is used to:

[0647] Send an address update request message to the CU of the anchor node.

[0648] Optionally, the first address update message, the address update notification message, or the address update request message includes at least one of the following information:

[0649] Identification information of the relay node or the DU of the relay node;

[0650] Address information of the relay node or DU of the relay node before update;

[0651] Updated address information of the relay node or the DU of the relay node;

[0652] Newly added address information of the relay node or DU of the relay node;

[0653] The address information of the relay node or the DU of the relay node to be deleted;

[0654] An indication of the number of new address information requested;

[0655] Request updated address information;

[0656] The address information requested to be removed;

[0657] Information about the addresses used when establishing an IPSec tunnel.

[0658] Optionally, when the updating device is set in the CU of the anchor node, it also includes:

[0659] The address update confirmation message receiving module is used to receive a first address update confirmation message sent by the relay node or the DU of the relay node based on the first address update message.

[0660] In this solution, the new address information of the relay node or the DU of the relay node may be allocated by the distribution unit of the anchor node.

[0661] Optionally, when the updating device is set in the DU of the anchor node, the updating device may further include an update notification confirmation message receiving module, which is used to:

[0662] The update notification confirmation message sent by the CU of the receiving anchor node based on the address update notification message.

[0663] In this solution, the new address information of the relay node or the DU of the relay node may be allocated by the centralized unit of the anchor node.

[0664] Optionally, when the updating device is set in the relay node or the DU of the relay node, the updating device may further include:

[0665] The confirmation message receiving module is used to receive an address update request confirmation message sent by the CU of the anchor node based on the address update request message.

[0666] In this solution, the new address information of the relay node or the DU of the relay node may be acquired by the relay node or the DU of the relay node itself.

[0667] The embodiment of the present application provides an address information updating method for a relay node, and the embodiment of the present application provides an address information updating device for a relay node. If the device is provided in a relay node or a DU of a relay node, the device includes an address update message receiving module, and the message receiving module is used to:

[0668] Receiving a first address update message sent by the CU of the anchor node;

[0669] If the device is set in the CU of the anchor node, the device includes an address update notification receiving module, and the notification receiving module is used to:

[0670] Receive an address update notification message sent by the DU of the anchor node;

[0671] If the device is set in the CU of the anchor node, the device includes an address update request receiving module, and the update request receiving module is used to:

[0672] Receive an address update request message sent by a relay node or a DU of the relay node.

[0673] Optionally, the first address update message, the address update notification message, or the address update request message includes at least one of the following information:

[0674] Identification information of the relay node or the DU of the relay node;

[0675] Address information of the relay node or DU of the relay node before update;

[0676] Updated address information of the relay node or the DU of the relay node;

[0677] Newly added address information of the relay node or DU of the relay node;

[0678] The address information of the relay node or the DU of the relay node to be deleted;

[0679] Instructions for requesting new address information;

[0680] an indication of the number of new address information requested;

[0681] Request updated address information;

[0682] The address information requested to be removed;

[0683] Information about the addresses used when establishing a security-related IPSec tunnel.

[0684] Optionally, when the updating device is set in the relay node or the DU of the relay node (the new address information of the relay node or the DU of the relay node may be allocated by the CU of the anchor node), the device further includes:

[0685] The address update confirmation information sending module is used to send a first address update confirmation message to the CU of the anchor node after receiving the first address update message sent by the CU of the anchor node.

[0686] Optionally, when the updating device is set in the CU of the anchor node (the new address information of the relay node or the DU of the relay node may be allocated by the DU of the anchor node), the updating device may further include an update notification confirmation message sending module, which is used to:

[0687] After receiving the address update notification message sent by the DU of the anchor node, an update notification confirmation message is sent to the DU of the anchor node.

[0688] Optionally, when the updating device is set in the CU of the anchor node (the new address information of the relay node or the DU of the relay node may be allocated by the DU of the anchor node), the device may further include at least one of the following modules:

[0689] An address update message sending module, used to send a second address update message to the relay node or the DU of the relay node;

[0690] The address update confirmation message receiving module is used to receive a second address update confirmation message sent by the relay node or the DU of the relay node based on the second address update message.

[0691] Optionally, when the updating device is set in the CU of the anchor node (the new address information of the relay node or the DU of the relay node can be obtained by the relay node or the DU of the relay node itself), the updating device may also include an update request confirmation sending module, which is used to:

[0692] After receiving the address update request message sent by the relay node or the DU of the relay node, an address update request confirmation message is sent to the relay node or the DU of the relay node.

[0693] Based on the principle of the solution provided in the present application, an embodiment of the present application provides an information interaction system, which may include at least one of the devices provided in any embodiment of the present application.

[0694] Based on the principle of the solution provided in the present application, an embodiment of the present application provides a communication network system, which may include the information interaction system provided in the embodiment of the present application.

[0695] An embodiment of the present application also provides an electronic device, which includes a processor and a memory; wherein the memory stores machine-readable instructions; and the processor is used to execute the machine-readable instructions to implement the method provided by any embodiment of the present application.

[0696] The present application also provides a computer-readable storage medium in an embodiment, on which a computer program is stored. When the computer program is executed by a processor, the method provided in any embodiment of the present application is implemented.

[0697] In an alternative embodiment, an electronic device is provided, such as Fig.15 As shown, Fig.15 The electronic device 4000 shown includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present application.

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

[0699] The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.15 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0700] The memory 4003 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0701] The memory 4003 is used to store application code for executing the solution of the present application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the application code stored in the memory 4003 to implement the content shown in any of the above method embodiments.

[0702] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0703] The above descriptions are only some embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method performed by a centralized unit IAB anchor CU of an integrated access and backhaul anchor node, It is characterized in that The method comprises: receiving a first message for allocating an Internet Protocol IP address from a distribution unit IAB anchor DU of an integrated access and backhaul anchor node, the IP address being used for data transmission of a control plane and a user plane between the IAB anchor CU and the integrated access and backhaul IAB node through an F1 interface; A first radio resource control (RRC) message is sent to the IAB node, where the first RRC message includes the IP address allocated by the IAB anchor DU based on the first message.

2. The method according to claim 1, It is characterized in that The first message includes the IP address allocated to the IAB node and first indication information of the use of the IP address; The first RRC message includes the IP address allocated to the IAB node and second indication information of the use of the IP address.

3. The method according to claim 2, It is characterized in that The IP address usage includes F1 control plane F1-C data flow and F1 user plane F1-U data flow.

4. The method according to claim 1, It is characterized in that Also includes: receiving a second RRC message requesting an IP address from the IAB node; A second message for acquiring the IP address of the IAB node is sent to the IAB anchor DU.

5. The method according to claim 4, It is characterized in that The second RRC message includes the number of IP addresses requested for the F1-C data flow and the number of IP addresses requested for the F1-U data flow; The second message includes the number of IP addresses requested for the F1-C data flow and the number of IP addresses requested for the F1-U data flow.

6. The method according to claim 1, It is characterized in that The first RRC message includes the IP address of the IAB node to be released.

7. The method according to claim 4, It is characterized in that The second message includes an IP address to be released which is no longer used by the IAB node.

8. A method performed by a distribution unit IAB anchor DU of an integrated access and backhaul anchor node, It is characterized in that The method comprises: receiving a second message for acquiring an Internet Protocol IP address of an IAB node from a centralized unit IAB anchor CU of an integrated access and backhaul anchor node; Sending a first message for allocating an IP address to the IAB anchor CU, where the IP address is used for data transmission of a control plane and a user plane between the IAB anchor CU and an integrated access and backhaul IAB node through an F1 interface; The first radio resource control RRC message sent by the IAB anchor CU to the IAB node includes the IP address.

9. A method performed by an integrated access and backhaul IAB node, It is characterized in that The method comprises: Sending a second radio resource control RRC message requesting an IP address to a centralized unit IAB anchor CU of an integrated access and backhaul anchor node; A first RRC message is received from the IAB anchor CU, wherein the first RRC message includes the IP address assigned from the first message sent from the IAB anchor DU to the IAB anchor CU, wherein the IP address is used for data transmission on a control plane and a user plane between the IAB anchor CU and the IAB node through an F1 interface.

10. A method performed by a centralized unit control plane entity IAB anchor CU-CP of an integrated access and backhaul anchor node, It is characterized in that Sending a first configuration request message to a centralized unit user plane entity IAB anchor CU-UP of an integrated access and backhaul anchor node, wherein the first configuration request message includes information related to first user data, and the first user data is sent from the IAB anchor CU-UP to the integrated access and backhaul anchor node via a distributed unit IAB anchor DU of the integrated access and backhaul anchor node; sending a second configuration request message to the IAB anchor DU, the second configuration request message including information related to second user data, the second user data being sent from the IAB anchor DU to the IAB node; Wherein, the IAB anchor CU-CP and the IAB anchor CU-UP are included in a centralized unit IAB anchor CU of an access and backhaul integrated anchor node; The information related to the first user data includes identification information of a radio bearer, first General Packet Radio Service Tunneling Protocol GTP tunnel endpoint information, and information for setting a data packet field of the first user data, wherein the first user data is sent through a GTP tunnel corresponding to the first GTP tunnel endpoint information; The information related to the second user data includes the IP address of the IAB node, identification information of a backhaul link channel used to transmit the second user data, identification information of the IAB node, identification information of a path, and identification information of a next-hop node.

11. The method according to claim 10, It is characterized in that The information for setting the data packet field of the first user data includes information of a differentiated services code point DSCP and information of a flow identifier; The information related to the second user data also includes DSCP information and flow identifier information.

12. The method according to claim 11, It is characterized in that At least one of a DSCP field or a flow identification field of the data packet of the first user data is set by the IAB anchor CU-UP based on the information for setting the data packet field of the first user data.

13. The method according to claim 10, It is characterized in that Also includes: receiving a third configuration request message from the base station; sending a third configuration response message to the base station, the third configuration response message including information related to third user data, the third user data being sent from the base station to the IAB node through the IAB anchor DU; The information related to the third user data includes identification information of the radio access bearer RAB, endpoint information of the second GTP tunnel, and information for setting a data packet field of the third user data, and the third user data is sent through the GTP tunnel corresponding to the second GTP tunnel endpoint information; The information for setting the data packet field of the third user data includes DSCP information and flow identifier information.

14. The method according to claim 13, It is characterized in that At least one of the DSCP field or the flow identification field of the data packet of the third user data is set by the base station based on the information for setting the data packet field of the third user data.

15. The method according to claim 13, It is characterized in that The second user data includes the first user data and the third user data.

16. The method according to claim 13, It is characterized in that The first GTP tunnel endpoint information includes at least one of address information of a destination receiving node or a tunnel endpoint identifier TEID of the destination receiving node; The second GTP tunnel endpoint information includes at least one of address information of the destination receiving node or TEID of the destination receiving node.

17. A method performed by a centralized unit user plane entity IAB anchor CU-UP of an integrated access and backhaul anchor node, It is characterized in that receiving a first configuration request message from a centralized unit control plane entity IAB anchor CU-CP of an integrated access and backhaul anchor node, wherein the first configuration request message includes information related to the first user data; Sending the first user data to the access and backhaul integrated IAB node through the distribution unit IAB anchor DU of the access and backhaul integrated anchor node; Wherein, the centralized unit IAB anchor CU of the integrated access and backhaul anchor node includes the IAB anchor CU-CP and the IAB anchor CU-UP; The information related to the first user data includes identification information of the wireless bearer, first General Packet Radio Service Tunnel Protocol GTP tunnel endpoint information, and information for setting the data packet field of the first user data. The first user data is sent through the GTP tunnel corresponding to the first GTP tunnel endpoint information.

18. A method performed by a distribution unit IAB anchor DU of an integrated access and backhaul anchor node, It is characterized in that The method includes: receiving a configuration request message from a centralized unit IAB anchor CU of an integrated access and backhaul anchor node, the configuration request message including information related to second user data, the second user data being sent from the IAB anchor DU to the integrated access and backhaul IAB node; sending the second user data to the IAB node; The second user data includes at least one of first user data or third user data, the first user data is sent from the IAB anchor CU to the IAB node, and the third user data is sent from the base station to the IAB node; The information related to the second user data includes at least one of the IP address of the IAB node, identification information of the return link channel used to transmit the second user data, identification information of the IAB node, identification information of the path, identification information of the next hop node, differentiated service code point DSCP information, or flow identification information.

19. The method according to claim 18, It is characterized in that The IAB anchor CU includes a centralized unit control plane entity IAB anchor CU-CP of a backhaul integrated anchor node and a centralized unit user plane entity IAB anchor CU-UP of an access and backhaul integrated anchor node; The first user data includes a data packet sent from the IAB anchor CU-UP based on information related to the first user data; The information related to the first user data is sent from the IAB anchor CU-CP to the IAB anchor CU-UP, and the information related to the first user data includes identification information of the wireless bearer, first general packet radio service tunneling protocol GTP tunnel endpoint information, and information for setting the data packet field of the first user data. The first user data is sent through the GTP tunnel corresponding to the first GTP tunnel endpoint information.

20. The method according to claim 19, It is characterized in that The third user data includes a data packet sent from the base station based on information related to the third user data; The information related to the third user data is sent from the base station to the IAB anchor CU, the information related to the third user data includes identification information of the radio access bearer RAB, second GTP tunnel endpoint information, and information for setting a data packet field of the third user data, and the third user data is sent through the GTP tunnel corresponding to the second GTP tunnel endpoint information; The information for setting the data packet field of the third user data includes DSCP information and flow identifier information.

21. The method according to claim 19, It is characterized in that The information for setting the data packet field of the first user data includes DSCP information and flow identifier information.

22. The method according to claim 20, It is characterized in that At least one of a DSCP field or a flow identification field of a data packet of the first user data is set by the IAB anchor CU-UP based on the information of setting the data packet field of the first user data; At least one of the DSCP field or the flow identification field of the data packet of the third user data is set by the base station based on the information for setting the data packet field of the third user data.

23. A method performed by a user equipment UE in a dual-connection network, It is characterized in that The method comprises: receiving first user data from a base station through an integrated access and backhaul IAB node, wherein the first user data includes first attribute indication information, and the first attribute indication information is included in at least one of a differentiated services code point DSCP field or a flow identification field; receiving second user data from a centralized unit user plane entity IAB anchor CU-UP of an integrated access and backhaul anchor node through the IAB node, wherein the second user data includes second attribute indication information, and the second attribute indication information is included in at least one of a DSCP field or a flow identification field; The first attribute indication information and the second attribute indication information include DSCP information and flow label information.

24. A centralized unit IAB anchor CU of an integrated access and backhaul anchor node, It is characterized in that include: transceiver, and A processor is coupled to the transceiver and configured to execute the method according to any one of claims 1 to 7.

25. A distribution unit IAB anchor DU of an integrated access and backhaul anchor node, It is characterized in that include: transceiver, and A processor coupled to the transceiver and configured to execute the method according to any one of claims 8 or 18-22.

26. An IAB node integrating access and backhaul, It is characterized in that include: transceiver, and A processor is coupled to the transceiver and configured to execute the method of claim 9.

27. A centralized unit control plane entity IAB anchor CU-CP of an integrated access and backhaul anchor node, It is characterized in that include: transceiver, and A processor is coupled to the transceiver and configured to execute the method according to any one of claims 10 to 16.

28. A centralized unit user plane entity IAB anchor CU-UP of an integrated access and backhaul anchor node, It is characterized in that include: transceiver, and A processor is coupled to the transceiver and configured to execute the method of claim 17.

29. A user equipment UE in a dual-connection network, It is characterized in that include: transceiver, and A processor is coupled to the transceiver and configured to execute the method of claim 23.